Re: Axis2 and Apache CXF

[Paul Fremantle]

Certainly Axis2 has much better support for advanced web services
standards including WSRM, WSSecConversation, WS-Trust,
WS-Notification, and others.

Paul

On Wed, Oct 1, 2008 at 5:47 AM, Shehan Simen <[EMAIL PROTECTED]> wrote:
> Thank you. It is useful to some extent.
>
> I would like to know anyone has more ideas to convince that axis2 has better
> features than CXF.
>
>
>
> Regards,
>
> Shehan
>
>
>
> From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Townsend
> Sent: Wednesday, 1 October 2008 1:56 PM
> To: axis-user@ws.apache.org
> Subject: Re: Axis2 and Apache CXF
>
>
>
> Ack, victim of a bad cut and paste buffer. :)
>
>
>
> http://www.theserverside.com/tt/articles/article.tss?l=AxisAxis2andCXF
>
>
>
> Sorry about that!
>
>
>
> On Sep 30, 2008, at 8:34 PM  September 30, Shehan Simen wrote:
>
> I cant find anything related to CXF in this url. Are u sure that this the
> right link?
>
>
>
> From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Townsend
> Sent: Wednesday, 1 October 2008 12:20 PM
> To: axis-user@ws.apache.org
> Subject: Re: Axis2 and Apache CXF
>
>
>
> Hello Shehan,
>
>
>
> You might find this article I wrote for TheServerSide.com:
>
>
>
> http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=885618
>
>
>
> helpful. It was written some time ago so it is a bit outdated, both Axis2
> and CXF have grown and matured a lot since then, but it might help give you
> the basic idea.
>
>
>
> Bjorn
>
>
>
>
>
> On Sep 30, 2008, at 5:59 PM  September 30, Shehan Simen wrote:
>
>
> Hi Axis2 guys,
>
> I was using axis2 for few months for work and found it quite handy.
>
> What is apache CXF? Can someone please compare CXF and Axis2? So I can
> recommend the people to use Axis2 instead of CXF. Hope to hear soon.
>
>
>
> Thanks.
>
>
>
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Axis2 and Apache CXF

[Shehan Simen]

Thank you. It is useful to some extent.
I would like to know anyone has more ideas to convince that axis2 has better 
features than CXF.

Regards,
Shehan

From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Townsend
Sent: Wednesday, 1 October 2008 1:56 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 and Apache CXF

Ack, victim of a bad cut and paste buffer. :)

http://www.theserverside.com/tt/articles/article.tss?l=AxisAxis2andCXF

Sorry about that!

On Sep 30, 2008, at 8:34 PM  September 30, Shehan Simen wrote:


I cant find anything related to CXF in this url. Are u sure that this the right 
link?

From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Townsend
Sent: Wednesday, 1 October 2008 12:20 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 and Apache CXF

Hello Shehan,

You might find this article I wrote for TheServerSide.com:

http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=885618

helpful. It was written some time ago so it is a bit outdated, both Axis2 and 
CXF have grown and matured a lot since then, but it might help give you the 
basic idea.

Bjorn


On Sep 30, 2008, at 5:59 PM  September 30, Shehan Simen wrote:



Hi Axis2 guys,
I was using axis2 for few months for work and found it quite handy.
What is apache CXF? Can someone please compare CXF and Axis2? So I can 
recommend the people to use Axis2 instead of CXF. Hope to hear soon.

Thanks.

Re: Axis2 and Apache CXF

[Bjorn Townsend]

Ack, victim of a bad cut and paste buffer. :)

http://www.theserverside.com/tt/articles/article.tss?l=AxisAxis2andCXF

Sorry about that!

On Sep 30, 2008, at 8:34 PM  September 30, Shehan Simen wrote:

I cant find anything related to CXF in this url. Are u sure that  
this the right link?


From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn  
Townsend

Sent: Wednesday, 1 October 2008 12:20 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 and Apache CXF

Hello Shehan,

You might find this article I wrote for TheServerSide.com:

http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=885618

helpful. It was written some time ago so it is a bit outdated, both  
Axis2 and CXF have grown and matured a lot since then, but it might  
help give you the basic idea.


Bjorn


On Sep 30, 2008, at 5:59 PM  September 30, Shehan Simen wrote:


Hi Axis2 guys,
I was using axis2 for few months for work and found it quite handy.
What is apache CXF? Can someone please compare CXF and Axis2? So I  
can recommend the people to use Axis2 instead of CXF. Hope to hear  
soon.


Thanks.

RE: Axis2 and Apache CXF

[Shehan Simen]

I cant find anything related to CXF in this url. Are u sure that this the right 
link?

From: Bjorn Townsend [mailto:[EMAIL PROTECTED] On Behalf Of Bjorn Townsend
Sent: Wednesday, 1 October 2008 12:20 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 and Apache CXF

Hello Shehan,

You might find this article I wrote for TheServerSide.com:

http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=885618

helpful. It was written some time ago so it is a bit outdated, both Axis2 and 
CXF have grown and matured a lot since then, but it might help give you the 
basic idea.

Bjorn


On Sep 30, 2008, at 5:59 PM  September 30, Shehan Simen wrote:


Hi Axis2 guys,
I was using axis2 for few months for work and found it quite handy.
What is apache CXF? Can someone please compare CXF and Axis2? So I can 
recommend the people to use Axis2 instead of CXF. Hope to hear soon.

Thanks.

Re: AW: Integrating Axis2 with Tomcat and Eclipse

[Saminda Wijeratne]

Well not exactly. Eclipse uses a plugin to integrate the functionality 
of axis2. It is through this plugin eclipse creates web services and 
client stubs using reflection over the binary distribution of axis2. 
Thats why you need to specify the axis2 binary location under 
preference. Other than that non of the eclipse distributions comes 
packed with axis2. But as Markus mentioned the plugins is a good place 
to start looking for what u might need to achieve yo goal.


Thank you
Saminda.

Grimm, Markus wrote:

Hi,

Axis2-setup is integrated in Eclispe WTP.
Look at

http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebServ
ice/bu_tutorial.html  or
http://www.eclipse.org/webtools/community/tutorials/TopDownAxis2WebServi
ce/td_tutorial.html

Thanks,
Markus

  
 



Von: Bai Shen [mailto:[EMAIL PROTECTED] 
Gesendet: Sonntag, 28. September 2008 21:30

An: axis-user@ws.apache.org
Betreff: Integrating Axis2 with Tomcat and Eclipse


I've been using Eclipse, Tomcat, and Axis for a while.  However, I'm
working on automating my setup. Thanks to the helpful members of the
Tomcat list, I have Tomcat integrated with Eclipse, so I can code and
deploy easily.

What I'm curious about is if there is a way to add Axis2 to the setup?
I'm running Eclipse 3.4, Tomcat 6.0.18, and Axis2 1.4.1.

TIA.

Bai Shen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Web Service requires secure header - how to generate with Axis?

[Steve Cohen]

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= Java option when you run the client, or set by 
a System.setProperty("axis2.xml", ) call in your program.  
In my experience, the pathname needed to be relative to the classpath.


The axis2.xml sections for rampart are the  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




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">

  
  
urn:uuid:xxx---- 


  
 

http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

 
  
  https://{url:443}
  
 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
  200401-wss-wssecurity-utility-1.0.xsd" 
wsu:Id="SecurityToken-xxx---

  -">
[username]
  
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username- 


  token-profile-1.0#PasswordText">
   [password]

 
  
  
   
...  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 and Apache CXF

[Bjorn Townsend]

Hello Shehan,

You might find this article I wrote for TheServerSide.com:

http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=885618

helpful. It was written some time ago so it is a bit outdated, both  
Axis2 and CXF have grown and matured a lot since then, but it might  
help give you the basic idea.


Bjorn


On Sep 30, 2008, at 5:59 PM  September 30, Shehan Simen wrote:


Hi Axis2 guys,
I was using axis2 for few months for work and found it quite handy.
What is apache CXF? Can someone please compare CXF and Axis2? So I  
can recommend the people to use Axis2 instead of CXF. Hope to hear  
soon.


Thanks.

Re: wsdl2java and basic authentication

[keith chapman]

Could you please file a JIRA please so that we will be able to fix this for
the next release.

Thanks,
Keith.

On Tue, Sep 30, 2008 at 8:51 PM, Jorge Medina <[EMAIL PROTECTED]> wrote:

>  I got it. There is a bug in version 1.4
>
>
>
> The same line works fine in version 1.3
>
>
>
>
>  --
>
> *From:* Jorge Medina [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, September 30, 2008 11:15 AM
> *To:* axis-user@ws.apache.org
> *Subject:* RE: wsdl2java and basic authentication
>
>
>
> No, I have the two computers in the same network, no firewall between them.
>
>
> The error wouldn't be 401 if the issue was a firewall, right?
>
>
>
> Nevertheless, I will repeat my test directly at the server.
>
>
>
>
>
> -Jorge
>
>
>  --
>
> *From:* Martin Gainty [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, September 30, 2008 11:09 AM
> *To:* Jorge Medina
> *Subject:* RE: wsdl2java and basic authentication
>
>
>
> appears you're behind a proxy server so
> you'll either need to specify WSDL2Java proxy settings e.g.
>   --http-proxy-hostProxy host address if you are behind a firewall
>   --http-proxy-portProxy prot address if you are behind a firewall
>
> or d/l the wsdl to an accessible file or webserver and use that
>
> Saludos Cordiales desde Mass
> Martin
> __
> Disclaimer and confidentiality note
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>  --
>
> Subject: wsdl2java and basic authentication
> Date: Tue, 30 Sep 2008 10:57:40 -0400
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
>
> Hi,
>
>   I have a Tomcat server (6.0.16) using basic authentication through a JDBC
> connection to a database.
>
>   The server runs in port 8080.
>
>
>
>I am trying to run wsdl2java against this server,
>
>
>
>> wsdl2java –uri http://ssmith:[EMAIL 
> PROTECTED]:8080/webservices/mywsdl.wsdl
> -s-uw -u
>
>
>
> but I get HTTP error 401:
>
>
>
> Retrieving document at '
> http://ssmith:[EMAIL PROTECTED]:8080/company
>
> -webservices/mywsdl.wsdl'.
>
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException
>
> : Error parsing WSDL
>
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
>
> ionEngine.java:156)
>
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
>
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
>
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR:
> Unabl
>
> e to resolve imported document at '
> http://ssmith:[EMAIL PROTECTED]:8
>
> 080/webservices/mywsdl.wsdl'.: java.io.IOException: Server retu
>
> rned HTTP response code: 401 for URL:
> http://ssmith:[EMAIL PROTECTED]
>
> m:8080/webservices/mywsdl.wsdl
>
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
>
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
>
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(
>
> CodeGenerationEngine.java:288)
>
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
>
> ionEngine.java:111)
>
> ... 2 more
>
> Caused by: java.io.IOException: Server returned HTTP response code: 401 for
> URL:
>
>  http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru
>
> dWsdl.wsdl
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
>
> nection.java:1241)
>
> at java.net.URL.openStream(URL.java:1009)
>
> at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
> Source)
>
>
>
> ... 6 more
>
>
>
>
>
> The same URL works perfectly fine in a browser.
>
> Is there any other way to specify the user and password required to get the
> WSDL when running wsdl2java?
>
>
>
> -Jorge
>
>
>
>
>
>
>  --
>
> Want to do more with Windows Live? Learn "10 hidden secrets" from Jamie. Learn
> Now
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: New to axis2, need some help

