users@cxf.apache.org Archives

RE: Race condition when using UriInfo to get baseUri value

2009-12-06T18:22:47Z

Hi Sadhana

Yes please, some more information/clarification would help.

Do 192.168.1.102 && localhost identify the same host in your particular
case ?

  
"We send a request to say host http://192.168.1.102:9000
and then send a ping request to say http://localhost:9000 where both
requests are going to the same host but different addresses"

I need  some more details please. Does gwy.ws.jaxrs.ElaborationProcessor
delegates to gwy.ws.jaxrs.UriInfoManager ? Are these 2 beans share the
same jaxrs:server endpoint ? Does gwy.ws.jaxrs.ElaborationProcessor
shows http://192.168.1.102:9000 with UriInfo.getBaseUri() but when it
delegates to   
gwy.ws.jaxrs.UriInfoManager it shows localhost ?

cheers, Sergey 

-----Original Message-----
From: Sadhana Jain [mailto:Sadhana.Jain@rovicorp.com] 
Sent: 05 December 2009 01:15
To: users@cxf.apache.org
Subject: Race condition when using UriInfo to get baseUri value

Hi,

We are using the UriInfo object to getBasrUri() and using UriBuilder to
build and create linked URIs for our rest based services.

However, we are seeing a strange race condition:

We send a request to say host http://192.168.1.102:9000
and then send a ping request to say http://localhost:9000 where both
requests are going to the same host but different addresses, the
UriInfo object returns the base uri of the second request instead of the
first one. So, it seems the UriInfo or message object is somehow
Being shared between threads.

Following is the log that shows the problem 9 I have hightlighted the
hostname and thread numbers.

[INFO ][17:05:02,258][::][v()][t(http-9000-2)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.jav
a:12
9) ]
---- elaboration map: {host=192.168.1.102:9000,
gateway-version=1.2.11-2,
reply=json, user-agent=curl/7.16.3 (powerpc-apple-darwin9.0)
libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3, Accept=*/*}
[INFO ][17:05:02,257][::][v()][t(http-9000-1)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.jav
a:12
9) ]
---- elaboration map: {host=localhost:9000, gateway-version=1.2.11-2,
reply=json, user-agent=curl/7.16.3 (powerpc-apple-darwin9.0)
libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3, Accept=*/*}
[DEBUG][17:05:02,258][::][v()][t(http-9000-2)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.jav
a:14
7) ]
---- request method: GET
[DEBUG][17:05:02,258][::][v()][t(http-9000-1)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.jav
a:14
7) ]
---- request method: GET
[DEBUG][17:05:02,259][::][v()][t(http-9000-2)]
[ gwy.ws.jaxrs.UriInfoManager.setUi(UriInfoManager.java:51) ]
---- setUi() beging UriInfo base URI: http://localhost:9000/domain
[DEBUG][17:05:02,259][::][v()][t(http-9000-1)]
[ gwy.ws.jaxrs.UriInfoManager.setUi(UriInfoManager.java:51) ]
---- setUi() beging UriInfo base URI: http://localhost:9000/domain

Any help is much appreciated.

Please let me know if I can supply more info.

Thanks,
Sadhana

multiple xjc args in extraargs for Maven cxf-codegen-plugin configuration

2009-12-05T19:35:37Z


After a bit of trial and error, I was able to apply multiple sets of xjc args
in respective extraargs.

This is handy when you need to specify multiple JAXB plugins and multiple
episodes for JAXB. Note that I still paired the related args with a
comma-delimiter in a single extraarg element (e.g.,
"-xjc-Xname,-Xname-classSubstitution=/$/Dto/")

I am including the entire Maven cxf-codegen-plugin XML with the extraargs
configuration here in case this is useful to anyone else.

-----------------------------------

    org.apache.cxf
    cxf-codegen-plugin
    ${cxf.version}
    
        
            org.cassee.xjc-plugins
            xjc-plugins-classname
            0.3
        
    
    
        
            generate-sources
            generate-sources
            
                true
               
${project.build.directory}/generated/cxf
                
                    
                       
${basedir}/src/main/wsdl/TrainTrackService.wsdl
                        
                            -xjc-verbose
                           
-xjc-b,${basedir}/src/main/wsdl/core-response.episode
                           
-xjc-Xname,-Xname-classSubstitution=/$/Dto/
                           
-xjc-episode,${project.build.outputDirectory}/train-track-service.episode
                        
                    
                
            
            
                wsdl2java
            
        
    

-----------------------------------
-- 
View this message in context: http://old.nabble.com/multiple-xjc-args-in-extraargs-for-Maven-cxf-codegen-plugin-configuration-tp26658501p26658501.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: AW: Problem with code generation and binding files

2009-12-05T18:02:08Z


I am on a project that is considering a switch to Apache CXF from Sun JAXWS.

For a while I have been following developments for CXF and have noted that
support for JAXB episode seems to be still in a formative stage. Is there a
document for the WSDL-to-Java Maven plugin for CXF that describes each
configuration parameter, especially how to pass arguments to JAXB for
episodes and/or JAXB plugins?

A helpful posting on what episodes are and how they are used can be found
here:

  

Thanks




dkulp wrote:
> 
> On Sun July 5 2009 7:53:46 pm johannes.konstantinidis@capgemini-sdm.com
> wrote:
>> Hello,
>>
>> does anybody have an idea?
>> My problem still exists.
> 
> As Benson stated, a JIRA with a reproducible test case would be great.  
> I've 
> heard of issues with episode files before as well, but I've never used an 
> episode file so I really don't know enough to dig in without some sort of 
> test. 
> 
> Dan
> 
> 
>>
>> Thanks
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Konstantinidis, Johannes
>> Gesendet: Dienstag, 23. Juni 2009 19:15
>> An: users@cxf.apache.org
>> Betreff: Problem with code generation and binding files
>>
>> Hello,
>>
>> I have a problem with the generation of the CXF classes when the JAXB
>> classes have been generated before via separate compilation with episode
>> files.
>>
>> I have a WSDL (service.wsdl) which imports a xml schema (service.xsd)
>> that
>> defines all types for service invocation. In addition I have a xml schema
>> with some basic types (common.xsd) which is imported by service.xsd.
>>
>> The whole generation takes place in one build within one project. No
>> compilation is performed between the different steps.
>>
>> At first I generate the JAXB classes for service.xsd and common.xsd with
>> the JAXB Maven Plugin (org.jvnet.jaxb2/maven2.maven-jaxb2-plugin). Now I
>> have the classes and the two episode files for them.
>>
>> Now I would like to generate the CXF classes with the Maven Plugin
>> (org.apache.cxf/ cxf-codegen-plugin).
>>
>> 
>>  src/main/resources/service.wsdl
>>  
>>    
>> ${project.build.directory}/generated-sources/xjc/common.episod
>>e
>> ${project.build.directory}/generated-sources/xjc/service.episo
>>de 
>>  
>>   -impl
>>   -server
>>   -validate
>>  
>> 
>>
>> That results in an error message: Failed to create java parameter for
>> part
>> [test] in method [test] It seems that the generator can not retrieve the
>> class name of test although it is specified within the corresponding
>> episode file. Btw, I tested the wsdl with the wsdlvalidator tool.
>>
>> When I try to specify some package names in addition to the binding files
>>
>>  
>>    
>> http://my.example.com/WSDLNamespace=my.example.com.ws
>> http://my.example.com/Service=my.example.com.ws.service
>> http://my.example.com/Common=my.example.com.ws.common
>> 
>>
>> I get an error
>> Thrown by JAXB : Multiple  are defined for the target
>> namespace http://my.example.com/Service at line 5 column 22 of schema  
>> temporary xsd file>
>>
>> What is my fault?
>> Btw: Is it possible not to delete the temporary xsd file just to get more
>> information about problem?
>>
>> Thanks for your help!
> 
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
> 
> 

-- 
View this message in context: http://old.nabble.com/Problem-with-code-generation-and-binding-files-tp24170728p26657819.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: CXF 2.2.5 not available in Maven central

2009-12-05T08:59:08Z


Thanks Daniel.

Yes I was using ibiblio:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/cxf/cxf-rt-core/

Are ibiblio having problems with repo1 ?

Now I know repo1 is OK, however Maven repo searches (mvnrepository.com) use
ibiblio, which is not uptodate now.

Anyway, it's not CXF's fault. Thanks Daniel.


dkulp wrote:
> 
> On Fri December 4 2009 1:40:29 pm Hendy Irawan wrote:
>> I just checked that the latest CXF available in Maven central is CXF
>> 2.2.4.
>> 
>> Is it planned to deploy CXF 2.2.5 to Maven central?
> 
> It has been deployed there.   I see it fine:
> 
> http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-core/2.2.5/
> 
> Are you using a mirror or something that hasn't been updated?
> -- 
> Daniel Kulp
> 

-- 
View this message in context: http://old.nabble.com/CXF-2.2.5-not-available-in-Maven-central-tp26636372p26653908.html
Sent from the cxf-user mailing list archive at Nabble.com.

Race condition when using UriInfo to get baseUri value

2009-12-05T01:14:55Z

Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi,

We are using the UriInfo object to getBasrUri() and using UriBuilder to
build and create linked URIs for our rest based services.

However, we are seeing a strange race condition:

We send a request to say host http://192.168.1.102:9000
and then send a ping request to say http://localhost:9000 where both
requests are going to the same host but different addresses, the
UriInfo object returns the base uri of the second request instead of the
first one. So, it seems the UriInfo or message object is somehow
Being shared between threads.

Following is the log that shows the problem 9 I have hightlighted the
hostname and thread numbers.

[INFO ][17:05:02,258][::][v()][t(http-9000-2)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.java:12
9) ]
---- elaboration map: {host=192.168.1.102:9000, gateway-version=1.2.11-2,
reply=json, user-agent=curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3, Accept=*/*}
[INFO ][17:05:02,257][::][v()][t(http-9000-1)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.java:12
9) ]
---- elaboration map: {host=localhost:9000, gateway-version=1.2.11-2,
reply=json, user-agent=curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3
OpenSSL/0.9.7l zlib/1.2.3, Accept=*/*}
[DEBUG][17:05:02,258][::][v()][t(http-9000-2)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.java:14
7) ]
---- request method: GET
[DEBUG][17:05:02,258][::][v()][t(http-9000-1)]
[ 
gwy.ws.jaxrs.ElaborationProcessor.handleRequest(ElaborationProcessor.java:14
7) ]
---- request method: GET
[DEBUG][17:05:02,259][::][v()][t(http-9000-2)]
[ gwy.ws.jaxrs.UriInfoManager.setUi(UriInfoManager.java:51) ]
---- setUi() beging UriInfo base URI: http://localhost:9000/domain
[DEBUG][17:05:02,259][::][v()][t(http-9000-1)]
[ gwy.ws.jaxrs.UriInfoManager.setUi(UriInfoManager.java:51) ]
---- setUi() beging UriInfo base URI: http://localhost:9000/domain

Any help is much appreciated.

Please let me know if I can supply more info.

Thanks,
Sadhana

Re: CXF 2.2.5 not available in Maven central

2009-12-04T18:45:21Z

On Fri December 4 2009 1:40:29 pm Hendy Irawan wrote:
> I just checked that the latest CXF available in Maven central is CXF 2.2.4.
> 
> Is it planned to deploy CXF 2.2.5 to Maven central?

It has been deployed there.   I see it fine:

http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-core/2.2.5/

Are you using a mirror or something that hasn't been updated?
-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Firewall-friendly connection establishment

2009-12-04T18:44:05Z


Wow.  Interesting case.   You're going to have to write a custom transport for 
this.     Normally, a custom transport isn't that hard.   A Conduit for the 
client side and a Destination for the server side.   However, in this case 
where the conduit becomes a destination and vice-versa might require a bit 
extra work under the covers to achieve.

Dan


On Fri December 4 2009 4:16:29 am Fromm, Stefan wrote:
> Hello,
> 
> I have the following scenario. A web service is running on the internet.
> My intranet server connects to this web service. After connection the
> web service is supposed to reuse the connection, become the client and
> send requests to the intranet server. This is firewall-friendly, because
> I do not have to open my intranet firewall to allow incoming requests.
> Instead I have to open the firewall for outgoing requests only. Once the
> connection is established, the web service could reuse it and send its
> requests. Using plain sockets it is simple to implement such a scenario.
> My question is, if this would also be possible with CXF? The underlying
> protocol can be HTTP(S) or TCP(S). I would need some hints where to
> start from reading documentation, because I am new to CXF.
> 
> Best regards
> Stefan Fromm
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

CXF 2.2.5 not available in Maven central

2009-12-04T18:40:29Z


I just checked that the latest CXF available in Maven central is CXF 2.2.4.

Is it planned to deploy CXF 2.2.5 to Maven central?
-- 
View this message in context: http://old.nabble.com/CXF-2.2.5-not-available-in-Maven-central-tp26636372p26636372.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: High memory usage with web service registration

2009-12-04T18:39:16Z


Actually, looking at the code, you may already be able to do this.   The 
JAXBDataBinding has a constructor of:

JAXBDataBinding(JAXBContext context)

Thus, via config or similar, you should be able to setup your own 
JAXBDataBinding object using a preconfigured JAXBContext.     Not sure how 
well tested that is though.

Dan



