Re: Axis2 deploy in Sun Application Server?

[Lahiru Sandakith]

Hi Duncan,

I have seen some compilation problems earlier and done small fixes to the
JSPs of the axis2 webapp to get it validate through the ECLIPSE WTP
1.5.1JSP syntax validator (I believe J2EE complient).  Other than few
warning
messages it did pass the validation. I have not tried it with sun
application server. Please try it, it will be valuable feedback.

Thanks

Lahiru

On 4/17/07, Duncan Thomson <[EMAIL PROTECTED]> wrote:


I'm trying to deploy Axis2 in Sun Java System Application Server
Platform Edition 9.0

It fails.

When I run the sun application server "verifier" tool on axis2.war
I get the errors shown below.

These errors seem like they'd be fixable without too much
effort...  However, before I attempt this, has anyone had any
experience getting axis2 deployed on the Sun App server?

Thanks,

Duncan


Output from running Sun "verifier" on axis2.war:
===
  FAILED TESTS :
  --

  Test Name : tests.web.AllJSPsMustBeCompilable
  Test Assertion : All the JSPs that are bundled inside a
web application must be compilable using a J2EE compliant JSP
compiler th
at does not have any proprietary or optional features in it.
  Test Description : For [ axis2 ]
Error: Some JSPs bundled inside [ axis2 ] could not be compiled.
See details below.
axis2-web/TopFrame.jsp(29,4) Expecting "jsp:param" standard action
with "name" and "value" attributes
axis2-web/listGroupService.jsp(38,0) Expecting "jsp:param"
standard action with "name" and "value" attributes

  Test Name : tests.web.WelcomeFile
  Test Assertion : welcome-file element contains the file
name to use as a default welcome file.
  Test Description : For [ axis2 ]
Error: Welcome file URL [ /axis2-web/index.jsp ] must be a partial
URL with no trailing or leading /.
=

--
Duncan Thomson
Tel:  703-983-7337
Mobile:   703-463-0536
Text Msg: [EMAIL PROTECTED]



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





--
Regards
Lahiru Sandakith

Axis2 SSL : org.apache.axis2.AxisFault: Unconnected sockets not implemented

[Eric Chow]

Hello,

When I tried to invoke a web service over SSL, it caused the following
exception.
Please help me and I just want to invoke web service over SSL.

I am using Axis2-1.1.1 + Tomcat-5.0.28 + J2SDK-1.4.2.




My client code:

System.setProperty("javax.net.ssl.keyStore", "client.keystore"");
System.setProperty("javax.net.ssl.keyStorePassword", "changeit");

ESignTrustServiceStub stub = new ESignTrustServiceStub(uri);
VerifyResponse resp = stub.verify(v);



Tomcat setting:
==


Please also check my key generation step in the attached file.


Exceptions:


org.apache.axis2.AxisFault: Unconnected sockets not implemented;
nested exception is:
   java.net.SocketException: Unconnected sockets not implemented;
nested exception is:
   org.apache.axis2.AxisFault: Unconnected sockets not
implemented; nested exception is:
   java.net.SocketException: Unconnected sockets not implemented
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227)
   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
   at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
   at 
mo.dse.esigntrust.client.ESignTrustServiceStub.verify(ESignTrustServiceStub.java:325)
   at mo.dse.esigntrust.client.Check.check(Check.java:83)
   at org.apache.jsp.process_jsp._jspService(process_jsp.java:79)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
   at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   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.valves.AccessLogValve.invoke(AccessLogValve.java:535)
   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$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
   at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
   at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.axis2.AxisFault: Unconnected sockets not
implemented; nested exception is:
   java.net.SocketException: Unconnected sockets not implemented
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:344)
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)
   ... 38 more
Caused by: java.net.SocketException: Unconnected sockets not implemented
   at javax.net.SocketFactory.creat

Re: Axis2 1.1.1 and HTTPS problem

[Eric Chow]

Hi Ognjjen,

Can you show me the steps(include those key generation steps) to setup
in tomcat and your client.

On 4/16/07, Ognjen Blagojevic <[EMAIL PROTECTED]> wrote:

Hi all,

When I try to call Axis2-generated client for Axis2 web service over HTTPS,
an exception is thrown:

 java.lang.IllegalStateException: Can't overwrite cause.

Here is source:

Korona2Stub stubSsl = new
Korona2Stub("https://127.0.0.1:8443/axis2/services/korona2";);
Korona2Stub.TestSnimi reqSsl = new Korona2Stub.TestSnimi();
reqSsl.setTestString("Test string.");
reqSsl.setTestInteger(1); // Test integer
Korona2Stub.TestSnimiResponse res1Ssl = stubSsl.testSnimi(req); // Exception
thrown here.
System.out.println(res1Ssl.get_return());

Same code works fine with HTTP on 8080. Is there anything else I need to do
to make HTTPS work?

I'm using Tomcat 6.0.10 with HTTPS connector enabled, and I can call REST
version of my web service from Firefox:
https://127.0.0.1/axis2/rest/korona2/testSnimi?testString=test&testInteger=1


Below is the full stack trace:


Exception in thread "main" java.lang.IllegalStateException: Can't overwrite
cause
at java.lang.Throwable.initCause(Throwable.java:320)
at
com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
at com.ctc.wstx.exc.WstxException.(WstxException.java:46)
at
com.ctc.wstx.exc.WstxIOException.(WstxIOException.java:16)
at
com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:115)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:420)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:190)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:232)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
at
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at
orka.generated.Korona2Stub.testSnimi(Korona2Stub.java:850)
at orka.Klijent.main(Klijent.java:149)



Regards,
Ognjen



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

Re: Axis2 deploy in Sun Application Server?

[Sanjiva Weerawarana]

Please go for it .. I don't recall seeing much conversation about the Sun 
App Server.


Sanjiva.

Duncan Thomson wrote:
I'm trying to deploy Axis2 in Sun Java System Application Server 
Platform Edition 9.0


It fails.

When I run the sun application server "verifier" tool on axis2.war I get 
the errors shown below.


These errors seem like they'd be fixable without too much effort...  
However, before I attempt this, has anyone had any experience getting 
axis2 deployed on the Sun App server?


Thanks,

Duncan


Output from running Sun "verifier" on axis2.war:
===
 FAILED TESTS :
 --

 Test Name : tests.web.AllJSPsMustBeCompilable
 Test Assertion : All the JSPs that are bundled inside a web 
application must be compilable using a J2EE compliant JSP compiler th

at does not have any proprietary or optional features in it.
 Test Description : For [ axis2 ]
Error: Some JSPs bundled inside [ axis2 ] could not be compiled. See 
details below.
axis2-web/TopFrame.jsp(29,4) Expecting "jsp:param" standard action with 
"name" and "value" attributes
axis2-web/listGroupService.jsp(38,0) Expecting "jsp:param" standard 
action with "name" and "value" attributes


 Test Name : tests.web.WelcomeFile
 Test Assertion : welcome-file element contains the file name to 
use as a default welcome file.

 Test Description : For [ axis2 ]
Error: Welcome file URL [ /axis2-web/index.jsp ] must be a partial URL 
with no trailing or leading /.

=



--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

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

Re: Axis2: soap/jms WSDL generation

[Davanum Srinivas]

Yes. it's a bug.

-- dims

On 4/16/07, Shantanu Sen <[EMAIL PROTECTED]> wrote:


Once I deploy a sample e.g. samples/pojo with jms transport, I see the
correct uri in the generated WSDL. But the bindings still show up as using
http transport. E.g. here is a part of the generated WSDL



  


where the binding is as follows:



  http://schemas.xmlsoap.org/soap/http";
style="document" />

- 


Looks like a bug to me. Any comments?

Thanks,
Shantanu Sen




--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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

Axis2: soap/jms WSDL generation

[Shantanu Sen]

Once I deploy a sample e.g. samples/pojo with jms transport, I see the correct 
uri in the generated WSDL. But the bindings still show up as using http 
transport. E.g. here is a part of the generated WSDL



  






where the binding is as follows:



  http://schemas.xmlsoap.org/soap/http"; 
style="document" 
/> 



- 





Looks like a bug to me. Any comments?

Thanks,
Shantanu Sen

Re: [Axis2 1.1.1] Exceptions and POJO services

[John G. Norman]

I'm having the same problem. In my POJO service I have something like:

public String myOp(String s) throws MyException . . .

But no fault for MyException is showing up in the WSDL, and so when I
try to generate an ADB client against the WSDL, I don't get
client-side exception code generated. And if I throw MyException from
the service, all I get is RemoteException on the client (with cause
set to null).

Could someone from Axis2 verify this a bit? POJO service/client
handling of exceptions seems pretty broken. I could file a JIRA, but
I'm uncertain that a description of these symptoms would capture what
seems to be pretty significant lack of functionality. (Or maybe POJO
services aren't supposed to throw exceptions!?)

On 4/16/07, Jarek Kucypera <[EMAIL PROTECTED]> wrote:

If I declare a (non-void) service method to throw an exception,
the resulting wsdl describes the corresponding exception
type as anyType, like this:
 
  
   
  
 
Is there a way to throw custom exceptions (return faults of custom
types) from POJO based services, so that the fault type is
described in the wsdl ?

J.K.

-
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: Procedure to report bug to axis2

[Chau, Hoang]

 Thanks Amila for pointing it out.  Actually, I am wondering how
the xmlbeans binding find all the references.  The Axis1.4 also has no
problem generating code from the same wsdl.
 
 Hoang

-Original Message-
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Sunday, April 15, 2007 10:27 PM
To: axis-user@ws.apache.org
Subject: Re: Procedure to report bug to axis2


in your wsdl you have the following imports,

http://www.irs.gov/a2a/mef/MeFTransmitterServiceWse.xsd
 " />
http://www.irs.gov/efile"; />

So in adb if you do not specify a schemaLocation it tries to get
the schema from the uri given in the namespace itself

but in this case 
http://www.irs.gov/a2a/mef/MeFTransmitterServiceWse.xsd
 is not linked to a proper xsd file.


On 4/16/07, Chau, Hoang <[EMAIL PROTECTED]> wrote: 

Thank you very much.

Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 15, 2007 8:36 PM
To: axis-user@ws.apache.org
Subject: Re: Procedure to report bug to axis2


http://issues.apache.org/jira/browse/AXIS2

On 4/15/07, Chau, Hoang < [EMAIL PROTECTED]> wrote:
>
>
> Hi all,
>
> There are some errors generating code using adb
binding with the
> following WSDL
>
http://fsettestprod.edd.ca.gov/fsetproxy/fsetservice.asmx?WSDL
>
>
> Basically, it can not find the element with the import
namespace.
> However, it is fine when I used xmlbean binding.
> 
> Secondly, when I generated the test program with the
codes generated
> with the xmlbeans binding, I got some error about
nullpointer
> exception.
>
>
>
> Exception in thread "main"
java.lang.NullPointerException
>
> at
>
org.apache.axis2.description.ClientUtils.inferInTransport(ClientUtils.
> java:85)
>
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute (OutInAxi
> sOperation.java:163)
>
>
> By the way,  I was able to generate client code using
adb binding
> accessing the other webservice and everything works
fine.
>
> If anybody knows the procedure to report to axis2,
please let me know. 
>
> Thanks in advance,
>
>
>
> Hoang
>
>
>
>
>
>
>
>
> 
>
>
>
>
>  This message and any attachments are intended only
for the use of the 

> addressee and may contain information that is
privileged and
> confidential. If the reader of the message is not the
intended
> recipient or an authorized representative of the
intended recipient, 
> you are hereby notified that any dissemination of this
communication
> is strictly prohibited. If you have received this
communication in
> error, notify the sender immediately by return email
and delete the 
> message and any attachments from your system.
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED] 
> For additional commands, e-mail:
[EMAIL PROTECTED]
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web
Services
Developers


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






