date:20070802

xs:anyType deserialize problem in Axis2 version 1.2

2007-08-02 Thread Ken Tam

Hi all,

I've exposed a POJO web service with a method which returns another POJO
containing a member of type Object. This translates to xs:anyType in the
WSDL. I wrote an AXIS2 client to consume this web service. The value of the
Object is null after the deserialization process. The actual value of the
Object member is a simple type (String, Float and Integer). Is there another
way to instruct the WSDL generation process to use a different value? Is
this a deserialization issue?

Thanks,
Ken

Developing doc/lit Axis service

2007-08-02 Thread Anil Kumar Tappetla

Hi,

 

   I need assistance - documentation to start with - to develop a doc/lit
Axis SOAP service (using custom serializer/deserializers). Can someone
please point to an appropriate resource?

 

Thanks,

Anil

 

  _  

From: Anil Kumar Tappetla [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 28, 2007 11:50 AM
To: axis-user@ws.apache.org
Subject: Documentation on customization

 

Hi,

 

   I am faced with developing an Axis 1.2 service that requires custom
deserialization/serialization. There does not seem to be an available
documentation on developing such services, or is there? Can someone please
point me to an appropriate resource in this respect?

 

Regards,

Anil

Newbie question about using axis as webservice client

2007-08-02 Thread DelGurth

Hi,

I recently stated using axis as my web service client. I've used the
wsdl2java tool (via Eclipse) to generate the client code based on the
wsdl file of the service.

Now the web service changed, it contains a new field, and my client
application doesn't work anymore. Is there a way to make my client
ignore fields that are unknown to it?

I tried finding an answer in the client-side axis documentation, but I
can't find it, unfortunately. That's why I end up here.

Regards,
Wessel van Norel

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

Re: Problem with Loading?

2007-08-02 Thread keith chapman

Hi,

Yes it is a classpath problem. You have set your AXIS2_HOME variable
correctly so that it can locate the Axis2 jars.

Thanks,
Keith.


On 8/3/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am stumped again and yet I think I am really close so ... I am trying to
> write an axis2 client for my new sample axis2 service.
> When I run the client I get:
>
> a99-run.myclient:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/axis2/client/Stub
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass (ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(
> SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$000 (URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java :188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at org.mlbissonnette.quote.client.RandomQuoteClient.main(
> RandomQuoteClient.java:35)
>
>
>
> RandomQuoteWSStub.class exists in build directory
>
> I get the same error message when I try run outside of ant usin g
>
> java -jar myclient.jar
>
> I'm using axis2  1.3 RC2.  Is this a classpath problem or did I not
> generate the code correctly?
>
> Any thought would be appreciated?
>
>
>
>



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

Err: SubElement error return

2007-08-02 Thread jnet2000


Hi All,


you can help me, I have a problem with a simple  ws.

using the client, response me with exception "

java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
subelement return

"
In my ws, I have specified that the output he will have to call  
itself “result”  through the WebResult annotation. In the wsdl I have  
indicated the output with the same name, “result”.


axis2 answer generates me in automatic rifle not taking in  
consideration the wsdl, why?!


On what this behavior depends?

Depends on one wrong configuration of Axis2? It depends on a wrong  
configuration of the services.xml, or from as I have written the ws?



I'm currently using a Sun Application Server 9, JAX-WS , AXIS2 1.3,  
JDK 1.6


please, you help me

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

Re: wsdl 2.0 process

2007-08-02 Thread keith chapman

Hi,

There is a tool hosted at
http://tools.wso2.org:19762/wservices/WSDLConverter/ which can be used
pretty easily to convert a WSDL 1.1 to WSDL 2.0.

Thanks,
Keith.

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am converting some 1.1 wsdl's to 2.0 and I am very pleased with using
> axis2.
>
> First I went to http://www.w3.org/2006/02/WSDLConvert.html and tried their
> online converter.
> It didn't work for me but I might have had a bad character in the file.
>
> Instead, I used their "XSLT 2.0 stylesheet used for the 
> conversion"
> with XMSpy and created
> a converted wsdl.
>
> Then I fed the converted wsdl's into axis2's wsdl2java batch file and ran
> it successfully.
>
> Various people have been asking about how to validate their 2.0 wsdl.
> This worked much
> better for me than trying to use my converted wsdl, with XMLSpy or Stylus
> Studio, and the
> wsdl2.0 schema.
>
> Thanks again Axis2 folks.
>



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

Re: Connection Reset erroe

2007-08-02 Thread Deepal jayasinghe

Please create a JIRA and attach the client code , and in the meantime
give us the environment that you used.

Thanks
Deepal
> We have created the client for the web service that other team has created
> for it's utilization.
>
> But the client works on one of our developer's system but when i run the
> same code from different system it throws following exception
>
> com.platform.intg.pim.SessionMgmtException: org.apache.axis2.AxisFault:
> Connection reset
>   at
> com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:90)
>   at
> com.deloitte.platform.intg.pim.ProfileUpdateWSProxyEndpointTest.testUpdateUser(ProfileUpdateWSProxyEndpointTest.java:32)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>   at java.lang.reflect.Method.invoke(Unknown Source)
>   at junit.framework.TestCase.runTest(TestCase.java:154)
>   at junit.framework.TestCase.runBare(TestCase.java:127)
>   at junit.framework.TestResult$1.protect(TestResult.java:106)
>   at junit.framework.TestResult.runProtected(TestResult.java:124)
>   at junit.framework.TestResult.run(TestResult.java:109)
>   at junit.framework.TestCase.run(TestCase.java:118)
>   at junit.framework.TestSuite.runTest(TestSuite.java:208)
>   at junit.framework.TestSuite.run(TestSuite.java:203)
>   at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
>   at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
>   at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
>   at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
>   at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.apache.axis2.AxisFault: Connection reset
>   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)
>   at
> com.deloitte.platform.intg.pim.ws.profile.PIMPeopleManagementServicesSoapStud.UpdatePerson(PIMPeopleManagementServicesSoapStud.java:1182)
>   at
> com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.callWebService(ProfileMgmtUpdateWSProxyEndpoint.java:148)
>   at
> com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:87)
>   ... 19 more
> Caused by: org.apache.axis2.AxisFault: Connection reset
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:314)
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
>   ... 25 more
> Caused by: org.apache.axis2.AxisFault: Connection reset
>   at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
>   at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
>   at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
>   ... 26 more
> Caused by: java.net.SocketException: Connection reset
>   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(AbstractHTT

Re: Problem with Loading?

2007-08-02 Thread Deepal jayasinghe

Do you have all the relevant axis2 jar files.

Thanks
Deepal
> Hi,
>  
> I am stumped again and yet I think I am really close so ... I am
> trying to write an axis2 client for my new sample axis2 service.
> When I run the client I get:
>
> a99-run.myclient:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/axis2/client/Stub
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass (ClassLoader.java:620)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$000 (URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java :188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at
> org.mlbissonnette.quote.client.RandomQuoteClient.main(RandomQuoteClient.java:35)
>
>  
>
> RandomQuoteWSStub.class exists in build directory
>
> I get the same error message when I try run outside of ant usin g
>
> java -jar myclient.jar
>
> I'm using axis2  1.3 RC2.  Is this a classpath problem or did I not
> generate the code correctly?
>
> Any thought would be appreciated?
>
>
>  
>


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

Re: Transport Level Session Management -- is this .NET interop Issue?

2007-08-02 Thread Deepal jayasinghe

Hi Shalab ,
>
> Hello,
>
> I have a question about session management.
>
> My Axis client is a consumer of .NET service, I am noticing the
> following interoperability issue. The Service is returning Cookie as
>
> *Set-Cookie: ASP.NET_SessionId=cml1mh45lc3yzf55flravg45; path=/; HttpOnly*
>
According the the servlet specification it should send the JSESSIONID ,
anyway Axis2 has a way to deal with this as well. So when you send the
request set the following property into the option.
 Options options = new Options();
options.setProperty(Constants.CUSTOM_COOKIE_ID,"ASP.NET_SessionId");

That will definitely solve the issue. You have to use Axis2 1.3 RC1 or
RC2 for this case.

Thanks
Deepal

> And this is not getting processed by Axis client.
>
> I have also created a test Axis service where I have enabled transport
> level sessions. The Cookie gets set here as:
>
> *Set-Cookie: JSESSIONID=0E2ACECB8CF2E5E91F55B5F8E6CEA150; Path=/axis2*
>
> In this case, Axis client is able to return back the sessionid to the
> Axis Service.
>
> Appreciate any input on how to work around this issue.
>
> Does Axis provide any API to inspect the incoming Cookies, and set
> outgoing Cookies explicitly?
>
> Thanks
>
> Shalab
>
>  
>


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

Re: non-repudiation with signature using rampart 1.2

2007-08-02 Thread Dimuthu

Hi Pavan,

I think this issue is related to
https://issues.apache.org/jira/browse/RAMPART-10

Regards,
Dimuthu

On Thu, 2007-08-02 at 23:29 -0400, Pavan Madiraju wrote:
> Hi,
> I am trying to implement  non-repudiation with signature with  Axis2
> 1.2  &  Rampart 1.2.
> 
> Here is my service.xml enabling rampart
> 
>   
>   
>   
>   Signature
>   
> service.properties
>   
>   
> 
> I have placed my service.properties file in
> 
>   
> \base_v61\profiles\AppSrv01\installedApps\NW815856Node02Cell\axis2_war.ear\axis2.war\WEB-INF\classes
> folder
> 
> service.properties contents are
> org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
> org.apache.ws.security.crypto.merlin.keystore.type=jks
> org.apache.ws.security.crypto.merlin.keystore.password=servertrust
> org.apache.ws.security.crypto.merlin.keystore.alias=wasclient
> org.apache.ws.security.crypto.merlin.alias.password=servertrust
> org.apache.ws.security.crypto.merlin.file=servertrust.jks
> 
> I am getting the following error
> 
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R at
> com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)
> [8/2/07 8:28:10:326 EDT] 0027 SystemErr R Caused by:
> org.apache.ws.security.components.crypto.CredentialException: Failed
> to load credentials. Inner Exception: [DerInputStream.getLength():
> lengthTag=109, too big.]
>   at 
> org.apache.ws.security.components.crypto.AbstractCrypto.load(AbstractCrypto.java:141)
>   at 
> org.apache.ws.security.components.crypto.AbstractCrypto.(AbstractCrypto.java:97)
>   at 
> org.apache.ws.security.components.crypto.Merlin.(Merlin.java:65)
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 
> 
> 
> 
>   at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
>   at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
>   at 
> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
>   at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
>   at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)
> 
> [8/2/07 8:28:10:346 EDT] 0027 SystemErr R at
> org.apache.ws.security.components.crypto.AbstractCrypto.load(AbstractCrypto.java:141)
> [8/2/07 8:28:10:346 EDT] 0027 SystemErr R at
> org.apache.ws.security.components.crypto.AbstractCrypto.(AbstractCrypto.java:97)
> [8/2/07 8:28:10:346 EDT] 0027 SystemErr R at
> org.apache.ws.security.components.crypto.Merlin.(Merlin.java:65)
> [8/2/07 8:28:10:346 EDT] 0027 SystemErr R ... 40 more
> [8/2/07 8:28:10:366 EDT] 0027 SystemErr R
> java.lang.InstantiationException:
> org.apache.ws.security.components.crypto.Merlin
> [8/2/07 8:28:10:366 EDT] 0027 SystemErr R at
> java.lang.Class.newInstanceImpl(Native Method)
> [8/2/07 8:28:10:366 EDT] 0027 SystemErr R at
> java.lang.Class.newInstance(Class.java:1263)
> [8/2/07 8:28:10:366 EDT] 0027 SystemErr R at
> org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:219)
> [8/2/07 8:28:10:366 EDT] 0027 SystemErr R at
> org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:176)
> [8/2/07 8:28:10:366 EDT] 0027 Sys

