Re: I must understand the "must understand" fault

[Nandana Mihindukulasooriya]

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-wssecurity-secext-1.0.xsd";
> soapenv:mustUnderstand="1">
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="UsernameToken-3201085">
>USERNAME
>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText
> ">PASSWORD
> 
>  
>   
>
> And this is the response header
> 
>   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-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-secext-1.0.xsd:
>  Security
>   at
> org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102)
>   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:363)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.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 advance for looking at the one millionth "must understand" error.
>
> -
> 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

ModulePolicyExtension

[Srisathya Thirumalai]

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.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008

RE: WS-addressing

[Srisathya Thirumalai]

Thanks Yoos, it worked.> Date: Fri, 26 Sep 2008 22:56:24 +0200> From: [EMAIL 
PROTECTED]> To: axis-user@ws.apache.org> Subject: RE: WS-addressing> > Hello 
all,> > If you think about using WS-ADDRESSING using Axis2 ServiceClient Api, 
you have> to engage the module using a ConfigurationContext:> > 
=> ConfigurationContext context => 
ConfigurationContextFactory.createConfigurationContextFromFileSystem(> 
PATH_OF_YOUR_REPOSITORY, PATH_OF_AXIS2.XML);> > ServiceClient client = new 
ServiceClient(context);> > Option opt = new Option();> 
opt.setAction(YOUR_ACTION);> > client.setOption(opt);> 
==> > PATH_OF_YOUR_REPOSITORY => repository> > modules 
: where adressing1.4.mar is stored> > services> PATH_OF_AXIS2.XML : axis2.xml 
contains the call to engage adressing> > I am not very sure of the method 
"createConfigurationContextFromFileSystem".> Test it or find in the api the 
right one.> > I didn't tried to use addressing with a Stub, but i should be 
merely the same.> > > yOOs> > > Selon Martin Gainty <[EMAIL PROTECTED]>:> > >> 
> how does he engage WS-Addressing as a module?> >> > (..TRYING to get the op 
to upgrade..)> >> > thx> > 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.> >> >> > To: axis-user@ws.apache.org> > Subject: 
RE: WS-addressing> > From: [EMAIL PROTECTED]> > Date: Fri, 26 Sep 2008 16:14:43 
-0400> >> >> >> > Actually, WS-addressing is available> > under Axis 1 - see: 
java\samples\wsa> >> >> >> > thanks> >> > -Doug> >> > 
__> >> > STSM | Web 
Services Architect | IBM Software Group> >> > (919) 254-6905 | IBM T/L 444-6905 
| [EMAIL PROTECTED]> >> >> >> >> >> >> >> >> > Martin Gainty <[EMAIL 
PROTECTED]>> >> > 09/26/2008 03:01 PM> >> >> >> > Please respond to> >> > 
axis-user@ws.apache.org> >> >> >> >> >> >> > To> > > 
>> >> > cc> >> >> >> >> > Subject> > RE: WS-addressing> >> >> >> >> >> >> >> >> 
>> >> >> >> >> >> >> > not available in Axis 1.x> >> > can you upgrade to 2.x> 
>> > ?> >> > 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.> >> >> >> >> >> >> >> > From: 
[EMAIL PROTECTED]> >> > To: axis-user@ws.apache.org> >> > Subject: 
WS-addressing> >> > Date: Fri, 26 Sep 2008 14:20:51 -0400> >> >> >> > Hello,> 
>> > Can somebody please tell me how to engage/enable WS-addressing in Axis> > 
1.4?> >> >> >> > Thanks> >> >> >> >> > Want to do more with Windows Live? 
Learn> > “10 hidden secrets” from Jamie. Learn> > Now> >> >> > Want to do more 
with Windows Live? Learn> > “10 hidden secrets” from Jamie. Learn> > Now> >> >> 
> _> > See how 
Windows Mobile brings your life together—at home, work, or on the go.> > 
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/> > > > 
-> To 
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL 
PROTECTED]> 
_
Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008

RE: Get XML REquest File

[Srisathya Thirumalai]

Thanks Martin. That logging tips worked for me.
 
 



From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: Get XML REquest FileDate: Sat, 
27 Sep 2008 18:38:32 -0400


configure Log4j to use ConsoleAppender ### direct log messages to stdout 
###log4j.appender.stdout=org.apache.log4j.ConsoleAppenderlog4j.appender.stdout.Target=System.outlog4j.appender.stdout.layout=org.apache.log4j.PatternLayoutlog4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE}
 %5p %c{1}:%L - %m%nlog4j.rootLogger=debug, stdoutimport 