--

issue when sending big arrays

[Jorge Fernandez]

Hi all,

I'm having problems when I have to return big arrays. I have an operation in 
the web service I'm building for my Career Final Project which returns the xml 
code for a class that contains two arrays and an int. One of the arrays is an 
short array and usually is very big. The other one has no components in the 
tests I did at the moment. I get the following exception in my client:


Exception in thread "main" java.lang.RuntimeException: Data binding error
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5792)
at client.Medici_LinkStub.getPrimitiveData(Medici_LinkStub.java:2678)
at client.ClientUtilities.getPrimitiveDataTest(ClientUtilities.java:336)
at client.Client.main(Client.java:64)
Caused by: org.apache.xmlbeans.XmlException: Unexpected end of input block in 
end tag
 at [row,col {unknown-source}]: [1,4095]
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:847)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
at 
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
at 
medici_link.op_messages.xsd.GetPrimitiveDataResponseDocument$Factory.parse(GetPrimitiveDataResponseDocument.java:163)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5313)
... 3 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in 
end tag
 at [row,col {unknown-source}]: [1,4095]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:675)
at 
com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1029)
at 
com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:786)
at 
com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3204)
at 
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2830)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:917)
at 
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1098)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
... 7 more



I tried to find out what was the problem in my web service so I used the 
debugger and compared executions with diferent sizes for the array and 
everything seems to be alright (the return message appears to be built 
correctly) until I reach axisServlet.

In my log file  I see:

in axisServlet  catch exception:  2007-04-16 22:36:05 ERROR 
org.apache.axis2.transport.http.AxisServlet  - java.lang.IllegalStateException: 
Can't overwrite cause

I think that the method that throws the exception is req.getInputStream() that 
is a parameter of  HTTPTransportUtils.processHTTPPostRequest.

I started having problems when the array is about 220 components. I would like 
to know if there is any limitation on array's sizes.


Thanks and regards,

Jorge Fernández



   
-

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com

[Axis2 1.1.1] Exceptions and POJO services

[Jarek Kucypera]

If I declare a (non-void) service method to throw an exception,
the resulting wsdl describes the corresponding exception
type as anyType, like this:

 
  
 

Is there a way to throw custom exceptions (return faults of custom
types) from POJO based services, so that the fault type is
described in the wsdl ?

J.K.

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

Axis fault accessing WCF web service with WsHttpBinding

[shantanu chawla]

I am creating a client in java using axis2 1.1.1 to test
interoperability with WCF web services. My WCF web service is based on
wsHttpBinding. When I am trying to call its methods I am getting this
axis fault error.

org.apache.axis2.AxisFault: The SOAP action specified on the message,
'', does not match the HTTP SOAP Action,
'http://tempuri.org/IMyService/MyOperation1'.

My wsdl is


http://tempuri.org/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:tns="http://tempuri.org/";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:wsa10="http://www.w3.org/2005/08/addressing";
xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex";>



 
 
 
 

http://tempuri.org/Imports";>
 http://svr11.lab.interface.local/WCFService/Service.svc?xsd=xsd0";
namespace="http://tempuri.org/"; />
 http://svr11.lab.interface.local/WCFService/Service.svc?xsd=xsd1";
namespace="http://schemas.microsoft.com/2003/10/Serialization/"; />
 http://svr11.lab.interface.local/WCFService/Service.svc?xsd=xsd2";
namespace="http://schemas.datacontract.org/2004/07/"; />
 
 

 
 

 
 

 
 

 
 


 http://tempuri.org/IMyService/MyOperation1";
message="tns:IMyService_MyOperation1_InputMessage" />
 http://tempuri.org/IMyService/MyOperation1Response";
message="tns:IMyService_MyOperation1_OutputMessage" />
 

 http://tempuri.org/IMyService/MyOperation2";
message="tns:IMyService_MyOperation2_InputMessage" />
 http://tempuri.org/IMyService/MyOperation2Response";
message="tns:IMyService_MyOperation2_OutputMessage" />
 
 

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

 http://tempuri.org/IMyService/MyOperation1";
style="document" />

 
 

 
 
 

 http://tempuri.org/IMyService/MyOperation2";
style="document" />

 
 

 
 
 
 


 http://svr11.lab.interface.local/WCFService/Service.svc"; />

 
http://svr11.lab.interface.local/WCFService/Service.svc
 
 
 
 

and the java code of the stub generated by axis is

  public  void startMyOperation1(

org.tempuri.MyServiceStub.MyOperation1 param4,

 final org.tempuri.MyServiceCallbackHandler callback)

   throws java.rmi.RemoteException{

 org.apache.axis2.client.OperationClient _operationClient
= _serviceClient.createClient(_operations[0].getName());

_operationClient.getOptions().setAction("http://tempuri.org/IMyService/MyOperation1";);
_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);



 // create SOAP envelope with that payload
 org.apache.axiom.soap.SOAPEnvelope env=null;

   //Style is Doc.


   env =
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
   param4,

optimizeContent(new javax.xml.namespace.QName("",
   "MyOperation1")));

   //adding SOAP headers
_serviceClient.addHeadersToEnvelope(env);
   // create message context with that soap envelope
   org.apache.axis2.context.MessageContext _messageContext = new
org.apache.axis2.context.MessageContext() ;
   _messageContext.setEnvelope(env);

   // add the message contxt to the operation client
   _operationClient.addMessageContext(_messageContext);



  _operationClient.setCallback(new
org.apache.axis2.client.async.Callback() {
   public void onComplete(
   org.apache.axis2.client.async.AsyncResult result) {
   java.lang.Object object =
fromOM(result.getResponseEnvelope().getBody().getFirstElement(),

org.tempuri.MyServiceStub.MyOperation1Response.class,

getEnvelopeNamespaces(result.getResponseEnvelope())
   );

callback.receiveResultMyOperation1((org.tempuri.MyServiceStub.MyOperation1Response)
object);
   }

   public void onError(java.lang.Exception e) {
   callback.receiveErrorMyOperation1(e);
   }
   });


 org.apache.axis2.util.CallbackReceiver _callbackReceiver = null;
   if ( _operations[0].getMessageReceiver()==null &&
_operationClient.getOptions().isUseSeparateListener()) {
  _callbackReceiver = new org.apache.axis2.util.CallbackReceiver();
 _operations[0].setMessageReceiver(
   _callbackReceiver);
   }

Re: Axis https/SSL Server Certificate Validation question

[cmanjarr]

Please note clarification of the error stack I'm reporting:

This stack correspond to axis2-kernel1.2-snapshot.jar (downloaded friday
morning EST Apr-13-2007 )

org.apache.axis2.AxisFault: unknown protocol: myhttps
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
  at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)

Caused by: org.apache.axis2.AxisFault: unknown protocol: myhttps
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:308)
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
  ... 12 more

Caused by: java.net.MalformedURLException: unknown protocol: myhttps
  at java.net.URL.(URL.java:574)
  at java.net.URL.(URL.java:464)
  at java.net.URL.(URL.java:413)
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:283)
  ... 13 more



The previous stack corresponds to  axis2-kernel-1.1.1.jar


cmanjarr wrote:
> 
> Hi all:
> 
> I tested a custom SSL Socket Factory registered as "https" as per
> document: http://jakarta.apache.org/commons/httpclient/sslguide.html and
> worked pretty good.
> However when I register my custom SSL Socket Factory with another name
> like "myhttps", it does not work.
> 
> 1) First the stable release has a bug (NullPointerException) which is
> documented here:
> 
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg25009.html
> 
> So after downloading the lastest code from the nightly build repository
> with the fix for the NullPointerException bug, Axis2 thows another error:
> 
> org.apache.axis2.AxisFault: Transport out has not been set
>   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
> . more lines pertaining to my client sub...
> 
> So I added a new transportSender to the axis2_default.xml file (in
> axis2-kernel-1.2-SNAPSHOT.jar)
> like this:  (notice that I resused the existing CommonsHTTPTransportSender
> )
> 
>  
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> HTTP/1.1
>  locked="false">chunked
> 
> 
> 
> Then Axis reports another problem:
> 
> org.apache.axis2.AxisFault: unknown protocol: myhttps
> 
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
> 
>   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
>   at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
> .. more lines
> 
> Caused by: org.apache.axis2.AxisFault: unknown protocol: myhttps
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:308)
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
>   ... 12 more
> 
> Caused by: java.net.MalformedURLException: unknown protocol: myhttps
>   at java.net.URL.(URL.java:574)
>   at java.net.URL.(URL.java:464)
>   at java.net.URL.(URL.java:413)
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:283)
>   ... 13 more
> 
> #==
> 
> 
> Am I missing anything here? or Axis2/HttpClient can not really work well
> with a custom protocol name other than valid URLs?
> 
> I'd appreciate any comments on this one.
> thx,
> 
> Carlos M.
> 
> 
> Note this is my client code:
> 
> Protocol httpsProtocol = 
>   new Protocol("https", 
>   (ProtocolSocketFactory) new MYSSLProtocolSocketFactory( 
>  
>   new URL("file:/tmp/keyStore.ks" ) , 
> "keyStorePassword", new
> URL("file:/tmp/trustStore.ks" ), "trustStorePassword" ),  443 ); 
> 
> //Protocol.registerProtocol("https", httpsProtocol); // works fine
> Protocol.registerProtocol("myhttps", httpsProtocol); // does not work
> !!
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> 
> Xinjun Chen wrote:
>> 
>> Axis2 uses HTTPClient, so you can overwrite the https protocol by
>> registering your own SSLSocketFactory.
>> Refer http://jakarta.apache.org/commons/httpclient/sslguide.html for
>> details.
>> 
>> In your SSLSocketFactory, override the "private static TrustManager[]
>> cre