On Thu December 3 2009 11:33:52 pm Basavaraja U T wrote:
> Hi Dan,
> 
> XFire has provided a mechanism to re-use the JAXBContext across different
> web service publishing.
> 
> The Bug Id - XFIRE-669. (http://jira.codehaus.org/browse/XFIRE-669)
> 
> Seems it lets us to pass an existing JAXBContext to a JaxbServiceFactory.
> The context is then used by all layers from there. i.e. we can construct
>  one JAXBContext object with all the ObjectFactory.class'es from wsdl2java
>  tool generated java files and re-use the JAXBContext object for multiple
>  web service publishing.
> 
> It helps to reduce the memory usage if there is large no. of related web
> services (like MTOSI solution, which has around 30-40 interfaces) are
> published by an application.
> 
> It would be great if such a mechanism is provided by CXF also.
> 
> With regards,
> Basava
> 
> ***************************************************************************
> * ***********
> This e-mail and attachments contain confidential information from HUAWEI,
> which is intended only for the person or entity whose address is listed
> above. Any use of the information contained herein in any way (including,
> but not limited to, total or partial disclosure, reproduction, or
> dissemination) by persons other than the intended recipient's) is
> prohibited. If you receive this e-mail in error, please notify the sender
>  by phone or email immediately and delete it!
> 
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, November 18, 2009 1:37 AM
> To: users@cxf.apache.org
> Cc: Basavaraja U T
> Subject: Re: High memory usage with web service registration
> 
> 
> 
> In a way, I'm not exactly surprised by this.  I just tried debugging some
>  of
> 
> the annotation stuff in the JRE and annotations are stored in
> LinkedHashMaps.
> Those hashmaps are definitely not the most  memory efficient, especially
>  for
> 
> cases where there are only one or two annotations.   Only Sun/Oracle can do
> much about that.
> 
> JAXB COULD probably not output annotations in cases where the defaults
>  would
> 
> match what the annotation is setting anyway.  That could be an enhancement
> request to them.    You could possibly even write an XJC plugin that would
> remove the annotations in the places where they aren't needed.   That could
> help.
> 
> I'm really not sure what else to suggest.  You COULD create a list of ALL
> the
> jaxb generated classes in all the services and configure them as extra
> classes.   Thus, every service would create their jaxb context based on all
> the classes.   We detect when they are the same and allow the services to
> share a JAXB context instead of creating a new one.   However, that would
> allow the services to "know" more than they really should.
> 
> Dan
> 
> On Tue November 17 2009 2:40:06 am Basavaraja U T wrote:
> > Hi All,
> >
> >
> >
> > I am facing a high memory usage problem with web service registration
> > when wsdl has lots of simple and complex type definitions. I am using
> > jaxb(default) databinding and memory usage is quite high, it is in the
> > range of 2 to 8 MBs for each of the web service registration. I have
> > around 20 web services in an application and total memory usage for web
> > services registration alone is taking more than 60 MB!.
> >
> >
> >
> > I observed the behavior with cxf 2.2 and cxf 2.3 on Windows XP.
> >
> > I observed there were lots of annotations in java files generated from
> > wsdl2java. When these annotations were removed(for testing), the memory
> > usage was drastically less.
> >
> >
> >
> > Is there any way to reduce/optimize the memory usage?
> >
> > Is there any optimizations with respect to annotations/binding generated
> 
> by
> 
> > wsdl2java.
> >
> >
> >
> > With regards,
> >
> > Basava
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

CXF 2.2.5 not available in Maven central

2009-12-04T18:38:25Z


I just checked that the latest CXF available in Maven central is CXF 2.2.4.

Is it planned to deploy CXF 2.2.5 to Maven central?
-- 
View this message in context: http://old.nabble.com/CXF-2.2.5-not-available-in-Maven-central-tp26636371p26636371.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: client socket properties

2009-12-04T18:26:54Z

On Fri December 4 2009 3:46:43 am vogelfanger wrote:
> Hi all,
> 
>   anyone here knows how to change (or even display) the client TCP socket
> properties that the web service is using? For example, how can I know if
> socket has 'nagle algorithm' enabled or disabled? (tcpNoDelay property),
>  and disable it if necessary?

Honestly, I'm not sure there is a way.   We use the JDK's HttpURLConnection 
object which doesn't seem to expose the raw socket.   

Dan


> 
> thanks in advance.
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Dispatch - how to get exception as soap message

2009-12-04T17:46:24Z

I'm not really seeing a way to do it without writing an interceptor.   CXF, 
generally, tries to discard things that aren't needed anymore whenever it can.   
In this case, by the time the exception is thrown, the SOAPMessage has been 
discarded.

Using an interceptor, you could save the SOAPMessage and then retrieve it 
later view the dispatch.getResponseContext().     It would really be something 
like:

SOAPMessage m = msg.getContent(SOAPMessage.class);
msg.put("my.soap.message", m);

That should stick it in the response context.

Dan

On Thu November 26 2009 5:02:39 am Lukasz Lichota wrote:
> Hi,
> 
> I'm using Dispatch and I'd like to return soap message (as e.g. Source) no
> matter if there was an exception or normal response, is there a way to tell
> Dispatch not to throw SOAPFaultException?
> If not, what's the easiest way to transform it to the whole-message Source?
> I can do something like this:
> 		catch(SOAPFaultException e)
> 		{
> 			SOAPFault fault = e.getFault();
> 			Source response = new DOMSource(fault);
> 		}
> but then response contains only soap:fault without body and envelope. How
>  to easily construct the whole envelope? Do I need to manually create XML
>  for soap elements is maybe there's any utility to do this?
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: WSDL2Java with -allowElementReferences with cxf 2.2.x

2009-12-04T16:55:33Z

On Thu November 19 2009 8:06:36 pm Shannon Hastings wrote:
> When in run wsdl to java on a wsdl doc using references in the message
>  where the message uses the same data type twice, ie to create a method
>  that looks like foo(Bar arg1, Bar arg2) I get the following error from
>  wsdlToJava:

Well, jaxws doesn't really allow us to automatically change/increment names 
when doing wsdl2java.   If there is a conflict, you're supposed to use a 
binding file to remap the name.

That said, we have a -autoNameResolution flag that can also be passed to 
automatically do the name increment thing.   That may work for this case.

Another thing you could try is:

  

That would generate as  a List, but would probably work.

Dan


> WSDLToJava Error: Element {http://org.cagrid.introduce/2/Services}Service
> has Having the same name with different types[null -- null],  In wrapper
> style, there is a collision as per the spec.
> 
> I do not get there error if I only have one ref of the Bar type.  Below is
> the snippit of wsdl that causes this error (note: the element test uses the
> introduce-ns0:Service  type twice which seems to be ok with spec and I
>  would expect it to create the method test(Service arg1, Service arg2) ).
> 
> 
>      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns:tns="http://testing.org"
>     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:addr="http://www.w3.org/2001/XMLSchema"
>     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:introduce-ns0="http://org.cagrid.introduce/2/Services">
>     
>          xmlns:wsa="http://www.w3.org/2005/08/addressing"
>             elementFormDefault="qualified"
> targetNamespace="http://testing.org">
>                              schemaLocation="./Services.xsd" />
> 
>             
>                 
>                     
>                         
>                         
>                     
>                 
>             
>             
>                 
>                     
>                         
>                     
>                 
>             
>         
>     
>     
>         
>         
>     
>     
>          element="introduce-ns0:ResourceFrameworkOptions">
>         
>     
>     
>         
>         
>     
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: WSDL2JAVA, store WSDLs and XSDs locally

2009-12-04T16:51:51Z

On Thu November 19 2009 12:53:33 am Craig Tataryn wrote:
> Problem we've faced with the catalog solution is the case where the
> XSDs your WSDL is referencing also references other XSDs in a relative
> way.  It seems (to me) that you can't make a catalog entry which
> overrides "../" to point to a specific place on the classpath.
> 
> For instance:
> WSDL has 
> We map schemas to classpath:/schemas in a catalog and that works well.
> 
> then, in 3rdPartySchema.xsd there is a: .  There seems no way to catalog "../" to point
> to classpath:/coreschemas...


Hmm...   You should HAVE to do anything with the catalogs in this case.   The 
systemId for 3rdPartySchema.xsd should end up being the full URL for whatever 
"classpath:/schemas/3rdPartySchema.xsd" resolves to. (like 
jar:file://..../myproject.jar!/schemas/3rdPartySchema.xsd)

Thus, the relative path, which would resolve from the systemId, should work 
fine for that.    If it isn't, that would be a bug and should be logged (with 
a testcase  :-)   ).

Dan


> 
> What happens is anytime 3rdPartySchema.xsd makes reference to an
> element from base.xsd, it complains it's an unresolved element (but
> doesn't seem to complain that it can't find base.xsd mind you).
> 
> Craig.
> 
> On 16-Nov-09, at 7:25 AM, Daniel Kulp wrote:
> > This is exactly what the XML catalogs are designed for (and the -
> > catalog flag
> > on wsdl2java).     Basically, they allow URL patterns and such used
> > for
> > imports to be mapped into new URL's where the stuff really lives.
> > Thus, you
> > can have "http://..."  type URL's in the wsdl's/xsd's, but have
> > those remapped
> > into file things or such.
> >
> > Dan
> >
> > On Sat November 14 2009 9:31:43 am Dominik Raymann wrote:
> >> Hi there,
> >>
> >> I use WSDL2JAVAto generate client code from a WSDL. I'd like to
> >> store the
> >> WSDL (and all referenced dependencies) locally so that the stubs
> >> can be
> >> generated offline. However, the WSDL references (imports) other
> >> WSDLs as
> >> well as schema files. These references are absolute URLs.
> >>
> >> Is it possible to map these URLs to local files somehow or do I
> >> have to
> >> edit the WSDL manually and change to URLs so that they point to the
> >> local
> >> files?
> >>
> >> Or is there a tool (wsdl2java itself?) that downloads everything
> >> needed for
> >> codegeneration and changes the references so that they point to the
> >> local
> >> copies of the files?
> >>
> >> Thanks for your answer,
> >>
> >> Dominik
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: WSDL wsaw:Action vs soapAction in MAPs on the response message

2009-12-04T16:40:42Z

On Fri December 4 2009 11:15:27 am rduhard wrote:
> I think that the following line of code might be the culprit:	(via the
> MAPAggregator interceptor)
> 
> ContextUtils.getActionFromServiceModel(Message, Exception):
> line: 722	action = (String) 
message.get(SoapBindingConstants.SOAP_ACTION);
> 
> When setting up the outgoing headers, it looks to create the Action from
>  the service model.  Oddly, it looks first to find if there is a SOAPAction
>  defined for the Message, and if not moves on to the wsaw:Action field. I
>  would argue that the line looking to the SOAPAction value be removed
>  entirely as it's not an applicable value for a response message.
> 
> Does this sound right? if so I can submit a patch to get it fixed asap.

For the response, yes.  That does sound correct. 

Dan



> 
> Rebecca
> 
> dkulp wrote:
> > Actually, the OTHER problem is that we're even setting a SOAPAction on
> > the response message.   That's really not needed.   Thus, that MAY be the
> > real bug.   If that wasn't set, then it wouldn't find it and thus it
> > would use the
> > Action header.
> >
> > Dan
> >
> > On Thu December 3 2009 2:58:04 pm Daniel Kulp wrote:
> >> On Wed December 2 2009 11:41:45 pm Craig Tataryn wrote:
> >> > Anyone have an inkling as to whether CXF is interpreting the spec
> >> > correctly on this?  Essentially we have an explicit wsaw:Action
> >> > specified on a response message, yet because there is a soapAction set
> >> > in the binding the wsaw:Action is ignored and replaced with the value
> >> > of the soapAction.
> >>
> >> Yea. This does seem backwords.   Checked the spec:
> >>
> >> http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#actioninwsdl
> >>
> >> "WS-Addressing defines a global attribute, wsaw:Action, that can be used
> >> to
> >> explicitly define the value of the [action] property for messages in a
> >> WSDL
> >> description. The type of the attribute is xs:anyURI and it is used as an
> >> extension on the WSDL input, output and fault elements. A SOAP binding
> >> can
> >> specify SOAPAction values for the input messages of operations. In the
> >>  absence of a wsaw:Action attribute on a WSDL input element where a
> >>  SOAPAction value is specified, the value of the [action] property for
> >> the
> >>  input message is the value of the SOAPAction specified."
> >>
> >> Thus, if that is what's occuring, it's backwords.
> >>
> >> I think the problem stems from :
> >> http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/
> >> which states that for SOAP 1.1, the SOAPAction and Action header have to
> >> match.  If not, a fault needs to be thrown.    Thus, we grab the
> >>  SOAPAction. However, we should be resetting the SOAPAction to the
> >> Action.
> >>   (although, if you are using SOAP 1.1, I would probably argue that your
> >>  wsdl is then "not correct" and the SOAPAction and Action should be set
> >> to
> >>  the same)
> >>
> >>
> >> Dan
> >>
> >> > Thanks,
> >> >
> >> > Craig.
> >> >
> >> > On Fri, Nov 27, 2009 at 10:54 AM, rduhard  wrote:
> >> > > I'm currently implementing WS-Addressing in my web service and am
a
> >> > > little confused about the way CXF is populating the wsa:Action
> >>
> >> property
> >>
> >> > > on the response message.  Our WSDL (provided, not created) defines
> >> > > an input and output message like this with corresponding wsaw:Action
> >> > > attributes defined:
> >> > >
> >> > > 
> >> > > ...
> >> > >  >>
> >> wsaw:Action="ns:messageType.version"
> >>
> >> > > />  >> > > wsaw:Action="ns:messageType-Response.version" />
> >> > > ...
> >> > > 
> >> > >
> >> > > There is also a soapAction defined in the  section:
> >> > > ...
> >> > > 
> >> > > ...
> >> > >
> >> > > From what I understand, the SOAPAction value is used in the HTTP
> >> > > Request Header as information to the receiving server endpoint. But
> >>
> >> on
> >>
> >> > > the outbound message, when populating the wsa:Action field in the
> >> > > outgoing SOAP Headers, CXF first checks for the soapAction element
> >>
> >> and
> >>
> >> > > if it doesn't find one, it then looks for the wsaw:Action value
> >>
> >> defined
> >>
> >> > > on the output message.
> >> > >
> >> > > I"m not sure if I'm missing something, but this seems backwards. I'm
> >> > > defining an explicit value for the Action on the response message
> >> > > but it first looks to the soapAction which I don't think should
> >> > > really apply to the outbound message.
> >> > >
> >> > > The only way I can get it to select my explicitly defined
> >> > > wsaw:Action value on the output is to remove the soapAction
> >> > > attribute from the
> >>
> >> WSDL
> >>
> >> > > (or set it to empty string). However, this isn't an option going
> >> > > forward as we are not the authors of the WSDL.
> >> > >
> >> > > Is it possible that CXF has implemented this wrong and has the
> >> > > action look-up backwards?
> >> > >
> >> > > Thanks in advance, any help/ideas/insight is appreciated.
> >> > >
> >> > >
> >> > > --
> >> > > View this message in context:
> >>
> >> http://old.nabble.com/WSDL-wsaw%3AAction-vs-soapAction-in-MAPs-on-the-r
> >>
> >> > >es ponse-message-tp26545030p26545030.html Sent from the cxf-user
> >>
> >> mailing
> >>
> >> > > list archive at Nabble.com.
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Exception in Soap Dynamic Client

