SAML signed token rejected
Hi all, I use CXF 2.0.4, opensaml 1.1b and wss4j 1.5 to generate and send a SOAP message containing a signed sender-vouches SAML token to a secured Web Service deployed on a Web Logic Server. In order to do it, I set the action of the wss4joutinterceptor to "SAMLToken Signature" instead of "SAMLTokenSigned" and I configure the rest nicely: the signature only sign the saml assertion. If I use the action "SAMLTokenSigned", it is exactly the same message but the body is signed as well (I don't understand why though). Anyway, when I send my token out, the token is rejected (the certificate and issuer and everything else on the server side is good though). The only difference I spotted when looking at a saml signed token generated with web logic is that they sign the BinarySecurity token and have an extra XML tag in the transform reference of the signature: http://www.w3.org/2001/10/xml-exc-c14n#"; PrefixList="" /> ( this is useless though since the prefixlist is empty...). I am a bit confused and don't really know what to think. In addition, I can not find in the specs the section about this. Any help would be appreciated. Thanks, Benjamin Coiffe
saml holder of key and CXF
rkspace/Kensington.SILVER/plugins/webservicestudio/test/security/c
erts/clientKS.jks");
configuration.put("C:/eclipse3.2.1/workspace/Kensington.SILVER/plugins/w
ebservicestudio/test/security/certs/clientKS.jks", properties);
configuration.put(WSHandlerConstants.USER, "admin");
client.getOutInterceptors().add(new
WSS4JOutInterceptor(configuration));
client.getOutInterceptors().add(new SAAJOutInterceptor());
try {
Object o = client.invoke("GetDatabases", new
Object[0]);
System.out.println(o);
} catch (Exception e) {
e.printStackTrace();
}
}
Benjamin Coiffe
wsdl containing multiple ports and dynamic client
Hi, I have a WSDL that contains multiple ports binding. I can easily generate a Dynamic Client using the wsdl but I could not find how to set the port to use before calling invoke(String operationName,Object...parameters). The default behaviour is to execute the first port in the WSDL. But I want to be able to change that before invoking the Web Service. Any Ideas? Thanks, Benjamin Coiffe
RE: Wrapped/UnWrapped document/literal question and issues
Forget about it! Sorry for the spam. I see that it is fixed in 2.0.4... Benjamin From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] Sent: 25 January 2008 10:16 To: cxf-user@incubator.apache.org Subject: Wrapped/UnWrapped document/literal question and issues Hi, I am a bit confused about the Wrapper style, Un-Wrapper style and I would be grateful could clarify a few thing about the way it is handle in CXF. The Jax-Ws specification gives some specific rules about the wrapper, un-wrapper style in section 2.3.1.2 and it works perfectly on the java side. The WSDL attached defines an operation that qualifies for the wrapper style: Boolean verifyTerm(String,String,String,String). Unfortunately, it affects the SOAP message as well... Instead of sending: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower It sends this: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower This doesn't works with the two web service stacks I have tries. Moreover, in doc-literal, there is "at most" one part in the Body element of the soap message and that must point to an XSD element (Basic Profile section 5.3.1, section 4.7.8 R2712). In Short the CXF SOAP message is not conform to the WS-I. For your information, I was using the Dynamic client to generate this. Any clarification appreciated, Benjamin Coiffe
Wrapped/UnWrapped document/literal question and issues
Hi, I am a bit confused about the Wrapper style, Un-Wrapper style and I would be grateful could clarify a few thing about the way it is handle in CXF. The Jax-Ws specification gives some specific rules about the wrapper, un-wrapper style in section 2.3.1.2 and it works perfectly on the java side. The WSDL attached defines an operation that qualifies for the wrapper style: Boolean verifyTerm(String,String,String,String). Unfortunately, it affects the SOAP message as well... Instead of sending: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower It sends this: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower This doesn't works with the two web service stacks I have tries. Moreover, in doc-literal, there is "at most" one part in the Body element of the soap message and that must point to an XSD element (Basic Profile section 5.3.1, section 4.7.8 R2712). In Short the CXF SOAP message is not conform to the WS-I. For your information, I was using the Dynamic client to generate this. Any clarification appreciated, Benjamin Coiffe
RE: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Cheers Daniel,
But I read that CXF-927 on your jira. And I am thinking that if I do
that in the wsdl:
http://java.sun.com/xml/ns/jaxws";>
false
I could deactivate the Wrapper mode for the method verifyTerm.
Then, in WSDLServiceBuilder.checkedWrapped, I can check for the tag in
the wsdl (xmlschema) and that would do the trick ( it does exactly what
I want - tested in debug mode). And I respect the jax-ws specification,
doesn't it? (My main concern is to respect that)
Fyi, I have no problem with the getApprovedTerms operation. So I would
avoid updating for the moment :).
Thanks again,
Benjamin
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 18:48
To: cxf-user@incubator.apache.org
Cc: Benjamin Coiffe
Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation]
problem
Honestly, I think this was a bug in 2.0.1 that was fixed in 2.0.2
(or .3). I HIGHLY suggest you update to 2.0.3 and check again.
Actually, you could try the 2.0.4 release candidates that we are voting
on:
http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator/
OK. I dug into some code a bit and figured out the problem with the
method generated for the getApprovedTerms method.It's the
parameterOrder attribute. It's confusing the BARE code generator. If
you could remove that, it should generate a proper (and usable) method.
I attached an updated wsdl that actually will work with wsdl2java to
generate a usable, completely BARE style client.
That all said, I just realized that you are using the Dynamic client.
That's JAXB only and doesn't really deal with the jaxws extensions at
all to figure out if it should be bare or wrapped. :-( In that
case, I DEFINITELY recommend checking out 2.0.4. The Client object in
2.0.4 has new invokeWrapped methods that can be used to ALWAYS use the
wrapper objects even if the normal code generators would have unwrapped
it.
Like:
VerifyTerm vt = new VerifyTerm();
vt.set.();
VerifyTermResponse vtr = client.invokeWrapped("verifyTerm", vt);
Dan
On Thursday 24 January 2008, Benjamin Coiffe wrote:
> Does not sound to bad...I guess the customization
> jaxws:enableWrapperStyle would be in an XML file somewhere in the cxf
> JAR.
> My final purpose here is to get this soap message:
>
> (Generated in SOAP UI)
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sii="http://sii.gri.roche.com";>
>
>
>
> random
> yes
> j
> Narrower
>
>
>
>
> Instead of that:
>
> (Generated by CXF)
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sii="http://sii.gri.roche.com";>
>
>
> random
> yes
> j
> Narrower
>
>
>
> The reason behind this is that a Web Service deployed on Web Logic
> replied me a weird error message (Hello.... ) when I send
> the cxf message and not the soapui one.
> Thanks,
>
> Benjamin
>
> -Original Message-
> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> Sent: 24 January 2008 17:43
> To: Benjamin Coiffe
> Cc: cxf-user@incubator.apache.org
> Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation]
> problem
>
>
> Ben,
>
> This won't do what you think. The DEFAULT is to enable wrapper
> style.
>
> The customization you are referring two will allow all operations to
> be generated in the "bare" style. In your case, the verifyTerm would
> be changed to match the other item:
> VerifyTermResponse verifyTerm(VerifyTermRequest req);
>
> If the schema does not match the rules in 2.3.1.2, there is nothing
> that
>
> can be done to get it unwrapped.
>
> Dan
>
> On Thursday 24 January 2008, Benjamin Coiffe wrote:
> > Ok, thanks, I found it. An I found this as well:
> >
> > Conformance (Disabling wrapper style): An implementation MUST
> > support use of the jaxws:enable-
> > WrapperStyle binding declaration to enable or disable the wrapper
> > style mapping of operations (see section
> > 8.7.3).
> >
> > How can I get this working for the dynamic client?
> >
> > Thanks,
> >
> > Ben
> >
> >
> > -Original Message-
> > From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> > Sent: 24 January 2008 17:05
> > To: cxf-user@incubator.apache.org
> > Cc: Benjamin Coiffe
> > Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped
> > operation] problem
> >
> >
> > It's the JAX-WS spec (which our tools implement) found at:
> >
> > http://jcp.org/en/jsr/detai
WebLogic, AquaLogic and CXF
Hi, I would like to know if any of you had a successful integration between these technologies. Basically, calling CXF Web Services from an EBA platform and calling EBA web Services from CXF? Any answer (link to a blog, anything) appreciated, Thanks Benjamin Coiffe
RE: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Does not sound to bad...I guess the customization jaxws:enableWrapperStyle would be in an XML file somewhere in the cxf JAR. My final purpose here is to get this soap message: (Generated in SOAP UI) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower Instead of that: (Generated by CXF) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sii="http://sii.gri.roche.com";> random yes j Narrower The reason behind this is that a Web Service deployed on Web Logic replied me a weird error message (Hello ) when I send the cxf message and not the soapui one. Thanks, Benjamin -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: 24 January 2008 17:43 To: Benjamin Coiffe Cc: cxf-user@incubator.apache.org Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem Ben, This won't do what you think. The DEFAULT is to enable wrapper style. The customization you are referring two will allow all operations to be generated in the "bare" style. In your case, the verifyTerm would be changed to match the other item: VerifyTermResponse verifyTerm(VerifyTermRequest req); If the schema does not match the rules in 2.3.1.2, there is nothing that can be done to get it unwrapped. Dan On Thursday 24 January 2008, Benjamin Coiffe wrote: > Ok, thanks, I found it. An I found this as well: > > Conformance (Disabling wrapper style): An implementation MUST support > use of the jaxws:enable- > WrapperStyle binding declaration to enable or disable the wrapper > style mapping of operations (see section > 8.7.3). > > How can I get this working for the dynamic client? > > Thanks, > > Ben > > > -Original Message- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: 24 January 2008 17:05 > To: cxf-user@incubator.apache.org > Cc: Benjamin Coiffe > Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation] > problem > > > It's the JAX-WS spec (which our tools implement) found at: > > http://jcp.org/en/jsr/detail?id=224 > > Specifically, it's section 2.3.1.2. The first table in there, item 5 > says: > (v) The wrapper elements only contain child elements, they must not > contain other structures such as wildcards (element or attribute), > xsd:choice, substitution groups (element references are not permitted) > or attributes; furthermore, they must not be nillable. > > > Dan > > On Thursday 24 January 2008, Benjamin Coiffe wrote: > > Do you have the link to the document you are quoting? > > I am reading the Basic Profile > > (http://www.ws-i.org/Profiles/BasicProfile-1_2(WGAD).html) and can't > > really find what you are mentioning. > > > > Thanks, Ben > > > > -Original Message- > > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > > Sent: 24 January 2008 16:09 > > To: cxf-user@incubator.apache.org > > Cc: Benjamin Coiffe > > Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped > > operation] problem > > > > > > According to the JAXWS spec, wrapper types are NOT allowed to > > contain wildcards.The xs:any is considered a wildcard. Thus, > > it's not unwrappable. > > > > That said, wsld2java is still broken for this case as it's > > generating a void return instead of a GetApprovedTermsResponse > > return . That's really not good. Off to log a bug for that. > > > > Dan > > > > On Thursday 24 January 2008, Benjamin Coiffe wrote: > > > Hi, > > > > > > > > > > > > The WSDL pasted at the end of this email contains two methods: > > > getApprovedTerms, verifyTerm. There signatures are very close, > > > yet, verifyItem is wrappable and getApprovedTerms isn't...Can > > > somebody please explain me why? > > > > > > I am working with CXF 2.0.1 patched. I did update > > > TypeClassSerializer to fix a couple of bugs. > > > > > > When I execute this code: > > > > > > > > > > > > DynamicClientFactory dynamicClientFactory = > > > DynamicClientFactory.newInstance(bus); > > > > > > Client client = dynamicClientFactory.createClient(wsdl); > > > > > > ServiceInfo model = > > > client.getEndpoint().getService().getServiceInfos().get(0); > > > > > > InterfaceInfo interfaceInfo = model.getInterface(); > > > > > > Co
RE: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Ok, thanks, I found it. An I found this as well:
Conformance (Disabling wrapper style): An implementation MUST support
use of the jaxws:enable-
WrapperStyle binding declaration to enable or disable the wrapper style
mapping of operations (see section
8.7.3).
How can I get this working for the dynamic client?
Thanks,
Ben
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 17:05
To: cxf-user@incubator.apache.org
Cc: Benjamin Coiffe
Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation]
problem
It's the JAX-WS spec (which our tools implement) found at:
http://jcp.org/en/jsr/detail?id=224
Specifically, it's section 2.3.1.2. The first table in there, item 5
says:
(v) The wrapper elements only contain child elements, they must not
contain other structures such as wildcards (element or attribute),
xsd:choice, substitution groups (element references are not permitted)
or attributes; furthermore, they must not be nillable.
Dan
On Thursday 24 January 2008, Benjamin Coiffe wrote:
> Do you have the link to the document you are quoting?
> I am reading the Basic Profile
> (http://www.ws-i.org/Profiles/BasicProfile-1_2(WGAD).html) and can't
> really find what you are mentioning.
>
> Thanks, Ben
>
> -Original Message-
> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> Sent: 24 January 2008 16:09
> To: cxf-user@incubator.apache.org
> Cc: Benjamin Coiffe
> Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation]
> problem
>
>
> According to the JAXWS spec, wrapper types are NOT allowed to contain
> wildcards.The xs:any is considered a wildcard. Thus, it's not
> unwrappable.
>
> That said, wsld2java is still broken for this case as it's generating
> a void return instead of a GetApprovedTermsResponse return . That's
> really not good. Off to log a bug for that.
>
> Dan
>
> On Thursday 24 January 2008, Benjamin Coiffe wrote:
> > Hi,
> >
> >
> >
> > The WSDL pasted at the end of this email contains two methods:
> > getApprovedTerms, verifyTerm. There signatures are very close, yet,
> > verifyItem is wrappable and getApprovedTerms isn't...Can somebody
> > please explain me why?
> >
> > I am working with CXF 2.0.1 patched. I did update
> > TypeClassSerializer to fix a couple of bugs.
> >
> > When I execute this code:
> >
> >
> >
> > DynamicClientFactory dynamicClientFactory =
> > DynamicClientFactory.newInstance(bus);
> >
> > Client client = dynamicClientFactory.createClient(wsdl);
> >
> > ServiceInfo model =
> > client.getEndpoint().getService().getServiceInfos().get(0);
> >
> > InterfaceInfo interfaceInfo = model.getInterface();
> >
> > Collection operationInfos =
> > interfaceInfo.getOperations();
> >
> > for(OperationInfo operationInfo:operationInfos){
> >
> > MessageInfo outputMessageInfo =
> > operationInfo.getInput();
> >
> > Map map =
> > outputMessageInfo.getMessagePartsMap();
> >
> > for(Entry entry :
> > map.entrySet()){
> >
> > MessagePartInfo messagePartInfo =
> > entry.getValue();
> >
> > if(messagePartInfo.getTypeClass() == null){
> >
> > throw new Exception("Should not happened!!")
> >
> > }
> >
> > }
> >
> > }
> >
> > }
> >
> >
> >
> > The Exception is unfortunately thrown:-( and should not be. I tried
> > to find a way to fix it myself but I am running out of ideas!
> >
> > My patched TypeClassInitializer is the latest code from the source
> > repository.
> >
> >
> >
> > Any Help would be really
RE: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Do you have the link to the document you are quoting?
I am reading the Basic Profile
(http://www.ws-i.org/Profiles/BasicProfile-1_2(WGAD).html) and can't
really find what you are mentioning.
Thanks, Ben
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 16:09
To: cxf-user@incubator.apache.org
Cc: Benjamin Coiffe
Subject: Re: [Dynamic Client, TypeClassInitializer, Wrapped operation]
problem
According to the JAXWS spec, wrapper types are NOT allowed to contain
wildcards.The xs:any is considered a wildcard. Thus, it's not
unwrappable.
That said, wsld2java is still broken for this case as it's generating a
void return instead of a GetApprovedTermsResponse return . That's
really not good. Off to log a bug for that.
Dan
On Thursday 24 January 2008, Benjamin Coiffe wrote:
> Hi,
>
>
>
> The WSDL pasted at the end of this email contains two methods:
> getApprovedTerms, verifyTerm. There signatures are very close, yet,
> verifyItem is wrappable and getApprovedTerms isn't...Can somebody
> please explain me why?
>
> I am working with CXF 2.0.1 patched. I did update TypeClassSerializer
> to fix a couple of bugs.
>
> When I execute this code:
>
>
>
> DynamicClientFactory dynamicClientFactory =
> DynamicClientFactory.newInstance(bus);
>
> Client client = dynamicClientFactory.createClient(wsdl);
>
> ServiceInfo model =
> client.getEndpoint().getService().getServiceInfos().get(0);
>
> InterfaceInfo interfaceInfo = model.getInterface();
>
> Collection operationInfos =
> interfaceInfo.getOperations();
>
> for(OperationInfo operationInfo:operationInfos){
>
> MessageInfo outputMessageInfo = operationInfo.getInput();
>
> Map map =
> outputMessageInfo.getMessagePartsMap();
>
> for(Entry entry : map.entrySet()){
>
> MessagePartInfo messagePartInfo = entry.getValue();
>
> if(messagePartInfo.getTypeClass() == null){
>
> throw new Exception("Should not happened!!")
>
> }
>
> }
>
> }
>
> }
>
>
>
> The Exception is unfortunately thrown:-( and should not be. I tried to
> find a way to fix it myself but I am running out of ideas!
>
> My patched TypeClassInitializer is the latest code from the source
> repository.
>
>
>
> Any Help would be really appreciated.
>
> Thanks,
>
>
>
> BEnjamin
>
>
>
>
>
>
>
> targetNamespace="http://sii.gri.roche.com";
> xmlns="http://schemas.xmlsoap.org/wsdl/";
> xmlns:s0="http://sii.gri.roche.com";
> xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";>
>
>
>
> elementFormDefault="qualified"
> targetNamespace="http://sii.gri.roche.com";
> xmlns:s0="http://sii.gri.roche.com";
> xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://localhost:9000"/>
>
>
>
>
>
>
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
FW: [Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Fyi, it fails to find the class for
{http://sii.gri.roche.com}:verifyTerm although it was generated. I
believe the bug here is that the operation is not Wrappable but can
somebody confirm?
Thanks
-Original Message-
From: Benjamin Coiffe [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 15:36
To: cxf-user@incubator.apache.org
Subject: [Dynamic Client, TypeClassInitializer, Wrapped operation]
problem
Hi,
The WSDL pasted at the end of this email contains two methods:
getApprovedTerms, verifyTerm. There signatures are very close, yet,
verifyItem is wrappable and getApprovedTerms isn't...Can somebody please
explain me why?
I am working with CXF 2.0.1 patched. I did update TypeClassSerializer to
fix a couple of bugs.
When I execute this code:
DynamicClientFactory dynamicClientFactory =
DynamicClientFactory.newInstance(bus);
Client client = dynamicClientFactory.createClient(wsdl);
ServiceInfo model =
client.getEndpoint().getService().getServiceInfos().get(0);
InterfaceInfo interfaceInfo = model.getInterface();
Collection operationInfos =
interfaceInfo.getOperations();
for(OperationInfo operationInfo:operationInfos){
MessageInfo outputMessageInfo = operationInfo.getInput();
Map map =
outputMessageInfo.getMessagePartsMap();
for(Entry entry : map.entrySet()){
MessagePartInfo messagePartInfo = entry.getValue();
if(messagePartInfo.getTypeClass() == null){
throw new Exception("Should not happened!!")
}
}
}
}
The Exception is unfortunately thrown:-( and should not be. I tried to
find a way to fix it myself but I am running out of ideas!
My patched TypeClassInitializer is the latest code from the source
repository.
Any Help would be really appreciated.
Thanks,
BEnjamin
http://sii.gri.roche.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:s0="http://sii.gri.roche.com";
xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";>
http://sii.gri.roche.com";
xmlns:s0="http://sii.gri.roche.com";
xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:9000"/>
[Dynamic Client, TypeClassInitializer, Wrapped operation] problem
Hi,
The WSDL pasted at the end of this email contains two methods:
getApprovedTerms, verifyTerm. There signatures are very close, yet,
verifyItem is wrappable and getApprovedTerms isn't...Can somebody please
explain me why?
I am working with CXF 2.0.1 patched. I did update TypeClassSerializer to
fix a couple of bugs.
When I execute this code:
DynamicClientFactory dynamicClientFactory =
DynamicClientFactory.newInstance(bus);
Client client = dynamicClientFactory.createClient(wsdl);
ServiceInfo model =
client.getEndpoint().getService().getServiceInfos().get(0);
InterfaceInfo interfaceInfo = model.getInterface();
Collection operationInfos =
interfaceInfo.getOperations();
for(OperationInfo operationInfo:operationInfos){
MessageInfo outputMessageInfo = operationInfo.getInput();
Map map =
outputMessageInfo.getMessagePartsMap();
for(Entry entry : map.entrySet()){
MessagePartInfo messagePartInfo = entry.getValue();
if(messagePartInfo.getTypeClass() == null){
throw new Exception("Should not happened!!")
}
}
}
}
The Exception is unfortunately thrown:-( and should not be. I tried to
find a way to fix it myself but I am running out of ideas!
My patched TypeClassInitializer is the latest code from the source
repository.
Any Help would be really appreciated.
Thanks,
BEnjamin
http://sii.gri.roche.com";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:s0="http://sii.gri.roche.com";
xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";>
http://sii.gri.roche.com";
xmlns:s0="http://sii.gri.roche.com";
xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:9000"/>
JMS and CXF: I want a ws method to handle only one message at a time
I use CXF-ApacheMQ to deploy different Web Service with a JMS binding. One of these WS has a one way method that should only de-queue and handle one message at a time (from the JMS queue)...In short, a JMS-consumer that is processing a message (for this one way method) should be unavailable until the end of the execution. I can't reproduce this behaviour in my environment. Is there a way to configure this? Any ideas? Benjamin Coiffe
JMS Topic and CXF
Hi, I was wondering if it is possible to open a JMS topic or queue using CXF. I know from the mailing-list and the doc that it is possible to send messages to a topic and a queue but I could not find anything to answer my question... If the answer is no, has anybody ever tried a lightweight and low latency JMS provider that is not a j2ee server?? Thanks, Benjamin
RE: dynamic client fails to create service
It got removed. It is at the end of the email. Thanks > Hi, > > The Dymamic client factory fails to create a client for the WSDL I have > attached to this email. > It is because of the complex type and the reference to a schema: > > > > > > name="GetMaterialDataResult"> > > > > > > > > > > > > Although I am disappointed that it does not work, I an really wondering how > the mapping rom this to JAVA could be done. Does the experts have any idea? > For this wsdl to get compiled by the DynamicClientFactory, I change the > previous type to: > > > > > name="GetMaterialDataResult" type="anyType"/> > > > > > And I did not change the implementation of the web service. What do you > guys think? > > Benjamin > http://schemas.xmlsoap.org/wsdl/http/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tns="http://BioSample.Roche.com/BioSampleWebServices/BioSampleWs"; xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; targetNamespace="http://BioSample.Roche.com/BioSampleWebServices/BioSamp leWs" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> http://BioSample.Roche.com/BioSampleWebServices/BioSamp leWs"> http://www.w3.org/2001/XMLSchema"; /> http://schemas.xmlsoap.org/soap/http"; style="document" /> http://BioSample.Roche.com/BioSampleWebServices/BioSampleWs/ GetMaterialData" style="document" /> http://rnumsriggap47/BioSampleWebServices/BioSampleWs.asmx"; />
FW: dynamic client fails to create service
I forgot to attach the wsdl... > Hi, > > The Dymamic client factory fails to create a client for the WSDL I have > attached to this email. > It is because of the complex type and the reference to a schema: > > > > > > name="GetMaterialDataResult"> > > > > > > > > > > > > Although I am disappointed that it does not work, I an really wondering how > the mapping rom this to JAVA could be done. Does the experts have any idea? > For this wsdl to get compiled by the DynamicClientFactory, I change the > previous type to: > > > > > name="GetMaterialDataResult" type="anyType"/> > > > > > And I did not change the implementation of the web service. What do you > guys think? > > Benjamin > > > >
RE: dynamic client fails to create service
Benjamin Coiffe, Software Engineer InforSense Ltd. Colet Court 100 Hammersmith Road London W6 7JP Email: [EMAIL PROTECTED] Skype: benjamin.inforsense -Original Message- From: tog [mailto:[EMAIL PROTECTED] Sent: Sun 12/9/2007 8:58 AM To: cxf-user@incubator.apache.org Subject: Re: dynamic client fails to create service Hi Benjamin, Would help if you can send the wsdl ;-) Cheers Guillaume On Dec 9, 2007 1:42 PM, Benjamin Coiffe <[EMAIL PROTECTED]> wrote: > > > > Hi, > > The Dymamic client factory fails to create a client for the WSDL I have > attached to this email. > It is because of the complex type and the reference to a schema: > > > > > > name="GetMaterialDataResult"> > > > > > > > > > > > > Although I am disappointed that it does not work, I an really wondering how > the mapping rom this to JAVA could be done. Does the experts have any idea? > For this wsdl to get compiled by the DynamicClientFactory, I change the > previous type to: > > > > > name="GetMaterialDataResult" type="anyType"/> > > > > > And I did not change the implementation of the web service. What do you > guys think? > > Benjamin > > > > -- Best Regards Guillaume http://cheztog.blogspot.com
dynamic client fails to create service
Hi, The Dymamic client factory fails to create a client for the WSDL I have attached to this email. It is because of the complex type and the reference to a schema: Although I am disappointed that it does not work, I an really wondering how the mapping rom this to JAVA could be done. Does the experts have any idea? For this wsdl to get compiled by the DynamicClientFactory, I change the previous type to: And I did not change the implementation of the web service. What do you guys think? Benjamin
Problem with data binding (XJC)
Hi,
I have problems trying to use the Dynamic Client for the web service:
http://www.ncbi.nlm.nih.gov/entrez/eutils/soap/efetch.wsdl.
It throws an exception that I copy-paste at the end of this email. I am
using cxf 2.0.1.
Is that something that could be fixed in future releases of XJC or that
could be already fixed in the next 2.0.3?
Thanks,
Benjamin
Caused by: java.lang.Exception: Error compiling schema from WSDL at
{http://www.ncbi.nlm.nih.gov/entrez/eutils/soap/efetch.wsdl}: Property
"Value" is already defined.
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory$InnerErrorListener.
error(DynamicClientFactory.java:409)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerIm
pl.java:245)
at
com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.jav
a:61)
at
com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.jav
a:61)
at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:66)
at
com.sun.tools.xjc.reader.ModelChecker.checkPropertyCollision(ModelChecke
r.java:57)
at
com.sun.tools.xjc.reader.ModelChecker.check(ModelChecker.java:43)
at
com.sun.tools.xjc.reader.ModelChecker.check(ModelChecker.java:27)
at
com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:145
)
at
com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:77)
at
com.sun.tools.xjc.ModelLoader.annotateXMLSchema(ModelLoader.java:388)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
l.java:206)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
l.java:66)
RE: Terra service
Guillaume It could be this: CXF-1168. It has been fixed recently. And the stacktrace below is probably similar to what you have: 7 ERROR [STDERR] org.apache.cxf.service.factory.ServiceConstructionException 12:04:26,837 ERROR [STDERR] at org.apache.cxf.endpoint.dynamic.TypeClassInitializer.begin(TypeClassInit ializer.java:93) 12:04:26,837 ERROR [STDERR] at org.apache.cxf.service.ServiceModelVisitor.visitOperation(ServiceModelVi sitor.java:62) 12:04:26,837 ERROR [STDERR] at org.apache.cxf.service.ServiceModelVisitor.walk(ServiceModelVisitor.java :48) 12:04:26,837 ERROR [STDERR] at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:249) 12:04:26,837 ERROR [STDERR] at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:145) 12:04:26,837 ERROR [STDERR] at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:124) I hope it helps Benjamin -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: 12 November 2007 21:05 To: cxf-user@incubator.apache.org Cc: tog Subject: Re: Terra service Guillaume, On Sunday 11 November 2007, tog wrote: > I have problem with the terra service using the dynamic client > (http://terraservice.net/TerraService.asmx?WSDL) > It is looking for a byte[] type which obviously does not exist ? > > Any thought ? At what point is it having a issue? At client creation or during method invoke? If method invoke, which operation? I tried with CXF 2.0.3 and it seemed to generate the client fine. However, I didn't know what operation to try or what params to send or anything like that. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Dynamic client bug
Hi, I think I found a bug in the Dynamic Client Factory. For the Web Service: http://www.ncbi.nlm.nih.gov/entrez/eutils/soap/eutils_lite.wsdl, it fails to build the JAXB context and throws the following exception: Caused by: java.lang.Exception: Unable to create JAXBContext for generated packages: "java.lang" doesnt contain ObjectFactory.class or jaxb.index at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:235) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:145) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami cClientFactory.java:124) at com.inforsense.webservicestudio.server.cache.ClientFactory.getClient(Cli entFactory.java:85) at com.inforsense.webservicestudio.server.HttpCxfImpl.getOperations(HttpCxf Impl.java:47) ... 27 more The Package list contains the following packages: java.lang:gov.nih.nlm.ncbi.soap.eutils.esummary:gov.nih.nlm.ncbi.soap.eu tils.esearch:java.io:gov.nih.nlm.ncbi.soap.eutils.egquery:gov.nih.nlm.nc bi.soap.eutils.espell:gov.nih.nlm.ncbi.soap.eutils.einfo:generated:gov.n ih.nlm.ncbi.soap.eutils.elink It fails because of java.lang, java.io, and generated. I am using cxf 2.0.1. I was looking for a similar bug in JIRA but could not find one. I would be grateful if someone finds one and can send the ID. Thanks, Benjamin Coiffe
RE: question about http://schemas.xmlsoap.org/soap/encoding/ and Dynamic Client
Thanks for the answer James,
Unfortunately, I don't think that it would help because the exception is
thrown when the wsdl is parsed (using XJC I believe)...
Any other suggestions?
Thanks,
Benjamin
-Original Message-
From: James Mao [mailto:[EMAIL PROTECTED]
Sent: 12 November 2007 02:38
To: cxf-user@incubator.apache.org
Subject: Re: question about http://schemas.xmlsoap.org/soap/encoding/
and Dynamic Client
We don't support rpc/encoded in CXF, but there's a work around
http://www.jroller.com/gmazza/entry/national_weather_service_forecasting
_web
Hope this helps
James
> Hi all,
>
>
>
> I noticed that the dynamic client can not handle objects of type
> belonging to http://schemas.xmlsoap.org/soap/encoding/. (at least the
> arrayType). For example, whenever I try to use the Dynamic Client with
> this http://soap.genome.jp/KEGG.wsdl , I get the following Exception.
>
> I haven't found so far any comments about this either on the wiki, in
> Jira, road maps...
>
> I am really looking for information about this and especially for a
> workaround (how far could I tweak the wsdl?).
>
> Any help appreciated!
>
>
>
> Benjamin
>
>
>
> java.lang.Exception: Error compiling schema from WSDL at
> {http://soap.genome.jp/KEGG.wsdl}: undefined simple or complex type
> 'soapenc:Array'
>
> at
>
org.apache.cxf.endpoint.dynamic.DynamicClientFactory$InnerErrorListener.
> error(DynamicClientFactory.java:409)
>
> at
>
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerIm
> pl.java:245)
>
> at
>
com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.jav
> a:61)
>
> at
>
com.sun.xml.xsom.impl.parser.ParserContext$2.error(ParserContext.java:18
> 8)
>
> at
>
com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.j
> ava:166)
>
> at
>
com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(NGCCRuntimeEx.jav
> a:103)
>
> at
> com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java:91)
>
> at
com.sun.xml.xsom.impl.parser.DelayedRef.run(DelayedRef.java:66)
>
> at
>
com.sun.xml.xsom.impl.parser.ParserContext.getResult(ParserContext.java:
> 126)
>
> at
> com.sun.xml.xsom.parser.XSOMParser.getResult(XSOMParser.java:172)
>
> at
com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:488)
>
> at
>
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
> l.java:197)
>
> at
>
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
> l.java:66)
>
> at
>
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
> cClientFactory.java:166)
>
> at
>
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
> cClientFactory.java:145)
>
> at
>
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
> cClientFactory.java:124)
>
> at
>
com.inforsense.webservicestudio.server.cache.ClientFactory.getClient(Cli
> entFactory.java:85)
>
> at
>
com.inforsense.webservicestudio.server.HttpCxfImpl.getOperations(HttpCxf
> Impl.java:47)
>
> ... 27 more
>
>
>
>
>
>
>
question about http://schemas.xmlsoap.org/soap/encoding/ and Dynamic Client
Hi all,
I noticed that the dynamic client can not handle objects of type
belonging to http://schemas.xmlsoap.org/soap/encoding/. (at least the
arrayType). For example, whenever I try to use the Dynamic Client with
this http://soap.genome.jp/KEGG.wsdl , I get the following Exception.
I haven't found so far any comments about this either on the wiki, in
Jira, road maps...
I am really looking for information about this and especially for a
workaround (how far could I tweak the wsdl?).
Any help appreciated!
Benjamin
java.lang.Exception: Error compiling schema from WSDL at
{http://soap.genome.jp/KEGG.wsdl}: undefined simple or complex type
'soapenc:Array'
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory$InnerErrorListener.
error(DynamicClientFactory.java:409)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerIm
pl.java:245)
at
com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.jav
a:61)
at
com.sun.xml.xsom.impl.parser.ParserContext$2.error(ParserContext.java:18
8)
at
com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.j
ava:166)
at
com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(NGCCRuntimeEx.jav
a:103)
at
com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java:91)
at com.sun.xml.xsom.impl.parser.DelayedRef.run(DelayedRef.java:66)
at
com.sun.xml.xsom.impl.parser.ParserContext.getResult(ParserContext.java:
126)
at
com.sun.xml.xsom.parser.XSOMParser.getResult(XSOMParser.java:172)
at com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:488)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
l.java:197)
at
com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImp
l.java:66)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
cClientFactory.java:166)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
cClientFactory.java:145)
at
org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami
cClientFactory.java:124)
at
com.inforsense.webservicestudio.server.cache.ClientFactory.getClient(Cli
entFactory.java:85)
at
com.inforsense.webservicestudio.server.HttpCxfImpl.getOperations(HttpCxf
Impl.java:47)
... 27 more
RE: Return direct XML
Hi, I was trying to use Aegis Binding on the Dynamic client (DynamicClientFactory.createClient()) but it is hard coded to use JAXB. Is there a specific reason for this or could I confidently modify the source code of my distribution and expect it to run using Aegis bindings? Thanks, Ps: benson, the fix for CXF-1168 works for me in 2.0.1. Thx! -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 07 November 2007 02:38 To: cxf-user@incubator.apache.org Subject: RE: Return direct XML I believe that Aegis allows you to have a return type of org.w3c.Document or the JDOM equivalent, and XML will appear. > -Original Message- > From: Liu, Jervis [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 06, 2007 9:32 PM > To: cxf-user@incubator.apache.org > Subject: RE: Return direct XML > > In your case, looks like the easiest way is to use JAX-WS Provider API > with XML Binding. You will find a bunch of different type of Provider > implementations under system test: > https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/test/j av > a/org/apache/cxf/systest/provider/. Of course the limitation is that the > input of your function has to be in XML format as well (can be > Source/SOAPMessage/DataSource, depend on your mode and binding), in some > cases you may find its hard to parse input from XML by yourself. > > Cheers, > Jervis > > > -Original Message- > > From: Roshan A. Punnoose [mailto:[EMAIL PROTECTED] > > Sent: 2007?11?7? 4:08 > > To: cxf-user@incubator.apache.org > > Subject: Return direct XML > > > > > > Hi, > > > > > > > > What is the easiest way to return XML directly? For example, in my > > function, if I create XML, I want to be able to send that object > > directly back to the calling client. Is this possible? > > > > > > > > Roshan > > > > > > > IONA Technologies PLC (registered in Ireland) > Registered Number: 171387 > Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
RE: Dynamic Client byte[]
Thanks, If you tell me which file I need to check out, I could path my CXF 2.0.2 and give it a go. Don't bother if that sounds painful. Thanks anyway. Ben -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 02 November 2007 13:33 To: cxf-user@incubator.apache.org Subject: RE: Dynamic Client byte[] I committed the fix to the trunk. I can't offer a workaround, unfortunately, but perhaps someone else will. > -Original Message- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Friday, November 02, 2007 9:26 AM > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > You have found a bug. I'm just trying to figure out if there are > interesting variations on the bug that I shold worry about. > > > -Original Message- > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 02, 2007 9:09 AM > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > Hum, sorry but I'm not following. > > > > Yet, I have tried using the dynamic client with xxx[][] where xxx is a > > primitive type and it worked well. The factory creates an > xxxArrayArray > > object that contains a list of xxxArray that contains a list of xxx. > The > > whole thing is right and works well. This only works in RPC/literal. > > > > When the wsdl is a Document/literal, it is completely wrong...but I > have > > read somewhere that it is not yet supported in CXF. The unwrapped > > operation contains only the primitive type: xxx instead of xxxArray or > > anything else. > > > > Ben > > > > > > -Original Message- > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > Sent: 02 November 2007 12:56 > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > I'm coding your fix. Can you think of a WSDL construct that would > amount > > to foo[][]? > > > > > -Original Message- > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > Sent: Friday, November 02, 2007 8:39 AM > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > My cxf version is 2.0.1. I will give it a go later today with 2.0.2. > > > > > > -Original Message- > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > Sent: 02 November 2007 12:31 > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > Hmm, I see. My test runs aground because I don't have enough > > > infrastructure where I put it. > > > > > > > -Original Message- > > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, November 02, 2007 8:28 AM > > > > To: cxf-user@incubator.apache.org > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > I set up a test case with the current development trunk, and it > > fails > > > > for lack of an endpoint, not for your reason. I should have > started > > by > > > > asking: what version of CXF have you got there? > > > > > > > > > -Original Message- > > > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > > > Sent: Friday, November 02, 2007 8:24 AM > > > > > To: cxf-user@incubator.apache.org > > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > > > You are right. See by yourself: > > > > > > > > > > CXFBusFactory busFactory = new CXFBusFactory(); > > > > > Bus bus = busFactory.createBus(); > > > > > DynamicClientFactory dynamicClientFactory = > > > > > DynamicClientFactory.newInstance(bus); > > > > > Client client = dynamicClientFactory.createClient(wsdl); > > > > > > > > > > Thanks, > > > > > > > > > > Ben > > > > > -Original Message- > > > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > > > Sent: 02 November 2007 12:11 > > > > > To: cxf-user@incubator.apache.org > > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > > > Are you sure you mean DynamicClient.create and not > > > > > DynamicClientFactory.create? > > > > > > > > > > > -Original Message- > > > > > > From: Benjamin Coiffe [mailto:[
RE: Dynamic Client byte[]
Hum, sorry but I'm not following. Yet, I have tried using the dynamic client with xxx[][] where xxx is a primitive type and it worked well. The factory creates an xxxArrayArray object that contains a list of xxxArray that contains a list of xxx. The whole thing is right and works well. This only works in RPC/literal. When the wsdl is a Document/literal, it is completely wrong...but I have read somewhere that it is not yet supported in CXF. The unwrapped operation contains only the primitive type: xxx instead of xxxArray or anything else. Ben -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 02 November 2007 12:56 To: cxf-user@incubator.apache.org Subject: RE: Dynamic Client byte[] I'm coding your fix. Can you think of a WSDL construct that would amount to foo[][]? > -Original Message- > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > Sent: Friday, November 02, 2007 8:39 AM > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > My cxf version is 2.0.1. I will give it a go later today with 2.0.2. > > -Original Message- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: 02 November 2007 12:31 > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > Hmm, I see. My test runs aground because I don't have enough > infrastructure where I put it. > > > -Original Message- > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 02, 2007 8:28 AM > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > I set up a test case with the current development trunk, and it fails > > for lack of an endpoint, not for your reason. I should have started by > > asking: what version of CXF have you got there? > > > > > -Original Message- > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > Sent: Friday, November 02, 2007 8:24 AM > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > You are right. See by yourself: > > > > > > CXFBusFactory busFactory = new CXFBusFactory(); > > > Bus bus = busFactory.createBus(); > > > DynamicClientFactory dynamicClientFactory = > > > DynamicClientFactory.newInstance(bus); > > > Client client = dynamicClientFactory.createClient(wsdl); > > > > > > Thanks, > > > > > > Ben > > > -Original Message- > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > Sent: 02 November 2007 12:11 > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > Are you sure you mean DynamicClient.create and not > > > DynamicClientFactory.create? > > > > > > > -Original Message- > > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, November 02, 2007 8:08 AM > > > > To: cxf-user@incubator.apache.org > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > Sorry I forgot the wsdl and stacktrace in my previous email. > > > > I appended them both in this email. > > > > > > > > Thanks, > > > > > > > > Benjamin > > > > > > > > > > > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > xmlns:ns1="http://rpc.data.webservicestudio.inforsense.com/"; > > > > xmlns:ns2="http://schemas.xmlsoap.org/soap/http"; > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > name="DataTestService" > > > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/";> > > > > > > > > xmlns="http://rpc.data.webservicestudio.inforsense.com/"; > > > > attributeFormDefault="unqualified" elementFormDefault="qualified" > > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/"; > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > type="UnsupportedEncodingException"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
RE: Dynamic Client byte[]
Thank you -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 02 November 2007 12:45 To: cxf-user@incubator.apache.org Subject: RE: Dynamic Client byte[] CXF-1168 > -Original Message- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Friday, November 02, 2007 8:42 AM > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > I've got your failure reproed on the trunk. Don't Bother. JIRA to > follow, then debugging. > > > -----Original Message- > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 02, 2007 8:39 AM > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > My cxf version is 2.0.1. I will give it a go later today with 2.0.2. > > > > -Original Message- > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > Sent: 02 November 2007 12:31 > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > Hmm, I see. My test runs aground because I don't have enough > > infrastructure where I put it. > > > > > -Original Message- > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > Sent: Friday, November 02, 2007 8:28 AM > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > I set up a test case with the current development trunk, and it > fails > > > for lack of an endpoint, not for your reason. I should have started > by > > > asking: what version of CXF have you got there? > > > > > > > -Original Message- > > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, November 02, 2007 8:24 AM > > > > To: cxf-user@incubator.apache.org > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > You are right. See by yourself: > > > > > > > > CXFBusFactory busFactory = new CXFBusFactory(); > > > > Bus bus = busFactory.createBus(); > > > > DynamicClientFactory dynamicClientFactory = > > > > DynamicClientFactory.newInstance(bus); > > > > Client client = dynamicClientFactory.createClient(wsdl); > > > > > > > > Thanks, > > > > > > > > Ben > > > > -Original Message- > > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > > Sent: 02 November 2007 12:11 > > > > To: cxf-user@incubator.apache.org > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > Are you sure you mean DynamicClient.create and not > > > > DynamicClientFactory.create? > > > > > > > > > -Original Message- > > > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > > > Sent: Friday, November 02, 2007 8:08 AM > > > > > To: cxf-user@incubator.apache.org > > > > > Subject: RE: Dynamic Client byte[] > > > > > > > > > > Sorry I forgot the wsdl and stacktrace in my previous email. > > > > > I appended them both in this email. > > > > > > > > > > Thanks, > > > > > > > > > > Benjamin > > > > > > > > > > > > > > > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > > xmlns:ns1="http://rpc.data.webservicestudio.inforsense.com/"; > > > > > xmlns:ns2="http://schemas.xmlsoap.org/soap/http"; > > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > name="DataTestService" > > > > > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/";> > > > > > > > > > > > xmlns="http://rpc.data.webservicestudio.inforsense.com/"; > > > > > attributeFormDefault="unqualified" > elementFormDefault="qualified" > > > > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/"; > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > type="UnsupportedEncodingException"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > &g
RE: Dynamic Client byte[]
My cxf version is 2.0.1. I will give it a go later today with 2.0.2. -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 02 November 2007 12:31 To: cxf-user@incubator.apache.org Subject: RE: Dynamic Client byte[] Hmm, I see. My test runs aground because I don't have enough infrastructure where I put it. > -Original Message- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Friday, November 02, 2007 8:28 AM > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > I set up a test case with the current development trunk, and it fails > for lack of an endpoint, not for your reason. I should have started by > asking: what version of CXF have you got there? > > > -Original Message- > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 02, 2007 8:24 AM > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > You are right. See by yourself: > > > > CXFBusFactory busFactory = new CXFBusFactory(); > > Bus bus = busFactory.createBus(); > > DynamicClientFactory dynamicClientFactory = > > DynamicClientFactory.newInstance(bus); > > Client client = dynamicClientFactory.createClient(wsdl); > > > > Thanks, > > > > Ben > > -Original Message- > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > Sent: 02 November 2007 12:11 > > To: cxf-user@incubator.apache.org > > Subject: RE: Dynamic Client byte[] > > > > Are you sure you mean DynamicClient.create and not > > DynamicClientFactory.create? > > > > > -Original Message- > > > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > > > Sent: Friday, November 02, 2007 8:08 AM > > > To: cxf-user@incubator.apache.org > > > Subject: RE: Dynamic Client byte[] > > > > > > Sorry I forgot the wsdl and stacktrace in my previous email. > > > I appended them both in this email. > > > > > > Thanks, > > > > > > Benjamin > > > > > > > > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > xmlns:ns1="http://rpc.data.webservicestudio.inforsense.com/"; > > > xmlns:ns2="http://schemas.xmlsoap.org/soap/http"; > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="DataTestService" > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/";> > > > > > > http://rpc.data.webservicestudio.inforsense.com/"; > > > attributeFormDefault="unqualified" elementFormDefault="qualified" > > > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > type="UnsupportedEncodingException"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="fault"> > > > > > > > > > > > > > > > > > > > > >> > name="getStringResponse"> > > > > > >> > name="UnsupportedEncodingException"> > > > > > > > > > > > >> > type="ns1:TestService"> > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > namespace="http://rpc.data.webservicestudio.inforsense.com/"; > > > use="literal"/> > > > > > > > > > > > namespace="http://rpc.data.webservicestudio.inforsense.com/"; > > > use="literal"/> > > > > > > > > > > use="literal"/> > > > > > > > > > > > > > > > > > name="TestServiceImplPort"> > > > http://localhost:9004/data"/> > > > > > > > > > > > > > > > > > > > > > > > > 7 ERROR [STDERR] > > > org.apache.cxf.s
RE: Dynamic Client byte[]
You are right. See by yourself: CXFBusFactory busFactory = new CXFBusFactory(); Bus bus = busFactory.createBus(); DynamicClientFactory dynamicClientFactory = DynamicClientFactory.newInstance(bus); Client client = dynamicClientFactory.createClient(wsdl); Thanks, Ben -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 02 November 2007 12:11 To: cxf-user@incubator.apache.org Subject: RE: Dynamic Client byte[] Are you sure you mean DynamicClient.create and not DynamicClientFactory.create? > -Original Message- > From: Benjamin Coiffe [mailto:[EMAIL PROTECTED] > Sent: Friday, November 02, 2007 8:08 AM > To: cxf-user@incubator.apache.org > Subject: RE: Dynamic Client byte[] > > Sorry I forgot the wsdl and stacktrace in my previous email. > I appended them both in this email. > > Thanks, > > Benjamin > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:ns1="http://rpc.data.webservicestudio.inforsense.com/"; > xmlns:ns2="http://schemas.xmlsoap.org/soap/http"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="DataTestService" > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/";> > > http://rpc.data.webservicestudio.inforsense.com/"; > attributeFormDefault="unqualified" elementFormDefault="qualified" > targetNamespace="http://rpc.data.webservicestudio.inforsense.com/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > type="UnsupportedEncodingException"/> > > > > > > > > > > > > > > > > > > > > > > > > > >name="getStringResponse"> > >name="UnsupportedEncodingException"> > > > >type="ns1:TestService"> > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > namespace="http://rpc.data.webservicestudio.inforsense.com/"; > use="literal"/> > > > namespace="http://rpc.data.webservicestudio.inforsense.com/"; > use="literal"/> > > > > > > > > name="TestServiceImplPort"> > http://localhost:9004/data"/> > > > > > > > > 7 ERROR [STDERR] > org.apache.cxf.service.factory.ServiceConstructionException > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.endpoint.dynamic.TypeClassInitializer.begin(TypeClassInit > ializer.java:93) > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.service.ServiceModelVisitor.visitOperation(ServiceModelVi > sitor.java:62) > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.service.ServiceModelVisitor.walk(ServiceModelVisitor.java > :48) > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami > cClientFactory.java:249) > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami > cClientFactory.java:145) > 12:04:26,837 ERROR [STDERR] at > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynami > cClientFactory.java:124) > 12:04:26,837 ERROR [STDERR] at > com.inforsense.webservicestudio.server.cache.ClientFactory.getClient(Cli > entFactory.java:53) > 12:04:26,837 ERROR [STDERR] at > com.inforsense.webservicestudio.server.HttpCxfImpl.getOperations(HttpCxf > Impl.java:44) > 12:04:26,837 ERROR [STDERR] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 12:04:26,837 ERROR [STDERR] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > 12:04:26,837 ERROR [STDERR] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > 12:04:26,837 ERROR [STDERR] at > java.lang.reflect.Method.invoke(Method.java:585) > 12:04:26,837 ERROR [STDERR] at > com.inforsense.servlet.ServiceServlet.doPost(ServiceServlet.java:79) > 12:04:26,837 ERROR [STDERR] at > javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 12:04:26,837 ERROR [STDERR] at > javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > 12:04:26,837 ERROR [STDERR] at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:252) > 12:04:26,837 ERROR [STDERR] at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:173) > 12:04
RE: Dynamic Client byte[]
11Processor.process(Http11Processor.java:86
9)
12:04:26,852 ERROR [STDERR] at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
essConnection(Http11BaseProtocol.java:664)
12:04:26,852 ERROR [STDERR] at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)
12:04:26,852 ERROR [STDERR] at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorker
Thread.java:112)
12:04:26,852 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
12:04:26,852 ERROR [STDERR] Caused by: java.lang.ClassNotFoundException:
No ClassLoaders found for: byte[]
12:04:26,852 ERROR [STDERR] at
org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
12:04:26,852 ERROR [STDERR] at
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClass
Loader.java:511)
12:04:26,852 ERROR [STDERR] at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoad
er.java:405)
12:04:26,852 ERROR [STDERR] at
java.lang.ClassLoader.loadClass(ClassLoader.java:251)
12:04:26,852 ERROR [STDERR] at
org.java.plugin.PluginClassLoader.loadClass(PluginClassLoader.java:290)
12:04:26,852 ERROR [STDERR] at
java.lang.ClassLoader.loadClass(ClassLoader.java:251)
12:04:26,852 ERROR [STDERR] at
org.apache.cxf.common.classloader.ClassLoaderUtils.loadClass2(ClassLoade
rUtils.java:127)
12:04:26,852 ERROR [STDERR] at
org.apache.cxf.common.classloader.ClassLoaderUtils.loadClass(ClassLoader
Utils.java:116)
12:04:26,852 ERROR [STDERR] at
org.apache.cxf.endpoint.dynamic.TypeClassInitializer.begin(TypeClassInit
ializer.java:88)
12:04:26,852 ERROR [STDERR] ... 34 more
-Original Message-
From: Benjamin Coiffe [mailto:[EMAIL PROTECTED]
Sent: 02 November 2007 11:31
To: cxf-user@incubator.apache.org
Subject: Dynamic Client byte[]
Hi,
I am trying to create a Dynamic Client from a wsdl that contains an
operation returning a base64binary (byte[]). The method
DynamicClient.createClient("http://mywsdl";) throws a
ServiceConstructionException because it is trying to initialise in the
service model a "byte[]" and can't find it in the ClassLoader.
Did anybody come across this problem? I could not find anything related
in the mailing list or in jira although it seems to be a basic(?) issue?
Any help appreciated...
Ben