org.apache.log4j.Logger;...private static org.apache.log4j.Logger log = 
Logger  .getLogger(YourClassNameGoesHere.class);and when use you call 
log.debug("foo");you will see the debug statements on screendocumentation is 
available athttp://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html?page=3you 
can also use Log4J Category as in this example..static Category cat = 
Category.getInstance(YOURClassNameGoesHere.class.getName());//now test the 
various debugging capabilities of the logger as explained herecat.info("Just 
testing a log message with priority set to INFO");cat.warn("Just testing a log 
message with priority set to WARN");cat.error("Just testing a log message with 
priority set to ERROR");cat.fatal("Just testing a log message with priority set 
to FATAL")HTHMartin __ 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. 

From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: Get XML REquest FileDate: Sat, 
27 Sep 2008 18:17:39 -0400

I am using Axis2 as the client. The server is not controlled by me. I want to 
spit the XML request I am sending to the server. Can you please tell me how to 
do that? (My request fails and the server person wants me to send the request 
XML to him so he can see what went wrong? )Thanks for replying!> Date: Sat, 27 
Sep 2008 09:22:30 -0400> From: [EMAIL PROTECTED]> To: axis-user@ws.apache.org> 
Subject: Re: Get XML REquest File> > > > Hello,> > How do I get the XML version 
of the request the client is sending to> > the web service? The client is using 
Axis 2.> If you are using Axis2 as the server , then you can write your 
service> using Axiom. Then you can get the XML as the input parameter. With 
this> your service would look like,> > public class MyService {> > public void 
doFoo(OMElement parameter){> // do your service logic here> }> > }> > > Thank 
you!> > > http://blogs.deepal.org> > > 
-> 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. 
See Now 

Stay up to date on your PC, the Web, and your mobile phone with Windows Live. 
See Now 
_
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: WS-addressing

[Srisathya Thirumalai]

Doug,
I don't see this folder in my Axis 1.4 download. Can you please email the 
snippet of code of how to set WS-addressing in Axis 1.4?
 
Thanks



To: [EMAIL PROTECTED]: RE: WS-addressingFrom: [EMAIL PROTECTED]: Fri, 26 Sep 
2008 16:14:43 -0400Actually, WS-addressing is available under Axis 1 - see: 
java\samples\wsa 
thanks-Doug__STSM  |  Web 
Services Architect  |  IBM Software Group(919) 254-6905  |  IBM T/L 444-6905  | 
 [EMAIL PROTECTED] 



Martin Gainty <[EMAIL PROTECTED]> 
09/26/2008 03:01 PM 




Please respond [EMAIL PROTECTED]





To
 


cc



Subject
RE: WS-addressing




not available in Axis 1.xcan you upgrade to 2.x?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. 

From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: WS-addressingDate: Fri, 26 Sep 2008 
14:20:51 -0400Hello,Can somebody please tell me how to engage/enable 
WS-addressing in Axis 1.4? Thanks

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

Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. Learn 
Now 
_
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: Error "HTTP :unsupported content-encoding of 'identity' found"

[keith chapman]

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(TestExecution.java:38)
>>
>> Please advise what I am doing wrong.
>>
>> I have tried both XMLbean and databinding approach to generate the client
>> code.
>>
>> Thanks
>> Sangita Pandit
>> 728 1606
>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman

Re: Internal/external operations

[keith chapman]

Looks like you need some throttling capabilities. This is not inherently
supported in Axis2 but WSO2 Web Services Application
Server(A.K.A. WSO2 WSAS) has support
for throttling and you should be able to
configure it to do just this. WSAS is made available under the same Apache
License that Axis2 is available under (Actually WSAS is a complete web
services runtime with enterprise capabilities built on top of Axis2).

Please do let me know if you need further details. You could find the
project details here.  [1]

Thanks,
Keith.

[1] http://wso2.org/projects/wsas

On Tue, Sep 30, 2008 at 2:38 AM, Richard <[EMAIL PROTECTED]> wrote:

> Keith,
>
> > What do u mean by external and internal WS-Clients?
>
> External web service clients would be our customers which we give a WSDL
> so they can call our web service.  Ideally, we could indicate which
> operations they are allowed to call but they are limited to the operations
> which are for external use.
>
> Internal web service clients would be our web application which calls
> operations which are intended for internal use.  The web application might
> also call operations which are intended for external use as well.
>
> > Well, If you use something like username token authentication on your
> > service, you could access the username of the caller from within your web
> > service and thus vary the action you need to perform. This is just
> > one way of doing it though.
>
> Customers can use the same username to access the web service either via a
> web services client outside of the firewall or by using the web
> application which calls the web service from inside the firewall.
>
> Thanks,
> Richard
>
> > Hi Richard,
> >
> > See comments inline.
> >
> > On Mon, Sep 29, 2008 at 11:09 PM, Richard <[EMAIL PROTECTED]> wrote:
> >
> >> Perhaps someone can help me with two questions:
> >>
> >> 1.  Is it possible to create a web service where most operations can be
> >> called by external ws clients but some operations can be called only by
> >> internal ws clients.
> >
> >
> > What do u mean by external and internal WS-Clients?
> >
> >>
> >>
> >> 2.  The behavior of an operation needs to differ slightly depending on
> >> whether an operation is called internally or externally--this can be
> >> done
> >> by checking the value an attribute or an element.  Is there a more
> >> transparent way to determine the ws caller so that behavior such as how
> >> to
> >> connect to the database can differ slightly.
> >
> >
> > Well, If you use something like username token authentication on your
> > service, you could access the username of the caller from within your web
> > service and thus vary the action you need to perform. This is just one
> way
> > of doing it though.
> >
> > Thanks,
> > Keith.
> >
> >>
> >>
> >> Thanks,
> >> Richard
> >>
> >>
> >> -
> >> 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
> >
>
>
>
> -
> 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

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

[keith chapman]

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

Re: wsdl-level client side compatibility between Axis 2 and Axis 1

[keith chapman]

Axis2 does not support soap-encoding (whereas Axis does), but soap-encoding
is actually deprecated. Other then that you should be just fine. And its
much better for you to go with Axis2 than Axis.

Thanks,
Keith.

On Tue, Sep 30, 2008 at 2:55 AM, Steve Cohen <[EMAIL PROTECTED]> wrote:

> Will a WSDL written and recommended to be used with Axis 1 definitely be
> usable with Axis 2 on the client side?  We have no investment in Axis 1 so
> if the switch is possible, we should probably make it now.  My group is
> going to be incorporating several web service clients into an application
> that currently has none, so my question is geared toward selecting the best
> client side technology going forward.
>
> -
> 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

Re: Axis2 and CXF - Handling WSDLs differently

[keith chapman]

Hmm, Now this is where the ambiguity of the WSDL comes into play. As it was
originally incorrect we are not sure what the payload should actually look,

Try adding another TestLoginType element around the SOAP body,


  
   
   ABC123
   KEY123
   
   
 

I'm not sure whether this would help but with an incorrect WSDL thats the
best you could do. Trial and error. (You should be able to modify this on
TCPMon and resend). BTW where did you get this WSDL from? (Just curios, was
it generated if so by what?).

Thanks,
Keith.

On Tue, Sep 30, 2008 at 4:28 AM, jackdawson <[EMAIL PROTECTED]> wrote:

>
> Yeah, I tried the one with Eclipse. I even changed the port to 9081 on
> which
> the TCP/IP Monitor listens but invain.
>
> I used the Web Services explorer and noted the SOAP messages, may be these
> would help:
>
> Request:
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:q0="urn:login.safe.two.us"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
>
>ABC123
>KEY123
>
>  
> 
>
> Response:
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
>
>soap:Client
>Parameter 
> {urn:login.safe.two.us}TestLoginType
> does not
> exist!
>
>  
> 
>
> Thanks.
>
>
>
>
>
>
> Keithgchapman wrote:
> >
> > TCPMon should wok irrespective of what your client or server is. It works
> > like a proxy sitting in between the client and server. Did you try to use
> > one of the plgins? Eclipse or Idea depending on what IDE you use.
> >
> > Thanks,
> > Keith.
> >
> > On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <[EMAIL PROTECTED]>
> > wrote:
> >
> >>
> >> If I'm not wrong then I get this when sending the request. This is the
> >> statement in the client that throws this exception:
> >>
> >> LoginServiceStub.TestLoginTypeResponse response =
> >>
> >>  stub.testLogin(testLoginRequestAttributes);
> >>
> >> And, I don't know why but I can't get TCP Monitor get to work. I ran the
> >> client and it's hanging there in the console. I won't run and won't
> stop.
> >>
> >> Local Monitoring port: 8080
> >> Host name: JISLOGINDEV
> >> Port: 8080
> >> Type: HTTP
> >> Timeout: 0
> >>
> >> Dumb question again:
> >> My client is a simple Java app. Would TCP Monitor still work? I'm not
> >> running it on a server.
> >>
> >> Thanks.
> >>
> >>
> >>
> >> Keithgchapman wrote:
> >> >
> >> > Did you get this message while trying ti send the request or while
> >> > processing the response?
> >> >
> >> > You may use TCPMonitor as explained
> >> > here<
> >>
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >> >[1]
> >> > to capture the SOAP messages sent.
> >> >
> >> > 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:26 PM, jackdawson <[EMAIL PROTECTED]>
> >> > wrote:
> >> >
> >> >>
> >> >> I changed the 'parts' to include element attributes and the WSDL is
> of
> >> >> 'document' style now. I generated the client stubs and the client and
> >> I'm
> >> >> still getting this exception:
> >> >>
> >> >> org.apache.axis2.AxisFault: Parameter
> >> >> {urn:login.safe.two.us}TestLoginType
> >> >> does not exist!
> >> >>
> >> >> I don't find where exactly it's going wrong even while debugging
> >> either.
> >> >> The service expects the parameters to be of type 'string' and that's
> >> what
> >> >> the client is sending.
> >> >>
> >> >> Here is the SOAP envelope:
> >> >>
> >> >> 
> >> >>  >> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> >> >> ">
> >> >>
> >> >>
> >> >>http://www.w3.org/2001/XMLSchema-instance";
> >> >>
> >> >> xmlns:s2="http://www.w3.org/2001/XMLSchema";
> >> >> s1:type="s2:string">G13522
> >> >>http://www.w3.org/2001/XMLSchema-instance";
> >> >>
> >> >> xmlns:s4="http://www.w3.org/2001/XMLSchema";
> >> >> s3:type="s4:string">P9534
> >> >>
> >> >>
> >> >> 
> >> >>
> >> >>
> >> >> Am I missing something here?
> >> >>
> >> >> Thanks.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Keithgchapman wrote:
> >> >> >
> >> >> > In your WSDL the parts section look RPC while the binding is
> >> document.
> >> >> I
> >> >> > recommend you that you make both of them the same. Either make both
> >> RPC
> >> >> > (just change the binding style to rpc) or both document (by making
> >> the
> >> >> > part
> >> >> > refer to an element instead of a type).
> >> >> >
> >>

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

Yeah, I tried the one with Eclipse. I even changed the port to 9081 on which
the TCP/IP Monitor listens but invain.

I used the Web Services explorer and noted the SOAP messages, may be these
would help:

Request:
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:q0="urn:login.safe.two.us" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>



ABC123 
KEY123 

  


Response:
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>



soap:Client 
Parameter 
{urn:login.safe.two.us}TestLoginType does not
exist! 

  


Thanks.






Keithgchapman wrote:
> 
> TCPMon should wok irrespective of what your client or server is. It works
> like a proxy sitting in between the client and server. Did you try to use
> one of the plgins? Eclipse or Idea depending on what IDE you use.
> 
> Thanks,
> Keith.
> 
> On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <[EMAIL PROTECTED]>
> wrote:
> 
>>
>> If I'm not wrong then I get this when sending the request. This is the
>> statement in the client that throws this exception:
>>
>> LoginServiceStub.TestLoginTypeResponse response =
>>
>>  stub.testLogin(testLoginRequestAttributes);
>>
>> And, I don't know why but I can't get TCP Monitor get to work. I ran the
>> client and it's hanging there in the console. I won't run and won't stop.
>>
>> Local Monitoring port: 8080
>> Host name: JISLOGINDEV
>> Port: 8080
>> Type: HTTP
>> Timeout: 0
>>
>> Dumb question again:
>> My client is a simple Java app. Would TCP Monitor still work? I'm not
>> running it on a server.
>>
>> Thanks.
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > Did you get this message while trying ti send the request or while
>> > processing the response?
>> >
>> > You may use TCPMonitor as explained
>> > here<
>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
>> >[1]
>> > to capture the SOAP messages sent.
>> >
>> > 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:26 PM, jackdawson <[EMAIL PROTECTED]>
>> > wrote:
>> >
>> >>
>> >> I changed the 'parts' to include element attributes and the WSDL is of
>> >> 'document' style now. I generated the client stubs and the client and
>> I'm
>> >> still getting this exception:
>> >>
>> >> org.apache.axis2.AxisFault: Parameter
>> >> {urn:login.safe.two.us}TestLoginType
>> >> does not exist!
>> >>
>> >> I don't find where exactly it's going wrong even while debugging
>> either.
>> >> The service expects the parameters to be of type 'string' and that's
>> what
>> >> the client is sending.
>> >>
>> >> Here is the SOAP envelope:
>> >>
>> >> 
>> >> > >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> >> ">
>> >>
>> >>
>> >>http://www.w3.org/2001/XMLSchema-instance";
>> >>
>> >> xmlns:s2="http://www.w3.org/2001/XMLSchema";
>> >> s1:type="s2:string">G13522
>> >>http://www.w3.org/2001/XMLSchema-instance";
>> >>
>> >> xmlns:s4="http://www.w3.org/2001/XMLSchema";
>> >> s3:type="s4:string">P9534
>> >>
>> >>
>> >> 
>> >>
>> >>
>> >> Am I missing something here?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Keithgchapman wrote:
>> >> >
>> >> > In your WSDL the parts section look RPC while the binding is
>> document.
>> >> I
>> >> > recommend you that you make both of them the same. Either make both
>> RPC
>> >> > (just change the binding style to rpc) or both document (by making
>> the
>> >> > part
>> >> > refer to an element instead of a type).
>> >> >
>> >> > Thanks,
>> >> > Keith.
>> >> >
>> >> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]>
>> >> > wrote:
>> >> >
>> >> >>
>> >> >> I posted in there too. They say that it's not mandatory to follow
>> the
>> >> >> WS-I
>> >> >> basic profile as they are just guidelines and this is what they
>> >> exactly
>> >> >> said:
>> >> >>
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >> >>
>> >> >> Instead, I would like to get help in moving ahead with Axis2.
>> >> >> Can anyone help me with this?
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Sanjiva Weerawarana wrote:
>> >> >> >
>> >> >> > I can't imagine how CXF can generate code for this .. there's no
>> >> >> element
>> >> >> > name to use to put the data in. Maybe you should also post on
>> >> >> > [EMAIL PROTECTED] and ask for them to review 

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

[Ramesh Vishwanatham]

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.

wsdl-level client side compatibility between Axis 2 and Axis 1

[Steve Cohen]

Will a WSDL written and recommended to be used with Axis 1 definitely be 
usable with Axis 2 on the client side?  We have no investment in Axis 1 
so if the switch is possible, we should probably make it now.  My group 
is going to be incorporating several web service clients into an 
application that currently has none, so my question is geared toward 
selecting the best client side technology going forward.


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

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}
  
 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: Internal/external operations

[Richard]

Keith,

> What do u mean by external and internal WS-Clients?

External web service clients would be our customers which we give a WSDL
so they can call our web service.  Ideally, we could indicate which
operations they are allowed to call but they are limited to the operations
which are for external use.

Internal web service clients would be our web application which calls
operations which are intended for internal use.  The web application might
also call operations which are intended for external use as well.

> Well, If you use something like username token authentication on your
> service, you could access the username of the caller from within your web
> service and thus vary the action you need to perform. This is just
> one way of doing it though.

Customers can use the same username to access the web service either via a
web services client outside of the firewall or by using the web
application which calls the web service from inside the firewall.

Thanks,
Richard

> Hi Richard,
>
> See comments inline.
>
> On Mon, Sep 29, 2008 at 11:09 PM, Richard <[EMAIL PROTECTED]> wrote:
>
>> Perhaps someone can help me with two questions:
>>
>> 1.  Is it possible to create a web service where most operations can be
>> called by external ws clients but some operations can be called only by
>> internal ws clients.
>
>
> What do u mean by external and internal WS-Clients?
>
>>
>>
>> 2.  The behavior of an operation needs to differ slightly depending on
>> whether an operation is called internally or externally--this can be
>> done
>> by checking the value an attribute or an element.  Is there a more
>> transparent way to determine the ws caller so that behavior such as how
>> to
>> connect to the database can differ slightly.
>
>
> Well, If you use something like username token authentication on your
> service, you could access the username of the caller from within your web
> service and thus vary the action you need to perform. This is just one way
> of doing it though.
>
> Thanks,
> Keith.
>
>>
>>
>> Thanks,
>> Richard
>>
>>
>> -
>> 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
>



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

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

[Mary Thompson]

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]