[keith chapman]

Which version of Axis2/ The eclipse plugin are you using?

Thanks,
Keith.

2008/9/30 Danny LIU <[EMAIL PROTECTED]>

> Hi everyone!
>
> Im a new learner of axis2, and basically Im following a tutorial to study
> it
> right now.
>
> My problem is I got a strange exception when I try to generate Java code
> from WSDL file
> using eclipse's plugin -Axis2 Code Generator .
> The exception is " java.lang.reflect.InvocationTargetException"
> does anyone know how to fix this?
>
> Thx in advance.
>
> Here is my wsdl code:
>
> 
> http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:tns="http://www.example.org/helloAxis2/";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="helloAxis2"
> targetNamespace="http://www.example.org/helloAxis2/";>
> 
>  targetNamespace="http://www.example.org/helloAxis2/";>
> 
> 
> 
> 
> 
>  name="Response" />
> 
> 
>  name="Request" />
> 
> 
> 
> 
> 
> 
> 
> 
>  transport="http://schemas.xmlsoap.org/soap/http"; />
> 
>  soapAction="
> http://localhost:8080/axis2/services/helloAxis2"; />
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> http://localhost:8080/axis2/services/helloAxis2"; />
> 
> 
> 
>
> --
>
>   天生万物以养人
>
> 人无一德以报天
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Axis2 and Apache CXF

[Shehan Simen]

Hi Axis2 guys,
I was using axis2 for few months for work and found it quite handy.
What is apache CXF? Can someone please compare CXF and Axis2? So I can 
recommend the people to use Axis2 instead of CXF. Hope to hear soon.

Thanks.

Re: Error "HTTP :unsupported content-encoding of 'identity' found"

[keith chapman]

We do not have a Axis2 release planned for any time soon. So you may have to
get the nightly.

Thanks,
Keith.

On Wed, Oct 1, 2008 at 1:33 AM, <[EMAIL PROTECTED]> wrote:

>  How can I get the jar and when will this change be in the official
> release.
>
>
> *Sangita Pandit*
> *728 1606*
>
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, September 30, 2008 12:31 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
> found"
>
>  I have fixed this in the transports module.
>
> Thanks,
> Keith.
>
> On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]> wrote:
>
>>  Also to be backwards compatible, AXIS2 has to support it as the AXIS did
>> not have issues like this.
>>
>>
>> *Sangita Pandit*
>> *728 1606*
>>
>>
>>  --
>> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>> *Sent:* Tuesday, September 30, 2008 4:20 AM
>> *To:* axis-user@ws.apache.org
>>  *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
>> found"
>>
>>   On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen <
>> [EMAIL PROTECTED]> wrote:
>>
>>> Googling for "Content-encoding: identity" reveals that this is actually
>>> quite common, so I guess that we should indeed support it.
>>
>>
>> Exactly. And we wont have to do much jsut ignore the content-type if its
>> identity.
>>
>> Thanks,
>> Keith .
>>
>>>
>>>
>>> Andreas
>>>
>>> keith chapman wrote:
>>>
 Interesting, It says SHOULD NOT but not MUST NOT. So it may be
 acceptable to have this header too. I guess one could argue that Axis2
 should ignore it if there is a header which says Content-encoding: 
 identity.
 WDYT?

 Thanks,
 Keith.

 On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen <
 [EMAIL PROTECTED] > wrote:

RFC2616, section 3.5 says the following about the identity content
encoding: "This content-coding is used only in the Accept-Encoding
header, and SHOULD NOT be used in the Content-Encoding header."
Assuming that the error is triggered by the Content-Encoding
header, the behavior of Axis2 in this particular case seems to be
acceptable.

Andreas


On 29 sept. 08, at 19:23, keith chapman wrote:

I just had a look at the code and it looks like we dont deal
with identity content encoding (whereas we should). Could you
use TCPMonitor to trace to request and response please. If you
want to use the TCPMonitor plugin this how to [1] would help.

Thanks,
Keith.

[1]

 http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html

On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED]
> wrote:
I generated the stubs using the WSDLToJava tool.

Sangita Pandit
728 1606



From: keith chapman [mailto:[EMAIL PROTECTED]
]
Sent: Monday, September 29, 2008 11:47 AM
To: axis-user@ws.apache.org 
Subject: Re: Error "HTTP :unsupported content-encoding of
'identity' found"

Hi,

How did you write the client for this service? Did you use
ServiceClient API or did you use a generated stub?

Thanks,
Keith.

On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED]
> wrote:
I am getting this error when webservice client is trying to
make a call to the webservice method.  I am using the released
version of Axis2 1.4.1. 


See stack trace here
org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
of 'identity' found
   at

  
 org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:223)
   at

  
 org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265)
   at

  
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
   at

  org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
   at

  
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)

   at

  
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
   at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
   at

  
 org.apache.axis2.description.OutInAxisO

Jgroups

[Igor Nogueira]

Hello guys!
I'd like to know if there's a way of invoking web services form Jgroups? I'd
like to have some services in group and send/receive messages to them
through Jgroups. As I'm working with replication, some of Jgroups features
would be very useful to me.

Thanks again,

Igor Nogueira Santos.

Re: Web Service requires secure header - how to generate with Axis?

[Mary Thompson]

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= Java 
option when you run the client, or set by a 
System.setProperty("axis2.xml", ) call in your program.  In my 
experience, the pathname needed to be relative to the classpath.


The axis2.xml sections for rampart are the  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




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">

  
  
urn:uuid:xxx---- 


  
 

http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

 
  
  https://{url:443}
  
 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
  200401-wss-wssecurity-utility-1.0.xsd" 
wsu:Id="SecurityToken-xxx---

  -">
[username]
  
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-

  token-profile-1.0#PasswordText">
   [password]

 
  
  
   
...  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Error when generating the proxies using xmlbeans

[Soyer, Muhammed A.]

Hi,
  I have a WSDL file which imports other WSDL files and they import XSD files. 
Looks like one of the XSD is being referred multiple times. I guess normally 
this shouldn't be an issue but when I use the xmlbeans binding I am getting an 
error saying that
I have "Duplicate global type ". When I use the default binding ADB I don't 
get an error message but I can't use ADB because of its limitations for 
inherited complex types.

  I am using axis2 1.4.1 . Do you have any suggestions to work around the issue?

Thanks


Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'.
Retrieving document at 'XClassService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'.
Retrieving document at 'XSpaService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'.
Retrieving document at 'XCustomer.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving document at 'XLocation.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'.
Retrieving document at 'XTee.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving document at 'XDiningService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'.
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'.
Retrieving document at 'XClassService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'.
Retrieving document at 'XSpaService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'.
Retrieving document at 'XCustomer.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving document at 'XLocation.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'.
Retrieving document at 'XTee.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving document at 'XDiningService.wsdl', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'.
Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'.
Retrieving schema at 'XReservationService.xsd', relative to 
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'.
[INFO] A SOAP port was not found - picking a random port!
[INFO] Resolving schema with publicId 
[http://schemas.zzz.com/OpenActivity/1/0/Reservation/] and systemId 
[XReservationService.xsd]
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.XMLBeansExtension.engage(XMLBeansExtension.java:126)
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
... 2 more
Caused by: java.lang.reflect.InvocationTargetEx

RE: Error "HTTP :unsupported content-encoding of 'identity' found"

[Sangita_Pandit]

How can I get the jar and when will this change be in the official
release.
 

Sangita Pandit 
728 1606 

 



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 12:31 PM
To: axis-user@ws.apache.org
Subject: Re: Error "HTTP :unsupported content-encoding of 'identity'
found"


I have fixed this in the transports module. 

Thanks,
Keith.


On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]> wrote:


Also to be backwards compatible, AXIS2 has to support it as the
AXIS did not have issues like this.
 

Sangita Pandit 
728 1606 

 



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 4:20 AM 

To: axis-user@ws.apache.org

Subject: Re: Error "HTTP :unsupported content-encoding of
'identity' found"


On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen
<[EMAIL PROTECTED]> wrote:


Googling for "Content-encoding: identity" reveals that
this is actually quite common, so I guess that we should indeed support
it.


Exactly. And we wont have to do much jsut ignore the
content-type if its identity.

Thanks,
Keith .




Andreas

keith chapman wrote:


Interesting, It says SHOULD NOT but not MUST
NOT. So it may be acceptable to have this header too. I guess one could
argue that Axis2 should ignore it if there is a header which says
Content-encoding: identity. WDYT?

Thanks,
Keith.


On Tue, Sep 30, 2008 at 12:01 AM, Andreas
Veithen <[EMAIL PROTECTED] >
wrote:

   RFC2616, section 3.5 says the following about
the identity content
   encoding: "This content-coding is used only
in the Accept-Encoding
   header, and SHOULD NOT be used in the
Content-Encoding header."
   Assuming that the error is triggered by the
Content-Encoding
   header, the behavior of Axis2 in this
particular case seems to be
   acceptable.

   Andreas


   On 29 sept. 08, at 19:23, keith chapman
wrote:

   I just had a look at the code and it
looks like we dont deal
   with identity content encoding (whereas
we should). Could you
   use TCPMonitor to trace to request and
response please. If you
   want to use the TCPMonitor plugin this
how to [1] would help.

   Thanks,
   Keith.

   [1]

http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-serv
ice.html

   On Mon, Sep 29, 2008 at 10:19 PM,
<[EMAIL PROTECTED]

   > wrote:
   I generated the stubs using the
WSDLToJava tool.

   Sangita Pandit
   728 1606



   From: keith chapman
[mailto:[EMAIL PROTECTED]
   ]
   Sent: Monday, September 29, 2008 11:47 AM

   To: axis-user@ws.apache.org
 

   Subject: Re: Error "HTTP :unsupported
content-encoding of
   'identity' found"

   Hi,

   How did you write the client for this
service? Did you use
   ServiceClient API or did you use a
generated stub?

   Thanks,
   Keith.

   On Mon, Sep 29, 2008 at 8:26 PM,
<[EMAIL PROTECTED]

   > wrote:
   I am getting this error when webservice
client is trying to
   make a call to the webservice method.  I
am using the released

   ver

Re: Web Service requires secure header - how to generate with Axis?

[Steve Cohen]

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 <[EMAIL PROTECTED] 
> 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?

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">

 
   
 urn:uuid:xxx----


 

 
 http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous


 
 https://{url:443}
 
http://docs.oasis-open.org/wss/2004/01/oasis-
 200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="SecurityToken-xxx---
 -">
   [username]
  
 Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-

 token-profile-1.0#PasswordText">
  [password]
   

 
 
  
...  





-
To unsubscribe, e-mail:
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]





--
Nandana Mihindukulasooriya  
WSO2 inc.


http://nandana83.blogspot.com/
http://www.wso2.org




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Web Service requires secure header - how to generate with Axis?

[Nandana Mihindukulasooriya]

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 <[EMAIL PROTECTED]>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?
>>>
>>> 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">
>>> 
>>>  
>>>
>>>  urn:uuid:xxx----
>>>
>>>  
>>> 
>>>
>>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>> 
>>>  
>>>  https://{url:443}
>>>  
>>> http://docs.oasis-open.org/wss/2004/01/oasis-
>>>  200401-wss-wssecurity-utility-1.0.xsd"
>>> wsu:Id="SecurityToken-xxx---
>>>  -">
>>>[username]
>>>>>  Type="
>>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
>>>  token-profile-1.0#PasswordText">
>>>   [password]
>>>
>>> 
>>>  
>>>  
>>>   
>>> ...  
>>> 
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

