You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Steve Cohen <sc...@javactivity.org> on 2008/09/29 22:17:05 UTC
Web Service requires secure header - how to generate with Axis?
I am trying to generate java Client code to access a web service from a
WSDL using axis 1.4. Documentation that comes with the WSDL expects me
to generate packets with SOAP headers that look something like this.
Is this a well-known security scheme that Axis can be easily configured
to generate or must it be coded by hand?
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
1.0.xsd">
<soap:Header>
<wsa:Action></wsa:Action>
<wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
<wsa:ReplyTo>
<wsa:Address>
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
</wsa:Address>
</wsa:ReplyTo>
<wsa:To>https://{url:443}</wsa:To>
<wsse:Security soap:mustUnderstand="1">
<wsse:UsernameToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
xxxx-xxxxxxxxxxxx">
<wsse:Username>[username]</wsse:Username>
<wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
token-profile-1.0#PasswordText">
[password]
</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by keith chapman <ke...@gmail.com>.
Hi,
Looks like the axis2.xml that your using has the JMS transport turned on.
You can dissable it by commenting out the JMS transport (Section that starts
with <transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">) from the axis2.xml.
Thanks,
Keith.
On Thu, Oct 2, 2008 at 2:11 AM, Steve Cohen <sc...@javactivity.org> wrote:
> On further investigation, I find that client.03 fails in the sample with
> the same error (java.lang.NoClassDefFoundError: javax/jms/BytesMessage).
> Before I got to that point, I also had to modify the build.xml file in the
> samples/basic directory changing
>
> <property name="addressing.mar" value="addressing-1.1.mar"/>
> to
> <property name="addressing.mar" value="addressing-1.4.mar"/>
>
> since that is what was installed with axis2-1.4.
>
> Is rampart written for axis2-1.3 rather than 1.4 and would I possibly be
> better off using that platform?
>
>
>
> Steve Cohen wrote:
>
>> The light dawns on this dinosaur's brain. Slowly, slowly. But it dawns.
>>
>> I think I am not supposed to use in my client code (or even look at :-))
>> these wretched classes that WSDL2Java created. Leave these classes for the
>> audience they were designed for, that is, for axis itself. Instead, in my
>> client code, use the OMElement methods as in the sample, to build my data
>> elements from element names defined in the WSDL.
>> That produces a readable xml fragment. This is odd to me but workable.
>>
>> However, I am still not out of the woods yet. Though it produces a viable
>> Soap Body, my SoapHeader was not being produced. This is because the
>> configuration process is not quite so simple as described. This line
>>
>> ConfigurationContext ctx =
>> ConfigurationContextFactory.createConfigurationContextFromFileSystem(args[1],
>> args[1] + "/conf/axis2.xml");
>>
>> is failing for me, even when I modify the parameters to fit my system,
>> because of this error:
>>
>> Exception in thread "main"
>> org.apache.axis2.deployment.DeploymentException: javax/jms/BytesMessage
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:663)
>>
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:119)
>>
>> at
>> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641)
>>
>> at
>> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
>>
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:68)
>>
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)
>>
>> ...
>> Caused by: java.lang.NoClassDefFoundError: javax/jms/BytesMessage
>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
>> at java.lang.Class.getConstructor0(Class.java:2671)
>> at java.lang.Class.newInstance0(Class.java:321)
>> at java.lang.Class.newInstance(Class.java:303)
>> at
>> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:648)
>>
>> ... 6 more
>>
>> This is a little surprising - Axis is expecting a JMS support library to
>> be loaded on the runtime classpath? Perhaps a valid assumption in an
>> application container - but how about a standalone client? What jar must I
>> place on my runtime classpath to resolve this dependency?
>>
>>
>>
>>
>>
>>
>> Steve Cohen wrote:
>>
>>> Thanks again, Mary.
>>>
>>> However, I am still in no-joy land. This is because of the absolutely
>>> wretched code that WSDL2Java generated for me from this WSDL. (See
>>> http://marc.info/?l=axis-user&m=122279472601179&w=2) or
>>> to recapitulate that thread, I got the WSDL here
>>>
>>> https://duoshare.com/dsWS/services/PostML/wsdl
>>>
>>> and processed it with Java2WSDL using these options
>>>
>>> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion
>>> 1.5 -uri {my wsdl}
>>>
>>>
>>> which created a mess of compilable but ungodly code. Therefore what
>>> should be simple setters and getters are instead gnarly thickets of
>>> BlahBlahBlah_type1 each of which in turn has a setter for
>>> BlahBlahBlah_type0, all to stick a stinking string parameter into an XML
>>> packet.
>>>
>>> Therefore I am unable to do the simple kinds of things in sample03 and
>>> must instead learn this whole axiom object model in order to work with this
>>> code.
>>>
>>> Or something. I don't know what.
>>>
>>> I think I need a WSDL2Java expert to tell me how to generate better code
>>> from this WSDL.
>>>
>>>
>>>
>>> Mary Thompson wrote:
>>>
>>>> Steve,
>>>> axis2.xml will be read by the appropriate library method if it appears
>>>> on your class path, or is specified using a -Daxis2.xml=<pathname> Java
>>>> option when you run the client, or set by a
>>>> System.setProperty("axis2.xml",<pathname> ) call in your program. In my
>>>> experience, the pathname needed to be relative to the classpath.
>>>>
>>>> The axis2.xml sections for rampart are the <module ref="rampart"> line
>>>> and the OutflowSecurity and InflowSecurity sections, specifying the security
>>>> properties of the request and response messages.
>>>>
>>>> I think that samples/basic/sample03/client-axis.xml would give you want
>>>> you want for the security heading. Since the message is not signed you don't
>>>> need the properties or keystore files.
>>>>
>>>> I'm not sure how you would set the user interactively. You can probably
>>>> write a PWCBHandler that prompts for a username and password, and then add
>>>> them to the header.
>>>>
>>>> As for the addressing part of the message I would guess that the
>>>> addressing module handles that, but I have no experience with it.
>>>>
>>>> Hope this is a bit of help
>>>>
>>>> Mary
>>>>
>>>> Steve Cohen wrote:
>>>>
>>>>> Okay, thanks Mary.
>>>>>
>>>>> On your suggestion and others I have rethought and begun switching to
>>>>> Axis2 so that I might use Rampart. I am looking at the samples and they
>>>>> pose a question I want to understand.
>>>>>
>>>>> That is, the use of client.axis2.xml as in the samples.
>>>>>
>>>>> WSDL2java did not generate this file for me and I'm not sure what is
>>>>> going to cause this file to be read.
>>>>>
>>>>> Can you explain how this works? Once I get past this, I think I will
>>>>> be on my way.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Steve
>>>>>
>>>>>
>>>>> Mary Thompson wrote:
>>>>>
>>>>>> If you mean axis2 1.4, the Rampart module will do that for you. The
>>>>>> Axis pages link to some documentation and to the rampart 1.3 module. Go to
>>>>>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart
>>>>>> 1.4 and more documentation.
>>>>>>
>>>>>> After you have read the overviews, look at the rampart/samples code. I
>>>>>> think samples/basic/sample03 may do what you want.
>>>>>>
>>>>>> Mary
>>>>>>
>>>>>> Steve Cohen wrote:
>>>>>>
>>>>>>> I am trying to generate java Client code to access a web service from
>>>>>>> a WSDL using axis 1.4. Documentation that comes with the WSDL expects me to
>>>>>>> generate packets with SOAP headers that look something like this.
>>>>>>> q
>>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
On further investigation, I find that client.03 fails in the sample with
the same error (java.lang.NoClassDefFoundError:
javax/jms/BytesMessage). Before I got to that point, I also had to
modify the build.xml file in the samples/basic directory changing
<property name="addressing.mar" value="addressing-1.1.mar"/>
to
<property name="addressing.mar" value="addressing-1.4.mar"/>
since that is what was installed with axis2-1.4.
Is rampart written for axis2-1.3 rather than 1.4 and would I possibly be
better off using that platform?
Steve Cohen wrote:
> The light dawns on this dinosaur's brain. Slowly, slowly. But it dawns.
>
> I think I am not supposed to use in my client code (or even look at
> :-)) these wretched classes that WSDL2Java created. Leave these
> classes for the audience they were designed for, that is, for axis
> itself. Instead, in my client code, use the OMElement methods as in
> the sample, to build my data elements from element names defined in
> the WSDL.
> That produces a readable xml fragment. This is odd to me but workable.
>
> However, I am still not out of the woods yet. Though it produces a
> viable Soap Body, my SoapHeader was not being produced. This is
> because the configuration process is not quite so simple as
> described. This line
>
> ConfigurationContext ctx =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(args[1],
> args[1] + "/conf/axis2.xml");
>
> is failing for me, even when I modify the parameters to fit my system,
> because of this error:
>
> Exception in thread "main"
> org.apache.axis2.deployment.DeploymentException: javax/jms/BytesMessage
> at
> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:663)
>
> at
> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:119)
>
> at
> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641)
>
> at
> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
>
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:68)
>
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)
>
> ...
> Caused by: java.lang.NoClassDefFoundError: javax/jms/BytesMessage
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
> at java.lang.Class.getConstructor0(Class.java:2671)
> at java.lang.Class.newInstance0(Class.java:321)
> at java.lang.Class.newInstance(Class.java:303)
> at
> org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:648)
>
> ... 6 more
>
> This is a little surprising - Axis is expecting a JMS support library
> to be loaded on the runtime classpath? Perhaps a valid assumption in
> an application container - but how about a standalone client? What
> jar must I place on my runtime classpath to resolve this dependency?
>
>
>
>
>
>
> Steve Cohen wrote:
>> Thanks again, Mary.
>>
>> However, I am still in no-joy land. This is because of the
>> absolutely wretched code that WSDL2Java generated for me from this
>> WSDL. (See http://marc.info/?l=axis-user&m=122279472601179&w=2) or
>> to recapitulate that thread, I got the WSDL here
>>
>> https://duoshare.com/dsWS/services/PostML/wsdl
>>
>> and processed it with Java2WSDL using these options
>>
>> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or
>> -Ejavaversion 1.5 -uri {my wsdl}
>>
>>
>> which created a mess of compilable but ungodly code. Therefore what
>> should be simple setters and getters are instead gnarly thickets of
>> BlahBlahBlah_type1 each of which in turn has a setter for
>> BlahBlahBlah_type0, all to stick a stinking string parameter into an
>> XML packet.
>>
>> Therefore I am unable to do the simple kinds of things in sample03
>> and must instead learn this whole axiom object model in order to work
>> with this code.
>>
>> Or something. I don't know what.
>>
>> I think I need a WSDL2Java expert to tell me how to generate better
>> code from this WSDL.
>>
>>
>>
>> Mary Thompson wrote:
>>> Steve,
>>> axis2.xml will be read by the appropriate library method if it
>>> appears on your class path, or is specified using a
>>> -Daxis2.xml=<pathname> Java option when you run the client, or set
>>> by a System.setProperty("axis2.xml",<pathname> ) call in your
>>> program. In my experience, the pathname needed to be relative to
>>> the classpath.
>>>
>>> The axis2.xml sections for rampart are the <module ref="rampart">
>>> line and the OutflowSecurity and InflowSecurity sections, specifying
>>> the security properties of the request and response messages.
>>>
>>> I think that samples/basic/sample03/client-axis.xml would give you
>>> want you want for the security heading. Since the message is not
>>> signed you don't need the properties or keystore files.
>>>
>>> I'm not sure how you would set the user interactively. You can
>>> probably write a PWCBHandler that prompts for a username and
>>> password, and then add them to the header.
>>>
>>> As for the addressing part of the message I would guess that the
>>> addressing module handles that, but I have no experience with it.
>>>
>>> Hope this is a bit of help
>>>
>>> Mary
>>>
>>> Steve Cohen wrote:
>>>> Okay, thanks Mary.
>>>>
>>>> On your suggestion and others I have rethought and begun switching
>>>> to Axis2 so that I might use Rampart. I am looking at the samples
>>>> and they pose a question I want to understand.
>>>>
>>>> That is, the use of client.axis2.xml as in the samples.
>>>>
>>>> WSDL2java did not generate this file for me and I'm not sure what
>>>> is going to cause this file to be read.
>>>>
>>>> Can you explain how this works? Once I get past this, I think I
>>>> will be on my way.
>>>>
>>>> Thanks.
>>>>
>>>> Steve
>>>>
>>>>
>>>> Mary Thompson wrote:
>>>>> If you mean axis2 1.4, the Rampart module will do that for you.
>>>>> The Axis pages link to some documentation and to the rampart 1.3
>>>>> module. Go to
>>>>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart
>>>>> 1.4 and more documentation.
>>>>>
>>>>> After you have read the overviews, look at the rampart/samples
>>>>> code. I think samples/basic/sample03 may do what you want.
>>>>>
>>>>> Mary
>>>>>
>>>>> Steve Cohen wrote:
>>>>>> I am trying to generate java Client code to access a web service
>>>>>> from a WSDL using axis 1.4. Documentation that comes with the
>>>>>> WSDL expects me to generate packets with SOAP headers that look
>>>>>> something like this.
>>>>>> q
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
The light dawns on this dinosaur's brain. Slowly, slowly. But it dawns.
I think I am not supposed to use in my client code (or even look at :-))
these wretched classes that WSDL2Java created. Leave these classes for
the audience they were designed for, that is, for axis itself. Instead,
in my client code, use the OMElement methods as in the sample, to build
my data elements from element names defined in the WSDL.
That produces a readable xml fragment. This is odd to me but workable.
However, I am still not out of the woods yet. Though it produces a
viable Soap Body, my SoapHeader was not being produced. This is because
the configuration process is not quite so simple as described. This line
ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(args[1],
args[1] + "/conf/axis2.xml");
is failing for me, even when I modify the parameters to fit my system,
because of this error:
Exception in thread "main"
org.apache.axis2.deployment.DeploymentException: javax/jms/BytesMessage
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:663)
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:119)
at
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641)
at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:68)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)
...
Caused by: java.lang.NoClassDefFoundError: javax/jms/BytesMessage
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at java.lang.Class.newInstance0(Class.java:321)
at java.lang.Class.newInstance(Class.java:303)
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:648)
... 6 more
This is a little surprising - Axis is expecting a JMS support library to
be loaded on the runtime classpath? Perhaps a valid assumption in an
application container - but how about a standalone client? What jar
must I place on my runtime classpath to resolve this dependency?
Steve Cohen wrote:
> Thanks again, Mary.
>
> However, I am still in no-joy land. This is because of the absolutely
> wretched code that WSDL2Java generated for me from this WSDL. (See
> http://marc.info/?l=axis-user&m=122279472601179&w=2) or
> to recapitulate that thread, I got the WSDL here
>
> https://duoshare.com/dsWS/services/PostML/wsdl
>
> and processed it with Java2WSDL using these options
>
> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or
> -Ejavaversion 1.5 -uri {my wsdl}
>
>
> which created a mess of compilable but ungodly code. Therefore what
> should be simple setters and getters are instead gnarly thickets of
> BlahBlahBlah_type1 each of which in turn has a setter for
> BlahBlahBlah_type0, all to stick a stinking string parameter into an
> XML packet.
>
> Therefore I am unable to do the simple kinds of things in sample03 and
> must instead learn this whole axiom object model in order to work with
> this code.
>
> Or something. I don't know what.
>
> I think I need a WSDL2Java expert to tell me how to generate better
> code from this WSDL.
>
>
>
> Mary Thompson wrote:
>> Steve,
>> axis2.xml will be read by the appropriate library method if it
>> appears on your class path, or is specified using a
>> -Daxis2.xml=<pathname> Java option when you run the client, or set by
>> a System.setProperty("axis2.xml",<pathname> ) call in your program.
>> In my experience, the pathname needed to be relative to the classpath.
>>
>> The axis2.xml sections for rampart are the <module ref="rampart">
>> line and the OutflowSecurity and InflowSecurity sections, specifying
>> the security properties of the request and response messages.
>>
>> I think that samples/basic/sample03/client-axis.xml would give you
>> want you want for the security heading. Since the message is not
>> signed you don't need the properties or keystore files.
>>
>> I'm not sure how you would set the user interactively. You can
>> probably write a PWCBHandler that prompts for a username and
>> password, and then add them to the header.
>>
>> As for the addressing part of the message I would guess that the
>> addressing module handles that, but I have no experience with it.
>>
>> Hope this is a bit of help
>>
>> Mary
>>
>> Steve Cohen wrote:
>>> Okay, thanks Mary.
>>>
>>> On your suggestion and others I have rethought and begun switching
>>> to Axis2 so that I might use Rampart. I am looking at the samples
>>> and they pose a question I want to understand.
>>>
>>> That is, the use of client.axis2.xml as in the samples.
>>>
>>> WSDL2java did not generate this file for me and I'm not sure what is
>>> going to cause this file to be read.
>>>
>>> Can you explain how this works? Once I get past this, I think I
>>> will be on my way.
>>>
>>> Thanks.
>>>
>>> Steve
>>>
>>>
>>> Mary Thompson wrote:
>>>> If you mean axis2 1.4, the Rampart module will do that for you. The
>>>> Axis pages link to some documentation and to the rampart 1.3
>>>> module. Go to
>>>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart
>>>> 1.4 and more documentation.
>>>>
>>>> After you have read the overviews, look at the rampart/samples
>>>> code. I think samples/basic/sample03 may do what you want.
>>>>
>>>> Mary
>>>>
>>>> Steve Cohen wrote:
>>>>> I am trying to generate java Client code to access a web service
>>>>> from a WSDL using axis 1.4. Documentation that comes with the
>>>>> WSDL expects me to generate packets with SOAP headers that look
>>>>> something like this.
>>>>> q
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
Thanks again, Mary.
However, I am still in no-joy land. This is because of the absolutely
wretched code that WSDL2Java generated for me from this WSDL. (See
http://marc.info/?l=axis-user&m=122279472601179&w=2) or
to recapitulate that thread, I got the WSDL here
https://duoshare.com/dsWS/services/PostML/wsdl
and processed it with Java2WSDL using these options
-o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion 1.5 -uri {my wsdl}
which created a mess of compilable but ungodly code. Therefore what
should be simple setters and getters are instead gnarly thickets of
BlahBlahBlah_type1 each of which in turn has a setter for
BlahBlahBlah_type0, all to stick a stinking string parameter into an XML
packet.
Therefore I am unable to do the simple kinds of things in sample03 and
must instead learn this whole axiom object model in order to work with
this code.
Or something. I don't know what.
I think I need a WSDL2Java expert to tell me how to generate better code
from this WSDL.
Mary Thompson wrote:
> Steve,
> axis2.xml will be read by the appropriate library method if it
> appears on your class path, or is specified using a
> -Daxis2.xml=<pathname> Java option when you run the client, or set by
> a System.setProperty("axis2.xml",<pathname> ) call in your program.
> In my experience, the pathname needed to be relative to the classpath.
>
> The axis2.xml sections for rampart are the <module ref="rampart"> line
> and the OutflowSecurity and InflowSecurity sections, specifying the
> security properties of the request and response messages.
>
> I think that samples/basic/sample03/client-axis.xml would give you
> want you want for the security heading. Since the message is not
> signed you don't need the properties or keystore files.
>
> I'm not sure how you would set the user interactively. You can
> probably write a PWCBHandler that prompts for a username and password,
> and then add them to the header.
>
> As for the addressing part of the message I would guess that the
> addressing module handles that, but I have no experience with it.
>
> Hope this is a bit of help
>
> Mary
>
> Steve Cohen wrote:
>> Okay, thanks Mary.
>>
>> On your suggestion and others I have rethought and begun switching to
>> Axis2 so that I might use Rampart. I am looking at the samples and
>> they pose a question I want to understand.
>>
>> That is, the use of client.axis2.xml as in the samples.
>>
>> WSDL2java did not generate this file for me and I'm not sure what is
>> going to cause this file to be read.
>>
>> Can you explain how this works? Once I get past this, I think I will
>> be on my way.
>>
>> Thanks.
>>
>> Steve
>>
>>
>> Mary Thompson wrote:
>>> If you mean axis2 1.4, the Rampart module will do that for you. The
>>> Axis pages link to some documentation and to the rampart 1.3 module.
>>> Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
>>> rampart 1.4 and more documentation.
>>>
>>> After you have read the overviews, look at the rampart/samples code.
>>> I think samples/basic/sample03 may do what you want.
>>>
>>> Mary
>>>
>>> Steve Cohen wrote:
>>>> I am trying to generate java Client code to access a web service
>>>> from a WSDL using axis 1.4. Documentation that comes with the WSDL
>>>> expects me to generate packets with SOAP headers that look
>>>> something like this.
>>>> q
>
>
>>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>>>
>>>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>>>
>>>> 1.0.xsd"
>>>>
>>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>>>
>>>> 1.0.xsd">
>>>> <soap:Header>
>>>> <wsa:Action></wsa:Action>
>>>>
>>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>>
>>>> <wsa:ReplyTo>
>>>> <wsa:Address>
>>>>
>>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>>> </wsa:Address>
>>>> </wsa:ReplyTo>
>>>> <wsa:To>https://{url:443}</wsa:To>
>>>> <wsse:Security soap:mustUnderstand="1">
>>>> <wsse:UsernameToken
>>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
>>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>>> xxxx-xxxxxxxxxxxx">
>>>> <wsse:Username>[username]</wsse:Username>
>>>> <wsse:Password
>>>>
>>>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>>>
>>>> token-profile-1.0#PasswordText">
>>>> [password]
>>>> </wsse:Password>
>>>> </wsse:UsernameToken>
>>>> </wsse:Security>
>>>> </soap:Header>
>>>> <soap:Body>
>>>> ... </soap:Body>
>>>> </soap:Envelope>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
Thanks!
We have no need of interactive user. Ours is a server side app that is
a client of this web service. What you have described is exactly what I
needed to know.
Mary Thompson wrote:
> Steve,
> axis2.xml will be read by the appropriate library method if it
> appears on your class path, or is specified using a
> -Daxis2.xml=<pathname> Java option when you run the client, or set by
> a System.setProperty("axis2.xml",<pathname> ) call in your program.
> In my experience, the pathname needed to be relative to the classpath.
>
> The axis2.xml sections for rampart are the <module ref="rampart"> line
> and the OutflowSecurity and InflowSecurity sections, specifying the
> security properties of the request and response messages.
>
> I think that samples/basic/sample03/client-axis.xml would give you
> want you want for the security heading. Since the message is not
> signed you don't need the properties or keystore files.
>
> I'm not sure how you would set the user interactively. You can
> probably write a PWCBHandler that prompts for a username and password,
> and then add them to the header.
>
> As for the addressing part of the message I would guess that the
> addressing module handles that, but I have no experience with it.
>
> Hope this is a bit of help
>
> Mary
>
> Steve Cohen wrote:
>> Okay, thanks Mary.
>>
>> On your suggestion and others I have rethought and begun switching to
>> Axis2 so that I might use Rampart. I am looking at the samples and
>> they pose a question I want to understand.
>>
>> That is, the use of client.axis2.xml as in the samples.
>>
>> WSDL2java did not generate this file for me and I'm not sure what is
>> going to cause this file to be read.
>>
>> Can you explain how this works? Once I get past this, I think I will
>> be on my way.
>>
>> Thanks.
>>
>> Steve
>>
>>
>> Mary Thompson wrote:
>>> If you mean axis2 1.4, the Rampart module will do that for you. The
>>> Axis pages link to some documentation and to the rampart 1.3 module.
>>> Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
>>> rampart 1.4 and more documentation.
>>>
>>> After you have read the overviews, look at the rampart/samples code.
>>> I think samples/basic/sample03 may do what you want.
>>>
>>> Mary
>>>
>>> Steve Cohen wrote:
>>>> I am trying to generate java Client code to access a web service
>>>> from a WSDL using axis 1.4. Documentation that comes with the WSDL
>>>> expects me to generate packets with SOAP headers that look
>>>> something like this.
>>>> q
>
>
>>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>>>
>>>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>>>
>>>> 1.0.xsd"
>>>>
>>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>>>
>>>> 1.0.xsd">
>>>> <soap:Header>
>>>> <wsa:Action></wsa:Action>
>>>>
>>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>>
>>>> <wsa:ReplyTo>
>>>> <wsa:Address>
>>>>
>>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>>> </wsa:Address>
>>>> </wsa:ReplyTo>
>>>> <wsa:To>https://{url:443}</wsa:To>
>>>> <wsse:Security soap:mustUnderstand="1">
>>>> <wsse:UsernameToken
>>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
>>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>>> xxxx-xxxxxxxxxxxx">
>>>> <wsse:Username>[username]</wsse:Username>
>>>> <wsse:Password
>>>>
>>>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>>>
>>>> token-profile-1.0#PasswordText">
>>>> [password]
>>>> </wsse:Password>
>>>> </wsse:UsernameToken>
>>>> </wsse:Security>
>>>> </soap:Header>
>>>> <soap:Body>
>>>> ... </soap:Body>
>>>> </soap:Envelope>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Mary Thompson <mr...@lbl.gov>.
Steve,
axis2.xml will be read by the appropriate library method if it appears
on your class path, or is specified using a -Daxis2.xml=<pathname> Java
option when you run the client, or set by a
System.setProperty("axis2.xml",<pathname> ) call in your program. In my
experience, the pathname needed to be relative to the classpath.
The axis2.xml sections for rampart are the <module ref="rampart"> line
and the OutflowSecurity and InflowSecurity sections, specifying the
security properties of the request and response messages.
I think that samples/basic/sample03/client-axis.xml would give you want
you want for the security heading. Since the message is not signed you
don't need the properties or keystore files.
I'm not sure how you would set the user interactively. You can
probably write a PWCBHandler that prompts for a username and password,
and then add them to the header.
As for the addressing part of the message I would guess that the
addressing module handles that, but I have no experience with it.
Hope this is a bit of help
Mary
Steve Cohen wrote:
> Okay, thanks Mary.
>
> On your suggestion and others I have rethought and begun switching to
> Axis2 so that I might use Rampart. I am looking at the samples and they
> pose a question I want to understand.
>
> That is, the use of client.axis2.xml as in the samples.
>
> WSDL2java did not generate this file for me and I'm not sure what is
> going to cause this file to be read.
>
> Can you explain how this works? Once I get past this, I think I will be
> on my way.
>
> Thanks.
>
> Steve
>
>
> Mary Thompson wrote:
>> If you mean axis2 1.4, the Rampart module will do that for you. The
>> Axis pages link to some documentation and to the rampart 1.3 module.
>> Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
>> rampart 1.4 and more documentation.
>>
>> After you have read the overviews, look at the rampart/samples code. I
>> think samples/basic/sample03 may do what you want.
>>
>> Mary
>>
>> Steve Cohen wrote:
>>> I am trying to generate java Client code to access a web service from
>>> a WSDL using axis 1.4. Documentation that comes with the WSDL
>>> expects me to generate packets with SOAP headers that look something
>>> like this.
>>>q
>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>>
>>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>>
>>> 1.0.xsd"
>>>
>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>>
>>> 1.0.xsd">
>>> <soap:Header>
>>> <wsa:Action></wsa:Action>
>>>
>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>
>>> <wsa:ReplyTo>
>>> <wsa:Address>
>>>
>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>> </wsa:Address>
>>> </wsa:ReplyTo>
>>> <wsa:To>https://{url:443}</wsa:To>
>>> <wsse:Security soap:mustUnderstand="1">
>>> <wsse:UsernameToken
>>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>> xxxx-xxxxxxxxxxxx">
>>> <wsse:Username>[username]</wsse:Username>
>>> <wsse:Password
>>>
>>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>> token-profile-1.0#PasswordText">
>>> [password]
>>> </wsse:Password>
>>> </wsse:UsernameToken>
>>> </wsse:Security>
>>> </soap:Header>
>>> <soap:Body>
>>> ... </soap:Body>
>>> </soap:Envelope>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
No, unfortunately, the WSDL does not have policies. All it really
requires is basic http authentication. Not sure how to do that, or if
Rampart is even required for that.
Nandana Mihindukulasooriya wrote:
> Hi Steve,
> Does the WSDL has policies ? If it does it will be easy for you
> to use the policy based configuration of Rampart. Simple samples shows
> how to use the parameter based configuration with Rampart. In the
> policy based approach, you don't need a axis2.xml in the client side.
> You can just use the generated stub and set the username and password
> using client's options as shown in this [1] tutorial.
>
> thanks,
> nandana
>
> [1] - http://wso2.org/library/3190#Securing_the_client
>
> On Tue, Sep 30, 2008 at 10:27 PM, Steve Cohen <scohen@javactivity.org
> <ma...@javactivity.org>> wrote:
>
> Okay, thanks Mary.
>
> On your suggestion and others I have rethought and begun switching
> to Axis2 so that I might use Rampart. I am looking at the samples
> and they pose a question I want to understand.
>
> That is, the use of client.axis2.xml as in the samples.
>
> WSDL2java did not generate this file for me and I'm not sure what
> is going to cause this file to be read.
>
> Can you explain how this works? Once I get past this, I think I
> will be on my way.
>
> Thanks.
>
> Steve
>
>
>
> Mary Thompson wrote:
>
> If you mean axis2 1.4, the Rampart module will do that for
> you. The Axis pages link to some documentation and to the
> rampart 1.3 module. Go to
> http://ws.apache.org/rampart/download/1.4/download.cgi for
> rampart 1.4 and more documentation.
>
> After you have read the overviews, look at the rampart/samples
> code. I think samples/basic/sample03 may do what you want.
>
> Mary
>
> Steve Cohen wrote:
>
> I am trying to generate java Client code to access a web
> service from a WSDL using axis 1.4. Documentation that
> comes with the WSDL expects me to generate packets with
> SOAP headers that look something like this.
>
> Is this a well-known security scheme that Axis can be
> easily configured to generate or must it be coded by hand?
>
> <soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>
> 1.0.xsd"
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>
> 1.0.xsd">
> <soap:Header>
> <wsa:Action></wsa:Action>
>
> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>
> <wsa:ReplyTo>
> <wsa:Address>
>
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> </wsa:Address>
> </wsa:ReplyTo>
> <wsa:To>https://{url:443}</wsa:To>
> <wsse:Security soap:mustUnderstand="1">
> <wsse:UsernameToken
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd"
> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
> xxxx-xxxxxxxxxxxx">
> <wsse:Username>[username]</wsse:Username>
> <wsse:Password
>
> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
> token-profile-1.0#PasswordText">
> [password]
> </wsse:Password>
> </wsse:UsernameToken>
> </wsse:Security>
> </soap:Header>
> <soap:Body>
> ... </soap:Body>
> </soap:Envelope>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Steve,
Does the WSDL has policies ? If it does it will be easy for you to
use the policy based configuration of Rampart. Simple samples shows how to
use the parameter based configuration with Rampart. In the policy based
approach, you don't need a axis2.xml in the client side. You can just use
the generated stub and set the username and password using client's options
as shown in this [1] tutorial.
thanks,
nandana
[1] - http://wso2.org/library/3190#Securing_the_client
On Tue, Sep 30, 2008 at 10:27 PM, Steve Cohen <sc...@javactivity.org>wrote:
> Okay, thanks Mary.
>
> On your suggestion and others I have rethought and begun switching to Axis2
> so that I might use Rampart. I am looking at the samples and they pose a
> question I want to understand.
>
> That is, the use of client.axis2.xml as in the samples.
>
> WSDL2java did not generate this file for me and I'm not sure what is going
> to cause this file to be read.
>
> Can you explain how this works? Once I get past this, I think I will be on
> my way.
>
> Thanks.
>
> Steve
>
>
>
> Mary Thompson wrote:
>
>> If you mean axis2 1.4, the Rampart module will do that for you. The Axis
>> pages link to some documentation and to the rampart 1.3 module. Go to
>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4
>> and more documentation.
>>
>> After you have read the overviews, look at the rampart/samples code. I
>> think samples/basic/sample03 may do what you want.
>>
>> Mary
>>
>> Steve Cohen wrote:
>>
>>> I am trying to generate java Client code to access a web service from a
>>> WSDL using axis 1.4. Documentation that comes with the WSDL expects me to
>>> generate packets with SOAP headers that look something like this.
>>>
>>> Is this a well-known security scheme that Axis can be easily configured
>>> to generate or must it be coded by hand?
>>>
>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>> xmlns:wsse="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>> 1.0.xsd"
>>> xmlns:wsu="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>> 1.0.xsd">
>>> <soap:Header>
>>> <wsa:Action></wsa:Action>
>>>
>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>
>>> <wsa:ReplyTo>
>>> <wsa:Address>
>>>
>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>> </wsa:Address>
>>> </wsa:ReplyTo>
>>> <wsa:To>https://{url:443}</wsa:To>
>>> <wsse:Security soap:mustUnderstand="1">
>>> <wsse:UsernameToken xmlns:wsu="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-
>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>> xxxx-xxxxxxxxxxxx">
>>> <wsse:Username>[username]</wsse:Username>
>>> <wsse:Password
>>> Type="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>> token-profile-1.0#PasswordText">
>>> [password]
>>> </wsse:Password>
>>> </wsse:UsernameToken>
>>> </wsse:Security>
>>> </soap:Header>
>>> <soap:Body>
>>> ... </soap:Body>
>>> </soap:Envelope>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
Okay, thanks Mary.
On your suggestion and others I have rethought and begun switching to
Axis2 so that I might use Rampart. I am looking at the samples and they
pose a question I want to understand.
That is, the use of client.axis2.xml as in the samples.
WSDL2java did not generate this file for me and I'm not sure what is
going to cause this file to be read.
Can you explain how this works? Once I get past this, I think I will be
on my way.
Thanks.
Steve
Mary Thompson wrote:
> If you mean axis2 1.4, the Rampart module will do that for you. The
> Axis pages link to some documentation and to the rampart 1.3 module.
> Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
> rampart 1.4 and more documentation.
>
> After you have read the overviews, look at the rampart/samples code. I
> think samples/basic/sample03 may do what you want.
>
> Mary
>
> Steve Cohen wrote:
>> I am trying to generate java Client code to access a web service from
>> a WSDL using axis 1.4. Documentation that comes with the WSDL
>> expects me to generate packets with SOAP headers that look something
>> like this.
>>
>> Is this a well-known security scheme that Axis can be easily
>> configured to generate or must it be coded by hand?
>>
>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>
>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>
>> 1.0.xsd"
>>
>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>
>> 1.0.xsd">
>> <soap:Header>
>> <wsa:Action></wsa:Action>
>>
>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>
>> <wsa:ReplyTo>
>> <wsa:Address>
>>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> </wsa:Address>
>> </wsa:ReplyTo>
>> <wsa:To>https://{url:443}</wsa:To>
>> <wsse:Security soap:mustUnderstand="1">
>> <wsse:UsernameToken
>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
>> 200401-wss-wssecurity-utility-1.0.xsd"
>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>> xxxx-xxxxxxxxxxxx">
>> <wsse:Username>[username]</wsse:Username>
>> <wsse:Password
>>
>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>> token-profile-1.0#PasswordText">
>> [password]
>> </wsse:Password>
>> </wsse:UsernameToken>
>> </wsse:Security>
>> </soap:Header>
>> <soap:Body>
>> ... </soap:Body>
>> </soap:Envelope>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Steve,
Yes, this a well known security scheme. Does the WSDL has security
policies attached to it ? Then it would be very easy. Please look at the
tutorial [1] which shows how to do it. Hope you are using the SSL for this
scenario as sending the clear text password over unsecured transport is not
a good idea.
thanks,
nandana
[1] - http://wso2.org/library/3190#Securing_the_client
On Tue, Sep 30, 2008 at 7:22 AM, keith chapman <ke...@gmail.com>wrote:
> If you have the option of switching please do so. Cause Axis2 should have
> much better support for this than Axis. I'll let a rampart expert answer
> your question on whether this is a common security theme. Does the WSDL
> advertise these security requirements using policy? If so it should be
> easier.
>
> Thanks,
> Keith.
>
>
> On Tue, Sep 30, 2008 at 2:46 AM, Steve Cohen <sc...@javactivity.org>wrote:
>
>> Actually, I meant original axis 1.4.
>>
>> However, if you tell me that support for this functionality is much
>> stronger in axis 2, or non-existent in original axis, I might consider
>> switching.
>>
>>
>>
>> Mary Thompson wrote:
>>
>>> If you mean axis2 1.4, the Rampart module will do that for you. The Axis
>>> pages link to some documentation and to the rampart 1.3 module. Go to
>>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4
>>> and more documentation.
>>>
>>> After you have read the overviews, look at the rampart/samples code. I
>>> think samples/basic/sample03 may do what you want.
>>>
>>> Mary
>>>
>>> Steve Cohen wrote:
>>>
>>>> I am trying to generate java Client code to access a web service from a
>>>> WSDL using axis 1.4. Documentation that comes with the WSDL expects me to
>>>> generate packets with SOAP headers that look something like this.
>>>>
>>>> Is this a well-known security scheme that Axis can be easily configured
>>>> to generate or must it be coded by hand?
>>>>
>>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>>> xmlns:wsse="
>>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>>> 1.0.xsd"
>>>> xmlns:wsu="
>>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>>> 1.0.xsd">
>>>> <soap:Header>
>>>> <wsa:Action></wsa:Action>
>>>>
>>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>>
>>>> <wsa:ReplyTo>
>>>> <wsa:Address>
>>>>
>>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>>> </wsa:Address>
>>>> </wsa:ReplyTo>
>>>> <wsa:To>https://{url:443}</wsa:To>
>>>> <wsse:Security soap:mustUnderstand="1">
>>>> <wsse:UsernameToken xmlns:wsu="
>>>> http://docs.oasis-open.org/wss/2004/01/oasis-
>>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>>> xxxx-xxxxxxxxxxxx">
>>>> <wsse:Username>[username]</wsse:Username>
>>>> <wsse:Password
>>>> Type="
>>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>>> token-profile-1.0#PasswordText">
>>>> [password]
>>>> </wsse:Password>
>>>> </wsse:UsernameToken>
>>>> </wsse:Security>
>>>> </soap:Header>
>>>> <soap:Body>
>>>> ... </soap:Body>
>>>> </soap:Envelope>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by keith chapman <ke...@gmail.com>.
If you have the option of switching please do so. Cause Axis2 should have
much better support for this than Axis. I'll let a rampart expert answer
your question on whether this is a common security theme. Does the WSDL
advertise these security requirements using policy? If so it should be
easier.
Thanks,
Keith.
On Tue, Sep 30, 2008 at 2:46 AM, Steve Cohen <sc...@javactivity.org> wrote:
> Actually, I meant original axis 1.4.
>
> However, if you tell me that support for this functionality is much
> stronger in axis 2, or non-existent in original axis, I might consider
> switching.
>
>
>
> Mary Thompson wrote:
>
>> If you mean axis2 1.4, the Rampart module will do that for you. The Axis
>> pages link to some documentation and to the rampart 1.3 module. Go to
>> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4
>> and more documentation.
>>
>> After you have read the overviews, look at the rampart/samples code. I
>> think samples/basic/sample03 may do what you want.
>>
>> Mary
>>
>> Steve Cohen wrote:
>>
>>> I am trying to generate java Client code to access a web service from a
>>> WSDL using axis 1.4. Documentation that comes with the WSDL expects me to
>>> generate packets with SOAP headers that look something like this.
>>>
>>> Is this a well-known security scheme that Axis can be easily configured
>>> to generate or must it be coded by hand?
>>>
>>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>> xmlns:wsse="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>> 1.0.xsd"
>>> xmlns:wsu="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>> 1.0.xsd">
>>> <soap:Header>
>>> <wsa:Action></wsa:Action>
>>>
>>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>>
>>> <wsa:ReplyTo>
>>> <wsa:Address>
>>>
>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>> </wsa:Address>
>>> </wsa:ReplyTo>
>>> <wsa:To>https://{url:443}</wsa:To>
>>> <wsse:Security soap:mustUnderstand="1">
>>> <wsse:UsernameToken xmlns:wsu="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-
>>> 200401-wss-wssecurity-utility-1.0.xsd"
>>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>>> xxxx-xxxxxxxxxxxx">
>>> <wsse:Username>[username]</wsse:Username>
>>> <wsse:Password
>>> Type="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>> token-profile-1.0#PasswordText">
>>> [password]
>>> </wsse:Password>
>>> </wsse:UsernameToken>
>>> </wsse:Security>
>>> </soap:Header>
>>> <soap:Body>
>>> ... </soap:Body>
>>> </soap:Envelope>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Steve Cohen <sc...@javactivity.org>.
Actually, I meant original axis 1.4.
However, if you tell me that support for this functionality is much
stronger in axis 2, or non-existent in original axis, I might consider
switching.
Mary Thompson wrote:
> If you mean axis2 1.4, the Rampart module will do that for you. The
> Axis pages link to some documentation and to the rampart 1.3 module.
> Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
> rampart 1.4 and more documentation.
>
> After you have read the overviews, look at the rampart/samples code. I
> think samples/basic/sample03 may do what you want.
>
> Mary
>
> Steve Cohen wrote:
>> I am trying to generate java Client code to access a web service from
>> a WSDL using axis 1.4. Documentation that comes with the WSDL
>> expects me to generate packets with SOAP headers that look something
>> like this.
>>
>> Is this a well-known security scheme that Axis can be easily
>> configured to generate or must it be coded by hand?
>>
>> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>>
>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>>
>> 1.0.xsd"
>>
>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>>
>> 1.0.xsd">
>> <soap:Header>
>> <wsa:Action></wsa:Action>
>>
>> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
>>
>> <wsa:ReplyTo>
>> <wsa:Address>
>>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> </wsa:Address>
>> </wsa:ReplyTo>
>> <wsa:To>https://{url:443}</wsa:To>
>> <wsse:Security soap:mustUnderstand="1">
>> <wsse:UsernameToken
>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
>> 200401-wss-wssecurity-utility-1.0.xsd"
>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
>> xxxx-xxxxxxxxxxxx">
>> <wsse:Username>[username]</wsse:Username>
>> <wsse:Password
>>
>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>> token-profile-1.0#PasswordText">
>> [password]
>> </wsse:Password>
>> </wsse:UsernameToken>
>> </wsse:Security>
>> </soap:Header>
>> <soap:Body>
>> ... </soap:Body>
>> </soap:Envelope>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Web Service requires secure header - how to generate with Axis?
Posted by Mary Thompson <mr...@lbl.gov>.
If you mean axis2 1.4, the Rampart module will do that for you. The Axis
pages link to some documentation and to the rampart 1.3 module. Go to
http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4
and more documentation.
After you have read the overviews, look at the rampart/samples code. I
think samples/basic/sample03 may do what you want.
Mary
Steve Cohen wrote:
> I am trying to generate java Client code to access a web service from a
> WSDL using axis 1.4. Documentation that comes with the WSDL expects me
> to generate packets with SOAP headers that look something like this.
>
> Is this a well-known security scheme that Axis can be easily configured
> to generate or must it be coded by hand?
>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
>
> 1.0.xsd"
>
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
>
> 1.0.xsd">
> <soap:Header>
> <wsa:Action></wsa:Action>
>
> <wsa:MessageID>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID>
> <wsa:ReplyTo>
> <wsa:Address>
>
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> </wsa:Address>
> </wsa:ReplyTo>
> <wsa:To>https://{url:443}</wsa:To>
> <wsse:Security soap:mustUnderstand="1">
> <wsse:UsernameToken
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd"
> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx-
> xxxx-xxxxxxxxxxxx">
> <wsse:Username>[username]</wsse:Username>
> <wsse:Password
>
> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
> token-profile-1.0#PasswordText">
> [password]
> </wsse:Password>
> </wsse:UsernameToken>
> </wsse:Security>
> </soap:Header>
> <soap:Body>
> ... </soap:Body>
> </soap:Envelope>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by keith chapman <ke...@gmail.com>.
Try using -u and see whether it bets any better.
Thanks,
Keith.
On Tue, Oct 21, 2008 at 4:01 PM, Bartolomeo Nicolotti
<bn...@siapcn.it>wrote:
> No, I don't use -u option, the command is:
>
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
> -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
>
> the xsd has the form
>
>
> <xs:schema xmlns="http://webservices.galileo.com"
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified" version="1.0" id="SG2008A">
>
> <!-- <xs:element name="PNRBFManagement_12" > -->
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType name="PNRBFManagement_12Type">
> <xs:sequence>
>
> ( <xs:element name="InsertSegAfterMods" minOccurs="0"
> maxOccurs="unbounded" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence>
> <xs:element name="SegNum" maxOccurs="unbounded"
> type="xs:int" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
> Determines insertion point for next segment
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element> ) repeated for many elments and also nested
>
> </xs:sequence>
> </xs:complexType>
> </xs:schema>
>
>
>
> Many thanks, Best Regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
>
> Did you use the -u option when generating code? If not try using it this
> will unpack the code and create a java class for each datatype used.
>
> Thanks,
> Keith.
>
> On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti <
> bnicolotti@siapcn.it> wrote:
>
> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
I've had to modify the client... Now it takes 2 min to create the client
stub with the instruction:
XmlSelectStub stub = new XmlSelectStub( gwsUrl );
Where xmlSelectStub is the stub generated by axis2
I will try with jixb...
Best regards
Il giorno mar, 21/10/2008 alle 15.02 +0200, Bartolomeo Nicolotti ha
scritto:
> Eureka!
>
> With -d jaxbri it only takes one min to compile the 9.5Mb generated file
> (by the way the xsd is 2.5Mb).
>
> but the option -S JavaSourec doesn't seem to take effect with -d jaxbri,
> i'll use mv to move the files from src/... to JavaSource/...
>
> Many thanks, best regards!
>
> B.Nicolotti
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxbri -o ../..
> Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
>
>
> Il giorno mar, 21/10/2008 alle 14.20 +0200, Bartolomeo Nicolotti ha
> scritto:
> > tried also jaxme
> >
> >
> > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../..
> > Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> > Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> > Retrieving document at 'XMLSelect_emea.wsdl'.
> > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
> > databinding has taken place
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
> > proper databinding has taken place
> > at
> > org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> > ... 2 more
> >
> >
> >
> > Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
> > scritto:
> > > Tried:
> > >
> > > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > > resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../..
> > > Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> > > Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> > > Retrieving document at 'XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > > Exception in thread "main"
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> > > at
> > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > > Caused by: java.lang.RuntimeException:
> > > java.lang.reflect.InvocationTargetException
> > > at
> > > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
> > > at
> > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> > > ... 2 more
> > > Caused by: java.lang.reflect.InvocationTargetException
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > at
> > > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
> > > ... 3 more
> > > Caused by: org.apache.axis2.schema.SchemaCompilationException:
> > > java.lang.NullPointerException
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
> > > at
> > > org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
> > > ... 8 more
> > > Caused by: java.lang.NullPointerException
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
> > > at
> > > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
> > > ... 9 more
> > >
> > >
> > >
> > > Il giorno mar, 21/10/2008 alle 16.49 +0530, keith chapman ha scritto:
> > > > As an alternative to xmlbeans (which actually generates quite a lot of
> > > > code) did you try using adb?
> > > >
> > > > Thanks,
> > > > Keith.
> > > >
> > > > On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
> > > > <bn...@siapcn.it> wrote:
> > > > Hi,
> > > >
> > > > I've tried the -u option, with the command:
> > > >
> > > > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > > > resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans
> > > > -o ../..
> > > >
> > > > but the result is the same, .java 12Mb and Impl.java 34Mb, I
> > > > think because in the xsd there's only one named complexType.
> > > >
> > > >
> > > > Many thanks, best regards,
> > > >
> > > > B.Nicolotti
> > > >
> > > >
> > > > Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo
> > > > Nicolotti ha scritto:
> > > >
> > > >
> > > > > No, I don't use -u option, the command is:
> > > > >
> > > > > wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient
> > > > > -s -sd -ssi -sp -d xmlbeans -o .. -ns2p [... namespace
> > > > > mappings]
> > > > > the xsd has the form
> > > > >
> > > > >
> > > > > <xs:schema
> > > > > xmlns="http://webservices.galileo.com"
> > > > > xmlns:xs="http://www.w3.org/2001/XMLSchema"
> > > > > elementFormDefault="qualified" version="1.0"
> > > > > id="SG2008A">
> > > > >
> > > > > <!-- <xs:element name="PNRBFManagement_12" > -->
> > > > > <xs:annotation>
> > > > > <xs:documentation xml:lang="en">
> > > > >
> > > > > </xs:documentation>
> > > > > </xs:annotation>
> > > > > <xs:complexType name="PNRBFManagement_12Type">
> > > > > <xs:sequence>
> > > > >
> > > > > ( <xs:element name="InsertSegAfterMods"
> > > > > minOccurs="0" maxOccurs="unbounded" >
> > > > > <xs:annotation>
> > > > > <xs:documentation xml:lang="en">
> > > > >
> > > > > </xs:documentation>
> > > > > </xs:annotation>
> > > > > <xs:complexType>
> > > > > <xs:sequence>
> > > > > <xs:element name="SegNum"
> > > > > maxOccurs="unbounded" type="xs:int" >
> > > > > <xs:annotation>
> > > > > <xs:documentation xml:lang="en">
> > > > > Determines insertion point for next
> > > > > segment
> > > > > </xs:documentation>
> > > > > </xs:annotation>
> > > > > </xs:element>
> > > > > </xs:sequence>
> > > > > </xs:complexType>
> > > > > </xs:element> ) repeated for many elments and
> > > > > also nested
> > > > >
> > > > > </xs:sequence>
> > > > > </xs:complexType>
> > > > > </xs:schema>
> > > > >
> > > > >
> > > > >
> > > > > Many thanks, Best Regards,
> > > > >
> > > > > B.Nicolotti
> > > > >
> > > > > Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha
> > > > > scritto:
> > > > > > Did you use the -u option when generating code? If not try
> > > > > > using it this will unpack the code and create a java class
> > > > > > for each datatype used.
> > > > > >
> > > > > > Thanks,
> > > > > > Keith.
> > > > > >
> > > > > > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > > > > > <bn...@siapcn.it> wrote:
> > > > > > Hi
> > > > > >
> > > > > > I'm using axis2 to consume document/literal web
> > > > > > services, but one xsd
> > > > > > for Galileo travel supplier is is 64227 lines long
> > > > > > and the .java
> > > > > > generated by wsdl2java is 12Mb and the
> > > > > > corresponding Impl.java is also
> > > > > > 34Mb long. The preblem is that when I must compile
> > > > > > these .java it takes
> > > > > > 10minutes. Does someone know why and how to make
> > > > > > this task faster?
> > > > > >
> > > > > > Many thanks, Best Regards.
> > > > > >
> > > > > > Bartolomeo Nicolotti.
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > > > > > axis-user-unsubscribe@ws.apache.org
> > > > > > For additional commands, e-mail:
> > > > > > axis-user-help@ws.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Keith Chapman
> > > > > > Senior Software Engineer
> > > > > > WSO2 Inc.
> > > > > > Oxygenating the Web Service Platform.
> > > > > > http://wso2.org/
> > > > > >
> > > > > > blog: http://www.keith-chapman.org
> > > > > >
> > > > > --
> > > > > Bartolomeo Nicolotti
> > > > > SIAP s.r.l.
> > > > > www.siapcn.it
> > > > > v.S.Albano 13 12049
> > > > > Trinità(CN) Italy
> > > > > ph:+39 0172 652553
> > > > > centralino: +39 0172 652511
> > > > > fax: +39 0172 652519
> > > > --
> > > > Bartolomeo Nicolotti
> > > > SIAP s.r.l.
> > > > www.siapcn.it
> > > > v.S.Albano 13 12049
> > > > Trinità(CN) Italy
> > > > ph:+39 0172 652553
> > > > centralino: +39 0172 652511
> > > > fax: +39 0172 652519
> > > >
> > > >
> > > >
> > > > --
> > > > Keith Chapman
> > > > Senior Software Engineer
> > > > WSO2 Inc.
> > > > Oxygenating the Web Service Platform.
> > > > http://wso2.org/
> > > >
> > > > blog: http://www.keith-chapman.org
> > > >
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
Eureka!
With -d jaxbri it only takes one min to compile the 9.5Mb generated file
(by the way the xsd is 2.5Mb).
but the option -S JavaSourec doesn't seem to take effect with -d jaxbri,
i'll use mv to move the files from src/... to JavaSource/...
Many thanks, best regards!
B.Nicolotti
wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxbri -o ../..
Using AXIS2_HOME: /home/user/software/axis2-1.4.1
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Il giorno mar, 21/10/2008 alle 14.20 +0200, Bartolomeo Nicolotti ha
scritto:
> tried also jaxme
>
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../..
> Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
> databinding has taken place
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
> proper databinding has taken place
> at
> org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> ... 2 more
>
>
>
> Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
> scritto:
> > Tried:
> >
> > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../..
> > Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> > Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> > Retrieving document at 'XMLSelect_emea.wsdl'.
> > Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'AirAvailability_8.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> > 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException:
> > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> > Caused by: java.lang.RuntimeException:
> > java.lang.reflect.InvocationTargetException
> > at
> > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
> > at
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> > ... 2 more
> > Caused by: java.lang.reflect.InvocationTargetException
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at
> > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
> > ... 3 more
> > Caused by: org.apache.axis2.schema.SchemaCompilationException:
> > java.lang.NullPointerException
> > at
> > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
> > at
> > org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
> > ... 8 more
> > Caused by: java.lang.NullPointerException
> > at
> > org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
> > at
> > org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
> > at
> > org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
> > at
> > org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> > at
> > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> > at
> > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> > at
> > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
> > at
> > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
> > at
> > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
> > ... 9 more
> >
> >
> >
> > Il giorno mar, 21/10/2008 alle 16.49 +0530, keith chapman ha scritto:
> > > As an alternative to xmlbeans (which actually generates quite a lot of
> > > code) did you try using adb?
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
> > > <bn...@siapcn.it> wrote:
> > > Hi,
> > >
> > > I've tried the -u option, with the command:
> > >
> > > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > > resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans
> > > -o ../..
> > >
> > > but the result is the same, .java 12Mb and Impl.java 34Mb, I
> > > think because in the xsd there's only one named complexType.
> > >
> > >
> > > Many thanks, best regards,
> > >
> > > B.Nicolotti
> > >
> > >
> > > Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo
> > > Nicolotti ha scritto:
> > >
> > >
> > > > No, I don't use -u option, the command is:
> > > >
> > > > wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient
> > > > -s -sd -ssi -sp -d xmlbeans -o .. -ns2p [... namespace
> > > > mappings]
> > > > the xsd has the form
> > > >
> > > >
> > > > <xs:schema
> > > > xmlns="http://webservices.galileo.com"
> > > > xmlns:xs="http://www.w3.org/2001/XMLSchema"
> > > > elementFormDefault="qualified" version="1.0"
> > > > id="SG2008A">
> > > >
> > > > <!-- <xs:element name="PNRBFManagement_12" > -->
> > > > <xs:annotation>
> > > > <xs:documentation xml:lang="en">
> > > >
> > > > </xs:documentation>
> > > > </xs:annotation>
> > > > <xs:complexType name="PNRBFManagement_12Type">
> > > > <xs:sequence>
> > > >
> > > > ( <xs:element name="InsertSegAfterMods"
> > > > minOccurs="0" maxOccurs="unbounded" >
> > > > <xs:annotation>
> > > > <xs:documentation xml:lang="en">
> > > >
> > > > </xs:documentation>
> > > > </xs:annotation>
> > > > <xs:complexType>
> > > > <xs:sequence>
> > > > <xs:element name="SegNum"
> > > > maxOccurs="unbounded" type="xs:int" >
> > > > <xs:annotation>
> > > > <xs:documentation xml:lang="en">
> > > > Determines insertion point for next
> > > > segment
> > > > </xs:documentation>
> > > > </xs:annotation>
> > > > </xs:element>
> > > > </xs:sequence>
> > > > </xs:complexType>
> > > > </xs:element> ) repeated for many elments and
> > > > also nested
> > > >
> > > > </xs:sequence>
> > > > </xs:complexType>
> > > > </xs:schema>
> > > >
> > > >
> > > >
> > > > Many thanks, Best Regards,
> > > >
> > > > B.Nicolotti
> > > >
> > > > Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha
> > > > scritto:
> > > > > Did you use the -u option when generating code? If not try
> > > > > using it this will unpack the code and create a java class
> > > > > for each datatype used.
> > > > >
> > > > > Thanks,
> > > > > Keith.
> > > > >
> > > > > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > > > > <bn...@siapcn.it> wrote:
> > > > > Hi
> > > > >
> > > > > I'm using axis2 to consume document/literal web
> > > > > services, but one xsd
> > > > > for Galileo travel supplier is is 64227 lines long
> > > > > and the .java
> > > > > generated by wsdl2java is 12Mb and the
> > > > > corresponding Impl.java is also
> > > > > 34Mb long. The preblem is that when I must compile
> > > > > these .java it takes
> > > > > 10minutes. Does someone know why and how to make
> > > > > this task faster?
> > > > >
> > > > > Many thanks, Best Regards.
> > > > >
> > > > > Bartolomeo Nicolotti.
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > > axis-user-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail:
> > > > > axis-user-help@ws.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Keith Chapman
> > > > > Senior Software Engineer
> > > > > WSO2 Inc.
> > > > > Oxygenating the Web Service Platform.
> > > > > http://wso2.org/
> > > > >
> > > > > blog: http://www.keith-chapman.org
> > > > >
> > > > --
> > > > Bartolomeo Nicolotti
> > > > SIAP s.r.l.
> > > > www.siapcn.it
> > > > v.S.Albano 13 12049
> > > > Trinità(CN) Italy
> > > > ph:+39 0172 652553
> > > > centralino: +39 0172 652511
> > > > fax: +39 0172 652519
> > > --
> > > Bartolomeo Nicolotti
> > > SIAP s.r.l.
> > > www.siapcn.it
> > > v.S.Albano 13 12049
> > > Trinità(CN) Italy
> > > ph:+39 0172 652553
> > > centralino: +39 0172 652511
> > > fax: +39 0172 652519
> > >
> > >
> > >
> > > --
> > > Keith Chapman
> > > Senior Software Engineer
> > > WSO2 Inc.
> > > Oxygenating the Web Service Platform.
> > > http://wso2.org/
> > >
> > > blog: http://www.keith-chapman.org
> > >
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
tried also jaxme
wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d jaxme -o ../..
Using AXIS2_HOME: /home/user/software/axis2-1.4.1
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException: No proper
databinding has taken place
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: No
proper databinding has taken place
at
org.apache.axis2.wsdl.codegen.extension.DefaultDatabindingExtension.engage(DefaultDatabindingExtension.java:41)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Il giorno mar, 21/10/2008 alle 14.05 +0200, Bartolomeo Nicolotti ha
scritto:
> Tried:
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../..
> Using AXIS2_HOME: /home/user/software/axis2-1.4.1
> Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
> Retrieving document at 'XMLSelect_emea.wsdl'.
> Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'AirAvailability_8.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Retrieving schema at 'PNRBFManagement_12.xsd', relative to
> 'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> at
> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> ... 2 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
> ... 3 more
> Caused by: org.apache.axis2.schema.SchemaCompilationException:
> java.lang.NullPointerException
> at
> org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
> at
> org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
> at
> org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
> at
> org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> at
> org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> at
> org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> at
> org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> at
> org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> at
> org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
> at
> org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
> at
> org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
> at
> org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
> at
> org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
> at
> org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
> at
> org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
> at
> org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
> at
> org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
> ... 9 more
>
>
>
> Il giorno mar, 21/10/2008 alle 16.49 +0530, keith chapman ha scritto:
> > As an alternative to xmlbeans (which actually generates quite a lot of
> > code) did you try using adb?
> >
> > Thanks,
> > Keith.
> >
> > On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
> > <bn...@siapcn.it> wrote:
> > Hi,
> >
> > I've tried the -u option, with the command:
> >
> > wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> > resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans
> > -o ../..
> >
> > but the result is the same, .java 12Mb and Impl.java 34Mb, I
> > think because in the xsd there's only one named complexType.
> >
> >
> > Many thanks, best regards,
> >
> > B.Nicolotti
> >
> >
> > Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo
> > Nicolotti ha scritto:
> >
> >
> > > No, I don't use -u option, the command is:
> > >
> > > wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient
> > > -s -sd -ssi -sp -d xmlbeans -o .. -ns2p [... namespace
> > > mappings]
> > > the xsd has the form
> > >
> > >
> > > <xs:schema
> > > xmlns="http://webservices.galileo.com"
> > > xmlns:xs="http://www.w3.org/2001/XMLSchema"
> > > elementFormDefault="qualified" version="1.0"
> > > id="SG2008A">
> > >
> > > <!-- <xs:element name="PNRBFManagement_12" > -->
> > > <xs:annotation>
> > > <xs:documentation xml:lang="en">
> > >
> > > </xs:documentation>
> > > </xs:annotation>
> > > <xs:complexType name="PNRBFManagement_12Type">
> > > <xs:sequence>
> > >
> > > ( <xs:element name="InsertSegAfterMods"
> > > minOccurs="0" maxOccurs="unbounded" >
> > > <xs:annotation>
> > > <xs:documentation xml:lang="en">
> > >
> > > </xs:documentation>
> > > </xs:annotation>
> > > <xs:complexType>
> > > <xs:sequence>
> > > <xs:element name="SegNum"
> > > maxOccurs="unbounded" type="xs:int" >
> > > <xs:annotation>
> > > <xs:documentation xml:lang="en">
> > > Determines insertion point for next
> > > segment
> > > </xs:documentation>
> > > </xs:annotation>
> > > </xs:element>
> > > </xs:sequence>
> > > </xs:complexType>
> > > </xs:element> ) repeated for many elments and
> > > also nested
> > >
> > > </xs:sequence>
> > > </xs:complexType>
> > > </xs:schema>
> > >
> > >
> > >
> > > Many thanks, Best Regards,
> > >
> > > B.Nicolotti
> > >
> > > Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha
> > > scritto:
> > > > Did you use the -u option when generating code? If not try
> > > > using it this will unpack the code and create a java class
> > > > for each datatype used.
> > > >
> > > > Thanks,
> > > > Keith.
> > > >
> > > > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > > > <bn...@siapcn.it> wrote:
> > > > Hi
> > > >
> > > > I'm using axis2 to consume document/literal web
> > > > services, but one xsd
> > > > for Galileo travel supplier is is 64227 lines long
> > > > and the .java
> > > > generated by wsdl2java is 12Mb and the
> > > > corresponding Impl.java is also
> > > > 34Mb long. The preblem is that when I must compile
> > > > these .java it takes
> > > > 10minutes. Does someone know why and how to make
> > > > this task faster?
> > > >
> > > > Many thanks, Best Regards.
> > > >
> > > > Bartolomeo Nicolotti.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > > axis-user-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail:
> > > > axis-user-help@ws.apache.org
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Keith Chapman
> > > > Senior Software Engineer
> > > > WSO2 Inc.
> > > > Oxygenating the Web Service Platform.
> > > > http://wso2.org/
> > > >
> > > > blog: http://www.keith-chapman.org
> > > >
> > > --
> > > Bartolomeo Nicolotti
> > > SIAP s.r.l.
> > > www.siapcn.it
> > > v.S.Albano 13 12049
> > > Trinità(CN) Italy
> > > ph:+39 0172 652553
> > > centralino: +39 0172 652511
> > > fax: +39 0172 652519
> > --
> > Bartolomeo Nicolotti
> > SIAP s.r.l.
> > www.siapcn.it
> > v.S.Albano 13 12049
> > Trinità(CN) Italy
> > ph:+39 0172 652553
> > centralino: +39 0172 652511
> > fax: +39 0172 652519
> >
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
Tried:
wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -o ../..
Using AXIS2_HOME: /home/user/software/axis2-1.4.1
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun/
Retrieving document at 'XMLSelect_emea.wsdl'.
Retrieving schema at 'LocalDateTimeCT_6_0.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'AirAvailability_8.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'FareQuoteSuperBB_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Retrieving schema at 'PNRBFManagement_12.xsd', relative to
'file:/home/user/workspace_HEAD_clean_OTA/galileo-util/wsdl/XMLSelectClient/XMLSelect_emea.wsdl'.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:53)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:50)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
java.lang.NullPointerException
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:289)
at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java:103)
... 8 more
Caused by: java.lang.NullPointerException
at
org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2704)
at
org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:925)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:552)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:1991)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:1874)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:1081)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaType(SchemaCompiler.java:980)
at
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:934)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:592)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:563)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:370)
at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:280)
... 9 more
Il giorno mar, 21/10/2008 alle 16.49 +0530, keith chapman ha scritto:
> As an alternative to xmlbeans (which actually generates quite a lot of
> code) did you try using adb?
>
> Thanks,
> Keith.
>
> On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
> <bn...@siapcn.it> wrote:
> Hi,
>
> I've tried the -u option, with the command:
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans
> -o ../..
>
> but the result is the same, .java 12Mb and Impl.java 34Mb, I
> think because in the xsd there's only one named complexType.
>
>
> Many thanks, best regards,
>
> B.Nicolotti
>
>
> Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo
> Nicolotti ha scritto:
>
>
> > No, I don't use -u option, the command is:
> >
> > wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient
> > -s -sd -ssi -sp -d xmlbeans -o .. -ns2p [... namespace
> > mappings]
> > the xsd has the form
> >
> >
> > <xs:schema
> > xmlns="http://webservices.galileo.com"
> > xmlns:xs="http://www.w3.org/2001/XMLSchema"
> > elementFormDefault="qualified" version="1.0"
> > id="SG2008A">
> >
> > <!-- <xs:element name="PNRBFManagement_12" > -->
> > <xs:annotation>
> > <xs:documentation xml:lang="en">
> >
> > </xs:documentation>
> > </xs:annotation>
> > <xs:complexType name="PNRBFManagement_12Type">
> > <xs:sequence>
> >
> > ( <xs:element name="InsertSegAfterMods"
> > minOccurs="0" maxOccurs="unbounded" >
> > <xs:annotation>
> > <xs:documentation xml:lang="en">
> >
> > </xs:documentation>
> > </xs:annotation>
> > <xs:complexType>
> > <xs:sequence>
> > <xs:element name="SegNum"
> > maxOccurs="unbounded" type="xs:int" >
> > <xs:annotation>
> > <xs:documentation xml:lang="en">
> > Determines insertion point for next
> > segment
> > </xs:documentation>
> > </xs:annotation>
> > </xs:element>
> > </xs:sequence>
> > </xs:complexType>
> > </xs:element> ) repeated for many elments and
> > also nested
> >
> > </xs:sequence>
> > </xs:complexType>
> > </xs:schema>
> >
> >
> >
> > Many thanks, Best Regards,
> >
> > B.Nicolotti
> >
> > Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha
> > scritto:
> > > Did you use the -u option when generating code? If not try
> > > using it this will unpack the code and create a java class
> > > for each datatype used.
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > > <bn...@siapcn.it> wrote:
> > > Hi
> > >
> > > I'm using axis2 to consume document/literal web
> > > services, but one xsd
> > > for Galileo travel supplier is is 64227 lines long
> > > and the .java
> > > generated by wsdl2java is 12Mb and the
> > > corresponding Impl.java is also
> > > 34Mb long. The preblem is that when I must compile
> > > these .java it takes
> > > 10minutes. Does someone know why and how to make
> > > this task faster?
> > >
> > > Many thanks, Best Regards.
> > >
> > > Bartolomeo Nicolotti.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail:
> > > axis-user-help@ws.apache.org
> > >
> > >
> > >
> > >
> > > --
> > > Keith Chapman
> > > Senior Software Engineer
> > > WSO2 Inc.
> > > Oxygenating the Web Service Platform.
> > > http://wso2.org/
> > >
> > > blog: http://www.keith-chapman.org
> > >
> > --
> > Bartolomeo Nicolotti
> > SIAP s.r.l.
> > www.siapcn.it
> > v.S.Albano 13 12049
> > Trinità(CN) Italy
> > ph:+39 0172 652553
> > centralino: +39 0172 652511
> > fax: +39 0172 652519
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.
> www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
[ANN] VTD-XML extended edition released
Posted by jimmy Zhang <cr...@comcast.net>.
The Java version of extended VTD-XmL is released and available for download.
This version supports 256 GB max file sizes and memory mapped capabilities.
The updated documentation is also available for download. In short, you can
basically do full XPath query on documents that are bigger than memory space
available on your machine.
A special thanks to Duane May who provided value suggestions and inputs and
helped refine the VTD specs to make this happen.
To download the package and the documentation, go to
https://sourceforge.net/project/downloading.php?group_id=110612&use_mirror=&filename=vtd-xml_2.4_doc.zip&64621261
https://sourceforge.net/project/downloading.php?group_id=110612&use_mirror=&filename=ximpleware_extended_2.4.zip&99532507
Re: [axis2] Huge .java generated by wsdl2java
Posted by keith chapman <ke...@gmail.com>.
As an alternative to xmlbeans (which actually generates quite a lot of code)
did you try using adb?
Thanks,
Keith.
On Tue, Oct 21, 2008 at 4:37 PM, Bartolomeo Nicolotti
<bn...@siapcn.it>wrote:
> Hi,
>
> I've tried the -u option, with the command:
>
> wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
> resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans -o ../..
>
> but the result is the same, .java 12Mb and Impl.java 34Mb, I think because
> in the xsd there's only one named complexType.
>
> Many thanks, best regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo Nicolotti ha
> scritto:
>
> No, I don't use -u option, the command is:
>
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
> -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
> the xsd has the form
>
>
> <xs:schema xmlns="http://webservices.galileo.com"
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified" version="1.0" id="SG2008A">
>
> <!-- <xs:element name="PNRBFManagement_12" > -->
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType name="PNRBFManagement_12Type">
> <xs:sequence>
>
> ( <xs:element name="InsertSegAfterMods" minOccurs="0"
> maxOccurs="unbounded" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence>
> <xs:element name="SegNum" maxOccurs="unbounded"
> type="xs:int" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
> Determines insertion point for next segment
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element> ) repeated for many elments and also nested
>
> </xs:sequence>
> </xs:complexType>
> </xs:schema>
>
>
>
> Many thanks, Best Regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
>
> Did you use the -u option when generating code? If not try using it this
> will unpack the code and create a java class for each datatype used.
>
> Thanks,
> Keith.
>
> On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti <
> bnicolotti@siapcn.it> wrote:
>
> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
Hi,
I've tried the -u option, with the command:
wsdl2java.sh -uri XMLSelect_emea.wsdl -S JavaSource -R
resources/XMLSelectClient -s -sd -u -ssi -sp -or -d xmlbeans -o ../..
but the result is the same, .java 12Mb and Impl.java 34Mb, I think
because in the xsd there's only one named complexType.
Many thanks, best regards,
B.Nicolotti
Il giorno mar, 21/10/2008 alle 12.31 +0200, Bartolomeo Nicolotti ha
scritto:
> No, I don't use -u option, the command is:
>
> wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd
> -ssi -sp -d xmlbeans -o .. -ns2p [... namespace mappings]
> the xsd has the form
>
>
> <xs:schema xmlns="http://webservices.galileo.com"
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified" version="1.0"
> id="SG2008A">
>
> <!-- <xs:element name="PNRBFManagement_12" > -->
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType name="PNRBFManagement_12Type">
> <xs:sequence>
>
> ( <xs:element name="InsertSegAfterMods" minOccurs="0"
> maxOccurs="unbounded" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
>
> </xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence>
> <xs:element name="SegNum" maxOccurs="unbounded"
> type="xs:int" >
> <xs:annotation>
> <xs:documentation xml:lang="en">
> Determines insertion point for next segment
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element> ) repeated for many elments and also nested
>
> </xs:sequence>
> </xs:complexType>
> </xs:schema>
>
>
>
> Many thanks, Best Regards,
>
> B.Nicolotti
>
> Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
>
> > Did you use the -u option when generating code? If not try using it
> > this will unpack the code and create a java class for each datatype
> > used.
> >
> > Thanks,
> > Keith.
> >
> > On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> > <bn...@siapcn.it> wrote:
> >
> > Hi
> >
> > I'm using axis2 to consume document/literal web services,
> > but one xsd
> > for Galileo travel supplier is is 64227 lines long and
> > the .java
> > generated by wsdl2java is 12Mb and the corresponding
> > Impl.java is also
> > 34Mb long. The preblem is that when I must compile
> > these .java it takes
> > 10minutes. Does someone know why and how to make this task
> > faster?
> >
> > Many thanks, Best Regards.
> >
> > Bartolomeo Nicolotti.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> > axis-user-help@ws.apache.org
> >
> >
> >
> >
> >
> > --
> > Keith Chapman
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> >
> > blog: http://www.keith-chapman.org
> >
>
> --
> Bartolomeo Nicolotti
> SIAP s.r.l.
> www.siapcn.it
> v.S.Albano 13 12049
> Trinità(CN) Italy
> ph:+39 0172 652553
> centralino: +39 0172 652511
> fax: +39 0172 652519
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
Re: [axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
No, I don't use -u option, the command is:
wsdl2java.sh -uri Galileo.wsdl -S JavaSource/XMLSelectClient -s -sd -ssi
-sp -d xmlbeans -o .. -ns2p [... namespace mappings]
the xsd has the form
<xs:schema xmlns="http://webservices.galileo.com"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" version="1.0"
id="SG2008A">
<!-- <xs:element name="PNRBFManagement_12" > -->
<xs:annotation>
<xs:documentation xml:lang="en">
</xs:documentation>
</xs:annotation>
<xs:complexType name="PNRBFManagement_12Type">
<xs:sequence>
( <xs:element name="InsertSegAfterMods" minOccurs="0"
maxOccurs="unbounded" >
<xs:annotation>
<xs:documentation xml:lang="en">
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SegNum" maxOccurs="unbounded"
type="xs:int" >
<xs:annotation>
<xs:documentation xml:lang="en">
Determines insertion point for next segment
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element> ) repeated for many elments and also nested
</xs:sequence>
</xs:complexType>
</xs:schema>
Many thanks, Best Regards,
B.Nicolotti
Il giorno mar, 21/10/2008 alle 15.47 +0530, keith chapman ha scritto:
> Did you use the -u option when generating code? If not try using it
> this will unpack the code and create a java class for each datatype
> used.
>
> Thanks,
> Keith.
>
>
> On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
> <bn...@siapcn.it> wrote:
>
> Hi
>
> I'm using axis2 to consume document/literal web services, but
> one xsd
> for Galileo travel supplier is is 64227 lines long and
> the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java
> is also
> 34Mb long. The preblem is that when I must compile these .java
> it takes
> 10minutes. Does someone know why and how to make this task
> faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Bartolomeo Nicolotti
SIAP s.r.l.
www.siapcn.it
v.S.Albano 13 12049
Trinità(CN) Italy
ph:+39 0172 652553
centralino: +39 0172 652511
fax: +39 0172 652519
Re: [axis2] Huge .java generated by wsdl2java
Posted by keith chapman <ke...@gmail.com>.
Did you use the -u option when generating code? If not try using it this
will unpack the code and create a java class for each datatype used.
Thanks,
Keith.
On Tue, Oct 21, 2008 at 3:33 PM, Bartolomeo Nicolotti
<bn...@siapcn.it>wrote:
> Hi
>
> I'm using axis2 to consume document/literal web services, but one xsd
> for Galileo travel supplier is is 64227 lines long and the .java
> generated by wsdl2java is 12Mb and the corresponding Impl.java is also
> 34Mb long. The preblem is that when I must compile these .java it takes
> 10minutes. Does someone know why and how to make this task faster?
>
> Many thanks, Best Regards.
>
> Bartolomeo Nicolotti.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
[axis2] Huge .java generated by wsdl2java
Posted by Bartolomeo Nicolotti <bn...@siapcn.it>.
Hi
I'm using axis2 to consume document/literal web services, but one xsd
for Galileo travel supplier is is 64227 lines long and the .java
generated by wsdl2java is 12Mb and the corresponding Impl.java is also
34Mb long. The preblem is that when I must compile these .java it takes
10minutes. Does someone know why and how to make this task faster?
Many thanks, Best Regards.
Bartolomeo Nicolotti.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org