RE: I must understand the "must understand" fault

[Taariq Levack]

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-wssecurity-secext-1.0.xsd";
 soapenv:mustUnderstand="1">
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 wsu:Id="UsernameToken-3201085">
   USERNAME
   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>PASSWORD
    
 
  

And this is the response header

  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
 
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-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-secext-1.0.xsd
 : Security
  at 
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166)
  at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:363)
  at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
  at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.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 advance for looking at the one millionth "must understand" error.

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

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

[Steve Cohen]

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]

Re: Easiest way of viewing SOAP packets before they are sent

[Steve Cohen]

Thanks a lot, Keith,I never knew Eclipse had an internal TCP monitor.

This quickly shows me how much the generated packets are missing - there 
is an an expected header which the test code isn't generating, including 
extra namespaces, etc.


I will ask that question in a new thread.


keith chapman wrote:

Hi,

This blog post "Using TCP Monitor to Debug Web Service Calls 
" 
[1] might help you.


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:25 PM, Steve Cohen <[EMAIL PROTECTED] 
> wrote:


I have to write a client application that accesses an outside web
service.  I have their WSDL and have generated Java classes using
Wsdl2Java, as well as JUnit tests.

The tests are failing with
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.securityException


faultSubcode:
faultString: com.ibm.wsspi.wssecurity.SoapSecurityException:
WSEC5048E: One of "SOAP Header" elements required.
faultActor:
faultNode:
faultDetail:

{http://xml.apache.org/axis/}stackTrace:com.ibm.wsspi.wssecurity.SoapSecurityException

:


WSEC5048E: One of "SOAP Header" elements required.

Since I have samples of what a valid SOAP packet that talks to
this web service looks like I would like to see the XML that is
being generated for me by all this generated code, so that I might
better understand what the problem is.  What is the easiest way to
do this?

-
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



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

Unsigned messages not rejected in rampart/policy/sample02

[Mary Thompson]

I have recently upgraded to axis2 1.4.1 and rampart 1.4. and decided to 
switch to using ws-policy files. I modeled my use on the 
policy/sample02, but noticed that if I sent a request that was 
time-stamped but did not have the body signed it was accepted by the 
service.


I went back to sample02 and just modified the policy.xml file to remove 
the  lines and ran a standalone (server ant 
service.02) and client (ant client.02) and the same thing happened.


The message that is being sent has a syntactically correct security 
header containing a signed timestamp, but not a signed body. The 
services file says there should be a signed body, but the service 
accepts and replies to the  unsigned message.


I don't see how this can be correct behavior. Is the services.xml file 
missing something?


BTW, If I remove the timestamp and keep the body signed, the message is 
rejected for a missing timestamp.


I'm running with Java 1.5.0_16, Mac OS X 10.4.11

Mary Thompson

-
Mary R. Thompson<[EMAIL PROTECTED]>
Lawrence Berkeley National Lab  http://acs.lbl.gov/~mrt
--

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

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

[Andreas Veithen]

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(TestExecution.java:38)


Please advise what I am doing wrong.

I have tried both XMLbean and databinding approach to generate the  
client code.


Thanks
Sangita Pandit
728 1606




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

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



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

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



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

RE: What is the advantage of using async clients if Axis creates a wait thread for every request?

[Franklin, Allen]

When I enable ws-addressing and set "Use Separate Listener", as you
recommended, my client requests fail with the following:

 

2008-09-29 14:18:46,768 [ERROR] (ClientUtils.java : inferInTransport :
117) > An unknown transport called https exists.

 

Note that I am using https for my client requests.

 

Is there some additional coding I need to do?

 

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 29, 2008 2:00 PM
To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

The following is a sample Request that I sent. You would see a messageID
for each request. This ID will be used to correlate the request and
response.

Thanks,
Keith.

POST /axis2/services/StudentService HTTP/1.1 
Content-Type: text/xml; charset=UTF-8 
SOAPAction: urn:getStudents 
User-Agent: Axis2 
Host: 127.0.0.1 
Transfer-Encoding: chunked 
 
208 

   http://schemas.xmlsoap.org/soap/envelope/";>
  http://www.w3.org/2005/08/addressing";>
 
http://localhost:8081/axis2/services/StudentService
 
 
http://192.168.1.3:6060/axis2/services/StudentService122271
0373364_1/
 
 
urn:uuid:23E9D68E8168C3C3F71222710374739
 urn:getStudents
  
  
   0

On Mon, Sep 29, 2008 at 11:24 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

How do I match up responses with their corresponding requests  in my
client?

It seems like I need to be able to send an ID in the request and have
the ID returned in the callback so I can do the matching.

I don't see this mechanism.

 

 

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


To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

When you send out the first request the server would spin up in the
client side and it will not die. Hence it will be used to listen for
responses of subsequent request.

In order to use a separate listener at the client side you just need to
do this,

stub._getServiceClient().engageModule("addressing");
 
stub._getServiceClient().getOptions().setUseSeparateListener(true);

Axis2 would handle everything else for you.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 11:06 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

Would the technique that you are suggesting require the client to listen
on a different/separate TCP/IP port for every outstanding request?

 

From: keith chapman [mailto:[EMAIL PROTECTED] 

Sent: Monday, September 29, 2008 1:15 PM
To: axis-user@ws.apache.org

Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

Axis2 client support two levels of async behavior. One of them is the
one you've explained. This is something like pseudo async. The other is
where you send a request and then listen on a separate port (by spinning
up a simple http server on the client) for the response (It is
compulsory that you use WS-Addressing for this to work). This does not
block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

It is my understanding that Axis2 v1.4 creates a thread to wait for the
reply for every async client request.

What is the advantage (on the client side) of using Axis2
async/non-blocking clients if Axis creates a wait thread for every
request?

In fact the blocking call seems more efficient because it saves Axis the
trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the
duration of the call with either way, blocking or non-blocking.




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

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




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

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




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

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

Re: What is the advantage of using async clients if Axis creates a wait thread for every request?

[keith chapman]

The following is a sample Request that I sent. You would see a messageID for
each request. This ID will be used to correlate the request and response.

Thanks,
Keith.

POST /axis2/services/StudentService HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: urn:getStudents
User-Agent: Axis2
Host: 127.0.0.1
Transfer-Encoding: chunked

208

   http://schemas.xmlsoap.org/soap/envelope/";>
  http://www.w3.org/2005/08/addressing";>
 http://localhost:8081/axis2/services/StudentService

 

http://192.168.1.3:6060/axis2/services/StudentService1222710373364_1/

 

urn:uuid:23E9D68E8168C3C3F71222710374739
 urn:getStudents
  
  
   0

On Mon, Sep 29, 2008 at 11:24 PM, Franklin, Allen <
[EMAIL PROTECTED]> wrote:

>  How do I match up responses with their corresponding requests  in my
> client?
>
> It seems like I need to be able to send an ID in the request and have the
> ID returned in the callback so I can do the matching.
>
> I don't see this mechanism.
>
>
>
>
>
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Monday, September 29, 2008 1:47 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: What is the advantage of using async clients if Axis
> creates a wait thread for every request?
>
>
>
> When you send out the first request the server would spin up in the client
> side and it will not die. Hence it will be used to listen for responses of
> subsequent request.
>
> In order to use a separate listener at the client side you just need to do
> this,
>
> stub._getServiceClient().engageModule("addressing");
> stub._getServiceClient().getOptions().setUseSeparateListener(true);
>
> Axis2 would handle everything else for you.
>
> Thanks,
> Keith.
>
> On Mon, Sep 29, 2008 at 11:06 PM, Franklin, Allen <
> [EMAIL PROTECTED]> wrote:
>
> Would the technique that you are suggesting require the client to listen on
> a different/separate TCP/IP port for every outstanding request?
>
>
>
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>
> *Sent:* Monday, September 29, 2008 1:15 PM
> *To:* axis-user@ws.apache.org
>
> *Subject:* Re: What is the advantage of using async clients if Axis
> creates a wait thread for every request?
>
>
>
> Axis2 client support two levels of async behavior. One of them is the one
> you've explained. This is something like pseudo async. The other is where
> you send a request and then listen on a separate port (by spinning up a
> simple http server on the client) for the response (It is compulsory that
> you use WS-Addressing for this to work). This does not block a thread.
>
> Thanks,
> Keith.
>
> On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen <
> [EMAIL PROTECTED]> wrote:
>
> It is my understanding that Axis2 v1.4 creates a thread to wait for the
> reply for every async client request.
>
> What is the advantage (on the client side) of using Axis2
> async/non-blocking clients if Axis creates a wait thread for every request?
>
> In fact the blocking call seems more efficient because it saves Axis the
> trouble of having to create another thread.
>
> There appears to be a cost of one thread per outstanding for the duration
> of the call with either way, blocking or non-blocking.
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



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

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

Re: Axis2 and CXF - Handling WSDLs differently

[keith chapman]

TCPMon should wok irrespective of what your client or server is. It works
like a proxy sitting in between the client and server. Did you try to use
one of the plgins? Eclipse or Idea depending on what IDE you use.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 11:23 PM, jackdawson <[EMAIL PROTECTED]> wrote:

>
> If I'm not wrong then I get this when sending the request. This is the
> statement in the client that throws this exception:
>
> LoginServiceStub.TestLoginTypeResponse response =
>
>  stub.testLogin(testLoginRequestAttributes);
>
> And, I don't know why but I can't get TCP Monitor get to work. I ran the
> client and it's hanging there in the console. I won't run and won't stop.
>
> Local Monitoring port: 8080
> Host name: JISLOGINDEV
> Port: 8080
> Type: HTTP
> Timeout: 0
>
> Dumb question again:
> My client is a simple Java app. Would TCP Monitor still work? I'm not
> running it on a server.
>
> Thanks.
>
>
>
> Keithgchapman wrote:
> >
> > Did you get this message while trying ti send the request or while
> > processing the response?
> >
> > You may use TCPMonitor as explained
> > here<
> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html
> >[1]
> > to capture the SOAP messages sent.
> >
> > 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:26 PM, jackdawson <[EMAIL PROTECTED]>
> > wrote:
> >
> >>
> >> I changed the 'parts' to include element attributes and the WSDL is of
> >> 'document' style now. I generated the client stubs and the client and
> I'm
> >> still getting this exception:
> >>
> >> org.apache.axis2.AxisFault: Parameter
> >> {urn:login.safe.two.us}TestLoginType
> >> does not exist!
> >>
> >> I don't find where exactly it's going wrong even while debugging either.
> >> The service expects the parameters to be of type 'string' and that's
> what
> >> the client is sending.
> >>
> >> Here is the SOAP envelope:
> >>
> >> 
> >>  >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> >> ">
> >>
> >>
> >>http://www.w3.org/2001/XMLSchema-instance";
> >>
> >> xmlns:s2="http://www.w3.org/2001/XMLSchema";
> >> s1:type="s2:string">G13522
> >>http://www.w3.org/2001/XMLSchema-instance";
> >>
> >> xmlns:s4="http://www.w3.org/2001/XMLSchema";
> >> s3:type="s4:string">P9534
> >>
> >>
> >> 
> >>
> >>
> >> Am I missing something here?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Keithgchapman wrote:
> >> >
> >> > In your WSDL the parts section look RPC while the binding is document.
> >> I
> >> > recommend you that you make both of them the same. Either make both
> RPC
> >> > (just change the binding style to rpc) or both document (by making the
> >> > part
> >> > refer to an element instead of a type).
> >> >
> >> > Thanks,
> >> > Keith.
> >> >
> >> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]>
> >> > wrote:
> >> >
> >> >>
> >> >> I posted in there too. They say that it's not mandatory to follow the
> >> >> WS-I
> >> >> basic profile as they are just guidelines and this is what they
> >> exactly
> >> >> said:
> >> >>
> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >>
> >> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >> >>
> >> >> Instead, I would like to get help in moving ahead with Axis2.
> >> >> Can anyone help me with this?
> >> >>
> >> >> Thanks.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Sanjiva Weerawarana wrote:
> >> >> >
> >> >> > I can't imagine how CXF can generate code for this .. there's no
> >> >> element
> >> >> > name to use to put the data in. Maybe you should also post on
> >> >> > [EMAIL PROTECTED] and ask for them to review this.
> >> >> >
> >> >> > Sanjiva.
> >> >> >
> >> >> > keith chapman wrote:
> >> >> >> This WSDL looks  invalid. As you have said when a message part
> >> refers
> >> >> to
> >> >> >> a type directly it is RPC whereas when it refers to an element its
> >> >> known
> >> >> >> as document. Now the messages parts of your WSDL is RPC but your
> >> >> binsind
> >> >> >> says that its document. I feel that the WSDL is incorrect and
> hence
> >> >> >> Axis2 is right in saying that the element is missing.
> >> >> >>
> >> >> >> Thanks,
> >> >> >> Keith.
> >> >> >>
> >> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <
> [EMAIL PROTECTED]
> >> >> >> > wrote:
> >> >> >>
> >> >> >>
> >> >> >> Here is what I found:
> >> >> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate
> >> >> Java
> >> >> >> source code
> >> >> >> from WSDL file) to generate code from this WSDL, it didn't
> >> allow
> >> >> me.
> >> >> >>It kept throwing me an error -
> >> >> >>"An error occurred while completing the
> >> >> >> 