Re: [AXIS2] MTOM is not sending binary data as references for array of DataHandlers

[Thilina Gunarathne]

Thanks :)..

On 4/17/07, Masin, Valerie <[EMAIL PROTECTED]> wrote:

I submitted Jira 2541, with an attached wsdl and test client. Sorry it
took so long.
-- Valerie

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 11, 2007 11:20 PM
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] MTOM is not sending binary data as references for
array of DataHandlers

Sounds like a bug to me... Please log a JIRA.. If possible include your
WSDL and a test case...

Thilina

On 4/12/07, Masin, Valerie <[EMAIL PROTECTED]> wrote:
>
>
> One of my datatypes is an array of DataHandlers (DataHandler[]). (I
> got the wsdl to generate this by setting my base64Binary's maxOccurs
> to unbounded)
>
>  maxOccurs="unbounded" type="base64Binary"/>
>
> When I use MTOM I had expected to see each of these base64Binary
> objects as separate references to entities outside the soap message.
> However, when viewing the soap message with tcpmon, they are being
> sent 'by value' even though it is clear that mtom is enabled. If I
> don't use an array then I get exactly what I expected.
>
> Here is what I see (fixed up for clarity). Under  the
> document (which is only 8 bytes) is embedded in the message rather
> than referencing outside. I was counting on being able to use MTOM to
> send more than one binary on the wire. Is it not possible to do this?
> Thanks, Valerie
>
> POST /webservices2_0d/services/DocHarborServices HTTP/1.1
> SOAPAction: "urn:compositeCreateDocument"
> User-Agent: Axis2
> Host: us00wl00.devportal.net:30004
> Content-Length: 2390
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159;
> type="application/xop+xml";
> start="<0.urn:uuid:[EMAIL PROTECTED]>";
> start-info="text/xml"; charset=UTF-8
>
> --MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159
> content-type: application/xop+xml; charset=UTF-8; type="text/xml";
> content-transfer-encoding: binary
> content-id:
> <0.urn:uuid:[EMAIL PROTECTED]>
>
>   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>   
>  xmlns:ns1="urn:webservices.docharbor.com">
>
> apiuser
>
>
user1cust1
>   MTIzLS0tLTENCg==
>   MTIzLS0tLTINCg==
>
> 
> --MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159--


--
Thilina Gunarathne  -  http://www.wso2.com -
http://thilinag.blogspot.com

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


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





--
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

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

Re: Axis https/SSL Server Certificate Validation question

[cmanjarr]

Hi all:

I tested a custom SSL Socket Factory registered as "https" as per document:
http://jakarta.apache.org/commons/httpclient/sslguide.html and worked pretty
good.
However when I register my custom SSL Socket Factory with another name like
"myhttps", it does not work.

1) First the stable release has a bug (NullPointerException) which is
documented here:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg25009.html

So after downloading the lastest code from the nightly build repository with
the fix for the NullPointerException bug, Axis2 thows another error:

org.apache.axis2.AxisFault: Transport out has not been set
  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
  at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
. more lines pertaining to my client sub...

So I added a new transportSender to the axis2_default.xml file (in
axis2-kernel-1.2-SNAPSHOT.jar)
like this:  (notice that I resused the existing CommonsHTTPTransportSender )


HTTP/1.1
chunked



Then Axis reports another problem:

org.apache.axis2.AxisFault: unknown protocol: myhttps

  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)

  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
  at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
.. more lines

Caused by: org.apache.axis2.AxisFault: unknown protocol: myhttps
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:308)
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
  ... 12 more

Caused by: java.net.MalformedURLException: unknown protocol: myhttps
  at java.net.URL.(URL.java:574)
  at java.net.URL.(URL.java:464)
  at java.net.URL.(URL.java:413)
  at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:283)
  ... 13 more

#==


Am I missing anything here? or Axis2/HttpClient can not really work well
with a custom protocol name other than valid URLs?

I'd appreciate any comments on this one.
thx,

Carlos M.


Note this is my client code:

Protocol httpsProtocol = 
new Protocol("https", 
(ProtocolSocketFactory) new MYSSLProtocolSocketFactory( 
 
new URL("file:/tmp/keyStore.ks" ) , 
"keyStorePassword", new
URL("file:/tmp/trustStore.ks" ), "trustStorePassword" ),  443 ); 

//Protocol.registerProtocol("https", httpsProtocol); // works fine
Protocol.registerProtocol("myhttps", httpsProtocol); // does not work !!

 












--


Xinjun Chen wrote:
> 
> Axis2 uses HTTPClient, so you can overwrite the https protocol by
> registering your own SSLSocketFactory.
> Refer http://jakarta.apache.org/commons/httpclient/sslguide.html for
> details.
> 
> In your SSLSocketFactory, override the "private static TrustManager[]
> createTrustManagers(final KeyStore keystore)" method.
> And create your own X509TrustManager to trust all certs.
> 
> Insert the following line in the Axis2 web services client code to
> register
> your own https protocol.
> "Protocol.registerProtocol("https", new
> Protocol("https",(ProtocolSocketFactory) yourOwnSSLSocketFactory, port));"
> And HTTPClient will use your own SSLSocketFactory.
> 
> 
> Regards,
> Xinjun
> 
> 
> On 11/23/06, xu cai <[EMAIL PROTECTED]> wrote:
>>
>> Actually, you can use
>> System.setProperty("javax.net.ss.trustStore", "your key store file
>> location") .
>> it can set truststore file path.
>>
>>
>>  On 11/23/06, Luis Rivera <[EMAIL PROTECTED]> wrote:
>> >
>> >
>> >
>> >  Thanks a lot Vicio and Magnus,
>> >
>> > I will try Vicio's suggestion first since I am using applets and
>> writing
>> > to
>> > the client's hard disk might not be a viable option. However, I wonder
>> > if
>> > including a keystore in the jar file will do the trick. I am not sure
>> if
>> > a
>> > keystore is also looked for in the classpath, but I guess I can try.
>> >
>> >Thanks again,
>> >--Luis R.
>> >
>> > >From: <[EMAIL PROTECTED]>
>> > >Reply-To: axis-user@ws.apache.org
>> > >To: 
>> > >Subject: RE: Axis https/SSL Server Certificate Validation question
>> > >Date: Wed, 22 Nov 2006 12:53:12 +0100
>> > >
>> > >For avoiding certification validation, try to use the code:
>> > >
>> > >AxisProperties.setProperty("axis.socketSecureFactory","
>> > org.apache.axis.c
>> > >omponents.net.SunFakeTrustSocketFactory");
>> > >
>> > >it should solve your problem.
>> > >
>> > >
>> > >Regards,
>> > >Vicio.
>> > >
>> > >
>> > >--

Re: Logging module error with userguide examples

[Duncan Thomson]

Thanks Martin,

The only application containing that line was example2.  I think I 
somehow got that application's .aar file installed under axis2 in 
the tomcat webapps folder.  The service was not showing on the 
axis2 admin console as active, but something was there.  Anyway, I 
rebuilt a clean axis2.war and redeployed it.  Now the problem is 
gone.  User error, I guess.  Thanks.


Duncan

Martin Gainty wrote:

Good Morning Duncan

These are great suggestions

what would happen if you replaced this line from services.xml
  
with a blank line?

Again these are great suggestions as they step you thru the process in a 
chronological fashion


Thanks,
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - From: "Duncan Thomson" <[EMAIL PROTECTED]>
To: 
Sent: Monday, April 16, 2007 9:17 AM
Subject: Logging module error with userguide examples



I'm slogging my way through the axis2 userguide introduction
section, and I have some questions.  Hopefully there is someone on the 
list familiar with how the userguide examples were put together who 
can tackle these...


I've deployed axis2 (1.1.1) into apache tomcat (6).  I created and 
deployed the server example as described in the "Apache Axis2 User's 
Guide -Building Services" section.  I created and deployed the client 
as described in the "Creating Clients" section.  The client and server 
are both based on the wsdl file in code listing 5 in the userguide.


The client and server seem to work, however when I run the client
under axis2 I get a bunch of error messages related to undeployed 
logging modules (messages duplicated below).


I did some searching of the archives, and found some information about 
configuration things that have to be done to enable logging modules. 
But...


1) At this point in the user guide logging modules have not even
been mentioned, and I don't think the example in question uses
them.  So... what is trying to load them?  Is this perhaps the way
the way axis2.war comes set up by default?  Did I inadvertently
turn logging on (or miss a step in which I was supposed to turn it
off)?

2) How do I either turn logging off or properly deploy it?

3) In general, what's with all the "Deploying module" stuff I'm
getting when I run the client?  I'm just trying to figure this
stuff out, but I exepected the client to simply send SOAP messages
to the service, which has already been deployed, hasn't it?  So what's 
with all these messages about "doDeploy" when I run the client?  (Note 
- at this point I still don't really understand

exactly what this client is doing - I'm just working through the
examples in the userguide.)

Any help would be appreciated!

Duncan

p.s. A comment to the userguide authors - suggest we move the
example of building a service BEFORE the example of building the
client, because obviously the client won't work until the service
is built and deployed.

p.s. Another comment for userguide authors - suggest the example
commands be given for both Windows and unix environments, rather than 
just Windows.


Here are the error messages I get when I try to run the client...

seafox:~/myservice> axis2.sh org.apache.axis2.axis2userguide.Client
 Using AXIS2_HOME:/home/duncant/axis2
 Using JAVA_HOME: /usr/local/java
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : addressing-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : soapmonitor-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  version.aar
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  sample-MyService.aar
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules logging module is invalid or has not been
deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is in

RE: Axis2 and Maven

[Jay Liang]

Try to depend on 

  org.apache.axis2
  axis2
1.1.1 

It will save you about 10 jars.

Once you get it fully working, can you also post that dependency list to
this mailing list? I think many people will find that list useful.