Re: Inheritance in WSDL

[Sagi Mann]

Hi, I know this is an old post, but did you find a solution?
thanks
-- 
View this message in context: 
http://www.nabble.com/Inheritance-in-WSDL-tp11831490p19747831.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

@XmlSeeAlso and/or parameter polymorphism

[Sagi Mann]

Hi,
Is there an axis2-equivalent for the JAXWS 2.1 @XmlSeeAlso annotation? I'm
trying to pass a polymorphic parameter to an axis2 web service, but
unfortunately I'm unable to find a way to get the web service to "publish"
the subclasses in its WSDL.

Example:
Assuming I have an AbstractBean, and a derived SubBean class, in JAXWS I
would be able to get the web service to "publish" the SubBean class in the
WSDL using the @XmlSeeAlso annotation:

@WebService
@XmlSeeAlso(SubBean.class)
public class Hello {
   @WebMethod
   // also correctly accepts subclasses of AbstractBean:
   public String testAbstractBeanArg(@WebParam AbstractBean bean) {
  return bean.toString(); 
   }
}

The resulting WSDL will contain both AbstractBean and SubBean in its schema:

















How do I do this in axis2? @XmlSeeAlso seems be ignored by axis2 web
services...

thanks

-- 
View this message in context: 
http://www.nabble.com/%40XmlSeeAlso-and-or-parameter-polymorphism-tp19747819p19747819.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisFault when using jibx

[Sagi Mann]

No problem. BTW, in the meantime, I switched to using jaxbri binding instead
of jibx.

The full web service code before all the additions of targetNamespace
annotation attributes is:

@WebService(
@XmlSeeAlso(SubBean.class)
public class Hello {

@WebMethod
public String testOneArg(@WebParam String name) { return "Hello " +
name; }

@WebMethod
public String testConcreteBeanArg(@WebParam ConcreteBean bean) {
return "concrete bean: " + bean.getClass().getName() + " " +
bean.toString() +
"[" +
" name=" + bean.getName() +
"]";
}

@WebMethod
public String testAbstractBeanArg(@WebParam AbstractBean bean) {
return "abstract bean: " + bean.getClass().getName() + " " +
bean.toString();
}

@WebMethod
public String testException(@WebParam AbstractBean bean) throws
BeanException {
if (bean.getColor().equals("black")) throw new BeanException("Black
exception");
return "abstract bean: " + bean.getClass().getName() + " " +
bean.toString();
}
}



The resulting full schema as generated by JAXW 2.1 over GlassFish v2
runtime, built with NetBeans 5.5.1 is:


http://ws/";
xmlns:xs="http://www.w3.org/2001/XMLSchema"; version="1.0"
targetNamespace="http://ws/";>
































































































Hope this helps...

-- 
View this message in context: 
http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19747689.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error "HTTP :unsupported content-encoding of 'identity' found"

[keith chapman]

I have fixed this in the transports module.

Thanks,
Keith.

On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]> wrote:

>  Also to be backwards compatible, AXIS2 has to support it as the AXIS did
> not have issues like this.
>
>
> *Sangita Pandit*
> *728 1606*
>
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, September 30, 2008 4:20 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity'
> found"
>
>  On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen <
> [EMAIL PROTECTED]> wrote:
>
>> Googling for "Content-encoding: identity" reveals that this is actually
>> quite common, so I guess that we should indeed support it.
>
>
> Exactly. And we wont have to do much jsut ignore the content-type if its
> identity.
>
> Thanks,
> Keith .
>
>>
>>
>> Andreas
>>
>> keith chapman wrote:
>>
>>> Interesting, It says SHOULD NOT but not MUST NOT. So it may be acceptable
>>> to have this header too. I guess one could argue that Axis2 should ignore it
>>> if there is a header which says Content-encoding: identity. WDYT?
>>>
>>> Thanks,
>>> Keith.
>>>
>>> On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen <
>>> [EMAIL PROTECTED] > wrote:
>>>
>>>RFC2616, section 3.5 says the following about the identity content
>>>encoding: "This content-coding is used only in the Accept-Encoding
>>>header, and SHOULD NOT be used in the Content-Encoding header."
>>>Assuming that the error is triggered by the Content-Encoding
>>>header, the behavior of Axis2 in this particular case seems to be
>>>acceptable.
>>>
>>>Andreas
>>>
>>>
>>>On 29 sept. 08, at 19:23, keith chapman wrote:
>>>
>>>I just had a look at the code and it looks like we dont deal
>>>with identity content encoding (whereas we should). Could you
>>>use TCPMonitor to trace to request and response please. If you
>>>want to use the TCPMonitor plugin this how to [1] would help.
>>>
>>>Thanks,
>>>Keith.
>>>
>>>[1]
>>>
>>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>>>
>>>On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED]
>>>> wrote:
>>>I generated the stubs using the WSDLToJava tool.
>>>
>>>Sangita Pandit
>>>728 1606
>>>
>>>
>>>
>>>From: keith chapman [mailto:[EMAIL PROTECTED]
>>>]
>>>Sent: Monday, September 29, 2008 11:47 AM
>>>To: axis-user@ws.apache.org 
>>>Subject: Re: Error "HTTP :unsupported content-encoding of
>>>'identity' found"
>>>
>>>Hi,
>>>
>>>How did you write the client for this service? Did you use
>>>ServiceClient API or did you use a generated stub?
>>>
>>>Thanks,
>>>Keith.
>>>
>>>On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED]
>>>> wrote:
>>>I am getting this error when webservice client is trying to
>>>make a call to the webservice method.  I am using the released
>>>version of Axis2 1.4.1. 
>>>
>>>
>>>See stack trace here
>>>org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
>>>of 'identity' found
>>>   at
>>>
>>>  
>>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:223)
>>>   at
>>>
>>>  
>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265)
>>>   at
>>>
>>>  org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
>>>   at
>>>
>>>  org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>>>   at
>>>
>>>  
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
>>>
>>>   at
>>>
>>>  
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
>>>   at
>>>org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
>>>   at
>>>
>>>  
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
>>>   at
>>>
>>>  
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>>>   at
>>>
>>>  org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>>>   at
>>>
>>>  
>>> com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusServiceStub.java:1056)
>>>   at
>>>
>>>  
>>> com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatusServiceTest.java:37)
>>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>Method)
>>>   at
>>>
>>>  
>>> sun.reflect.NativeMethodAccessorImpl.

RE: axis2 1.3 stackoverflow

[omatzura]

Hi Tony,

Ole from the soapUI team here. This sounds more like an error in soapUI to
me, it shouldn't receive the WSDL for each time it asserts the response, and
probably is not releasing the previously retreived WSDLs correctly.. could
you check if this problem persists in our newly release 2.5 beta1 version
and mail me your findings ([EMAIL PROTECTED])?

Thanks for your help..

regards!

/Ole
eviware.com


Tony Dean wrote:
> 
> there must be some issues with wsdl4j... I'm using soapUI to perform some
> load testing and if I turn off SOAP compliance assertion, the problems go
> away.  With SOAP compliance assertion, soapUI continuously retrieves the
> WSDL from the service to assert the response message.  Turning this off
> takes wsdl4j out of the picture and no errors.
> 
>> -Original Message-
>> From: Tony Dean [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, September 27, 2008 9:34 PM
>> To: axis-user@ws.apache.org
>> Subject: RE: axis2 1.3 stackoverflow
>>
>> this appears to be in the Axis2 code before my implementation is
>> dispatched...
>>
>> > -Original Message-
>> > From: Nan Null [mailto:[EMAIL PROTECTED]
>> > Sent: Saturday, September 27, 2008 8:10 PM
>> > To: axis-user@ws.apache.org
>> > Subject: Re: axis2 1.3 stackoverflow
>> >
>> > Do you have database connection involved?  Look like you have
>> resource
>> > sharing problem.  If it's not database, then make sure you
>> > synchronized where needed.  If it's database, make sure to use
>> > connection pool, and try..finally to release all connections
>> properly.
>> > I would comment out all code, except returning empty result.  Then
>> > progressively uncomment code to find out where causes the problem.
>> >
>> > On Sat, Sep 27, 2008 at 7:25 PM, Tony Dean <[EMAIL PROTECTED]> wrote:
>> > > I have seen numerous jira issues regarding stackoverflow...
>> > >
>> > > A single client accessing my Axis2 service is successful and
>> appears
>> > to be successful an unlimited amount of iterations.
>> > >
>> > > However, if I put a load on the service and allow multiple clients
>> to
>> > access my service simultaneously, it does take long for
>> stackoverflows
>> > to occur.  I'm getting a consistent stacktrace as follows:
>> > >
>> > > 08:25:00,237 ERROR [[AxisServlet]] Servlet.service() for servlet
>> > AxisServlet thre
>> > > java.lang.StackOverflowError
>> > >at
>> > java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:544)
>> > >at
>> > sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:384)
>> > >at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
>> > >at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
>> > >at
>> > java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
>> > >at java.io.PrintWriter.write(PrintWriter.java:384)
>> > >at java.io.PrintWriter.write(PrintWriter.java:384)
>> > >at java.io.PrintWriter.write(PrintWriter.java:401)
>> > >at java.io.PrintWriter.print(PrintWriter.java:532)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
>> > >
>> > >
>> > > Anyone know what's going on?
>> > >
>> > > Thanks for any insight.
>> > >
>> > > Tony Dean
>> > > SAS Institute Inc.
>> > > 919.531.6704
>> > > [EMAIL PROTECTED]
>> > >
>> > > SAS... The Power to Know
>> > > http://www.sas.com
>> > >
>> > >
>> > >
>> > > ---
>> --
>> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > > For additional commands, e-mail: [EMAIL PROTECTED]
>> > >
>> > >
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/axis2-1.3-stackoverflow-tp19707394p19746513.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL2Java behavior

[Steve Cohen]

I'm not sure.  I now see that each xxx_type1 class uses the xxx_type0.

In any case, the WSDL in question is available here:

https://duoshare.com/dsWS/services/PostML/wsdl


Martin Gainty wrote:

Good Morning Mr Cohen

there appears to be a double definition for City and State entities
can you display the WSDL so we can reproduce here?

thanks
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official 
business of Sender. This transmission is of a confidential nature and 
Sender does not endorse distribution to any party other than intended 
recipient. Sender does not necessarily endorse content contained 
within this transmission.



> Date: Tue, 30 Sep 2008 10:16:14 -0500
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: WSDL2Java behavior
>
> running command line WSDL2Java, (axis2 1.4.1) with following options
>
> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion
> 1.5 -uri {my wsdl}
>
>
> I find the following source code generation pattern:
> In reasonable packages under source, it generates data classes from the
> WSDL, say com.whatever.City1.java
> com.whatever.State1.java
>
> But it also generates (in the default package)
> City0.java
> State0.java
>
> What could be causing it to generate these extra classes in the default
> package and is there anything I can or should do about it.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


Stay up to date on your PC, the Web, and your mobile phone with 
Windows Live. See Now 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Web Service requires secure header - how to generate with Axis?

[Steve Cohen]

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?


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">

  
  
urn:uuid:xxx---- 


  
 