2009-12-04T16:15:54Z

Thank you,

results = client.invoke("ListarBacias");

works fine :-)


Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br



2009/12/4 Daniel Kulp 

>
> This is probably due to:
>
> results = client.invoke("ListarBacias", (Object[]) null);
>
> What does the ListarBacias operations input message look like?
>
> The probably should be:
>
> results = client.invoke("ListarBacias", new Object[0]);
>
> or:
>
> results = client.invoke("ListarBacias");
>
>
> Dan
>
>
>
>
>
>
> On Fri December 4 2009 10:52:06 am Walter Mourão wrote:
> > I removed the Xerces dependency and now I've got:
> >
> > Exception in thread "main" java.lang.RuntimeException:
> > java.lang.NullPointerException
> >     at com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:28)
> >     at com.wim.ita.testemaven.App.main(App.java:116)
> > Caused by: java.lang.NullPointerException
> >     at java.util.Arrays$ArrayList.(Arrays.java:3369)
> >     at java.util.Arrays.asList(Arrays.java:3355)
> >     at
> >
> org.apache.cxf.message.MessageContentsList.(MessageContentsList.java:
> > 36) at
> >  org.apache.cxf.endpoint.ClientImpl.setParameters(ClientImpl.java:592) at
> >  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:454) at
> >  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309) at
> >  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261) at
> >  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:281) at
> >  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:267) at
> >  com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:26)
> >
> > Hints ?
> >
> > Walter Mourão
> > http://waltermourao.com.br
> > http://arcadian.com.br
> > http://oriens.com.br
> >
> >
> >
> > 2009/12/4 Daniel Kulp 
> >
> > > This is due to an old version of Xerces found on the classpath.  Check
> > > the xerces jars and such to make sure they are recent.  (or remove them
> > > entirely
> > > and use the parsers built into the JDK).
> > >
> > > Dan
> > >
> > > On Fri December 4 2009 6:55:55 am Walter Mourão wrote:
> > > > Hi folks,
> > > > I've got the following exception when executing a remote method
> (XFire
> > > >  1.2.5 based server) :
> > > >
> > > > Exception in thread "main" java.lang.AbstractMethodError:
> > >
> > >
> org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/l
> > >an
> > >
> > > > g/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; at
> > > >  org.apache.cxf.staxutils.StaxUtils.addLocation(StaxUtils.java:941)
> at
> > > >  org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:799)
> at
> > > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
> > > >     at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> > > >     at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> > >:2
> > >
> > > > 17) at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:
> > >16
> > >
> > > > 1) at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:6
> > >7)
> > >
> > > >     at org.apache.cxf.endpoint.ClientImpl.(ClientImpl.java:148)
> > > >     at
> > >
> > >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> > >Cl
> > >
> > > > ientFactory.java:253) at
> > >
> > >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> > >Cl
> > >
> > > > ientFactory.java:231) at
> > >
> > >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> > >Cl
> > >
> > > > ientFactory.java:224) at
> > >
> > >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> > >Cl
> > >
> > > > ientFactory.java:159) at
> > > >  com.wim.ita.testemaven.App.testeTestaIPFromFCHT(App.java:75) at
> > > >  com.wim.ita.testemaven.App.main(App.java:116)
> > > >
> > > > The invocation code:
> > > >
> > > >             final JaxWsDynamicClientFactory dcf =
> > > > JaxWsDynamicClientFactory.newInstance();
> > > >             final Client client = dcf.createClient(new URL("
> > > > http://localhost:8080/ioserver-1.0/services/MMAService?wsdl"));
> > > >             results = client.invoke("ListarBacias", (Object[]) null);
> > > >
> > > > The WSDL is attached (and pasted after the message).
> > > >
> > > > Could you please help me ?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Walter Mourão
> > > > http://waltermourao.com.br
> > > > http://arcadian.com.br
> > > > http://oriens.com.br
> > > >
> > > >
> > > > WSDS:
> > > > 
> > > >  > > >  targetNamespace="http://service.webserver.exemplo.ita.br/"
> > > >  xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding"
> xmlns:tns="
> > > >  http://service.webserver.exemplo.ita.br/" xmlns:wsdl="
> > > > http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="
> > > > http://www.w3.org/2001/XMLSchema" xmlns:soap11="
> > > > http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap="
> > > > http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc11="
> > > > http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="
> > > > http://www.w3.org/2003/05/soap-envelope">
> > > >   
> > > >  > > > attributeFormDefault="qualified" elementFormDefault="qualified"
> > > > targetNamespace="http://service.webserver.exemplo.ita.br/">
> > > > 
> > > > 
> > > > 
> > > >  > > > type="xsd:string"/>
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > > type="xsd:string"/>
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > > type="xsd:string"/>
> > > > 
> > > > 
> > > > 
> > > > 
> > > >   
> > > >   
> > > >     
> > > >     
> > > >   
> > > >   
> > > >     
> > > >     
> > > >   
> > > >   
> > > >     
> > > >     
> > > >   
> > > >   
> > > >     
> > > >     
> > > >   
> > > >   
> > > >     
> > > >        > >
> > > message="tns:CriarBaciaRequest">
> > >
> > > >     
> > > >        > > > message="tns:CriarBaciaResponse">
> > > >     
> > > >     
> > > >     
> > > >        > > > message="tns:ListarBaciasRequest">
> > > >     
> > > >        > > > message="tns:ListarBaciasResponse">
> > > >     
> > > >     
> > > >   
> > > >    > >
> > > type="tns:MMAServicePortType">
> > >
> > > >     
> > > >     
> > > >       
> > > >       
> > > >         
> > > >       
> > > >       
> > > >         
> > > >       
> > > >     
> > > >     
> > > >       
> > > >       
> > > >         
> > > >       
> > > >       
> > > >         
> > > >       
> > > >     
> > > >   
> > > >   
> > > >      > > > binding="tns:MMAServiceHttpBinding">
> > > >       
> > > >     
> > > >   
> > > > 
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://www.dankulp.com/blog
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: WSDL wsaw:Action vs soapAction in MAPs on the response message

2009-12-04T16:15:27Z


I think that the following line of code might be the culprit:	(via the
MAPAggregator interceptor)

ContextUtils.getActionFromServiceModel(Message, Exception):
line: 722	action = (String) message.get(SoapBindingConstants.SOAP_ACTION);

When setting up the outgoing headers, it looks to create the Action from the
service model.  Oddly, it looks first to find if there is a SOAPAction
defined for the Message, and if not moves on to the wsaw:Action field. I
would argue that the line looking to the SOAPAction value be removed
entirely as it's not an applicable value for a response message.   

Does this sound right? if so I can submit a patch to get it fixed asap.

Rebecca


dkulp wrote:
> 
> 
> Actually, the OTHER problem is that we're even setting a SOAPAction on the 
> response message.   That's really not needed.   Thus, that MAY be the real 
> bug.   If that wasn't set, then it wouldn't find it and thus it would use
> the 
> Action header.
> 
> Dan
> 
> 
> On Thu December 3 2009 2:58:04 pm Daniel Kulp wrote:
>> On Wed December 2 2009 11:41:45 pm Craig Tataryn wrote:
>> > Anyone have an inkling as to whether CXF is interpreting the spec
>> > correctly on this?  Essentially we have an explicit wsaw:Action
>> > specified on a response message, yet because there is a soapAction set
>> > in the binding the wsaw:Action is ignored and replaced with the value
>> > of the soapAction.
>> 
>> Yea. This does seem backwords.   Checked the spec:
>> 
>> http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#actioninwsdl
>> 
>> "WS-Addressing defines a global attribute, wsaw:Action, that can be used
>> to
>> explicitly define the value of the [action] property for messages in a
>> WSDL
>> description. The type of the attribute is xs:anyURI and it is used as an
>> extension on the WSDL input, output and fault elements. A SOAP binding
>> can
>> specify SOAPAction values for the input messages of operations. In the
>>  absence of a wsaw:Action attribute on a WSDL input element where a
>>  SOAPAction value is specified, the value of the [action] property for
>> the
>>  input message is the value of the SOAPAction specified."
>> 
>> Thus, if that is what's occuring, it's backwords.
>> 
>> I think the problem stems from :
>> http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/
>> which states that for SOAP 1.1, the SOAPAction and Action header have to
>> match.  If not, a fault needs to be thrown.    Thus, we grab the
>>  SOAPAction. However, we should be resetting the SOAPAction to the
>> Action. 
>>   (although, if you are using SOAP 1.1, I would probably argue that your
>>  wsdl is then "not correct" and the SOAPAction and Action should be set
>> to
>>  the same)
>> 
>> 
>> Dan
>> 
>> > Thanks,
>> >
>> > Craig.
>> >
>> > On Fri, Nov 27, 2009 at 10:54 AM, rduhard  wrote:
>> > > I'm currently implementing WS-Addressing in my web service and am a
>> > > little confused about the way CXF is populating the wsa:Action
>> property
>> > > on the response message.  Our WSDL (provided, not created) defines an
>> > > input and output message like this with corresponding wsaw:Action
>> > > attributes defined:
>> > >
>> > > 
>> > > ...
>> > > > wsaw:Action="ns:messageType.version"
>> > > /> > > > wsaw:Action="ns:messageType-Response.version" />
>> > > ...
>> > > 
>> > >
>> > > There is also a soapAction defined in the  section:
>> > > ...
>> > > 
>> > > ...
>> > >
>> > > From what I understand, the SOAPAction value is used in the HTTP
>> > > Request Header as information to the receiving server endpoint. But
>> on
>> > > the outbound message, when populating the wsa:Action field in the
>> > > outgoing SOAP Headers, CXF first checks for the soapAction element
>> and
>> > > if it doesn't find one, it then looks for the wsaw:Action value
>> defined
>> > > on the output message.
>> > >
>> > > I"m not sure if I'm missing something, but this seems backwards. I'm
>> > > defining an explicit value for the Action on the response message but
>> > > it first looks to the soapAction which I don't think should really
>> > > apply to the outbound message.
>> > >
>> > > The only way I can get it to select my explicitly defined wsaw:Action
>> > > value on the output is to remove the soapAction attribute from the
>> WSDL
>> > > (or set it to empty string). However, this isn't an option going
>> > > forward as we are not the authors of the WSDL.
>> > >
>> > > Is it possible that CXF has implemented this wrong and has the action
>> > > look-up backwards?
>> > >
>> > > Thanks in advance, any help/ideas/insight is appreciated.
>> > >
>> > >
>> > > --
>> > > View this message in context:
>> > >
>> http://old.nabble.com/WSDL-wsaw%3AAction-vs-soapAction-in-MAPs-on-the-r
>> > >es ponse-message-tp26545030p26545030.html Sent from the cxf-user
>> mailing
>> > > list archive at Nabble.com.
>> 
> 
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
> 
> 

-- 
View this message in context: http://old.nabble.com/WSDL-wsaw%3AAction-vs-soapAction-in-MAPs-on-the-response-message-tp26545030p26635939.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: off topic - jaxb and DTDs

2009-12-04T16:15:06Z

Well, I'd try converting the DTD to a schema (there are tools out
there for this purpose), then edit the schema to make sure I liked it,
and then use it with JAXB.

On Fri, Dec 4, 2009 at 11:10 AM, Nathaniel Auvil
 wrote:
> This is a bit off topic but is kind of related...
>
> I am calling a SOAP service with a single operation which passes four
> xml:string parameters.  the fourth being the request XML passed as a
> xml:String.  (I had nothing to do with this ugly interface).  It is
> basically a "do everything" method.  On top of this, the types used in this
> parameter are defined in a DTD!  I got JAXB to generate the classes from the
> DTD (some super long method names LOL) and i can marshall the Objects to a
> String with no problems (yet), however when i unmarshall the response, the
> jaxb objects do not get populated correctly, which is not a surprise since
> the DTD support in JAXB is market as "experimental"
>
> I am wondering if anyone has any ideas as to how i can get the result into
> Objects easily without having to manually parse with JAXP or something.  Or
> even better any tricks to getting JAXB to work with DTD based Classes.
>

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T16:12:51Z

On Fri December 4 2009 10:59:11 am Nathaniel Auvil wrote:
> is there a best practice to create a service Singleton and have all your
> threads use it rather than create it new all the time?

Well, it's kind of  tradeoff of memory vs performance and only you can answer 
that in your application.

When we create a Service object, we need to download and parse the WSDL.     
The WSDL is held in a weak cache so it COULD still be around next time you 
create a service, but it might not be.   If the service is a singleton, it 
would keep it around forever consuming memory.   If you never need it again, 
that's a waste of memory.

Likewise, the client proxies created from the Service could ALSO be 
singletons.  (caveat: see the FAQ about the thread safety of these: 
http://cxf.apache.org/faq.html)    When we create a proxy, we have to create 
JAXBContexts, wire the wsdl information in, map methods, etc.... which is 
expensive.   However, holding onto the proxy consumes memory due to the jaxb 
context, method maps, etc.....   

In general, my recommendation is that if the service will be used pretty 
often, a singleton is definitely appropriate. The cost of creating new proxies 
per request is pretty high so reusing them is definitely a good thing.    If 
the service is not used often, then don't.

One more caveat:  the Service and Proxy objects in the JAX-WS RI are NOT 
thread safe at all.   Thus, from a portability standpoint, once you do this, 
you are kind of tied to CXF.    The RI folks recommend either synchronizing on 
the objects or use a pool.    Personally, I prefer just making the things 
thread safe if possible.   :-)


Dan





> 
> On Fri, Dec 4, 2009 at 10:55 AM, Benson Margulies 
wrote:
> > The WSDL reader just reads the stream. There could be some sort of
> > option to have it buffer and log. My idea was to buffer a bit so that
> > we had something to log without paying the cost of a full buffer.
> >
> >
> > On Fri, Dec 4, 2009 at 10:47 AM, Nathaniel Auvil
> >
> >  wrote:
> > > Is there a way to have the log interceptors show the request/response
> > > for the WSDL?
> > >
> > > On Fri, Dec 4, 2009 at 10:22 AM, Daniel Kulp  wrote:
> > >> On Fri December 4 2009 10:13:52 am Benson Margulies wrote:
> > >> > Dan, I still wonder what is hitting him to begin with. I have an
> > >> > idea: capture the first 256 bytes of the returned WSDL and include
> > >> > it in the error. I'm musing about how to make the unit test for
> > >> > this.
> > >>
> > >> It's probably the "Cannot find operation...." soap fault that would
> > >> normally
> > >> be generated when you do a get on the service address.
> > >>
> > >> Dan
> > >>
> > >> > On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp 
wrote:
> > >> > > On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> > >> > >> ah...when i added a ?wsdl to the URL it worked.  Why does
CXF
> > >> > >> need
> >
> > to
> >
> > >> > >> parse the WSDL at runtime?  I have already generated my code.
> > >> > >
> > >> > > That's pretty much what the JAX-WS spec requires.   There are
> > >> > > things in
> > >> > > the WSDL that are not completely represented in code.   The actual
> > >> > > endpoint address is one of them.   Things like policies are
> > >> > > another.
> > >> > >
> > >> > > In MOST cases, you can pass null for the wsdl location and then
do
> > >> > > a service.createPort(...) call to create a port with your service
> > >> > > URL and
> > >> > > it will work fine.    For straight soap calls with nothing fancy,
> >
> > the
> >
> > >> > > generated code may be enough in that case.
> > >> > >
> > >> > > Dan
> > >> > >
> > >> > >> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> > >> > >
> > >> > > wrote:
> > >> > >> > CXF is trying to dynamically take the WSDL from your
service,
> > >> > >> > and something is coming back (perhaps an error page)
that is
> > >> > >> > not much like
> > >> > >> > a WSDL. If you manually grab the ?wsdl URL what do you
see?
> > >> > >> >
> > >> > >> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> > >> > >> >
> > >> > >> >  wrote:
> > >> > >> > > Hi all.  I am using Maven to generate a SOAP client
from
> > >> > >> > > WSDL.
> >
> > I
> >
> > >> > >> > > followed the web site example and some other examples
i found
> >
> > on
> >
> > >> > >> > > the
> > >> > >> > > net and my classes seemed to generate fine. As
a side note i
> > >> > >> > > am using java version "1.6.0_16"
> > >> > >> > >
> > >> > >> > >        
> > >> > >> > >                org.apache.cxf
> > >> > >> > >                cxf-codegen-plugin
> > >> > >> > >                ${cxf.version}
> > >> > >> > >                
> > >> > >> > >                    
> > >> > >> > >                        generate-sources
> > >> > >> > >                        generate-sources
> > >> > >> > >                        
> > >> > >> > >                            true
> >
> > ${project.build.directory}/generated/cxf
> >
> > >> > >> > >                            
> > >> > >> > >                                
> > >> > >> > >
> > >> > >> > > ${basedir}/src/main/wsdl/oasApi.wsdl
> > >> > >> > >                                    
> > >> > >> > >
> > >> > >> > >                                       
> > >> > >> > > -p
> > >> > >> > >
> > >> > >> > > com.xxx.soap 
> > >> > >> > >
> > >> > >> > >                                
> > >> > >> > >
> > >> > >> > >                            
> > >> > >> > >                        
> > >> > >> > >                        
> > >> > >> > >                            wsdl2java
> > >> > >> > >                        
> > >> > >> > >                    
> > >> > >> > >                
> > >> > >> > >            
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > However, when i create a new xxxService Object
as in...
> > >> > >> > >
> > >> > >> > > OaxApiService service = new OaxApiService( url,
> > >> > >> > > OaxApiService.SERVICE );
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > i am getting the following exception....
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > org.apache.cxf.service.factory.ServiceConstructionException:
> > >> > >> > > Failed
> > >> > >> > > to create service.
> > >> > >> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >
> > >> > >> >a:9 3)
> > >> > >> >
> > >> > >> > >    at
> >
> > org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:20
> >
> > >> > >> > >5) at
> > >> > >> > > org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> > >> > >> > > at
> >
> > org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderIm
> >
> > >> > >> >pl. java:65)
> > >> > >> >
> > >> > >> > >    at javax.xml.ws.Service.(Service.java:56)
> > >> > >> > >    at
> > >> > >> > > com.xxx.soap.OaxApiService.(OaxApiService.java:48)
at
> > >> > >> > > com.xxx.OaxClient.invoke(OaxClient.java:97)
> > >> > >> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> > >> > >> > > Caused by: javax.wsdl.WSDLException: WSDLException:
> > >> > >> >
> > >> > >> > faultCode=PARSER_ERROR:
> > >> > >> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> > >> > >> > > character
> > >> > >> > > 't'
> > >> > >> >
> > >> > >> > (code
> > >> > >> >
> > >> > >> > > 116) excepted space, or '>' or "/>"
> > >> > >> > >  at [row,col,system-id]:
> > >> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >
> > >> > >> >ava
> > >> > >> >
> > >> > >> >:226)
> > >> > >> >:
> > >> > >> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.ja
> >
> > >> > >> >va: 179)
> > >> > >> >
> > >> > >> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >
> > >> > >> >a:9 1)
> > >> > >> >
> > >> > >> > >    ... 7 more
> > >> > >> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
> > >> > >> > > Unexpected
> > >> > >> > > character 't' (code 116) excepted space, or '>'
or "/>"
> > >> > >> > >  at [row,col,system-id]:
> > >> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >
> > com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java
> >
> > >> > >> > >:64 8) at
> >
> > com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java
> >
> > >> > >> >:29 65)
> > >> > >> >:
> > >> > >> > >    at
> >
> > com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.ja
> >
> > >> > >> >va: 2936)
> > >> > >> >
> > >> > >> > >    at
> >
> > com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:
> > >> > >> >284 8)
> > >> > >> >
> > >> > >> > >    at
> >
> > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
> >
> > >> > >> > > at
> >
> > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:90
> >
> > >> > >> > >8) at
> >
> > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
> >
> > >> > >> > > at
> >
> > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:86
> >
> > >> > >> > >8) at
> >
> > org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> >
> > >> > >> > > at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >
> > >> > >> >ava
> > >> > >> >
> > >> > >> >:217)
> > >> > >> >:
> > >> > >> > >    ... 9 more
> > >> > >
> > >> > > --
> > >> > > Daniel Kulp
> > >> > > dkulp@apache.org
> > >> > > http://www.dankulp.com/blog
> > >>
> > >> --
> > >> Daniel Kulp
> > >> dkulp@apache.org
> > >> http://www.dankulp.com/blog
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