non-repudiation with signature using rampart 1.2

2007-08-02 Thread Pavan Madiraju

Hi,
I am trying to implement  non-repudiation with signature with  Axis2
1.2  &  Rampart 1.2.

Here is my service.xml enabling rampart




Signature

service.properties



I have placed my service.properties file in

  
\base_v61\profiles\AppSrv01\installedApps\NW815856Node02Cell\axis2_war.ear\axis2.war\WEB-INF\classes
folder

service.properties contents are
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=servertrust
org.apache.ws.security.crypto.merlin.keystore.alias=wasclient
org.apache.ws.security.crypto.merlin.alias.password=servertrust
org.apache.ws.security.crypto.merlin.file=servertrust.jks

I am getting the following error

[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R   at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)
[8/2/07 8:28:10:326 EDT] 0027 SystemErr R Caused by:
org.apache.ws.security.components.crypto.CredentialException: Failed
to load credentials. Inner Exception: [DerInputStream.getLength():
lengthTag=109, too big.]
at 
org.apache.ws.security.components.crypto.AbstractCrypto.load(AbstractCrypto.java:141)
at 
org.apache.ws.security.components.crypto.AbstractCrypto.(AbstractCrypto.java:97)
at 
org.apache.ws.security.components.crypto.Merlin.(Merlin.java:65)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)




at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
at 
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)

[8/2/07 8:28:10:346 EDT] 0027 SystemErr R   at
org.apache.ws.security.components.crypto.AbstractCrypto.load(AbstractCrypto.java:141)
[8/2/07 8:28:10:346 EDT] 0027 SystemErr R   at
org.apache.ws.security.components.crypto.AbstractCrypto.(AbstractCrypto.java:97)
[8/2/07 8:28:10:346 EDT] 0027 SystemErr R   at
org.apache.ws.security.components.crypto.Merlin.(Merlin.java:65)
[8/2/07 8:28:10:346 EDT] 0027 SystemErr R   ... 40 more
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R
java.lang.InstantiationException:
org.apache.ws.security.components.crypto.Merlin
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R   at
java.lang.Class.newInstanceImpl(Native Method)
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R   at
java.lang.Class.newInstance(Class.java:1263)
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R   at
org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFactory.java:219)
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R   at
org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFactory.java:176)
[8/2/07 8:28:10:366 EDT] 0027 SystemErr R   at
org.apache.ws.security.handler.WSHandler.loadSignatureCrypto(WSHandler.java:347)


Did anyone encounter this error before ?

Please help.

Thanks,
Pavan

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

Re: FW: java.lang.NumberFormatException

2007-08-02 Thread Davanum Srinivas

Can you please log and bug and upload all relevent files and sample code?

thanks,
dims

On 8/2/07, Matthew Bailey <[EMAIL PROTECTED]> wrote:
>
>
> STILL STUCK :-/
>
> I'm not totally clear on how to generate the files using scomp, or what to
> do with them after I have generated them, so here is what I tried.
>
> ##
>
> #axis2-1.3-RC2#
> ##
> generated using scomp directly
> >scomp -src src -out xmltypes.jar -javasource 1.4 IntegrationServices.wsdl
>
> * Coppied the source files to the src directory of my service.
> * Extracted the schemaorg_apache_xmlbeans folder (and contents) from
> xmltypes.jar and replaced the
> /resources/schemaorg_apache_xmlbeans folder with this one.
> (??? not sure that it should replace the entire folder, may want to regen
> this folder using axis2 and then merge these folders) (on another attempt
> merged snapshot generated schemaorg_apache_xmlbeans with the newly generated
> one with the same results)
> * Deleted build files for a clean build, ran ant
> * Coppied aar file to axis2/WEB-INF/service
> * Coppied XBeans-packaged.jar to axis2/WEB-INF/lib
> * Started webserver
>
> SOAP MSG
> -
>
>
>  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
> 
>   
>
>
>
>
>
>
>
> http://localhost:7001/axis2/"/>
> Axis2 :: Internal server error
>  type="text/css"/>
> 
>   
>
>   
> 
>   
>  alt=""/>
>  src="axis2-web/images/axis_l.jpg" alt=""/>
>   
> 
> 
>   
> 
>   Internal server error
>   
>   
>   
>   
> 
>   
>href="axis2-web/index.jsp">home
> 
> 
> 
>   
> 
>   
>   
> Copyright © 1999-2006, The Apache
> Software FoundationLicensed under the 
> href="http://www.apache.org/licenses/LICENSE-2.0";>Apache
> License, Version 2.0.
>   
> 
>   
>  
>   
> 
>   
> 
> --
> EXCEPTION
> --
> Aug 2, 2007 12:19:56 PM
> org.apache.axis2.transport.http.AxisServlet doPost
> SEVERE: java.lang.ExceptionInInitializerError
>
> <[ServletContext(id=6079374,name=axis2,context-path=/axis2)]
> Servlet failed with Exception
> java.lang.NullPointerException
>  at
> org.apache.axis2.transport.http.AxisServlet.doPost(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(AxisServlet.java:170)
>  at
> javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:760)
>  at
> javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
>  at
> weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:1006)
>  at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
>  at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
>  at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6718)
>  at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
>  at
> weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:121)
>  at
> weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3764)
>  at
> weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2644)
>  at
> weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
>  at
> weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
>  at
> java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown
> Source)
>
>
>
>
>
>
> 
> I have attempted to generate the code w/ scomp, the steps I took to do this
> follow:
>
> >scomp -src xmlbeansrc IntegrationServices.wsdl
>
> I then coppied the source files that were generated to the service src
> directory, deleted the build files and did a build. Then I placed the
> Services.aar file into the axis2/WEB-INF/services directory and the
> XBeans-packaged.jar into the axis2/WEB-INF/lib directory.
>
> Then I used soapUI to post a validated request to the service.
>
> ##
> #axis2-1.2#
> ##
> Server:
> Soap response:
> --
>
>

RE: Transport error: 400 Error: Bad Request

2007-08-02 Thread Jorge Fernandez

Hi David,

There is some working around it. See 
https://issues.apache.org/jira/browse/AXIS2-2845

Regards, 

Jorge Fernández

David Robertson <[EMAIL PROTECTED]> escribió: I'm wondering if something 
changed in the way a client handles SOAP 
faults between Axis2 1.1.1 and Axis2 1.2.  Previously if a fault message 
was thrown, the client would receive the fault message.  As of 1.2, 
we've always gotten the error in the subject line when a fault is thrown 
on the server.  I believe that what comes back to the client is the 
correct message with the fault.  This still occurs with the nightly 
build of 1.3.  (We have modified our skeleton and exception classes to 
follow the latest code generation.)  Any help would be greatly appreciated.

-David Robertson



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



   
-

Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.

RE: Transport error: 400 Error: Bad Request

2007-08-02 Thread Merritt, Norris

I suspect the server you are talking to is returning an ordinary HTTP
400 Bad request, not a SOAP fault. The HTTP status code must be 500 for
all SOAP faults. Services can sometimes respond with 400 Bad Request or
401 Unauthorized in addition to actual SOAP faults with code 500.