http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

 
  
  https://{url:443}
  
 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-
  200401-wss-wssecurity-utility-1.0.xsd" 
wsu:Id="SecurityToken-xxx---

  -">
[username]
  
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-

  token-profile-1.0#PasswordText">
   [password]

 
  
  
   
...  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: ModulePolicyExtension

[Srisathya Thirumalai]

 
Downloading Rampart 1.4 and using its mar and jar files and removing 
axis2-security-1.1.jar file solved the problem.
 
Thanks> Date: Tue, 30 Sep 2008 13:04:42 +0530> From: [EMAIL PROTECTED]> To: 
axis-user@ws.apache.org> Subject: Re: ModulePolicyExtension> > Hi,> > This 
occurs because Rampart version is not compatible with Axis2 version.> > You 
have to use Rampart 1.4 with Axis2 1.4. Or if you are using older > Axis2 
versions use the relevant Rampart jars and modules.> > Thank you,> Dimuthu> > 
Srisathya Thirumalai wrote:> > Hello,> > I am trying to refer to rampart module 
from axis2.xml. It fails saying> > > > ERROR ModuleDeployer:108 - The 
rampart-1.1.mar module, which is not > > valid, caused 
org/apache/axis2/modules/ModulePolicyExtension> > 
java.lang.NoClassDefFoundError: > > 
org/apache/axis2/modules/ModulePolicyExtension> > .> > .> > ERROR 
ModuleDeployer:108 - The axis2-security-1.1.jar module, which is > > not valid, 
caused org/apache/axis2/modules/ModulePolicyExtension> > 
java.lang.NoClassDefFoundError: > > 
org/apache/axis2/modules/ModulePolicyExtension> > > > I don't see a 
ModulePolicyExtension class anywhere in any of the jar > > files I have. I have 
camong other axis2 jar > > files in my lib folder and I have rampart-1.1.mar 
and > > addressing-1.41.mar in my modules folder.> > > > Any ideas?> > > > 
Thanks> > > > > >> > 
> > Get 
more out of the Web. Learn 10 hidden secrets of Windows Live. > > Learn Now > > 
>
 > > -> To 
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL 
PROTECTED]> 
_
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/

RE: WSDL2Java behavior

[Martin Gainty]

Good Morning Mr Cohen

there appears to be a double definition for City and State entities
can you display the WSDL so we can reproduce here?

thanks
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


> Date: Tue, 30 Sep 2008 10:16:14 -0500
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: WSDL2Java behavior
> 
> running command line WSDL2Java, (axis2 1.4.1) with following options
> 
> -o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion 
> 1.5 -uri {my wsdl}
> 
> 
> I find the following source code generation pattern:
> In reasonable packages under source, it generates data classes from the 
> WSDL, say   com.whatever.City1.java
> com.whatever.State1.java
> 
> But it also generates (in the default package)
> City0.java
> State0.java
> 
> What could be causing it to generate these extra classes in the default 
> package and is there anything I can or should do about it.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/

RE: wsdl2java and basic authentication

[Jorge Medina]

Actually, I only tested with version 1.4.1 and version 1.3

Version 1.3 works fine

 



From: Jorge Medina [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:22 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl2java and basic authentication

 

I got it. There is a bug in version 1.4

 

The same line works fine in version 1.3

 

 



From: Jorge Medina [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:15 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl2java and basic authentication

 

No, I have the two computers in the same network, no firewall between
them. 

The error wouldn't be 401 if the issue was a firewall, right?

 

Nevertheless, I will repeat my test directly at the server.

 

 

-Jorge

 



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:09 AM
To: Jorge Medina
Subject: RE: wsdl2java and basic authentication

 

appears you're behind a proxy server so 
you'll either need to specify WSDL2Java proxy settings e.g.
  --http-proxy-hostProxy host address if you are behind a
firewall
  --http-proxy-portProxy prot address if you are behind a
firewall

or d/l the wsdl to an accessible file or webserver and use that

Saludos Cordiales desde Mass
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 



Subject: wsdl2java and basic authentication
Date: Tue, 30 Sep 2008 10:57:40 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Hi, 

  I have a Tomcat server (6.0.16) using basic authentication through a
JDBC connection to a database.

  The server runs in port 8080.

 

   I am trying to run wsdl2java against this server, 

 

   > wsdl2java -uri
http://ssmith:[EMAIL PROTECTED]:8080/webservices/mywsdl.wsdl -s
-uw -u

 

but I get HTTP error 401:

 

Retrieving document at
'http://ssmith:[EMAIL PROTECTED]:8080/company

-webservices/mywsdl.wsdl'.

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException

: Error parsing WSDL

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:156)

at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)

at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)

Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=OTHER_ERROR: Unabl

e to resolve imported document at
'http://ssmith:[EMAIL PROTECTED]:8

080/webservices/mywsdl.wsdl'.: java.io.IOException: Server retu

rned HTTP response code: 401 for URL:
http://ssmith:[EMAIL PROTECTED]

m:8080/webservices/mywsdl.wsdl

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(

CodeGenerationEngine.java:288)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:111)

... 2 more

Caused by: java.io.IOException: Server returned HTTP response code: 401
for URL:

 http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru

dWsdl.wsdl

at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:1241)

at java.net.URL.openStream(URL.java:1009)

at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
Source)

 

... 6 more

 

 

The same URL works perfectly fine in a browser.

Is there any other way to specify the user and password required to get
the WSDL when running wsdl2java?

 

-Jorge

 

 

 



Want to do more with Windows Live? Learn "10 hidden secrets" from Jamie.
Learn Now
 

RE: wsdl2java and basic authentication

[Martin Gainty]

it seems you have found a malicious bug..please let us know how to remove 

thanks
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Subject: RE: wsdl2java and basic authentication
Date: Tue, 30 Sep 2008 11:21:31 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org



















I got it. There is a bug in version 1.4

 

The same line works fine in version 1.3

 

 









From: Jorge Medina
[mailto:[EMAIL PROTECTED] 

Sent: Tuesday, September 30, 2008 11:15
AM

To: axis-user@ws.apache.org

Subject: RE: wsdl2java and basic
authentication



 

No, I have the two computers in the same
network, no firewall between them. 

The error wouldn’t be 401 if the
issue was a firewall, right?

 

Nevertheless, I will repeat my test
directly at the server.

 

 

-Jorge

 









From: Martin Gainty
[mailto:[EMAIL PROTECTED] 

Sent: Tuesday, September 30, 2008
11:09 AM

To: Jorge Medina

Subject: RE: wsdl2java and basic
authentication



 

appears you're behind a proxy
server so 

you'll either need to specify WSDL2Java proxy settings e.g.

  --http-proxy-hostProxy host
address if you are behind a firewall

  --http-proxy-portProxy prot
address if you are behind a firewall



or d/l the wsdl to an accessible file or webserver and use that



Saludos Cordiales desde Mass

Martin 

__ 

Disclaimer and confidentiality note 

Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission. 







Subject: wsdl2java and basic
authentication

Date: Tue, 30 Sep 2008 10:57:40 -0400

From: [EMAIL PROTECTED]

To: axis-user@ws.apache.org



Hi, 

  I have a Tomcat server (6.0.16) using basic
authentication through a JDBC connection to a database.

  The server runs in port 8080.

 

   I am trying to run wsdl2java against this
server, 

 

   >
wsdl2java –uri http://ssmith:[EMAIL PROTECTED]:8080/webservices/mywsdl.wsdl
-s -uw -u

 

but I get HTTP error 401:

 

Retrieving document at
'http://ssmith:[EMAIL PROTECTED]:8080/company

-webservices/mywsdl.wsdl'.

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException

: Error parsing WSDL

   
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:156)

   
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)

   
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)

Caused by: javax.wsdl.WSDLException:
WSDLException: faultCode=OTHER_ERROR: Unabl

e to resolve imported document at
'http://ssmith:[EMAIL PROTECTED]:8

080/webservices/mywsdl.wsdl'.:
java.io.IOException: Server retu

rned HTTP response code: 401 for
URL: http://ssmith:[EMAIL PROTECTED]

m:8080/webservices/mywsdl.wsdl

   
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

   
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

   
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(

CodeGenerationEngine.java:288)

   
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:111)

   
... 2 more

Caused by: java.io.IOException:
Server returned HTTP response code: 401 for URL:

 http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru

dWsdl.wsdl

   
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:1241)

   
at java.net.URL.openStream(URL.java:1009)

   
at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source)

 

   
... 6 more

 

 

The same URL works perfectly fine in a browser.

Is there any other way to specify the user and password required
to get the WSDL when running wsdl2java?

 

-Jorge

 

 



 







Want to do more with Windows Live? Learn “10 hidden
secrets” from Jamie. Learn Now







_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/

RE: wsdl2java and basic authentication

[Jorge Medina]

I got it. There is a bug in version 1.4

 

The same line works fine in version 1.3

 

 



From: Jorge Medina [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:15 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl2java and basic authentication

 

No, I have the two computers in the same network, no firewall between
them. 

The error wouldn't be 401 if the issue was a firewall, right?

 

Nevertheless, I will repeat my test directly at the server.

 

 

-Jorge

 



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:09 AM
To: Jorge Medina
Subject: RE: wsdl2java and basic authentication

 

appears you're behind a proxy server so 
you'll either need to specify WSDL2Java proxy settings e.g.
  --http-proxy-hostProxy host address if you are behind a
firewall
  --http-proxy-portProxy prot address if you are behind a
firewall

or d/l the wsdl to an accessible file or webserver and use that

Saludos Cordiales desde Mass
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 



Subject: wsdl2java and basic authentication
Date: Tue, 30 Sep 2008 10:57:40 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Hi, 

  I have a Tomcat server (6.0.16) using basic authentication through a
JDBC connection to a database.

  The server runs in port 8080.

 

   I am trying to run wsdl2java against this server, 

 

   > wsdl2java -uri
http://ssmith:[EMAIL PROTECTED]:8080/webservices/mywsdl.wsdl -s
-uw -u

 

but I get HTTP error 401:

 

Retrieving document at
'http://ssmith:[EMAIL PROTECTED]:8080/company

-webservices/mywsdl.wsdl'.

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException

: Error parsing WSDL

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:156)

at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)

at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)

Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=OTHER_ERROR: Unabl

e to resolve imported document at
'http://ssmith:[EMAIL PROTECTED]:8

080/webservices/mywsdl.wsdl'.: java.io.IOException: Server retu

rned HTTP response code: 401 for URL:
http://ssmith:[EMAIL PROTECTED]

m:8080/webservices/mywsdl.wsdl

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(

CodeGenerationEngine.java:288)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:111)

... 2 more

Caused by: java.io.IOException: Server returned HTTP response code: 401
for URL:

 http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru

dWsdl.wsdl

at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:1241)

at java.net.URL.openStream(URL.java:1009)

at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
Source)

 

... 6 more

 

 

The same URL works perfectly fine in a browser.

Is there any other way to specify the user and password required to get
the WSDL when running wsdl2java?

 

-Jorge

 

 

 



Want to do more with Windows Live? Learn "10 hidden secrets" from Jamie.
Learn Now
 

WSDL2Java behavior

[Steve Cohen]

running command line WSDL2Java, (axis2 1.4.1) with following options

-o {root of my source tree} -t -d adb -u -ssi -wv 1.1 -or -Ejavaversion 
1.5 -uri {my wsdl}