off topic - jaxb and DTDs

2009-12-04T16:10:28Z

This is a bit off topic but is kind of related...

I am calling a SOAP service with a single operation which passes four
xml:string parameters.  the fourth being the request XML passed as a
xml:String.  (I had nothing to do with this ugly interface).  It is
basically a "do everything" method.  On top of this, the types used in this
parameter are defined in a DTD!  I got JAXB to generate the classes from the
DTD (some super long method names LOL) and i can marshall the Objects to a
String with no problems (yet), however when i unmarshall the response, the
jaxb objects do not get populated correctly, which is not a surprise since
the DTD support in JAXB is market as "experimental"

I am wondering if anyone has any ideas as to how i can get the result into
Objects easily without having to manually parse with JAXP or something.  Or
even better any tricks to getting JAXB to work with DTD based Classes.

Re: Exception in Soap Dynamic Client

2009-12-04T16:00:26Z


This is probably due to:

results = client.invoke("ListarBacias", (Object[]) null);

What does the ListarBacias operations input message look like?

The probably should be:

results = client.invoke("ListarBacias", new Object[0]);

or:

results = client.invoke("ListarBacias");


Dan






On Fri December 4 2009 10:52:06 am Walter Mour�o wrote:
> I removed the Xerces dependency and now I've got:
> 
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.NullPointerException
>     at com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:28)
>     at com.wim.ita.testemaven.App.main(App.java:116)
> Caused by: java.lang.NullPointerException
>     at java.util.Arrays$ArrayList.(Arrays.java:3369)
>     at java.util.Arrays.asList(Arrays.java:3355)
>     at
> org.apache.cxf.message.MessageContentsList.(MessageContentsList.java:
> 36) at
>  org.apache.cxf.endpoint.ClientImpl.setParameters(ClientImpl.java:592) at
>  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:454) at
>  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309) at
>  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261) at
>  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:281) at
>  org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:267) at
>  com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:26)
> 
> Hints ?
> 
> Walter Mour�o
> http://waltermourao.com.br
> http://arcadian.com.br
> http://oriens.com.br
> 
> 
> 
> 2009/12/4 Daniel Kulp 
> 
> > This is due to an old version of Xerces found on the classpath.  Check
> > the xerces jars and such to make sure they are recent.  (or remove them
> > entirely
> > and use the parsers built into the JDK).
> >
> > Dan
> >
> > On Fri December 4 2009 6:55:55 am Walter Mour�o wrote:
> > > Hi folks,
> > > I've got the following exception when executing a remote method (XFire
> > >  1.2.5 based server) :
> > >
> > > Exception in thread "main" java.lang.AbstractMethodError:
> >
> > org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/l
> >an
> >
> > > g/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; at
> > >  org.apache.cxf.staxutils.StaxUtils.addLocation(StaxUtils.java:941) at
> > >  org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:799) at
> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
> > >     at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> > >     at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> >:2
> >
> > > 17) at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:
> >16
> >
> > > 1) at
> >
> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:6
> >7)
> >
> > >     at org.apache.cxf.endpoint.ClientImpl.(ClientImpl.java:148)
> > >     at
> >
> > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> >Cl
> >
> > > ientFactory.java:253) at
> >
> > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> >Cl
> >
> > > ientFactory.java:231) at
> >
> > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> >Cl
> >
> > > ientFactory.java:224) at
> >
> > org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(Dynamic
> >Cl
> >
> > > ientFactory.java:159) at
> > >  com.wim.ita.testemaven.App.testeTestaIPFromFCHT(App.java:75) at
> > >  com.wim.ita.testemaven.App.main(App.java:116)
> > >
> > > The invocation code:
> > >
> > >             final JaxWsDynamicClientFactory dcf =
> > > JaxWsDynamicClientFactory.newInstance();
> > >             final Client client = dcf.createClient(new URL("
> > > http://localhost:8080/ioserver-1.0/services/MMAService?wsdl"));
> > >             results = client.invoke("ListarBacias", (Object[]) null);
> > >
> > > The WSDL is attached (and pasted after the message).
> > >
> > > Could you please help me ?
> > >
> > > Thanks in advance,
> > >
> > > Walter Mour�o
> > > http://waltermourao.com.br
> > > http://arcadian.com.br
> > > http://oriens.com.br
> > >
> > >
> > > WSDS:
> > > 
> > >  > >  targetNamespace="http://service.webserver.exemplo.ita.br/"
> > >  xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="
> > >  http://service.webserver.exemplo.ita.br/" xmlns:wsdl="
> > > http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="
> > > http://www.w3.org/2001/XMLSchema" xmlns:soap11="
> > > http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap="
> > > http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc11="
> > > http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="
> > > http://www.w3.org/2003/05/soap-envelope">
> > >   
> > >  > > attributeFormDefault="qualified" elementFormDefault="qualified"
> > > targetNamespace="http://service.webserver.exemplo.ita.br/">
> > > 
> > > 
> > > 
> > >  > > type="xsd:string"/>
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > type="xsd:string"/>
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > > type="xsd:string"/>
> > > 
> > > 
> > > 
> > > 
> > >   
> > >   
> > >     
> > >     
> > >   
> > >   
> > >     
> > >     
> > >   
> > >   
> > >     
> > >     
> > >   
> > >   
> > >     
> > >     
> > >   
> > >   
> > >     
> > >        >
> > message="tns:CriarBaciaRequest">
> >
> > >     
> > >        > > message="tns:CriarBaciaResponse">
> > >     
> > >     
> > >     
> > >        > > message="tns:ListarBaciasRequest">
> > >     
> > >        > > message="tns:ListarBaciasResponse">
> > >     
> > >     
> > >   
> > >    >
> > type="tns:MMAServicePortType">
> >
> > >     
> > >     
> > >       
> > >       
> > >         
> > >       
> > >       
> > >         
> > >       
> > >     
> > >     
> > >       
> > >       
> > >         
> > >       
> > >       
> > >         
> > >       
> > >     
> > >   
> > >   
> > >      > > binding="tns:MMAServiceHttpBinding">
> > >       
> > >     
> > >   
> > > 
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T15:59:11Z

is there a best practice to create a service Singleton and have all your
threads use it rather than create it new all the time?


On Fri, Dec 4, 2009 at 10:55 AM, Benson Margulies wrote:

> The WSDL reader just reads the stream. There could be some sort of
> option to have it buffer and log. My idea was to buffer a bit so that
> we had something to log without paying the cost of a full buffer.
>
>
> On Fri, Dec 4, 2009 at 10:47 AM, Nathaniel Auvil
>  wrote:
> > Is there a way to have the log interceptors show the request/response for
> > the WSDL?
> >
> >
> > On Fri, Dec 4, 2009 at 10:22 AM, Daniel Kulp  wrote:
> >>
> >> On Fri December 4 2009 10:13:52 am Benson Margulies wrote:
> >> > Dan, I still wonder what is hitting him to begin with. I have an idea:
> >> > capture the first 256 bytes of the returned WSDL and include it in the
> >> > error. I'm musing about how to make the unit test for this.
> >>
> >> It's probably the "Cannot find operation...." soap fault that would
> >> normally
> >> be generated when you do a get on the service address.
> >>
> >> Dan
> >>
> >>
> >>
> >> > On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:
> >> > > On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> >> > >> ah...when i added a ?wsdl to the URL it worked.  Why does CXF
need
> to
> >> > >> parse the WSDL at runtime?  I have already generated my code.
> >> > >
> >> > > That's pretty much what the JAX-WS spec requires.   There are things
> >> > > in
> >> > > the WSDL that are not completely represented in code.   The actual
> >> > > endpoint address is one of them.   Things like policies are another.
> >> > >
> >> > > In MOST cases, you can pass null for the wsdl location and then do
a
> >> > > service.createPort(...) call to create a port with your service URL
> >> > > and
> >> > > it will work fine.    For straight soap calls with nothing fancy,
> the
> >> > > generated code may be enough in that case.
> >> > >
> >> > > Dan
> >> > >
> >> > >> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> >> > >
> >> > > wrote:
> >> > >> > CXF is trying to dynamically take the WSDL from your service,
and
> >> > >> > something is coming back (perhaps an error page) that is
not much
> >> > >> > like
> >> > >> > a WSDL. If you manually grab the ?wsdl URL what do you see?
> >> > >> >
> >> > >> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> >> > >> >
> >> > >> >  wrote:
> >> > >> > > Hi all.  I am using Maven to generate a SOAP client
from WSDL.
> I
> >> > >> > > followed the web site example and some other examples
i found
> on
> >> > >> > > the
> >> > >> > > net and my classes seemed to generate fine. As a side
note i am
> >> > >> > > using java version "1.6.0_16"
> >> > >> > >
> >> > >> > >        
> >> > >> > >                org.apache.cxf
> >> > >> > >                cxf-codegen-plugin
> >> > >> > >                ${cxf.version}
> >> > >> > >                
> >> > >> > >                    
> >> > >> > >                        generate-sources
> >> > >> > >                        generate-sources
> >> > >> > >                        
> >> > >> > >                            true
> >> > >> > >
> >> > >> > >
> ${project.build.directory}/generated/cxf
> >> > >> > >                            
> >> > >> > >                                
> >> > >> > >
> >> > >> > > ${basedir}/src/main/wsdl/oasApi.wsdl
> >> > >> > >                                    
> >> > >> > >
> >> > >> > >                                        -p
> >> > >> > >
> >> > >> > > com.xxx.soap 
> >> > >> > >
> >> > >> > >                                
> >> > >> > >
> >> > >> > >                            
> >> > >> > >                        
> >> > >> > >                        
> >> > >> > >                            wsdl2java
> >> > >> > >                        
> >> > >> > >                    
> >> > >> > >                
> >> > >> > >            
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > However, when i create a new xxxService Object as in...
> >> > >> > >
> >> > >> > > OaxApiService service = new OaxApiService( url,
> >> > >> > > OaxApiService.SERVICE );
> >> > >> > >
> >> > >> > >
> >> > >> > > i am getting the following exception....
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > org.apache.cxf.service.factory.ServiceConstructionException:
> >> > >> > > Failed
> >> > >> > > to create service.
> >> > >> > >    at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >> > >> >a:9 3)
> >> > >> >
> >> > >> > >    at
> >> > >> > >
> >> > >> > >
> org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:20
> >> > >> > >5) at
> >> > >> > > org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> >> > >> > > at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderIm
> >> > >> >pl. java:65)
> >> > >> >
> >> > >> > >    at javax.xml.ws.Service.(Service.java:56)
> >> > >> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
> >> > >> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
> >> > >> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> >> > >> > > Caused by: javax.wsdl.WSDLException: WSDLException:
> >> > >> >
> >> > >> > faultCode=PARSER_ERROR:
> >> > >> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> >> > >> > > character
> >> > >> > > 't'
> >> > >> >
> >> > >> > (code
> >> > >> >
> >> > >> > > 116) excepted space, or '>' or "/>"
> >> > >> > >  at [row,col,system-id]:
> >> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >> > >> >ava
> >> > >> >
> >> > >> >:226)
> >> > >> >:
> >> > >> > >    at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.ja
> >> > >> >va: 179)
> >> > >> >
> >> > >> > >    at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >> > >> >a:9 1)
> >> > >> >
> >> > >> > >    ... 7 more
> >> > >> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
> >> > >> > > Unexpected
> >> > >> > > character 't' (code 116) excepted space, or '>' or
"/>"
> >> > >> > >  at [row,col,system-id]:
> >> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >> > >> > >
> >> > >> > >
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java
> >> > >> > >:64 8) at
> >> > >> >
> >> > >> >
> >> > >> >
> com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java
> >> > >> >:29 65)
> >> > >> >
> >> > >> > >    at
> >> > >> >
> >> > >> >
> >> > >> >
> com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.ja
> >> > >> >va: 2936)
> >> > >> >
> >> > >> > >    at
> >> > >> >
> >> > >> >
> >> > >> >
> com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:
> >> > >> >284 8)
> >> > >> >
> >> > >> > >    at
> >> > >> > >
> >> > >> > >
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
> >> > >> > > at
> >> > >> > >
> >> > >> > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:90
> >> > >> > >8) at
> >> > >> > >
> >> > >> > >
> org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
> >> > >> > > at
> >> > >> > >
> >> > >> > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:86
> >> > >> > >8) at
> org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> >> > >> > > at
> >> > >> >
> >> > >> >
> >> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >> > >> >ava
> >> > >> >
> >> > >> >:217)
> >> > >> >:
> >> > >> > >    ... 9 more
> >> > >
> >> > > --
> >> > > Daniel Kulp
> >> > > dkulp@apache.org
> >> > > http://www.dankulp.com/blog
> >> >
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://www.dankulp.com/blog
> >
> >
>

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T15:55:13Z