RE: What is the advantage of using async clients if Axis creates a wait thread for every request?

[Franklin, Allen]

How do I match up responses with their corresponding requests  in my
client?

It seems like I need to be able to send an ID in the request and have
the ID returned in the callback so I can do the matching.

I don't see this mechanism.

 

 

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 29, 2008 1:47 PM
To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

When you send out the first request the server would spin up in the
client side and it will not die. Hence it will be used to listen for
responses of subsequent request.

In order to use a separate listener at the client side you just need to
do this,

stub._getServiceClient().engageModule("addressing");
 
stub._getServiceClient().getOptions().setUseSeparateListener(true);

Axis2 would handle everything else for you.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 11:06 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

Would the technique that you are suggesting require the client to listen
on a different/separate TCP/IP port for every outstanding request?

 

From: keith chapman [mailto:[EMAIL PROTECTED] 

Sent: Monday, September 29, 2008 1:15 PM
To: axis-user@ws.apache.org

Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

Axis2 client support two levels of async behavior. One of them is the
one you've explained. This is something like pseudo async. The other is
where you send a request and then listen on a separate port (by spinning
up a simple http server on the client) for the response (It is
compulsory that you use WS-Addressing for this to work). This does not
block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

It is my understanding that Axis2 v1.4 creates a thread to wait for the
reply for every async client request.

What is the advantage (on the client side) of using Axis2
async/non-blocking clients if Axis creates a wait thread for every
request?

In fact the blocking call seems more efficient because it saves Axis the
trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the
duration of the call with either way, blocking or non-blocking.




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

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




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

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

Re: Easiest way of viewing SOAP packets before they are sent

[keith chapman]

Hi,

This blog post "Using TCP Monitor to Debug Web Service
Calls"
[1] might help you.

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:25 PM, Steve Cohen <[EMAIL PROTECTED]>wrote:

> I have to write a client application that accesses an outside web service.
>  I have their WSDL and have generated Java classes using Wsdl2Java, as well
> as JUnit tests.
>
> The tests are failing with
> AxisFault
> faultCode: {
> http://schemas.xmlsoap.org/soap/envelope/}Server.securityException<
> http://schemas.xmlsoap.org/soap/envelope/%7DServer.securityException>
> faultSubcode:
> faultString: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: One
> of "SOAP Header" elements required.
> faultActor:
> faultNode:
> faultDetail:
> {
> http://xml.apache.org/axis/}stackTrace:com.ibm.wsspi.wssecurity.SoapSecurityException:
> <
> http://xml.apache.org/axis/%7DstackTrace:com.ibm.wsspi.wssecurity.SoapSecurityException:>
> WSEC5048E: One of "SOAP Header" elements required.
>
> Since I have samples of what a valid SOAP packet that talks to this web
> service looks like I would like to see the XML that is being generated for
> me by all this generated code, so that I might better understand what the
> problem is.  What is the easiest way to do this?
>
> -
> 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

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

If I'm not wrong then I get this when sending the request. This is the
statement in the client that throws this exception:

LoginServiceStub.TestLoginTypeResponse response = 

stub.testLogin(testLoginRequestAttributes);

And, I don't know why but I can't get TCP Monitor get to work. I ran the
client and it's hanging there in the console. I won't run and won't stop.

Local Monitoring port: 8080
Host name: JISLOGINDEV
Port: 8080
Type: HTTP
Timeout: 0

Dumb question again:
My client is a simple Java app. Would TCP Monitor still work? I'm not
running it on a server.

Thanks.



Keithgchapman wrote:
> 
> Did you get this message while trying ti send the request or while
> processing the response?
> 
> You may use TCPMonitor as explained
> here[1]
> to capture the SOAP messages sent.
> 
> 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:26 PM, jackdawson <[EMAIL PROTECTED]>
> wrote:
> 
>>
>> I changed the 'parts' to include element attributes and the WSDL is of
>> 'document' style now. I generated the client stubs and the client and I'm
>> still getting this exception:
>>
>> org.apache.axis2.AxisFault: Parameter
>> {urn:login.safe.two.us}TestLoginType
>> does not exist!
>>
>> I don't find where exactly it's going wrong even while debugging either.
>> The service expects the parameters to be of type 'string' and that's what
>> the client is sending.
>>
>> Here is the SOAP envelope:
>>
>> 
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> ">
>>
>>
>>http://www.w3.org/2001/XMLSchema-instance";
>>   
>> xmlns:s2="http://www.w3.org/2001/XMLSchema";
>> s1:type="s2:string">G13522
>>http://www.w3.org/2001/XMLSchema-instance";
>>   
>> xmlns:s4="http://www.w3.org/2001/XMLSchema";
>> s3:type="s4:string">P9534
>>
>>
>> 
>>
>>
>> Am I missing something here?
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > In your WSDL the parts section look RPC while the binding is document.
>> I
>> > recommend you that you make both of them the same. Either make both RPC
>> > (just change the binding style to rpc) or both document (by making the
>> > part
>> > refer to an element instead of a type).
>> >
>> > Thanks,
>> > Keith.
>> >
>> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]>
>> > wrote:
>> >
>> >>
>> >> I posted in there too. They say that it's not mandatory to follow the
>> >> WS-I
>> >> basic profile as they are just guidelines and this is what they
>> exactly
>> >> said:
>> >>
>> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >>
>> >>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>> >>
>> >> Instead, I would like to get help in moving ahead with Axis2.
>> >> Can anyone help me with this?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >> Sanjiva Weerawarana wrote:
>> >> >
>> >> > I can't imagine how CXF can generate code for this .. there's no
>> >> element
>> >> > name to use to put the data in. Maybe you should also post on
>> >> > [EMAIL PROTECTED] and ask for them to review this.
>> >> >
>> >> > Sanjiva.
>> >> >
>> >> > keith chapman wrote:
>> >> >> This WSDL looks  invalid. As you have said when a message part
>> refers
>> >> to
>> >> >> a type directly it is RPC whereas when it refers to an element its
>> >> known
>> >> >> as document. Now the messages parts of your WSDL is RPC but your
>> >> binsind
>> >> >> says that its document. I feel that the WSDL is incorrect and hence
>> >> >> Axis2 is right in saying that the element is missing.
>> >> >>
>> >> >> Thanks,
>> >> >> Keith.
>> >> >>
>> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED]
>> >> >> > wrote:
>> >> >>
>> >> >>
>> >> >> Here is what I found:
>> >> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate
>> >> Java
>> >> >> source code
>> >> >> from WSDL file) to generate code from this WSDL, it didn't
>> allow
>> >> me.
>> >> >>It kept throwing me an error -
>> >> >>"An error occurred while completing the
>> >> >> process -
>> >> >> java.lang.InterruptedException
>> >> >> No element type is defind for the
>> message
>> >> >> x"
>> >> >>2.) Then, I switched to CXF 2.0.8 and tried to generate
>> the
>> >> >> client as I did
>> >> >> with Axis2 and surprisingly, it got through and created the
>> client
>> >> >> side
>> >> >> stubs.
>> >> >>CXF doesn't see this WSDL as a bad one.
>> >> >>
>> >> >>Please correct me if I'm wrong. To my kno