I find the following source code generation pattern:
In reasonable packages under source, it generates data classes from the 
WSDL, say   com.whatever.City1.java

com.whatever.State1.java

But it also generates (in the default package)
City0.java
State0.java

What could be causing it to generate these extra classes in the default 
package and is there anything I can or should do about it.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: wsdl2java and basic authentication

[Jorge Medina]

No, I have the two computers in the same network, no firewall between
them. 

The error wouldn't be 401 if the issue was a firewall, right?

 

Nevertheless, I will repeat my test directly at the server.

 

 

-Jorge

 



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 11:09 AM
To: Jorge Medina
Subject: RE: wsdl2java and basic authentication

 

appears you're behind a proxy server so 
you'll either need to specify WSDL2Java proxy settings e.g.
  --http-proxy-hostProxy host address if you are behind a
firewall
  --http-proxy-portProxy prot address if you are behind a
firewall

or d/l the wsdl to an accessible file or webserver and use that

Saludos Cordiales desde Mass
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 





Subject: wsdl2java and basic authentication
Date: Tue, 30 Sep 2008 10:57:40 -0400
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org

Hi, 

  I have a Tomcat server (6.0.16) using basic authentication through a
JDBC connection to a database.

  The server runs in port 8080.

 

   I am trying to run wsdl2java against this server, 

 

   > wsdl2java -uri
http://ssmith:[EMAIL PROTECTED]:8080/webservices/mywsdl.wsdl -s
-uw -u

 

but I get HTTP error 401:

 

Retrieving document at
'http://ssmith:[EMAIL PROTECTED]:8080/company

-webservices/mywsdl.wsdl'.

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException

: Error parsing WSDL

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:156)

at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)

at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)

Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=OTHER_ERROR: Unabl

e to resolve imported document at
'http://ssmith:[EMAIL PROTECTED]:8

080/webservices/mywsdl.wsdl'.: java.io.IOException: Server retu

rned HTTP response code: 401 for URL:
http://ssmith:[EMAIL PROTECTED]

m:8080/webservices/mywsdl.wsdl

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(

CodeGenerationEngine.java:288)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:111)

... 2 more

Caused by: java.io.IOException: Server returned HTTP response code: 401
for URL:

 http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru

dWsdl.wsdl

at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:1241)

at java.net.URL.openStream(URL.java:1009)

at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
Source)

 

... 6 more

 

 

The same URL works perfectly fine in a browser.

Is there any other way to specify the user and password required to get
the WSDL when running wsdl2java?

 

-Jorge

 

 

 



Want to do more with Windows Live? Learn "10 hidden secrets" from Jamie.
Learn Now
 

RE: axis2 1.3 stackoverflow

[Tony Dean]

there must be some issues with wsdl4j... I'm using soapUI to perform some load 
testing and if I turn off SOAP compliance assertion, the problems go away.  
With SOAP compliance assertion, soapUI continuously retrieves the WSDL from the 
service to assert the response message.  Turning this off takes wsdl4j out of 
the picture and no errors.

> -Original Message-
> From: Tony Dean [mailto:[EMAIL PROTECTED]
> Sent: Saturday, September 27, 2008 9:34 PM
> To: axis-user@ws.apache.org
> Subject: RE: axis2 1.3 stackoverflow
>
> this appears to be in the Axis2 code before my implementation is
> dispatched...
>
> > -Original Message-
> > From: Nan Null [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, September 27, 2008 8:10 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: axis2 1.3 stackoverflow
> >
> > Do you have database connection involved?  Look like you have
> resource
> > sharing problem.  If it's not database, then make sure you
> > synchronized where needed.  If it's database, make sure to use
> > connection pool, and try..finally to release all connections
> properly.
> > I would comment out all code, except returning empty result.  Then
> > progressively uncomment code to find out where causes the problem.
> >
> > On Sat, Sep 27, 2008 at 7:25 PM, Tony Dean <[EMAIL PROTECTED]> wrote:
> > > I have seen numerous jira issues regarding stackoverflow...
> > >
> > > A single client accessing my Axis2 service is successful and
> appears
> > to be successful an unlimited amount of iterations.
> > >
> > > However, if I put a load on the service and allow multiple clients
> to
> > access my service simultaneously, it does take long for
> stackoverflows
> > to occur.  I'm getting a consistent stacktrace as follows:
> > >
> > > 08:25:00,237 ERROR [[AxisServlet]] Servlet.service() for servlet
> > AxisServlet thre
> > > java.lang.StackOverflowError
> > >at
> > java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:544)
> > >at
> > sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:384)
> > >at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
> > >at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
> > >at
> > java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
> > >at java.io.PrintWriter.write(PrintWriter.java:384)
> > >at java.io.PrintWriter.write(PrintWriter.java:384)
> > >at java.io.PrintWriter.write(PrintWriter.java:401)
> > >at java.io.PrintWriter.print(PrintWriter.java:532)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> > >
> > >
> > > Anyone know what's going on?
> > >
> > > Thanks for any insight.
> > >
> > > Tony Dean
> > > SAS Institute Inc.
> > > 919.531.6704
> > > [EMAIL PROTECTED]
> > >
> > > SAS... The Power to Know
> > > http://www.sas.com
> > >
> > >
> > >
> > > ---
> --
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

wsdl2java and basic authentication

[Jorge Medina]

Hi, 

  I have a Tomcat server (6.0.16) using basic authentication through a
JDBC connection to a database.

  The server runs in port 8080.

 

   I am trying to run wsdl2java against this server, 

 

   > wsdl2java -uri
http://ssmith:[EMAIL PROTECTED]:8080/webservices/mywsdl.wsdl -s
-uw -u

 

but I get HTTP error 401:

 

Retrieving document at
'http://ssmith:[EMAIL PROTECTED]:8080/company

-webservices/mywsdl.wsdl'.

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException

: Error parsing WSDL

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:156)

at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)

at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)

Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=OTHER_ERROR: Unabl

e to resolve imported document at
'http://ssmith:[EMAIL PROTECTED]:8

080/webservices/mywsdl.wsdl'.: java.io.IOException: Server retu

rned HTTP response code: 401 for URL:
http://ssmith:[EMAIL PROTECTED]

m:8080/webservices/mywsdl.wsdl

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(

CodeGenerationEngine.java:288)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat

ionEngine.java:111)

... 2 more

Caused by: java.io.IOException: Server returned HTTP response code: 401
for URL:

 http://ssmith:[EMAIL PROTECTED]:8080/webservices/mailingCru

dWsdl.wsdl

at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon

nection.java:1241)

at java.net.URL.openStream(URL.java:1009)

at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
Source)

 

... 6 more

 

 

The same URL works perfectly fine in a browser.

Is there any other way to specify the user and password required to get
the WSDL when running wsdl2java?

 

-Jorge

 

 

New to axis2, need some help

[Danny LIU]

Hi everyone!

Im a new learner of axis2, and basically Im following a tutorial to study it
right now.

My problem is I got a strange exception when I try to generate Java code
from WSDL file
using eclipse's plugin -Axis2 Code Generator .
The exception is " java.lang.reflect.InvocationTargetException"
does anyone know how to fix this?

Thx in advance.

Here is my wsdl code:


http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:tns="http://www.example.org/helloAxis2/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="helloAxis2"
targetNamespace="http://www.example.org/helloAxis2/";>

http://www.example.org/helloAxis2/";>

















http://schemas.xmlsoap.org/soap/http"; />

http://localhost:8080/axis2/services/helloAxis2";
/>










http://localhost:8080/axis2/services/helloAxis2"; />




-- 

  天生万物以养人

人无一德以报天

RE: Error "HTTP :unsupported content-encoding of 'identity' found"

[Sangita_Pandit]

Also to be backwards compatible, AXIS2 has to support it as the AXIS did
not have issues like this.
 

Sangita Pandit 
728 1606 

 



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2008 4:20 AM
To: axis-user@ws.apache.org
Subject: Re: Error "HTTP :unsupported content-encoding of 'identity'
found"


On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen
<[EMAIL PROTECTED]> wrote:


Googling for "Content-encoding: identity" reveals that this is
actually quite common, so I guess that we should indeed support it.


Exactly. And we wont have to do much jsut ignore the content-type if its
identity.

Thanks,
Keith .




Andreas

keith chapman wrote:


Interesting, It says SHOULD NOT but not MUST NOT. So it
may be acceptable to have this header too. I guess one could argue that
Axis2 should ignore it if there is a header which says Content-encoding:
identity. WDYT?

Thanks,
Keith.


On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen
<[EMAIL PROTECTED] > wrote:

   RFC2616, section 3.5 says the following about the
identity content
   encoding: "This content-coding is used only in the
Accept-Encoding
   header, and SHOULD NOT be used in the
Content-Encoding header."
   Assuming that the error is triggered by the
Content-Encoding
   header, the behavior of Axis2 in this particular case
seems to be
   acceptable.

   Andreas


   On 29 sept. 08, at 19:23, keith chapman wrote:

   I just had a look at the code and it looks like
we dont deal
   with identity content encoding (whereas we
should). Could you
   use TCPMonitor to trace to request and response
please. If you
   want to use the TCPMonitor plugin this how to [1]
would help.

   Thanks,
   Keith.

   [1]

http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-serv
ice.html

   On Mon, Sep 29, 2008 at 10:19 PM,
<[EMAIL PROTECTED]

   > wrote:
   I generated the stubs using the WSDLToJava tool.

   Sangita Pandit
   728 1606



   From: keith chapman
[mailto:[EMAIL PROTECTED]
   ]
   Sent: Monday, September 29, 2008 11:47 AM

   To: axis-user@ws.apache.org
 

   Subject: Re: Error "HTTP :unsupported
content-encoding of
   'identity' found"

   Hi,

   How did you write the client for this service?
Did you use
   ServiceClient API or did you use a generated
stub?

   Thanks,
   Keith.

   On Mon, Sep 29, 2008 at 8:26 PM,
<[EMAIL PROTECTED]

   > wrote:
   I am getting this error when webservice client is
trying to
   make a call to the webservice method.  I am using
the released

   version of Axis2 1.4.1.  


   See stack trace here
   org.apache.axis2.AxisFault: HTTP :unsupported
content-encoding
   of 'identity' found
  at

org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(Abstr
actHTTPSender.java:223)
  at

org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.jav
a:265)
  at

org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1
90)
  at

org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
  at

org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
ithCommons(CommonsHTTPTransportSender.java:371)

  at

org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:209)
  at

org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
   

Re: axis2 1.4 and later versions fail to deploy with Java 1.4.2 under RAD6/WAS6.0

[Ramesh Vishwanatham]

Brian
Thanks for replying to my post. I have commented "threadContextMigrators" 
part and other places where jaxws was mentioned in axis2.xml file to make 
it work with RAD6 using Java 1.4. When I first tried comment out 
threadContextMigrators part, I still got errors and then I did all others 
in the file.

Regards
Ramesh Vishwanatham




Brian De Pradine <[EMAIL PROTECTED]> 
09/30/2008 06:16 AM
Please respond to
axis-user@ws.apache.org


To
axis-user@ws.apache.org
cc

Subject
Re: axis2 1.4 and later versions fail to deploy with Java 1.4.2 under 
RAD6/WAS6.0







Hi Ramesh, 

In order to get Axis2 1.4 to work with Java 1.4 you need to comment out 
the following in your axis2.xml file: 

 
 

 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Ramesh Vishwanatham <[EMAIL PROTECTED]> wrote on 29/09/2008 22:26:33:

> 
> Hi 
> I have tried to deploy Axis2 1.4 and 1.4.1 versions in RAD6 using 
> Java 1.4.2 and was getting below error message: 
> 
> [9/29/08 13:50:19:706 EDT] 0022 ApplicationMg A   WSVR0200I: 
> Starting application: axis214EAR 
> [9/29/08 13:50:20:018 EDT] 0022 WebGroup  A   SRVE0169I: 
> Loading Web Module: Apache-Axis2. 
> [9/29/08 13:50:21:049 EDT] 0022 ServletWrappe E   SRVE0100E: Did
> not realize  init() exception thrown by servlet AxisServlet: java.
> lang.LinkageError: LinkageError while defining class: org.apache.
> axis2.jaxws.addressing.migrator.EndpointContextMapMigrator 
> Could not be defined due to: 
> org/apache/axis2/jaxws/addressing/migrator/EndpointContextMapMigrator
> (Unsupported major.minor version 49.0) 
> This is often caused by having a class defined at multiple 
> locations within the classloader hierarchy.  Other potential causes 
> include compiling against an older or newer version of the class 
> 
> 
> After some effort and search on web I have realized that error was 
> caused because of JAXWS introduction in axis2 1.4 version and it 
> will need Java 1.5 annotations. I have commented all the instances 
> of jaxws in axis2.xml file (total 7 places) and retried deploying 
> axis2.war file in RAD6 and was successful. 
> 
> I was able to deploy successfully axis2.war version 1.1 and 1.3 in 
> RAD6 environment. I would like to know is the axis2 1.4 and later 
> versions only suppose to work under Java 1.5? Also I see on axis2 1.
> 4 web page saying that it should work with Java 1.4 or later, is it 
> still a goal of axis2 development team. 
> 
> If someone from axis2 team can clarify these issues and guide me If 
> I need to deploy axis2 1.4 or newer versions under Java 1.4 under 
> RAD6 without modifying the axis2.xml file. 
> 
> Thanks in advance for looking into this matter. 
> 
> Ramesh Vishwanatham 
>  
> DTCC DISCLAIMER: This email and any files transmitted with it are 
> confidential and intended solely for the use of the individual or 
> entity to whom they are addressed. If you have received this email 
> in error, please notify us immediately and delete the email and any 
> attachments from your system. The recipient should check this email 
> and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this 
email.




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 








-

DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email
in error, please notify us immediately and delete the email and any
attachments from your system. The recipient should check this email
and any attachments for the presence of viruses.  The company
accepts no liability for any damage caused by any virus transmitted
by this email.

HELP!!! - Axis 2 1.4 CodeGenerator Eclipse Plugin fails

[Steve Cohen]

I ran the eclipse plugin wizard to generate Java from a WSDL and it 
failed with


"An error occurred while completing process - 
java.lang.reflect.InvocationTargetException"


upon pressing Finish.

Platform is Ubuntu Linux 7.10
Eclipse is version 3.3.2

I noticed that the plugin code I had was not the most recent, so I 
removed this plugin from my eclipse plugins directory and downloaded the 
latest from the site, and placed it back in the plugins directory.


Now the wizard fails immediately upon launch as follows:

The selected wizard could not be started.

Plug-in Axis2_Codegen_Wizard was unable to load class 
org.apache.axis2.tool.codegen.eclipse.CodeGenWizard


Ironically, before I tried using this wizard I was making some progress 
with the command line tool.  I thought this would be easier.  Geez.


Can someone explain what I need to make this plugin work?  Or would I be 
better off just using the command line tool.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

issue with digital signature and MTOM

[Srihari]

Hi,
I am having issue with digital signature with MTOM format.
i am using Axis for my server side service.

When I use Axis client it works but when I use the CXF client it failed with
"The signature or decryption was invalid".  Can you please help me what I am
doing wrong.

here are the various requests;

*Request generated by Axis:*
**
--MIMEBoundaryurn_uuid_8EF88BC3D516858F361222778974305
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: binary
Content-ID: <0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
>

http://schemas.xmlsoap.org/soap/envelope/";>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
EncodingType="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
ValueType="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
wsu:Id="CertId-526577">MIICGDCCAYGgAwIBAgIBADANBgkqhkiG9w0BAQUFADBSMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEjAQBgNVBAcTCUNhbWJyaWRnZTESMBAGA1UEChMJRGF0YVBvd2VyMQ4wDAYDVQQDEwVBbGljZTAeFw0wMjExMjMwMTE1MzNaFw0xMjExMjMwMTE1MzNaMFIxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTESMBAGA1UEBxMJQ2FtYnJpZGdlMRIwEAYDVQQKEwlEYXRhUG93ZXIxDjAMBgNVBAMTBUFsaWNlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCUIz3F9Kwgu57QfATZfCJmJq0kNoXFN2cagRP/YtH+T3A0fyA6g0MASAkjRX4waOCZL/Dpl+kIyUiFjbDku2vNIZS49OC66g021bIJpDHrV2+nML+XDc5tTOgyNCX2drT3AL9Rjj2guAIvUQLvi8Nj7sd2PL98h4wCKQCXbMpOdwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAJBKfQN7hJZ2tNjLiZWpXaRyiTc80TDZhPZYsSAEMYJ13R4gcThuZuSkpr3qxpdHotS8KhNn7FzVn/KtOnh1fqCGQQ6UfRiRAtEruhaBDI9jculwQRyzm7Ard7q5MLIIx3CKjaf12kN1mmEdHOitpfb+2LM/ksBIEaJ2MC5F0Jvihttp://www.w3.org/2000/09/xmldsig#"; Id="Signature-6586390">

http://www.w3.org/2001/10/xml-exc-c14n#";
/>
http://www.w3.org/2000/09/xmldsig#rsa-sha1";
/>


http://www.w3.org/2001/10/xml-exc-c14n#"; />

http://www.w3.org/2000/09/xmldsig#sha1"; />
M6bH0e9aKPGWXzYjCdQQSlAIApo=



BtTcWjTzXqT1d+3ifYyt4SorrVzS8/2Rwh4qzWVdFs3uI3KNfC3FtOpfU0u7NOJFjsbsx/J9tJEJ
C86aGn37f8p5rKtN6ze0O7xfp6hicXlkNajzZR3WiJJ1ZUjLUI5DksY1sKtHRjUHBVbSynCsDNi0
QGTGk73brkooMxgrpPY=


http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="STRId-31882858">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
/>

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="Timestamp-7031149">2008-09-30T12:49:34.066Z2008-09-30T12:54:34.066Zhttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="UsernameToken-1812813">EREWSDV2http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>1newpasshttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="id-12518719">test.txt55d41402abc4b2a76b9719d911017c592http://www.w3.org/2005/05/xmlmime";
ns2:contentType="application/xop+xml">http://www.w3.org/2004/08/xop/include";
/>
--MIMEBoundaryurn_uuid_8EF88BC3D516858F361222778974305
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <1.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
>

hello
--MIMEBoundaryurn_uuid_8EF88BC3D516858F361222778974305--





*CXF client request:*

POST /EREWSV2/services/EREWebServices HTTP/1.1
Content-Type: multipart/related; type="application/xop+xml";

boundary="=_Part_0_28008463.1222778483657"; start="<
[EMAIL PROTECTED]>";

start-info="text/xml"; charset=UTF-8
SOAPAction: "submitBulkFile"
Accept: *
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.5.0_08
Host: localhost:8000
Connection: keep-alive
Transfer-Encoding: chunked

ffb

--=_Part_0_28008463.1222778483657
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml";
Content-Transfer-Encoding: binary
Content-ID: <[EMAIL PROTECTED]>

http://schemas.xmlsoap.org/soap/envelope/";>

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>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";


EncodingType="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64B

inary"

ValueType="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";


wsu:Id="CertId-526577">MIICGDCCAYGgAwIBAgIBADANBgkqhkiG9w0BAQUFADBSMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUEx

EjAQBgNVBAcTCUNhbWJyaWRnZTESMBAGA1UEChMJRGF0YVBvd2VyMQ4wDAYDVQQDEwVBbGljZTAeFw0wMjExMjMwMTE1MzNaFw0xMjE

xMjMwMTE1MzNaMFIxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTESMBAGA1UEBxMJQ2FtYnJpZGdlMRIwEAYDVQQKEwlEYXRhUG93ZX

IxDjAMBgNVBAMTBUFsaWNlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCUIz3F9Kwgu57QfATZfCJmJq0kNoXFN2cagRP/YtH+T

3A0fyA6g0MASAkjRX4waOCZL/Dpl+kIyUiFjbDku2vNIZS49OC66g021bIJpDHrV2+nML+XDc5tTOgyNCX2drT3AL9Rjj2guAIvUQLv

i8Nj7sd2PL98h4wCKQCXbMpOdwIDAQABMA0GCSqGS

Starting with JAXBI binding

[Sagi Mann]

Hi all,
I would like to try Axis2 while using JAXBRI as a binding layer. I did not
find any tutorial on the axis2 website - only for adb, xmlbeans and jibx.
Can anyone tell me where to start?
thanks.
-- 
View this message in context: 
http://www.nabble.com/Starting-with-JAXBI-binding-tp19740938p19740938.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisFault when using jibx

[Dennis Sosnoski]

Looks like the JiBX code for Wsdl2Java may be having a problem with the 
schema generated by the JAXWS service. Can you provide the full schema 
portion of the WSDL, so that I can see the namespace usage?


By default, JAXB does not use elementFormDefault="qualified" in schema 
definitions, meaning only the top-level element definitions are 
namespace qualified. That's a shame, since 
elementFormDefault="qualified" is basically a best practice for clean 
XML structure. Wsdl2Java and JiBX should be able to handle it either 
way, though.


Thanks, and I'll look into the problem.

 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Sagi Mann wrote:

Yes, this is misunderstanding, I simply used the sample quick start code tree
as a template. This is why you see the .adb package, but I assure you it's
jibx.


DSosnoski wrote:
  

Hi Sagi,

 From your exception stack trace, it appears that you're still using 
ADB, rather than JiBX:





Anyway, I took your advice regarding TCPmon and found a difference between
what SoapUI generates and what Axis2/JIbx generates:

SoapUI sends the following request, which works great:

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:ws="http://ws/";>
   
  
 sagi
  
   


Axis2/jibx sends:

http://schemas.xmlsoap.org/soap/envelope/";>
   
  http://ws/";> 
 sagi

  
   


I found a solution, but it seems somewhat strange: not on the client side,
but on the server side:

If I added a targetNamespace to the method params as well, the SAME "bad"
request now gets invoked correctly, i.e. when changing the web service like
so:

@WebMethod
@WebResult(targetNamespace="http://ws/";)
public String testOneArg(@WebParam(name="testOneArg0",
targetNamespace="http://ws/";) String name) {
return "Hello " + name;
}

The Axis2/jibx client works great, and the same request it sent before now
gets a proper "Hello john" response...

I'm not sure if this is the "correct" solution, but at least it works. The
con of this solution, is, of course, the fact that I need to "enforce"
things on the service side, which may be 3rd party and out of my control. Is
there any better way to do this?

thanks
  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisFault when using jibx

[Sagi Mann]

I have an update: unfortunately, the solution with the targetNamespace on
each param only worked for me if the param is simple, i.e. String. However,
when my param was a bean, the issue continued in a different variation: the
bean was non-null, but all its properties were null.

