WSDL 2.0

Hi all, Axis started supporting WSDL 2.0 with Axis2 correct? Thanks

Re: WSDL 2.0

And thus the support of REST in Axis 2 ... Great - thanks Deepal. Deepal Jayasinghe wrote: Axis does not support WSDL 2.0, however Axis2 support WSDL 2.0 Deepal Hi all, Axis started supporting WSDL 2.0 with Axis2 correct? Thanks

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

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 <mailto:mgai...@hotmail.com>> wrote: Good Evening Demetris Axis1 is a servlet

Axis2 and POJO from Axis1

Hi all, I am testing legacy WS modules that were running well on Axis 1.4. In essense with minimal changes I have been able to deploy these services on Axis2 1.5 in Tomcat. I can retrieve their WSDL docs the same way I did with Axis 1.4. However, I am noticing that simple clients that generated

Re: Axis2 and POJO from Axis1

org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:595) Demetris wrote: Hi all, I am testing legacy WS modules that were running well on Axis 1.4. In essense with minimal changes I have been able to deploy these services on Axis2

Re: Axis2 and POJO from Axis1

OMElements can also be used in this case). With Axis 1.4 we got used to generating stubs and importing them in our services - calls to them were what was needed to access the remote service. How much of the stubs/proxy model is used in Axis2? Thanks again Demetris wrote: Hi all, this is

Re: Axis2 and POJO from Axis1

Has anyone seen this exception before? Is this a Class issue on the client side? This client code (last line): RPCServiceClient serviceClient = new RPCServiceClient(); Options options = serviceClient.getOptions(); EndpointReference targetEPR = new EndpointReference("http:/

Re: Axis2 and POJO from Axis1

? And I cannot use Vectors at all? Thanks Demetris wrote: Has anyone seen this exception before? Is this a Class issue on the client side? This client code (last line): RPCServiceClient serviceClient = new RPCServiceClient(); Options options = serviceClient.getOptions

Re: unsubscribe

Aren't there filters to reject/respond emails that have the title unsuscribe since they don't belong to this list? I know catch spam is not easy but catching the unsubscribers should be easier ;) Rares use the links below to unsubscribe man. Cheers Rares Pop wrote:

Re: Axis2 and POJO from Axis1

Hi all, even the example from the UserGuide outputs this when intecepted. How can I print the complete SOAP message (env and body) that is emitted as payload from these simple clients? Thanks POST /axis2/services/BooksAxis2Service HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: "ur

Re: Axis2 and POJO from Axis1

initialized? Thanks again Demetris wrote: Hi all, even the example from the UserGuide outputs this when intecepted. How can I print the complete SOAP message (env and body) that is emitted as payload from these simple clients? Thanks POST /axis2/services/BooksAxis2Service HTTP/1.1 Content-Type

Re: Axis2 and POJO from Axis1

Got it - thanks. Andreas Veithen wrote: Axis2 uses commons-logging. If log4j is present in the classpath, it takes precedence over java.util.logging and you must supply a log4j.properties file. Andreas On Fri, Apr 23, 2010 at 22:32, Demetris wrote: And I am also getting the following

Re: Axis2 and POJO from Axis1

I gave up using the POJO method for generating the outgoing SOAP message as it does not seem to work. I am able to generate a correct SOAP envelope using the SOAPFactory etc explicitly. However, I get the following: org.apache.axis2.AxisFault: Unknown SOAP Version. Current Axis handles only

Re: Axis2 and POJO from Axis1

log4j.properties file. Andreas On Fri, Apr 23, 2010 at 22:32, Demetris wrote: And I am also getting the following: log4j:WARN No appenders could be found for logger (org.apache.axis2.util.Loader). log4j:WARN Please initialize the log4j system properly. The actual client code does not include

Re: Axis2 and POJO from Axis1

I gave up using the POJO method for generating the outgoing SOAP message as it does not seem to work. I am able to generate a correct SOAP envelope using the SOAPFactory etc explicitly. However, I get the following: org.apache.axis2.AxisFault: Unknown SOAP Version. Current Axis handles only SO