Jay
-Original Message-
From: lightbulb432 [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 16, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 and Maven


So in the binary distribution of Axis2 in the lib folder I see 43 JARs.
In my
project's pom.xml will I actually have to specify 43 ?
Plus
the MARs? That's what it looks like in the 3 pom.xml's you pointed me to
earlier, but I couldn't tell if those POMs specified all 43
dependencies...

In making my project's pom.xml is there any way for me to know what's
the
best way to specify the  of each dependency, rather than keeping
all
to default? For example, which are runtime, compile, test, provided,
system,
etc? Is there any documentation, or has anybody come up with their own
pom.xml's that show this?

Thanks a lot.



Thilina Gunarathne wrote:
> 
>> Thanks for the links. When you do a "mvn package" in your project
that
>> depends on Axis2, is the Axis2 JAR that gets put in your local
repository
>> ~
>> 14 MB, or is it only 1.5 MB?
> 1.5 MB
>> When I do the maven command it's the latter,
>> but when I download directly from the Axis2 website it's the former,
so
>> clearly it's missing all the  dependencies!
> Seems like you are talking about the Axis2 binary distribution... You
> cannot make it a dependency as whole to your projects. It is a package
> made for the distribution, not to use with maven...  You will need to
> get maven to download the individual jars & mars (modules) you
> wanted..
> 
> Thanks,
> Thilina
> 
> 
> 
> -- 
> Thilina Gunarathne  -  http://www.wso2.com -
http://thilinag.blogspot.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/Axis2-and-Maven-tf3567687.html#a10016782
Sent from the Axis - User mailing list archive at Nabble.com.


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


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

Axis2 deploy in Sun Application Server?

[Duncan Thomson]

I'm trying to deploy Axis2 in Sun Java System Application Server 
Platform Edition 9.0


It fails.

When I run the sun application server "verifier" tool on axis2.war 
I get the errors shown below.


These errors seem like they'd be fixable without too much 
effort...  However, before I attempt this, has anyone had any 
experience getting axis2 deployed on the Sun App server?


Thanks,

Duncan


Output from running Sun "verifier" on axis2.war:
===
 FAILED TESTS :
 --

 Test Name : tests.web.AllJSPsMustBeCompilable
 Test Assertion : All the JSPs that are bundled inside a 
web application must be compilable using a J2EE compliant JSP 
compiler th

at does not have any proprietary or optional features in it.
 Test Description : For [ axis2 ]
Error: Some JSPs bundled inside [ axis2 ] could not be compiled. 
See details below.
axis2-web/TopFrame.jsp(29,4) Expecting "jsp:param" standard action 
with "name" and "value" attributes
axis2-web/listGroupService.jsp(38,0) Expecting "jsp:param" 
standard action with "name" and "value" attributes


 Test Name : tests.web.WelcomeFile
 Test Assertion : welcome-file element contains the file 
name to use as a default welcome file.

 Test Description : For [ axis2 ]
Error: Welcome file URL [ /axis2-web/index.jsp ] must be a partial 
URL with no trailing or leading /.

=

--
Duncan Thomson
Tel:  703-983-7337
Mobile:   703-463-0536
Text Msg: [EMAIL PROTECTED]



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

Problems when sending byte[] as attachment

[Faggart, Robin]

Can someone please give me some guidance..I'm a novice to
webservices

I picked up support for an existing webservice that passes image data as
an attachment using a java-specific DataHandler class.  Recently, I was
asked to add support for a .NET client which I think means that I need
to remove the DataHandler and pass the data via primitives or arrays.
In order to test the service in my java environment (I don't have a .net
environment), I modified my client code to pass the image data as a
byteArray in an attachment.  The code actually works, but the resulting
SOAP message (as seen in tcpmon) is huge (5.5 meg).  When I turn trace
on, I see multiple instances of what looks like the image data
(imageSource) being added 1000's of times.  Here is a snippet from the
log:

org.apache.axis.message.MessageElement - New MessageElement
([EMAIL PROTECTED]) named {}imageSource
org.apache.axis.message.MessageElement -   soapenc:arrayType =
'ns1:byte[][24576]'
org.apache.axis.message.MessageElement -   xsi:type = 'soapenc:Array'
org.apache.axis.encoding.DeserializationContext - Pushing element
imageSource
org.apache.axis.encoding.DeserializationContext - Exit:
DeserializationContext::startElement()
org.apache.axis.encoding.DeserializationContext - Enter:
DeserializationContext::startElement(, imageSource)
org.apache.axis.i18n.ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(pushHandler00)
org.apache.axis.encoding.DeserializationContext - Pushing handler
[EMAIL PROTECTED]
org.apache.axis.i18n.ProjectResourceBundle -
org.apache.axis.i18n.resource::handleGetObject(newElem00)
org.apache.axis.message.MessageElement - New MessageElement
([EMAIL PROTECTED]) named {}imageSource
org.apache.axis.message.MessageElement -   href = '#id0'
 org.apache.axis.encoding.DeserializationContext - Pushing element
imageSource
org.apache.axis.utils.NSStack - NSPush (32)
org.apache.axis.encoding.DeserializationContext - Exit:
DeserializationContext::startElement()
...
org.apache.axis.message.MessageElement - New MessageElement
([EMAIL PROTECTED]) named {}imageSource
org.apache.axis.message.MessageElement -   href = '#id1'
org.apache.axis.encoding.DeserializationContext - Pushing element
imageSource
...etc

I'm also including the client source code below. I've tried various
things that haven't worked, for example, I removed the type mapping for
the serializer factory.  The results were always the same.  Can someone
tell me what I'm doing wrong or point me to a resource that shows me how
to pass the image data via a byte array in an attachment?

I appreciate your help.
Robin


Client Source Code==>

public String sendSingleImage(String imageFileName) throws
Exception {
String qNamespaceDH = "urn:AService";
String qNamespaceOp = "urn:AService";

Service service = new Service();

Call call = (Call) service.createCall();

byte[] imageArray = readBytesFromFile(imageFileName);

//Set the target service host and service location,
String aHostName = getAServiceHostName();
String aPortNumber = getAServicePortNumber();
String aServletPath = getAServiceServletPath();
call.setTargetEndpointAddress(new URL("http://"; +
aHostName + ":" + aPortNumber + aServletPath));

//This is the target services method to invoke.
call.setOperationName(new QName(qNamespaceOp,
"imageAsByteArray"));

QName qNameAttachment = new QName(qNamespaceDH,
"byte[]");

// Add serializer for attachment
call.registerTypeMapping(Object.class,
qNameAttachment,
JAFDataHandlerSerializerFactory.class,
JAFDataHandlerDeserializerFactory.class);

//Add the file
call.addParameter("imageSource", qNameAttachment,
ParameterMode.IN);


call.setReturnType(org.apache.axis.Constants.XSD_STRING);

call.setUsername(getOpts().getUser());
call.setPassword(getOpts().getPassword());

call.setProperty(call.ATTACHMENT_ENCAPSULATION_FORMAT,

call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME);
Object ret = null;
try {
ret = call.invoke(new Object[] { imageArray });
} catch (Exception e) {
.

RE: [AXIS2] MTOM is not sending binary data as references for array of DataHandlers

[Masin, Valerie]

I submitted Jira 2541, with an attached wsdl and test client. Sorry it
took so long.
-- Valerie

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 11, 2007 11:20 PM
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] MTOM is not sending binary data as references for
array of DataHandlers

Sounds like a bug to me... Please log a JIRA.. If possible include your
WSDL and a test case...

Thilina

On 4/12/07, Masin, Valerie <[EMAIL PROTECTED]> wrote:
>
>
> One of my datatypes is an array of DataHandlers (DataHandler[]). (I 
> got the wsdl to generate this by setting my base64Binary's maxOccurs 
> to unbounded)
>
>  maxOccurs="unbounded" type="base64Binary"/>
>
> When I use MTOM I had expected to see each of these base64Binary 
> objects as separate references to entities outside the soap message. 
> However, when viewing the soap message with tcpmon, they are being 
> sent 'by value' even though it is clear that mtom is enabled. If I 
> don't use an array then I get exactly what I expected.
>
> Here is what I see (fixed up for clarity). Under  the 
> document (which is only 8 bytes) is embedded in the message rather 
> than referencing outside. I was counting on being able to use MTOM to 
> send more than one binary on the wire. Is it not possible to do this?
> Thanks, Valerie
>
> POST /webservices2_0d/services/DocHarborServices HTTP/1.1
> SOAPAction: "urn:compositeCreateDocument"
> User-Agent: Axis2
> Host: us00wl00.devportal.net:30004
> Content-Length: 2390
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159;
> type="application/xop+xml";
> start="<0.urn:uuid:[EMAIL PROTECTED]>";
> start-info="text/xml"; charset=UTF-8
>
> --MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159
> content-type: application/xop+xml; charset=UTF-8; type="text/xml";
> content-transfer-encoding: binary
> content-id:
> <0.urn:uuid:[EMAIL PROTECTED]>
>
>   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>   
>  xmlns:ns1="urn:webservices.docharbor.com">
>
> apiuser
>
>
user1cust1
>   MTIzLS0tLTENCg==
>   MTIzLS0tLTINCg==
>
> 
> --MIMEBoundaryurn_uuid_66DC1A499FD08057761176316581159--


--
Thilina Gunarathne  -  http://www.wso2.com -
http://thilinag.blogspot.com

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


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

Re: REST over GET support in Java clients?

[keith chapman]

Hi Phillip,

Most of the REST support (including support for PUT and DELETE) was added
after the 1.1 release. The REST support in Axis2 mostly emulates the WSDL
2.0 HTTPBinding. The 1.2 release will be out by the end of this month. You
can use the 1.2 Release candidate for the moment.

Also some of the properties I mentioned in my previous reply was added after
the 1.1 release (eg. MESSAGE_TYPE)

Thanks,
Keith.


On 4/16/07, Philipp Leitner <[EMAIL PROTECTED]> wrote:


I am currently at version 1.1.1 . Do you think that I should upgrade to
a more recent version?

/philipp

keith chapman schrieb:
> Hi Philipp,
>
> I guess the parameter ENABLE_REST_THROUGH_GET is not used anymore. Yes
> Axis2 supports REST. BTW which version are you using?
>
> The following applies if you are using the nightlies or the 1.2 Release
> candidate.
>
> Hope I answered your question...
>
> See comments inline
>
> On 4/16/07, *Philipp Leitner* <[EMAIL PROTECTED]
> > wrote:
>
> Hi folks,
>
> I am wondering if there is support for REST over HTTP GET for Java
> clients in Axis2?
>
> I know that there is the configuration parameter
> Constants.Configuration.ENABLE_REST_THROUGH_GET , but so far
I  could
> not make it work.
>
> I tried something like
>
> 
> Options options = new Options();
> options.setTo(new EndpointReference(toEpr));
>
>
> // Not really needed but better have it as it takes care of setting up
> default REST rules in case you miss something
>
> options.setProperty(Constants.Configuration.ENABLE_REST,
> Constants.VALUE_TRUE );
>
>
>  // Not needed
>
> options.setProperty(Constants.Configuration.ENABLE_REST_THROUGH_GET,
> Constants.VALUE_TRUE);
>
>
>
> // Need to add the following bit of code
>
> // The following will set the httpMethod to use (Supported methods are
> GET, PUT, DELETE and POST)
>  options.setProperty (Constants.Configuration.HTTP_METHOD,
> Constants.Configuration.HTTP_METHOD_GET);
>
> // Set the relavant contentType (Need to set the messagetype as well as
> its needed by the messageFormatters)
> // Supported contentTypes are  "application/x-www-form-urlencoded",
> "multipart/form-data" and "application/xml";
>  options.setProperty(Constants.Configuration.CONTENT_TYPE,
> HTTPConstants);
> options.setProperty(Constants.Configuration.MESSAGE_TYPE,
> HTTPConstants);
>
> ServiceClient sender = new ServiceClient();
> sender.setOptions(options);
> OMElement result = sender.sendReceive(
> OMAbstractFactory.getOMFactory().createOMElement("dummy",
null));
> 
>
> so far. I figure that the "payload" of an GET request should be null
or
> something irrelevant, given that a GET request does not have a body
to
> contain any payload?
>
> A quick check with tcpmon showed me that this code actually works,
but
> still (although I enabled
> Constants.Configuration.ENABLE_REST_THROUGH_GET ) uses HTTP POST for
the
> request.
>
> Can anybody tell me how I enable REST GET in the client (or if it is
> even supported) ?
>
> regards,
> philipp
>
>
>
> --
> Philipp Wolfgang Leitner, Bakk.rer.soc.oec .
> 0225511
> Vienna University of Technology
>
> " A programmer is a person who passes as an exacting expert on the
> basis of
> being able to turn out, after innumerable punching, an infinite
> series of
> incomprehensible answers calculated with micrometric precisions from
> vague
> assumptions based on debatable figures taken from inconclusive
documents
> and carried out on instruments of problematical accuracy by persons
of
> dubious reliability and questionable mentality for the avowed
> purpose of
> annoying and confounding a hopelessly defenseless department that
was
> unfortunate enough to ask for the information in the first place.
>  -- IEEE Grid newsmagazine "
>
>
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> 
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>
>
> Thanks,
> Keith.
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/

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