Example:

I have a bean called ConcreteBean with a single 'name' property.

The following SOAP message is ok and the bean name is passed correctly to
the web service. Note the 'ws' namespace declared at the envelope:

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:ws="http://ws/";>
   
   
  
 
my bean name
 
  
   


The following SOAP message was generated by axis2/jibx, and does not work.
The service gets a non-null bean instance, but with a null name property.
Note the lack of 'ws:' prefix in the SOAP body and the lack of a 'ws'
namespace declaration:

http://schemas.xmlsoap.org/soap/envelope/";>
   
  http://ws/";>
 
my bean name
 
  
   


pls advise... thanks.

-- 
View this message in context: 
http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19740500.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisFault when using jibx

[Sagi Mann]

Yes, this is misunderstanding, I simply used the sample quick start code tree
as a template. This is why you see the .adb package, but I assure you it's
jibx.


DSosnoski wrote:
> 
> Hi Sagi,
> 
>  From your exception stack trace, it appears that you're still using 
> ADB, rather than JiBX:
> 

Anyway, I took your advice regarding TCPmon and found a difference between
what SoapUI generates and what Axis2/JIbx generates:

SoapUI sends the following request, which works great:

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:ws="http://ws/";>
   
  
 sagi
  
   


Axis2/jibx sends:

http://schemas.xmlsoap.org/soap/envelope/";>
   
  http://ws/";> 
 sagi
  
   


I found a solution, but it seems somewhat strange: not on the client side,
but on the server side:

If I added a targetNamespace to the method params as well, the SAME "bad"
request now gets invoked correctly, i.e. when changing the web service like
so:

@WebMethod
@WebResult(targetNamespace="http://ws/";)
public String testOneArg(@WebParam(name="testOneArg0",
targetNamespace="http://ws/";) String name) {
return "Hello " + name;
}

The Axis2/jibx client works great, and the same request it sent before now
gets a proper "Hello john" response...

I'm not sure if this is the "correct" solution, but at least it works. The
con of this solution, is, of course, the fact that I need to "enforce"
things on the service side, which may be 3rd party and out of my control. Is
there any better way to do this?

thanks
-- 
View this message in context: 
http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19739691.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: axis2 1.4 and later versions fail to deploy with Java 1.4.2 under RAD6/WAS6.0

[Brian De Pradine]

Hi Ramesh,

In order to get Axis2 1.4 to work with Java 1.4 you need to comment out 
the following in your axis2.xml file:





Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Ramesh Vishwanatham <[EMAIL PROTECTED]> wrote on 29/09/2008 22:26:33:

> 
> Hi 
> I have tried to deploy Axis2 1.4 and 1.4.1 versions in RAD6 using 
> Java 1.4.2 and was getting below error message: 
> 
> [9/29/08 13:50:19:706 EDT] 0022 ApplicationMg A   WSVR0200I: 
> Starting application: axis214EAR 
> [9/29/08 13:50:20:018 EDT] 0022 WebGroup  A   SRVE0169I: 
> Loading Web Module: Apache-Axis2. 
> [9/29/08 13:50:21:049 EDT] 0022 ServletWrappe E   SRVE0100E: Did
> not realize  init() exception thrown by servlet AxisServlet: java.
> lang.LinkageError: LinkageError while defining class: org.apache.
> axis2.jaxws.addressing.migrator.EndpointContextMapMigrator 
> Could not be defined due to: 
> org/apache/axis2/jaxws/addressing/migrator/EndpointContextMapMigrator
> (Unsupported major.minor version 49.0) 
> This is often caused by having a class defined at multiple 
> locations within the classloader hierarchy.  Other potential causes 
> include compiling against an older or newer version of the class 
> 
> 
> After some effort and search on web I have realized that error was 
> caused because of JAXWS introduction in axis2 1.4 version and it 
> will need Java 1.5 annotations. I have commented all the instances 
> of jaxws in axis2.xml file (total 7 places) and retried deploying 
> axis2.war file in RAD6 and was successful. 
> 
> I was able to deploy successfully axis2.war version 1.1 and 1.3 in 
> RAD6 environment. I would like to know is the axis2 1.4 and later 
> versions only suppose to work under Java 1.5? Also I see on axis2 1.
> 4 web page saying that it should work with Java 1.4 or later, is it 
> still a goal of axis2 development team. 
> 
> If someone from axis2 team can clarify these issues and guide me If 
> I need to deploy axis2 1.4 or newer versions under Java 1.4 under 
> RAD6 without modifying the axis2.xml file. 
> 
> Thanks in advance for looking into this matter. 
> 
> Ramesh Vishwanatham 
>  
> DTCC DISCLAIMER: This email and any files transmitted with it are 
> confidential and intended solely for the use of the individual or 
> entity to whom they are addressed. If you have received this email 
> in error, please notify us immediately and delete the email and any 
> attachments from your system. The recipient should check this email 
> and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this 
email.





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: AxisFault when using jibx

[Sagi Mann]

Found a way to solve one part of the problem: explicitly set the namespace
for the return value:

@WebMethod 
@WebResult(targetNamespace="http://ws/";)
public String testOneArg(@WebParam(mode=Mode.IN, name="testOneArg0")
String name) { 
return "Hello " + name; 
} 

This added a 'qualified' keyword to the schema:

 
 
 
 
 

Now, I don't get the exception any more, but the input parameter always
comes in as null. I know this by writing a debug message at the service
side. The client code is:

public static void testOneArg(HelloServiceStub stub){
try{
ws.TestOneArg arg = new ws.TestOneArg();
arg.setTestOneArg0("john"); 
ws.TestOneArgResponse res = stub.testOneArg(arg);
// expected output is "Hello john" but I get "Hello null":
System.out.println(res.getReturn());
} catch(Exception e){
e.printStackTrace();
System.err.println("\n\n\n");
}
}

Any ideas? thanks...

-- 
View this message in context: 
http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19739246.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisFault when using jibx

[Dennis Sosnoski]

Hi Sagi,

From your exception stack trace, it appears that you're still using 
ADB, rather than JiBX:


samples.quickstart.service.adb.HelloServiceStub.fromOM(HelloServiceStub.java:641)
   at
samples.quickstart.service.adb.HelloServiceStub.testOneArg(HelloServiceStub.java:215)
   at
samples.quickstart.clients.ADBClient.testOneArg(ADBClient.java:57)
   at samples.quickstart.clients.ADBClient.main(ADBClient.java:43)

Am I misunderstanding this? If so, it'd help if you can capture the 
response message with TCPMon so we can see what's actually there.


 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117


Sagi Mann wrote:

Hello,
I've got an issue when working with a jibx axis2 client, based on the
tutorial at:
http://ws.apache.org/axis2/1_4_1/userguide-creatingclients-jibx.html
http://ws.apache.org/axis2/1_4_1/userguide-creatingclients-jibx.html 


I'd appreciate if someone could tell if this is a bug or a misuse.
thanks...


My web service is a JAXWS web service, that look like this:

@WebService
public class Hello {

@WebMethod

public String testOneArg(@WebParam(mode=Mode.IN, name="testOneArg0")
String name) {
return "Hello " + name;
}
}

I can correctly invoke the method when using axis2 client with ADB. But I
cannot invoke when using jibx. I get an execption:

org.apache.axis2.AxisFault: Expected "{http://ws/}testOneArgResponse"; end
tag, found "return" start tag (line -1, col -1, in SOAP-message)
at
samples.quickstart.service.adb.HelloServiceStub.fromOM(HelloServiceStub.java:641)
at
samples.quickstart.service.adb.HelloServiceStub.testOneArg(HelloServiceStub.java:215)
at
samples.quickstart.clients.ADBClient.testOneArg(ADBClient.java:57)
at samples.quickstart.clients.ADBClient.main(ADBClient.java:43)

The xsd that JAXWS generates contains:














I use this schema when creating binding.xml with the xsd2jibx utility. The
binding.xml file contains:

  
http://ws/"; default="elements"/>

  
  
http://ws/"; default="elements"/>

  

  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error "HTTP :unsupported content-encoding of 'identity' found"

[keith chapman]

On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen
<[EMAIL PROTECTED]>wrote:

> Googling for "Content-encoding: identity" reveals that this is actually
> quite common, so I guess that we should indeed support it.


Exactly. And we wont have to do much jsut ignore the content-type if its
identity.

Thanks,
Keith .

>
>
> Andreas
>
> keith chapman wrote:
>
>> Interesting, It says SHOULD NOT but not MUST NOT. So it may be acceptable
>> to have this header too. I guess one could argue that Axis2 should ignore it
>> if there is a header which says Content-encoding: identity. WDYT?
>>
>> Thanks,
>> Keith.
>>
>> On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen <
>> [EMAIL PROTECTED] > wrote:
>>
>>RFC2616, section 3.5 says the following about the identity content
>>encoding: "This content-coding is used only in the Accept-Encoding
>>header, and SHOULD NOT be used in the Content-Encoding header."
>>Assuming that the error is triggered by the Content-Encoding
>>header, the behavior of Axis2 in this particular case seems to be
>>acceptable.
>>
>>Andreas
>>
>>
>>On 29 sept. 08, at 19:23, keith chapman wrote:
>>
>>I just had a look at the code and it looks like we dont deal
>>with identity content encoding (whereas we should). Could you
>>use TCPMonitor to trace to request and response please. If you
>>want to use the TCPMonitor plugin this how to [1] would help.
>>
>>Thanks,
>>Keith.
>>
>>[1]
>>
>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>>
>>On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED]
>>> wrote:
>>I generated the stubs using the WSDLToJava tool.
>>
>>Sangita Pandit
>>728 1606
>>
>>
>>
>>From: keith chapman [mailto:[EMAIL PROTECTED]
>>]
>>Sent: Monday, September 29, 2008 11:47 AM
>>To: axis-user@ws.apache.org 
>>Subject: Re: Error "HTTP :unsupported content-encoding of
>>'identity' found"
>>
>>Hi,
>>
>>How did you write the client for this service? Did you use
>>ServiceClient API or did you use a generated stub?
>>
>>Thanks,
>>Keith.
>>
>>On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED]
>>> wrote:
>>I am getting this error when webservice client is trying to
>>make a call to the webservice method.  I am using the released
>>version of Axis2 1.4.1. 
>>
>>
>>See stack trace here
>>org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
>>of 'identity' found
>>   at
>>
>>  
>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:223)
>>   at
>>
>>  
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265)
>>   at
>>
>>  org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
>>   at
>>org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>>   at
>>
>>  
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
>>
>>   at
>>
>>  
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
>>   at
>>org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
>>   at
>>
>>  
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
>>   at
>>
>>  
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>>   at
>>
>>  org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>>   at
>>
>>  
>> com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusServiceStub.java:1056)
>>   at
>>
>>  
>> com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatusServiceTest.java:37)
>>   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 junit.framework.TestCase.runTest(TestCase.java:154)
>>   at junit.framework.TestCase.runBare(TestCase.java:127)
>>   at
>>junit.framework.TestResult$1.protect(TestResult.java:106)
>>   at
>>junit.framework.TestResult.runProtected(TestResult.java:124)
>>   at junit.framework.TestResult.run(TestResult.java:109)
>>   at junit.framewor

AxisFault when using jibx

[Sagi Mann]