Re: Axis2 and POJO from Axis1

I solved it - just in case another poor soul makes the same mistake I did - the env.setNamespace(ns) below is not necessary and it causes the issue. Demetris wrote: I gave up using the POJO method for generating the outgoing SOAP message as it does not seem to work. I am able to generate a

Re: Starting axis2server.sh in a different port

Exactly - ok thanks Amila - I am used to changing the services.xml file with Tomcat ;) Amila Suriarachchi wrote: On Sat, Apr 24, 2010 at 11:54 PM, D G > wrote: So the only way is to modify the baseline? Then why not just fix the configurable -p option?

Re: RPC SOAP

/envelope/ namespace. * getText returns the results as specified in the Javadoc [1]. Andreas [1] http://people.apache.org/~veithen/axiom/apidocs/org/apache/axiom/om/OMElement.html#getText() On Sun, Apr 25, 2010 at 07:20, Demetris wrote: Why is the Body print showing this xmlns:soapenv="

Re: RPC SOAP

Would the Axis2 engine accept proper SOAP messages (Envelope + Body) that do not carry the ? Also is the soapenv: prefix for the Envelope and the Body tags required? Thanks again Demetris wrote: OK I think I got it. Thanks Andreas Andreas Veithen wrote: All this is by design

Re: RPC SOAP

Super - thanks for verifying this. Andreas Veithen wrote: On Mon, Apr 26, 2010 at 07:57, Demetris wrote: Would the Axis2 engine accept proper SOAP messages (Envelope + Body) that do not carry the ? Yes. If I remember correctly the SOAP specs even say that the message should not

Re: RPC SOAP

out) whereas using the ws.js lib it is set to application/xml. Any ideas? Thanks again Demetris wrote: Super - thanks for verifying this. Andreas Veithen wrote: On Mon, Apr 26, 2010 at 07:57, Demetris wrote: Would the Axis2 engine accept proper SOAP messages (Envelope + Body) that do

Re: RPC SOAP

And it was the application/xml encoding - switched it to text/xml and the js client script works exactly as the java client. Cheers and thanks Demetris wrote: One of the reasons I was asking is because using a java-based client I wrote I can access the remote Axis2 service with no issues

Axis2 and Same origin

HI all, do standalone instances of Axis2 deal with the same origin scenarios? If a remote client is running Ajax/XHR on a browser, there are cases taht that the browser will send a preflight OPTIONS request to the server before it can send the request. Does Axis2 deal with such a request or does

Chunked response

Hi all, is there a way to configure the server not to returned chunked data? Or dealing with the chunked data (may be reading the returned response using InputStreams) is more efficient than eliminating it? Thanks - To unsu

Re: Chunked response

ves the limit on the size of the response. Brett -Original Message- From: Demetris [mailto:demet...@ece.neu.edu] Sent: Thursday, August 04, 2011 10:17 AM To: java-user@axis.apache.org Subject: Chunked response Hi all, is there a way to configure the server not to returned chunked data?

SVN

Hi all, last time I was developing with Axis was Axis 1.4 - yep a while ago. Working to migrate to Axis2 1.5 and from what I read the development of WS now has changed dramatically, although the fundamental concepts of implementing the SOAP spec is the same - true? In any case, I don't see much so

Axis2 sources

I understand the Axis2 source can be build only using Maven but are the sources also removed from the SVN repos? - To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axi

Re: Axis2 sources

Super ;) Thanks Paul and Nandana for the info. Quoting Paul Fremantle : > No! Of course not. All Apache source code is always available in the SVN. > > Paul > > On 3/7/10, Demetris G. Galatopoullos wrote: > > > > > > I understand the Axis2 source can be build

Re: Problem when calling local service

Nice - thanks fhe info. Quoting Adnan : > i turned on the axis logs 2 more details, and saw tht sevice endpoint was not > being sent correctly by bpel process, case sentivity problem. > > -- > al > > > > > > From: D G > To: "java-user@axis.apache.org" > Cc: "j