Re: Internal/external operations

[keith chapman]

Hi Richard,

See comments inline.

On Mon, Sep 29, 2008 at 11:09 PM, Richard <[EMAIL PROTECTED]> wrote:

> Perhaps someone can help me with two questions:
>
> 1.  Is it possible to create a web service where most operations can be
> called by external ws clients but some operations can be called only by
> internal ws clients.


What do u mean by external and internal WS-Clients?

>
>
> 2.  The behavior of an operation needs to differ slightly depending on
> whether an operation is called internally or externally--this can be done
> by checking the value an attribute or an element.  Is there a more
> transparent way to determine the ws caller so that behavior such as how to
> connect to the database can differ slightly.


Well, If you use something like username token authentication on your
service, you could access the username of the caller from within your web
service and thus vary the action you need to perform. This is just one way
of doing it though.

Thanks,
Keith.

>
>
> Thanks,
> Richard
>
>
> -
> 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

License question on WSDL4J in Axis 1.2.1

[Srini2008]

Hi,

I plan to use Apache Axis 1.2.1 for our software application in which I
intend to redistribute Apache Axis 1.2.1.

I have a question on the WSDL4J component which is under "Common Public
License version 1.0" on it. My legal team says its not a friendly license
and wants to exclude this component from distribution, but I cannot.

When I went through the maillist archive I saw a thread mentioning that
WSDL4J code was donated to Apache from IBM at some point of time. Can
someone confirm if this WSDL4J is okay to redistribute under ASL or is it
still under CPL?

Thanks,
Srini

BTW I already searched through this list and found this thread but still
wanted to confirm if things have changed since this thread was posted
http://www.nabble.com/forum/Search.jtp?query=wsdl4j+license&local=y&forum=232&daterange=0&startdate=&enddate
-- 
View this message in context: 
http://www.nabble.com/License-question-on-WSDL4J-in-Axis-1.2.1-tp19728531p19728531.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: What is the advantage of using async clients if Axis creates a wait thread for every request?

[keith chapman]

When you send out the first request the server would spin up in the client
side and it will not die. Hence it will be used to listen for responses of
subsequent request.

In order to use a separate listener at the client side you just need to do
this,

stub._getServiceClient().engageModule("addressing");
stub._getServiceClient().getOptions().setUseSeparateListener(true);

Axis2 would handle everything else for you.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 11:06 PM, Franklin, Allen <
[EMAIL PROTECTED]> wrote:

>  Would the technique that you are suggesting require the client to listen
> on a different/separate TCP/IP port for every outstanding request?
>
>
>
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Monday, September 29, 2008 1:15 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: What is the advantage of using async clients if Axis
> creates a wait thread for every request?
>
>
>
> Axis2 client support two levels of async behavior. One of them is the one
> you've explained. This is something like pseudo async. The other is where
> you send a request and then listen on a separate port (by spinning up a
> simple http server on the client) for the response (It is compulsory that
> you use WS-Addressing for this to work). This does not block a thread.
>
> Thanks,
> Keith.
>
> On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen <
> [EMAIL PROTECTED]> wrote:
>
> It is my understanding that Axis2 v1.4 creates a thread to wait for the
> reply for every async client request.
>
> What is the advantage (on the client side) of using Axis2
> async/non-blocking clients if Axis creates a wait thread for every request?
>
> In fact the blocking call seems more efficient because it saves Axis the
> trouble of having to create another thread.
>
> There appears to be a cost of one thread per outstanding for the duration
> of the call with either way, blocking or non-blocking.
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



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

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

Internal/external operations

[Richard]

Perhaps someone can help me with two questions:

1.  Is it possible to create a web service where most operations can be
called by external ws clients but some operations can be called only by
internal ws clients.

2.  The behavior of an operation needs to differ slightly depending on
whether an operation is called internally or externally--this can be done
by checking the value an attribute or an element.  Is there a more
transparent way to determine the ws caller so that behavior such as how to
connect to the database can differ slightly.

Thanks,
Richard


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

RE: What is the advantage of using async clients if Axis creates a wait thread for every request?

[Franklin, Allen]

Would the technique that you are suggesting require the client to listen
on a different/separate TCP/IP port for every outstanding request?

 

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 29, 2008 1:15 PM
To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

Axis2 client support two levels of async behavior. One of them is the
one you've explained. This is something like pseudo async. The other is
where you send a request and then listen on a separate port (by spinning
up a simple http server on the client) for the response (It is
compulsory that you use WS-Addressing for this to work). This does not
block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

It is my understanding that Axis2 v1.4 creates a thread to wait for the
reply for every async client request.

What is the advantage (on the client side) of using Axis2
async/non-blocking clients if Axis creates a wait thread for every
request?

In fact the blocking call seems more efficient because it saves Axis the
trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the
duration of the call with either way, blocking or non-blocking.




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

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

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

[keith chapman]

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(TestExecution.java:38)
>>
>> Please advise what I am doing wrong.
>>
>> I have tried both XMLbean and databinding approach to generate the client
>> code.
>>
>> Thanks
>> *Sangita Pandit*
>> *728 1606*
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>



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

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

RE: What is the advantage of using async clients if Axis creates a wait thread for every request?

[Franklin, Allen]

Can you recommend any sample code for me to look at?

I have been using 'wsdl2java -a' to generate client stubs.

What you are recommending sounds a bit more complex.

 

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 29, 2008 1:15 PM
To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis
creates a wait thread for every request?

 

Axis2 client support two levels of async behavior. One of them is the
one you've explained. This is something like pseudo async. The other is
where you send a request and then listen on a separate port (by spinning
up a simple http server on the client) for the response (It is
compulsory that you use WS-Addressing for this to work). This does not
block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen
<[EMAIL PROTECTED]> wrote:

It is my understanding that Axis2 v1.4 creates a thread to wait for the
reply for every async client request.

What is the advantage (on the client side) of using Axis2
async/non-blocking clients if Axis creates a wait thread for every
request?

In fact the blocking call seems more efficient because it saves Axis the
trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the
duration of the call with either way, blocking or non-blocking.




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

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

Re: What is the advantage of using async clients if Axis creates a wait thread for every request?

[keith chapman]

Axis2 client support two levels of async behavior. One of them is the one
you've explained. This is something like pseudo async. The other is where
you send a request and then listen on a separate port (by spinning up a
simple http server on the client) for the response (It is compulsory that
you use WS-Addressing for this to work). This does not block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen <
[EMAIL PROTECTED]> wrote:

>  It is my understanding that Axis2 v1.4 creates a thread to wait for the
> reply for every async client request.
>
> What is the advantage (on the client side) of using Axis2
> async/non-blocking clients if Axis creates a wait thread for every request?
>
> In fact the blocking call seems more efficient because it saves Axis the
> trouble of having to create another thread.
>
> There appears to be a cost of one thread per outstanding for the duration
> of the call with either way, blocking or non-blocking.
>



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

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

Re: Axis2 and CXF - Handling WSDLs differently

[keith chapman]

Did you get this message while trying ti send the request or while
processing the response?

You may use TCPMonitor as explained
here[1]
to capture the SOAP messages sent.

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:26 PM, jackdawson <[EMAIL PROTECTED]> wrote:

>
> I changed the 'parts' to include element attributes and the WSDL is of
> 'document' style now. I generated the client stubs and the client and I'm
> still getting this exception:
>
> org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
> does not exist!
>
> I don't find where exactly it's going wrong even while debugging either.
> The service expects the parameters to be of type 'string' and that's what
> the client is sending.
>
> Here is the SOAP envelope:
>
> 
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>http://www.w3.org/2001/XMLSchema-instance";
>xmlns:s2="http://www.w3.org/2001/XMLSchema";
> s1:type="s2:string">G13522
>http://www.w3.org/2001/XMLSchema-instance";
>xmlns:s4="http://www.w3.org/2001/XMLSchema";
> s3:type="s4:string">P9534
>
>
> 
>
>
> Am I missing something here?
>
> Thanks.
>
>
>
>
>
>
>
>
>
> Keithgchapman wrote:
> >
> > In your WSDL the parts section look RPC while the binding is document. I
> > recommend you that you make both of them the same. Either make both RPC
> > (just change the binding style to rpc) or both document (by making the
> > part
> > refer to an element instead of a type).
> >
> > Thanks,
> > Keith.
> >
> > On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]>
> > wrote:
> >
> >>
> >> I posted in there too. They say that it's not mandatory to follow the
> >> WS-I
> >> basic profile as they are just guidelines and this is what they exactly
> >> said:
> >>
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >>
> >>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
> >>
> >> Instead, I would like to get help in moving ahead with Axis2.
> >> Can anyone help me with this?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >> Sanjiva Weerawarana wrote:
> >> >
> >> > I can't imagine how CXF can generate code for this .. there's no
> >> element
> >> > name to use to put the data in. Maybe you should also post on
> >> > [EMAIL PROTECTED] and ask for them to review this.
> >> >
> >> > Sanjiva.
> >> >
> >> > keith chapman wrote:
> >> >> This WSDL looks  invalid. As you have said when a message part refers
> >> to
> >> >> a type directly it is RPC whereas when it refers to an element its
> >> known
> >> >> as document. Now the messages parts of your WSDL is RPC but your
> >> binsind
> >> >> says that its document. I feel that the WSDL is incorrect and hence
> >> >> Axis2 is right in saying that the element is missing.
> >> >>
> >> >> Thanks,
> >> >> Keith.
> >> >>
> >> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED]
> >> >> > wrote:
> >> >>
> >> >>
> >> >> Here is what I found:
> >> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate
> >> Java
> >> >> source code
> >> >> from WSDL file) to generate code from this WSDL, it didn't allow
> >> me.
> >> >>It kept throwing me an error -
> >> >>"An error occurred while completing the
> >> >> process -
> >> >> java.lang.InterruptedException
> >> >> No element type is defind for the message
> >> >> x"
> >> >>2.) Then, I switched to CXF 2.0.8 and tried to generate
> the
> >> >> client as I did
> >> >> with Axis2 and surprisingly, it got through and created the
> client
> >> >> side
> >> >> stubs.
> >> >>CXF doesn't see this WSDL as a bad one.
> >> >>
> >> >>Please correct me if I'm wrong. To my knowledge,
> >> when
> >> >> you define "type"
> >> >> attribute for the "message" and not the "element" attribute then
> >> it
> >> >> has to
> >> >> be an "rpc" style.
> >> >>Axis2 knows it but CXF ignores it.
> >> >>
> >> >>Can anyone let me know why there's a difference in
> >> >> handling the WSDLs?
> >> >>If I modify the WSDL as Axis2 wants me to and
> >> >> generate just the client and
> >> >> hit the service (which is already existing), will I still be able
> >> to
> >> >> succeed?
> >> >>
> >> >> Here is the WSDL I'm talking about:
> >> >>
> >> >> 
> >> >> http://login.safe.two.us>"
> >> >>xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >> >>xmlns:impl="urn:login.safe.two.us <
> http://login.safe.two.us

What is the advantage of using async clients if Axis creates a wait thread for every request?

[Franklin, Allen]

It is my understanding that Axis2 v1.4 creates a thread to wait for the
reply for every async client request.

What is the advantage (on the client side) of using Axis2
async/non-blocking clients if Axis creates a wait thread for every
request?

In fact the blocking call seems more efficient because it saves Axis the
trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the
duration of the call with either way, blocking or non-blocking.

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

I changed the 'parts' to include element attributes and the WSDL is of
'document' style now. I generated the client stubs and the client and I'm
still getting this exception: 

org.apache.axis2.AxisFault: Parameter {urn:login.safe.two.us}TestLoginType
does not exist!

I don't find where exactly it's going wrong even while debugging either.
The service expects the parameters to be of type 'string' and that's what
the client is sending.

Here is the SOAP envelope:


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


http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:s2="http://www.w3.org/2001/XMLSchema";
s1:type="s2:string">G13522
http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:s4="http://www.w3.org/2001/XMLSchema";
s3:type="s4:string">P9534





Am I missing something here?

Thanks.









Keithgchapman wrote:
> 
> In your WSDL the parts section look RPC while the binding is document. I
> recommend you that you make both of them the same. Either make both RPC
> (just change the binding style to rpc) or both document (by making the
> part
> refer to an element instead of a type).
> 
> Thanks,
> Keith.
> 
> On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]>
> wrote:
> 
>>
>> I posted in there too. They say that it's not mandatory to follow the
>> WS-I
>> basic profile as they are just guidelines and this is what they exactly
>> said:
>>
>>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>>
>> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>>
>> Instead, I would like to get help in moving ahead with Axis2.
>> Can anyone help me with this?
>>
>> Thanks.
>>
>>
>>
>>
>> Sanjiva Weerawarana wrote:
>> >
>> > I can't imagine how CXF can generate code for this .. there's no
>> element
>> > name to use to put the data in. Maybe you should also post on
>> > [EMAIL PROTECTED] and ask for them to review this.
>> >
>> > Sanjiva.
>> >
>> > keith chapman wrote:
>> >> This WSDL looks  invalid. As you have said when a message part refers
>> to
>> >> a type directly it is RPC whereas when it refers to an element its
>> known
>> >> as document. Now the messages parts of your WSDL is RPC but your
>> binsind
>> >> says that its document. I feel that the WSDL is incorrect and hence
>> >> Axis2 is right in saying that the element is missing.
>> >>
>> >> Thanks,
>> >> Keith.
>> >>
>> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED]
>> >> > wrote:
>> >>
>> >>
>> >> Here is what I found:
>> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate
>> Java
>> >> source code
>> >> from WSDL file) to generate code from this WSDL, it didn't allow
>> me.
>> >>It kept throwing me an error -
>> >>"An error occurred while completing the
>> >> process -
>> >> java.lang.InterruptedException
>> >> No element type is defind for the message
>> >> x"
>> >>2.) Then, I switched to CXF 2.0.8 and tried to generate the
>> >> client as I did
>> >> with Axis2 and surprisingly, it got through and created the client
>> >> side
>> >> stubs.
>> >>CXF doesn't see this WSDL as a bad one.
>> >>
>> >>Please correct me if I'm wrong. To my knowledge,
>> when
>> >> you define "type"
>> >> attribute for the "message" and not the "element" attribute then
>> it
>> >> has to
>> >> be an "rpc" style.
>> >>Axis2 knows it but CXF ignores it.
>> >>
>> >>Can anyone let me know why there's a difference in
>> >> handling the WSDLs?
>> >>If I modify the WSDL as Axis2 wants me to and
>> >> generate just the client and
>> >> hit the service (which is already existing), will I still be able
>> to
>> >> succeed?
>> >>
>> >> Here is the WSDL I'm talking about:
>> >>
>> >> 
>> >> http://login.safe.two.us>"
>> >>xmlns:apachesoap="http://xml.apache.org/xml-soap";
>> >>xmlns:impl="urn:login.safe.two.us > >"
>> >>xmlns:intf="urn:login.safe.two.us > >"
>> >>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>> >>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>> >>xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>> >>
>> >>> >>targetNamespace="urn:login.safe.two.us
>> >> "
>> >>xmlns="http://www.w3.org/2001/XMLSchema";>
>> >>
>> >>
>> >>
>> >>> >> maxOccurs="1" minOccurs="1" type="xsd

Easiest way of viewing SOAP packets before they are sent

[Steve Cohen]

I have to write a client application that accesses an outside web 
service.  I have their WSDL and have generated Java classes using 
Wsdl2Java, as well as JUnit tests.


The tests are failing with
AxisFault
faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.securityException 


faultSubcode:
faultString: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5048E: 
One of "SOAP Header" elements required.

faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:com.ibm.wsspi.wssecurity.SoapSecurityException: 
 
WSEC5048E: One of "SOAP Header" elements required.


Since I have samples of what a valid SOAP packet that talks to this web 
service looks like I would like to see the XML that is being generated 
for me by all this generated code, so that I might better understand 
what the problem is.  What is the easiest way to do this?


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

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

[Sangita_Pandit]

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) 
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:401) 
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:228) 
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
) 
at
com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusSer
viceStub.java:1056) 
at
com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatu
sServiceTest.java:37) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) 
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39) 
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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(JUn
it3TestReference.java:130) 
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
va:38) 

Please advise what I am doing wrong. 

I have tried both XMLbean and databinding approach to generate
the client code. 

Thanks 
Sangita Pandit 
728 1606 




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

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

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

[keith chapman]

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(TestExecution.java:38)
>
> Please advise what I am doing wrong.
>
> I have tried both XMLbean and databinding approach to generate the client
> code.
>
> Thanks
> *Sangita Pandit*
> *728 1606*
>



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

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

RE: I must understand the "must understand" fault

[Taariq Levack]

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-wssecurity-secext-1.0.xsd";
 soapenv:mustUnderstand="1">
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
 wsu:Id="UsernameToken-3201085">
   USERNAME
   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>PASSWORD
    
 
  

And this is the response header

  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
 
xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-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-secext-1.0.xsd
 : Security
  at 
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166)
  at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:363)
  at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
  at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.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 advance for looking at the one millionth "must understand" error.


http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
	
	  
		http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
		  
			
			  

			  
			
			
			  

			  
			
			
			  

			  
			
		  
		
		http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
			
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"; />
		  
		
		
		http://ws.apache.org/rampart/policy";> 
			SOMEUSERNAME
			ws.client.PwdCallbackHandler
		
		
	  
	
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 and CXF - Handling WSDLs differently

[keith chapman]

In your WSDL the parts section look RPC while the binding is document. I
recommend you that you make both of them the same. Either make both RPC
(just change the binding style to rpc) or both document (by making the part
refer to an element instead of a type).