--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

Re: Too many nulls

[Neil Blue]

Thanks Ryan,

This looks like an error that also produces invalid WSDL when using addressing 
in the wsdl2java tool.

Neil

On Monday 16 April 2007 16:21, Ryan Nelsestuen wrote:
> OMSerializerUtil

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

Re: wsa:Action header emitted from client with value ""

[Steven E. Harris]

"Steven E. Harris" <[EMAIL PROTECTED]> writes:

> In the meantime, I'll file a JIRA issue.

That would be AXIS2-2534:

  http://issues.apache.org/jira/browse/AXIS2-2534

-- 
Steven E. Harris


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

Question regarding SOAP11 client compatibility

[Vibhor_Sharma]

Hi 
 I get the following error when i tested the webservices with soap11 client.
The web services have been developed by using the axis2(1.1.1) code generation 
tools and deployed on Jboss application server.
 
 
ERROR: Missing  element inFault "gryphonWSFault" in operation 
"gryphonWSFault", in binding certifyContact   

 

 

 

 

 

 

I'm using the wsdl generated by wsdl2java

Please compare the fault elements in the following WSDL snippet. Why is the 
tool not generating the appropriate element? 

Would it be the right thing to do by replacing the contents of fault elemnt 
from SOAP12 binding into SOAP11 binding?  



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





























http://schemas.xmlsoap.org/soap/http"; 
style="document"/>



























Thanks

Vibhor

 
 

Re: wsa:Action header emitted from client with value ""

[Steven E. Harris]

Lahiru Sandakith <[EMAIL PROTECTED]> writes:

> I got the same result when trying to codegen a WSDL 2.0 from the Axis2
> Codegen Eclipse plugin with the snapshot build.

Good, so I'm not the only one. I just updated to the 16 April 2007
nightly build and I'm still seeing the same result in the generated
code.

Can someone point us to where in the code takes care of generating the
following line?

  _operationClient.getOptions().setAction("\"\"");

In the meantime, I'll file a JIRA issue.

> Are you seeing this for a wsdl 1.1 as well ?

Unfortunately I don't have any WSDL 1.1 documents around to test.

-- 
Steven E. Harris


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

RE: Too many nulls

[Ryan Nelsestuen]

Assuming you are using Axis2, that looks a bit like this (unresolved) bug:

https://issues.apache.org/jira/browse/WSCOMMONS-175

You may be able to patch the OMSerializerUtil class to address.

-Original Message-
From: Neil Blue [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 16, 2007 9:06 AM
To: axis-user@ws.apache.org
Subject: Too many nulls

Hello,

I am using the simple RPCServiceClient to connect to a remote service. I
have 
a problem with null values. If an object that is passed to the service has 
more than one null value then I get an error as the nil namespace prefix is 
not bound often enough. 

For example:

xml sent
...
 
  http://www.w3.org/2001/XMLSchema-instance"; 
nil:nil="true">
  value
   
   
  http://www.w3.org/2001/XMLSchema-instance"; 
nil:nil="true">
  
   
...

Is there a work around for this? maybe defining the xmlschema namespace in
the 
root element?

Thanks
Neil

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

Too many nulls

[Neil Blue]

Hello,

I am using the simple RPCServiceClient to connect to a remote service. I have 
a problem with null values. If an object that is passed to the service has 
more than one null value then I get an error as the nil namespace prefix is 
not bound often enough. 

For example:

xml sent
...
 
  http://www.w3.org/2001/XMLSchema-instance"; 
nil:nil="true">
  value
   
   
  http://www.w3.org/2001/XMLSchema-instance"; 
nil:nil="true">
  
   
...

Is there a work around for this? maybe defining the xmlschema namespace in the 
root element?

Thanks
Neil

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

Databinding to existing domain java classes

[Nicolae Marasoiu]

Hi;

What are the options to make a web services remoting of a certain java call
?

1. RPC Service, hot deployed + RPC client: this requires no java code
generation by the user. It is the slowest solution right?
2. ADB generation: how to reuse my own domain objects?
- I can remove the attributes in each generated type class and make
it inherit my own type class, the domain class; javabean accessors will
delegate to corresponding accessors of the parent class or they are deleted
when the property names are the same (this will probably be my case); given
that one to many relationships are represented as array properties in both
domains (mine and generated one) I asses that this is a workable solution
right?
- Is there a currently implemented way of telling the generator to
work with existing type classes? Is it smart enaugh to make such a
decoupling between existing, user supplied data javabeans (DTOs) and the XML
- java binding infrastructure?
3. XML Beans or other generation

Thank you,
Nicu Marasoiu


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

[Axis2] getLastOperationContext() returns null

[José Antonio Sánchez]

I'm trying to access the returned SOAP headers in a generated Stub
from Axis 1.2RC2. I do this by invoking an operation in the stub and
then calling:

OperationContext opContext = stub._getServiceClient().getLastOperationContext();

But this returns null, so I can't go any further. I thought that
method was designed for that, get Headers in a response message.

I've filled a JIRA issue:

https://issues.apache.org/jira/browse/AXIS2-2533

--
Saludos.
José Antonio Sánchez

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

Axis 1.4 + Xfire serializer trouble

[ojojoj]

Hi! I'm having an Axis 1.4 client that tries to cooperate with a Xfire
webservice. The Axis client is generated from the Xfire WSDL. 

When the Client receives the SOAP response :

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
   
  http://service.customer.xxx.com";>
 None
  
   


... it seems to work. However, the Xfire service is more likely to give the
SOAP response :

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
   
  http://service.customer.xxx.com";>
 
http://api.customer.crm..xxx.com";>
   http://api.customer.crm..xxx.com.com";>
  
  
  
  SomeStreet
  34
  [EMAIL PROTECTED]
   
   http://api.customer.crm.xxx.com";>
  http://customer.type.xxx.com";
xsi:nil="true" />
  http://customer.type.xxx.com";>Y
  http://customer.type.xxx.com";>O
   

 
  
   


... and that causes my Axis 1.4 client to go :

org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
which is NOT expected, in something it was trying to deserialize.
at
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at org.apache.axis.client.Call.invoke(Call.java:2467)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)

Is there a way around this?

-- 
View this message in context: 
http://www.nabble.com/Axis-1.4-%2B-Xfire-serializer-trouble-tf3584850.html#a10017377
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Axis2 and Maven

[lightbulb432]

So in the binary distribution of Axis2 in the lib folder I see 43 JARs. In my
project's pom.xml will I actually have to specify 43 ? Plus
the MARs? That's what it looks like in the 3 pom.xml's you pointed me to
earlier, but I couldn't tell if those POMs specified all 43 dependencies...

In making my project's pom.xml is there any way for me to know what's the
best way to specify the  of each dependency, rather than keeping all
to default? For example, which are runtime, compile, test, provided, system,
etc? Is there any documentation, or has anybody come up with their own
pom.xml's that show this?

Thanks a lot.



Thilina Gunarathne wrote:
> 
>> Thanks for the links. When you do a "mvn package" in your project that
>> depends on Axis2, is the Axis2 JAR that gets put in your local repository
>> ~
>> 14 MB, or is it only 1.5 MB?
> 1.5 MB
>> When I do the maven command it's the latter,
>> but when I download directly from the Axis2 website it's the former, so
>> clearly it's missing all the  dependencies!
> Seems like you are talking about the Axis2 binary distribution... You
> cannot make it a dependency as whole to your projects. It is a package
> made for the distribution, not to use with maven...  You will need to
> get maven to download the individual jars & mars (modules) you
> wanted..
> 
> Thanks,
> Thilina
> 
> 
> 
> -- 
> Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis2-and-Maven-tf3567687.html#a10016782
Sent from the Axis - User mailing list archive at Nabble.com.


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

[axis2] accessing the password callback handler from the message contexts

[Nencho Lupanov]

Hi guys,

Are you aware if there is a way to get an instance of the password callback
that is used
from rampart for authentification.I need to get that instance within the
message receiver so,
can i obtain this somehow from the message context.

Thanks.

Re: AXIS2 option to run HttpClient in non-multithreadded way?

[Paul Fremantle]

I'm surprised - I wouldn't expect the code you have written to multithread.

The normal calls should block unless you use the callbacks in which
case its multi-threaded.

Paul

On 4/16/07, Peter Gylling Jørgensen <[EMAIL PROTECTED]> wrote:

Paul,

This is the simple code, which cause the problems

// Setup trust
this.activateTrust();
if(DbserverStubTest.sslFactory == null) {
DbserverStubTest.fatalError = true;
Assert.fail();
return;
}
// Define new protocol
Protocol trustHttps = new Protocol("https", DbserverStubTest.sslFactory, 6001);
Protocol.registerProtocol("https", trustHttps);