The WSDL reader just reads the stream. There could be some sort of
option to have it buffer and log. My idea was to buffer a bit so that
we had something to log without paying the cost of a full buffer.


On Fri, Dec 4, 2009 at 10:47 AM, Nathaniel Auvil
 wrote:
> Is there a way to have the log interceptors show the request/response for
> the WSDL?
>
>
> On Fri, Dec 4, 2009 at 10:22 AM, Daniel Kulp  wrote:
>>
>> On Fri December 4 2009 10:13:52 am Benson Margulies wrote:
>> > Dan, I still wonder what is hitting him to begin with. I have an idea:
>> > capture the first 256 bytes of the returned WSDL and include it in the
>> > error. I'm musing about how to make the unit test for this.
>>
>> It's probably the "Cannot find operation...." soap fault that would
>> normally
>> be generated when you do a get on the service address.
>>
>> Dan
>>
>>
>>
>> > On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:
>> > > On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
>> > >> ah...when i added a ?wsdl to the URL it worked.  Why does CXF need
to
>> > >> parse the WSDL at runtime?  I have already generated my code.
>> > >
>> > > That's pretty much what the JAX-WS spec requires.   There are things
>> > > in
>> > > the WSDL that are not completely represented in code.   The actual
>> > > endpoint address is one of them.   Things like policies are another.
>> > >
>> > > In MOST cases, you can pass null for the wsdl location and then do a
>> > > service.createPort(...) call to create a port with your service URL
>> > > and
>> > > it will work fine.    For straight soap calls with nothing fancy, the
>> > > generated code may be enough in that case.
>> > >
>> > > Dan
>> > >
>> > >> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
>> > >
>> > > wrote:
>> > >> > CXF is trying to dynamically take the WSDL from your service,
and
>> > >> > something is coming back (perhaps an error page) that is not much
>> > >> > like
>> > >> > a WSDL. If you manually grab the ?wsdl URL what do you see?
>> > >> >
>> > >> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
>> > >> >
>> > >> >  wrote:
>> > >> > > Hi all.  I am using Maven to generate a SOAP client from
WSDL. I
>> > >> > > followed the web site example and some other examples i found
on
>> > >> > > the
>> > >> > > net and my classes seemed to generate fine. As a side note
i am
>> > >> > > using java version "1.6.0_16"
>> > >> > >
>> > >> > >        
>> > >> > >                org.apache.cxf
>> > >> > >                cxf-codegen-plugin
>> > >> > >                ${cxf.version}
>> > >> > >                
>> > >> > >                    
>> > >> > >                        generate-sources
>> > >> > >                        generate-sources
>> > >> > >                        
>> > >> > >                            true
>> > >> > >
>> > >> > > ${project.build.directory}/generated/cxf
>> > >> > >                            
>> > >> > >                                
>> > >> > >
>> > >> > > ${basedir}/src/main/wsdl/oasApi.wsdl
>> > >> > >                                    
>> > >> > >
>> > >> > >                                      
 -p
>> > >> > >
>> > >> > > com.xxx.soap 
>> > >> > >
>> > >> > >                                
>> > >> > >
>> > >> > >                            
>> > >> > >                        
>> > >> > >                        
>> > >> > >                            wsdl2java
>> > >> > >                        
>> > >> > >                    
>> > >> > >                
>> > >> > >            
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > However, when i create a new xxxService Object as in...
>> > >> > >
>> > >> > > OaxApiService service = new OaxApiService( url,
>> > >> > > OaxApiService.SERVICE );
>> > >> > >
>> > >> > >
>> > >> > > i am getting the following exception....
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > org.apache.cxf.service.factory.ServiceConstructionException:
>> > >> > > Failed
>> > >> > > to create service.
>> > >> > >    at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
>> > >> >a:9 3)
>> > >> >
>> > >> > >    at
>> > >> > >
>> > >> > > org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:20
>> > >> > >5) at
>> > >> > > org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
>> > >> > > at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderIm
>> > >> >pl. java:65)
>> > >> >
>> > >> > >    at javax.xml.ws.Service.(Service.java:56)
>> > >> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
>> > >> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
>> > >> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
>> > >> > > Caused by: javax.wsdl.WSDLException: WSDLException:
>> > >> >
>> > >> > faultCode=PARSER_ERROR:
>> > >> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> > >> > > character
>> > >> > > 't'
>> > >> >
>> > >> > (code
>> > >> >
>> > >> > > 116) excepted space, or '>' or "/>"
>> > >> > >  at [row,col,system-id]:
>> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
>> > >> >ava
>> > >> >
>> > >> >:226)
>> > >> >:
>> > >> > >    at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.ja
>> > >> >va: 179)
>> > >> >
>> > >> > >    at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
>> > >> >a:9 1)
>> > >> >
>> > >> > >    ... 7 more
>> > >> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
>> > >> > > Unexpected
>> > >> > > character 't' (code 116) excepted space, or '>' or "/>"
>> > >> > >  at [row,col,system-id]:
>> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
>> > >> > >
>> > >> > > com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java
>> > >> > >:64 8) at
>> > >> >
>> > >> >
>> > >> > com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java
>> > >> >:29 65)
>> > >> >
>> > >> > >    at
>> > >> >
>> > >> >
>> > >> > com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.ja
>> > >> >va: 2936)
>> > >> >
>> > >> > >    at
>> > >> >
>> > >> >
>> > >> > com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:
>> > >> >284 8)
>> > >> >
>> > >> > >    at
>> > >> > >
>> > >> > > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
>> > >> > > at
>> > >> > >
>> > >> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:90
>> > >> > >8) at
>> > >> > >
>> > >> > > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
>> > >> > > at
>> > >> > >
>> > >> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:86
>> > >> > >8) at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
>> > >> > > at
>> > >> >
>> > >> >
>> > >> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
>> > >> >ava
>> > >> >
>> > >> >:217)
>> > >> >:
>> > >> > >    ... 9 more
>> > >
>> > > --
>> > > Daniel Kulp
>> > > dkulp@apache.org
>> > > http://www.dankulp.com/blog
>> >
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://www.dankulp.com/blog
>
>

Re: Exception in Soap Dynamic Client

2009-12-04T15:52:06Z

I removed the Xerces dependency and now I've got:

Exception in thread "main" java.lang.RuntimeException:
java.lang.NullPointerException
    at com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:28)
    at com.wim.ita.testemaven.App.main(App.java:116)
Caused by: java.lang.NullPointerException
    at java.util.Arrays$ArrayList.(Arrays.java:3369)
    at java.util.Arrays.asList(Arrays.java:3355)
    at
org.apache.cxf.message.MessageContentsList.(MessageContentsList.java:36)
    at org.apache.cxf.endpoint.ClientImpl.setParameters(ClientImpl.java:592)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:454)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:281)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:267)
    at com.wim.ita.testemaven.App.testeBaciasFromIOServer(App.java:26)

Hints ?

Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br



2009/12/4 Daniel Kulp 