-Original Message-
From: David Robertson [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 02, 2007 3:36 PM
To: axis-user@ws.apache.org
Cc: Andrew Lake
Subject: Transport error: 400 Error: Bad Request

I'm wondering if something changed in the way a client handles SOAP 
faults between Axis2 1.1.1 and Axis2 1.2.  Previously if a fault message

was thrown, the client would receive the fault message.  As of 1.2, 
we've always gotten the error in the subject line when a fault is thrown

on the server.  I believe that what comes back to the client is the 
correct message with the fault.  This still occurs with the nightly 
build of 1.3.  (We have modified our skeleton and exception classes to 
follow the latest code generation.)  Any help would be greatly
appreciated.

-David Robertson

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

Transport error: 400 Error: Bad Request

2007-08-02 Thread David Robertson

I'm wondering if something changed in the way a client handles SOAP 
faults between Axis2 1.1.1 and Axis2 1.2.  Previously if a fault message 
was thrown, the client would receive the fault message.  As of 1.2, 
we've always gotten the error in the subject line when a fault is thrown 
on the server.  I believe that what comes back to the client is the 
correct message with the fault.  This still occurs with the nightly 
build of 1.3.  (We have modified our skeleton and exception classes to 
follow the latest code generation.)  Any help would be greatly appreciated.


-David Robertson



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

Transport Level Session Management -- is this .NET interop Issue?

2007-08-02 Thread Shalab Goel

Hello,

I have a question about session management. 

My Axis client is a consumer of .NET service, I am noticing the
following interoperability issue. The Service is returning Cookie as

Set-Cookie: ASP.NET_SessionId=cml1mh45lc3yzf55flravg45; path=/; HttpOnly

And this is not getting processed by Axis client.

I have also created a test Axis service where I have enabled transport
level sessions. The Cookie gets set here as:

Set-Cookie: JSESSIONID=0E2ACECB8CF2E5E91F55B5F8E6CEA150; Path=/axis2

In this case, Axis client is able to return back the sessionid to the
Axis Service.

Appreciate any input on how to work around this issue. 

Does Axis provide any API to inspect the incoming Cookies, and set
outgoing Cookies explicitly?

Thanks

Shalab

 



If you have received this e-mail in error, please delete it and notify the 
sender as soon as possible. The contents of this e-mail may be confidential and 
the unauthorized use, copying, or dissemination of it and any attachments to 
it, is prohibited. Internet communications are not secure and Hyperion does 
not, therefore, accept legal responsibility for the contents of this message 
nor for any damage caused by viruses. The views expressed here do not 
necessarily represent those of Hyperion. For more information about Hyperion, 
please visit our Web site at: www.hyperion.com

How to configure SSL client authentication with Axis2?

2007-08-02 Thread Merritt, Norris

Hi, I would like to get my Axis2 client application to present a
certificate to the server when initiating the SSL handshake. Can anyone
shed some light on how to configure this?

Please disregard my last plea for help

2007-08-02 Thread New AxisU

I found the problem - no axis2 & xmlbeans in classpath.

Problem with Loading?

2007-08-02 Thread New AxisU

Hi,

I am stumped again and yet I think I am really close so ... I am trying to
write an axis2 client for my new sample axis2 service.
When I run the client I get:

a99-run.myclient:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/axis2/client/Stub
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(
SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at org.mlbissonnette.quote.client.RandomQuoteClient.main(
RandomQuoteClient.java:35)



RandomQuoteWSStub.class exists in build directory

I get the same error message when I try run outside of ant usin g

java -jar myclient.jar

I'm using axis2  1.3 RC2.  Is this a classpath problem or did I not generate
the code correctly?

Any thought would be appreciated?

Helpful Netbeans Axis2 Tutorial

2007-08-02 Thread New AxisU

Hi,

I mentioned this in my first post and I just now "re-found" the url:
http://epubs.cclrc.ac.uk/bitstream/1539/Axis2WebServiceNetBeans.pdf

Re: Error in BeanSerializer

2007-08-02 Thread Ashish Kulkarni

Hi
But how do i find which class, i have this complex java code, created from a
complex XSD (Style sheet)
this does not show which class has this issue

Ashish
On 8/2/07, albert quinn <[EMAIL PROTECTED]> wrote:
>
>   Hi Ashish !!! :
>
>   I'm a newbie in the Axis 2 world, but i've faced a problem similar
> to yours. Perhaps when you send the response from the WebService,
> you're returning an object from a class which it's not a bean class.
> Add getters and setters methods to that class and a no parameters
> constructor. I hope it helps!!!.
>
> 2007/8/2, Ashish Kulkarni <[EMAIL PROTECTED]>:
> > Hi
> > I am getting the following error when i am trying to send a response
> from
> > Webservice,
> >
> > what does this mean
> >
> >
> > 2007-08-02 14:44:37,038 ERROR [http-4080-Processor25] ser.BeanSerializer
> > (BeanSerializer.java :274) - Exception:
> > java.lang.NullPointerException
> > at
> > org.apache.axis.encoding.ser.BeanSerializer.serialize(
> BeanSerializer.java:265)
> > at
> > org.apache.axis.encoding.SerializationContext.serializeActual(
> SerializationContext.java
> > :1502)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:978)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:732)
> > at org.apache.axis.encoding.ser.BeanSerializer.serialize
> > (BeanSerializer.java:230)
> > at
> > org.apache.axis.encoding.SerializationContext.serializeActual(
> SerializationContext.java:1502)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:978)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:732)
> > at
> > org.apache.axis.encoding.ser.BeanSerializer.serialize(
> BeanSerializer.java:230)
> > at
> > org.apache.axis.encoding.SerializationContext.serializeActual
> > (SerializationContext.java:1502)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:978)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(
> SerializationContext.java:799)
> > at
> > org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
> > at
> > org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
> > at
> > org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> > at
> > org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
> > at
> > org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
> > at
> > org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> > at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
> > at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
> > at org.apache.axis.Message.writeTo(Message.java:539)
> > at org.apache.axis.transport.http.AxisServlet.sendResponse
> > (AxisServlet.java:902)
> > at
> > org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
> > at
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> > at org.apache.axis.transport.http.AxisServletBase.service
> > (AxisServletBase.java:327)
> > at
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:252)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter
> > (ApplicationFilterChain.java:173)
> > at
> > org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:213)
> > at
> > org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:178)
> > at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :126)
> > at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :105)
> > at org.apache.catalina.core.StandardEngineValve.invoke
> > (StandardEngineValve.java:107)
> > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
> :148)
> > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :869)
> > at
> >
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
> > (Http11BaseProtocol.java:664)
> > at
> > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
> PoolTcpEndpoint.java:527)
> > at
> > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(
> LeaderFollowerWorkerThread.java:80)
> > at
> > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.java:684)
> > at java.lang.Thread.run(Thread.java:534)
> >
> >
> > Ashish
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Error in BeanSerializer

2007-08-02 Thread albert quinn

  Hi Ashish !!! :

  I'm a newbie in the Axis 2 world, but i've faced a problem similar
to yours. Perhaps when you send the response from the WebService,
you're returning an object from a class which it's not a bean class.
Add getters and setters methods to that class and a no parameters
constructor. I hope it helps!!!.

2007/8/2, Ashish Kulkarni <[EMAIL PROTECTED]>:
> Hi
> I am getting the following error when i am trying to send a response from
> Webservice,
>
> what does this mean
>
>
> 2007-08-02 14:44:37,038 ERROR [http-4080-Processor25] ser.BeanSerializer
> (BeanSerializer.java :274) - Exception:
> java.lang.NullPointerException
> at
> org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:265)
> at
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java
> :1502)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:978)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:732)
> at org.apache.axis.encoding.ser.BeanSerializer.serialize
> (BeanSerializer.java:230)
> at
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1502)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:978)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:732)
> at
> org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:230)
> at
> org.apache.axis.encoding.SerializationContext.serializeActual
> (SerializationContext.java:1502)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:978)
> at
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:799)
> at
> org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
> at
> org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
> at
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> at
> org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
> at
> org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
> at
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
> at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
> at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
> at org.apache.axis.Message.writeTo(Message.java:539)
> at org.apache.axis.transport.http.AxisServlet.sendResponse
> (AxisServlet.java:902)
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at org.apache.axis.transport.http.AxisServletBase.service
> (AxisServletBase.java:327)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at org.apache.catalina.core.StandardEngineValve.invoke
> (StandardEngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
> (Http11BaseProtocol.java:664)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:534)
>
>
> Ashish
>

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

Re: how to configure axis 1.4 loggingusing log4j

2007-08-02 Thread Anil Philip

I had the same problem.

The solution was to create a log4j.properties file.
And put it in C:\Program Files\Apache Software
Foundation\Tomcat 5.5\webapps\axis\WEB-INF\classes
 

# Set root category priority to INFO and its only
appender to CONSOLE.

log4j.rootCategory=INFO, CONSOLE

#log4j.rootCategory=INFO, CONSOLE, LOGFILE

 

# Set the enterprise logger category to FATAL and its
only appender to CONSOLE.

log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE

log4j.logger.org.apache.axis=FATAL, CONSOLE

 

# CONSOLE is set to be a ConsoleAppender using a
PatternLayout.

log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender

log4j.appender.CONSOLE.Threshold=INFO

log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout

log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n

 

# LOGFILE is set to be a File appender using a
PatternLayout.

log4j.appender.LOGFILE=org.apache.log4j.FileAppender

log4j.appender.LOGFILE.File=axis.log

log4j.appender.LOGFILE.Append=true

log4j.appender.LOGFILE.Threshold=INFO

log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout

log4j.appender.LOGFILE.layout.ConversionPattern=%-4r
[%t] %-5p %c %x - %m%n

 

thanks,

Anil

--- Ashish Kulkarni <[EMAIL PROTECTED]>
wrote:

> Hi
> I am using log4j for logging in my application, i
> have recently added
> webservice using axis 1.4 to my application,
> now i am
> getting lots of axis logs in the log file, how do i
> suppress those
> logs, or contral what to log and what not to log,
> my log4j is configured using properties file and is
> as below
> 
> 
> 
> log4j.rootLogger=, A1, A2
> 
> # A1 is set to be ConsoleAppender sending its output
> to System.out
> log4j.appender.A1=org.apache.log4j.ConsoleAppender
> 
> 
> # A1 uses PatternLayout.
>
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
> 
> # The conversion pattern consists of date in ISO8601
> format, level,
> # thread name, logger name truncated to its
> rightmost two components
> # and left justified to 17 characters, location
> information consisting
> # of file name (padded to 13 characters) and line
> number, nested
> # diagnostic context, the and the application
> supplied message
> 
> log4j.appender.A1.layout.ConversionPattern=%d %-5p
> [%t] %-17c{2} (%13F:%L)
> %3x - %m%n
> 
> # Appender A2 writes to the file "log".
>
log4j.appender.A2=org.apache.log4j.DailyRollingFileAppender
> # use ${} to specify location
>
log4j.appender.A2.File=${java.io.tmpdir}approvals6000F3.txt
> 
> # Truncate 'test' if it aleady exists.
> log4j.appender.A2.Append=false
> log4j.appender.A2.DatePattern='.'-MM-dd
> 
> # Appender A2 uses the PatternLayout.
>
log4j.appender.A2.layout=org.apache.log4j.PatternLayout
> log4j.appender.A2.layout.ConversionPattern=%-5r %-5p
> [%t] %c{2} - %m%n
> 
> 
> 
> Ashish
> 



   

Moody friends. Drama queens. Your life? Nope! - their life, your story. Play 
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  

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

Problem with JAX-WS and AXIS2, Help Me please

2007-08-02 Thread jnet2000


Hi All

i'm problem with WS written JAX-WS and AXIS2(1.2 or 1.3)
if use that services.xml (created by plug-in eclipse):
- <#> 
 Please Type your service description here
- <#> 
 http://www.w3.org/2004/08/wsdl/in-only*";  
class="*org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver*" />
 http://www.w3.org/2004/08/wsdl/in-out*";  
class="*org.apache.axis2.rpc.receivers.RPCMessageReceiver*" />

 
 locked="*false*">it.my.endpoint.implement.CustomerService

 

Generated Exception :
java.lang.RuntimeException: java.lang.RuntimeException: Unexpected  
subelement retrieveCustomerIdentifyByCFResponse


msg soap
request
POST /axis2/services/CustomerService HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8; action="http:// 
my.it/retrieveCustomerIdentifyByCF"

User-Agent: Axis2
Host: localhost:
Transfer-Encoding: chunked


  http://www.w3.org/2003/05/soap- 
envelope">

 


   1234567890
   CCCFFF84L12H501Z

 
  

response
HTTP/1.1 200 OK
X-Powered-By: Servlet/2.5
Content-Type: application/soap+xml; action="//my.it/ 
CustomerServicePortType/ 
retrieveCustomerIdentifyByCFResponse";charset=UTF-8

Transfer-Encoding: chunked
Date: Thu, 02 Aug 2007 15:55:23 GMT
Server: Sun Java System Application Server Platform Edition 9.0_01


  http://www.w3.org/2003/05/soap- 
envelope">

 


   
  0
  
 0055
 00111
 OK
 Formatta TUTTO!!!
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">

  
  type="it.my.common.bean.results.CustomerIdentify">

 via magna grecia
 19740907
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">

 GGGCCC74L09H501Z
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/ 
2001/XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/2001/ 
XMLSchema-instance" xsi:nil="true">
 http://www.w3.org/ 
2001/XMLSchema-instance" xsi:nil="true">

  
   

 
  

---

if use that services.xml(created by me):

   PostPay Payment
  
http://www.w3.org/2004/08/wsdl/in-out";  
class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>
 http://www.w3.org/2004/08/wsdl/in-only";  
class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>
http://www.w3.org/2004/08/wsdl/robust-in-only";  
class="org.apache.axis2.jaxws.server.JAXWSMessageReceiver"/>

  
   locked="false">it.my.endpoint.implement.CustomerService

   true
   true


Generated Exception :
org.apache.axis2.AxisFault: Transport error: 400 Error: Bad Request
   at org.apache.axis2.transport.http.HTTPSender.handleResponse 
(HTTPSender.java:296)
   at org.apache.axis2.transport.http.HTTPSender.sendViaPost 
(HTTPSender.java:192)
   at org.apache.axis2.transport.http.HTTPSender.send 
(HTTPSender.java:77)
   at  
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW 
ithCommons(CommonsHTTPTransportSender.java:327)
   at  
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke 
(CommonsHTTPTransportSender.java:206)

   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:397)
   at org.apache.axis2.description.OutInAxisOperationClient.send 
(OutInAxisOperation.java:372)
   at  
org.apache.axis2.description.OutInAxisOperationClient.executeImpl 
(OutInAxisOperation.java:211)
   at org.apache.axis2.client.OperationClient.execute 
(OperationClient.java:163)
   at  
it.my.client.CustomerServiceCustomerServiceSOAP12PortStub.retrieveCustom 
erIdentifyByCF(CustomerServiceCustomerServiceSOAP12PortStub.java:154)

   at it.my.client.ClientProva.main(ClientProva.java:14)

msg soap

request
  http://www.w3.org/2003/05/soap- 
envelope">

 


   1234567890
   CCCFFF84L12H501Z

 
  

response

  http://www.w3.org/2003/05/soap- 
envelope">

 

   
  soapenv:Sender
   
   
  java.lang.Nu

Error in BeanSerializer

2007-08-02 Thread Ashish Kulkarni

Hi
I am getting the following error when i am trying to send a response from
Webservice,

what does this mean


2007-08-02 14:44:37,038 ERROR [http-4080-Processor25] ser.BeanSerializer (
BeanSerializer.java:274) - Exception:
java.lang.NullPointerException
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java
:265)
at org.apache.axis.encoding.SerializationContext.serializeActual(
SerializationContext.java:1502)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:978)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:732)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java
:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(
SerializationContext.java:1502)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:978)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:732)
at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java
:230)
at org.apache.axis.encoding.SerializationContext.serializeActual(
SerializationContext.java:1502)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:978)
at org.apache.axis.encoding.SerializationContext.serialize(
SerializationContext.java:799)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.Message.writeTo(Message.java:539)
at org.apache.axis.transport.http.AxisServlet.sendResponse(AxisServlet.java
:902)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at org.apache.axis.transport.http.AxisServletBase.service(
AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(
StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(
StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(
LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:534)


Ashish

Re: Axis2 isn't following document literal wrapped standard in generated code

2007-08-02 Thread Davanum Srinivas

Michael,

Did you try the ADB binding ("-d adb") option with unwrap option ("-uw"?)

thanks,
dims

On 8/2/07, Michael Mattox <[EMAIL PROTECTED]> wrote:
> I'm trying out Axis2 after using XFire.  I have a WSDL that is
> document literal wrapped.  My WSDL operation has a single element
> named parameters.  This element refers to a complex type called
> XInHolder.  This element contains a single element, called XIn which
> is a complextype.
>
> As I understand the wrapped standard, my method foo should have one
> parameter named XIn.  This is because each element of the "wrapper
> object" is a parameter to the method.  This is the case with XFire.
>
> With Axis2, my method foo has a XDocument parameter (using xmlbeans
> bindings).  This document class as a getXInHolder method.  The result
> is Axis2 is generating the code with not only the wrapper element
> (which shouldn't be) but also a Document object which wraps the
> wrapper element.  This adds 2 levels to my web service.
>
> This isn't a major problem because my web service simply delegates to
> a business service and we can dereference the objects and pass the
> correct object (XIn).  But it doesn't seem like Axis2 is respecting
> the wrapped standard.  Actually I'm not sure this is even specified in
> the standard.
>
> Any ideas?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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

wsdl 2.0 process

2007-08-02 Thread New AxisU

Hi,

I am converting some 1.1 wsdl's to 2.0 and I am very pleased with using
axis2.

First I went to http://www.w3.org/2006/02/WSDLConvert.html and tried their
online converter.
It didn't work for me but I might have had a bad character in the file.

Instead, I used their "XSLT 2.0 stylesheet used for the
conversion"
with XMSpy and created
a converted wsdl.

Then I fed the converted wsdl's into axis2's wsdl2java batch file and ran it
successfully.

Various people have been asking about how to validate their 2.0 wsdl.  This
worked much
better for me than trying to use my converted wsdl, with XMLSpy or Stylus
Studio, and the
wsdl2.0 schema.

Thanks again Axis2 folks.

Connection Reset error

2007-08-02 Thread Sunny44


We have created the client for the web service that other team has created
for it's utilization.

But the client works on one of our developer's system but when i run the
same code from different system it throws following exception

com.platform.intg.pim.SessionMgmtException: org.apache.axis2.AxisFault:
Connection reset
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:90)
at
com.deloitte.platform.intg.pim.ProfileUpdateWSProxyEndpointTest.testUpdateUser(ProfileUpdateWSProxyEndpointTest.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: org.apache.axis2.AxisFault: Connection reset
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)
at
com.deloitte.platform.intg.pim.ws.profile.PIMPeopleManagementServicesSoapStud.UpdatePerson(PIMPeopleManagementServicesSoapStud.java:1182)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.callWebService(ProfileMgmtUpdateWSProxyEndpoint.java:148)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:87)
... 19 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:314)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
... 25 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
... 26 more
Caused by: java.net.SocketException: Connection reset
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:558)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:176)
... 28 more


Thanks

Sunnny
-- 
View this message in context: 
http://www.nabble.com/Conn

Connection Reset erroe

2007-08-02 Thread Sunny44


We have created the client for the web service that other team has created
for it's utilization.

But the client works on one of our developer's system but when i run the
same code from different system it throws following exception

com.platform.intg.pim.SessionMgmtException: org.apache.axis2.AxisFault:
Connection reset
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:90)
at
com.deloitte.platform.intg.pim.ProfileUpdateWSProxyEndpointTest.testUpdateUser(ProfileUpdateWSProxyEndpointTest.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: org.apache.axis2.AxisFault: Connection reset
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)
at
com.deloitte.platform.intg.pim.ws.profile.PIMPeopleManagementServicesSoapStud.UpdatePerson(PIMPeopleManagementServicesSoapStud.java:1182)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.callWebService(ProfileMgmtUpdateWSProxyEndpoint.java:148)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:87)
... 19 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:314)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
... 25 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
... 26 more
Caused by: java.net.SocketException: Connection reset
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:558)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:176)
... 28 more