// Loop joblist and delete jobs
for(int i=0; i -Oprindelig meddelelse-
> Fra: Paul Fremantle [mailto:[EMAIL PROTECTED]
> Sendt: 16. april 2007 14:31
> Til: axis-user@ws.apache.org
> Emne: Re: AXIS2 option to run HttpClient in non-multithreadded way?
>
> Peter
>
> My understanding was that if you used the blocking model and your
> client code only made the second call after the first one returned
> then all should be fine.
>
> Can you post your client code?
>
> Paul
>
> On 4/16/07, Peter Gylling Jørgensen <[EMAIL PROTECTED]> wrote:
> > Dear all,
> >
> > How can I tweak the HttpClient not to run in a
> multithreaded environment? I discovered, that my AXIS2 based
> java client initiates a second connection to the server
> before the first connection is terminated, thus the server
> hits a fatal error due to a now known bug in the server code.
> >
> > But I would like to be capable of continuing the
> development of the client code while the bug is fixed in the
> server part.
> >
> > \pgj
> > --
> > Peter Gylling Jørgensen
> > Modelling group, section of Oceanography
> > Royal Danish Administration of Navigation and Hydrography
> > Overgaden o. Vandet 62B DK-1023 København K
> > Phone: +45 32 68 96 85
> > Email: [EMAIL PROTECTED]
> > www: http://www.frv.dk/
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> 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
>
> -
> 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]





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

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

Re: Logging module error with userguide examples

[Martin Gainty]

Good Morning Duncan

These are great suggestions

what would happen if you replaced this line from services.xml
  
with a blank line?

Again these are great suggestions as they step you thru the process in a 
chronological fashion


Thanks,
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: "Duncan Thomson" <[EMAIL PROTECTED]>

To: 
Sent: Monday, April 16, 2007 9:17 AM
Subject: Logging module error with userguide examples



I'm slogging my way through the axis2 userguide introduction
section, and I have some questions.  Hopefully there is someone on the 
list familiar with how the userguide examples were put together who can 
tackle these...


I've deployed axis2 (1.1.1) into apache tomcat (6).  I created and 
deployed the server example as described in the "Apache Axis2 User's 
Guide -Building Services" section.  I created and deployed the client as 
described in the "Creating Clients" section.  The client and server are 
both based on the wsdl file in code listing 5 in the userguide.


The client and server seem to work, however when I run the client
under axis2 I get a bunch of error messages related to undeployed logging 
modules (messages duplicated below).


I did some searching of the archives, and found some information about 
configuration things that have to be done to enable logging modules. 
But...


1) At this point in the user guide logging modules have not even
been mentioned, and I don't think the example in question uses
them.  So... what is trying to load them?  Is this perhaps the way
the way axis2.war comes set up by default?  Did I inadvertently
turn logging on (or miss a step in which I was supposed to turn it
off)?

2) How do I either turn logging off or properly deploy it?

3) In general, what's with all the "Deploying module" stuff I'm
getting when I run the client?  I'm just trying to figure this
stuff out, but I exepected the client to simply send SOAP messages
to the service, which has already been deployed, hasn't it?  So what's 
with all these messages about "doDeploy" when I run the client?  (Note - 
at this point I still don't really understand

exactly what this client is doing - I'm just working through the
examples in the userguide.)

Any help would be appreciated!

Duncan

p.s. A comment to the userguide authors - suggest we move the
example of building a service BEFORE the example of building the
client, because obviously the client won't work until the service
is built and deployed.

p.s. Another comment for userguide authors - suggest the example
commands be given for both Windows and unix environments, rather than just 
Windows.


Here are the error messages I get when I try to run the client...

seafox:~/myservice> axis2.sh org.apache.axis2.axis2userguide.Client
 Using AXIS2_HOME:/home/duncant/axis2
 Using JAVA_HOME: /usr/local/java
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : addressing-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : soapmonitor-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  version.aar
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  sample-MyService.aar
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules logging module is invalid or has not been
deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:139)
at

Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
bee

Re: REST over GET support in Java clients?

[Philipp Leitner]

I am currently at version 1.1.1 . Do you think that I should upgrade to 
a more recent version?


/philipp

keith chapman schrieb:

Hi Philipp,

I guess the parameter ENABLE_REST_THROUGH_GET is not used anymore. Yes 
Axis2 supports REST. BTW which version are you using?


The following applies if you are using the nightlies or the 1.2 Release 
candidate.


Hope I answered your question...

See comments inline

On 4/16/07, *Philipp Leitner* <[EMAIL PROTECTED] 
> wrote:


Hi folks,

I am wondering if there is support for REST over HTTP GET for Java
clients in Axis2?

I know that there is the configuration parameter
Constants.Configuration.ENABLE_REST_THROUGH_GET , but so far I  could
not make it work.

I tried something like


Options options = new Options();
options.setTo(new EndpointReference(toEpr));


// Not really needed but better have it as it takes care of setting up 
default REST rules in case you miss something


options.setProperty(Constants.Configuration.ENABLE_REST,
Constants.VALUE_TRUE );


 // Not needed

options.setProperty(Constants.Configuration.ENABLE_REST_THROUGH_GET ,
Constants.VALUE_TRUE);



// Need to add the following bit of code

// The following will set the httpMethod to use (Supported methods are 
GET, PUT, DELETE and POST)
 options.setProperty (Constants.Configuration.HTTP_METHOD,   
Constants.Configuration.HTTP_METHOD_GET);


// Set the relavant contentType (Need to set the messagetype as well as 
its needed by the messageFormatters)
// Supported contentTypes are  "application/x-www-form-urlencoded", 
"multipart/form-data" and "application/xml";
 options.setProperty(Constants.Configuration.CONTENT_TYPE,   
HTTPConstants);
options.setProperty(Constants.Configuration.MESSAGE_TYPE,   
HTTPConstants);


ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(
OMAbstractFactory.getOMFactory().createOMElement("dummy", null));


so far. I figure that the "payload" of an GET request should be null or
something irrelevant, given that a GET request does not have a body to
contain any payload?

A quick check with tcpmon showed me that this code actually works, but
still (although I enabled
Constants.Configuration.ENABLE_REST_THROUGH_GET ) uses HTTP POST for the
request.

Can anybody tell me how I enable REST GET in the client (or if it is
even supported) ?

regards,
philipp



--
Philipp Wolfgang Leitner, Bakk.rer.soc.oec .
0225511
Vienna University of Technology

" A programmer is a person who passes as an exacting expert on the
basis of
being able to turn out, after innumerable punching, an infinite
series of
incomprehensible answers calculated with micrometric precisions from
vague
assumptions based on debatable figures taken from inconclusive documents
and carried out on instruments of problematical accuracy by persons of
dubious reliability and questionable mentality for the avowed
purpose of
annoying and confounding a hopelessly defenseless department that was
unfortunate enough to ask for the information in the first place.
 -- IEEE Grid newsmagazine "

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

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



Thanks,
Keith.

--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/


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

Logging module error with userguide examples

[Duncan Thomson]

I'm slogging my way through the axis2 userguide introduction
section, and I have some questions.  Hopefully there is someone on 
the list familiar with how the userguide examples were put 
together who can tackle these...


I've deployed axis2 (1.1.1) into apache tomcat (6).  I created and 
deployed the server example as described in the "Apache Axis2 
User's Guide -Building Services" section.  I created and deployed 
the client as described in the "Creating Clients" section.  The 
client and server are both based on the wsdl file in code listing 
5 in the userguide.


The client and server seem to work, however when I run the client
under axis2 I get a bunch of error messages related to undeployed 
logging modules (messages duplicated below).


I did some searching of the archives, and found some information 
about configuration things that have to be done to enable logging 
modules.  But...


1) At this point in the user guide logging modules have not even
been mentioned, and I don't think the example in question uses
them.  So... what is trying to load them?  Is this perhaps the way
the way axis2.war comes set up by default?  Did I inadvertently
turn logging on (or miss a step in which I was supposed to turn it
off)?

2) How do I either turn logging off or properly deploy it?

3) In general, what's with all the "Deploying module" stuff I'm
getting when I run the client?  I'm just trying to figure this
stuff out, but I exepected the client to simply send SOAP messages
to the service, which has already been deployed, hasn't it?  So 
what's with all these messages about "doDeploy" when I run the 
client?  (Note - at this point I still don't really understand

exactly what this client is doing - I'm just working through the
examples in the userguide.)

Any help would be appreciated!

Duncan

p.s. A comment to the userguide authors - suggest we move the
example of building a service BEFORE the example of building the
client, because obviously the client won't work until the service
is built and deployed.

p.s. Another comment for userguide authors - suggest the example
commands be given for both Windows and unix environments, rather 
than just Windows.


Here are the error messages I get when I try to run the client...

seafox:~/myservice> axis2.sh org.apache.axis2.axis2userguide.Client
 Using AXIS2_HOME:/home/duncant/axis2
 Using JAVA_HOME: /usr/local/java
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : addressing-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : soapmonitor-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  version.aar
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  sample-MyService.aar
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules logging module is invalid or has not been
deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:139)
at

Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:

Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service  sample-WsaMappingService.aar
done
echo! ... echo!
[EMAIL PROTECTED]
true
23872983





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

Re: [Axis2] How to add outbound headers?

[Michele Mazzucco]

http://ws.apache.org/axis2/1_1_1/modules.html

You can use the message context for that. The service saves information
into the message context (as properties). The out-handler adds those
information to the SOAP header.

Michele

On Mon, 2007-04-16 at 13:54 +0200, José Antonio Sánchez wrote:
> The problem is that only the service, reading the request message and
> invoking its business logic knows what it must be put in the header,
> so if I override the InOutMessageReceiver class I will not know what
> to put in the headers. Only the service implementation knows that but
> it can't put anything on the header.
> Anyway, does anybody know where can I find information about how to
> start a module/handler or something like that?
> 
> On 4/14/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> > AFAIK currently it's not possible to do that from your service
> > implementation class...
> >
> > You may need to write a handler to add those elements to the header of
> > the outgoing message and engage that handler in the outflow..
> >
> > On 4/13/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> > > Hello, I'm developing a service and I have to return some elements in
> > > the header when some operations of my service are invoked but I don't
> > > know how to do this. For the incoming message I can use
> > > MessageContext.getCurrentMessageContext().getEnvelope() but, how do I
> > > add a header to a response?
> > >
> > > --
> > > Saludos.
> > > José Antonio Sánchez
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 


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

SV: AXIS2 option to run HttpClient in non-multithreadded way?

[Peter Gylling Jørgensen]

Paul, 

This is the simple code, which cause the problems

// Setup trust
this.activateTrust();
if(DbserverStubTest.sslFactory == null) {
DbserverStubTest.fatalError = true;
Assert.fail();
return;
}
// Define new protocol
Protocol trustHttps = new Protocol("https", DbserverStubTest.sslFactory, 6001);
Protocol.registerProtocol("https", trustHttps);