>
> This is due to an old version of Xerces found on the classpath.  Check the
> xerces jars and such to make sure they are recent.  (or remove them
> entirely
> and use the parsers built into the JDK).
>
> Dan
>
>
> On Fri December 4 2009 6:55:55 am Walter Mourão wrote:
> > Hi folks,
> > I've got the following exception when executing a remote method (XFire
> >  1.2.5 based server) :
> >
> > Exception in thread "main" java.lang.AbstractMethodError:
> >
> org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lan
> > g/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; at
> >  org.apache.cxf.staxutils.StaxUtils.addLocation(StaxUtils.java:941) at
> >  org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:799) at
> > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
> >     at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> >     at
> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:2
> > 17) at
> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:16
> > 1) at
> >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:67)
> >     at org.apache.cxf.endpoint.ClientImpl.(ClientImpl.java:148)
> >     at
> >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> > ientFactory.java:253) at
> >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> > ientFactory.java:231) at
> >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> > ientFactory.java:224) at
> >
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> > ientFactory.java:159) at
> >  com.wim.ita.testemaven.App.testeTestaIPFromFCHT(App.java:75) at
> >  com.wim.ita.testemaven.App.main(App.java:116)
> >
> > The invocation code:
> >
> >             final JaxWsDynamicClientFactory dcf =
> > JaxWsDynamicClientFactory.newInstance();
> >             final Client client = dcf.createClient(new URL("
> > http://localhost:8080/ioserver-1.0/services/MMAService?wsdl"));
> >             results = client.invoke("ListarBacias", (Object[]) null);
> >
> > The WSDL is attached (and pasted after the message).
> >
> > Could you please help me ?
> >
> > Thanks in advance,
> >
> > Walter Mourão
> > http://waltermourao.com.br
> > http://arcadian.com.br
> > http://oriens.com.br
> >
> >
> > WSDS:
> > 
> >  >  targetNamespace="http://service.webserver.exemplo.ita.br/"
> >  xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="
> >  http://service.webserver.exemplo.ita.br/" xmlns:wsdl="
> > http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="
> > http://www.w3.org/2001/XMLSchema" xmlns:soap11="
> > http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap="
> > http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc11="
> > http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="
> > http://www.w3.org/2003/05/soap-envelope">
> >   
> >  > attributeFormDefault="qualified" elementFormDefault="qualified"
> > targetNamespace="http://service.webserver.exemplo.ita.br/">
> > 
> > 
> > 
> >  > type="xsd:string"/>
> > 
> > 
> > 
> > 
> > 
> > 
> >  > type="xsd:string"/>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  > type="xsd:string"/>
> > 
> > 
> > 
> > 
> >   
> >   
> >     
> >     
> >   
> >   
> >     
> >     
> >   
> >   
> >     
> >     
> >   
> >   
> >     
> >     
> >   
> >   
> >     
> >        message="tns:CriarBaciaRequest">
> >     
> >        > message="tns:CriarBaciaResponse">
> >     
> >     
> >     
> >        > message="tns:ListarBaciasRequest">
> >     
> >        > message="tns:ListarBaciasResponse">
> >     
> >     
> >   
> >    type="tns:MMAServicePortType">
> >     
> >     
> >       
> >       
> >         
> >       
> >       
> >         
> >       
> >     
> >     
> >       
> >       
> >         
> >       
> >       
> >         
> >       
> >     
> >   
> >   
> >      > binding="tns:MMAServiceHttpBinding">
> >       
> >     
> >   
> > 
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: Init Code

2009-12-04T15:48:20Z

Thank you very much Pawel!!!!
Paweł Lipka escribió:
> Alternatively, not to tie yourself to JSR-250, you could put your code 
> into a plain 'void initialize() throws Exception' method and use 
> Spring's bean element init-method attribute to specify which method is 
> to be invoked after ur component is instantiated and wired to its 
> dependencies.
>
>
> Daniel Kulp wrote:
>>
>> In a method annotated with @PostConstruct?
>>
>> Dan
>>
>>
>>
>> On Fri December 4 2009 9:45:05 am Wadi Jalil Maluf wrote:
>>> Hi all,
>>>        I'm building a web application with spring and apache cxf. I
>>> would like to know where te best place to put initialization code is.
>>> Thanks in advance,
>>> Regards,
>>> Wadi
>>>
>>>
>>> __________ Información de ESET NOD32 Antivirus, versión de la base de
>>>  firmas de virus 4660 (20091204) __________
>>>
>>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>>
>>> http://www.eset.com
>>>
>>
>
>



__________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de virus 4660
(20091204) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T15:47:45Z

Is there a way to have the log interceptors show the request/response for
the WSDL?


On Fri, Dec 4, 2009 at 10:22 AM, Daniel Kulp  wrote:

> On Fri December 4 2009 10:13:52 am Benson Margulies wrote:
> > Dan, I still wonder what is hitting him to begin with. I have an idea:
> > capture the first 256 bytes of the returned WSDL and include it in the
> > error. I'm musing about how to make the unit test for this.
>
> It's probably the "Cannot find operation...." soap fault that would
> normally
> be generated when you do a get on the service address.
>
> Dan
>
>
>
> > On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:
> > > On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> > >> ah...when i added a ?wsdl to the URL it worked.  Why does CXF need to
> > >> parse the WSDL at runtime?  I have already generated my code.
> > >
> > > That's pretty much what the JAX-WS spec requires.   There are things in
> > > the WSDL that are not completely represented in code.   The actual
> > > endpoint address is one of them.   Things like policies are another.
> > >
> > > In MOST cases, you can pass null for the wsdl location and then do a
> > > service.createPort(...) call to create a port with your service URL and
> > > it will work fine.    For straight soap calls with nothing fancy, the
> > > generated code may be enough in that case.
> > >
> > > Dan
> > >
> > >> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> > >
> > > wrote:
> > >> > CXF is trying to dynamically take the WSDL from your service, and
> > >> > something is coming back (perhaps an error page) that is not much
> like
> > >> > a WSDL. If you manually grab the ?wsdl URL what do you see?
> > >> >
> > >> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> > >> >
> > >> >  wrote:
> > >> > > Hi all.  I am using Maven to generate a SOAP client from WSDL.
I
> > >> > > followed the web site example and some other examples i found
on
> the
> > >> > > net and my classes seemed to generate fine. As a side note i
am
> > >> > > using java version "1.6.0_16"
> > >> > >
> > >> > >        
> > >> > >                org.apache.cxf
> > >> > >                cxf-codegen-plugin
> > >> > >                ${cxf.version}
> > >> > >                
> > >> > >                    
> > >> > >                        generate-sources
> > >> > >                        generate-sources
> > >> > >                        
> > >> > >                            true
> > >> > >
> > >> > > ${project.build.directory}/generated/cxf
> > >> > >                            
> > >> > >                                
> > >> > >
> > >> > > ${basedir}/src/main/wsdl/oasApi.wsdl
> > >> > >                                    
> > >> > >
> > >> > >                                        -p
> > >> > >
> > >> > > com.xxx.soap 
> > >> > >
> > >> > >                                
> > >> > >
> > >> > >                            
> > >> > >                        
> > >> > >                        
> > >> > >                            wsdl2java
> > >> > >                        
> > >> > >                    
> > >> > >                
> > >> > >            
> > >> > >
> > >> > >
> > >> > >
> > >> > > However, when i create a new xxxService Object as in...
> > >> > >
> > >> > > OaxApiService service = new OaxApiService( url,
> > >> > > OaxApiService.SERVICE );
> > >> > >
> > >> > >
> > >> > > i am getting the following exception....
> > >> > >
> > >> > >
> > >> > >
> > >> > > org.apache.cxf.service.factory.ServiceConstructionException:
> Failed
> > >> > > to create service.
> > >> > >    at
> > >> >
> > >> >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> > >> >a:9 3)
> > >> >
> > >> > >    at
> > >> > >
> org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:20
> > >> > >5) at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> > >> > > at
> > >> >
> > >> >
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderIm
> > >> >pl. java:65)
> > >> >
> > >> > >    at javax.xml.ws.Service.(Service.java:56)
> > >> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
> > >> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
> > >> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> > >> > > Caused by: javax.wsdl.WSDLException: WSDLException:
> > >> >
> > >> > faultCode=PARSER_ERROR:
> > >> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
> > >> > > 't'
> > >> >
> > >> > (code
> > >> >
> > >> > > 116) excepted space, or '>' or "/>"
> > >> > >  at [row,col,system-id]:
> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> > >> >
> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> > >> >ava
> > >> >
> > >> >:226)
> > >> >:
> > >> > >    at
> > >> >
> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.ja
> > >> >va: 179)
> > >> >
> > >> > >    at
> > >> >
> > >> >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> > >> >a:9 1)
> > >> >
> > >> > >    ... 7 more
> > >> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected
> > >> > > character 't' (code 116) excepted space, or '>' or "/>"
> > >> > >  at [row,col,system-id]:
> > >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> > >> > >
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java
> > >> > >:64 8) at
> > >> >
> > >> >
> com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java
> > >> >:29 65)
> > >> >
> > >> > >    at
> > >> >
> > >> >
> com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.ja
> > >> >va: 2936)
> > >> >
> > >> > >    at
> > >> >
> > >> >
> com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:
> > >> >284 8)
> > >> >
> > >> > >    at
> > >> > >
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
> > >> > > at
> > >> > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:90
> > >> > >8) at
> > >> > >
> org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
> > >> > > at
> > >> > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:86
> > >> > >8) at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> at
> > >> >
> > >> >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> > >> >ava
> > >> >
> > >> >:217)
> > >> >:
> > >> > >    ... 9 more
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://www.dankulp.com/blog
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: Init Code

2009-12-04T15:47:45Z

Thanks Edwin, Thanks Daniel!!
Edwin Quita escribi�:
> you could also configure this declaratively in your service's impl
> bean declaration:
>
> 
>
> and inside your impl class implement the methods:
>
> public void start() {
>     //init code here..
> }
>
> public void stop() {
>     //shutdown code here...
> }
>
> On Fri, Dec 4, 2009 at 11:05 PM, Pawe� Lipka  wrote:
>   
>> Alternatively, not to tie yourself to JSR-250, you could put your code into
>> a plain 'void initialize() throws Exception' method and use Spring's bean
>> element init-method attribute to specify which method is to be invoked after
>> ur component is instantiated and wired to its dependencies.
>>
>>
>> Daniel Kulp wrote:
>>     
>>> In a method annotated with @PostConstruct?
>>>
>>> Dan
>>>
>>>
>>>
>>> On Fri December 4 2009 9:45:05 am Wadi Jalil Maluf wrote:
>>>       
>>>> Hi all,
>>>>       I'm building a web application with spring and apache cxf. I
>>>> would like to know where te best place to put initialization code is.
>>>> Thanks in advance,
>>>> Regards,
>>>> Wadi
>>>>
>>>>
>>>> __________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de
>>>>  firmas de virus 4660 (20091204) __________
>>>>
>>>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>>>
>>>> http://www.eset.com
>>>>
>>>>         
>> --
>> Pawe� Lipka
>> Senior IT Architect
>> AMG.net, A Bull Group Company
>> ul. ��kowa 29
>> 90-554 ��d�
>> tel.: (+48 42) 634 56 78
>> www.amg.net.pl
>>
>> Tre�� niniejszej wiadomo�ci mo�e by� poufna.
>> Je�eli nie jeste�cie Pa�stwo jej adresatem, to rozprowadzanie
>> lub wykorzystywanie zawartych tu informacji jest zabronione.
>>
>> This e-mail contains material that is confidential for the sole
>> use of the intended recipient. Any review, reliance or distribution
>> by others or forwarding without express permission is strictly
>> prohibited. If you are not the intended recipient, please contact
>> the sender and delete all copies.
>>
>>     
>
>
>
> __________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de virus
4660 (20091204) __________
>
> ESET NOD32 Antivirus ha comprobado este mensaje.
>
> http://www.eset.com
>
>
>   



__________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de virus 4660
(20091204) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

Re: interceptors - message

2009-12-04T15:40:23Z


The message object holds onto the exchange which holds onto both the in and 
out messages.   Thus, on the in chain, you can do 
msg.getExchange().getInMessage().get(...);

Alternatively, the Exchange also implements Map.   Thus, store it on the 
Exchange itself. 

Dan


On Thu November 19 2009 9:11:10 am Ernst Oberortner wrote:
> dear all!
> 
> i have a question regarding the data of the message which is transfered
> from the client to the service...
> 
> example:
> i have an interceptor in the client out-chain (doesn't matter yet in
> which phase) which puts some data into the message
> (by using the Message.put method)... now i want to read the data in the
> in-chain of the service host...
> 
> i haven't discovered yet any possibility how to implement this...
> 
> so please... can anybody help me by giving hints, examples, or links?
> 
> many thanks in advance!
> 
> best regards,
> ernst
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Initialization code, where?

2009-12-04T15:32:09Z

you could configure this declaratively in your service's impl
bean declaration:



and inside your impl class implement the methods:

public void start() {
   //init code here..
}

public void stop() {
   //shutdown code here...
}

HTH,
kits

On Fri, Dec 4, 2009 at 10:50 PM, Wadi Jalil Maluf  wrote:
> Hi all,
> � � I dont know where would be convenient and a good practice to put the
> initialization code that access the db with some services on a Apache CXF
> application.
> Any help would be appreciated,
> Regards,
> Wadi
>
>
> __________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas
> de virus 4660 (20091204) __________
>
> ESET NOD32 Antivirus ha comprobado este mensaje.
>
> http://www.eset.com
>
>
>

Re: Init Code

2009-12-04T15:28:45Z

you could also configure this declaratively in your service's impl
bean declaration:



and inside your impl class implement the methods:

public void start() {
    //init code here..
}

public void stop() {
    //shutdown code here...
}

On Fri, Dec 4, 2009 at 11:05 PM, Pawe� Lipka  wrote:
> Alternatively, not to tie yourself to JSR-250, you could put your code into
> a plain 'void initialize() throws Exception' method and use Spring's bean
> element init-method attribute to specify which method is to be invoked after
> ur component is instantiated and wired to its dependencies.
>
>
> Daniel Kulp wrote:
>>
>> In a method annotated with @PostConstruct?
>>
>> Dan
>>
>>
>>
>> On Fri December 4 2009 9:45:05 am Wadi Jalil Maluf wrote:
>>>
>>> Hi all,
>>> � � � I'm building a web application with spring and apache cxf. I
>>> would like to know where te best place to put initialization code is.
>>> Thanks in advance,
>>> Regards,
>>> Wadi
>>>
>>>
>>> __________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de
>>> �firmas de virus 4660 (20091204) __________
>>>
>>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>>
>>> http://www.eset.com
>>>
>>
>
>
> --
> Pawe� Lipka
> Senior IT Architect
> AMG.net, A Bull Group Company
> ul. ��kowa 29
> 90-554 ��d�
> tel.: (+48 42) 634 56 78
> www.amg.net.pl
>
> Tre�� niniejszej wiadomo�ci mo�e by� poufna.
> Je�eli nie jeste�cie Pa�stwo jej adresatem, to rozprowadzanie
> lub wykorzystywanie zawartych tu informacji jest zabronione.
>
> This e-mail contains material that is confidential for the sole
> use of the intended recipient. Any review, reliance or distribution
> by others or forwarding without express permission is strictly
> prohibited. If you are not the intended recipient, please contact
> the sender and delete all copies.
>

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T15:22:53Z