Thanks,
Keith.

On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]> wrote:

>
> I posted in there too. They say that it's not mandatory to follow the WS-I
> basic profile as they are just guidelines and this is what they exactly
> said:
>
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> Instead, I would like to get help in moving ahead with Axis2.
> Can anyone help me with this?
>
> Thanks.
>
>
>
>
> Sanjiva Weerawarana wrote:
> >
> > I can't imagine how CXF can generate code for this .. there's no element
> > name to use to put the data in. Maybe you should also post on
> > [EMAIL PROTECTED] and ask for them to review this.
> >
> > Sanjiva.
> >
> > keith chapman wrote:
> >> This WSDL looks  invalid. As you have said when a message part refers to
> >> a type directly it is RPC whereas when it refers to an element its known
> >> as document. Now the messages parts of your WSDL is RPC but your binsind
> >> says that its document. I feel that the WSDL is incorrect and hence
> >> Axis2 is right in saying that the element is missing.
> >>
> >> Thanks,
> >> Keith.
> >>
> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED]
> >> > wrote:
> >>
> >>
> >> Here is what I found:
> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> >> source code
> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
> >>It kept throwing me an error -
> >>"An error occurred while completing the
> >> process -
> >> java.lang.InterruptedException
> >> No element type is defind for the message
> >> x"
> >>2.) Then, I switched to CXF 2.0.8 and tried to generate the
> >> client as I did
> >> with Axis2 and surprisingly, it got through and created the client
> >> side
> >> stubs.
> >>CXF doesn't see this WSDL as a bad one.
> >>
> >>Please correct me if I'm wrong. To my knowledge, when
> >> you define "type"
> >> attribute for the "message" and not the "element" attribute then it
> >> has to
> >> be an "rpc" style.
> >>Axis2 knows it but CXF ignores it.
> >>
> >>Can anyone let me know why there's a difference in
> >> handling the WSDLs?
> >>If I modify the WSDL as Axis2 wants me to and
> >> generate just the client and
> >> hit the service (which is already existing), will I still be able to
> >> succeed?
> >>
> >> Here is the WSDL I'm talking about:
> >>
> >> 
> >> http://login.safe.two.us>"
> >>xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >>xmlns:impl="urn:login.safe.two.us  >"
> >>xmlns:intf="urn:login.safe.two.us  >"
> >>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >>xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >>
> >> >>targetNamespace="urn:login.safe.two.us
> >> "
> >>xmlns="http://www.w3.org/2001/XMLSchema";>
> >>
> >>
> >>
> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> >> nillable="true" type="xsd:string" />
> >>
> >>
> >>
> >>
> >>
> >> >> nillable="true" type="xsd:string" />
> >> >> type="xsd:boolean" />
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> >> type="impl:TestLoginType"/>
> >>
> >>
> >>
> >> >> type="impl:TestLoginTypeResponse"/>
> >>
> >>
> >>
> >>
> >> >> name="testLoginRequest" />
> >> >> name="testLoginResponse" />
> >>
> >>
> >>
> >> >> type="impl:LoginServicePortType">
> >> >> transport="http://schemas.xmlsoap.org/soap/http"; />
> >> 

Re: Axis2 and CXF - Handling WSDLs differently

[keith chapman]

On Mon, Sep 29, 2008 at 6:57 PM, jackdawson <[EMAIL PROTECTED]> wrote:

>
> I posted in there too. They say that it's not mandatory to follow the WS-I
> basic profile as they are just guidelines and this is what they exactly
> said:
>
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
>
> http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html


Interesting replies on the CXF list. Its true that its not required for a
WSDL to be WS-I  compliant to be valid. But irrespective of what WS-I says I
think this WSDL is invalid (According to the WSDL spec). Section 3.4 [1] of
the WSDL spec states that "The *style* attribute indicates whether the
operation is RPC-oriented (messages containing parameters and return values)
or document-oriented (message containing document(s))." It clearly states
there that referring to types from a part is RPC and referring to elements
from a part is document style.

I don't see how its possible for parts to be RPC and the binding to be
document. This sure could be confusing and this is the very reason why WSDL
2.0 got rid of this mess. In WSDL 2.0 everything is doc/lit.

Thanks,
Keith.


[1] http://www.w3.org/TR/wsdl#_soap:operation

>
> 
>
> Instead, I would like to get help in moving ahead with Axis2.
> Can anyone help me with this?
>
> Thanks.
>
>
>
>
> Sanjiva Weerawarana wrote:
> >
> > I can't imagine how CXF can generate code for this .. there's no element
> > name to use to put the data in. Maybe you should also post on
> > [EMAIL PROTECTED] and ask for them to review this.
> >
> > Sanjiva.
> >
> > keith chapman wrote:
> >> This WSDL looks  invalid. As you have said when a message part refers to
> >> a type directly it is RPC whereas when it refers to an element its known
> >> as document. Now the messages parts of your WSDL is RPC but your binsind
> >> says that its document. I feel that the WSDL is incorrect and hence
> >> Axis2 is right in saying that the element is missing.
> >>
> >> Thanks,
> >> Keith.
> >>
> >> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED]
> >> > wrote:
> >>
> >>
> >> Here is what I found:
> >>1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
> >> source code
> >> from WSDL file) to generate code from this WSDL, it didn't allow me.
> >>It kept throwing me an error -
> >>"An error occurred while completing the
> >> process -
> >> java.lang.InterruptedException
> >> No element type is defind for the message
> >> x"
> >>2.) Then, I switched to CXF 2.0.8 and tried to generate the
> >> client as I did
> >> with Axis2 and surprisingly, it got through and created the client
> >> side
> >> stubs.
> >>CXF doesn't see this WSDL as a bad one.
> >>
> >>Please correct me if I'm wrong. To my knowledge, when
> >> you define "type"
> >> attribute for the "message" and not the "element" attribute then it
> >> has to
> >> be an "rpc" style.
> >>Axis2 knows it but CXF ignores it.
> >>
> >>Can anyone let me know why there's a difference in
> >> handling the WSDLs?
> >>If I modify the WSDL as Axis2 wants me to and
> >> generate just the client and
> >> hit the service (which is already existing), will I still be able to
> >> succeed?
> >>
> >> Here is the WSDL I'm talking about:
> >>
> >> 
> >> http://login.safe.two.us>"
> >>xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >>xmlns:impl="urn:login.safe.two.us  >"
> >>xmlns:intf="urn:login.safe.two.us  >"
> >>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >>xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >>
> >> >>targetNamespace="urn:login.safe.two.us
> >> "
> >>xmlns="http://www.w3.org/2001/XMLSchema";>
> >>
> >>
> >>
> >> >> maxOccurs="1" minOccurs="1" type="xsd:string" />
> >> >> nillable="true" type="xsd:string" />
> >>
> >>
> >>
> >>
> >>
> >> >> nillable="true" type="xsd:string" />
> >> >> type="xsd:boolean" />
> >>
> >>   

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

[Sangita_Pandit]

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)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:401)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163
)
at
com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusSer
viceStub.java:1056)
at
com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatu
sServiceTest.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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(JUn
it3TestReference.java:130)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
va:38)

Please advise what I am doing wrong.

I have tried both XMLbean and databinding approach to generate the
client code.

Thanks
Sangita Pandit
728 1606

Re: Axis2 and CXF - Handling WSDLs differently

[jackdawson]

I posted in there too. They say that it's not mandatory to follow the WS-I
basic profile as they are just guidelines and this is what they exactly
said:

http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
http://www.nabble.com/Axis2-and-CXF---Handling-WSDLs-differently-to19696717.html
 

Instead, I would like to get help in moving ahead with Axis2.
Can anyone help me with this?

Thanks.




Sanjiva Weerawarana wrote:
> 
> I can't imagine how CXF can generate code for this .. there's no element 
> name to use to put the data in. Maybe you should also post on 
> [EMAIL PROTECTED] and ask for them to review this.
> 
> Sanjiva.
> 
> keith chapman wrote:
>> This WSDL looks  invalid. As you have said when a message part refers to 
>> a type directly it is RPC whereas when it refers to an element its known 
>> as document. Now the messages parts of your WSDL is RPC but your binsind 
>> says that its document. I feel that the WSDL is incorrect and hence 
>> Axis2 is right in saying that the element is missing.
>> 
>> Thanks,
>> Keith.
>> 
>> On Fri, Sep 26, 2008 at 7:45 PM, jackdawson <[EMAIL PROTECTED] 
>> > wrote:
>> 
>> 
>> Here is what I found:
>>1.) When I used Axis2 Eclipse Codegen plugins (Generate Java
>> source code
>> from WSDL file) to generate code from this WSDL, it didn't allow me.
>>It kept throwing me an error -
>>"An error occurred while completing the
>> process -
>> java.lang.InterruptedException
>> No element type is defind for the message
>> x"
>>2.) Then, I switched to CXF 2.0.8 and tried to generate the
>> client as I did
>> with Axis2 and surprisingly, it got through and created the client
>> side
>> stubs.
>>CXF doesn't see this WSDL as a bad one.
>> 
>>Please correct me if I'm wrong. To my knowledge, when
>> you define "type"
>> attribute for the "message" and not the "element" attribute then it
>> has to
>> be an "rpc" style.
>>Axis2 knows it but CXF ignores it.
>> 
>>Can anyone let me know why there's a difference in
>> handling the WSDLs?
>>If I modify the WSDL as Axis2 wants me to and
>> generate just the client and
>> hit the service (which is already existing), will I still be able to
>> succeed?
>> 
>> Here is the WSDL I'm talking about:
>> 
>> 
>> http://login.safe.two.us>"
>>xmlns:apachesoap="http://xml.apache.org/xml-soap";
>>xmlns:impl="urn:login.safe.two.us "
>>xmlns:intf="urn:login.safe.two.us "
>>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>>xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>>
>>>targetNamespace="urn:login.safe.two.us
>> "
>>xmlns="http://www.w3.org/2001/XMLSchema";>
>> 
>>
>>
>>> maxOccurs="1" minOccurs="1" type="xsd:string" />
>>> nillable="true" type="xsd:string" />
>>
>>
>> 
>>
>>
>>> nillable="true" type="xsd:string" />
>>> type="xsd:boolean" />
>>
>>
>> 
>>
>>
>> 
>>
>>> type="impl:TestLoginType"/>
>>
>> 
>>
>>> type="impl:TestLoginTypeResponse"/>
>>
>> 
>>
>>
>>> name="testLoginRequest" />
>>> name="testLoginResponse" />
>>
>>
>> 
>>> type="impl:LoginServicePortType">
>>> transport="http://schemas.xmlsoap.org/soap/http"; />
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>>
>>> name="LoginService">
>>>
>> location="http://JISLOGINDEV:8080/JisAuthentication/services/safelogin";
>> />
>>
>>
>> 
>> 
>> 
>> 
>>Thanks.
>> --
>>