// Loop joblist and delete jobs
for(int i=0; i -Oprindelig meddelelse-
> Fra: Paul Fremantle [mailto:[EMAIL PROTECTED] 
> Sendt: 16. april 2007 14:31
> Til: axis-user@ws.apache.org
> Emne: Re: AXIS2 option to run HttpClient in non-multithreadded way?
> 
> Peter
> 
> My understanding was that if you used the blocking model and your
> client code only made the second call after the first one returned
> then all should be fine.
> 
> Can you post your client code?
> 
> Paul
> 
> On 4/16/07, Peter Gylling Jørgensen <[EMAIL PROTECTED]> wrote:
> > Dear all,
> >
> > How can I tweak the HttpClient not to run in a 
> multithreaded environment? I discovered, that my AXIS2 based 
> java client initiates a second connection to the server 
> before the first connection is terminated, thus the server 
> hits a fatal error due to a now known bug in the server code.
> >
> > But I would like to be capable of continuing the 
> development of the client code while the bug is fixed in the 
> server part.
> >
> > \pgj
> > --
> > Peter Gylling Jørgensen
> > Modelling group, section of Oceanography
> > Royal Danish Administration of Navigation and Hydrography
> > Overgaden o. Vandet 62B DK-1023 København K
> > Phone: +45 32 68 96 85
> > Email: [EMAIL PROTECTED]
> > www: http://www.frv.dk/
> >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> -- 
> 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
> 
> -
> 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 option to run HttpClient in non-multithreadded way?

[Paul Fremantle]

Peter

My understanding was that if you used the blocking model and your
client code only made the second call after the first one returned
then all should be fine.

Can you post your client code?

Paul

On 4/16/07, Peter Gylling Jørgensen <[EMAIL PROTECTED]> wrote:

Dear all,

How can I tweak the HttpClient not to run in a multithreaded environment? I 
discovered, that my AXIS2 based java client initiates a second connection to 
the server before the first connection is terminated, thus the server hits a 
fatal error due to a now known bug in the server code.

But I would like to be capable of continuing the development of the client code 
while the bug is fixed in the server part.

\pgj
--
Peter Gylling Jørgensen
Modelling group, section of Oceanography
Royal Danish Administration of Navigation and Hydrography
Overgaden o. Vandet 62B DK-1023 København K
Phone: +45 32 68 96 85
Email: [EMAIL PROTECTED]
www: http://www.frv.dk/


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





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

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

Re: Axis2 and existing client code

[Jenn Chen]

Thank you all for your replies.  I'll give it a try.

Jennifer

- Original Message 
From: Sanjiva Weerawarana <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, April 16, 2007 3:09:24 AM
Subject: Re: Axis2 and existing client code

Thilina Gunarathne wrote:
> Axis2 and Axis1 to generate slightly different WSDL's for the same
> pojo service.. So the client's that depend on axis1 service (described
> by the wsdl) will not be able to communicate with the Axis2 service
> (described by Axis2 generated wsdl)...


If the service is the same (i.e., it accepts the same XML and returns the 
same XML) then changes in how that XML is described should not affect the 
clients. That is, what Thilina is saying is that we generate doc/lit style 
WSDL 1.1 documents by default and Axis1 I believe generates rpc/encoded 
style ones for POJOs. However, if they're backed by the same POJO then the 
client should continue to work unmodified because its sending and 
receiving the same XML as before.

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

-
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 

AXIS2 option to run HttpClient in non-multithreadded way?

[Peter Gylling Jørgensen]

Dear all,

How can I tweak the HttpClient not to run in a multithreaded environment? I 
discovered, that my AXIS2 based java client initiates a second connection to 
the server before the first connection is terminated, thus the server hits a 
fatal error due to a now known bug in the server code.

But I would like to be capable of continuing the development of the client code 
while the bug is fixed in the server part.

\pgj
--
Peter Gylling Jørgensen
Modelling group, section of Oceanography
Royal Danish Administration of Navigation and Hydrography 
Overgaden o. Vandet 62B DK-1023 København K 
Phone: +45 32 68 96 85
Email: [EMAIL PROTECTED]
www: http://www.frv.dk/ 
 

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

Re: [Axis2] How to add outbound headers?

[José Antonio Sánchez]

The problem is that only the service, reading the request message and
invoking its business logic knows what it must be put in the header,
so if I override the InOutMessageReceiver class I will not know what
to put in the headers. Only the service implementation knows that but
it can't put anything on the header.
Anyway, does anybody know where can I find information about how to
start a module/handler or something like that?

On 4/14/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:

AFAIK currently it's not possible to do that from your service
implementation class...

You may need to write a handler to add those elements to the header of
the outgoing message and engage that handler in the outflow..

On 4/13/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> Hello, I'm developing a service and I have to return some elements in
> the header when some operations of my service are invoked but I don't
> know how to do this. For the incoming message I can use
> MessageContext.getCurrentMessageContext().getEnvelope() but, how do I
> add a header to a response?
>
> --
> Saludos.
> José Antonio Sánchez
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

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





--
Saludos.
José Antonio Sánchez

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

Re: Data binding frameworks that allow backwards compatible schema changes?

[Josh]

Amila,

If I configure a databinding approach to work with the following XML:


   John
   Doe


Which databinding approaches will not break if I pass in the following XML:


   John
   Doe
   25
   M


While most client applications may not want to interpret the new
information, I want to make sure that I can recommend a binding approach
that does not cause a ripple effect when new items are added to the schema.
Does this clarify what I am looking for?

-Joshua


On 4/16/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:




On 4/14/07, Josh <[EMAIL PROTECTED]> wrote:
>
> All,
>
> I am looking to determine which client side data binding choices
> (castor, jibx, jaxb etc) allow backwards compatible schema changes (eg
> addition of a new field) without throwing an exception.
>

What you exactly mean by backword compatible schema?
e g.  if you add a new element to a complex type with minOccurs 0 then
this should work properly with  the requests you got earlier as well. But in
this case it the way you write schema and it has nothing to do with the
databinding frame work as far as it correctly interpret the schema.


 I am hoping to recommend some solutions to my clients that would allow me
> to make backward compatible schema changes without causing a ripple effect.
> Has anyone come across this information?
>
> Regards,
>
> Joshua
>



--
Amila Suriarachchi,
WSO2 Inc.

Re: REST over GET support in Java clients?

[keith chapman]

Hi Philipp,

I guess the parameter ENABLE_REST_THROUGH_GET is not used anymore. Yes Axis2
supports REST. BTW which version are you using?

The following applies if you are using the nightlies or the 1.2 Release
candidate.

Hope I answered your question...

See comments inline

On 4/16/07, Philipp Leitner <[EMAIL PROTECTED]> wrote:


Hi folks,

I am wondering if there is support for REST over HTTP GET for Java
clients in Axis2?

I know that there is the configuration parameter
Constants.Configuration.ENABLE_REST_THROUGH_GET , but so far I  could
not make it work.

I tried something like


Options options = new Options();
options.setTo(new EndpointReference(toEpr));



// Not really needed but better have it as it takes care of setting up
default REST rules in case you miss something

options.setProperty(Constants.Configuration.ENABLE_REST,

Constants.VALUE_TRUE);



// Not needed

options.setProperty(Constants.Configuration.ENABLE_REST_THROUGH_GET,

Constants.VALUE_TRUE);




// Need to add the following bit of code

// The following will set the httpMethod to use (Supported methods are GET,
PUT, DELETE and POST)
options.setProperty(Constants.Configuration.HTTP_METHOD,
Constants.Configuration.HTTP_METHOD_GET);

// Set the relavant contentType (Need to set the messagetype as well as its
needed by the messageFormatters)
// Supported contentTypes are  "application/x-www-form-urlencoded",
"multipart/form-data" and "application/xml";
options.setProperty(Constants.Configuration.CONTENT_TYPE,
HTTPConstants);
options.setProperty(Constants.Configuration.MESSAGE_TYPE,
HTTPConstants);

ServiceClient sender = new ServiceClient();

sender.setOptions(options);
OMElement result = sender.sendReceive(
OMAbstractFactory.getOMFactory().createOMElement("dummy", null));


so far. I figure that the "payload" of an GET request should be null or
something irrelevant, given that a GET request does not have a body to
contain any payload?

A quick check with tcpmon showed me that this code actually works, but
still (although I enabled
Constants.Configuration.ENABLE_REST_THROUGH_GET) uses HTTP POST for the
request.

Can anybody tell me how I enable REST GET in the client (or if it is
even supported) ?

regards,
philipp



--
Philipp Wolfgang Leitner, Bakk.rer.soc.oec.
0225511
Vienna University of Technology

" A programmer is a person who passes as an exacting expert on the basis
of
being able to turn out, after innumerable punching, an infinite series of
incomprehensible answers calculated with micrometric precisions from vague
assumptions based on debatable figures taken from inconclusive documents
and carried out on instruments of problematical accuracy by persons of
dubious reliability and questionable mentality for the avowed purpose of
annoying and confounding a hopelessly defenseless department that was
unfortunate enough to ask for the information in the first place.
 -- IEEE Grid newsmagazine "

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



Thanks,
Keith.

--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

Axis2 1.1.1 and HTTPS problem

[Ognjen Blagojevic]

Hi all,

When I try to call Axis2-generated client for Axis2 web service over 
HTTPS, an exception is thrown:


java.lang.IllegalStateException: Can't overwrite cause.

Here is source:

Korona2Stub stubSsl = *new* 
Korona2Stub("https://127.0.0.1:8443/axis2/services/korona2";);

Korona2Stub.TestSnimi reqSsl = *new* Korona2Stub.TestSnimi();
reqSsl.setTestString("Test string.");
reqSsl.setTestInteger(1); // Test integer
Korona2Stub.TestSnimiResponse res1Ssl = stubSsl.testSnimi(req); // 
Exception thrown here.

System./out/.println(res1Ssl.get_return());

Same code works fine with HTTP on 8080. Is there anything else I need to 
do to make HTTPS work?


I'm using Tomcat 6.0.10 with HTTPS connector enabled, and I can call 
REST version of my web service from Firefox:

https://127.0.0.1/axis2/rest/korona2/testSnimi?testString=test&testInteger=1

Below is the full stack trace:

Exception in thread "main" java.lang.IllegalStateException: Can't 
overwrite cause

   at java.lang.Throwable.initCause(Throwable.java:320)
   at com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
   at com.ctc.wstx.exc.WstxException.(WstxException.java:46)
   at com.ctc.wstx.exc.WstxIOException.(WstxIOException.java:16)
   at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
   at 
org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:115)
   at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:420)
   at 
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:190)
   at 
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:232)
   at 
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
   at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
   at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
   at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
   at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
   at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
   at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
   at 
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541)
   at 
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119)
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)
   at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)

   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
   at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)

   at orka.generated.Korona2Stub.testSnimi(Korona2Stub.java:850)
   at orka.Klijent.main(Klijent.java:149)


Regards,
Ognjen

[Axis2] Problems with .NET Service and Axis2 Client