On Fri December 4 2009 10:13:52 am Benson Margulies wrote:
> Dan, I still wonder what is hitting him to begin with. I have an idea:
> capture the first 256 bytes of the returned WSDL and include it in the
> error. I'm musing about how to make the unit test for this.

It's probably the "Cannot find operation...." soap fault that would normally 
be generated when you do a get on the service address.

Dan



> On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:
> > On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> >> ah...when i added a ?wsdl to the URL it worked.  Why does CXF need to
> >> parse the WSDL at runtime?  I have already generated my code.
> >
> > That's pretty much what the JAX-WS spec requires.   There are things in
> > the WSDL that are not completely represented in code.   The actual
> > endpoint address is one of them.   Things like policies are another.
> >
> > In MOST cases, you can pass null for the wsdl location and then do a
> > service.createPort(...) call to create a port with your service URL and
> > it will work fine.    For straight soap calls with nothing fancy, the
> > generated code may be enough in that case.
> >
> > Dan
> >
> >> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> >
> > wrote:
> >> > CXF is trying to dynamically take the WSDL from your service, and
> >> > something is coming back (perhaps an error page) that is not much like
> >> > a WSDL. If you manually grab the ?wsdl URL what do you see?
> >> >
> >> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> >> >
> >> >  wrote:
> >> > > Hi all.  I am using Maven to generate a SOAP client from WSDL. I
> >> > > followed the web site example and some other examples i found on the
> >> > > net and my classes seemed to generate fine. As a side note i am
> >> > > using java version "1.6.0_16"
> >> > >
> >> > >        
> >> > >                org.apache.cxf
> >> > >                cxf-codegen-plugin
> >> > >                ${cxf.version}
> >> > >                
> >> > >                    
> >> > >                        generate-sources
> >> > >                        generate-sources
> >> > >                        
> >> > >                            true
> >> > >
> >> > > ${project.build.directory}/generated/cxf
> >> > >                            
> >> > >                                
> >> > >
> >> > > ${basedir}/src/main/wsdl/oasApi.wsdl
> >> > >                                    
> >> > >
> >> > >                                        -p
> >> > >
> >> > > com.xxx.soap 
> >> > >
> >> > >                                
> >> > >
> >> > >                            
> >> > >                        
> >> > >                        
> >> > >                            wsdl2java
> >> > >                        
> >> > >                    
> >> > >                
> >> > >            
> >> > >
> >> > >
> >> > >
> >> > > However, when i create a new xxxService Object as in...
> >> > >
> >> > > OaxApiService service = new OaxApiService( url,
> >> > > OaxApiService.SERVICE );
> >> > >
> >> > >
> >> > > i am getting the following exception....
> >> > >
> >> > >
> >> > >
> >> > > org.apache.cxf.service.factory.ServiceConstructionException: Failed
> >> > > to create service.
> >> > >    at
> >> >
> >> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >> >a:9 3)
> >> >
> >> > >    at
> >> > > org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:20
> >> > >5) at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> >> > > at
> >> >
> >> > org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderIm
> >> >pl. java:65)
> >> >
> >> > >    at javax.xml.ws.Service.(Service.java:56)
> >> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
> >> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
> >> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> >> > > Caused by: javax.wsdl.WSDLException: WSDLException:
> >> >
> >> > faultCode=PARSER_ERROR:
> >> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
> >> > > 't'
> >> >
> >> > (code
> >> >
> >> > > 116) excepted space, or '>' or "/>"
> >> > >  at [row,col,system-id]:
> >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >> >
> >> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >> >ava
> >> >
> >> >:226)
> >> >:
> >> > >    at
> >> >
> >> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.ja
> >> >va: 179)
> >> >
> >> > >    at
> >> >
> >> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.jav
> >> >a:9 1)
> >> >
> >> > >    ... 7 more
> >> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> >> > > character 't' (code 116) excepted space, or '>' or "/>"
> >> > >  at [row,col,system-id]:
> >> > > [2,41,"https://server.xxx.com/oasapi/OaxApi"] at
> >> > > com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java
> >> > >:64 8) at
> >> >
> >> > com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java
> >> >:29 65)
> >> >
> >> > >    at
> >> >
> >> > com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.ja
> >> >va: 2936)
> >> >
> >> > >    at
> >> >
> >> > com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:
> >> >284 8)
> >> >
> >> > >    at
> >> > > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
> >> > > at
> >> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:90
> >> > >8) at
> >> > > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
> >> > > at
> >> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:86
> >> > >8) at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755) at
> >> >
> >> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.j
> >> >ava
> >> >
> >> >:217)
> >> >:
> >> > >    ... 9 more
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T15:13:52Z

Dan, I still wonder what is hitting him to begin with. I have an idea:
capture the first 256 bytes of the returned WSDL and include it in the
error. I'm musing about how to make the unit test for this.

On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:
> On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
>> ah...when i added a ?wsdl to the URL it worked.  Why does CXF need to parse
>> the WSDL at runtime?  I have already generated my code.
>
> That's pretty much what the JAX-WS spec requires.   There are things in the
> WSDL that are not completely represented in code.   The actual endpoint
> address is one of them.   Things like policies are another.
>
> In MOST cases, you can pass null for the wsdl location and then do a
> service.createPort(...) call to create a port with your service URL and it
> will work fine.    For straight soap calls with nothing fancy, the generated
> code may be enough in that case.
>
> Dan
>
>
>
>
>>
>> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> wrote:
>> > CXF is trying to dynamically take the WSDL from your service, and
>> > something is coming back (perhaps an error page) that is not much like
>> > a WSDL. If you manually grab the ?wsdl URL what do you see?
>> >
>> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
>> >
>> >  wrote:
>> > > Hi all.  I am using Maven to generate a SOAP client from WSDL. I
>> > > followed the web site example and some other examples i found on the
>> > > net and my classes seemed to generate fine. As a side note i am using
>> > > java version "1.6.0_16"
>> > >
>> > >        
>> > >                org.apache.cxf
>> > >                cxf-codegen-plugin
>> > >                ${cxf.version}
>> > >                
>> > >                    
>> > >                        generate-sources
>> > >                        generate-sources
>> > >                        
>> > >                            true
>> > >
>> > > ${project.build.directory}/generated/cxf
>> > >                            
>> > >                                
>> > >
>> > > ${basedir}/src/main/wsdl/oasApi.wsdl
>> > >                                    
>> > >
>> > >                                        -p
>> > >
>> > > com.xxx.soap 
>> > >
>> > >                                
>> > >
>> > >                            
>> > >                        
>> > >                        
>> > >                            wsdl2java
>> > >                        
>> > >                    
>> > >                
>> > >            
>> > >
>> > >
>> > >
>> > > However, when i create a new xxxService Object as in...
>> > >
>> > > OaxApiService service = new OaxApiService( url, OaxApiService.SERVICE
>> > > );
>> > >
>> > >
>> > > i am getting the following exception....
>> > >
>> > >
>> > >
>> > > org.apache.cxf.service.factory.ServiceConstructionException: Failed to
>> > > create service.
>> > >    at
>> >
>> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
>> >3)
>> >
>> > >    at
>> > > org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:205)
>> > >    at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
>> > >    at
>> >
>> > org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.
>> >java:65)
>> >
>> > >    at javax.xml.ws.Service.(Service.java:56)
>> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
>> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
>> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
>> > > Caused by: javax.wsdl.WSDLException: WSDLException:
>> >
>> > faultCode=PARSER_ERROR:
>> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 't'
>> >
>> > (code
>> >
>> > > 116) excepted space, or '>' or "/>"
>> > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi"]
>> > >    at
>> >
>> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
>> >:226)
>> >
>> > >    at
>> >
>> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:
>> >179)
>> >
>> > >    at
>> >
>> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
>> >1)
>> >
>> > >    ... 7 more
>> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> > > character 't' (code 116) excepted space, or '>' or "/>"
>> > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi"]
>> > >    at
>> > > com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:64
>> > >8) at
>> >
>> > com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:29
>> >65)
>> >
>> > >    at
>> >
>> > com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:
>> >2936)
>> >
>> > >    at
>> >
>> > com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:284
>> >8)
>> >
>> > >    at
>> > > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019) at
>> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:908)
>> > >    at
>> > > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826) at
>> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
>> > >    at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
>> > >    at
>> >
>> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
>> >:217)
>> >
>> > >    ... 9 more
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: Init Code

2009-12-04T15:05:32Z

Alternatively, not to tie yourself to JSR-250, you could put your code 
into a plain 'void initialize() throws Exception' method and use 
Spring's bean element init-method attribute to specify which method is 
to be invoked after ur component is instantiated and wired to its 
dependencies.

Daniel Kulp wrote:
> 
> In a method annotated with @PostConstruct?
> 
> Dan
> 
> 
> 
> On Fri December 4 2009 9:45:05 am Wadi Jalil Maluf wrote:
>> Hi all,
>>        I'm building a web application with spring and apache cxf. I
>> would like to know where te best place to put initialization code is.
>> Thanks in advance,
>> Regards,
>> Wadi
>>
>>
>> __________ Información de ESET NOD32 Antivirus, versión de la base de
>>  firmas de virus 4660 (20091204) __________
>>
>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>
>> http://www.eset.com
>>
> 

-- 
Paweł Lipka
Senior IT Architect
AMG.net, A Bull Group Company
ul. Łąkowa 29
90-554 Łódź
tel.: (+48 42) 634 56 78
www.amg.net.pl

Treść niniejszej wiadomości może być poufna.
Jeżeli nie jesteście Państwo jej adresatem, to rozprowadzanie
lub wykorzystywanie zawartych tu informacji jest zabronione.

This e-mail contains material that is confidential for the sole
use of the intended recipient. Any review, reliance or distribution
by others or forwarding without express permission is strictly
prohibited. If you are not the intended recipient, please contact
the sender and delete all copies.

Re: java.lang.VerifyError: Cannot inherit from final class

2009-12-04T15:02:56Z


Not really sure.   Is the javac version appropriate (java 5 or higher?).

I really don't know what would cause it.    Maybe an older version of jaxb in 
the tomcat shared/lib?       Or possibly jaxb is in the endorsed area?   I'm 
really not sure.

Dan


On Fri December 4 2009 6:04:45 am Shahul Hameed wrote:
> Hi Dan
> 
> I am getting this error on our dev environment however my local eclipse
>  works fine :
> 
>  SEVERE org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient
>  Could not compile java files for
>  http://dev-andregws/regWS/services/soap/authenticatedSession.wsdl.
> 
> [ERROR] IOException during exec() of compiler "javac". Check your path
>  environment variable.
> 
> Caused by: javax.xml.bind.JAXBException: "uk.co.and.register.schemas"
>  doesnt contain ObjectFactory.class or jaxb.index
> 
> I did confirm that the javac is on the path
> 
> $which javac
> $/usr/bin/javac
> 
>  echo $PATH
> /usr/bin:/usr/sfw/bin:/usr/local/bin:/export/home/hyperlocal/bin$
> 
> So you can see that /usr/bin is on the path ..
> 
> Another strange thing is  this error occured on my local machine and to fix
>  this I had to create a new Tomcat instance (deleting all temp, work dirs
>  didnt work) and all worked, but I cant do that on the dev or prod
>  environment.
> 
> Any ideas what may be wrong.
> 
> Best Regards
> 
> Shahul Hameed
> 
> > From: dkulp@apache.org
> > To: users@cxf.apache.org
> > Subject: Re: java.lang.VerifyError: Cannot inherit from final class
> > Date: Thu, 3 Dec 2009 10:52:09 -0500
> > CC: shahul@hotmail.co.uk
> >
> > On Thu December 3 2009 4:09:31 am Shahul Hameed wrote:
> > > Hi Dan
> > >
> > > You were right .. I was getting an old version of DynamicClientFactory
> > > from one of the jars GroovyWS-all.jar
> > >
> > > I removed it from the class path and it worked.
> > >
> > > Thanks very much for your help.
> > >
> > > Also do I need to have the same version of CXF (2.1.4) at the cleint
> > > side coz the team which develops the webservices uses 2.1.4
> >
> > You shouldn't.   That's one of the nice things about soap.   Nothing
> > about the software on either end is really exposed on the wire.   :-)
> >
> > Dan
> >
> > > Best Regards
> > >
> > > Shahul Hameed
> > >
> > > > From: dkulp@apache.org
> > > > To: users@cxf.apache.org
> > > > Subject: Re: java.lang.VerifyError: Cannot inherit from final class
> > > > Date: Wed, 2 Dec 2009 15:19:29 -0500
> > > > CC: shahul@hotmail.co.uk
> > > >
> > > >
> > > > Check for other versions of:
> > > > org.apache.cxf.endpoint.dynamic.DynamicClientFactory
> > > >
> > > > The OLD OLD versions of DynamicClientFactory were final.   When the
> > > > JaxWsDynamicClientFactory class was added, the final restriction was
> > > > taken off.   Thus, it kind of sounds like you are getting a new
> > > > JaxWsDynamicClientFactory, but somehow getting an old
> > > > DynamicClientFactory.
> > > >
> > > > That all said, consider upgrading everything to a newer version of
> > > > CXF. 2.1.7 or 2.2.5.   :-)
> > > >
> > > > Dan
> > > >
> > > > On Wed December 2 2009 8:18:57 am Shahul Hameed wrote:
> > > > > Hi
> > > > >
> > > > > I am getting the following exception when my application starts up
> > > > >
> > > > > Caused by: java.lang.VerifyError: Cannot inherit from final class
> > > > >         at java.lang.ClassLoader.defineClass1(Native Method)
> > > > >         at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
> > > > >         at
> > > > > 
> > > > > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:
> > > > >12 4) at
> > > > > 
> > > > > org.apache.catalina.loader.WebappClassLoader.findClassInternal(Weba
> > > > >pp ClassLoader.java:1817)
> > > > >         at
> > > > > 
> > > > > org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassL
> > > > >oa der.java:872)
> > > > >         at
> > > > > 
> > > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassL
> > > > >oa der.java:1325)
> > > > >         at
> > > > > 
> > > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassL
> > > > >oa der.java:1204)
> > > > >         at
> > > > > java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at
> > > > > 
> > > > > uk.co.and.commons.services.soap.AbstractSOAPService.afterProperties
> > > > >Se t(AbstractSOAPService.java:231)
> > > > >         at
> > > > > 
> > > > > uk.co.and.tin.service.RegistrationService.afterPropertiesSet(Regist
> > > > >ra tionService.java:46)
> > > > >         at
> > > > > 
> > > > > org.springframework.beans.factory.support.AbstractAutowireCapableBe
> > > > >an
> > > > >
> > > > > Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1
> > > > >369) at
> > > > > org.springframework.beans.factory.support.AbstractAutowireCapableBe
> > > > >an
> > > > > Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335
> > > > >) ... 39 more
> > > > >
> > > > >
> > > > > AbstractSOAPService.java:231 (where this exception is thrown
> > > > > )contains this line :
> > > > >
> > > > > JaxWsDynamicClientFactory factory =
> > > > >  JaxWsDynamicClientFactory.newInstance();
> > > > >
> > > > > I am using dynamic client to make web service calls ..
> > > > >
> > > > > I
> > > > > have checked if there are any references to the cxf-bundle-2.1.4
> > > > > jar but there is only one and thats in the WEB-INF lib directory.
> > > > >
> > > > > Any help would be much appreciated.
> > > > >
> > > > >
> > > > > Best Regards
> > > > >
> > > > > Shahul Hameed
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: Init Code