Thanks

Sunnny
-- 
View this message in context: 
http://www.nabble.com/Conn

Connection Reset error

2007-08-02 Thread Sunny44


I have created the client and Stub for the Web service. 

It runs on one of our developers system but when try to run the same code it
throws following exception 

com.deloitte.platform.intg.pim.SessionMgmtException:
org.apache.axis2.AxisFault: Connection reset
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:90)
at
com.deloitte.platform.intg.pim.ProfileUpdateWSProxyEndpointTest.testUpdateUser(ProfileUpdateWSProxyEndpointTest.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: org.apache.axis2.AxisFault: Connection reset
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)
at
com.deloitte.platform.intg.pim.ws.profile.PIMPeopleManagementServicesSoapStud.UpdatePerson(PIMPeopleManagementServicesSoapStud.java:1182)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.callWebService(ProfileMgmtUpdateWSProxyEndpoint.java:148)
at
com.deloitte.platform.intg.pim.ProfileMgmtUpdateWSProxyEndpoint.getPersonProfile(ProfileMgmtUpdateWSProxyEndpoint.java:87)
... 19 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:314)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
... 25 more
Caused by: org.apache.axis2.AxisFault: Connection reset
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305)
... 26 more
Caused by: java.net.SocketException: Connection reset
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:558)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:176)
... 28 more



Please advice ---


Sunny
-- 
View this message in context: 
http://www.nabble.com/Connection-Reset-error-tf4207615.html#a11969284
Sent

WSDL2Java Ant Task Question

2007-08-02 Thread Alejandro Calbazana


Simple question...  How can I fail a target if the WSDL2Java task fails?

Thanks,

Al


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

how to tell if axis 1.4 is using http persistent connections or not?

2007-08-02 Thread Anil Philip

Hello,
how to tell if axis 1.4 is using http persistent
connections or not? And how to configure it.
thanks much,
Anil


   

Moody friends. Drama queens. Your life? Nope! - their life, your story. Play 
Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  

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

how to configure axis 1.4 loggingusing log4j

2007-08-02 Thread Ashish Kulkarni

Hi
I am using log4j for logging in my application, i have recently added
webservice using axis 1.4 to my application,
now i am
getting lots of axis logs in the log file, how do i suppress those
logs, or contral what to log and what not to log,
my log4j is configured using properties file and is as below



log4j.rootLogger=, A1, A2

# A1 is set to be ConsoleAppender sending its output to System.out
log4j.appender.A1=org.apache.log4j.ConsoleAppender


# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout

# The conversion pattern consists of date in ISO8601 format, level,
# thread name, logger name truncated to its rightmost two components
# and left justified to 17 characters, location information consisting
# of file name (padded to 13 characters) and line number, nested
# diagnostic context, the and the application supplied message

log4j.appender.A1.layout.ConversionPattern=%d %-5p [%t] %-17c{2} (%13F:%L)
%3x - %m%n

# Appender A2 writes to the file "log".
log4j.appender.A2=org.apache.log4j.DailyRollingFileAppender
# use ${} to specify location
log4j.appender.A2.File=${java.io.tmpdir}approvals6000F3.txt

# Truncate 'test' if it aleady exists.
log4j.appender.A2.Append=false
log4j.appender.A2.DatePattern='.'-MM-dd

# Appender A2 uses the PatternLayout.
log4j.appender.A2.layout=org.apache.log4j.PatternLayout
log4j.appender.A2.layout.ConversionPattern=%-5r %-5p [%t] %c{2} - %m%n



Ashish

Re: wsdl 2.0 questions

2007-08-02 Thread Chathura Herath

Its the MEP in your operation. Interface->operation pattern attribute.

Again a namespace problem. Please try replacing it with the following.
http://www.w3.org/ns/wsdl/in-out

Thanks
Chathura

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Right.  That makes sense and the soap12 one must be changed as well.
>
> Ok so using the same batch file as before and making those changes (see
> below).  I am now back to yesterday's error message about the message
> exchange pattern.  Where is this http://www.w3.org/2004/03/wsdl/in-outcoming 
> from?
>
> >wsdl2java.bat -uri hilton2.wsdl -wv 2.0
> Using AXIS2_HOME: C:\Java\axis2-1.3RC2
> Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(
> CodeGenerationEngine.java:147)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.AxisFault: An unsupported message exchange
> pattern (MEP) exists in ID is http://www.w3.org/2004/03/wsdl/in-out
> ...
>
> -
> hilton2.wsdl
> -
>
>  xmlns="http://www.w3.org/ns/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
>   
> This document describes the GreatH Web service.  Additional
> application-level requirements for use of this service --
> beyond what WSDL 2.0 is able to describe -- are available
> at http://greath.example.com/2004/reservation-documentation.html
>   
>
>   
>  xmlns:xs="http://www.w3.org/2001/XMLSchema";
> targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> "
> xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
>
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>
>   
>
> 
>   
>
>   
>
>  element = "ghns:invalidDataError"/>
>
>  pattern=" http://www.w3.org/2004/03/wsdl/in-out"; >
>element="ghns:checkAvailability" />
>element="ghns:checkAvailabilityResponse" />
> 
> 
>
>   
>
>  interface="tns:reservationInterface"
>   type="http://www.w3.org/ns/wsdl/soap";
>   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
>
>
> wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>
>
>wsoap:code="soap:Sender"/>
>
>   
>
>   interface="tns:reservationInterface">
>
>  binding="tns:reservationSOAPBinding"
>address ="http://greath.example.com/2004/reservation"/
> >
>
>   
>
> 
>
>
> On 8/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> >
> > Make sure you're using the correct WSDL namespace.
> >
> > You're currently using " 
> > http://www.w3.org/2004/08/wsdl";
> >
> > You should be using "http://www.w3.org/ns/wsdl
> >  "
> >
> > Anne
> >
> > On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Keith,
> > >
> > > Thanks for looking at this.  I'm reading your message and I'm
> > > confused. I am using Axis2 1.3 RC2 which is the latest RC from the url
> > > you listed. If you are using the same one, then perhaps I have some kind 
> > > of
> > > pilot error in my wsdl2java usage.  Actually I seem to be heading full 
> > > speed
> > > into reverse because now the error message is
> > >
> > > Using AXIS2_HOME:
> > >
> > > 
> > > Here's my fancy batch file:
> > >
> > > echo %AXIS2_HOME%
> > > wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> > > -
> > > and I get
> > >
> > > Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> > > Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> > > Woden[Fatal Error],0:0, WSDL501, Expected a "{
> > > http://www.w3.org/ns/wsdl}description"
> > > element, but found a "{ 
> > > http://www.w3.org/2004/08/wsdl}description"
> > > element instead.
> > > Exception in thread "main"
> > > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in
> > > parsing WSDL
> > > ...
> > >
> > > But maybe this isn't so weird because the w3c example uses
> > >
> > >  > > xmlns="http://www.w3.org/2004/08/wsdl";
> > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl
> > > "
> > > xmlns:tns= " http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > > xmlns:ghns = " http://g

Axis2 isn't following document literal wrapped standard in generated code

2007-08-02 Thread Michael Mattox

I'm trying out Axis2 after using XFire.  I have a WSDL that is
document literal wrapped.  My WSDL operation has a single element
named parameters.  This element refers to a complex type called
XInHolder.  This element contains a single element, called XIn which
is a complextype.

As I understand the wrapped standard, my method foo should have one
parameter named XIn.  This is because each element of the "wrapper
object" is a parameter to the method.  This is the case with XFire.

