[Axis2][Post 1.0 SVN] New JMS implementation doesn't support username and password while creating connection

[Ali Sadik Kumlali]

Hi all,

I'm using SonicMQ and triying Axis2's current and the new JMS implementations 
over it.

When I enable the security of my broker, it requires username and password to 
be passed while creating a connection. The current JMS implementation supports 
this kind of connection. Is there any reason why we don't have this feature 
anymore?

It can easily be achived by replacing the line

  con = connectionFac.createConnection();
 
with following lines

  if (username != null && password != null) {
  con = connectionFac.createConnection(username, password);
  } else {
  con = connectionFac.createConnection();
  }
 
Here, username and password can be loaded from the configuration context as 
follows:

  AxisConfiguration axisConf = context.getAxisService().getAxisConfiguration(); 
   String username = (String) 
axisConf.getParameter(Constants.USER_NAME).getValue();
   String password = (String) 
axisConf.getParameter(Constants.PASSWORD).getValue();
 
Any comments?

Regards,

Ali Sadik Kumlali





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

Re: [axis2] code generated service :: Operation not found

[studium-sbr]

Sure, here it is.

Thanks for your time!!

Bille

> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 30.06.06 07:04:06
> An: axis-user@ws.apache.org
> Betreff: Re: [axis2] code generated service :: Operation not found


> Hi Studium;
> 
> Could you please post the wsdl as well.
> 
> [EMAIL PROTECTED] wrote:
> 
> >Thank you Deepal, but I think the action is set.
> >While debugging I can see that the options-Container of the 
> >messageContext-Object has an entry
> >action with the value 
> >'http://localhost:8080/axis2/services/MyService/myMethod'
> >which is the correct URL.
> >
> >Attached is the client (stubclass).
> >While stepping through the stubs myMethod the axisOperation within the 
> >messageContext seems to be correct. The field soapAction has the value 
> >urn:myMethod. 
> >Within the OutInAxisOperationClient::execute(), MC.getSoapAction() returns 
> >http://localhost:8080/axis2/services/MyService/myMethod
> >
> >
> >Is it possible that the cause of this error is the first element in the body 
> >which is called myMethodRequest
> >
> >--
> >The sent SOAP-Message I get from the MessageContext envelope-variable looks 
> >like this:
> >
> >
> >http://schemas.xmlsoap.org/soap/envelope/";>
> > 
> > 
> >  > xmlns="http://localhost:8080/axis2/services/MyService/xsd";>
> > 
> > hostname
> > 
> > 
> > 
> >
> >
> >Does anyone has further ideas ?
> >
> >Thanks so long
> >
> >Bille
> >  
> >
> >>-Ursprüngliche Nachricht-
> >>Von: axis-user@ws.apache.org
> >>Gesendet: 29.06.06 08:00:25
> >>An: axis-user@ws.apache.org
> >>Betreff: Re: [axis2] code generated service :: Operation not found
> >>
> >>
> >
> >
> >  
> >
> >>Hi Studium;
> >>As I understand , you are not sending SOAP action in the request.
> >>try
> >>option.setAction("myMethod"); , before calling the service.
> >>
> >>[EMAIL PROTECTED] wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>I have a code generated service deployed, let's call it 'MyService'. The 
> >>>axis service list says the service is fine and has a method 'myMethod'
> >>>When running the Client with a simple message I get an AxisFault saying:
> >>>
> >>>Operation Not found EPR is http://localhost:8080/axis2/services/MyService 
> >>>and WSA Action =  http://localhost:8080/axis2/services/MyService/myMethod
> >>>   at 
> >>> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
> >>>
> >>>While debugging I realized, that the instance variable axisOperation isn't 
> >>>set (DispatchPhase::checkPostCondition()).
> >>>The AxisEngine class doesn't seem to get the axisOperation set.
> >>>For code  generation I used the Eclipse PlugIn Version 1.2.0
> >>>
> >>>I'm using the nightly build of 07.06.2006.
> >>>
> >>>Could anybody give me a hint please of what I'm missing?
> >>>
> >>>TIA Bille
> >>>
> >>>
> >>>__
> >>>Verschicken Sie romantische, coole und witzige Bilder per SMS!
> >>>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
> >>>
> >>>
> >>>-
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>> 
> >>>
> >>>  
> >>>
> >>-- 
> >>Thanks,
> >>Deepal
> >>
> >>~Future is Open~ 
> >>
> >>
> >>
> >>-
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> >
> >__
> >Verschicken Sie romantische, coole und witzige Bilder per SMS!
> >Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
> >
> >  
> >
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~ 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Mit WEB.DE iNews werden Sie über die Ergebnisse der wichtigsten WM-Begegnungen
per SMS informiert: http://freemail.web.de/features/inews.htm/?mc=021202


http://localhost:8080/axis2/services/MyService/"; xmlns:tns="http://localhost:8080/axis2/services/MyService/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsd1="http://localhost:8080/axis2/services/MyService/xsd"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:soap="http://schemas

Re: [axis2 nightly build 22 Jun] more bug

[Wan Kaveevivitchai]

Dear dims,

 have you figure out, what should be the problem with the release? I 
have tested another issue related to the ws-security. I had downloaded the 
rampart module and then try to deploy it by add the module into axis2.xml 
and put .aar file into modules directory under web-inf in axis2 , when i 
started the server, the problem occur


it said that : Trying to engage a module which is not available

but i did test it with the other version release on Jun 4th, and everything 
work file for that version as well as the cache..but in Jun 4th version, it 
had the problem of broken pipe while sending large attachment.


is there any completed version out? or how shold / could fix these problem?

Best regards,

Sathita


From: "Wan Kaveevivitchai" <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: [EMAIL PROTECTED], axis-user@ws.apache.org
Subject: Re: [axis2 nightly build 22 Jun] file caching not working bug
Date: Wed, 28 Jun 2006 08:25:32 +


I was writing some email earlier about problem in sending large file ~ 10 
MB and got broken pipe exception. And there was the suggestion to use the 
new nightly release which is the 22 Jun 06 release and the broken pipe 
problem was solve.


So i moved on to test with 100 MB size attachment, and i got 
java.lang.OutOfMemory error, so i did some setting about cache on axis2.xml 
as following


   true
   locked="false">/users/alice3/home/

   4000

but it seems like it still cache into the memory, also when i check at the 
home directory, there is no cached file at all. So we tried extend the 
memory size and the attachment is received fine but it isn't the good way 
to do it, i supposed. So i think the problem is about cache is not working.


Please take a look,
 Sathita


From: "Davanum Srinivas" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: [axis2 nightly build 22 Jun] file caching not working bug
Date: Wed, 28 Jun 2006 04:13:03 -0400

Sathita,

We have no idea what this is about. Can you please explain a bit
further? which property did you set? expected behavior and stack
traces if any.

thanks,
dims

On 6/28/06, Wan Kaveevivitchai <[EMAIL PROTECTED]> wrote:

There is the problem of file caching, it doesn't working in nightly build
version released on June 22, 06. Eventhough, the cache properties in
axis2.xml already been set.

Is there any solution for this? Is it a bug?

Sathita



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





--
Davanum Srinivas : http://people.apache.org/~dims/

-
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: Content is not allowed in prolog

[Luanne Coutinho]

Hi,

 

Turns out that the endpoint supplied by our client was
wrong! I wonder why Axis kept throwing this particular error…

 

-Luanne

 

 

-Original Message-
From: Luanne Coutinho 
Sent: Friday,
 June 30, 2006 9:41 AM
To: Luanne
 Coutinho
Subject: 

 

Hello, I had this same error before.  Question though, what version of Axis are you using?  Also if you areusing any attachments in your program, you need to include the activation.jar. Tom  Luanne Coutinho wrote:>> Hi,>>  >> I used wsdl2Java to generate stubs so that I can access a web service > hosted elsewhere.>> I wrote a test program to invoke an operation, but I keep getting this > error:>>  >> AxisFault>>  faultCode: > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException>>  faultSubcode:>>  faultString: org.xml.sax.SAXParseException: Content is not allowed in > prolog.>>  faultActor:>>  faultNode:>>  faultDetail:>> > {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: > Content is not allowed in prolog.>> at > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown > Source)>> at > org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)>> at > org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)>> at > org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)>> at > org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)>> at > org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown > Source)>> at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source)>> at > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)>> at > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)>> at > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)>> at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)>> at > org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)>> at > org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)>> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)>> at > org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)>> at > org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)>> at org.apache.axis.client.Call.invoke(Call.java:2767)>> at org.apache.axis.client.Call.invoke(Call.java:2443)>> at org.apache.axis.client.Call.invoke(Call.java:2366)>> at org.apache.axis.client.Call.invoke(Call.java:1812)>>  >> Could someone please help? I have tried all sugestions from this > mailing list, but none have resolved the problem.>>  >> Thanks>> Luanne Misquitta>>  >  -  -To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

 

Re: [Axis v1.4] deploying with Basic Authentication turned on?

[Warren Crossing]

can you please explain why you want to use j2ee declarative security 
tomcat instead of webservices context security?


you must specify the http header authorization in the http-request?

otherwise add the handler to the wsdd

type="java:org.apache.axis.handlers.SimpleAuthenticationHandler" />


...

 
...

and set the usename and password properties in the client side SOAP call

I can't give any more informaiton because you haven't really described 
in any detail what you are doing, what you have done and what you expect 
to happen? Why do you expect it to return HTTP 200 OK?


Warren.

Artur Kraft wrote:

Is this a common issue or am I doing something basically wrong?
On the axis-user mailinglist (also checked axis-dev and tomcat-user) I 
found a few other posts with suggestions, but none really apply to me. 
Shouldn't this be fixed quite simple or do I have to code something to 
get it to work?


kind regards
Artur



Artur Kraft wrote:


Hello,

in Tomcat I turned on BASIC Authentication to protect the use of all 
axis services. Since then I always get a HTTP-Error 401/Unauthorized. 
How can I provide username and password to deploy again to axis?


I tried the -uUserName -wPassword parameters, but they seem to belong 
rather to the axis-file "user.lst" than providing the tomcat access 
user data.


Any suggestions?


My environment:
Axis v1.4
Tomcat v5.5.17
Java v1.5.0_06
WinXP


kind regards,
Artur

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




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




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

Re: [Axis2] WS soap action question

[Deepal Jayasinghe]

Michele Mazzucco wrote:

>Hi Eran,
>
>does AxisServlet run after the dispatchers? I need to get the soap
>action in a handler running before the dispatcher phase: is there any
>way to get it? If so, how can I accomplish my goal?
>  
>
AxisServlet run before the dispatchers , in fact AxisServelt is the one
how call AxisEngine.receive();
AxisServlet set the soapaction into message context , so at any point
you can get the soapaction , if that is there in HTTP headers

>Thanks,
>Michele
>
>Michele
>
>Eran Chinthaka wrote:
>  
>
>>Michele Mazzucco wrote:
>>
>>
>>>Hi all,
>>>
>>>how, 
>>>  
>>>
>>Read HTTP headers and SOAP Action header.
>>
>>
>>
>>>when 
>>>  
>>>
>>Whenever message comes to the engine.
>>
>>
>>
>>>(and where) 
>>>  
>>>
>>AxisServlet.
>>
>>-- Chinthaka
>>
>>
>>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: [axis2] code generated service :: Operation not found

[Deepal Jayasinghe]

Hi Studium;

Could you please post the wsdl as well.

[EMAIL PROTECTED] wrote:

>Thank you Deepal, but I think the action is set.
>While debugging I can see that the options-Container of the 
>messageContext-Object has an entry
>action with the value 'http://localhost:8080/axis2/services/MyService/myMethod'
>which is the correct URL.
>
>Attached is the client (stubclass).
>While stepping through the stubs myMethod the axisOperation within the 
>messageContext seems to be correct. The field soapAction has the value 
>urn:myMethod. 
>Within the OutInAxisOperationClient::execute(), MC.getSoapAction() returns 
>http://localhost:8080/axis2/services/MyService/myMethod
>
>
>Is it possible that the cause of this error is the first element in the body 
>which is called myMethodRequest
>
>--
>The sent SOAP-Message I get from the MessageContext envelope-variable looks 
>like this:
>
>
>http://schemas.xmlsoap.org/soap/envelope/";>
>   
>   
>xmlns="http://localhost:8080/axis2/services/MyService/xsd";>
>   
>   hostname
>   
>   
>   
>
>
>Does anyone has further ideas ?
>
>Thanks so long
>
>Bille
>  
>
>>-Ursprüngliche Nachricht-
>>Von: axis-user@ws.apache.org
>>Gesendet: 29.06.06 08:00:25
>>An: axis-user@ws.apache.org
>>Betreff: Re: [axis2] code generated service :: Operation not found
>>
>>
>
>
>  
>
>>Hi Studium;
>>As I understand , you are not sending SOAP action in the request.
>>try
>>option.setAction("myMethod"); , before calling the service.
>>
>>[EMAIL PROTECTED] wrote:
>>
>>
>>
>>>Hi,
>>>
>>>I have a code generated service deployed, let's call it 'MyService'. The 
>>>axis service list says the service is fine and has a method 'myMethod'
>>>When running the Client with a simple message I get an AxisFault saying:
>>>
>>>Operation Not found EPR is http://localhost:8080/axis2/services/MyService 
>>>and WSA Action =  http://localhost:8080/axis2/services/MyService/myMethod
>>> at 
>>> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
>>>
>>>While debugging I realized, that the instance variable axisOperation isn't 
>>>set (DispatchPhase::checkPostCondition()).
>>>The AxisEngine class doesn't seem to get the axisOperation set.
>>>For code  generation I used the Eclipse PlugIn Version 1.2.0
>>>
>>>I'm using the nightly build of 07.06.2006.
>>>
>>>Could anybody give me a hint please of what I'm missing?
>>>
>>>TIA Bille
>>>
>>>
>>>__
>>>Verschicken Sie romantische, coole und witzige Bilder per SMS!
>>>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>>>
>>>
>>>-
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>> 
>>>
>>>  
>>>
>>-- 
>>Thanks,
>>Deepal
>>
>>~Future is Open~ 
>>
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
>__
>Verschicken Sie romantische, coole und witzige Bilder per SMS!
>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>
>  
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

Axis 1.4 complex types missing namespace with bean serializer?

[Cmb List]

In Axis 1.4 I am having problems with complex types and the namespace not being set in the response message when I use my own bean class and the built in bean serializer in the type mapping.I have found that Axis clients work fine w/o the namespace but .NET clients ignore the response unless it has the namespace.  I must be doing something wrong because my understanding is that the namespacemust be on the response?Here are my dev steps:1) java2wsdl on a service facade to create the WSDL2) wsdl2java on the WSDL to get the deploy.wsdd contents3) edit wsdd so that my service facade is the classname4) edit wsdd so that the typemapping is my bean class returned on the facade5) I do not push any .java files from wsdl2java to my webappBelow is my tcpmon capture of the response showing the missing namespace, the wsdd and the wsdlWhen hosting a service, do you use the wsdl2java generated bean class on the server
 side?  Example 5 in the axis samples does not use the wsdl2java generated bean class so I do not either.             Super   1  
 Man   Has a new movie           James   2   Bond   Is 007   
        George   3   Bush   Is the Decider                                        xmlns:ns="http://value.abc.mysite.com"    qname="ns:UserVO"    type="java:com.mysite.abc.value.UserVO"    serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"    deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"   
 encodingStyle=""  />                                                                                                      
                        
		Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2�/min or less. __Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com 

RE: Content is not allowed in prolog

[Luanne Coutinho]

Hi Tom,

 

I’m using Axis 1.4, though I tried
with 1.3 as well.

Regarding attachments, I do not think I am
using any, though activation.jar and mail.jar are both present.

 

What else could be the problem?

 

Thanks,



Luanne
Misquitta



-Original Message-
From: Luanne
 Coutinho 
Sent: Friday, June 30, 2006 9:41
AM
To: Luanne
 Coutinho
Subject: 

 

Hello, I had this same error before.  Question though, what version of Axis are you using?  Also if you areusing any attachments in your program, you need to include the activation.jar. Tom  Luanne Coutinho wrote:>> Hi,>>  >> I used wsdl2Java to generate stubs so that I can access a web service > hosted elsewhere.>> I wrote a test program to invoke an operation, but I keep getting this > error:>>  >> AxisFault>>  faultCode: > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException>>  faultSubcode:>>  faultString: org.xml.sax.SAXParseException: Content is not allowed in > prolog.>>  faultActor:>>  faultNode:>>  faultDetail:>> > {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: > Content is not allowed in prolog.>> at > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown > Source)>> at > org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)>> at > org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)>> at > org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)>> at > org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)>> at > org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown > Source)>>     at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source)>> at > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)>> at > org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)>> at > org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)>> at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)>> at > org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)>> at > org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)>> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)>> at > org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)>>     at > org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)>> at org.apache.axis.client.Call.invoke(Call.java:2767)>> at org.apache.axis.client.Call.invoke(Call.java:2443)>> at org.apache.axis.client.Call.invoke(Call.java:2366)>> at org.apache.axis.client.Call.invoke(Call.java:1812)>>  >> Could someone please help? I have tried all sugestions from this > mailing list, but none have resolved the problem.>>  >> Thanks>> Luanne Misquitta>>  >  -  -To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

 

Re: Custom Serializer writeSchema() - adding xsd:import and wrapped arrays

[Ben Reif]

Sorry, in the email below I meant that I ran the java2wsdl utility.
On 6/29/06, Ben Reif <[EMAIL PROTECTED]> wrote:


Hey everyone,
 
I have two questions regarding generating schema with custom serializers. I'm using Axis 1.3 and I have some complex type objects that I want to expose in a Web Service. These objects aren't pure Java Beans so I had to write my own custom serializer and deserializer. These objects have getters and setters that deal with Lists of other complex type objects. In the writeSchema() method of my serializer I add an element to handle the getters/setters as arrays. When I run wsdl2java the schema in the WSDL comes out like this: 

 

http://my.class.package.name " xmlns="http://www.w3.org/2001/XMLSchema
">
        
     

    
    

 
I have tns2:ArrayOfMyClass2 defined farther down in the types section of the WSDL and it's in a different namespace then MyClass1. When I validate the WSDL it says that it's invalid because it's missing an http://my.class2.package.name/> from the above  definition. My question is how can I add this import from the writeSchema() method in my serializer? The 
org.apache.wsdl.fromJava.Types class doesn't give you access to the WSDL document as a whole, or even the current  element that's being written. Does anyone know of a way to do this?

 
 
My second question is that my service has methods that take in object arrays. So in my WSDD file I have  defined and the schema in my WSDL I have wrapped array types like this: 

 
          

 
The problem is that when I run wsdl2java the operation definitions in the default namespace  section of the  come out like: 

 
             

 
This is incorrect because the maxOccurs should be 1, not unbounded, since it's a wrapped array type. It doesn't seem like the org.apache.wsdl.fromJava.Types has any methods to write out a wrapped array definition and it doesn't give you access to change this. Does anyone know how this can be done?

 
If anyone knows how to accomplish either of these thanks in advance,

 
Ben

Re: How to publish WSDL for services of a ServiceGroup

[Deepal Jayasinghe]

Hi ;
Say your services.xml look like follows;



   
   


Then you can add two wsdl files into META-INF directory  , and service
name of the wsdl files should "abc" and "xyc" respectively.

[EMAIL PROTECTED] wrote:

>Hi,
>
>the problem I habe is as followes: Trying to publish a group of services using 
>the 'servicegroup'-Tag in services.xml descriptor I did not found any chance 
>to provide some wsdl files in the aar archive in that way, that every service 
>is able to provide a wsdl using his special file from META-INF directory. Are 
>there any consideration I've to watch for or is there a special tag in 
>servicedescription to let each service in a service group know his wsdl file?
>
>Mayby someone can help me with it,
>
>thanks a lot
>Ted
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 




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

Re: The duplicate type is happening here for the WSDL file

[Deepal Jayasinghe]

Hi John;
good to know that , I will resolve the JIRA issue

john andersen wrote:

> Hi Deepal,
>
> Good stuff!   I downloaded the June 27 snap and the duplicate element
> did not exist after running Java2WSDL.  I'll test further with a more
> robust implementation in the coming days.

Great !! , hope you wont find any more bugs :)

>
> Do you still need a jira issue?  I thought that Jim Bender already
> created jira-807 for this issue.
>
> Thanks,
>
> john andersen
>
>
>
> On 6/28/06, *Deepal Jayasinghe* <[EMAIL PROTECTED]
> > wrote:
>
>
>
> Xinjun Chen wrote:
>
> > Hi Deepal,
> >
> > I encountered the same problem as I posted in Joshua's thread on
> > operation inheritance. Could you also have a look at that thread?
> >
> > Could you tell me the minimal modules I need to rebuild? only
> codegen
> > and wsdl or all the rest?
>
> hmm , the best thing is get an update and rebuild the project .
>
> >
> >
> > Regards,
> > Xinjun
> >
> > On 6/28/06, Deepal Jayasinghe <[EMAIL PROTECTED]
> > wrote:
> >
> >> I have already fixed this , any possibility of testing with
> current SVN
> >> or nightly build.
> >>
> >> Davanum Srinivas wrote:
> >>
> >> > John,
> >> >
> >> > Could i pester you to please open up a JIRA issue?
> >> >
> >> > thanks,
> >> > dims
> >> >
> >> > On 6/27/06, [EMAIL PROTECTED]
>  <[EMAIL PROTECTED]
> > wrote:
> >> >
> >> >> Hi Deepal,
> >> >>
> >> >> I've butted my head against the same issue during the past
> few weeks
> >> >> (most
> >> >> recently with the June 19 Axis2 snap) and have had to resort to
> >> >> fixing the
> >> >> wsdl with a perl script.  Rather easy to reproduce with 2 source
> >> files:
> >> >>
> >> >> test.MyService.java
> >> >> 
> >> >> package test;
> >> >> import test.MyData;
> >> >> public class MyService
> >> >> {
> >> >> private MyData myData = new MyData();
> >> >>
> >> >> public MyData retrieveMyData()
> >> >> {
> >> >> return myData;
> >> >> }
> >> >> }
> >> >>
> >> >> Test.MyData.java
> >> >> ###
> >> >> package test;
> >> >> public class MyData
> >> >> {
> >> >> private String myString = null;
> >> >> public String getMyString() { return
> this.myString; }
> >> >> public void setMyString(String arg) {
> this.myString =
> >> >> arg; }
> >> >> }
> >> >>
> >> >>
> >> >> I ran:
> >> >> ..\bin\java2wsdl.bat -cp . -sn TEST -l
> >> >> http://localhost:8080/axis2/services/Logger -st wrapped -cn
> >> >> test.MyService
> >> >> (and I did try different styles - same result)
> >> >>
> >> >> Which resulted in the following wsdl with the element "MyData"
> >> defined
> >> >> twice:
> >> >> ###
> >> >> wsdl:definitions xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/";
> >> >> xmlns:axis2="http://test";
> >> >> xmlns:soap12=" http://schemas.xmlsoap.org/wsdl/soap12/";
> >> >> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
> >> >> xmlns:mime=" http://schemas.xmlsoap.org/wsdl/mime/";
> >> >> xmlns:ns1="http://test/xsd";
> >> >> xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/";
> >> >> targetNamespace="http://test";>
> >> >>   
> >> >> http://www.w3.org/2001/XMLSchema";
> >> >> xmlns:ns="http://test/xsd " targetNamespace="http://test/xsd";
> >> >> elementFormDefault="unqualified"
> attributeFormDefault="unqualified">
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >> 
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >> 
> >> >>   
> >> >> 
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >> 
> >> >>   
> >> >> 
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >>   
> >> >>  name="part1" />
> >> >>   
> >> >>   
> >> >> 
> >> >>   
> >> >>message="axis2:retrieveMyDataResponseMessage" />
> >> >> 
> >> >>   
> >> >>name="TESTSOAP11Binding">
> >> >>  >> >> transport="http://schemas.xmlsoap.org/soap/http"; />
> >> >> 
> >> >>>> soapAction="urn:retrieveMyData" />
> >> >>   
> >> >> http://test"; use="literal" />
> >> >>   
> >>

Re: sending soap messages asynchronously

[Deepal Jayasinghe]

Yes  , you can do it with Axis2   :)

Phani Sekhar wrote:

>Thank you very much for ur response ...
>We want the Axis server to first initiate and send one-way messages to the
>Axis client.
>Can we configure the Axis2 server in such a way ???
>
>~ Phani Sekhar
>
>
>
>-Original Message-
>From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
>Sent: Thursday, June 29, 2006 1:01 PM
>To: axis-user@ws.apache.org
>Subject: Re: Re : sending soap messages asynchronously
>
>Axis2 support asynchronous invocation
>
>Phani Sekhar wrote:
>
>  
>
>>Hi all,
>>
>>We are implementing NETCONF on SOAP over HTTP. We are using Axis.
>>
>>We require the Axis web service to send some soap messages
>>asynchronously to the Axis client without any initiation.
>>
>>Ofcourse for the first time, we can register the client at the server.
>>We are trying to implement something similar to the snmp
>>traps/notifications.
>>
>>Is is possible to do this using Axis Does Axis support
>>asynchronous messaging???
>>
>>
>>
>>Please help me.
>>
>>
>>
>>Thanks in advance
>>
>>Phani Sekhar
>>
>>
>>
>>-Original Message-
>>*From:* Phani Sekhar [mailto:[EMAIL PROTECTED]
>>*Sent:* Wednesday, June 21, 2006 12:47 PM
>>*To:* axis-user@ws.apache.org
>>*Subject:* sending asynchronous soap messages
>>
>>
>>
>>Hi,
>>
>>Is there any way to send asynchronous soap messages from a webservice
>>in Axis, something similar to snmp notifications ???
>>
>>
>>
>>Thanks in Advance
>>
>>Phani Sekhar
>>
>>
>>
>
>--
>Thanks,
>Deepal
>
>~Future is Open~
>
>
>
>-
>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]
>
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 




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

Custom Serializer writeSchema() - adding xsd:import and wrapped arrays

[Ben Reif]

Hey everyone,
 
I have two questions regarding generating schema with custom serializers. I'm using Axis 1.3 and I have some complex type objects that I want to expose in a Web Service. These objects aren't pure Java Beans so I had to write my own custom serializer and deserializer. These objects have getters and setters that deal with Lists of other complex type objects. In the writeSchema() method of my serializer I add an element to handle the getters/setters as arrays. When I run wsdl2java the schema in the WSDL comes out like this:

 
http://my.class.package.name
" xmlns="http://www.w3.org/2001/XMLSchema">
        
    

    
    

 
I have tns2:ArrayOfMyClass2 defined farther down in the types section of the WSDL and it's in a different namespace then MyClass1. When I validate the WSDL it says that it's invalid because it's missing an http://my.class2.package.name/> from the above  definition. My question is how can I add this import from the writeSchema() method in my serializer? The 
org.apache.wsdl.fromJava.Types class doesn't give you access to the WSDL document as a whole, or even the current  element that's being written. Does anyone know of a way to do this?

 
 
My second question is that my service has methods that take in object arrays. So in my WSDD file I have  defined and the schema in my WSDL I have wrapped array types like this:

 
         

 
The problem is that when I run wsdl2java the operation definitions in the default namespace  section of the  come out like:

 
            

 
This is incorrect because the maxOccurs should be 1, not unbounded, since it's a wrapped array type. It doesn't seem like the 
org.apache.wsdl.fromJava.Types has any methods to write out a wrapped array definition and it doesn't give you access to change this. Does anyone know how this can be done?
 
If anyone knows how to accomplish either of these thanks in advance,
 
Ben

axis-user@ws.apache.org

[Ralph O. Delfs]

Hello,
i am running axis2 1.0 on tomcat 5.0 and try to get a simple service using 
xmlbeans data binding to work. i use WSDL2JAVA to generate client and 
server-side code. the service deploys without problems, but on testing there 
seems to be a problem during deserialization of the xmlbean on the server side, 
but i am not able to find out what is going wrong. i rechecked xbeans.jar, but 
there is only the one that comes with the standart distribution, which also 
contains the XBeanDebug class, which cannot be found. any help in further 
debugging apprechiated!
Cheers,
Ralph

2006-06-30 03:35:51 StandardWrapperValve[AxisServlet]: Servlet.service() for 
servlet AxisServlet threw exception
java.lang.ExceptionInInitializerError
   at sun.misc.Unsafe.ensureClassInitialized(Native Method)
   at 
sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
   at 
sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
   at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
   at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
   at java.lang.reflect.Field.get(Field.java:357)
   at 
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:768)
   at pong.PongDocument.(PongDocument.java:19)
   at pong.PongDocument$Factory.parse(PongDocument.java:133)
   at 
pong.PongAMessageReceiverInOut.fromOM(PongAMessageReceiverInOut.java:148)
   at 
pong.PongAMessageReceiverInOut.invokeBusinessLogic(PongAMessageReceiverInOut.java:50)
   at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
   at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
   at java.security.AccessController.doPrivileged(Native Method)
   at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
   at 
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
   at 
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
   at 
org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:50)
   at 
org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
   at java.security.AccessController.doPrivileged(Native Method)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
   at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
   at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
   at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
   at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
   at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
   at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
   at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
   at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
   at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
   at 
org.apache.coyote.http11.Http11Protocol$Http11

Re: Two simple questions...

[Anne Thomas Manes]

Axis2 supports SOAP 1.2.An effort is underway to support annotations in Axis2.AnneOn 6/29/06, Marco Tedone <
[EMAIL PROTECTED]> wrote:Hi, I've got  a couple of questions, being new to this mailing list and to
Axis in general.1) Does Axis use (or intend to use) annotations to make developers' lifeeasier (i.e. by flagging a class with annotations rather then writing thetedious deployment descriptors)?
2) How do I use SOAP 1.2 with Axis? Is it enough to change the envelopenamespace to be http://www.w3c.org/2005/05/soap-enveloper? And does Axissupport all of the SOAP 
1.2 features?Thanks for any time you will find to answer to my questions.Marco-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Two simple questions...

[Marco Tedone]

Hi, I've got  a couple of questions, being new to this mailing list and to 
Axis in general.


1) Does Axis use (or intend to use) annotations to make developers' life 
easier (i.e. by flagging a class with annotations rather then writing the 
tedious deployment descriptors)?


2) How do I use SOAP 1.2 with Axis? Is it enough to change the envelope 
namespace to be http://www.w3c.org/2005/05/soap-enveloper? And does Axis 
support all of the SOAP 1.2 features?


Thanks for any time you will find to answer to my questions.

Marco 




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

[Axis2]client ignoring timeout settings

[Andrew B]

Hi,I have an Axis2 client, calling an Axis2 service. The call times out after maybe 10 seconds, when the service typically needs at least a minute to complete its processing. I have tried setting both the connection and socket timeouts to half an hour:            options.setProperty(HTTPConstants.SO_TIMEOUT,  new Integer(180));            options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,  new Integer(180));but this has had no effect at all. Any ideas, anyone?Thanks,Andrew __Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com 

Axis 2 - Can it Support JAX-WS Style Versioning - Ignoring Invalid Content

[Hathaway, Robert]

I'm working on SOA service versioning standards on
backwards/forwards interface compatibility and trying to avoid the nested
wrapped any/anyAttribute solution.

 

JAX-WS seems to specify WSDL/Schema evolution support thru JAXB
2.0.

 

Does Axis 2 provide any support for WSDL/XSD schema evolution/versioning
- such as ignoring extra XML Schema fields?

 

Thanks in advance for any heads up, versioning is now a critical
issue for the large project I work on and is an overall area that needs
support, given the issues created by strict or inflexible XML schema and/or
endpoints.

 

Bob Hathaway

Senior SOA Architect

 




This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.

Re: [Axis2]setting username and password

[Andrew B]

Actually I just found it - it's called _getServiceClient. Any reason for the underscore?robert lazarski <[EMAIL PROTECTED]> wrote: Forgot to mention - stub has a getServiceClient method.Roberthttp://www.braziloutsource.com/On 6/29/06, robert lazarski <[EMAIL PROTECTED]> wrote:> Seems to be a new class - I recommend updating anyways as there has> been a lot of bug fixes since 1.0 :>> http://people.apache.org/dist/axis2/nightly/>> Set your client options like ...>> ServiceClient serviceClient = new ServiceClient();>> Options options = new Options();> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,>basicAuthentication);>
 serviceClient.setOptions(options);>> HTH,> Robert> http://www.braziloutsource.com/>> On 6/29/06, Andrew B <[EMAIL PROTECTED]> wrote:> > I don't seem to have the class> > HttpTransportProperties.BasicAuthentication in Axis2 1.0.> > Is it in a later build? Same is true for> > HTTPConstants.BASIC_AUTHENTICATION.> >> > Also, once these problems are ironed out, how do I set the options object on> > the client stub?> >> > robert lazarski <[EMAIL PROTECTED]> wrote:> >  If your talking about the way call.setPassword etc worked in axis 1.x,> > in axis2 it is:> >> > HttpTransportProperties.BasicAuthentication> >  basicAuthentication = new HttpTransportProperties().> >  new BasicAuthentication();> >  basicAuthentication.setUsername(userName);> > 
 basicAuthentication.setPassword(password);> >> >  options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,> >  basicAuthentication);> >> > HTH,> > Robert> > http://www.braziloutsource.com/> >> > On 6/20/06, Andrew B wrote:> > > Hi,> > >> > > My Axis1 -> Axis2 migration continues. The issue I have now is with> > getting> > > the username and password within the Axis2 service. Are they now> > accessible> > > via MessageContext.getProperty instead of getUsername() and getPassword()?> > > If so, what are the names of the properties?> > >> > > Thanks> > >> > >> > > > > > Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.> > >> >
 >> >> > -> > To unsubscribe, e-mail: [EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED]> >> >> >> >> >> >  > > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates> > starting at 1�/min.> >> >>-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] 
		Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1¢/min.

Re: [Axis2]setting username and password

[Andrew B]

Got the latest nightly build. Everything now compiles, but stub has neither a getServiceClient nor setServiceClient method Thanksrobert lazarski <[EMAIL PROTECTED]> wrote: Forgot to mention - stub has a getServiceClient method.Roberthttp://www.braziloutsource.com/On 6/29/06, robert lazarski <[EMAIL PROTECTED]> wrote:> Seems to be a new class - I recommend updating anyways as there has> been a lot of bug fixes since 1.0 :>> http://people.apache.org/dist/axis2/nightly/>> Set your client options like ...>> ServiceClient serviceClient = new ServiceClient();>> Options options = new Options();> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,>basicAuthentication);>
 serviceClient.setOptions(options);>> HTH,> Robert> http://www.braziloutsource.com/>> On 6/29/06, Andrew B <[EMAIL PROTECTED]> wrote:> > I don't seem to have the class> > HttpTransportProperties.BasicAuthentication in Axis2 1.0.> > Is it in a later build? Same is true for> > HTTPConstants.BASIC_AUTHENTICATION.> >> > Also, once these problems are ironed out, how do I set the options object on> > the client stub?> >> > robert lazarski <[EMAIL PROTECTED]> wrote:> >  If your talking about the way call.setPassword etc worked in axis 1.x,> > in axis2 it is:> >> > HttpTransportProperties.BasicAuthentication> >  basicAuthentication = new HttpTransportProperties().> >  new BasicAuthentication();> >  basicAuthentication.setUsername(userName);> > 
 basicAuthentication.setPassword(password);> >> >  options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,> >  basicAuthentication);> >> > HTH,> > Robert> > http://www.braziloutsource.com/> >> > On 6/20/06, Andrew B wrote:> > > Hi,> > >> > > My Axis1 -> Axis2 migration continues. The issue I have now is with> > getting> > > the username and password within the Axis2 service. Are they now> > accessible> > > via MessageContext.getProperty instead of getUsername() and getPassword()?> > > If so, what are the names of the properties?> > >> > > Thanks> > >> > >> > > > > > Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.> > >> >
 >> >> > -> > To unsubscribe, e-mail: [EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED]> >> >> >> >> >> >  > > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates> > starting at 1�/min.> >> >>-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] 
		Do you Yahoo!? Next-gen email? Have it all with the  all-new Yahoo! Mail Beta.

Strange format of SOAP Response causing errors

[Matthew Brown]

We are using stub 
classes created from WSDL2Java to communicate with a customer's web service. 
Axis (1.3 and 1.4) seems unable to parse the response of the SOAP message, and 
eyeballing the response in a tool like tcpmon one can see junk characters 
inserted between every valid XML character (the typical ASCII square), and two 
before the opening xml bracket.
 
Using the default 
Http sender, Axis reports an IO exception with a message like "Invalid byte 
1 of 1 byte UTF-8 sequence". Using the commons-http-client, this becomes a 
SAXParseException of "Content is not allowed in prolog". The SOAP response's 
header claims a content type of UTF-8, although it does not appear to be 
so.
 
I've been able to 
test out communications with the same web services using a .NET generated proxy. 
Watching the traffic in tcpmon, the response looks the same, but is understood 
by the client.
 
Should we be setting 
the character set / encoding expected in the response stream manually 
somewhere?
 
 
Thanks
Matthew 
Brown

Re: [Axis2]setting username and password

[robert lazarski]

Forgot to mention - stub has a getServiceClient method.

Robert
http://www.braziloutsource.com/

On 6/29/06, robert lazarski <[EMAIL PROTECTED]> wrote:

Seems to be a new class - I recommend updating anyways as there has
been a lot of bug fixes since 1.0 :

http://people.apache.org/dist/axis2/nightly/

Set your client options like ...

ServiceClient serviceClient = new ServiceClient();

Options options = new Options();
options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
   basicAuthentication);
serviceClient.setOptions(options);

HTH,
Robert
http://www.braziloutsource.com/

On 6/29/06, Andrew B <[EMAIL PROTECTED]> wrote:
> I don't seem to have the class
> HttpTransportProperties.BasicAuthentication in Axis2 1.0.
> Is it in a later build? Same is true for
> HTTPConstants.BASIC_AUTHENTICATION.
>
> Also, once these problems are ironed out, how do I set the options object on
> the client stub?
>
> robert lazarski <[EMAIL PROTECTED]> wrote:
>  If your talking about the way call.setPassword etc worked in axis 1.x,
> in axis2 it is:
>
> HttpTransportProperties.BasicAuthentication
>  basicAuthentication = new HttpTransportProperties().
>  new BasicAuthentication();
>  basicAuthentication.setUsername(userName);
>  basicAuthentication.setPassword(password);
>
>  options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
>  basicAuthentication);
>
> HTH,
> Robert
> http://www.braziloutsource.com/
>
> On 6/20/06, Andrew B wrote:
> > Hi,
> >
> > My Axis1 -> Axis2 migration continues. The issue I have now is with
> getting
> > the username and password within the Axis2 service. Are they now
> accessible
> > via MessageContext.getProperty instead of getUsername() and getPassword()?
> > If so, what are the names of the properties?
> >
> > Thanks
> >
> >
> > 
> > Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>  
> Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
> starting at 1¢/min.
>
>



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

Re: [Axis2]setting username and password

[robert lazarski]

Seems to be a new class - I recommend updating anyways as there has
been a lot of bug fixes since 1.0 :

http://people.apache.org/dist/axis2/nightly/

Set your client options like ...

   ServiceClient serviceClient = new ServiceClient();

   Options options = new Options();
options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
  basicAuthentication);
   serviceClient.setOptions(options);

HTH,
Robert
http://www.braziloutsource.com/

On 6/29/06, Andrew B <[EMAIL PROTECTED]> wrote:

I don't seem to have the class
HttpTransportProperties.BasicAuthentication in Axis2 1.0.
Is it in a later build? Same is true for
HTTPConstants.BASIC_AUTHENTICATION.

Also, once these problems are ironed out, how do I set the options object on
the client stub?

robert lazarski <[EMAIL PROTECTED]> wrote:
 If your talking about the way call.setPassword etc worked in axis 1.x,
in axis2 it is:

HttpTransportProperties.BasicAuthentication
 basicAuthentication = new HttpTransportProperties().
 new BasicAuthentication();
 basicAuthentication.setUsername(userName);
 basicAuthentication.setPassword(password);

 options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
 basicAuthentication);

HTH,
Robert
http://www.braziloutsource.com/

On 6/20/06, Andrew B wrote:
> Hi,
>
> My Axis1 -> Axis2 migration continues. The issue I have now is with
getting
> the username and password within the Axis2 service. Are they now
accessible
> via MessageContext.getProperty instead of getUsername() and getPassword()?
> If so, what are the names of the properties?
>
> Thanks
>
>
> 
> Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
>
>

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





 
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
starting at 1¢/min.




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

Re: [Axis2]setting username and password

[Andrew B]

I don't seem to have the class HttpTransportProperties.BasicAuthentication in Axis2 1.0. Is it in a later build? Same is true for HTTPConstants.BASIC_AUTHENTICATION.Also, once these problems are ironed out, how do I set the options object on the client stub?robert lazarski <[EMAIL PROTECTED]> wrote: If your talking about the way call.setPassword etc worked in axis 1.x,in axis2 it is:HttpTransportProperties.BasicAuthentication   basicAuthentication = new HttpTransportProperties().   new BasicAuthentication();   basicAuthentication.setUsername(userName);   basicAuthentication.setPassword(password);   options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,  
 basicAuthentication);HTH,Roberthttp://www.braziloutsource.com/On 6/20/06, Andrew B <[EMAIL PROTECTED]> wrote:> Hi,>> My Axis1 -> Axis2 migration continues. The issue I have now is with getting> the username and password within the Axis2 service. Are they now accessible> via MessageContext.getProperty instead of getUsername() and getPassword()?> If so, what are the names of the properties?>> Thanks>>>  > Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.>>-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] 
		Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1¢/min.

[Axis2] I tried the latest daily build for today (29 June) and still had the IllegalStateException

[Jim Bender]

My current test for Axis2-Std-1.0 is to run my end-to-end web service
generation, which builds the service archive and  jar, deploys them to
a directory for Embedded Tomcat, runs Tomcat, hits it from the test
client within the TestNG test. I still am seeing the same error with
the daily build for 29 June 2006:

Points Calculation, firing...
Caught Throwable exception in runPointsCalculator:
org.apache.axiom.om.OMException: java.lang.IllegalStateException
org.apache.axiom.om.OMException: java.lang.IllegalStateException
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
at 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322)
at 
testexamples.types.PointsCalculatorStub.toOM(PointsCalculatorStub.java:213)
at 
testexamples.types.PointsCalculatorStub.toEnvelope(PointsCalculatorStub.java:230)
at 
testexamples.types.PointsCalculatorStub.calculatePoints(PointsCalculatorStub.java:105)
at 
com.recursionsw.ve.tools.webservices.TestWebServicesCompleteGenEndToEndTestNG.runPointsCalculato
r(TestWebServicesCompleteGenEndToEndTestNG.java:164)

For whatever reason, there is some parsing using a state machine
happening, and that fails with an Illegal State. This is the problem
documented in my second JIRA issue.

Regards,
--
Jim

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

Re: More Axis & wrapped (Was: Re: No such operation)

[Doug B]

Thanks, Anne.  That's how I "guessed" the ant task's syntax, but there
were a few possible ways it could have been implemented, or even not
at all, so I was glad to find it.

But I think that approach is what we're going to try to do, but at
this point my customer is still trying to use JBuilder's Axis-hiding
tools, and he hasn't found out how to do -noWrapped from them.  He's
willing to revert to command-line if necessary, but is leaving that as
a last resort.

Doug

On 6/29/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

Doug,

The WSDL2Java Reference Guide documents the -W --nowrapped option. See
http://ws.apache.org/axis/java/reference.html#WSDL2JavaReference

My recommendation is to define your WSDLs following the wrapped convention,
but to turn it off in your service implementation (using -W). That gives
your client developers to use the wrapped option if they like.

Anne


On 6/28/06, Doug B <[EMAIL PROTECTED]> wrote:
>
 Sigh.  I changed our WSDL & Schema to use a naming convention that I
thought would work with Axis' current default behaviour on the server
side, and it caused its own issues.  Namely, apparently 4 of my 5
operation signatures now meet all Axis' criteria for "wrapped" style,
but one does not.  So Axis generated 1 interface method the way I
wanted, with request and response complexType beans, and 4 "wrapped"
style methods (which would have confused the heck out of me if we
 hadn't had this whole discussion).

Eventually I got the ant  task to not use "wrapped"
(seemingly undocumented syntax*), so things look like they might be
ok.  My test-generated server deploy.wsdd at least looks like the
qnames will match now.

I'm not sure if using a "wrapped-compatible" WSDL is better or worse
if you're not planning on actually using wrapped mappings.  It looks
 like, at least with Axis, either way you have to customize the
generated artifacts, so you have to know about "wrapped" even if you
don't want to use it.

BTW, wrapped looks much harder to use portably than non-wrapped, from
a business code point-of-view.  The wrapped method signatures have
dependencies on axis packages, where the non-wrapped ones only have
dependencies on my Schema beans, which ideally, one day, will be
totally POJO allowing me to switch out engines easily.  But that's a
different subject.

* http://ws.apache.org/axis/java/ant/axis-wsdl2java.html
doesn't
document any attribute to disable wrapped, but setting the attribute
noWrapped="true" in the main element of the task worked.

Doug

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

Newbie problem with addressing

[Layne Shepherd]

I have several clients who connect to my axis webservice from .NET clients.
In their soap headers, they are adding addressing headers to the envelope.
How can I get axis to ignore the addressing headers?

I am actually processing the security headers, and that works fine until I
get a soap request that contains the wsa headers, then I get the
"WSDoAllReceiver: security processing failed (actions mismatch)" error.

Following is my wsdd file and a sample soap message from a .net client:

Wsdd for the axis engine:


http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
  








  

  
  


  

  
  
  
  
  



http://xml.apache.org/axis/wsdd/
  
  


  
  

  
  


  

http://www.docusign.net/API/2.2"; />

http://www.docusign.net/API/2.2"; />







http://www.docusign.net/API/2.2";
qname="ns:>CreateAndSendEnvelope"
type="java:net.docusign.www.API._2_2.CreateAndSendEnvelope"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:Document"
type="java:net.docusign.www.API._2_2.Document"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:RecipientSignatureInfo"
type="java:net.docusign.www.API._2_2.RecipientSignatureInfo"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:ArrayOfTab"
type="java:net.docusign.www.API._2_2.Tab[]"
innerType="cmp-ns:Tab"
xmlns:cmp-ns="http://www.docusign.net/API/2.2";
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:TabTypeCode"
type="java:net.docusign.www.API._2_2.TabTypeCode"
serializer="org.apache.axis.encoding.ser.EnumSerializerFactory"
deserializer="org.apache.axis.encoding.ser.EnumDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:CustomField"
type="java:net.docusign.www.API._2_2.CustomField"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:>CreateEnvelope"
type="java:net.docusign.www.API._2_2.CreateEnvelope"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:Envelope"
type="java:net.docusign.www.API._2_2.Envelope"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:ArrayOfDocument"
type="java:net.docusign.www.API._2_2.Document[]"
innerType="cmp-ns:Document"
xmlns:cmp-ns="http://www.docusign.net/API/2.2";
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:EnvelopeStatus"
type="java:net.docusign.www.API._2_2.EnvelopeStatus"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:Recipient"
type="java:net.docusign.www.API._2_2.Recipient"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:RecipientStatus"
type="java:net.docusign.www.API._2_2.RecipientStatus"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
qname="ns:EnvelopeStatusCode"
type="java:net.docusign.www.API._2_2.EnvelopeStatusCode"
serializer="org.apache.axis.encoding.ser.EnumSerializerFactory"
deserializer="org.apache.axis.encoding.ser.EnumDeserializerFactory"
encodingStyle=""
/>
http://www.docusign.net/API/2.2";
  

IBMFakeTrustSocketFactory

[Justin Miller]

I'm trying to use a self-signed certificate to connect to an endpoint via SSL.  However, when I set the axis.socketSecureFactory property to org.apache.axis.components.net.IBMFakeTrustSocketFactory, I get a javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found.
 
This same code works with the SunFakeTrustSocketFactory and the Sun JDK 1.4.  I've cracked open the source for both FakeTrustSocketFactory classes and they are very similar.  The problem seems to be coming from the org.apache.axis.components.net.SocketFactoryFactory.getFactory method.  It always returns the JSSESocketFactory even if I specify the IBMFakeTrustSocketFactory.  
 

Environment:
 
IBM JDK 1.4
Axis 1.3
 
Has anyone experienced this same issue?  Any suggestions?
 
Thanks in advance
Justin Miller

Re: [Axis2] Flash Not Compatible with Axis2

[Luke DeWitt]

Hi again,

I guess should also post what I get when trying to connect with the Tungsten 
servers.


Top Window:

GET /axis2/services/version?wsdl HTTP/1.1
Referer: http://localhost:9100/axis2/services/version?wsdl
x-flash-version: 8,0,22,0
User-Agent: Shockwave Flash
Host: localhost:9100
Cache-Control: no-cache
Cookie: JSESSIONID=D60FB81F45CE803F0C9A238B4B108982


Bottom Window:
HTTP/1.1 500 Internal Server Error
Date: Thu, 29 Jun 2006 17:22:37 GMT
Server: Jetty/5.1.10 (Linux/2.6.8-11-em64t-p4-smp i386 java/1.4.2-03
Content-Type: text/html
Content-Length: 1259
Connection: close



Error 500 Internal Server Error


HTTP ERROR: 500Internal Server Error
RequestURI=/axis2/services/version
http://jetty.mortbay.org";>Powered by 
Jetty://

























Thanks again,

--LD


- Original Message - 
From: "Luke DeWitt" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, June 29, 2006 12:45 PM
Subject: Re: [Axis2] Flash Not Compatible with Axis2



Sorry for the late reply.

Using TCPmon I attempted to use my webservice on my localhost, port 80.

This is what came up in TCPmon. In the higher of the two windows I got.

GET /axis2/services/version?wsdl HTTP/1.1
Referer: http://localhost:9000/axis2/services/version?wsdl
x-flash-version: 8,0,22,0
User-Agent: Shockwave Flash
Host: localhost:9000
Cache-Control: no-cache
Cookie: JSESSIONID=871705657F39D028CFCA7DC17836C6A5

POST /axis2/services/version HTTP/1.1
Referer: http://localhost:9000/axis2/services/version
x-flash-version: 8,0,22,0
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:getVersion"
Content-Length: 281
User-Agent: Shockwave Flash
Host: localhost:9000
Cache-Control: no-cache
Cookie: JSESSIONID=871705657F39D028CFCA7DC17836C6A5


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


and in the Lower of the two, I got:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml
Transfer-Encoding: chunked
Date: Thu, 29 Jun 2006 15:43:07 GMT

c39
http://schemas.xmlsoap.org/wsdl/"; 
xmlns:axis2="http://ws.apache.org/axis2"; 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
xmlns:ns0="http://axisversion.sample/xsd"; 
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; 
xmlns:ns1="http://org.apache.axis2/xsd"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
targetNamespace="http://ws.apache.org/axis2";>xmlns:ns="http://axisversion.sample/xsd"; 
targetNamespace="http://axisversion.sample/xsd"; 
elementFormDefault="unqualified" attributeFormDefault="unqualified">











element="ns0:getVersion" name="part1" />name="getVersionResponse">name="part1" />name="versionPortType">message="axis2:getVersionMessage" />message="axis2:getVersionResponse" 
/>type="axis2:versionPortType" name="versionSOAP11Binding">style="document" transport="http://schemas.xmlsoap.org/soap/http"; 
/>soapAction="urn:getVersion" />namespace="http://ws.apache.org/axis2"; use="literal" 
/>namespace="http://ws.apache.org/axis2"; use="literal" 
/>type="axis2:versionPortType" name="versionSOAP12Binding">style="document" transport="http://schemas.xmlsoap.org/soap/http"; 
/>soapAction="urn:getVersion" />namespace="http://ws.apache.org/axis2"; use="literal" 
/>namespace="http://ws.apache.org/axis2"; use="literal" 
/>type="axis2:versionPortType" name="versionHttpBinding">verb="POST" />location="getVersion" />/>/>name="version">name="versionSOAP11port0">location="http://localhost:9000/axis2/services/version"; 
/>name="versionSOAP12port0">location="http://localhost:9000/axis2/services/version"; 
/>name="versionHttpport0">location="http://localhost:9000/axis2/rest/version"; 
/>

0

HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Thu, 29 Jun 2006 15:43:07 GMT
Connection: close

c6
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>soapenv:Client

56
null; nested exception is:
java.lang.NullPointerException
8f2
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.Applicat

How to order the elements in soap message?

[akkachotu]

I am having a web service provider on AXIS1.3 and when am sending
below response to the consumer:


a1






c

d1



But instead of above soap message I want to send below and want to
order the elements.


c

a1







d1



Is there any tweaking reqired in the generated AXIS server-config.wsdd
file. Please suggest.

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

Re: sending soap messages asynchronously

[Eran Chinthaka]

Anne Thomas Manes wrote:
> Keep in mind that in order for your Axis "client" to receive unsolicited
> messages, it must be a "server".

One more addition to Anne's comment. Here what you are trying to send is
a request. We always think of endpoints and they become a server or a
client depending on the message interaction.
So your "server" can use the service client api to send a request to
another endpoint.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] How to access the soapAction from Handlers

[Eran Chinthaka]

David Illsley wrote:
> As far as I know you'll have to parse the document.
> The wsa:Action element will be found in the SOAP Header so I'd expect that 
> due to the wonders of AXIOM the whole document won't be parsed, just the 
> first few elements.

Yep, you are correct.

> I'm not an expert on AXIOM/parsing though..

This is a hint of how you can get the Action header from the envelope
from your handler.

msgContext.getEnvelope().getHeader().getFirstChildWithName(new
QName("Action"))

Thanks,
Eran Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

Thanks,

Michele

David Illsley wrote:
> As far as I know you'll have to parse the document.
> The wsa:Action element will be found in the SOAP Header so I'd expect that 
> due to the wonders of AXIOM the whole document won't be parsed, just the 
> first few elements.
> I'm not an expert on AXIOM/parsing though..
> David
> 
> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 04:42:40 
> PM:
> 
>> David,
>>
>> can you suggest me the best way to get it from the SOAP envelope? Is
>> parsing the full document the only way to get it?
>>
>>
>> Thanks,
>> Michele
>>
>> Michele Mazzucco wrote:
>>> David,
>>>
>>> I'm sorry, I was wrong. Actually it is available :).
>>>
>>> Thanks,
>>> Michele
>>>
>>>
>>> Michele
>>>
>>> Michele Mazzucco wrote:
 David,

 I realized that the first element local name is actually the 
> operation
 name, and not the ws action.

 Thanks,
 Michele

 David Illsley wrote:
> In short, no.
>
> The only way to get the wsaddressing action is to read the 
>> contents of the 
> wsa:Action element.
> That probably doesn't help :-( but it's the case.
 Yes, unfortunately it doesn't help :( since it seems to me that the
 wsa:Action is not available before the transport/security phase.


 Regards,
 Michele
> David Illsley
>
> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 
>> 06/29/2006 10:24:19 
> AM:
>
>> And add "urn:" before it?
>>
>> Michele
>>
>> Michele Mazzucco wrote:
>>> Hi all,
>>>
>>> I've got a handler running before the transport phase. How can I 
> get 
> the
>>>  WS addressing action there as the  element is created
>>> later? Is it enough to get the first element local name of the 
> SOAP 
> body?
>>> Thanks,
>>> Michele
>>>
>>>
> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>> -
>> 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: Content is not allowed in prolog

[Tomas Molina]

Hello,

I had this same error before.  Question though, what version of Axis are 
you using?  Also if you are
using any attachments in your program, you need to include the 
activation.jar.


Tom


Luanne Coutinho wrote:


Hi,

 

I used wsdl2Java to generate stubs so that I can access a web service 
hosted elsewhere.


I wrote a test program to invoke an operation, but I keep getting this 
error:


 


AxisFault

 faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException


 faultSubcode:

 faultString: org.xml.sax.SAXParseException: Content is not allowed in 
prolog.


 faultActor:

 faultNode:

 faultDetail:


{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: 
Content is not allowed in prolog.


at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)


at 
org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)


at 
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)


at 
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)


at 
org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)


at 
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown 
Source)


at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)


at 
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)


at 
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)


at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at 
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)


at 
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)


at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)

at 
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)


at 
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)


at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)

at 
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)


at 
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)


at org.apache.axis.client.Call.invokeEngine(Call.java:2784)

at org.apache.axis.client.Call.invoke(Call.java:2767)

at org.apache.axis.client.Call.invoke(Call.java:2443)

at org.apache.axis.client.Call.invoke(Call.java:2366)

at org.apache.axis.client.Call.invoke(Call.java:1812)

 

Could someone please help? I have tried all sugestions from this 
mailing list, but none have resolved the problem.


 


Thanks

Luanne Misquitta

 




-


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

Re: [Axis2] How to access the soapAction from Handlers

[David Illsley]

As far as I know you'll have to parse the document.
The wsa:Action element will be found in the SOAP Header so I'd expect that 
due to the wonders of AXIOM the whole document won't be parsed, just the 
first few elements.
I'm not an expert on AXIOM/parsing though..
David

Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 04:42:40 
PM:

> David,
> 
> can you suggest me the best way to get it from the SOAP envelope? Is
> parsing the full document the only way to get it?
> 
> 
> Thanks,
> Michele
> 
> Michele Mazzucco wrote:
> > David,
> > 
> > I'm sorry, I was wrong. Actually it is available :).
> > 
> > Thanks,
> > Michele
> > 
> > 
> > Michele
> > 
> > Michele Mazzucco wrote:
> >> David,
> >>
> >> I realized that the first element local name is actually the 
operation
> >> name, and not the ws action.
> >>
> >> Thanks,
> >> Michele
> >>
> >> David Illsley wrote:
> >>> In short, no.
> >>>
> >>> The only way to get the wsaddressing action is to read the 
> contents of the 
> >>> wsa:Action element.
> >>> That probably doesn't help :-( but it's the case.
> >> Yes, unfortunately it doesn't help :( since it seems to me that the
> >> wsa:Action is not available before the transport/security phase.
> >>
> >>
> >> Regards,
> >> Michele
> >>> David Illsley
> >>>
> >>> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 
> 06/29/2006 10:24:19 
> >>> AM:
> >>>
>  And add "urn:" before it?
> 
>  Michele
> 
>  Michele Mazzucco wrote:
> > Hi all,
> >
> > I've got a handler running before the transport phase. How can I 
get 
> >>> the
> >  WS addressing action there as the  element is created
> > later? Is it enough to get the first element local name of the 
SOAP 
> >>> body?
> > Thanks,
> > Michele
> >
> > 
-
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>  
-
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
> 
> >>> 
-
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> -
> 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: More Axis & wrapped (Was: Re: No such operation)

[Anne Thomas Manes]

Doug,The WSDL2Java Reference Guide documents the -W --nowrapped option. Seehttp://ws.apache.org/axis/java/reference.html#WSDL2JavaReference
 My recommendation is to define your WSDLs following the wrapped convention, but to turn it off in your service implementation (using -W). That gives your client developers to use the wrapped option if they like.
AnneOn 6/28/06, Doug B <[EMAIL PROTECTED]> wrote:
Sigh.  I changed our WSDL & Schema to use a naming convention that Ithought would work with Axis' current default behaviour on the serverside, and it caused its own issues.  Namely, apparently 4 of my 5operation signatures now meet all Axis' criteria for "wrapped" style,
but one does not.  So Axis generated 1 interface method the way Iwanted, with request and response complexType beans, and 4 "wrapped"style methods (which would have confused the heck out of me if we
hadn't had this whole discussion).Eventually I got the ant  task to not use "wrapped"(seemingly undocumented syntax*), so things look like they might beok.  My test-generated server 
deploy.wsdd at least looks like theqnames will match now.I'm not sure if using a "wrapped-compatible" WSDL is better or worseif you're not planning on actually using wrapped mappings.  It looks
like, at least with Axis, either way you have to customize thegenerated artifacts, so you have to know about "wrapped" even if youdon't want to use it.BTW, wrapped looks much harder to use portably than non-wrapped, from
a business code point-of-view.  The wrapped method signatures havedependencies on axis packages, where the non-wrapped ones only havedependencies on my Schema beans, which ideally, one day, will betotally POJO allowing me to switch out engines easily.  But that's a
different subject.* http://ws.apache.org/axis/java/ant/axis-wsdl2java.html doesn'tdocument any attribute to disable wrapped, but setting the attribute
noWrapped="true" in the main element of the task worked.Doug-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

RE: ReplyTo is not working

[David Illsley]

"Munir Badir" <[EMAIL PROTECTED]> wrote on 06/29/2006 03:03:21 PM:

> Eran, thanks for answering the question.
> The bottom line is:
> -
> I'm trying to use the ReplyTo header. So I'll be more than thankful 
> if you can send me the simplest example for calling a service on 
> HTTP and getting response back via HTTP using the ReplyTo node in 
> WS-Addressing.
> 
> About the question:
> -
> I tried to use the ReplyTo header using the Axis2 userguide samples.
> In the Axis2 samples\userguide there is an example of a service 
> called MyService which has three methods: echo, ping and pingF
> package userguide.example1;

> }
> I wanted the result of the echo method call to be sent to the 
> MyService service, and call the ping method. So I added the following
> options.setReplyTo(new EndpointReference("http://localhost:
> 8080/axis2/services/MyService"));
> In the EchoNonBlockingDualClient so that the result of the echo call 
would 
> be sent to MyService service, and changed the result of the echo method 
to be
> ping element (for calling the ping method of MyService).

> Maybe I don?t understand the whole point around the ReplyTo, but I 
> expected that the EchoNonBlockingDualClient will call the MyService.
> echo() method and the result of this call would be sent to the 
> MyService with the ping action, calling the ping method.
> But the ping method was not called at all.
> 
> Thanks,
> Munir 
> -Original Message-
> From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 29, 2006 4:23 PM
> To: axis-user@ws.apache.org
> Subject: Re: ReplyTo is not working
> Munir Badir wrote:
> > As a result I expected that the echo method would call the ping 
method,
> > but it didn?t. Can anyone help?
> I'm still confused in understanding the question. If you can explain a
> bit with your code, it will be helpful in answering this question.
> 
> Thanks,
> Chinthaka

Munir,
I think I understand your scenario:
You want to invoke a service and have the result sent to (and 
processed by) another service.

I have a couple of comments based on this:
 1. For that scenario you don't need a 2-way client as there will never be 
a response to the client (it should go to the ping service).
 2. The scenario isn't currently supported by Axis2. I proposed a patch to 
support it a while ago that received some objections and I've been meaning 
to follow it up. This has reminded me about it and I'll follow up soon.
 3. There is a ReplyTo based scenario which Axis2 does support, namely an 
asynchronous 2-way invocation where the response is sent back to the 
initiating client on a second connection though I don't think this matches 
what you're trying to do. (I think its what you've based your client on)

David

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

Re: [Axis2] Flash Not Compatible with Axis2

[Luke DeWitt]

Sorry for the late reply.

Using TCPmon I attempted to use my webservice on my localhost, port 80.

This is what came up in TCPmon. In the higher of the two windows I got.

GET /axis2/services/version?wsdl HTTP/1.1
Referer: http://localhost:9000/axis2/services/version?wsdl
x-flash-version: 8,0,22,0
User-Agent: Shockwave Flash
Host: localhost:9000
Cache-Control: no-cache
Cookie: JSESSIONID=871705657F39D028CFCA7DC17836C6A5

POST /axis2/services/version HTTP/1.1
Referer: http://localhost:9000/axis2/services/version
x-flash-version: 8,0,22,0
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:getVersion"
Content-Length: 281
User-Agent: Shockwave Flash
Host: localhost:9000
Cache-Control: no-cache
Cookie: JSESSIONID=871705657F39D028CFCA7DC17836C6A5


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


and in the Lower of the two, I got:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml
Transfer-Encoding: chunked
Date: Thu, 29 Jun 2006 15:43:07 GMT

c39
http://schemas.xmlsoap.org/wsdl/"; 
xmlns:axis2="http://ws.apache.org/axis2"; 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
xmlns:ns0="http://axisversion.sample/xsd"; 
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; 
xmlns:ns1="http://org.apache.axis2/xsd"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
targetNamespace="http://ws.apache.org/axis2";>xmlns:ns="http://axisversion.sample/xsd"; 
targetNamespace="http://axisversion.sample/xsd"; 
elementFormDefault="unqualified" attributeFormDefault="unqualified">











element="ns0:getVersion" name="part1" />name="getVersionResponse">name="part1" />name="versionPortType">message="axis2:getVersionMessage" />message="axis2:getVersionResponse" 
/>type="axis2:versionPortType" name="versionSOAP11Binding">style="document" transport="http://schemas.xmlsoap.org/soap/http"; 
/>soapAction="urn:getVersion" />namespace="http://ws.apache.org/axis2"; use="literal" 
/>namespace="http://ws.apache.org/axis2"; use="literal" 
/>type="axis2:versionPortType" name="versionSOAP12Binding">style="document" transport="http://schemas.xmlsoap.org/soap/http"; 
/>soapAction="urn:getVersion" />namespace="http://ws.apache.org/axis2"; use="literal" 
/>namespace="http://ws.apache.org/axis2"; use="literal" 
/>type="axis2:versionPortType" name="versionHttpBinding">verb="POST" />location="getVersion" />/>/>name="version">name="versionSOAP11port0">location="http://localhost:9000/axis2/services/version"; 
/>name="versionSOAP12port0">location="http://localhost:9000/axis2/services/version"; 
/>name="versionHttpport0">location="http://localhost:9000/axis2/rest/version"; 
/>

0

HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Thu, 29 Jun 2006 15:43:07 GMT
Connection: close

c6
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>soapenv:Client

56
null; nested exception is:
java.lang.NullPointerException
8f2
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
a

Re: [Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

David,

can you suggest me the best way to get it from the SOAP envelope? Is
parsing the full document the only way to get it?


Thanks,
Michele

Michele Mazzucco wrote:
> David,
> 
> I'm sorry, I was wrong. Actually it is available :).
> 
> Thanks,
> Michele
> 
> 
> Michele
> 
> Michele Mazzucco wrote:
>> David,
>>
>> I realized that the first element local name is actually the operation
>> name, and not the ws action.
>>
>> Thanks,
>> Michele
>>
>> David Illsley wrote:
>>> In short, no.
>>>
>>> The only way to get the wsaddressing action is to read the contents of the 
>>> wsa:Action element.
>>> That probably doesn't help :-( but it's the case.
>> Yes, unfortunately it doesn't help :( since it seems to me that the
>> wsa:Action is not available before the transport/security phase.
>>
>>
>> Regards,
>> Michele
>>> David Illsley
>>>
>>> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 10:24:19 
>>> AM:
>>>
 And add "urn:" before it?

 Michele

 Michele Mazzucco wrote:
> Hi all,
>
> I've got a handler running before the transport phase. How can I get 
>>> the
>  WS addressing action there as the  element is created
> later? Is it enough to get the first element local name of the SOAP 
>>> body?
> Thanks,
> Michele
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

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

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

Re: [Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

David,

I'm sorry, I was wrong. Actually it is available :).

Thanks,
Michele


Michele

Michele Mazzucco wrote:
> David,
> 
> I realized that the first element local name is actually the operation
> name, and not the ws action.
> 
> Thanks,
> Michele
> 
> David Illsley wrote:
>> In short, no.
>>
>> The only way to get the wsaddressing action is to read the contents of the 
>> wsa:Action element.
>> That probably doesn't help :-( but it's the case.
> 
> Yes, unfortunately it doesn't help :( since it seems to me that the
> wsa:Action is not available before the transport/security phase.
> 
> 
> Regards,
> Michele
>> David Illsley
>>
>> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 10:24:19 
>> AM:
>>
>>> And add "urn:" before it?
>>>
>>> Michele
>>>
>>> Michele Mazzucco wrote:
 Hi all,

 I've got a handler running before the transport phase. How can I get 
>> the
  WS addressing action there as the  element is created
 later? Is it enough to get the first element local name of the SOAP 
>> body?
 Thanks,
 Michele

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

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


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

Re: wsdl2java and namespaces

[John Ibbotson]

Thanks Anne,
The problem is that this is running under GT4 who (I think) have a back
level/modified version of wsdl2java. Will raise a bug on the globus site.

Regards,
John

John Ibbotson CEng FIEE
Grid Provenance Project, Emerging Technology Services
Hursley Park, MP137, Winchester, Hants. SO21 2JN, UK

Tel: +44 1962 815188
Mobile:  +44 7739 876 196
Email: [EMAIL PROTECTED]

Provenance:  http://www.gridprovenance.org

Technical Solutions to business problems that require innovation across IBM
knowledge portfolio.


   
 "Anne Thomas  
 Manes"
 <[EMAIL PROTECTED]  To 
 m>axis-user@ws.apache.org 
cc 
 29/06/2006 16:28  
   Subject 
   Re: wsdl2java and namespaces
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




Looks like a bug.

On 6/29/06, John Ibbotson <[EMAIL PROTECTED]> wrote:

  I have some WSDL that imports some schemas. The schema includes elements
  that are typed to WS-Addressing EndpointReferenceType. For example:

  

  The source of the message within the sender.

  


  The is a child of an element of type:

  



  


  When I use wsdl2java to build the stubs and deploy the service, my test
  message get deserialized on the server. However, the wsa namespace is not
  defined. A section of the
  deserialized XML looks like:
  http://www.pasoa.org/schemas/version024/PStruct.xsd";>
  

  http://TestCase.commonservices/IdentifiedContentWithIPAandASA/urlAsserter
  
  
  

  http://messageSource.hursley.ibm.com:18080/axis/services/sourceApplication

  
  
  
  

  http://messageSink.hursley.ibm.com:18080/axis/services/sinkApplication
  
  
  

  Note that the ps namespace is defined on the interactionKey element and I
  would have expected the wsa namespace to be defined on the messageSource
  and messageSink elements so that the child QNames are correct.

  Any idea what's going on ?

  Regards,
  John


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




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

Re: [Axis2,Sandesha2]MTOM/XOP + WSRM

[Mancinelli Elodie]

Hi Paul

Thanks for your response. I wish have more information because I don' t 
understand why MTOM can't work with XmlBeans? And what is the 
marshalling I have to use?
I try ADB but it not seems to work, I can't generate the server 
implementation.


In more, I create a client-server with only MTOM and I also create the 
same thing with only WSRM(sandesha2) and  both work separetly with 
XmlBeans. Is the problem is WSRM + MTOM together? And how could I do to 
resolve my problem?



Thanks a lot.

Regards
Elodie


Paul Fremantle wrote:


Elodie

I think the problem is that you are using MTOM with XMLBeans which
does not work.

Paul

--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

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


On 6/28/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:


Mancinelli Elodie wrote:

> Sorry, I want to precise my request. When I observe with TCPMon the
> soap message, the differents messages of WSRM's protocole are created
> (CreateSequence, CreateSequenceResponse, Message, Acknowldgement and
> TerminateSequence). These messages are correct. The problem is on the
> server after messages.
>
> Thanks,
>
> Regards,
> Elodie
>
>
> Mancinelli Elodie wrote:
>
>> Hi all,
>>
>> I try to create an OneWay method which supports WSRM and an 
attachment.

>> My service is really simple, it's only a "println".
>> The method runs successfully when there is only the WSRM
>> implementation, but when I add the attachement part, I have an server
>> error:
>>
>> org.apache.sandesha2.SandeshaException: Data binding error; nested
>> exception is:
>>java.lang.RuntimeException: Data binding error; nested
>> exception is:
>>org.apache.axis2.AxisFault: Data binding error; nested
>> exception is:
>>java.lang.RuntimeException: Data binding error
>>at
>> 
org.apache.sandesha2.workers.InOrderInvoker.run(InOrderInvoker.java:199)

>> Caused by: org.apache.axis2.AxisFault: Data binding error; nested
>> exception is:
>>java.lang.RuntimeException: Data binding error
>>at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
>>at
>> 
fr.gouv.finances.dgme.presto.PrestoSvcMessageReceiverInOnly.invokeBusinessLogic(PrestoSvcMessageReceiverInOnly.java:50) 


>>
>>at
>> 
org.apache.axis2.receivers.AbstractInMessageReceiver.receive(AbstractInMessageReceiver.java:34) 


>>
>>at
>> org.apache.axis2.engine.AxisEngine.resumeReceive(AxisEngine.java:497)
>>at 
org.apache.axis2.engine.AxisEngine.resume(AxisEngine.java:543)

>>at
>> 
org.apache.sandesha2.workers.InOrderInvoker.run(InOrderInvoker.java:189)

>> Caused by: java.lang.RuntimeException: Data binding error
>>at
>> 
fr.gouv.finances.dgme.presto.PrestoSvcMessageReceiverInOnly.fromOM(PrestoSvcMessageReceiverInOnly.java:174) 


>>
>>at
>> 
fr.gouv.finances.dgme.presto.PrestoSvcMessageReceiverInOnly.invokeBusinessLogic(PrestoSvcMessageReceiverInOnly.java:46) 


>>
>>... 4 more
>> Caused by: org.apache.axiom.om.OMException:
>> java.lang.NullPointerException
>>at
>> org.apache.axiom.om.impl.llom.OMTextImpl.getText(OMTextImpl.java:254)
>>at
>> 
org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:365) 


>>
>>at
>> 
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154) 


>>
>>at
>> 
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)

>>at
>> 
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)

>>at
>> 
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) 


>>
>>at
>> 
fr.gouv.finances.dgme.presto.SubmitOneWayDocument$Factory.parse(SubmitOneWayDocument.java:128) 


>>
>>at
>> 
fr.gouv.finances.dgme.presto.PrestoSvcMessageReceiverInOnly.fromOM(PrestoSvcMessageReceiverInOnly.java:145) 


>>
>>... 5 more
>> Caused by: java.lang.NullPointerException
>>at
>> 
org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:737) 


>>
>>at
>> 
org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:777) 


>>
>>at
>> 
org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:710) 


>>
>>at org.apache.coyote.Request.doRead(Request.java:423)
>>at
>> 
org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:283) 


>>
>>at
>> org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:371)
>>at
>> 
org.apache.catalina.connector.InputBuffer.readByte(InputBuffer.java:292)

>>at
>> 
org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:104) 


>>
>>at java.io.FilterInputStream.read(FilterInputStream.java:66)
>>at 
java.io.PushbackInputStream.read(PushbackInputStream.java:120)

>>at
>> 
org.ap

Re: Howto add schema definition of type to wsdl?

[Anne Thomas Manes]

Is ScheduleMetaData defined as a JavaBean? Did you run java2wsdl?Or did you perhaps try to deploy the service using the .jws option?If you are using complex types, then you can't use the .jws option.
(I'm assuming that you're using Axis 1.)AnneOn 6/29/06, Jansen Werner <[EMAIL PROTECTED]
> wrote:Hallo everybody,I have a web service called ScheduleNotifyService. It has a single
operation called "scheduleNotify". This operation needs a parameter ofjava type ScheduleMetaData. So I wrote a Serializer/Deserializer pairwith their corresponding factories. This works.But: When I call my wsdl using ScheduleNotifyService?wsdl, it defines a
part without defining ScheduleMetaData in the document. Is it possible toautomatically include the definition for my java types somehow? Axis
could - i suppose - extract the definition from the serializer. Do Ineed to manually include the definition?I hope I made myself clear. :) If not, don't hesitate to ask for furtherinformation ... :)
Greetings from Munich,Werner Jansen-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

David,

I realized that the first element local name is actually the operation
name, and not the ws action.

Thanks,
Michele

David Illsley wrote:
> In short, no.
> 
> The only way to get the wsaddressing action is to read the contents of the 
> wsa:Action element.
> That probably doesn't help :-( but it's the case.

Yes, unfortunately it doesn't help :( since it seems to me that the
wsa:Action is not available before the transport/security phase.


Regards,
Michele
> 
> David Illsley
> 
> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 10:24:19 
> AM:
> 
>> And add "urn:" before it?
>>
>> Michele
>>
>> Michele Mazzucco wrote:
>>> Hi all,
>>>
>>> I've got a handler running before the transport phase. How can I get 
> the
>>>  WS addressing action there as the  element is created
>>> later? Is it enough to get the first element local name of the SOAP 
> body?
>>> Thanks,
>>> Michele
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

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

Re: wsdl2java and namespaces

[Anne Thomas Manes]

Looks like a bug.On 6/29/06, John Ibbotson <[EMAIL PROTECTED]> wrote:
I have some WSDL that imports some schemas. The schema includes elementsthat are typed to WS-Addressing EndpointReferenceType. For example:  
  The source of the message within the sender.  
  The is a child of an element of type:
  
When I use wsdl2java to build the stubs and deploy the service, my testmessage get deserialized on the server. However, the wsa namespace is notdefined. A section of thedeserialized XML looks like:xmlns:ps="http://www.pasoa.org/schemas/version024/PStruct.xsd">
http://TestCase.commonservices/IdentifiedContentWithIPAandASA/urlAsserter
http://messageSource.hursley.ibm.com:18080/axis/services/sourceApplication
http://messageSink.hursley.ibm.com:18080/axis/services/sinkApplication
Note that the ps namespace is defined on the interactionKey element and Iwould have expected the wsa namespace to be defined on the messageSourceand messageSink elements so that the child QNames are correct.
Any idea what's going on ?Regards,John-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] How to access the soapAction from Handlers

[David Illsley]

In short, no.

The only way to get the wsaddressing action is to read the contents of the 
wsa:Action element.
That probably doesn't help :-( but it's the case.

David Illsley

Michele Mazzucco <[EMAIL PROTECTED]> wrote on 06/29/2006 10:24:19 
AM:

> And add "urn:" before it?
> 
> Michele
> 
> Michele Mazzucco wrote:
> > Hi all,
> > 
> > I've got a handler running before the transport phase. How can I get 
the
> >  WS addressing action there as the  element is created
> > later? Is it enough to get the first element local name of the SOAP 
body?
> > 
> > Thanks,
> > Michele
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

Re: [Axis2] REST vs. SOAP and enableREST

[Anne Thomas Manes]

RESTiness refers to how the service is exposed to the outside world, not to the way Axis handles the request internally. The message receiver determines how Axis handles the request internally.A REST interface exposes the service as a resource with a unique URL. It supports the following possible operations/methods on that resource (and no others):
- GET- POST- PUT- DELETEAnneOn 6/29/06, heikki <[EMAIL PROTECTED]> wrote:
Hi there,it seems I'm not quite getting how Axis2 handles REST vs. SOAP ..
>From the documentation I had gathered that this element in the server side's axis2.xml :true
should cause REST handling of incoming messages. I had therefore also assumed that setting this parameter to false, or removing it altogether, would cause Axis2 to handle incoming messages as SOAP -- which would mean (I thought) discarding the envelope before binding the payload to the type expected in the SEI. 
However, I see no difference in behaviour at all ! Whether I set this parameter to false or true or take it out; Axis2 keeps handling messages as REST messages ! So if I have a client sending SOAP (instead of REST) messages, the SOAP message does not get processed correctly, as it's trying to bind the SOAP:Envelope type to the type expected in the SEI -- it does this even though the enableREST param is false !
I have now modified the generated MyServiceMessageReceiverInOut such that its fromOM() method checks for SOAP-ness of the param and if so, it discards the SOAP envelope before trying to bind the payload. This way it now correctly handles both SOAP and REST messages coming in. But I have a distinct feeling that this is fishy; that I shouldn't have to do this; that I'm missing something here; and that the enableREST parameter setting should have some impact on how Axis2 behaves.
Anyone care to explain these matters ?thank you !Heikki Doeleman

Re: [Axis2] large MTOM binary data not returning to client

[Andrew B]

It is an SSL connection to the production server, so I cannot do packet sniffing. By the MTOM entry, do you mean the OMText node that is created from calling factory.createOMText(dataHandler, true) ?I don't think it's the Axis1 client, because the problem is intermittent - sometimes it works on the large data chunks, and sometimes not. -AndrewPaul Fremantle <[EMAIL PROTECTED]> wrote: Have you tried doing any packet sniffing? It might well be the Axis1client? I assume you have optimised = false on the MTOM entry?PaulOn 6/28/06, Andrew B <[EMAIL PROTECTED]> wrote:> Hi,>> I have an Axis2 service running in our production environment. The web> service call completes, but control is not returned to the client.>> It is passing back 1.2Mb of binary data, via
 MTOM. Smaller amounts of binary> work consistently (say 350Kb or so). The client is Axis1 (Java). The app> server is JBoss 4.0.3 running on Linux, with JDK 1.4. MTOM is enabled,> according to the documentation:>> true>> The server-side processing always completes, in around 1 minute, according> to the log files, even when the data is not returned. According to the JBoss> console, the request is still being processed, even though the web service> call is complete.>> Any ideas at all are appreciated!>> Thanks, as always,>>> Andrew>  > Sneak preview the all-new Yahoo.com. It's not radically different. Just> radically better.>>-- Paul FremantleVP/Technology, WSO2 and OASIS WS-RX TC
 Co-chairhttp://bloglines.com/blog/paulfremantle[EMAIL PROTECTED]"Oxygenating the Web Service Platform", www.wso2.com-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] 
		Do you Yahoo!? 
Get on board. You're invited to try the new Yahoo! Mail Beta.

Re: Min lentgh and max length of an input string parameter

[Anne Thomas Manes]

Create a handler that validates the message.AnneOn 6/29/06, Roy <[EMAIL PROTECTED]> wrote:
Hello,     I have edited the wsdl with this field in a string element:        
      
     Is any way AXIS to validate automatically this maxExclusive and throw an exception if this value exceeds the limit?  
   Regards,  Roy  Anne Thomas Manes <
[EMAIL PROTECTED]> έγραψε:  You need to edit the WSDL file to add this type of restriction.
  On 6/28/06, Roy <[EMAIL PROTECTED]> wrote:
 Hello all,Does anyone know a way to declare max and min size of a string in a input parameter in a wsdl generated with the Java2WSDL tool? Can i declare something in the 
deploy.wsdd file?Thanks,  RoyΧρησιμοποιείτε Yahoo!Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το
 Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr

		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr 

wsdl2java and namespaces

[John Ibbotson]

I have some WSDL that imports some schemas. The schema includes elements
that are typed to WS-Addressing EndpointReferenceType. For example:
  

  
The source of the message within the sender.
  

  

The is a child of an element of type:
  

  
  
  

  

When I use wsdl2java to build the stubs and deploy the service, my test
message get deserialized on the server. However, the wsa namespace is not
defined. A section of the
deserialized XML looks like:
http://www.pasoa.org/schemas/version024/PStruct.xsd";>


http://TestCase.commonservices/IdentifiedContentWithIPAandASA/urlAsserter




http://messageSource.hursley.ibm.com:18080/axis/services/sourceApplication





http://messageSink.hursley.ibm.com:18080/axis/services/sinkApplication




Note that the ps namespace is defined on the interactionKey element and I
would have expected the wsa namespace to be defined on the messageSource
and messageSink elements so that the child QNames are correct.

Any idea what's going on ?

Regards,
John


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

Re: cannot generate axis2 client stubs

[Nicolas Urien]

Suddenly the script started to work!Thanks for your help,- Original Message From: Nicolas Urien <[EMAIL PROTECTED]>To: axis-user@ws.apache.orgSent: Thursday, June 29, 2006 4:08:02 PMSubject: Re: cannot generate axis2 client stubsHi,Sorry but what do you mean exactly please?I am using the axis bundled war ( version 1.0 released on 05-05-06) on tomcat 5.thank
 you,- Original Message From: Ajith Ranabahu <[EMAIL PROTECTED]>To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>Sent: Thursday, June 29, 2006 3:32:33 PMSubject: Re: cannot generate axis2 client stubsHi,is the adb-codegen module in class pathAjithOn 6/29/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> Hi,>> I have just found out what the problem was : I had
 added an extra space on> the command line with:> WSDL2Java.bat -uri> http://localhost.urssaf.fr:8080/axis2/services/PojoDao?wsdl> -o c:\axis2bis\bin>> Now I get a different stack trace (maybe easier to fix?). (PojoDao is> another web service)>> Thanks for helping>>> Using AXIS2_HOME:   C:\axis2bis> Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06> Exception in thread "main"> org.apache.axis2.wsdl.codegen.CodeGenerationException> : java.lang.RuntimeException:> java.lang.ClassNotFoundException:> org.apache.axis2.schema.ExtensionUtility> at>
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235)>> at> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)> at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> Caused by: java.lang.RuntimeException:> java.lang.ClassNotFoundException: org.apa> che.axis2.schema.ExtensionUtility> at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp> leDBExtension.java:52)> at> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener> ationEngine.java:188)> ... 2 more> Caused by: java.lang.ClassNotFoundException:>
 org.apache.axis2.schema.ExtensionUt> ility> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)> at> java.security.AccessController.doPrivileged(Native Method)> at> java.net.URLClassLoader.findClass(URLClassLoader.java:188)> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)> at> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)> at> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)> at
 java.lang.Class.forName0(Native Method)> at java.lang.Class.forName(Class.java:164)> at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp> leDBExtension.java:44)> ... 3 more> - Original Message > From: Kinichiro Inoguchi <[EMAIL PROTECTED]>> To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>> Sent: Thursday, June 29, 2006 1:35:10 PM> Subject: Re: cannot generate axis2 client stubs>> Hi Nicolas,>> could you post your service aar file ?>> Regards,> kinichiro>> --- Nicolas Urien <[EMAIL PROTECTED]> wrote:>> > Hi Kinichiro,> >> > No it has parameters :>
 >> > public String echo(String value) {> > return value;> > }> >> > cheers> >> >   Nicolas Urien> >> > Mobile phone : +33-6 75 77 15 42> >> >  Victory favors those who take pains> >> >> >> >> >> >> > - Original Message > > From: Kinichiro Inoguchi <[EMAIL PROTECTED]>> > To: axis-user@ws.apache.org> > Sent: Wednesday, June 28, 2006 8:19:13 PM> > Subject: Re: cannot generate axis2 client stubs> >> > Nicolas,> >> > Does your service class method have no in/out parameter, like this ?> >> > public void echo () {> > System.out.println("hello world");> >
 }> >> >> > --- Nicolas Urien <[EMAIL PROTECTED]> wrote:> >> > > Hello,> > >> > > I have successfully deployed a very simple aar archive ("hello> > > world") into my axis tomcat server.> > > I started from an implementation class and so I didn't write any> > wsdl> > > file.> > >> > > I cannot generate the axis2 client stubs. Here is the exception> > > I get (The entity "nbsp" was referenced, but not declared.) when> > > executing :> > >> > > WSDL2Java.bat -uri> http://localhost.urssaf.fr:8080/axis2/services/> > > SimpleService?wsdl -o c:\axis2bis\bin\> > >> > > Using AXIS2_HOME:   C:\axis2bis>
 > > Using
 JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06> > > Exception in thread "main"> > > org.apache.axis2.wsdl.codegen.CodeGenerationException> > > : Error parsing WSDL> > > at> > >> >> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat> > > ionEngine.java:125)> > > at> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)> > > at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > > Caused by: WSDLException: faultCode=PARSER_ERROR: Parser SAX Error:> > > Fatal Error:> > >  URI=http://localhost.urssaf.fr:8080/axis2/services/> Line=32: The> > > entity "nbsp"> > > was referenced, but not declared.: org.xml.sax.SAXException: Fatal> > > Error: URI=

Re: sending soap messages asynchronously

[Anne Thomas Manes]

Keep in mind that in order for your Axis "client" to receive unsolicited messages, it must be a "server". And yes, Axis2 supports this type of processing.Anne
On 6/29/06, Phani Sekhar <[EMAIL PROTECTED]> wrote:
Thank you very much for ur response ...We want the Axis server to first initiate and send one-way messages to theAxis client.Can we configure the Axis2 server in such a way ???~ Phani Sekhar
-Original Message-From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 29, 2006 1:01 PMTo: 
axis-user@ws.apache.orgSubject: Re: Re : sending soap messages asynchronouslyAxis2 support asynchronous invocationPhani Sekhar wrote:> Hi all,>> We are implementing NETCONF on SOAP over HTTP. We are using Axis.
>> We require the Axis web service to send some soap messages> asynchronously to the Axis client without any initiation.>> Ofcourse for the first time, we can register the client at the server.
> We are trying to implement something similar to the snmp> traps/notifications.>> Is is possible to do this using Axis Does Axis support> asynchronous messaging???>>
>> Please help me. Thanks in advance>> Phani Sekhar -Original Message-> *From:* Phani Sekhar [mailto:
[EMAIL PROTECTED]]> *Sent:* Wednesday, June 21, 2006 12:47 PM> *To:* axis-user@ws.apache.org> *Subject:* sending asynchronous soap messages
 Hi,>> Is there any way to send asynchronous soap messages from a webservice> in Axis, something similar to snmp notifications ??? Thanks in Advance
>> Phani Sekhar>--Thanks,Deepal~Future is Open~-
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: Compatability of wss4j with XWS-Security implementation WS-security

[Anne Thomas Manes]

They should. Please recount your experiences.On 6/29/06, Kashif Saleem <[EMAIL PROTECTED]
> wrote:Hi All,   I am using axis1.3 for calling couple of secure web-service which are secured using 
JWSDP2.0 which uses XWS-Security implementation.   But as axis1.3 uses wss4j implementation so I am just wondering if it possible to communicate with secure services which uses JWSDP2.0.I would really appreciate if someone could shed light on 
it.Thanks.Kind RegardsKashif-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] ServiceClient running inside a handler problem

[Michele Mazzucco]

Hi all,

how can let a ServiceClient running inside a handler work? The request
to the service executes correctly, but the result is not sent back (the
endpoint is set to
http://null:8080/axis2/services/annonService5978327/annonOutInOp).


Thanks,
Michele

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

RE: [Axis2] unable to turn off Axiom OMElement caching in client

[Gordon, Gary]

Hi Ajith,

Thanks for the tip, which is perfect except for one little problem.  I
now seem to be able to handle 30 MB payloads (although I need to do some
memory profiling to verify for sure).  The only problem is that
setParent() is not exposed as a method in the OMElement interface.  I
need to cast to the concrete impl class as such:

OMElement oe = builder.getDocumentElement();
org.apache.axiom.om.impl.llom.OMElementImpl oei =
(org.apache.axiom.om.impl.llom.OMElementImpl) oe;
oei.setParent(null);

So either the setParent() method needs to be added to the interface or a
fix needs to be made somewhere else in the internal processing of the
payload.  I prefer the first option (perhaps in addition to the second).
I think a bug submission needs to be made to JIRA, but I'll defer to you
if you prefer.

Regards,
Gary

-Original Message-
From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 29, 2006 9:42 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] unable to turn off Axiom OMElement caching in
client

Hi Gary,
Hmm... this seems like an issue we need to look into. I'm not sure
whether the caching flag is useful any more (it is a left over from
one of the previous features AFAIK).

Just try this and see whether it works.

Just before return oe, add a statement
oe.setParent(null);

that should avoid any building of the tree

Ajith

On 6/29/06, Gordon, Gary <[EMAIL PROTECTED]> wrote:
>
>
>
>
> (Reposting earlier message but with [Axis2] in subject line hoping
someone
> else will read this).
>
>
>
> For a ServiceClient, you must produce an OMElement for the SOAP body,
but I
> don't see a way to write a client that doesn't build the whole OM
object
> tree for the payload.  I run out of memory for a large payload.  If I
set
> caching to false as follows, the Axiom code infinite loops:
>
>
>
> public OMElement getPayload(InputStream is) throws XMLStreamException
{
>
> XMLInputFactory xif = XMLInputFactory.newInstance();
>
> XMLStreamReader reader = xif.createXMLStreamReader(is);
>
> StAXOMBuilder builder = new StAXOMBuilder(reader);
>
> builder.setCache(false);
>
> OMElement oe = builder.getDocumentElement();
>
> return oe;
>
> }
>
>
>
> This is caused by the following sequence of calls in Axiom, wherein
the
> document element is never set to a non-null value because caching is
on.
>
>
>
> OMDocumentImpl:
>
> public OMElement getOMDocumentElement() {
>
>   while (documentElement == null) {
>
> parserWrapper.next();
>
>   }
>
>   return documentElement;
>
> }
>
>
>
> StAXOMBuilder:
>
> public int next() throws OMException {
>
>   try {
>
> if (done) {
>
>   throw new OMException();
>
> }
>
> int token = parser.next();
>
> if (!cache) {
>
>   return token;
>
> }
>
>
>
> ..etc.
>
>
>
> Now if I comment out the call to turn off caching, Axiom merrily goes
along
> and builds the entire OM tree, so I run out of memory for large
documents.
> This is because
>
>
>
> OMElement result = sender.sendReceive(payload);
>
>
>
> eventually calls:
>
> ServiceClient.fillSOAPEnvelope()
>
>
>
> which eventually leads to:
>
> OMElementImpl.detach();
>
>
>
> The detach() causes the whole tree to be rendered as OMObjects.  For a
> similar server-side question that was asked, the Axis person suggested
> looking at the OMDatasource test code, but looking at this seemed to
yield
> nothing relevant unless I'm missing something.
>
>
>
> Any suggestions on how to efficiently handle a large client-side
payload
> using Axiom?  Is this a bug that should be submitted?
>
>
>
>
>
> Gary Gordon
>
>
>
>
>
>
>
> Gary Gordon
>
> R&D Fellow
>
> Software AG, Inc.
>
>


-- 
Ajith Ranabahu

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


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

Re: [Axis2] WS soap action question

[Michele Mazzucco]

Hi Eran,

Eran Chinthaka wrote:
> Michele Mazzucco wrote:
>> Hi Eran,
>>
>> does AxisServlet run after the dispatchers? 
> 
> Its our http transport listener, in war case, and it runs before
> dispatchers.
> 
>> I need to get the soap
>> action in a handler running before the dispatcher phase: is there any
>> way to get it? If so, how can I accomplish my goal?
> 
> messageContext.getSoapAction()


the problem is that it's null (I create the message context before the
transport phase, and running the handler before the security phase
doesn't change the situation):

DEBUG RouterDispatcher:clientRequest - Target action mapping [null]


Any idea?
> 
> -- Chinthaka
> 


Michele

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

Re: [axis2] code generated service :: Operation not found

[studium-sbr]

Thank you Deepal, but I think the action is set.
While debugging I can see that the options-Container of the 
messageContext-Object has an entry
action with the value 'http://localhost:8080/axis2/services/MyService/myMethod'
which is the correct URL.

Attached is the client (stubclass).
While stepping through the stubs myMethod the axisOperation within the 
messageContext seems to be correct. The field soapAction has the value 
urn:myMethod. 
Within the OutInAxisOperationClient::execute(), MC.getSoapAction() returns 
http://localhost:8080/axis2/services/MyService/myMethod


Is it possible that the cause of this error is the first element in the body 
which is called myMethodRequest

--
The sent SOAP-Message I get from the MessageContext envelope-variable looks 
like this:


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


http://localhost:8080/axis2/services/MyService/xsd";>

hostname





Does anyone has further ideas ?

Thanks so long

Bille
> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 29.06.06 08:00:25
> An: axis-user@ws.apache.org
> Betreff: Re: [axis2] code generated service :: Operation not found


> Hi Studium;
> As I understand , you are not sending SOAP action in the request.
> try
> option.setAction("myMethod"); , before calling the service.
> 
> [EMAIL PROTECTED] wrote:
> 
> >Hi,
> >
> >I have a code generated service deployed, let's call it 'MyService'. The 
> >axis service list says the service is fine and has a method 'myMethod'
> >When running the Client with a simple message I get an AxisFault saying:
> >
> >Operation Not found EPR is http://localhost:8080/axis2/services/MyService 
> >and WSA Action =  http://localhost:8080/axis2/services/MyService/myMethod
> > at 
> > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
> >
> >While debugging I realized, that the instance variable axisOperation isn't 
> >set (DispatchPhase::checkPostCondition()).
> >The AxisEngine class doesn't seem to get the axisOperation set.
> >For code  generation I used the Eclipse PlugIn Version 1.2.0
> >
> >I'm using the nightly build of 07.06.2006.
> >
> >Could anybody give me a hint please of what I'm missing?
> >
> >TIA Bille
> >
> >
> >__
> >Verschicken Sie romantische, coole und witzige Bilder per SMS!
> >Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~ 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193



MyServiceStub.java
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cannot generate axis2 client stubs

[Nicolas Urien]

Hi,Sorry but what do you mean exactly please?I am using the axis bundled war ( version 1.0 released on 05-05-06) on tomcat 5.thank you,- Original Message From: Ajith Ranabahu <[EMAIL PROTECTED]>To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>Sent: Thursday, June 29, 2006 3:32:33 PMSubject: Re: cannot generate axis2 client stubsHi,is the adb-codegen module in class pathAjithOn 6/29/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> Hi,>> I have just found out what the problem was : I had
 added an extra space on> the command line with:> WSDL2Java.bat -uri> http://localhost.urssaf.fr:8080/axis2/services/PojoDao?wsdl> -o c:\axis2bis\bin>> Now I get a different stack trace (maybe easier to fix?). (PojoDao is> another web service)>> Thanks for helping>>> Using AXIS2_HOME:   C:\axis2bis> Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06> Exception in thread "main"> org.apache.axis2.wsdl.codegen.CodeGenerationException> : java.lang.RuntimeException:> java.lang.ClassNotFoundException:> org.apache.axis2.schema.ExtensionUtility> at>
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235)>> at> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)> at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> Caused by: java.lang.RuntimeException:> java.lang.ClassNotFoundException: org.apa> che.axis2.schema.ExtensionUtility> at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp> leDBExtension.java:52)> at> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener> ationEngine.java:188)> ... 2 more> Caused by: java.lang.ClassNotFoundException:>
 org.apache.axis2.schema.ExtensionUt> ility> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)> at> java.security.AccessController.doPrivileged(Native Method)> at> java.net.URLClassLoader.findClass(URLClassLoader.java:188)> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)> at> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)> at> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)> at
 java.lang.Class.forName0(Native Method)> at java.lang.Class.forName(Class.java:164)> at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp> leDBExtension.java:44)> ... 3 more> - Original Message > From: Kinichiro Inoguchi <[EMAIL PROTECTED]>> To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>> Sent: Thursday, June 29, 2006 1:35:10 PM> Subject: Re: cannot generate axis2 client stubs>> Hi Nicolas,>> could you post your service aar file ?>> Regards,> kinichiro>> --- Nicolas Urien <[EMAIL PROTECTED]> wrote:>> > Hi Kinichiro,> >> > No it has parameters :>
 >> > public String echo(String value) {> > return value;> > }> >> > cheers> >> >   Nicolas Urien> >> > Mobile phone : +33-6 75 77 15 42> >> >  Victory favors those who take pains> >> >> >> >> >> >> > - Original Message > > From: Kinichiro Inoguchi <[EMAIL PROTECTED]>> > To: axis-user@ws.apache.org> > Sent: Wednesday, June 28, 2006 8:19:13 PM> > Subject: Re: cannot generate axis2 client stubs> >> > Nicolas,> >> > Does your service class method have no in/out parameter, like this ?> >> > public void echo () {> > System.out.println("hello world");> >
 }> >> >> > --- Nicolas Urien <[EMAIL PROTECTED]> wrote:> >> > > Hello,> > >> > > I have successfully deployed a very simple aar archive ("hello> > > world") into my axis tomcat server.> > > I started from an implementation class and so I didn't write any> > wsdl> > > file.> > >> > > I cannot generate the axis2 client stubs. Here is the exception> > > I get (The entity "nbsp" was referenced, but not declared.) when> > > executing :> > >> > > WSDL2Java.bat -uri> http://localhost.urssaf.fr:8080/axis2/services/> > > SimpleService?wsdl -o c:\axis2bis\bin\> > >> > > Using AXIS2_HOME:   C:\axis2bis> > > Using
 JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06> > > Exception in thread "main"> > > org.apache.axis2.wsdl.codegen.CodeGenerationException> > > : Error parsing WSDL> > > at> > >> >> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat> > > ionEngine.java:125)> > > at> org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)> > > at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > > Caused by: WSDLException: faultCode=PARSER_ERROR: Parser SAX Error:> > > Fatal Error:> > >  URI=http://localhost.urssaf.fr:8080/axis2/services/> Line=32: The> > > entity "nbsp"> > > was referenced, but not declared.: org.xml.sax.SAXException: Fatal> > > Error: URI=ht> > > tp://localhost.urssaf.fr:8080/axis2/services/ Line=32:> The entity> > > "nbsp" was referenced, but not declared.> > > at> > >> >> org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils> > > .java:361)> > >   

RE: ReplyTo is not working

[Munir Badir]

Title: RE: ReplyTo is not working






Eran, thanks for answering the question.



The bottom line is:

-

I'm trying to use the ReplyTo header. So I'll be more than thankful if you can send me the simplest example for calling a service on HTTP and getting response back via HTTP using the ReplyTo node in WS-Addressing.


About the question:

-

I tried to use the ReplyTo header using the Axis2 userguide samples.



In the Axis2 samples\userguide there is an example of a service called MyService which has three methods: echo, ping and pingF







package userguide.example1;

import org.apache.axiom.om.OMAbstractFactory;

import org.apache.axiom.om.OMElement;

import org.apache.axiom.om.OMFactory;

import org.apache.axiom.om.OMNamespace;

import org.apache.axis2.AxisFault;

import javax.xml.stream.XMLStreamException;

/**

 * Created by IntelliJ IDEA.

 * User: Jaliya

 * Date: Jun 2, 2005

 * Time: 2:17:58 PM

 */

public class MyService {

    

    public OMElement echo(OMElement element) throws XMLStreamException {

    //Praparing the OMElement so that it can be attached to another OM Tree.

    //First the OMElement should be completely build in case it is not fully built and still

    //some of the xml is in the stream.

    element.build();

    //Secondly the OMElement should be detached from the current OMTree so that it can be attached

    //some other OM Tree. Once detached the OmTree will remove its connections to this OMElement.

    element.detach();

    return element;

    }

    public void ping(OMElement element) throws XMLStreamException {

    //Do some processing

    }

    public void pingF(OMElement element) throws AxisFault{

    throw new AxisFault("Fault being thrown");

    }

}




And there is a client called EchoNonBlockingDualClient which calls the echo method in the MyService service:



package userguide.clients;

import org.apache.axiom.om.OMAbstractFactory;

import org.apache.axiom.om.OMElement;

import org.apache.axiom.om.OMFactory;

import org.apache.axiom.om.OMNamespace;

import org.apache.axis2.AxisFault;

import org.apache.axis2.Constants;

import org.apache.axis2.addressing.EndpointReference;

import org.apache.axis2.client.Options;

import org.apache.axis2.client.ServiceClient;

import org.apache.axis2.client.async.AsyncResult;

import org.apache.axis2.client.async.Callback;

import javax.xml.namespace.QName;

/**

 * Sample for asynchronous dual channel non-blocking service invocation.

 * Message Exchage Pattern IN-OUT

 * Ulitmate asynchronous service invocation sample.

 */

public class EchoNonBlockingDualClient {

    private static EndpointReference targetEPR = new EndpointReference("http://localhost:8080/axis2/services/MyService");   

    

    public static void main(String[] args) {

    ServiceClient sender = null;

    try {

    OMElement payload = ClientUtil.getEchoOMElement();

    Options options = new Options();

    options.setTo(targetEPR);

    options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

    options.setUseSeparateListener(true);

    options.setAction("urn:echo");  // this is the action mapping we put within the service.xml    

   

    

    //Callback to handle the response

    Callback callback = new Callback() {

    public void onComplete(AsyncResult result) {

    System.out.println(result.getResponseEnvelope());

    }

    public void onError(Exception e) {

    e.printStackTrace();

    }

    };

    //Non-Blocking Invocation

    sender = new ServiceClient();

    sender.engageModule(new QName(Constants.MODULE_ADDRESSING));

    sender.setOptions(options);

    

    sender.sendReceiveNonBlocking(payload, callback);

    //Wait till the callback receives the response.

    while (!callback.isComplete()) {

    Thread.sleep(1000);

    }

    //Need to close the Client Side Listener.

    } catch (AxisFault axisFault) {

    axisFault.printStackTrace();

    } catch (Exception ex) {

    ex.printStackTrace();

    } finally {

    try {

    sender.finalizeInvoke();

    } catch (AxisFault axisFault) {

    //have to ignore this

    }

    }

    }

}



I wanted the result of the echo method call to be sent to the MyService service, and call the ping method. So I added the following

options.setReplyTo(new EndpointReference("http://localhost:8080/axis2/services/MyService"));

In the EchoNonBlockingDualClient so that the result of the echo call would be sent to MyService service, and changed the result of the echo method to be ping element (for calling the ping method of MyService).

Re: [Axis2] WS soap action question

[Eran Chinthaka]

Michele Mazzucco wrote:
> Hi Eran,
> 
> does AxisServlet run after the dispatchers? 

Its our http transport listener, in war case, and it runs before
dispatchers.

> I need to get the soap
> action in a handler running before the dispatcher phase: is there any
> way to get it? If so, how can I accomplish my goal?

messageContext.getSoapAction()

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: [Axis2] unable to turn off Axiom OMElement caching in client

[Ajith Ranabahu]

Hi Gary,
Hmm... this seems like an issue we need to look into. I'm not sure
whether the caching flag is useful any more (it is a left over from
one of the previous features AFAIK).

Just try this and see whether it works.

Just before return oe, add a statement
oe.setParent(null);

that should avoid any building of the tree

Ajith

On 6/29/06, Gordon, Gary <[EMAIL PROTECTED]> wrote:





(Reposting earlier message but with [Axis2] in subject line hoping someone
else will read this).



For a ServiceClient, you must produce an OMElement for the SOAP body, but I
don't see a way to write a client that doesn't build the whole OM object
tree for the payload.  I run out of memory for a large payload.  If I set
caching to false as follows, the Axiom code infinite loops:



public OMElement getPayload(InputStream is) throws XMLStreamException {

XMLInputFactory xif = XMLInputFactory.newInstance();

XMLStreamReader reader = xif.createXMLStreamReader(is);

StAXOMBuilder builder = new StAXOMBuilder(reader);

builder.setCache(false);

OMElement oe = builder.getDocumentElement();

return oe;

}



This is caused by the following sequence of calls in Axiom, wherein the
document element is never set to a non-null value because caching is on.



OMDocumentImpl:

public OMElement getOMDocumentElement() {

  while (documentElement == null) {

parserWrapper.next();

  }

  return documentElement;

}



StAXOMBuilder:

public int next() throws OMException {

  try {

if (done) {

  throw new OMException();

}

int token = parser.next();

if (!cache) {

  return token;

}



..etc.



Now if I comment out the call to turn off caching, Axiom merrily goes along
and builds the entire OM tree, so I run out of memory for large documents.
This is because



OMElement result = sender.sendReceive(payload);



eventually calls:

ServiceClient.fillSOAPEnvelope()



which eventually leads to:

OMElementImpl.detach();



The detach() causes the whole tree to be rendered as OMObjects.  For a
similar server-side question that was asked, the Axis person suggested
looking at the OMDatasource test code, but looking at this seemed to yield
nothing relevant unless I'm missing something.



Any suggestions on how to efficiently handle a large client-side payload
using Axiom?  Is this a bug that should be submitted?





Gary Gordon







Gary Gordon

R&D Fellow

Software AG, Inc.





--
Ajith Ranabahu

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

Re: [Axis2] WS soap action question

[Michele Mazzucco]

Hi Eran,

does AxisServlet run after the dispatchers? I need to get the soap
action in a handler running before the dispatcher phase: is there any
way to get it? If so, how can I accomplish my goal?

Thanks,
Michele

Michele

Eran Chinthaka wrote:
> Michele Mazzucco wrote:
>> Hi all,
>>
>> how, 
> 
> Read HTTP headers and SOAP Action header.
> 
>> when 
> 
> Whenever message comes to the engine.
> 
>> (and where) 
> 
> AxisServlet.
> 
> -- Chinthaka
> 

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

Re: cannot generate axis2 client stubs

[Ajith Ranabahu]

Hi,
is the adb-codegen module in class path

Ajith

On 6/29/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:



Hi,

I have just found out what the problem was : I had added an extra space on
the command line with:
WSDL2Java.bat -uri
http://localhost.urssaf.fr:8080/axis2/services/PojoDao?wsdl
-o c:\axis2bis\bin

Now I get a different stack trace (maybe easier to fix?). (PojoDao is
another web service)

Thanks for helping


Using AXIS2_HOME:   C:\axis2bis
Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException:
java.lang.ClassNotFoundException:
org.apache.axis2.schema.ExtensionUtility
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235)

at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.ClassNotFoundException: org.apa
che.axis2.schema.ExtensionUtility
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:52)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:188)
... 2 more
Caused by: java.lang.ClassNotFoundException:
org.apache.axis2.schema.ExtensionUt
ility
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:44)
... 3 more




- Original Message 
From: Kinichiro Inoguchi <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>
Sent: Thursday, June 29, 2006 1:35:10 PM
Subject: Re: cannot generate axis2 client stubs

Hi Nicolas,

could you post your service aar file ?

Regards,
kinichiro

--- Nicolas Urien <[EMAIL PROTECTED]> wrote:

> Hi Kinichiro,
>
> No it has parameters :
>
> public String echo(String value) {
> return value;
> }
>
> cheers
>
>   Nicolas Urien
>
> Mobile phone : +33-6 75 77 15 42
>
>  Victory favors those who take pains
>
>
>
>
>
>
> - Original Message 
> From: Kinichiro Inoguchi <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Wednesday, June 28, 2006 8:19:13 PM
> Subject: Re: cannot generate axis2 client stubs
>
> Nicolas,
>
> Does your service class method have no in/out parameter, like this ?
>
> public void echo () {
> System.out.println("hello world");
> }
>
>
> --- Nicolas Urien <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > I have successfully deployed a very simple aar archive ("hello
> > world") into my axis tomcat server.
> > I started from an implementation class and so I didn't write any
> wsdl
> > file.
> >
> > I cannot generate the axis2 client stubs. Here is the exception
> > I get (The entity "nbsp" was referenced, but not declared.) when
> > executing :
> >
> > WSDL2Java.bat -uri
http://localhost.urssaf.fr:8080/axis2/services/
> > SimpleService?wsdl -o c:\axis2bis\bin\
> >
> > Using AXIS2_HOME:   C:\axis2bis
> > Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException
> > : Error parsing WSDL
> > at
> >
>
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
> > ionEngine.java:125)
> > at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
> > at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> > Caused by: WSDLException: faultCode=PARSER_ERROR: Parser SAX Error:
> > Fatal Error:
> >  URI=http://localhost.urssaf.fr:8080/axis2/services/
Line=32: The
> > entity "nbsp"
> > was referenced, but not declared.: org.xml.sax.SAXException: Fatal
> > Error: URI=ht
> > tp://localhost.urssaf.fr:8080/axis2/services/ Line=32:
The entity
> > "nbsp" was referenced, but not declared.
> > at
> >
>
org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils
> > .java:361)
> > at
> >
>
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalErro
> > r(ErrorHandlerWrapper.java:218)
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> > XMLErrorReporter.java:386)
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> > XMLErrorReporter.java:316)
> > at
> >
>
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(X
> > MLScanner.java:1438)
> > at
>

[Axis2] unable to turn off Axiom OMElement caching in client

[Gordon, Gary]

(Reposting earlier message but with [Axis2] in subject line hoping
someone else will read this).

 

For a ServiceClient, you must produce an OMElement for the
SOAP body, but I don’t see a way to write a client that doesn’t
build the whole OM object tree for the
payload.  I run out of memory for a large payload.  If I set caching to
false as follows, the Axiom code infinite loops:

 

public OMElement getPayload(InputStream is) throws
XMLStreamException {

    XMLInputFactory xif =
XMLInputFactory.newInstance();

    XMLStreamReader reader =
xif.createXMLStreamReader(is);

    StAXOMBuilder builder = new
StAXOMBuilder(reader);

    builder.setCache(false);

    OMElement oe =
builder.getDocumentElement();

    return oe;

}

 

This is caused by the following sequence of calls in Axiom,
wherein the document element is never set to a non-null value because caching
is on.

 

OMDocumentImpl:

public OMElement getOMDocumentElement() {

  while (documentElement == null) {

    parserWrapper.next();

  }

  return documentElement;

}

 

StAXOMBuilder:

public int next() throws OMException {

  try {

    if (done) {

  throw new OMException();

    }

    int token = parser.next();

    if (!cache) {

  return token;

    }

 

    ..etc.

 

Now if I comment out the call to turn off caching, Axiom
merrily goes along and builds the entire OM
tree, so I run out of memory for large documents.  This is because

 

OMElement result = sender.sendReceive(payload);

 

eventually calls:

ServiceClient.fillSOAPEnvelope()

 

which eventually leads to:

OMElementImpl.detach();

 

The detach() causes the whole tree to be rendered as
OMObjects.  For a similar server-side question that was asked, the Axis
person suggested looking at the OMDatasource test code, but looking at this
seemed to yield nothing relevant unless I’m missing something.

 

Any suggestions on how to efficiently handle a large
client-side payload using Axiom?  Is this a bug that should be submitted?

 

 

Gary Gordon

 

 

 

Gary Gordon

R&D Fellow

Software AG, Inc.

 

Re: [Axis2] WS soap action question

[Eran Chinthaka]

Michele Mazzucco wrote:
> Hi all,
> 
> how, 

Read HTTP headers and SOAP Action header.

> when 

Whenever message comes to the engine.

> (and where) 

AxisServlet.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: ReplyTo is not working

[Eran Chinthaka]

Munir Badir wrote:

> As a result I expected that the echo method would call the ping method,
> but it didn’t. Can anyone help?

I'm still confused in understanding the question. If you can explain a
bit with your code, it will be helpful in answering this question.


Thanks,
Chinthaka




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] rest question

[Anne Thomas Manes]

Here's a useful guide to understanding REST:http://prescod.net/rest/Steps_to_extreme.html AnneOn 6/27/06, 
Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
If you have two methods, then you must have two endpoints. Otherwise, it isn't RESTful.Anne
On 6/27/06, 
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Hi Anne I am sorry - I probably didnt get the answer.I have a service class that has 2 methods -public OMElement dothis(OMElement om1)public OMElement dothat(OMElement om2)Now for this service there will be one REST endpoint address - right?
then my question is given my payload xml - how does axis decide whichmethod to invoke in my service?I didnt quite get what u meant by"You have only one function associated with POST to a specific URL"
Are u saying that my service can have only one method for it to be restenabled?thanksAnamitra "Anne Thomas Manes" <

[EMAIL PROTECTED]  To m>
axis-user@ws.apache.orgcc
 06/27/2006 01:17 PMSubject   Re: [Axis2] rest question Please respond to

 [EMAIL PROTECTED]  
he.orgWhen using a RESTful service, *POST* is your method. You have only one
function associated with POST to a specific URL. If you have a service thatexposes methods other than GET, POST, PUT, or DELETE, then it isn'tRESTful.AnneOn 6/27/06, 

[EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:  Hi
  As per the axis2 doc it seems that if I want to do a POST rest service -
  the only way axis runtime would detect which method to delegate the call  to  is from the name of the top level element in the http message body XML -  right?  I have a service whose method definition is like
  public OMElement dothis(OMElelemt payload)  When I do the SOAP client  invoke I send the soap action as urn:dothis  and  my payload top element does not match the method name - This works fine

  with axis2.  But now if I have to do REST call and not have the root element as method  name - how can I acheive that using rest? [I presume soap action is not  going to work here or is it?]  thanks
  Anamitra  -  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: cannot generate axis2 client stubs

[Nicolas Urien]

Hi,I have just found out what the problem was : I had added an extra space on the command line with:WSDL2Java.bat -uri http://localhost.urssaf.fr:8080/axis2/services/PojoDao?wsdl -o c:\axis2bis\binNow I get a different stack trace (maybe easier to fix?). (PojoDao is another web service)Thanks for helpingUsing AXIS2_HOME:   C:\axis2bisUsing JAVA_HOME:    C:\Program Files\Java\jdk1.5.0_06Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.ClassNotFoundException:
 org.apache.axis2.schema.ExtensionUtility    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:235)    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.axis2.schema.ExtensionUtility    at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:52)    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:188)    ... 2 moreCaused by: java.lang.ClassNotFoundException:
 org.apache.axis2.schema.ExtensionUtility    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)    at java.security.AccessController.doPrivileged(Native Method)    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)    at java.lang.Class.forName0(Native Method)    at
 java.lang.Class.forName(Class.java:164)    at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:44)    ... 3 more- Original Message From: Kinichiro Inoguchi <[EMAIL PROTECTED]>To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>Sent: Thursday, June 29, 2006 1:35:10 PMSubject: Re: cannot generate axis2 client stubsHi Nicolas,could you post your service aar file ?Regards,kinichiro--- Nicolas Urien <[EMAIL PROTECTED]> wrote:> Hi Kinichiro,> > No it has parameters :> > public String echo(String value) {> return value;> }>
 > cheers>  >   Nicolas Urien > > Mobile phone : +33-6 75 77 15 42>   >  Victory favors those who take pains> > > > > > > - Original Message > From: Kinichiro Inoguchi <[EMAIL PROTECTED]>> To: axis-user@ws.apache.org> Sent: Wednesday, June 28, 2006 8:19:13 PM> Subject: Re: cannot generate axis2 client stubs> > Nicolas,> > Does your service class method have no in/out parameter, like this ?> > public void echo () {> System.out.println("hello world");> }> > > --- Nicolas Urien <[EMAIL PROTECTED]> wrote:> > > Hello,> > > > I have successfully deployed a very simple aar archive ("hello> > world") into my axis tomcat server.> > I
 started from an implementation class and so I didn't write any> wsdl> > file.> > > > I cannot generate the axis2 client stubs. Here is the exception > > I get (The entity "nbsp" was referenced, but not declared.) when> > executing :> > > > WSDL2Java.bat -uri http://localhost.urssaf.fr:8080/axis2/services/> > SimpleService?wsdl -o c:\axis2bis\bin\> > > > Using AXIS2_HOME:   C:\axis2bis> > Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06> > Exception in thread "main"> > org.apache.axis2.wsdl.codegen.CodeGenerationException> > : Error parsing WSDL> > at> >> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat> >
 ionEngine.java:125)> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > Caused by: WSDLException: faultCode=PARSER_ERROR: Parser SAX Error:> > Fatal Error:> >  URI=http://localhost.urssaf.fr:8080/axis2/services/ Line=32: The> > entity "nbsp"> > was referenced, but not declared.: org.xml.sax.SAXException: Fatal> > Error: URI=ht> > tp://localhost.urssaf.fr:8080/axis2/services/ Line=32: The entity> > "nbsp" was referenced, but not declared.> > at> >> org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils> > .java:361)>
 > at> >> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalErro> > r(ErrorHandlerWrapper.java:218)> > at> >> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(> > XMLErrorReporter.java:386)> > at> >> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(> > XMLErrorReporter.java:316)> > at> >> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(X> > MLScanner.java:1438)> > at> >> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp> >
 l.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1332)> > at> >> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScanner

Re: [Axis 2]How can I check that a handler is executed?

[Fabien Couble]

Nothing has changed! The file is not created!!
That mean that the handler is not executed!
I really don't understand
Can the problem be caused by something else?

Fabien
- Original Message - 
From: "Deepal Jayasinghe" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, June 29, 2006 12:33 PM
Subject: Re: [Axis 2]How can I check that a handler is executed?


there is small problem , you need to modify your code in the invoke method 
;

try {
   FileWriter fw = new FileWriter("toto.txt");
   fw.write("Test");
   fw.flush();
   fw.close();
   } catch (IOException e) {
   System.out.println(e.getStackTrace());
   }


Fabien Couble wrote:



I tried to create the file in the invoke method. But no result...
Actually, a file should have been created in the module directory of
Axis2 but nothing appeared!


That is mean your handler is get called , dont worry it is working !!


This is the code of my handler!!

package userguide.loggingmodule;

import org.apache.axis2.AxisFault;
import org.apache.axis2.context.MessageContext;
import org.apache.axis2.engine.Handler;
import org.apache.axis2.handlers.AbstractHandler;
import org.apache.commons.logging.Log;



import org.apache.commons.logging.LogFactory;
import java.io.*;

import javax.xml.namespace.QName;

public class LogHandler extends AbstractHandler implements Handler {
private static final Log log = LogFactory.getLog(LogHandler.class);
   private QName name;

   public QName getName() {
   return name;
   }

   public void invoke(MessageContext msgContext) throws AxisFault {
System.out.println("Invoke Method!");

try{
 FileWriter fw = new FileWriter("toto.txt");
 fw.write("Test");
}catch(IOException  e){
 System.out.println(e.getStackTrace());
}


   log.info(msgContext.getEnvelope().toString());
   }

   public void revoke(MessageContext msgContext) {
   log.info(msgContext.getEnvelope().toString());
   }

   public void setName(QName name) {
   this.name = name;
   }

}

I don't know what to do!!
What do you think about this?

Fabien





- Original Message - From: "Deepal Jayasinghe"
<[EMAIL PROTECTED]>
To: 
Sent: Thursday, June 29, 2006 10:53 AM
Subject: Re: [Axis 2]How can I check that a handler is executed?



hmm , as I can see everything is OK .
I think this is smt to do with logging properties, can you please try
the following
- juts try to create a file inside invoke method of the handler and see
its working :)
.


Fabien Couble wrote:



Hi Deepal,
As you said, I can see my module via the web admin console. The
phaseName I have added is loggingPhase.
This is what the web console return me:
View Operation Specific Chains
Operation Name : echo
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
Operation Name : ping
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
So I think, everything is allright.
I engaged this module by adding a module ref to the service.xml file
of my service.
However, when I want to test that my module is executed, I can't see
anything!!
An idea...??

Cheers
Fabien



- Original Message - From: "Deepal Jayasinghe"
<[EMAIL PROTECTED]>
To: 
Sent: Thursday, June 29, 2006 9:53 AM
Subject: Re: [Axis 2]How can I check that a handler is executed?



Hi Fabien;

Fabien Couble wrote:


Hello,

I'm trying to engage a module in the Axis2 chain.
Apparently, the module is well engaged in a service (I checked the
Administration console) but I'd like to be sure that the handler of
the module is executed!!




If you engage the module correctly , using web admin console you
should
be able to see your handler in the handler chain.


To do that, I put a "System.out.println" command in the method invoke
of the handler but nothing... (in the log of the Tomcat server)
That is why, I'd like to know if it is a good method to check that
or not!




How do you engage a module , using web admin console or adding module
ref to services.xml ?


If not, how can I do?




--
Thanks,
Deepal

~Future is Open~

ReplyTo exmaple (please help)

[Munir Badir]

Hi,

 

Is there an example for calling a service on HTTP and get
response back via HTTP using the ReplyTo node in WS-Addressing.

 

Thanks,

Munir





__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

Compatability of wss4j with XWS-Security implementation WS-security

[Kashif Saleem]

Hi All,
   I am using axis1.3 for calling couple of secure web-service which are 
secured using JWSDP2.0 which uses XWS-Security implementation.
   But as axis1.3 uses wss4j implementation so I am just wondering if it 
possible to communicate with secure services which uses JWSDP2.0.

I would really appreciate if someone could shed light on it.Thanks.


Kind Regards
Kashif

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

ReplyTo is not working

[Munir Badir]

Hi,

I’m trying to test the ReplyTo option in the WS
addressing. 

I tried to make the echo method result be sent to the ping
method of the Myservice service.

For doing it I took the EchoNonBlockingDualClient example in
AXIS2 \samples\userguide and set the replyTo option by adding the following:

 

options.setReplyTo(new EndpointReference("http://localhost:8080/axis2/services/MyService"));

 

And I changed the echo method in MyService to return Ping
OMElement 

 

public OMElement echo(OMElement element) throws
XMLStreamException {

    OMElement o = getPingOMElement();

    return o;

    }

 

As a result I expected that the echo method would call the
ping method, but it didn’t. Can anyone help?

 

Thanks,

Munir





__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

How to write Security Environment handler

[Kashif Saleem]

Hi All,
   I am calling couple of secure web-service.So before sending and 
receiving the information to and from the services,I need to sign and encrypt 
the information using client and server certificates stored in client and 
server keystore respectively.For that reason I need to add a handler to the 
Axis handler chain to implement this.I search  on the web for writing the 
security environment handler that would sign and encrypt or decrypt etc but I 
could not find any information related to that.So I would really appreciate if 
someone could provide me the code snippets or provide pointers for how to  
write  security environment handler.Thanks.


Kind Regards
Kashif

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

[Axis2] WS soap action question

[Michele Mazzucco]

Hi all,

how, when (and where) is the WS soap action retrieved?


Thanks,
Michele

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

Re: cannot generate axis2 client stubs

[Kinichiro Inoguchi]

Hi Nicolas,

could you post your service aar file ?

Regards,
kinichiro

--- Nicolas Urien <[EMAIL PROTECTED]> wrote:

> Hi Kinichiro,
> 
> No it has parameters :
> 
> public String echo(String value) {
> return value;
> }
> 
> cheers
>  
>   Nicolas Urien 
> 
> Mobile phone : +33-6 75 77 15 42
>   
>  Victory favors those who take pains
> 
> 
> 
> 
> 
> 
> - Original Message 
> From: Kinichiro Inoguchi <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Wednesday, June 28, 2006 8:19:13 PM
> Subject: Re: cannot generate axis2 client stubs
> 
> Nicolas,
> 
> Does your service class method have no in/out parameter, like this ?
> 
> public void echo () {
> System.out.println("hello world");
> }
> 
> 
> --- Nicolas Urien <[EMAIL PROTECTED]> wrote:
> 
> > Hello,
> > 
> > I have successfully deployed a very simple aar archive ("hello
> > world") into my axis tomcat server.
> > I started from an implementation class and so I didn't write any
> wsdl
> > file.
> > 
> > I cannot generate the axis2 client stubs. Here is the exception 
> > I get (The entity "nbsp" was referenced, but not declared.) when
> > executing :
> > 
> > WSDL2Java.bat -uri http://localhost.urssaf.fr:8080/axis2/services/
> > SimpleService?wsdl -o c:\axis2bis\bin\
> > 
> > Using AXIS2_HOME:   C:\axis2bis
> > Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_06
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException
> > : Error parsing WSDL
> > at
> >
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
> > ionEngine.java:125)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> > Caused by: WSDLException: faultCode=PARSER_ERROR: Parser SAX Error:
> > Fatal Error:
> >  URI=http://localhost.urssaf.fr:8080/axis2/services/ Line=32: The
> > entity "nbsp"
> > was referenced, but not declared.: org.xml.sax.SAXException: Fatal
> > Error: URI=ht
> > tp://localhost.urssaf.fr:8080/axis2/services/ Line=32: The entity
> > "nbsp" was referenced, but not declared.
> > at
> >
> org.apache.axis2.util.XMLUtils$ParserErrorHandler.fatalError(XMLUtils
> > .java:361)
> > at
> >
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalErro
> > r(ErrorHandlerWrapper.java:218)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> > XMLErrorReporter.java:386)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> > XMLErrorReporter.java:316)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(X
> > MLScanner.java:1438)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> > l.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1332)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> >
>
l$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1756)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> > l.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
> > ML11Configuration.java:834)
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
> > ML11Configuration.java:764)
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.
> > java:148)
> > at
> >
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.
> > java:250)
> > at
> >
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Doc
> > umentBuilderImpl.java:292)
> > at
> > org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:178)
> > at
> > org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:223)
> > at
> > org.apache.axis2.util.XMLUtils.newDocument(XMLUtils.java:206)
> > at
> >
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(
> > CodeGenerationEngine.java:274)
> > at
> >
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
> > ionEngine.java:108)
> > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
> > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> > 
> > at
> >
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(
> > CodeGenerationEngine.java:280)
> > at
> >
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
> > ionEngine.java:108)
> > ... 2 more
> > C:\axis2bis\bin>WSDL2Java.bat -uri
> > http://localhost.urssaf.fr:8080/axis2/service
> > s/ SimpleService?wsdl -o c:\axis2bis\bin\
> > 
> > 
> > What should I do please??
> > 
> > cheers
> > 
> > Extract of the generated WSDL file:
> > 
> >  http://schemas.xmlsoap.org/wsdl/";;
> > xmlns:axis2="http://ws.apache.org/axis2";; 
> > xm

Re: Error reading data stream: Error in MIME data stream, start boundary not found

[Stromblad]

Hi again,I've realized that I can send a DataHandler from the client to the server, but when I try sending a DataHandler from the server to the client i get that error on linux, and this one on windows:org.apache.axis.client.Call
 invokeGRAVE: Exception:java.lang.RuntimeException: javax.mail.MessagingException: Error in input stream;  nested exception is:    java.io.IOException: End of stream encountered before final boundary marker.
Using tcpmon i get the soap message returned from the server:HTTP/1.1 200 OKServer: Apache-Coyote/1.1Set-Cookie: JSESSIONID=16FE8EDA331F865F18B328439A8BCF44; Path=/axisContent-Type: multipart/related; type="text/xml"; start="<9069F26CAF4DFDB10496822D71C6F12B>";     boundary="=_Part_5_28730188.1151580330109"Date: Thu, 29 Jun 2006 11:25:30 GMTConnection: close--=_Part_5_28730188.1151580330109Content-Type: text/xml; charset=UTF-8Content-Transfer-Encoding: binaryContent-Id: 
   <9069F26CAF4DFDB10496822D71C6F12B>   
http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">       http://schemas.xmlsoap.org/soap/encoding/
" xmlns:ns1="urn:lomService">  
http://xml.apache.org/xml-soap"/>        --=_Part_5_28730188.1151580330109Content-Type: application/octet-stream
Content-Transfer-Encoding: binaryContent-Id:  <9B09705100746E248D3E8937986DBB39>comparing this message with the one sent from the client i realize that there is a MIME boundary missing on the end of the response from the server. How can i fix this?
Thanks in advance,Stromblad

Re: [Axis2 current SVN 6/28] services.list needed ?

[Kinichiro Inoguchi]

Deepal,

I am sorry, it was my fault.
Current SVN version also works as before.
I could deploy my service with just dropping it.

Regards,
kinichiro

--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

> Hi Kinichiro;
> pls see my comment below;
> 
> 
> Kinichiro Inoguchi wrote:
> 
> >Hi,Is services.list in services folder needed at current SVN ?
> >  
> >
> No , you need that only if you are going to use un-expand war case .
> 
> >To add new service to TOMCAT_HOME/webapps/axis2/WEB-INF/services/ , 
> >I just dropped my aar file to this folder, before.
> >But with current SVN build version of Axis2,
> >I need to add aar file name to services.list, after dropping aar
> file.
> >  
> >
> You do not need to modify anything , just drop the aar it will work.
> 
> >New feature "module service" affects this ?
> >  
> >
> Nope;
> 
> >Regards,
> >kinichiro
> >
> >__
> >Do You Yahoo!?
> >Tired of spam?  Yahoo! Mail has the best spam protection around 
> >http://mail.yahoo.com 
> >
>
>-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >  
> >
> 
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~ 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

RE: sending soap messages asynchronously

[Phani Sekhar]

Thank you very much for ur response ...
We want the Axis server to first initiate and send one-way messages to the
Axis client.
Can we configure the Axis2 server in such a way ???

~ Phani Sekhar



-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 29, 2006 1:01 PM
To: axis-user@ws.apache.org
Subject: Re: Re : sending soap messages asynchronously

Axis2 support asynchronous invocation

Phani Sekhar wrote:

> Hi all,
>
> We are implementing NETCONF on SOAP over HTTP. We are using Axis.
>
> We require the Axis web service to send some soap messages
> asynchronously to the Axis client without any initiation.
>
> Ofcourse for the first time, we can register the client at the server.
> We are trying to implement something similar to the snmp
> traps/notifications.
>
> Is is possible to do this using Axis Does Axis support
> asynchronous messaging???
>
>
>
> Please help me.
>
>
>
> Thanks in advance
>
> Phani Sekhar
>
>
>
> -Original Message-
> *From:* Phani Sekhar [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, June 21, 2006 12:47 PM
> *To:* axis-user@ws.apache.org
> *Subject:* sending asynchronous soap messages
>
>
>
> Hi,
>
> Is there any way to send asynchronous soap messages from a webservice
> in Axis, something similar to snmp notifications ???
>
>
>
> Thanks in Advance
>
> Phani Sekhar
>

--
Thanks,
Deepal

~Future is Open~



-
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: Min lentgh and max length of an input string parameter

[Roy]

Hello,     I have edited the wsdl with this field in a string element:                   Is any way AXIS to validate automatically this maxExclusive and throw an exception if this value exceeds the limit?     Regards,  Roy  Anne Thomas Manes <[EMAIL PROTECTED]> έγραψε:  You need to edit the WSDL file to add this type of restriction.  On 6/28/06, Roy <[EMAIL PROTECTED]> wrote: Hello all,Does anyone know a way to declare max and min size of a string in a input parameter in a wsdl generated with the Java2WSDL tool? Can i declare something in the deploy.wsdd file?Thanks,  RoyΧρησιμοποιείτε Yahoo!Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το
 Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr 

Re: [Axis 2]How can I check that a handler is executed?

[Deepal Jayasinghe]

there is small problem , you need to modify your code in the invoke method ;
try {
FileWriter fw = new FileWriter("toto.txt");
fw.write("Test");
fw.flush();
fw.close();
} catch (IOException e) {
System.out.println(e.getStackTrace());
}


Fabien Couble wrote:

>
> I tried to create the file in the invoke method. But no result...
> Actually, a file should have been created in the module directory of
> Axis2 but nothing appeared!

That is mean your handler is get called , dont worry it is working !!

> This is the code of my handler!!
>
> package userguide.loggingmodule;
>
> import org.apache.axis2.AxisFault;
> import org.apache.axis2.context.MessageContext;
> import org.apache.axis2.engine.Handler;
> import org.apache.axis2.handlers.AbstractHandler;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> import java.io.*;
>
> import javax.xml.namespace.QName;
>
> public class LogHandler extends AbstractHandler implements Handler {
> private static final Log log = LogFactory.getLog(LogHandler.class);
>private QName name;
>
>public QName getName() {
>return name;
>}
>
>public void invoke(MessageContext msgContext) throws AxisFault {
> System.out.println("Invoke Method!");
>
> try{
>  FileWriter fw = new FileWriter("toto.txt");
>  fw.write("Test");
> }catch(IOException  e){
>  System.out.println(e.getStackTrace());
> }
>
>
>log.info(msgContext.getEnvelope().toString());
>}
>
>public void revoke(MessageContext msgContext) {
>log.info(msgContext.getEnvelope().toString());
>}
>
>public void setName(QName name) {
>this.name = name;
>}
>
> }
>
> I don't know what to do!!
> What do you think about this?
>
> Fabien
>
>
>
>
>
> - Original Message - From: "Deepal Jayasinghe"
> <[EMAIL PROTECTED]>
> To: 
> Sent: Thursday, June 29, 2006 10:53 AM
> Subject: Re: [Axis 2]How can I check that a handler is executed?
>
>
>> hmm , as I can see everything is OK .
>> I think this is smt to do with logging properties, can you please try
>> the following
>> - juts try to create a file inside invoke method of the handler and see
>> its working :)
>> .
>>
>>
>> Fabien Couble wrote:
>>
>>>
>>> Hi Deepal,
>>> As you said, I can see my module via the web admin console. The
>>> phaseName I have added is loggingPhase.
>>> This is what the web console return me:
>>> View Operation Specific Chains
>>> Operation Name : echo
>>> In Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : InFlowLogHandler
>>>  b.. Phase Name : OperationInPhase
>>> In Fault Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : FaultInFlowLogHandler
>>>  b.. Phase Name : OperationInFaultPhase
>>> Out Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : OutFlowLogHandler
>>>  b.. Phase Name : OperationOutPhase
>>> Out Fault Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : FaultOutFlowLogHandler
>>>  b.. Phase Name : OperationOutFaultPhase
>>> Operation Name : ping
>>> In Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : InFlowLogHandler
>>>  b.. Phase Name : OperationInPhase
>>> In Fault Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : FaultInFlowLogHandler
>>>  b.. Phase Name : OperationInFaultPhase
>>> Out Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : OutFlowLogHandler
>>>  b.. Phase Name : OperationOutPhase
>>> Out Fault Flow
>>>  a.. Phase Name : loggingPhase
>>>a.. Handler Name : FaultOutFlowLogHandler
>>>  b.. Phase Name : OperationOutFaultPhase
>>> So I think, everything is allright.
>>> I engaged this module by adding a module ref to the service.xml file
>>> of my service.
>>> However, when I want to test that my module is executed, I can't see
>>> anything!!
>>> An idea...??
>>>
>>> Cheers
>>> Fabien
>>>
>>>
>>>
>>> - Original Message - From: "Deepal Jayasinghe"
>>> <[EMAIL PROTECTED]>
>>> To: 
>>> Sent: Thursday, June 29, 2006 9:53 AM
>>> Subject: Re: [Axis 2]How can I check that a handler is executed?
>>>
>>>
 Hi Fabien;

 Fabien Couble wrote:

> Hello,
>
> I'm trying to engage a module in the Axis2 chain.
> Apparently, the module is well engaged in a service (I checked the
> Administration console) but I'd like to be sure that the handler of
> the module is executed!!



 If you engage the module correctly , using web admin console you
 should
 be able to see your handler in the handler chain.

> To do that, I put a "System.out.println" command in the method invoke
> of the handler but nothing... (in the log of the Tomcat server)
> That is why, I'd like to know if it is a good method to check that
> or not!



 How do you engage a module , using web admin console or adding module
 ref to services.xml ?

> If not, how 

Re: WSDL2Java and one-way binding

[Dies Koper]

Hello Bonjamin,

There is a tag in the WSDD to set the WSDL file, I believe "".
If you specify it, that file will be returned by ?wsdl instead.
No need to touch the skeletons.

Regards,
Dies

Benjamin Fan wrote:

I've given up on service-generated-WSDL - I hand-cut/validate WSDL and use
WSDL2Java to generate both the server-side skeleton and the client side
stubs. I haven't done it yet but I'm told its straight forward to modify 
the

generated code to return static WSDL files rather than genertaing WSDL on
the fly. ANy chance of you manually maintaining the generated skeleton? 
This

is what I'm going to have to do...

On 6/29/06, John Mani <[EMAIL PROTECTED]> wrote:


Hi all

Any comments on the below issue ? I'd expect this to be a common scenario
.. so am I
misunderstanding something ?

thanx
-john



From: John Mani [mailto:[EMAIL PROTECTED]
Sent: Tue 6/27/2006 6:53 PM
To: axis-user@ws.apache.org
Subject: WSDL2Java and one-way binding


I'm using Axis 1.4 WSDL2Java to generate skeletons for a webservice 
from a

WSDL doc.

The source WSDL (generated by .NET) uses one-way binding - it just
specifies a
 element, no  element.

However, the generated skeleton code seems to be including a response to
the request.
This is proven by checking the deployed skeleton's WSDL (deployed in
tomcat, using
the axis war) - it contains   and  messages.
Also, when
I run the .NET client against the deployed skeleton, the client 
complaints

about the
unexpected entity body in the response.

Any comments/help ?

thanx
-jm



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

Re: [Axis v1.4] deploying with Basic Authentication turned on?

[Artur Kraft]

Is this a common issue or am I doing something basically wrong?
On the axis-user mailinglist (also checked axis-dev and tomcat-user) I 
found a few other posts with suggestions, but none really apply to me. 
Shouldn't this be fixed quite simple or do I have to code something to 
get it to work?


kind regards
Artur



Artur Kraft wrote:

Hello,

in Tomcat I turned on BASIC Authentication to protect the use of all 
axis services. Since then I always get a HTTP-Error 401/Unauthorized. 
How can I provide username and password to deploy again to axis?


I tried the -uUserName -wPassword parameters, but they seem to belong 
rather to the axis-file "user.lst" than providing the tomcat access 
user data.


Any suggestions?


My environment:
Axis v1.4
Tomcat v5.5.17
Java v1.5.0_06
WinXP


kind regards,
Artur

-
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: [Axis 2]How can I check that a handler is executed?

[Fabien Couble]

I tried to create the file in the invoke method. But no result...
Actually, a file should have been created in the module directory of Axis2 
but nothing appeared!

This is the code of my handler!!

package userguide.loggingmodule;

import org.apache.axis2.AxisFault;
import org.apache.axis2.context.MessageContext;
import org.apache.axis2.engine.Handler;
import org.apache.axis2.handlers.AbstractHandler;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import java.io.*;

import javax.xml.namespace.QName;

public class LogHandler extends AbstractHandler implements Handler {
private static final Log log = LogFactory.getLog(LogHandler.class);
   private QName name;

   public QName getName() {
   return name;
   }

   public void invoke(MessageContext msgContext) throws AxisFault {
System.out.println("Invoke Method!");

try{
 FileWriter fw = new FileWriter("toto.txt");
 fw.write("Test");
}catch(IOException  e){
 System.out.println(e.getStackTrace());
}


   log.info(msgContext.getEnvelope().toString());
   }

   public void revoke(MessageContext msgContext) {
   log.info(msgContext.getEnvelope().toString());
   }

   public void setName(QName name) {
   this.name = name;
   }

}

I don't know what to do!!
What do you think about this?

Fabien





- Original Message - 
From: "Deepal Jayasinghe" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, June 29, 2006 10:53 AM
Subject: Re: [Axis 2]How can I check that a handler is executed?



hmm , as I can see everything is OK .
I think this is smt to do with logging properties, can you please try
the following
- juts try to create a file inside invoke method of the handler and see
its working :)
.


Fabien Couble wrote:



Hi Deepal,
As you said, I can see my module via the web admin console. The
phaseName I have added is loggingPhase.
This is what the web console return me:
View Operation Specific Chains
Operation Name : echo
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
Operation Name : ping
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
So I think, everything is allright.
I engaged this module by adding a module ref to the service.xml file
of my service.
However, when I want to test that my module is executed, I can't see
anything!!
An idea...??

Cheers
Fabien



- Original Message - From: "Deepal Jayasinghe"
<[EMAIL PROTECTED]>
To: 
Sent: Thursday, June 29, 2006 9:53 AM
Subject: Re: [Axis 2]How can I check that a handler is executed?



Hi Fabien;

Fabien Couble wrote:


Hello,

I'm trying to engage a module in the Axis2 chain.
Apparently, the module is well engaged in a service (I checked the
Administration console) but I'd like to be sure that the handler of
the module is executed!!



If you engage the module correctly , using web admin console you should
be able to see your handler in the handler chain.


To do that, I put a "System.out.println" command in the method invoke
of the handler but nothing... (in the log of the Tomcat server)
That is why, I'd like to know if it is a good method to check that
or not!



How do you engage a module , using web admin console or adding module
ref to services.xml ?


If not, how can I do?




--
Thanks,
Deepal

~Future is Open~



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




This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient,  you are not authorized to read, print,
retain, copy, disseminate,  distribute, or use this message or any
part thereof. If you receive this  message in error, please notify the
sender immediately and delete all  copies of this message.


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

[Axis2] REST vs. SOAP and enableREST

[heikki]

Hi there,it seems I'm not quite getting how Axis2 handles REST vs. SOAP ..From the documentation I had gathered that this element in the server side's axis2.xml :true
should cause REST handling of incoming messages. I had therefore also assumed that setting this parameter to false, or removing it altogether, would cause Axis2 to handle incoming messages as SOAP -- which would mean (I thought) discarding the envelope before binding the payload to the type expected in the SEI. 
However, I see no difference in behaviour at all ! Whether I set this parameter to false or true or take it out; Axis2 keeps handling messages as REST messages ! So if I have a client sending SOAP (instead of REST) messages, the SOAP message does not get processed correctly, as it's trying to bind the SOAP:Envelope type to the type expected in the SEI -- it does this even though the enableREST param is false !
I have now modified the generated MyServiceMessageReceiverInOut such that its fromOM() method checks for SOAP-ness of the param and if so, it discards the SOAP envelope before trying to bind the payload. This way it now correctly handles both SOAP and REST messages coming in. But I have a distinct feeling that this is fishy; that I shouldn't have to do this; that I'm missing something here; and that the enableREST parameter setting should have some impact on how Axis2 behaves.
Anyone care to explain these matters ?thank you !Heikki Doeleman

Howto add schema definition of type to wsdl?

[Jansen Werner]

Hallo everybody,

I have a web service called ScheduleNotifyService. It has a single
operation called "scheduleNotify". This operation needs a parameter of
java type ScheduleMetaData. So I wrote a Serializer/Deserializer pair
with their corresponding factories. This works.

But: When I call my wsdl using ScheduleNotifyService?wsdl, it defines a
part 

 

without defining ScheduleMetaData in the document. Is it possible to
automatically include the definition for my java types somehow? Axis
could - i suppose - extract the definition from the serializer. Do I
need to manually include the definition?

I hope I made myself clear. :) If not, don't hesitate to ask for further
information ... :)

Greetings from Munich,

Werner Jansen


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

Re: [Axis2] [subclipse] check out Axis2 SVN source code

[Xinjun Chen]

Sorry, it is a typo. It is "trunk".


Regards,
Xinjun

On 6/29/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:

Hi,
"/repos/asf/webservices/axis2/truck/java'' -> shouldn't 'truck'
become "trunk" here? Seems to be a typo ?

On 6/29/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
> Forget to mention my system info:
> OS: Windows XP V5.1 SP1.
> Java: JDK1.4.2_11
> Eclipse: 3.1.1
> Subclipse: latest, 1.0.3
>
> By the way, I have already checkout Axis2 source code using
> TortoiseSVN, but why I cannot checkout Axis2 source code using
> Subclipse plugin? Is there any problem with Subclipse plugin? What's
> suggestions on this?
>
>
> Regards,
> Xinjun
>
> On 6/29/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I am trying to check out Axis2 SVN source code but failed.
> > I have installed subclipse plugin into my Eclipse following the
> > instruction at page
> > http://subclipse.tigris.org/install.html.
> >
> > However, when I try to create a new repository location
> > "http://svn.apache.org/repos/asf/webservices/axis2/trunk/java";, I get
> > the
> > following exception:
> >
> > Unable to Validate.
> > Error validating location:
> > "org.tigris.subversion.javahl.ClientException: RA layer request failed
> > svn:PROPFIND request failed on '/repos/asf/webservices/axis2/truck/java'
> > svn:PROPFIND of '/repos/asf/webservices/axis2/truck/java': could not
> > connect to server (http://svn.apache.org)"
> >
> > When trying to expand the tree. I get the error message:
> >
> > Folder " does not exist remotely.
> >
> >
> > I don't know how and where to run "svn co  axis2"
> > command. Please forgive me if the question is too trivial. "svn is not
> > an internal command"
> >
> > Could anyone who has successfully checked out Axis2 source code help me on 
this?
> >
> > Thanks.
> >
> >
> >
> > Regards,
> >
> > Xinjun
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Ajith Ranabahu

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




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

Re: [Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

And add "urn:" before it?

Michele

Michele Mazzucco wrote:
> Hi all,
> 
> I've got a handler running before the transport phase. How can I get the
>  WS addressing action there as the  element is created
> later? Is it enough to get the first element local name of the SOAP body?
> 
> Thanks,
> Michele
> 
> -
> 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]

[Axis2] How to access the soapAction from Handlers

[Michele Mazzucco]

Hi all,

I've got a handler running before the transport phase. How can I get the
 WS addressing action there as the  element is created
later? Is it enough to get the first element local name of the SOAP body?

Thanks,
Michele

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

Re: [Axis2] MTOM question

[Michele Mazzucco]

Hi Ajith,

I've got 2 machines, A and B. On A is running my handler (which runs
before the transport phase) while on B is running a service. When the
handler on A invokes the service on B, the replyTo field is set by Axis2
(B side) to
http://null:8080/axis2/services/annonService5978327/annonOutInOp. I hope
you'll agree with me that something does not work as expected.
Furthermore, server A is running on port 18080 while server B is running
on port 28080.

Any idea?

Thanks,
Michele

Ajith Ranabahu wrote:
> Hi Michele,
> This whole scenario is not very clear to me. Ofcourse a handler can
> invoke a web service call but I don't understand the part "It seems to
> me that the problem is the handler endpoint generated by Axis2"
> 
> Ajith
> 
> On 6/27/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> is it possible to use MTOM from a handler? In other words, can a handler
>> send a request (say, for a file) to a web service? It seems to me that
>> the problem is the handler endpoint generated by Axis2, needed to
>> receive the response, which is wrong.
>>
>>
>>
>> Thanks in advance,
>> Michele
>>
>> -
>> 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: [Axis 2]How can I check that a handler is executed?

[Deepal Jayasinghe]

hmm , as I can see everything is OK .
I think this is smt to do with logging properties, can you please try
the following
- juts try to create a file inside invoke method of the handler and see
its working :)
.


Fabien Couble wrote:

>
> Hi Deepal,
> As you said, I can see my module via the web admin console. The
> phaseName I have added is loggingPhase.
> This is what the web console return me:
> View Operation Specific Chains
> Operation Name : echo
> In Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : InFlowLogHandler
>  b.. Phase Name : OperationInPhase
> In Fault Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : FaultInFlowLogHandler
>  b.. Phase Name : OperationInFaultPhase
> Out Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : OutFlowLogHandler
>  b.. Phase Name : OperationOutPhase
> Out Fault Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : FaultOutFlowLogHandler
>  b.. Phase Name : OperationOutFaultPhase
> Operation Name : ping
> In Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : InFlowLogHandler
>  b.. Phase Name : OperationInPhase
> In Fault Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : FaultInFlowLogHandler
>  b.. Phase Name : OperationInFaultPhase
> Out Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : OutFlowLogHandler
>  b.. Phase Name : OperationOutPhase
> Out Fault Flow
>  a.. Phase Name : loggingPhase
>a.. Handler Name : FaultOutFlowLogHandler
>  b.. Phase Name : OperationOutFaultPhase
> So I think, everything is allright.
> I engaged this module by adding a module ref to the service.xml file
> of my service.
> However, when I want to test that my module is executed, I can't see
> anything!!
> An idea...??
>
> Cheers
> Fabien
>
>
>
> - Original Message - From: "Deepal Jayasinghe"
> <[EMAIL PROTECTED]>
> To: 
> Sent: Thursday, June 29, 2006 9:53 AM
> Subject: Re: [Axis 2]How can I check that a handler is executed?
>
>
>> Hi Fabien;
>>
>> Fabien Couble wrote:
>>
>>> Hello,
>>>
>>> I'm trying to engage a module in the Axis2 chain.
>>> Apparently, the module is well engaged in a service (I checked the
>>> Administration console) but I'd like to be sure that the handler of
>>> the module is executed!!
>>
>>
>> If you engage the module correctly , using web admin console you should
>> be able to see your handler in the handler chain.
>>
>>> To do that, I put a "System.out.println" command in the method invoke
>>> of the handler but nothing... (in the log of the Tomcat server)
>>> That is why, I'd like to know if it is a good method to check that
>>> or not!
>>
>>
>> How do you engage a module , using web admin console or adding module
>> ref to services.xml ?
>>
>>> If not, how can I do?
>>>
>>
>>
>> -- 
>> Thanks,
>> Deepal
>> 
>> ~Future is Open~
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED] 
>
>
>
> This message contains information that may be privileged or
> confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not
> the intended recipient,  you are not authorized to read, print,
> retain, copy, disseminate,  distribute, or use this message or any
> part thereof. If you receive this  message in error, please notify the
> sender immediately and delete all  copies of this message.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

-- 
Thanks,
Deepal

~Future is Open~ 



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

Content is not allowed in prolog

[Luanne Coutinho]

Hi,

 

I used wsdl2Java to generate
stubs so that I can access a web service hosted elsewhere. 

I wrote a test program
to invoke an operation, but I keep getting this error: 

 

AxisFault

 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode:


 faultString:
org.xml.sax.SAXParseException: Content is not allowed
in prolog.

 faultActor:


 faultNode:


 faultDetail:


    {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException:
Content is not allowed in prolog.

    at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)

    at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)

    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)

    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)

    at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
Source)

    at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown
Source)

    at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)

    at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

    at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

    at org.apache.xerces.parsers.XMLParser.parse(Unknown
Source)

    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)

    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)

    at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)

    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)

    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)

    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)

    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)

    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)

    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)

    at org.apache.axis.client.Call.invoke(Call.java:2767)

    at org.apache.axis.client.Call.invoke(Call.java:2443)

    at org.apache.axis.client.Call.invoke(Call.java:2366)

    at org.apache.axis.client.Call.invoke(Call.java:1812)

 

Could
someone please help? I have tried all sugestions from this mailing list, but
none have resolved the problem.

 

Thanks

Luanne
Misquitta

 

Re: [Axis2] SESSION_MAINTAIN_PROPERTY problem

[Loïc MAZE]

Thanks for this quick reply !


- Original Message - 
From: "Deepal Jayasinghe" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, June 29, 2006 10:40 AM
Subject: Re: [Axis2] SESSION_MAINTAIN_PROPERTY problem



Hi ;
This is how it works in Axis2.

   Options options = new Options();
   *options.setManageSession(true);*
   ServiceClient sender = new ServiceClient(configContext, null);
   sender.setOptions(options);
   sender.sendReceive(payload.getBody().getFirstElement());

Loïc MAZE wrote:


Hi all,

I would like to know how to set the property SESSION_MAINTAIN_PROPERTY
to true.
It's very easy to make a such thing with Axis 1 but I've found
absolutely nothing with Axis 2.

Does anyone have some information in this regard ?

Best regards,
Loïc



--
Thanks,
Deepal

~Future is Open~



-
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: [Axis 2]How can I check that a handler is executed?

[Fabien Couble]

Hi Deepal,
As you said, I can see my module via the web admin console. The phaseName I 
have added is loggingPhase.

This is what the web console return me:
View Operation Specific Chains
Operation Name : echo
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
Operation Name : ping
In Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : InFlowLogHandler
 b.. Phase Name : OperationInPhase
In Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultInFlowLogHandler
 b.. Phase Name : OperationInFaultPhase
Out Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : OutFlowLogHandler
 b.. Phase Name : OperationOutPhase
Out Fault Flow
 a.. Phase Name : loggingPhase
   a.. Handler Name : FaultOutFlowLogHandler
 b.. Phase Name : OperationOutFaultPhase
So I think, everything is allright.
I engaged this module by adding a module ref to the service.xml file of my 
service.
However, when I want to test that my module is executed, I can't see 
anything!!

An idea...??

Cheers
Fabien



- Original Message - 
From: "Deepal Jayasinghe" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, June 29, 2006 9:53 AM
Subject: Re: [Axis 2]How can I check that a handler is executed?



Hi Fabien;

Fabien Couble wrote:


Hello,

I'm trying to engage a module in the Axis2 chain.
Apparently, the module is well engaged in a service (I checked the
Administration console) but I'd like to be sure that the handler of
the module is executed!!


If you engage the module correctly , using web admin console you should
be able to see your handler in the handler chain.


To do that, I put a "System.out.println" command in the method invoke
of the handler but nothing... (in the log of the Tomcat server)
That is why, I'd like to know if it is a good method to check that or 
not!


How do you engage a module , using web admin console or adding module
ref to services.xml ?


If not, how can I do?




--
Thanks,
Deepal

~Future is Open~



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



This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


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

Re: [Axis2] SESSION_MAINTAIN_PROPERTY problem

[Deepal Jayasinghe]

Hi ;
This is how it works in Axis2.  

Options options = new Options();
*options.setManageSession(true);*
ServiceClient sender = new ServiceClient(configContext, null);
sender.setOptions(options);
sender.sendReceive(payload.getBody().getFirstElement());

Loïc MAZE wrote:

> Hi all,
>  
> I would like to know how to set the property SESSION_MAINTAIN_PROPERTY
> to true.
> It's very easy to make a such thing with Axis 1 but I've found
> absolutely nothing with Axis 2.
>  
> Does anyone have some information in this regard ?
>  
> Best regards,
> Loïc


-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: WSDL2Java and one-way binding

[Benjamin Fan]

I've given up on service-generated-WSDL - I hand-cut/validate WSDL and use WSDL2Java to generate both the server-side skeleton and the client side stubs. I haven't done it yet but I'm told its straight forward to modify the generated code to return static WSDL files rather than genertaing WSDL on the fly. ANy chance of you manually maintaining the generated skeleton? This is what I'm going to have to do...

On 6/29/06, John Mani <[EMAIL PROTECTED]> wrote:
Hi allAny comments on the below issue ? I'd expect this to be a common scenario .. so am Imisunderstanding something ?
thanx-johnFrom: John Mani [mailto:[EMAIL PROTECTED]]Sent: Tue 6/27/2006 6:53 PMTo: 
axis-user@ws.apache.orgSubject: WSDL2Java and one-way bindingI'm using Axis 1.4 WSDL2Java to generate skeletons for a webservice from a WSDL doc.The source WSDL (generated by .NET) uses one-way binding - it just specifies a
 element, no  element.However, the generated skeleton code seems to be including a response to the request.This is proven by checking the deployed skeleton's WSDL (deployed in tomcat, using
the axis war) - it contains   and  messages. Also, whenI run the .NET client against the deployed skeleton, the client complaints about theunexpected entity body in the response.
Any comments/help ?thanx-jm-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] SESSION_MAINTAIN_PROPERTY problem

[Loïc MAZE]

Hi all,
 
I would like to know how to set the property 
SESSION_MAINTAIN_PROPERTY to true.
It's very easy to make a such thing with Axis 
1 but I've found absolutely nothing with Axis 2.
 
Does anyone have some information in this 
regard ?
 
Best 
regards,Loïc

Re: [Axis 2]How can I check that a handler is executed?

[Deepal Jayasinghe]

Hi Fabien;

Fabien Couble wrote:

> Hello,
>  
> I'm trying to engage a module in the Axis2 chain.
> Apparently, the module is well engaged in a service (I checked the
> Administration console) but I'd like to be sure that the handler of
> the module is executed!!

If you engage the module correctly , using web admin console you should
be able to see your handler in the handler chain.

> To do that, I put a "System.out.println" command in the method invoke
> of the handler but nothing... (in the log of the Tomcat server)
> That is why, I'd like to know if it is a good method to check that or not!

How do you engage a module , using web admin console or adding module
ref to services.xml ?

> If not, how can I do?
>  


-- 
Thanks,
Deepal

~Future is Open~ 



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

[Axis 2]How can I check that a handler is executed?

[Fabien Couble]

Hello,
 
I'm trying to engage a module in the Axis2 chain. 

Apparently, the module is well engaged in a service 
(I checked the Administration console) but I'd like to be sure that the 
handler of the module is executed!!
To do that, I put a "System.out.println" command in 
the method invoke of the handler but nothing... (in the log of the Tomcat 
server)
That is why, I'd like to know if it is a good 
method to check that or not!
If not, how can I do?
 
Please, help me...
Cheers 
Fabien

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.

Re: Re : sending soap messages asynchronously

[Deepal Jayasinghe]

Axis2 support asynchronous invocation

Phani Sekhar wrote:

> Hi all,
>
> We are implementing NETCONF on SOAP over HTTP. We are using Axis.
>
> We require the Axis web service to send some soap messages
> asynchronously to the Axis client without any initiation.
>
> Ofcourse for the first time, we can register the client at the server.
> We are trying to implement something similar to the snmp
> traps/notifications.
>
> Is is possible to do this using Axis Does Axis support
> asynchronous messaging???
>
>  
>
> Please help me.
>
>  
>
> Thanks in advance
>
> Phani Sekhar
>
>  
>
> -Original Message-
> *From:* Phani Sekhar [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, June 21, 2006 12:47 PM
> *To:* axis-user@ws.apache.org
> *Subject:* sending asynchronous soap messages
>
>  
>
> Hi,
>
> Is there any way to send asynchronous soap messages from a webservice
> in Axis, something similar to snmp notifications ???
>
>  
>
> Thanks in Advance
>
> Phani Sekhar
>

-- 
Thanks,
Deepal

~Future is Open~ 



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