I must understand the "must understand" fault

[Taariq Levack]

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 advance for looking at the one millionth "must understand"
error.

RE: axis/tomcat restart problem

[srdjan]

Is the question ment for me or for David?:)

mgainty wrote:
> 
> 
> David-
> 
> assuming you redeployed AxisServlet to the remote server (copy and unwar
> to axis folder in webapps)
> did you recycle axis on the remote server?
> did you verify the servlet has been redeployed?
> can you display the service entry from the wsdd so we can ensure the
> parameters are correct?
> 
> 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: Fri, 26 Sep 2008 07:48:28 -0700
>> From: [EMAIL PROTECTED]
>> To: axis-user@ws.apache.org
>> Subject: Re: axis/tomcat restart problem
>> 
>> 
>> I'm sorry,I should have been more concise.I mean I have tested my service
>> on
>> the tomcat instance which is on my own computer and it works fine.when I
>> stop and then start the tomcat,my service's wsdl is still visible on the
>> http://localhost:8080/axis/servlet/AxisServlet url. This is not the case
>> with the tomcat which is located on the remote server machine which runs
>> on
>> linux gentoo. when i restart that tomcat,my own service is no longer
>> visible
>> on the ...8080/axis/servlet/AxisServlet url. and yes,this instance of
>> tomcat
>> is instaled using emerge command.
>> 
>>  
>> David Ojeda wrote:
>> > 
>> > Hello,
>> > 
>> > What do you mean by "every time tomcat is restarted" and "This doesnt
>> > happen 
>> > when i restart my local tomcat" ?
>> > I am guessing that "local tomcat" is a tomcat instance installed
>> manually
>> > in 
>> > your home and there is another instance installed by portage/emerge ?
>> > 
>> > On Friday 26 September 2008 07:27:55 srdjan wrote:
>> >> Yes,but axis is not standalone server,tomcat is,and it recognizes axis
>> as
>> >> some sort of servlet.
>> >> I am deploying my service on axis using wsdd.My service is simply a
>> java
>> >> class(+ a client for another service) ,not a servlet.I can deploy it
>> on
>> >> tomcat as war,but it wont work,because its not a servlet and it uses
>> >> axis.
>> >> Perhapse I am mistaken on this, if someone knows a way i can do this,
>> i
>> >> will gladly listen.
>> >> Again,my problem is not in deploying my service,my problem is that my
>> >> service disapears( its wsdl is not visible on
>> >> ..:8080/axis/servlet/AxisServlet) every time tomcat is restarted. This
>> >> doesnt happen when i restart my  local tomcat.
>> >> the worst thing is i can't seem to find a similar situation anywhere..
>> >>
>> >> thanks for your effort David
>> >>
>> >> David Ojeda wrote:
>> >> > Hello,
>> >> >
>> >> > I don't think that your problem is related to the way you installed
>> >> axis.
>> >> > I
>> >> > believe most people don't use that particular flavor of linux nor
>> >> install
>> >> > axis
>> >> > using emerge, rpm, apt-get, pacman, etc. IMO most people just deploy
>> >> the
>> >> > axis
>> >> > war in tomcat or deploy a customized war with the axis content.
>> >> >
>> >> > In my case, I create a war with the axis content, the webservices
>> >> > classes, resources, jars and aars, and the appropiate axis
>> >> configuration.
>> >> >
>> >> > Hope it helps.
>> >> >
>> >> > On Thursday 25 September 2008 12:06:34 srdjan wrote:
>> >> >> hi,
>> >> >> i have recently succesfully deployed my service on axis,however
>> when i
>> >> >> restart tomcat on the remote server my service is somehow lost- its
>> >> wsdl
>> >> >> is
>> >> >> no longer visible.all the class files of the service are in
>> place,and
>> >> >> everything is ok with service itself( i have tested it on my local
>> >> >> tomcat).
>> >> >> tomcat is on the remote server which runs on linux gentoo,and i
>> have
>> >> >> developed my service under windows,but i seriously doubt that the
>> >> >> problem lays there.
>> >> >> could the problem be in that i haven't actualy instaled axis(using
>> the
>> >> >> linux emerge command) but have just copied axis/webaps in
>> >> tomcat/webaps?
>> >> >> i
>> >> >> have lost entire blody day trying to figure this out.
> 
>> >> >> any sugestions will be greatly appreciated.
>> >> >>
>> >> >> thanks
>> >> >
>> >> > --
>> >> > Ing. David Ojeda
>> >> > Integra Consultores
>> >> > Caracas, Venezuela
>> >> >
>> >> >
>> -
>> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> > For additional commands, e-mail: [EMAIL PROTECTED]
>> > 
>> > -- 
>> > Ing. David Ojeda
>> > Integra Consultores
>> > Caracas, Venezuela
>> > 
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> > 
>> > 
>> > 
>> 
>> -- 
>> View this message in conte

Re: Service Archiver

[losintikfos]

problem solved! 
If you wondering what was the cause {it was unseal JAR}


=)


losintikfos wrote:
> 
> Hi Experts,
> 
> Need your urgent help! i am trying to archive a java class which has
> access reference to other java classes. Therefore i have pushed the
> reference classes into a JAR file and added to the archiver as liabrary.
> 
> My problem is! After deployment i get below error if i try to access the
> Service WSDL;
> 
> Error: org.apache.axis2.AxisFault: java.io.EOFException: Unexpected end of
> ZLIB input stream at
> org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:117)
> at
> org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:64)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
> at
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83)
> at java.util.TimerThread.mainLoop(Timer.java:512) at
> java.util.TimerThread.run(Timer.java:462) Caused by:
> java.lang.RuntimeException: java.io.EOFException: Unexpected end of ZLIB
> input stream at
> org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:869) at
> org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:945)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
> ... 12 more Caused by: java.io.EOFException: Unexpected end of ZLIB input
> stream at
> java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:223) at
> java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) at
> java.util.zip.ZipInputStream.read(ZipInputStream.java:146) at
> java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92) at
> java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70) at
> org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:854) ... 14
> more 
> 
> Do anyone know what i am doing wrong here! please help.
> 
> 
> B:jumping:
> 

-- 
View this message in context: 
http://www.nabble.com/Service-Archiver-tp19720816p19720932.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]

Service Archiver

[losintikfos]

Hi Experts,

Need your urgent help! i am trying to archive a java class with has access
reference to other java classes. Therefore i have pushed the reference
classes into a JAR file and added to the archiver as liabrary.

My problem is! After deployment i get below error if i try to access the
Service WSDL;

Error: org.apache.axis2.AxisFault: java.io.EOFException: Unexpected end of
ZLIB input stream at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:117)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:64)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
at
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83)
at java.util.TimerThread.mainLoop(Timer.java:512) at
java.util.TimerThread.run(Timer.java:462) Caused by:
java.lang.RuntimeException: java.io.EOFException: Unexpected end of ZLIB
input stream at
org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:869) at
org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:945) at
org.apache.axis2.deployment.repository.util.DeploymentFileData.setClassLoader(DeploymentFileData.java:115)
... 12 more Caused by: java.io.EOFException: Unexpected end of ZLIB input
stream at
java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:223) at
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) at
java.util.zip.ZipInputStream.read(ZipInputStream.java:146) at
java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92) at
java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70) at
org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:854) ... 14
more 

Do anyone know what i am doing wrong here! please help.


B:jumping:
-- 
View this message in context: 
http://www.nabble.com/Service-Archiver-tp19720816p19720816.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]

[ANN] Addressing 1.1 available at Maven Central Repository

[Rodrigo Ruiz]

We are glad to announce that Addressing 1.1 has been successfuly 
mirrored to the Maven2 Central Repository.


WS-Addressing implementation for Axis 1.4 aims to provide a common 
implementation for any open source project that rely on 
non-interoperable modifications of the original source code from the 
Apache WS-FX project.


Hope you enjoy it,
- The Addressing Team

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

Re: ArrayOf -problem

[Janne Rantala]

Hi Keith,

And thanks for your reply. It doesn't matter which type I use, both adb and
xmlbeans give me the same result. I'm sure there is a way to generate proper
classes with both of these types but just can't find it.

Regards,

Janne

2008/9/26 keith chapman <[EMAIL PROTECTED]>

> Hi Jaane,
>
> Is there any particular reason you tried to generate the code using
> xmlbeans? ADB which is the default databinding in Axis2 gives you much
> better performance than xmlbeans.
>
> Thanks,
> Keith.
>
>
> On Mon, Sep 22, 2008 at 1:16 PM, Janne Rantala <[EMAIL PROTECTED]>wrote:
>
>> Hi,
>>
>> I'm having trouble with ws-client which was originally created and used
>> with Axis1. Now I'm forced to upgrade to Axis2 but this has not gone as I
>> have hoped. I've tried creating stub classes with xmlbeans -option. One of
>> the methods is supposed to to transfer an array of Product-objects, but
>> xmlbeans option only creates object with name ArrayOfTns4Product classes.
>>
>> How am I able to generate classes the way they were created with Axis1?
>>
>> Best regards,
>>
>> Janne
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>