Axis2 and WSCL ,WSBPEL

Hi All, does AXIS2 supports WSCL and WSBPEL? if yes could u please point me to some link. your response is highly appreciated. Thanks.

Re: Axis 1.4 to Axis 2

Thanks Sanjiva Sanjiva Weerawarana wrote: I think the question is about wire-level interop .. not code portability? Yes it should work. Sanjiva. On Thu, Mar 25, 2010 at 5:10 AM, Martin Gainty > wrote: Good Evening Demetris Axis1 is a servlet available i

Re: Axis 1.4 to Axis 2

Not a bad idea Martin thanks. Martin Gainty wrote: Good Evening Demetris Axis1 is a servlet available in RPC and doc-literal styles Axis2 primarily for AARs (Service Archives) primarily for doc-literal style I would refactor by hand just to make sure you have firmer control over what is sp

Re: Axis 1.4 to Axis 2

I think the question is about wire-level interop .. not code portability? Yes it should work. Sanjiva. On Thu, Mar 25, 2010 at 5:10 AM, Martin Gainty wrote: > Good Evening Demetris > > Axis1 is a servlet available in RPC and doc-literal styles > Axis2 primarily for AARs (Service Archives) pri

RE: Axis 1.4 to Axis 2

Good Evening Demetris Axis1 is a servlet available in RPC and doc-literal styles Axis2 primarily for AARs (Service Archives) primarily for doc-literal style I would refactor by hand just to make sure you have firmer control over what is specific to the service and which code segments can be

Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...

Note that "suddenly" doesn't exist in the IT world. If the problem occurs when moving from a server that exclusively uses HTTP to a server that uses HTTPS, then it is definitely caused by AXIS2-4465. Andreas On Wed, Mar 24, 2010 at 21:42, Raghu Upadhyayula wrote: > Andreas, > >        I'm using

Axis 1.4 to Axis 2

I am not sure but this may have been asked before. Is it possible for an Axis 1.4 client to call an Axis 2 service and an Axis 2 client to call an Axis 1.4 service? Is the SOÁP message carrying a different content or is the version of supported soap different across these versions? It would

RE: [Axis2] - Issue with soap:address locaiton in the WSDL ...

Andreas, I'm using Axis2 1.4 & it used to work correctly last week, but it is showing port 8080 since then. It is happening in our QA box which is using https. Thanks Raghu -Original Message- From: Andreas Veithen [mailto:[email protected]] Sent: Wednesday, March 24,

Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...

Could be caused by AXIS2-4465. Andreas On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula wrote: > > Hi, > > My webservices is deployed under port 80, but when I see the WSDL in the > browser, the soap:address location in the WSDL is showing port 8080. > > > > My webservices url is http://localho

[Axis2] - Issue with soap:address locaiton in the WSDL ...

Hi, My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080. My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as http://localhost:8080/webservic

Re: How to set Timeout for SOAP calls? [SOAP-Client built with Axis2 1.4.1 / XMLbeans 2.3.0 on JRE 1.4.2 (IBM WAS60)]

you can use stub._getServiceClient().getOptions().setTimeOutInMilliSeconds(); or stub._getServiceClient().getOptions().setProperty(); to set any property. thanks, Amila. On Wed, Mar 24, 2010 at 9:37 PM, Christian Gosch wrote: > No one answered, so I searched and found: > > If I use a generat

RE: How to set Timeout for SOAP calls? [SOAP-Client built with Axis2 1.4.1 / XMLbeans 2.3.0 on JRE 1.4.2 (IBM WAS60)]

No one answered, so I searched and found: If I use a generated class based on "org.apache.axis2.client.Stub", then there is a method "addPropertyToOperationClient(OperationClient operationClient, String propertyKey, Object propertyValue)", which simply executes "operationClient.getOptions().set

Axis2.war deployment problem on Weblogic 10.3

Hi, The "version" service in axis2.war works if it is packed into an aar inside the services folder. If the "version" service is exploded, and then the whole thing is re-packed into a war file (The war file has the service in exploded format), the version service is also not working !! If we want