2009-12-04T14:54:06Z



In a method annotated with @PostConstruct?

Dan



On Fri December 4 2009 9:45:05 am Wadi Jalil Maluf wrote:
> Hi all,
>        I'm building a web application with spring and apache cxf. I
> would like to know where te best place to put initialization code is.
> Thanks in advance,
> Regards,
> Wadi
> 
> 
> __________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de
>  firmas de virus 4660 (20091204) __________
> 
> ESET NOD32 Antivirus ha comprobado este mensaje.
> 
> http://www.eset.com
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Initialization code, where?

2009-12-04T14:50:34Z

Hi all,
      I dont know where would be convenient and a good practice to put 
the initialization code that access the db with some services on a 
Apache CXF application.
Any help would be appreciated,
Regards,
Wadi


__________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de virus 4660
(20091204) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

Init Code

2009-12-04T14:45:05Z

Hi all,
       I'm building a web application with spring and apache cxf. I 
would like to know where te best place to put initialization code is.
Thanks in advance,
Regards,
Wadi


__________ Informaci�n de ESET NOD32 Antivirus, versi�n de la base de firmas de virus 4660
(20091204) __________

ESET NOD32 Antivirus ha comprobado este mensaje.

http://www.eset.com

Re: Exception in Soap Dynamic Client

2009-12-04T14:32:42Z


This is due to an old version of Xerces found on the classpath.  Check the 
xerces jars and such to make sure they are recent.  (or remove them entirely 
and use the parsers built into the JDK).

Dan


On Fri December 4 2009 6:55:55 am Walter Mour�o wrote:
> Hi folks,
> I've got the following exception when executing a remote method (XFire
>  1.2.5 based server) :
> 
> Exception in thread "main" java.lang.AbstractMethodError:
> org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lan
> g/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; at
>  org.apache.cxf.staxutils.StaxUtils.addLocation(StaxUtils.java:941) at
>  org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:799) at
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
>     at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
>     at
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:2
> 17) at
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:16
> 1) at
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:67)
>     at org.apache.cxf.endpoint.ClientImpl.(ClientImpl.java:148)
>     at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> ientFactory.java:253) at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> ientFactory.java:231) at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> ientFactory.java:224) at
> org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicCl
> ientFactory.java:159) at
>  com.wim.ita.testemaven.App.testeTestaIPFromFCHT(App.java:75) at
>  com.wim.ita.testemaven.App.main(App.java:116)
> 
> The invocation code:
> 
>             final JaxWsDynamicClientFactory dcf =
> JaxWsDynamicClientFactory.newInstance();
>             final Client client = dcf.createClient(new URL("
> http://localhost:8080/ioserver-1.0/services/MMAService?wsdl"));
>             results = client.invoke("ListarBacias", (Object[]) null);
> 
> The WSDL is attached (and pasted after the message).
> 
> Could you please help me ?
> 
> Thanks in advance,
> 
> Walter Mour�o
> http://waltermourao.com.br
> http://arcadian.com.br
> http://oriens.com.br
> 
> 
> WSDS:
> 
>   targetNamespace="http://service.webserver.exemplo.ita.br/"
>  xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="
>  http://service.webserver.exemplo.ita.br/" xmlns:wsdl="
> http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="
> http://www.w3.org/2001/XMLSchema" xmlns:soap11="
> http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap="
> http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc11="
> http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="
> http://www.w3.org/2003/05/soap-envelope">
>   
>  attributeFormDefault="qualified" elementFormDefault="qualified"
> targetNamespace="http://service.webserver.exemplo.ita.br/">
> 
> 
> 
>  type="xsd:string"/>
> 
> 
> 
> 
> 
> 
>  type="xsd:string"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  type="xsd:string"/>
> 
> 
> 
> 
>   
>   
>     
>     
>   
>   
>     
>     
>   
>   
>     
>     
>   
>   
>     
>     
>   
>   
>     
>       
>     
>        message="tns:CriarBaciaResponse">
>     
>     
>     
>        message="tns:ListarBaciasRequest">
>     
>        message="tns:ListarBaciasResponse">
>     
>     
>   
>   
>     
>     
>       
>       
>         
>       
>       
>         
>       
>     
>     
>       
>       
>         
>       
>       
>         
>       
>     
>   
>   
>      binding="tns:MMAServiceHttpBinding">
>       
>     
>   
> 
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T14:32:29Z

thanks for the help. greatly appreciated


On Fri, Dec 4, 2009 at 9:31 AM, Daniel Kulp  wrote:

> On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> > ah...when i added a ?wsdl to the URL it worked.  Why does CXF need to
> parse
> > the WSDL at runtime?  I have already generated my code.
>
> That's pretty much what the JAX-WS spec requires.   There are things in the
> WSDL that are not completely represented in code.   The actual endpoint
> address is one of them.   Things like policies are another.
>
> In MOST cases, you can pass null for the wsdl location and then do a
> service.createPort(...) call to create a port with your service URL and it
> will work fine.    For straight soap calls with nothing fancy, the
> generated
> code may be enough in that case.
>
> Dan
>
>
>
>
> >
> > On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies
> wrote:
> > > CXF is trying to dynamically take the WSDL from your service, and
> > > something is coming back (perhaps an error page) that is not much like
> > > a WSDL. If you manually grab the ?wsdl URL what do you see?
> > >
> > > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> > >
> > >  wrote:
> > > > Hi all.  I am using Maven to generate a SOAP client from WSDL. I
> > > > followed the web site example and some other examples i found on the
> > > > net and my classes seemed to generate fine. As a side note i am using
> > > > java version "1.6.0_16"
> > > >
> > > >        
> > > >                org.apache.cxf
> > > >                cxf-codegen-plugin
> > > >                ${cxf.version}
> > > >                
> > > >                    
> > > >                        generate-sources
> > > >                        generate-sources
> > > >                        
> > > >                            true
> > > >
> > > > ${project.build.directory}/generated/cxf
> > > >                            
> > > >                                
> > > >
> > > > ${basedir}/src/main/wsdl/oasApi.wsdl
> > > >                                    
> > > >
> > > >                                        -p
> > > >
> > > > com.xxx.soap 
> > > >
> > > >                                
> > > >
> > > >                            
> > > >                        
> > > >                        
> > > >                            wsdl2java
> > > >                        
> > > >                    
> > > >                
> > > >            
> > > >
> > > >
> > > >
> > > > However, when i create a new xxxService Object as in...
> > > >
> > > > OaxApiService service = new OaxApiService( url, OaxApiService.SERVICE
> > > > );
> > > >
> > > >
> > > > i am getting the following exception....
> > > >
> > > >
> > > >
> > > > org.apache.cxf.service.factory.ServiceConstructionException: Failed
> to
> > > > create service.
> > > >    at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
> > >3)
> > >
> > > >    at
> > > >
> org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:205)
> > > >    at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> > > >    at
> > >
> > >
> org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.
> > >java:65)
> > >
> > > >    at javax.xml.ws.Service.(Service.java:56)
> > > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
> > > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
> > > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> > > > Caused by: javax.wsdl.WSDLException: WSDLException:
> > >
> > > faultCode=PARSER_ERROR:
> > > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
> 't'
> > >
> > > (code
> > >
> > > > 116) excepted space, or '>' or "/>"
> > > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi
> "]
> > > >    at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> > >:226)
> > >
> > > >    at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:
> > >179)
> > >
> > > >    at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
> > >1)
> > >
> > > >    ... 7 more
> > > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> > > > character 't' (code 116) excepted space, or '>' or "/>"
> > > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi
> "]
> > > >    at
> > > >
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:64
> > > >8) at
> > >
> > >
> com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:29
> > >65)
> > >
> > > >    at
> > >
> > >
> com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:
> > >2936)
> > >
> > > >    at
> > >
> > >
> com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:284
> > >8)
> > >
> > > >    at
> > > > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
> at
> > > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:908)
> > > >    at
> > > > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826)
> at
> > > >
> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
> > > >    at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> > > >    at
> > >
> > >
> org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> > >:217)
> > >
> > > >    ... 9 more
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>

Re: CXF 2.2.5 SOAP to Java problem

2009-12-04T14:31:03Z

On Fri December 4 2009 8:43:25 am Nathaniel Auvil wrote:
> ah...when i added a ?wsdl to the URL it worked.  Why does CXF need to parse
> the WSDL at runtime?  I have already generated my code.

That's pretty much what the JAX-WS spec requires.   There are things in the 
WSDL that are not completely represented in code.   The actual endpoint 
address is one of them.   Things like policies are another.

In MOST cases, you can pass null for the wsdl location and then do a 
service.createPort(...) call to create a port with your service URL and it 
will work fine.    For straight soap calls with nothing fancy, the generated 
code may be enough in that case.

Dan




> 
> On Fri, Dec 4, 2009 at 8:38 AM, Benson Margulies 
wrote:
> > CXF is trying to dynamically take the WSDL from your service, and
> > something is coming back (perhaps an error page) that is not much like
> > a WSDL. If you manually grab the ?wsdl URL what do you see?
> >
> > On Fri, Dec 4, 2009 at 8:09 AM, Nathaniel Auvil
> >
> >  wrote:
> > > Hi all.  I am using Maven to generate a SOAP client from WSDL. I
> > > followed the web site example and some other examples i found on the
> > > net and my classes seemed to generate fine. As a side note i am using
> > > java version "1.6.0_16"
> > >
> > >        
> > >                org.apache.cxf
> > >                cxf-codegen-plugin
> > >                ${cxf.version}
> > >                
> > >                    
> > >                        generate-sources
> > >                        generate-sources
> > >                        
> > >                            true
> > >
> > > ${project.build.directory}/generated/cxf
> > >                            
> > >                                
> > >
> > > ${basedir}/src/main/wsdl/oasApi.wsdl
> > >                                    
> > >
> > >                                        -p
> > >                                       
> > > com.xxx.soap 
> > >
> > >                                
> > >
> > >                            
> > >                        
> > >                        
> > >                            wsdl2java
> > >                        
> > >                    
> > >                
> > >            
> > >
> > >
> > >
> > > However, when i create a new xxxService Object as in...
> > >
> > > OaxApiService service = new OaxApiService( url, OaxApiService.SERVICE
> > > );
> > >
> > >
> > > i am getting the following exception....
> > >
> > >
> > >
> > > org.apache.cxf.service.factory.ServiceConstructionException: Failed to
> > > create service.
> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
> >3)
> >
> > >    at
> > > org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:205)
> > >    at org.apache.cxf.jaxws.ServiceImpl.(ServiceImpl.java:148)
> > >    at
> >
> > org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.
> >java:65)
> >
> > >    at javax.xml.ws.Service.(Service.java:56)
> > >    at com.xxx.soap.OaxApiService.(OaxApiService.java:48)
> > >    at com.xxx.OaxClient.invoke(OaxClient.java:97)
> > >    at com.xxx.oas.OaxClient.main(OaxClient.java:32)
> > > Caused by: javax.wsdl.WSDLException: WSDLException:
> >
> > faultCode=PARSER_ERROR:
> > > com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 't'
> >
> > (code
> >
> > > 116) excepted space, or '>' or "/>"
> > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi"]
> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> >:226)
> >
> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:
> >179)
> >
> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLServiceFactory.(WSDLServiceFactory.java:9
> >1)
> >
> > >    ... 7 more
> > > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> > > character 't' (code 116) excepted space, or '>' or "/>"
> > >  at [row,col,system-id]: [2,41,"https://server.xxx.com/oasapi/OaxApi"]
> > >    at
> > > com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:64
> > >8) at
> >
> > com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:29
> >65)
> >
> > >    at
> >
> > com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:
> >2936)
> >
> > >    at
> >
> > com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:284
> >8)
> >
> > >    at
> > > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019) at
> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:908)
> > >    at
> > > org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:826) at
> > > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:868)
> > >    at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:755)
> > >    at
> >
> > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java
> >:217)
> >
> > >    ... 9 more
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog