Hello,
I have a big problem with reception of a CXF answer and i'm looking for a
solution since many days. In my aut-generated classes, i have a null
pointer.
I use "apache-cxf-2.1.2". From a wsdl file, with https, i've auto-generated
many classes with wsdl2java. My application send a request to
Daniel Kulp wrote:
- ensuring the multiplicity of conduit beans configured alongside a
failover selector is consistent with the set of ports defined in the
WSDL, as the CXF static failover strategy is based on burning the
alternate ports into a multi-port service definition in the WSDL.
Well,
Hi all,
I've attached another patch to
https://issues.apache.org/jira/browse/CXF-1836 that implements the
required Service Properties on the DistributionProvider service. The
patch is called DistributionProvider-properties.patch and a direct link
to it can be found here:
https://issues.apach
Quick question:
On Tuesday 07 October 2008, [EMAIL PROTECTED] wrote:
> Modified: cxf/branches/2.1.x-fixes/api/pom.xml
>
> + org.apache.geronimo.specs
> + geronimo-j2ee-connector_1.5_spec
> +
Could this have provided so we don't ship this and have it
added
Thanks David, patch applied.
/Eoghan
David Bosschaert wrote:
Hi all,
I've attached another patch to
https://issues.apache.org/jira/browse/CXF-1836 that implements the
required Service Properties on the DistributionProvider service. The
patch is called DistributionProvider-properties.patch
Yes, we should not ship this jar, I will fix it in my next commit.
Thanks,
Willem
Daniel Kulp wrote:
Quick question:
On Tuesday 07 October 2008, [EMAIL PROTECTED] wrote:
Modified: cxf/branches/2.1.x-fixes/api/pom.xml
+org.apache.geronimo.specs
+geronimo-j2
Most likely, the response message is actually wrong according to the
schema.
The request message makes it look like the element form of the schema is
set to "unqualified". The "urn:connect" element is qualified properly,
but the child elements (user, etc...) are not namespace qualified.
I'd definitely prefer if the excpetion was on of the I18N things. A
LARGE chunk of our users are actually from China. According to google
analytics, China is #2 after the US. It's definitely important to keep
the option open to make this stuff localizable. ESPECIALLY for
configuration th
Hi Dan,
I have included a first exception. It looks like this:
org.apache.cxf.common.i18n.Message msg = new
org.apache.cxf.common.i18n.Message("INSUFFICIENT_CONFIGURATION_CONDUIT",
LOG, name);
throw new ConfigurationException(msg);
This looks extremly ugly as Message is already imported eith
Yes, it was good that James Mao created a CXF-zh list, with so many Chinese
committers, developing a Chinese language CXF community was a huge bonus for
us that the other web service stacks didn't have. Doing Google blog
searches, we do seem to lag in Japan though because the Axis 1.x web site is
I'm +1 to the constructor. I find the new-ing of messages to be a pain.
On Tue, Oct 7, 2008 at 5:27 PM, Christian Schneider <[EMAIL PROTECTED]
> wrote:
> Hi Dan,
>
> I have included a first exception. It looks like this:
>
> org.apache.cxf.common.i18n.Message msg = new
> org.apache.cxf.common.i18
Christian, usage of "you" is somewhat uncommon in error messages, wouldn't
you say? Although I think it's more permissable for the first two messages
below, because you're asking a question, but normally the latter two should
avoid "you".
Glen
cschneider-2 wrote:
>
> DISPATCH_FAILURE_MSG = Di
Well, I've always liked technical writing that uses 'you' to avoid the
passive. Since this is a config error, it seems to me to have an audience
that can handle a you. But that's just my opinion.
On Tue, Oct 7, 2008 at 7:25 PM, Glen Mazza <[EMAIL PROTECTED]> wrote:
>
> Christian, usage of "you" i
I like the use of "you" also. It avoids needlessly convoluted syntax
and it makes the messages a little more personal.
That said consistency is king.
How about:
Configure a and set the
jndiConnectionFactoryName.
The jmsConfig property is required.
Benson's suggestion for the second error mes
Technical documentation, yes, I use "you" all the time there. Windows- and
browser-error messages, frequently yes also, because you're trying to be
warm and friendly to a non-technical user. Lower-level Oracle database
error[1] or operating system messages, I would say "you" looks strange, and
i
Hi,
I ran into an interesting interop issue with wsa:Action between CXF
and JAX-WS RI (2.1.4). I have a simple service class, no sei, no
@Action annotations, something like:
@WebService
@Addressing
class Calculator {
public int add(in n1, in2) {
return n1 + n2;
}
}
CXF generated the followi
With a strong reation from opensource community, SpringSource seems to have
taken a major turnaround. Rod Johnson, in a recent post on SpringSource has
announced modifications in the Spring enterprise maintenance policy. More on
this link:
http://blog.springsource.com/2008/10/07/a-question-of-bal
It seems it's not needed anymore.
On Wed, Oct 8, 2008 at 8:13 AM, CXF Explorer
<[EMAIL PROTECTED]> wrote:
>
> With a strong reation from opensource community, SpringSource seems to have
> taken a major turnaround. Rod Johnson, in a recent post on SpringSource has
> announced modifications in the S
18 matches
Mail list logo