[Florian Wachs]

Hello all,

I`m trying to use a simple .NET Service with Axis2. It´s a simple 
HelloWorld Service. After generating the stub with wsdl2java, I tried to 
invoke the service, but I´m getting the following errors. I also 
implemented the same service with Axis2 and created a Axis2 service and 
it worked. I´m quite confused, because weeks ago it worked with the same 
Axis / NET versions without any problem.

Maybe someone of you has a clue.

Thanks
Florian

org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad 
Request'; nested exception is:
org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad 
Request'; nested exception is:
org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad 
Request'; nested exception is:

org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad Request'
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227)

at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at 
de.fhrosenheim.webservices.QuizServiceStub.holeFrage(QuizServiceStub.java:152)

at de.fhrosenheim.ws.quizclient.Client.main(Client.java:33)
Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '400' - 
'Bad Request'; nested exception is:

org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad Request'
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:344)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)

... 5 more
Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '400' - 
'Bad Request'
at 
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:144)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)

... 6 more


org.apache.axis2.AxisFault: Software caused connection abort: recv 
failed; nested exception is:
java.net.SocketException: Software caused connection abort: recv failed; 
nested exception is:
org.apache.axis2.AxisFault: Software caused connection abort: recv 
failed; nested exception is:

java.net.SocketException: Software caused connection abort: recv failed
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227)

at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at 
de.fhrosenheim.webservices.QuizServiceStub.holeFrage(QuizServiceStub.java:152)

at de.fhrosenheim.ws.quizclient.Client.main(Client.java:33)
Caused by: org.apache.axis2.AxisFault: Software caused connection abort: 
recv failed; nested exception is:

java.net.SocketException: Software caused connection abort: recv failed
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:344)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)

... 5 more
Caused by: java.net.SocketException: Software caused connection abort: 
recv failed

at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at 
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at 
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
at 
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at 
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541)
at 
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)

... 6 more



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

[AXIS2] NumberFormatException on parsing null date with hot deployed RPC service

[Nicolae Marasoiu]

Hi;

In the auto-generated wsdl, I have such a type entry inside a
xs:complexType:


I get:
java.lang.NumberFormatException: badDateTime00
at
org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeCalendar(Simpl
eTypeMapper.java:214)
at
org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObjec
t(SimpleTypeMapper.java:93)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:291)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:299)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:247)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:296)
at
org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:557)
at
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:507
)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:446)
at
org.apache.axis2.rpc.receivers.RPCUtil.processRequest(RPCUtil.java:109)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(
RPCInOnlyMessageReceiver.java:84)

How can I make axis generate nillable="true" on these elements also? Or is
it part of xs:dateTime definition?
The exception above is given precisely at asserting not null and not empty
value.
On the wire:
http://www.w3.org/2001/XMLSchema-instance";
nil:nil="true" />.

Another problem I get with hot deployed RPC service is when I have null
array properties. For these nillable=true is generated in wsdl, but still:
org.apache.axiom.om.OMException: java.lang.NullPointerException
 at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:194)
 at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:318)
 at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:632)
 at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:599)
 at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:117)
 at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:249)
 at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:202)
 at org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:97)
 at org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:192)
 at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMes
sageReceiver.java:136)
 at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Abstract
InOutSyncMessageReceiver.java:39)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
 at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:328)
 at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
 at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1
212)
 at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1
173)
 at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.
java:92)
 at CatchFilter.doFilter(CatchFilter.java:21)
 at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstance
Wrapper.java:142)
 at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.
java:77)
 at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.
java:626)
 at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServl
etWrapper.java:80)
 at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
 at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
 at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(Ht
tpInboundLink.java:421)
 at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(Ht
tpInboundLink.java:367)
 at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.j
ava:276)
 at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscrimin
aters(NewConnectionInitialReadCallback.java:201)
 at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewCon
nectionInitialReadCallback.java:103)
 at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManage
r.java:548)
 at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java
:601)
 at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java
:934)
 at
com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.jav
a:1021)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Caused by: java.lang.NullPointerException
 at
org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:135)
 at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProp
erties(ADB

RE: [axis2] Specification about the service.xml and ANT taskdef

[Hardi Sukrisman]

Specification for services.xml:
 
Through searching in the ws02 website, I finally found the URL.
Probably this is useful for the other begginers:
 
http://ws.apache.org/axis2/1_1_1/resources/schemas/
 
However there is a note:
Submitted by Davanum Srinivas on February 5, 2007 - 12:03.

Tom,

Unfortunately, the schemas for those 2 were incomplete when we
published Axis2 1.1.1. Do you have a specific question that we can
asnwer? Sorry for the delay in reply.

thanks,
dims

 
The original entry can be read in http://wso2.org/forum/thread/599
 
 



From: Hardi Sukrisman [mailto:[EMAIL PROTECTED] 
Sent: Freitag, 13. April 2007 17:19
To: axis-user@ws.apache.org
Subject: [axis2] Specification about the service.xml and ANT taskdef


Hi,
 
I've just start to use Axis2 and I have problem on finding the
specification of service.xml and the ANT taskdef available for axis.
Can anyone tell me the URL of  the specification??
 
I need the syntax definition e.g for defining service group, etc.
 
Thank you.
 
Regards,
 
Hardi

REST over GET support in Java clients?

[Philipp Leitner]

Hi folks,

I am wondering if there is support for REST over HTTP GET for Java 
clients in Axis2?


I know that there is the configuration parameter 
Constants.Configuration.ENABLE_REST_THROUGH_GET , but so far I  could 
not make it work.


I tried something like


Options options = new Options();
options.setTo(new EndpointReference(toEpr));
options.setProperty(Constants.Configuration.ENABLE_REST,
   Constants.VALUE_TRUE); 
options.setProperty(Constants.Configuration.ENABLE_REST_THROUGH_GET,

   Constants.VALUE_TRUE);

ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(
   OMAbstractFactory.getOMFactory().createOMElement("dummy", null));


so far. I figure that the "payload" of an GET request should be null or 
something irrelevant, given that a GET request does not have a body to 
contain any payload?


A quick check with tcpmon showed me that this code actually works, but 
still (although I enabled 
Constants.Configuration.ENABLE_REST_THROUGH_GET) uses HTTP POST for the 
request.


Can anybody tell me how I enable REST GET in the client (or if it is 
even supported) ?


regards,
philipp



--
Philipp Wolfgang Leitner, Bakk.rer.soc.oec.
0225511
Vienna University of Technology

" A programmer is a person who passes as an exacting expert on the basis of
being able to turn out, after innumerable punching, an infinite series of
incomprehensible answers calculated with micrometric precisions from vague
assumptions based on debatable figures taken from inconclusive documents
and carried out on instruments of problematical accuracy by persons of
dubious reliability and questionable mentality for the avowed purpose of
annoying and confounding a hopelessly defenseless department that was
unfortunate enough to ask for the information in the first place.
-- IEEE Grid newsmagazine "

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

[Axis2] Complex types with extension base and generated Axis2 classes

[Volker Honds]

Hi there,

I hope you can help me.
I am using Axis2 1.1.1. and running into problems using the generated Axis2
classes from my xml schema:

1. xml schema (snippet):

...

  

  
  

  

...


2. the generated Java class has a getter and setter for the named attribute
"id".

public class MyType implements org.apache.axis2.databinding.ADBBean {
...
protected org.apache.axis2.databinding.types.URI localId ;

/**
 * field for Id This was an Attribute!
 */
protected org.apache.axis2.databinding.types.URI localId;
/**
 * Auto generated getter method
 *
 * @return org.apache.axis2.databinding.types.URI
 */
public org.apache.axis2.databinding.types.URI getId() {
  return localId;
}
/**
 * Auto generated setter method
 *
 * @param param
 *Id
 */
public void setId(org.apache.axis2.databinding.types.URI param) {
this.localId = param;
}
...


3.  But I am missing a getter and setter to handle the content (of type
anyType). There is no other setter at all.
What I am doing wrong? Thank a lot in advance,
Volker
   
 Volker Honds   IBM Deutschland GmbH   
 IT Specialist  Gustav Heinemann Ufer  
 AS Delivery Application120-122
 Innovation 50968 Köln   
 Global Business Services   Deutschland
 (GBS) 
   
   
 IBM Deutschland GmbH  
 Vorsitzender des  
 Aufsichtsrats: Hans Ulrich
 Maerki , Geschäftsführung:
 Martin Jetter 
 (Vorsitzender), Rudolf
 Bauer, Christian Diedrich,
 Christoph Grandpierre,
 Matthias Hartmann, Andreas
 Kerstan   
 Sitz der Gesellschaft:
 Stuttgart -   
 Registergericht:  
 Amtsgericht Stuttgart, HRB
 14562 - WEEE-Reg.-Nr. DE  
 99369940  
   






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

[axis2] Calendar serialization to xsd:dateTime bug?

[Tore . Larsen]

Hei,
I'm using Axis 1.1.1 and I see that the Calendar serializes into 
2007-04-16T10:31:29.162+0200 when it should be 
2007-04-16T10:31:29.162+02:00 (missing the last colon) according to 
XMLSchema recommandation http://www.w3.org/TR/xmlschema11-2/#dateTime . Or 
am I wrong here?

Soap message example:

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


http://webservices.norgesgruppen.no/butikkinfo/generatedtypes/responsetypes";>
 2007-04-16T10:31:29.162+0200


 18364
 2007-03-01T00:00:00.000+0100
...






Regards from Tore Larsen

[AXIS2] codegen using ADB : skeleton uses xsd element and not type

[Ephemeris Lappis]

Hello.

 

If I'm not wrong, the generated skeleton, using the ant codegen with ADB
data binding, relies on the schema elements that are mapped to the WSDL
messages parts, and not the schema types as I was thinking. It's not a real
problem, since the generated element classes give an access to the wrapped
raw type.

 

If I remember well, Axis 1 generated server code uses types.

 

Is it a normal behavior, or did I make something bad ?

Thanks.

 

--

Ephemeris Lappis

 

Re: Axis2 and existing client code

[Sanjiva Weerawarana]

Thilina Gunarathne wrote:

Axis2 and Axis1 to generate slightly different WSDL's for the same
pojo service.. So the client's that depend on axis1 service (described
by the wsdl) will not be able to communicate with the Axis2 service
(described by Axis2 generated wsdl)...



If the service is the same (i.e., it accepts the same XML and returns the 
same XML) then changes in how that XML is described should not affect the 
clients. That is, what Thilina is saying is that we generate doc/lit style 
WSDL 1.1 documents by default and Axis1 I believe generates rpc/encoded 
style ones for POJOs. However, if they're backed by the same POJO then the 
client should continue to work unmodified because its sending and 
receiving the same XML as before.


Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

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