With Axis2, my method foo has a XDocument parameter (using xmlbeans
bindings).  This document class as a getXInHolder method.  The result
is Axis2 is generating the code with not only the wrapper element
(which shouldn't be) but also a Document object which wraps the
wrapper element.  This adds 2 levels to my web service.

This isn't a major problem because my web service simply delegates to
a business service and we can dereference the objects and pass the
correct object (XIn).  But it doesn't seem like Axis2 is respecting
the wrapped standard.  Actually I'm not sure this is even specified in
the standard.

Any ideas?

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

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Right.  That makes sense and the soap12 one must be changed as well.

Ok so using the same batch file as before and making those changes (see
below).  I am now back to yesterday's error message about the message
exchange pattern.  Where is this
http://www.w3.org/2004/03/wsdl/in-outcoming from?

>wsdl2java.bat -uri hilton2.wsdl -wv 2.0
Using AXIS2_HOME: C:\Java\axis2-1.3RC2
Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(
CodeGenerationEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: An unsupported message exchange
pattern (MEP) exists in ID is http://www.w3.org/2004/03/wsdl/in-out
...

-
hilton2.wsdl
-

http://www.w3.org/ns/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

  
This document describes the GreatH Web service.  Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
  

  
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>

  
  

  
  
  

  

  

  


  

  



http://www.w3.org/2004/03/wsdl/in-out"; >





  

  http://www.w3.org/ns/wsdl/soap";
  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>

http://www.w3.org/2003/05/soap/mep/request-response"/>



  

  

 http://greath.example.com/2004/reservation"/>

  




On 8/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>
> Make sure you're using the correct WSDL namespace.
>
> You're currently using " 
> http://www.w3.org/2004/08/wsdl";
>
> You should be using 
> "http://www.w3.org/ns/wsdl"
>
> Anne
>
> On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> >
> > Hi Keith,
> >
> > Thanks for looking at this.  I'm reading your message and I'm
> > confused. I am using Axis2 1.3 RC2 which is the latest RC from the url
> > you listed. If you are using the same one, then perhaps I have some kind of
> > pilot error in my wsdl2java usage.  Actually I seem to be heading full speed
> > into reverse because now the error message is
> >
> > Using AXIS2_HOME:
> >
> > 
> > Here's my fancy batch file:
> >
> > echo %AXIS2_HOME%
> > wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> > -
> > and I get
> >
> > Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> > Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> > Woden[Fatal Error],0:0, WSDL501, Expected a "{
> > http://www.w3.org/ns/wsdl}description"
> > element, but found a "{ 
> > http://www.w3.org/2004/08/wsdl}description"
> > element instead.
> > Exception in thread "main"
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing
> > WSDL
> > ...
> >
> > But maybe this isn't so weird because the w3c example uses
> >
> >  > xmlns="http://www.w3.org/2004/08/wsdl";
> > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl "
> >
> > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 "
> > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
> >
> > and I thought that xmlns should be http://www.w3.org/ns/wsdl
> > but then I am less clear on what other changes should be made does 
> > www.w3.org/2004/08/wsdl/soap12
> > become www.w3.org/ns/wsdl/soap12 ?
> >
> > Could you send me the example wsdl you used successfully?
> >
> > Thanks
> >
> >
> >
> >
> > -
> >
> > Here's the hilton wsdl
> >
> > -
> >
> >  > xmlns="http://www.w3.org/2004/08/wsdl";
> > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl "
> >
> > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 "
> > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
> >
> >   
> > This document describes the GreatH Web service.  Additional
> > a

Re: [Axis2] 1.3 Snapshot - Fatal error restarting the Http Nio transportReceiver

2007-08-02 Thread Tobias Seng


Seems to be a HTTPCORE issue

see here
https://issues.apache.org/jira/browse/HTTPCORE-108

Thanks
Tobias


Hi Asankha
Do you have any idea about this ?

Thanks
Deepal
  



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

Re: wsdl 2.0 questions

2007-08-02 Thread Anne Thomas Manes

Make sure you're using the correct WSDL namespace.

You're currently using
"http://www.w3.org/2004/08/wsdl";

You should be using
"http://www.w3.org/ns/wsdl
"

Anne

On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi Keith,
>
> Thanks for looking at this.  I'm reading your message and I'm confused. I
> am using Axis2 1.3 RC2 which is the latest RC from the url you listed. If
> you are using the same one, then perhaps I have some kind of pilot error in
> my wsdl2java usage.  Actually I seem to be heading full speed into reverse
> because now the error message is
>
> Using AXIS2_HOME:
>
> 
> Here's my fancy batch file:
>
> echo %AXIS2_HOME%
> wsdl2java.bat -uri hilton.wsdl  -wv 2.0
> -
> and I get
>
> Using AXIS2_HOME: c:\Java\axis2-1.3RC2
> Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
> Woden[Fatal Error],0:0, WSDL501, Expected a "{
> http://www.w3.org/ns/wsdl}description"
> element, but found a "{ 
> http://www.w3.org/2004/08/wsdl}description"
> element instead.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing
> WSDL
> ...
>
> But maybe this isn't so weird because the w3c example uses
>
>  xmlns="http://www.w3.org/2004/08/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
> and I thought that xmlns should be http://www.w3.org/ns/wsdl
> but then I am less clear on what other changes should be made does
> www.w3.org/2004/08/wsdl/soap12 become www.w3.org/ns/wsdl/soap12 ?
>
> Could you send me the example wsdl you used successfully?
>
> Thanks
>
>
>
>
> -
>
> Here's the hilton wsdl
>
> -
>
>  xmlns="http://www.w3.org/2004/08/wsdl";
> targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
> xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";>
>
>   
> This document describes the GreatH Web service.  Additional
> application-level requirements for use of this service --
> beyond what WSDL 2.0 is able to describe -- are available
> at http://greath.example.com/2004/reservation-documentation.html
>   
>
>   
>  xmlns:xs="http://www.w3.org/2001/XMLSchema";
>
> targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> "
> xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
>
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>
>   
>
> 
>   
>
>   
>
>  element = "ghns:invalidDataError"/>
>
>  pattern=" http://www.w3.org/2004/03/wsdl/in-out"; >
>element="ghns:checkAvailability" />
>element="ghns:checkAvailabilityResponse" />
> 
> 
>
>   
>
>  interface="tns:reservationInterface"
>   type="http://www.w3.org/2004/08/wsdl/soap12 "
>   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
>
>
> wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
>
>
>wsoap:code="soap:Sender"/>
>
>   
>
>   interface="tns:reservationInterface">
>
>  binding="tns:reservationSOAPBinding"
>address ="http://greath.example.com/2004/reservation"/
> >
>
>   
>
> 
>
>
>
>  **
>
> On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
> >
> > Axis2 1.3 RC2
> >
> > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi,
> > >
> > > I just tried the wsdl located at
> > > http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the
> > > primer with Axis2-1.3-RC2. It worked without any problems. WSDL 
> > > 2.0support was only available in
> > > Axis2-1.2 prior to this. Please use the latest RC located at
> > > http://ws.apache.org/axis2/download.cgi. The 1.3 release will be out
> > > very soon. You can swtich to that once its released. The 1.3 release
> > > will be very stable.
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi,
> > > >
> > > > Wats your Axis2 version?
> > > >
> > > > Thanks,
> > > > Keith.
> > > >
> > > > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > >

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Hi Keith,

Thanks for looking at this.  I'm reading your message and I'm confused. I am
using Axis2 1.3 RC2 which is the latest RC from the url you listed. If you
are using the same one, then perhaps I have some kind of pilot error in my
wsdl2java usage.  Actually I seem to be heading full speed into reverse
because now the error message is

Using AXIS2_HOME:


Here's my fancy batch file:

echo %AXIS2_HOME%
wsdl2java.bat -uri hilton.wsdl  -wv 2.0
-
and I get

Using AXIS2_HOME: c:\Java\axis2-1.3RC2
Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01
Woden[Fatal Error],0:0, WSDL501, Expected a "{
http://www.w3.org/ns/wsdl}description";  element, but found a "{
http://www.w3.org/2004/08/wsdl}description"; element instead.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing WSDL
...

But maybe this isn't so weird because the w3c example uses

http://www.w3.org/2004/08/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

and I thought that xmlns should be http://www.w3.org/ns/wsdl
but then I am less clear on what other changes should be made does
www.w3.org/2004/08/wsdl/soap12 become www.w3.org/ns/wsdl/soap12?

Could you send me the example wsdl you used successfully?

Thanks




-

Here's the hilton wsdl

-

http://www.w3.org/2004/08/wsdl";
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>

  
This document describes the GreatH Web service.  Additional
application-level requirements for use of this service --
beyond what WSDL 2.0 is able to describe -- are available
at http://greath.example.com/2004/reservation-documentation.html
  

  
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd";
xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>

  
  

  
  
  

  

  

  


  

  



http://www.w3.org/2004/03/wsdl/in-out"; >





  

  http://www.w3.org/2004/08/wsdl/soap12";
  wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>

http://www.w3.org/2003/05/soap/mep/request-response"/>



  

  

 http://greath.example.com/2004/reservation"/>

  




 **
On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Axis2 1.3 RC2
>
> On 8/2/07, keith chapman <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I just tried the wsdl located at
> > http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the primer
> > with Axis2-1.3-RC2. It worked without any problems. WSDL 2.0 support was
> > only available in Axis2-1.2 prior to this. Please use the latest RC
> > located at http://ws.apache.org/axis2/download.cgi. The 1.3 release will
> > be out very soon. You can swtich to that once its released. The 1.3release 
> > will be very stable.
> >
> > Thanks,
> > Keith.
> >
> > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi,
> > >
> > > Wats your Axis2 version?
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using
> > > > axis2 wsdl2java as a way of sanity checking the wsdls.  I am seeing 
> > > > messages
> > > > about "unsupported message exchange patterns".  The wsdl below is much
> > > > simpler than the one I'm using but it gets that same message.  I got it 
> > > > from
> > > > the w3c wsdl 2.0 primer.  Any idea what is wrong with it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >  > > > xmlns="http://www.w3.org/ns/wsdl";
> > > > targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> > > >
> > > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl "
> > > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > > > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 "
> > > > xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
> > > >
> > > >   
> > > > This document describes the GreatH Web service.  Additional
> > > > application-level requirements for use of this service --
> > > > beyond what WSDL 2.0 is able to describe -- are available
> > > > at http://greath.example.com/2004/reservation-documentation.html
> > > >   
> > > >
> > > >   
> > > >  > > > xmlns:xs="

Re: wsdl 2.0 questions

2007-08-02 Thread New AxisU

Axis2 1.3 RC2

On 8/2/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I just tried the wsdl located at
> http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the primer
> with Axis2-1.3-RC2. It worked without any problems. WSDL 2.0 support was
> only available in Axis2-1.2 prior to this. Please use the latest RC
> located at http://ws.apache.org/axis2/download.cgi. The 1.3 release will
> be out very soon. You can swtich to that once its released. The 1.3release 
> will be very stable.
>
> Thanks,
> Keith.
>
> On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote:
> >
> > Hi,
> >
> > Wats your Axis2 version?
> >
> > Thanks,
> > Keith.
> >
> > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote:
> > >
> > > Hi, I am looking at migrating our wsdls from 1.1 to 2.0.  I am using
> > > axis2 wsdl2java as a way of sanity checking the wsdls.  I am seeing 
> > > messages
> > > about "unsupported message exchange patterns".  The wsdl below is much
> > > simpler than the one I'm using but it gets that same message.  I got it 
> > > from
> > > the w3c wsdl 2.0 primer.  Any idea what is wrong with it?
> > >
> > > Thanks
> > >
> > >
> > >  > > xmlns="http://www.w3.org/ns/wsdl";
> > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl
> > > "
> > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl";
> > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd";
> > > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 "
> > > xmlns:soap=" http://www.w3.org/ns/soap-envelope";>
> > >
> > >   
> > > This document describes the GreatH Web service.  Additional
> > > application-level requirements for use of this service --
> > > beyond what WSDL 2.0 is able to describe -- are available
> > > at http://greath.example.com/2004/reservation-documentation.html
> > >   
> > >
> > >   
> > >  > > xmlns:xs="XMLSchema.xsd"
> > > targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd
> > > "
> > > xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";>
> > >> > type="tCheckAvailability"/>
> > >   
> > > 
> > >   
> > >   
> > >   
> > > 
> > >   
> > >> > type="xs:double"/>
> > >   
> > > 
> > >   
> > >
> > >   
> > >  > > element = "ghns:invalidDataError"/>
> > >  > > pattern=" http://www.w3.org/2004/03/wsdl/in-out " >
> > >  > >   element="ghns:checkAvailability" />
> > >  > >   element="ghns:checkAvailabilityResponse" />
> > > 
> > > 
> > >   
> > >
> > >> >   interface="tns:reservationInterface"
> > >   type=" http://www.w3.org/2004/08/wsdl/soap12 "
> > >   wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";>
> > >
> > >  > >   
> > > wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/>
> > >  > >   wsoap:code="soap:Sender"/>
> > >   
> > >
> > >> >interface="tns:reservationInterface">
> > >   > >binding="tns:reservationSOAPBinding"
> > >address 
> > > ="http://greath.example.com/2004/reservation"/
> > > >
> > >   
> > > 
> > >
> >
> >
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/
>
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>

Re: bug: org.apache.axis2.wsdl.codegen.writer.adjustWSDLSchemaLocatins

2007-08-02 Thread Davanum Srinivas

Done.

On 8/2/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
>
> > Fixed in trunk. thanks! (svn revision 561898). Next time, please do
> > raise a JIRA.
> >
> Dims , how about in the branch .
>
> Thanks
> Deepal
> > -- dims
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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

Re: Addressig configuration at server's side

2007-08-02 Thread Brian De Pradine

Hello Marc,

If you send a request using the Submission version of WS-Addressing then 
the response will automatically use the Submission version as well.

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Marc de Palol <[EMAIL PROTECTED]> wrote on 02/08/2007 10:21:00:

> Hello all,
> 
> I'm running a client/server with axis2 on both sides. I'm using the
> Addressing module, so the WS-Addressing is on.
> 
> For some reasons I need to use the old version of the Addressing
> specification. In the client side I've modified it to be something like:
> 
> org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
> org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE
> 
> my question is now, how do I force the axis2 server to answer in this
> same version? or is it done automatically?
> 
> I've been looking through the documentation about this kind of
> configuration, but I've not been able to find any options for the
> addressing in the server side.
> 
> Thanks in advance,
> 
> -- 
> Marc de Palol Martínez
> 
> BSC-CNS
> Barcelona Supercomputing Center
> Centro Nacional de Supercomputación 
> e-mail: [EMAIL PROTECTED]
> phone : +34-93 4137946
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Addressig configuration at server's side

2007-08-02 Thread Marc de Palol

Hello all,

I'm running a client/server with axis2 on both sides. I'm using the
Addressing module, so the WS-Addressing is on.

For some reasons I need to use the old version of the Addressing
specification. In the client side I've modified it to be something like:

org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE

my question is now, how do I force the axis2 server to answer in this
same version? or is it done automatically?

I've been looking through the documentation about this kind of
configuration, but I've not been able to find any options for the
addressing in the server side.

Thanks in advance,

-- 
Marc de Palol Martínez

BSC-CNS
Barcelona Supercomputing Center
Centro Nacional de Supercomputación 
e-mail: [EMAIL PROTECTED]
phone : +34-93 4137946


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

Two Server_Config.wsdd or Two different configurations in the same Server_Config.wsdd

2007-08-02 Thread at4david


Hi, I am using Axis with Tomcat and I am using two differents services
deploys in the same Server_Config.wsdd, I need that both services have
different security configurations in its , it is say, I need a

  



  
  

for a service A, and another like this:


  

  
   


for the service B, but I have read that it is not possible to have multiples
requestflow, Have I to deploy each service in a Server_Config.wsdd separate
or can I use the same Server_Config.wsdd to support two differents security
requestflow (one for each service)??

Thanks in advance
-- 
View this message in context: 
http://www.nabble.com/Two-Server_Config.wsdd-or-Two-different-configurations-in-the-same-Server_Config.wsdd-tf4204905.html#a11960747
Sent from the Axis - User mailing list archive at Nabble.com.


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

Two Server_Config.wsdd or Two different configurations in the same Server_Config.wsdd

2007-08-02 Thread at4david


Hi, I am using Axis with Tomcat and I am using two differents services
deploys in the same Server_Config.wsdd, I need that both services have
different security configurations in its , it is say, I need a

  



   
  

for a service A, and another like this:




   
   


for the service B, but I have read that it is not possible to have multiples
requestflow, Have I to deploy each service in a Server_Config.wsdd separate
or can I use the same Server_Config.wsdd to support two differents security
requestflow (one for each service)??

Thanks in advance
-- 
View this message in context: 
http://www.nabble.com/Two-Server_Config.wsdd-or-Two-different-configurations-in-the-same-Server_Config.wsdd-tf4204903.html#a11960742
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: Different binding in auto generated wsdl (soap11, soap12, http)

2007-08-02 Thread Erwin Reinhoud

Hello Keith,
 
Thanks, i did not know that was enough. I'll give it a try.
 
Kind regards,
Erwin
 
 

-Oorspronkelijk bericht-
Van: keith chapman [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 10:30
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


Hi Erwin,

You could use the parameter  true.

Here is a sample services.xml with this parameter.

 
 First axis2 web service 

http://www.w3.org/2004/08/wsdl/in-out " 
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

Mathsclass
true 
 




Thanks,
Keith.


On 8/2/07, Erwin Reinhoud < [EMAIL PROTECTED]> wrote: 

Hello Keith,
 
I 've been wondering about this to, where can i find documentation on how to do 
this (what param in services.xml)? I use Axis2 1.2 and would really like to 
only expose a soap 1.1 service.
 
Thanks.
 
Kind regards,
Erwin

-Oorspronkelijk bericht-
Van: keith chapman [mailto: [EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 6:48
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


Hi Patel,

You can set this parameter in the servoces.xml. Also pack your original wsdl in 
to the meta-inf directory of the aar file.

true

This will forse Axis2 to use your original WSDL. BTW wat is your Axis2 version?

Thanks,
Keith.


On 8/2/07, Patel, Ronak (US SSA) <   [EMAIL 
PROTECTED]> wrote: 

Expanding on Orly Lampert's email from October 2006, I created a wsdl with one 
binding (soap1 binding) and one port with that



binding.



 
When I view the wsdl which is generated by axis (?wsdl) I always get 3



bindings and 3 ports added by axis2 (soap11, soap12 and http). 



 
Now, I want to keep only the SOAP11 port and force Axis to use the Port Name 
that I specify in the WSDL file.



 



Without this in place, there is no way a client written using the original WSDL 
can work with this service.



 
Can anyone help me? I can't seem to find anything on this on the web.

 
Ronak Patel



Software Engineer


BAE Systems S2

 




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




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

Re: Different binding in auto generated wsdl (soap11, soap12, http)

2007-08-02 Thread keith chapman

Hi Erwin,

You could use the parameter  true.

Here is a sample services.xml with this parameter.


 First axis2 web service 

http://www.w3.org/2004/08/wsdl/in-out"; class="
org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

Mathsclass
true





Thanks,
Keith.

On 8/2/07, Erwin Reinhoud <[EMAIL PROTECTED]> wrote:
>
>  Hello Keith,
>
> I 've been wondering about this to, where can i find documentation on how
> to do this (what param in services.xml)? I use Axis2 1.2 and would really
> like to only expose a soap 1.1 service.
>
> Thanks.
>
> Kind regards,
> Erwin
>
> -Oorspronkelijk bericht-
> *Van:* keith chapman [mailto:[EMAIL PROTECTED]
> *Verzonden:* donderdag 2 augustus 2007 6:48
> *Aan:* axis-user@ws.apache.org
> *Onderwerp:* Re: Different binding in auto generated wsdl (soap11, soap12,
> http)
>
> Hi Patel,
>
> You can set this parameter in the servoces.xml. Also pack your original
> wsdl in to the meta-inf directory of the aar file.
>
> true
>
> This will forse Axis2 to use your original WSDL. BTW wat is your Axis2
> version?
>
> Thanks,
> Keith.
>
> On 8/2/07, Patel, Ronak (US SSA) < [EMAIL PROTECTED]> wrote:
> >
> >  Expanding on Orly Lampert's email from October 2006, I created a wsdl with 
> > one binding (soap1 binding) and one port with that
> >
> > binding.
> >
> >
> >
> >
> > When I view the wsdl which is generated by axis (?wsdl) I always get 3
> >
> >
> > bindings and 3 ports added by axis2 (soap11, soap12 and http).
> >
> >
> >
> >
> > Now, I want to keep only the SOAP11 port and force Axis to use the Port 
> > Name that I specify in the WSDL file.
> >
> >
> >
> >
> > Without this in place, there is no way a client written using the original 
> > WSDL can work with this service.
> >
> >
> >
> >
> > Can anyone help me? I can't seem to find anything on this on the web.
> >
> >
> >
> >
> > Ronak Patel
> >
> >
> > Software Engineer
> >
> > BAE Systems S2
> >
> >
> >
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>
>


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

RE: Different binding in auto generated wsdl (soap11, soap12, http)

2007-08-02 Thread Erwin Reinhoud

Hello Keith,
 
I 've been wondering about this to, where can i find documentation on how to do 
this (what param in services.xml)? I use Axis2 1.2 and would really like to 
only expose a soap 1.1 service.
 
Thanks.
 
Kind regards,
Erwin

-Oorspronkelijk bericht-
Van: keith chapman [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 6:48
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


Hi Patel,

You can set this parameter in the servoces.xml. Also pack your original wsdl in 
to the meta-inf directory of the aar file.

true

This will forse Axis2 to use your original WSDL. BTW wat is your Axis2 version?

Thanks,
Keith.


On 8/2/07, Patel, Ronak (US SSA) <   [EMAIL 
PROTECTED]> wrote: 

Expanding on Orly Lampert's email from October 2006, I created a wsdl with one 
binding (soap1 binding) and one port with that


binding.


 
When I view the wsdl which is generated by axis (?wsdl) I always get 3


bindings and 3 ports added by axis2 (soap11, soap12 and http). 


 
Now, I want to keep only the SOAP11 port and force Axis to use the Port Name 
that I specify in the WSDL file.


 


Without this in place, there is no way a client written using the original WSDL 
can work with this service.


 
Can anyone help me? I can't seem to find anything on this on the web.


 
Ronak Patel


Software Engineer
BAE Systems S2

 




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

Re: WSDL problem

2007-08-02 Thread Amila Suriarachchi

use -ap option if you want to generate the code for all ports.

On 8/1/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Yes no problem.
>
> Thanks,
> Keith.
>
> On 8/1/07, Snehil Brajpuriya <[EMAIL PROTECTED]> wrote:
> >
> >  Thanks Keith,
> >
> > Just to confirm following will be the action for 2 operations and
> > address for service respectively -
> >
> >
> >
> > 1.
> >
> >  > 
> > soapAction="http://tbd/PersonalDetailsSvc/PersonalDetailsInq
> > "
> >
> >
> >
> > 2.
> >
> >  
> >  > 
> > soapAction="http://tbd/PersonalDetailsSvc/PersonalDetailsUpdt
> > "
> >
> >   3.
> >
> >  > location="http://tbd/PersonalDetailsSvc"/>
> > 
> >
> >
> >
> > Thanks
> >
> > Snehil
> >
> >   --
> >
> > *From:* keith chapman [mailto:[EMAIL PROTECTED]
> > *Sent:* Wednesday, August 01, 2007 6:49 PM
> > *To:* axis-user@ws.apache.org
> > *Subject:* Re: WSDL problem
> >
> >
> >
> > Hi Sehil,
> >
> > You dont need to have two ports and two bindings. According to your WSDL
> > both bindings are identicle just a difference in the name so can have it in
> > the same binding. The following might be what your looking for
> >
> > 
> >  >  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
> > " xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
> >   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/ "
> >   xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> >   xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/ "
> >   xmlns:ns="urn:abc:XSD:a" xmlns:ns1="urn:abc:XSD:b"
> >   targetNamespace="urn:abc:XSD:a">
> > 
> >  > elementFormDefault="qualified"
> > attributeFormDefault="unqualified"
> > xmlns="urn:abc:XSD:b"
> > xmlns:xsd=" http://www.w3.org/2001/XMLSchema";
> > xmlns:y="urn:abc:XSD:a">
> >  > schemaLocation=" baseschemas.xsd"/>
> > 
> > 
> > 
> >  > ref="ns1:PersonalInfoInqRq"/>
> > 
> > 
> > 
> > 
> > 
> > 
> >  > ref="ns1:PersonalInfoInqRs"/>
> > 
> > 
> > 
> >
> > 
> > 
> > 
> >  > ref="ns1:PersonalInfoModRq"/>
> > 
> > 
> > 
> > 
> > 
> > 
> >  > ref="ns1:PersonalInfoModRs"/>
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> >  >  type="ns:PersonalDetailsInq_portType">
> >  >   transport="http://schemas.xmlsoap.org/soap/http
> > "/>
> > 
> >  > 
> > soapAction="http://tbd/PersonalDetailsSvc/PersonalDetailsInq
> > "
> > style="document"/>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  > 
> > soapAction="http://tbd/PersonalDetailsSvc/PersonalDetailsUpdt
> > "
> > style="document"/>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> >  >   binding="ns:PersonalDetailsInq_binding">
> >  > location="
> > http://tbd/PersonalDetailsSvc/PersonalDetailsInq"/>
> > 
> > 
> > 
> >
> > Thanks,
> > Keith.
> >
> > On 8/1/07, *Snehil Brajpuriya* <[EMAIL PROTECTED]> wrote:
> >
> > Hi ,
> > Can any expert give some guidance here -
> >
> > I am having this WSDL file. I want to have two operation in one service
> > PersonalDetailsSvc.
> > When I convert this to Java however only first binding and first port
> > definition is getting converted.
> > Am I doing something wrong here?
> > Should I have only one binding(one binding name) having two port types
> > and
> > then only one port?
> > What happends when I have two port definition in one service?
> >
> > 
> >  > xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/
> > "xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
> > xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:soapenc=" http://schemas.xmlsoap.org

Re: Problem with stub generated

2007-08-02 Thread Amila Suriarachchi

fixed the issue in both trunk and branch. please have a look at with a
nighly build.

Amila.

On 8/1/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
>
> thanks, I could recrate the problem and looking into it. please put a
> jira.
>
> On 8/1/07, Mehar <[EMAIL PROTECTED] > wrote:
> >
> > Hai Amila
> >
> > I cannot give u my wsdl, did u try with a soap header with a single
> > element??
> >
> > Code works fine with soap headers with multiple elements like
> > 
> >  
> > 
> >
> > My suspect is soapHeaderBlockSource565.addChild(
> > omElementSource565.getFirstElement ());
> >
> > if the omElementSource565 = 31231312321
> >
> > Are u sure like omElementSource565.getFirstElement () returns this
> > 31231312321??
> >
> > I am not sure about this anyways i dont know much about AXIOM
> >
> > Thanks in advance
> > Mehar
> >
> > On 8/1/07, Amila Suriarachchi < [EMAIL PROTECTED]> wrote:
> > >
> > > I wrote a sample service which uses the Headers and it worked fine.
> > >
> > > Can you please send your wsdl and Client?
> > >
> > > Amila.
> > >
> > > On 8/1/07, Mehar < [EMAIL PROTECTED]> wrote:
> > > >
> > > > Hai All,
> > > >
> > > > I have a wsdl with a singele service and many operations.
> > > >
> > > > The typical payload for an operation will look like this
> > > > 
> > > >
> > > > 
> > > > 123123123141341
> > > > 32312312312312
> > > >
> > > > 
> > > > 
> > > > afjlksdajflas
> > > > fsdakljfaskljf
> > > > 
> > > > 
> > > >
> > > > 
> > > >
> > > > 
> > > > 
> > > >
> > > > 
> > > >
> > > > wsdl fragments corrosponding to that are given here
> > > >
> > > > 
> > > >  > > > targetNamespace=""
> > > > elementFormDefault="qualified">
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > >
> > > > 
> > > > 
> > > >  > > > element="types:sessionid" />
> > > > 
> > > >
> > > > 
> > > >  > > > element="wsse:Security" />
> > > > 
> > > >
> > > > 
> > > >  > > > />
> > > > 
> > > >
> > > >
> > > > 
> > > > 
> > > >  > > > part="sessionTokenHeader" use="literal" />
> > > >  > > > part="usernameTokenHeader" use="literal" />
> > > >  > > > part="sourceTokenHeader" use="literal" />
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > The stub got generated has the following code to add the headers
> > > > // add the children only if the parameter is not null
> > > > if (sessionId563!=null){
> > > >
> > > >
> > > > org.apache.axiom.om.OMElement omElementsessionId563 =
> > > > toOM(sessionId563, optimizeContent(new 
> > > > javax.xml.namespace.QName("", "myoperation")));
> > > >
> > > > org.apache.axiom.soap.SOAPHeaderBlock soapHeaderBlocksessionId563 =
> > > > env.getHeader().addHeaderBlock(omElementsessionId563.getLocalName(),
> > > > omElementsessionId563.getNamespace());
> > > >
> > > > soapHeaderBlocksessionId563.addChild(
> > > > omElementsessionId563.getFirstElement());
> > > >
> > > > }
> > > >
> > > > // add the children only if
> > > > the parameter is not null
> > > > if (security564!=null){
> > > >
> > > >
> > > > org.apache.axiom.om.OMElement omElementsecurity564 =
> > > > toOM(security564, optimizeContent(new javax.xml.namespace.QName("",
> > > > "myoperation")));
> > > >
> > > > org.apache.axiom.soap.SOAPHeaderBlock soapHeaderBlocksecurity564 =
> > > > env.getHeader().addHeaderBlock(omElementsecurity564.getLocalName(),
> > > > omElementsecurity564.getNamespace ());
> > > >
> > > > soapHeaderBlocksecurity564.addChild(
> > > > omElementsecurity564.getFirstElement());
> > > >
> > > > }
> > > >
> > > > // add the children only if
> > > > the parameter is not null
> > > > if (source565!=null){
> > > >
> > > >
> > > > org.apache.axiom.om.OMElement omElementSource565 = toOM(Source565,
> > > > optimizeContent(new javax.xml.namespace.QName("x",
> > > > "myoperation")));
> > > >
> > > > org.apache.axiom.soap.SOAPHeaderBlock soapHeaderBlocksource565 =
> > > > env.getHeader().addHeaderBlock(omElementSource565.getLocalName(),
> > > > omElementSource565.getNamespace());
> > > >
> > > > soapHeaderBlockSource565.addChild(omElementSource565.getFirstElement
> > > > ());
> > > >
> > > > }
> > > >
> > > > If u look at the bold stuff results in a null pointer, here i will
> > > > explain how
> > > > omElementsource565 = 31234234213
> > > > soapHeaderBlocksource565 =
> > > > omElementSource5

50 matches

Mail list logo