Hello,
I've got an issue when working with a jibx axis2 client, based on the
tutorial at:
http://ws.apache.org/axis2/1_4_1/userguide-creatingclients-jibx.html
http://ws.apache.org/axis2/1_4_1/userguide-creatingclients-jibx.html 

I'd appreciate if someone could tell if this is a bug or a misuse.
thanks...


My web service is a JAXWS web service, that look like this:

@WebService
public class Hello {

@WebMethod
public String testOneArg(@WebParam(mode=Mode.IN, name="testOneArg0")
String name) {
return "Hello " + name;
}
}

I can correctly invoke the method when using axis2 client with ADB. But I
cannot invoke when using jibx. I get an execption:

org.apache.axis2.AxisFault: Expected "{http://ws/}testOneArgResponse"; end
tag, found "return" start tag (line -1, col -1, in SOAP-message)
at
samples.quickstart.service.adb.HelloServiceStub.fromOM(HelloServiceStub.java:641)
at
samples.quickstart.service.adb.HelloServiceStub.testOneArg(HelloServiceStub.java:215)
at
samples.quickstart.clients.ADBClient.testOneArg(ADBClient.java:57)
at samples.quickstart.clients.ADBClient.main(ADBClient.java:43)

The xsd that JAXWS generates contains:













I use this schema when creating binding.xml with the xsd2jibx utility. The
binding.xml file contains:

  
http://ws/"; default="elements"/>

  
  
http://ws/"; default="elements"/>

  


-- 
View this message in context: 
http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19738701.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error "HTTP :unsupported content-encoding of 'identity' found"

[Andreas Veithen]

Googling for "Content-encoding: identity" reveals that this is actually 
quite common, so I guess that we should indeed support it.


Andreas

keith chapman wrote:
Interesting, It says SHOULD NOT but not MUST NOT. So it may be 
acceptable to have this header too. I guess one could argue that Axis2 
should ignore it if there is a header which says Content-encoding: 
identity. WDYT?


Thanks,
Keith.

On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen 
<[EMAIL PROTECTED] > wrote:


RFC2616, section 3.5 says the following about the identity content
encoding: "This content-coding is used only in the Accept-Encoding
header, and SHOULD NOT be used in the Content-Encoding header."
Assuming that the error is triggered by the Content-Encoding
header, the behavior of Axis2 in this particular case seems to be
acceptable.

Andreas


On 29 sept. 08, at 19:23, keith chapman wrote:

I just had a look at the code and it looks like we dont deal
with identity content encoding (whereas we should). Could you
use TCPMonitor to trace to request and response please. If you
want to use the TCPMonitor plugin this how to [1] would help.

Thanks,
Keith.

[1]

http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html

On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED]
> wrote:
I generated the stubs using the WSDLToJava tool.

Sangita Pandit
728 1606



From: keith chapman [mailto:[EMAIL PROTECTED]
]
Sent: Monday, September 29, 2008 11:47 AM
To: axis-user@ws.apache.org 
Subject: Re: Error "HTTP :unsupported content-encoding of
'identity' found"

Hi,

How did you write the client for this service? Did you use
ServiceClient API or did you use a generated stub?

Thanks,
Keith.

On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED]
> wrote:
I am getting this error when webservice client is trying to
make a call to the webservice method.  I am using the released
version of Axis2 1.4.1. 

See stack trace here
org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
of 'identity' found
   at

org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:223)
   at

org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265)
   at

org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
   at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
   at

org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)

   at

org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
   at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
   at

org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
   at

org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
   at

org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at

com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusServiceStub.java:1056)
   at

com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatusServiceTest.java:37)
   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 junit.framework.TestCase.runTest(TestCase.java:154)
   at junit.framework.TestCase.runBare(TestCase.java:127)
   at
junit.framework.TestResult$1.protect(TestResult.java:106)
   at
junit.framework.TestResult.runProtected(TestResult.java:124)
   at junit.framework.TestResult.run(TestResult.java:109)
   at junit.framework.TestCase.run(TestCase.java:118)
   at junit.framework.TestSuite.runTest(TestSuite.java:208)
   at junit.framework.TestSuite.run(TestSuite.java:203)
   at

org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
   at

org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecutio

RE: I must understand the "must understand" fault

[Taariq Levack]

That makes good sense, I've created issue 197.

https://issues.apache.org/jira/browse/RAMPART-197

 

Yes we're using Oracle server, OC4J 10.1.3. We're also sending requests
to a server we have no control over and don't know what it will be as
yet.

 

Thank you Nandana.

 

Best regards

Taariq

 

 

From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] 
Sent: 30 September 2008 08:58
To: axis-user@ws.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: I must understand the "must understand" fault

 

Hi Taariq,
  The reason for this is, empty security header (with must
understand header set 1) being not processed by any of the handlers.
Normally security header is processed by Rampart module but in this case
after reading the policy Rampart decides that there is nothing to be
processed in the response as response doesn't need to have a security
header. But before handing over the message to the service, Axis Engine
checks whether all must understand headers are processed and fault if
not. We have successfully tested this scenario with Axis2 <-> Axis2 and
Axis2 <-> WCF but in both cases Aixs2/WCF doesn't generate empty
security headers when security header is not necessary. Are you using
oracle server ?
 I personally believe that we don't need to send empty security
headers when there is nothing to be send in the security header but we
can make Rampart to flag empty security header as processed when it
expects nothing in the security header for interoperability. Please
create a issue in the Rampart JIRA and it will be fixed. I don't
recommend going back to Axis2 1.3 / Rampart 1.3 just because of this
issue as there has been lot of improvements in both Axis2 and Rampart
since 1.3. 

thanks,
nandana

[1] - http://issues.apache.org/jira/browse/Rampart
   

On Tue, Sep 30, 2008 at 2:03 AM, Taariq Levack
<[EMAIL PROTECTED]> wrote:

For the next one to fall into this trap, it's not worth it.
Move swiftly along and download Axis 1.3 and Rampart 1.3.


-Original Message-
From: Taariq Levack [mailto:[EMAIL PROTECTED]

Sent: 29 September 2008 17:26
To: axis-user@ws.apache.org

Subject: RE: I must understand the "must understand" fault

If I set a breakpoint in AxisEngine and force the SOAPHeaderBlock's
"mustUnderstand" to "0" it works.
Obviously I don't want to change that code, I don't even understand why
its checked on the response, is it a bug at all?

The method isReceiverMustUnderstandProcessor checks if its server side
and returns which it's not, or if the receiver's name ends in
JAXWSMessageReceiver, if it's not null, which it is.

I've attached the policy.xml file if that has anything to do with it.



From: Taariq Levack [mailto:[EMAIL PROTECTED]
Sent: 29 September 2008 13:13
To: axis-user@ws.apache.org
Subject: I must understand the "must understand" fault

Hi

The exception happens at the client side, after the request is sent,
authenticated and response returned.
Seems to me that the Axis engine doesn't expect the security header in
the response.
SoapUi client works, and the Oracle generated client works,
surprisingly.


This is the request header, simple username token

 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
curity-secext-1.0.xsd" soapenv:mustUnderstand="1">
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd" wsu:Id="UsernameToken-3201085">
   USERNAME
   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
oken-profile-1.0#PasswordText">PASSWORD

 
  

And this is the response header

  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
curity-secext-1.0.xsd"
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
y-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";
env:mustUnderstand="1"/>
   

Configuration
Axis 1.4
 Rampart 1.4.
The service is deployed in an oracle container, OC4J.
The client was generated using Axis and the config is copied from the
Rampart samples.

Exception in thread "main" org.apache.axis2.AxisFault: Must Understand
check failed for header
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secex
t-1.0.xsd : Security
  at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:1
02)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166)
  at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(Out
InAxisOperation.java:363)
  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:416)
  at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:228)
  at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
)
  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:548
)
  at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:528
)

Thanks in ad

Re: Web Service requires secure header - how to generate with Axis?

[Nandana Mihindukulasooriya]

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 <[EMAIL PROTECTED]>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 <[EMAIL PROTECTED]>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?

 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">
 
  

  
 urn:uuid:xxx----

  
 

 http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
 
  
  https://{url:443}
  
 http://docs.oasis-open.org/wss/2004/01/oasis-
  200401-wss-wssecurity-utility-1.0.xsd"
 wsu:Id="SecurityToken-xxx---
  -">
[username]
>>>  Type="
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-
  token-profile-1.0#PasswordText">
   [password]

 
  
  
   
 ...  
 



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> 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: ModulePolicyExtension

[Dimuthu Leelarathne]

Hi,

This occurs because Rampart version is not compatible with Axis2 version.

You have to use Rampart 1.4 with Axis2 1.4. Or if you are using older 
Axis2 versions use the relevant Rampart jars and modules.


Thank you,
Dimuthu

Srisathya Thirumalai wrote:

Hello,
I am trying to refer to rampart module from axis2.xml. It fails saying
 
ERROR ModuleDeployer:108 - The rampart-1.1.mar module, which is not 
valid, caused org/apache/axis2/modules/ModulePolicyExtension
java.lang.NoClassDefFoundError: 
org/apache/axis2/modules/ModulePolicyExtension

.
.
ERROR ModuleDeployer:108 - The axis2-security-1.1.jar module, which is 
not valid, caused org/apache/axis2/modules/ModulePolicyExtension
java.lang.NoClassDefFoundError: 
org/apache/axis2/modules/ModulePolicyExtension
 
I don't see a ModulePolicyExtension class anywhere in any of the jar 
files I have. I have axis2-security-1.1.jar among other axis2 jar 
files in my lib folder and I have rampart-1.1.mar and 
addressing-1.41.mar in my modules folder.
 
Any ideas?
 
Thanks
 
 



Get more out of the Web. Learn 10 hidden secrets of Windows Live. 
Learn Now 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ModulePolicyExtension

[Nandana Mihindukulasooriya]

Hi,
Please take a look at this [1] thread. It is for Axis2 1.4 but may help you
to solve the problem.

thanks,
nandana

[1] -
http://markmail.org/message/2b2ngk5pzcoxpzwv?q=list:org%2Eapache%2Ews%2Erampart-dev+ModulePolicyExtension#query:list%3Aorg.apache.ws.rampart-dev%20ModulePolicyExtension+page:1+mid:epf7kyw4gfno2lst+state:results

On Tue, Sep 30, 2008 at 10:56 AM, Srisathya Thirumalai
<[EMAIL PROTECTED]>wrote:

>  Hello,
> I am trying to refer to rampart module from axis2.xml. It fails saying
>
> ERROR ModuleDeployer:108 - The rampart-1.1.mar module, which is not valid,
> caused org/apache/axis2/modules/ModulePolicyExtension
> java.lang.NoClassDefFoundError:
> org/apache/axis2/modules/ModulePolicyExtension
> .
> .
> ERROR ModuleDeployer:108 - The axis2-security-1.1.jar module, which is not
> valid, caused org/apache/axis2/modules/ModulePolicyExtension
> java.lang.NoClassDefFoundError:
> org/apache/axis2/modules/ModulePolicyExtension
>
> I don't see a ModulePolicyExtension class anywhere in any of the jar files
> I have. I have axis2-security-1.1.jar among other axis2 jar files in my lib
> folder and I have rampart-1.1.mar and addressing-1.41.mar in my modules
> folder.
>
> Any ideas?
>
> Thanks
>
>
>
> --
> Get more out of the Web. Learn 10 hidden secrets of Windows Live. Learn
> Now
>



-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org