Re: [axis2-rampart1.1] Error parsing SoapFaults by client-side code once rampart-1.1 is deployed
thanks for the reply. We are using soap 1.1 in hopes of being compatible
with non-axis2 clients. I'll have to check to see if we can change.
Mary
Ruchith Fernando wrote:
This is a know issues as reported here :
https://issues.apache.org/jira/browse/AXIS2-1643
https://issues.apache.org/jira/browse/WSCOMMONS-104
If you can use SOAP 1.2 then this issue can be avoided.
Thanks,
Ruchith
On 12/16/06, Mary Thompson <[EMAIL PROTECTED]> wrote:
I have been fighting with SoapFaults failing to parse once rampart 1.1
is deployed ever since I moved to Axis2.1.1. It did work in axis2.1.0.
I am currently using the December 15 snapshot of axis1.1.1.1 and the
rampart1.1 release. Maybe I am missing some trick in deploying
rampart. If any one else is getting this to work, I would love to know
how.
I have been working with the code is samples/faulthandling since it
parallels my real code. The stub is is generated by WSDL2Java. The
response message looks correct to me:
soapenv:Client
Account does not exist!
http://example";>
13
Without rampart deployed the client program catches a
AccountNotExistFaultMessageException. With rampart deployed it geta the
following exception:
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
To duplicate this result try:
a recent axis2-1.1 release.
set AXIS2_HOME to where the zip file was unziped
start the server running locally by bin/axis2server.sh
cd to samples/faulthandling
ant generate.service - builds and deploys the service locally
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
should work
[java] Withdrawing 400 dollars from account#13
[java] Account#13 does not exist
Then deploy a rampart module in the samples/faulthandling client.
Download and unzip rampart.1.1.zip
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip
Copy the rampart libraries to axis2-home per rampart release instructions
pd ../../../rampart-1.1/samples
ant -- copies 7 jar files from ../lib to AXIS2_HOME/lib
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
Test still works
Deploy rampart
create client/repo/axis2.xml by copying
rampart-1.1/samples/basic/sample01/client.axis2.xml, then copy the
rampart.1.1.mar file to client/repo/modules/rampart.1.1.mar
Then you need to edit BankClient.java to add the line
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("client/repo",
"client/repo/axis2.xml");
now
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
fails with
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
It seems like it is caused by some confusion of classes, but I haven't
figured which ones yet.
Mary Thompson
-
Mary R. Thompson<[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to deploy Axis2 in https
How have you configured HTTPS at the service? (the servlet container axis2 is deployed). Does it require the client to authenticate itself with its certificate? if so you MUST add the client cert into the container's trust store and then configure the client's following JSSE properties properly. javax.net.ssl.keyStore javax.net.ssl.keyStoreType javax.net.ssl.keyStoreType However even if the HTTPS config of the container does not require client auth you MUST have the CA cert of the CA that signed the container's cert in your jre/lib/security/cacerts store or if it uses a self signed cert then you can override trust store config with the JSSE properties. Please see here for more information [1] Thanks, Ruchith [1] http://java.sun.com/products/jsse/install.html On 12/16/06, Subash Devkota <[EMAIL PROTECTED]> wrote: Hi all, I have problem deploying axis2 1.0 in https. I need to deploy my axis2 1.0 server over https application. I used following configuration in axis2.xml in client side. HTTP/1.1 chunked The web service works well when i use it in http. But when axis2 server is deployed in https, the client can not connect to server (axis2 1.0 where web services is deployed). I am using self signed certificate in client side. I added the certificate of the client in https server's trusted certificate key store. But could not connect to server. It throws nullPointerException while trying to connect web service. I tried using CA certified key in the client side. In this case, it works. I need to connect to axis2 1.0 server deployed over https with client that has self signed certificate. Does any one knows how to configure the client for this? Thanks in advance. Subash PRIVACY NOTICE This email and any attachments may be confidential and/or privileged. Use of the information contained in this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and delete this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Axis2 filling my /var/tmp with axis.jar
Please log a Jira with details about your environment.. ~Thilina On 12/16/06, sean curtis <[EMAIL PROTECTED]> wrote: After searching the docs and mailing list, I was unable to come up with a way to get Axis2 to stop making what looks like "tmp" versions of all my jars (i.e. axismyjar.jar) in /var/tmp, each time I deploy a new version of my .aar files. This problem is being multiplied exponentially by multiple developers working on the same host, so if anyone has come up with a handy way of either having axis2 write to, perhaps, /dev/null, or cleaning itself up, or not doing it all, it would be appreciated. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can axis 1.4 and 2.0 be run simultaneously in the same deployment?
correction Axis2 HAS rest support (sorry pet distraction!) M- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: Jim Nash To: axis-user@ws.apache.org Sent: Friday, December 15, 2006 7:22 PM Subject: Can axis 1.4 and 2.0 be run simultaneously in the same deployment? ... or is this just a bad idea? thx, jim ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Re: Can axis 1.4 and 2.0 be run simultaneously in the same deployment?
Hi Jim- many deltas between the 2 Axis versions 1.x supports RPC and Axis2 doesnt and most of all REST support in Axis2 and Axis2 has no support for REST BUT If you could separate the deployments I think this would be a great way to test 2 identical services to capture performance metrics between the 2 so in effect there would have to be 2 different context's (one called Axis14 and one called Axis2) to that end dims has already published this comparison between the 2 http://www.wso2.net/2006/05/axis2_performance_testing_round_1 HTH Martin-- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ... or is this just a bad idea? thx, jim ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Re: setting actor in the outgoing wsse headers
On 12/15/06, George Stanchev <[EMAIL PROTECTED]> wrote: Hi Ruchith, I have related question though. Say I create my own wsse header and inject it in the outgoing message alongside with the wsse header created by rampart. Would an axis2 rampart just ignore my custom wsse header on the service side? As of now ... we reuse an existing wsse header. Therefore other info will be appended to the header that that you added. If say I have UsernameToken action in the InflowConfiguration, and provide 2 wsse headers - one being the "default" and the other targeted towards a particular actor - would the service-side rampart just ignore the "actor"-ed one? There is some support to specify the actor in processing the security header in WSS4J. Let me have a closer look at it and see whether this is already supported and how. Thanks, Ruchith George From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Thu 12/14/2006 4:49 PM To: axis-user@ws.apache.org Subject: Re: setting actor in the outgoing wsse headers This is not supported in Rampart right now... Please file a JIRA. The new configuration is based on WS-SecurityPolicy and I'm not sure how we can achieve this with policy. Maybe we should ask the WS-SX folks about it. Thanks, Ruchith On 12/15/06, George Stanchev <[EMAIL PROTECTED]> wrote: > > > > Hi, > > Is there a way to set the actor of the outgoing security headers using > rampart? > > I would like to create 2 security headers on an outgoing message - one with > the > default actor and another targeting a specific actor name. > > I am not able to find a way to do it via the (now deprecated) configuration > methods > using OutflowConfiguration() objects. > > Any suggestions? > > Thanks > > George Stanchev > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the sender > by reply e-mail and destroy all copies of the original message. > -- www.ruchith.org www.wso2.org - 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] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2-rampart1.1] Error parsing SoapFaults by client-side code once rampart-1.1 is deployed
This is a know issues as reported here :
https://issues.apache.org/jira/browse/AXIS2-1643
https://issues.apache.org/jira/browse/WSCOMMONS-104
If you can use SOAP 1.2 then this issue can be avoided.
Thanks,
Ruchith
On 12/16/06, Mary Thompson <[EMAIL PROTECTED]> wrote:
I have been fighting with SoapFaults failing to parse once rampart 1.1
is deployed ever since I moved to Axis2.1.1. It did work in axis2.1.0.
I am currently using the December 15 snapshot of axis1.1.1.1 and the
rampart1.1 release. Maybe I am missing some trick in deploying
rampart. If any one else is getting this to work, I would love to know how.
I have been working with the code is samples/faulthandling since it
parallels my real code. The stub is is generated by WSDL2Java. The
response message looks correct to me:
soapenv:Client
Account does not exist!
http://example";>
13
Without rampart deployed the client program catches a
AccountNotExistFaultMessageException. With rampart deployed it geta the
following exception:
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
To duplicate this result try:
a recent axis2-1.1 release.
set AXIS2_HOME to where the zip file was unziped
start the server running locally by bin/axis2server.sh
cd to samples/faulthandling
ant generate.service - builds and deploys the service locally
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
should work
[java] Withdrawing 400 dollars from account#13
[java] Account#13 does not exist
Then deploy a rampart module in the samples/faulthandling client.
Download and unzip rampart.1.1.zip
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip
Copy the rampart libraries to axis2-home per rampart release instructions
pd ../../../rampart-1.1/samples
ant -- copies 7 jar files from ../lib to AXIS2_HOME/lib
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
Test still works
Deploy rampart
create client/repo/axis2.xml by copying
rampart-1.1/samples/basic/sample01/client.axis2.xml, then copy the
rampart.1.1.mar file to client/repo/modules/rampart.1.1.mar
Then you need to edit BankClient.java to add the line
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("client/repo",
"client/repo/axis2.xml");
now
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
fails with
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
It seems like it is caused by some confusion of classes, but I haven't
figured which ones yet.
Mary Thompson
-
Mary R. Thompson<[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
--
--
www.ruchith.org
www.wso2.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[axis2-rampart1.1] Error parsing SoapFaults by client-side code once rampart-1.1 is deployed
I have been fighting with SoapFaults failing to parse once rampart 1.1
is deployed ever since I moved to Axis2.1.1. It did work in axis2.1.0.
I am currently using the December 15 snapshot of axis1.1.1.1 and the
rampart1.1 release. Maybe I am missing some trick in deploying
rampart. If any one else is getting this to work, I would love to know how.
I have been working with the code is samples/faulthandling since it
parallels my real code. The stub is is generated by WSDL2Java. The
response message looks correct to me:
soapenv:Client
Account does not exist!
http://example";>
13
Without rampart deployed the client program catches a
AccountNotExistFaultMessageException. With rampart deployed it geta the
following exception:
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
To duplicate this result try:
a recent axis2-1.1 release.
set AXIS2_HOME to where the zip file was unziped
start the server running locally by bin/axis2server.sh
cd to samples/faulthandling
ant generate.service - builds and deploys the service locally
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
should work
[java] Withdrawing 400 dollars from account#13
[java] Account#13 does not exist
Then deploy a rampart module in the samples/faulthandling client.
Download and unzip rampart.1.1.zip
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_1/rampart-1.1.zip
Copy the rampart libraries to axis2-home per rampart release instructions
pd ../../../rampart-1.1/samples
ant -- copies 7 jar files from ../lib to AXIS2_HOME/lib
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
Test still works
Deploy rampart
create client/repo/axis2.xml by copying
rampart-1.1/samples/basic/sample01/client.axis2.xml, then copy the
rampart.1.1.mar file to client/repo/modules/rampart.1.1.mar
Then you need to edit BankClient.java to add the line
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("client/repo",
"client/repo/axis2.xml");
now
ant run.client -Durl=http://localhost:8080/axis2/services/BankService
-Daccount=13 -Damt=400
fails with
[java] Withdrawing 1000 dollars from account#13
[java] java.lang.ClassCastException:
org.apache.axiom.om.impl.llom.OMElementImpl
[java] at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:215)
[java] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
It seems like it is caused by some confusion of classes, but I haven't
figured which ones yet.
Mary Thompson
-
Mary R. Thompson<[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] databinding parameters
Let me explain my use case and hopefully people have answers to my query; I can an existing interface/implementation that I want to expose as web service. I use Java2Wsdl to generate the wsdl file, which includes the xsd for the defined objects. For examples, I want to expose getUser(com.comergent.api.UserBean b) as a web service. Since the client should have no dependency on the server object/classes (com.comergent.api.UserBean), the client uses the generated classes (com.comergent.xsd.UserBean) from a databinding scheme. The client uses WSDL2Java and invokes the operation using the generated classes. The server on having received the call has to construct its version of a bean (com.comergent.api.UserBean) that adheres to the XSD specified in the WSDL. My question is how do i go about doing this? One possibility is to register custom MessageReceiver and code to AXIOM api's to construct the bean. But, is there an alternative approach that I can adopt. Any help/insight will be greatly appreciated. Thanks, vedha -- Vedha Vijayan Senior Software Engineer Comergent Technologies Inc. Ph: 650 232 5833 Fax: 650 232 6010 Email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can axis 1.4 and 2.0 be run simultaneously in the same deployment?
... or is this just a bad idea? thx, jim ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
[axis2] Axis2 filling my /var/tmp with axis.jar
After searching the docs and mailing list, I was unable to come up with a way to get Axis2 to stop making what looks like "tmp" versions of all my jars (i.e. axismyjar.jar) in /var/tmp, each time I deploy a new version of my .aar files. This problem is being multiplied exponentially by multiple developers working on the same host, so if anyone has come up with a handy way of either having axis2 write to, perhaps, /dev/null, or cleaning itself up, or not doing it all, it would be appreciated. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Help handling faults as exceptions
Mary, El vie, 15-12-2006 a las 10:53 -0800, Mary Thompson escribió: > Javier, >Did you ever figure this out? There is a faulthandling example in the > axis2-1.1 release that generates code that looks like yours and does > work. I have also been using the same wsdl/code pattern with success. Thanks for pointing out the example. It confirmed what I feared. Namely, that the server I'm working with is sending unwrapped fault messages. In other words, the fault/exception name is passed inside the faultcode element and the fault's children are placed directly inside the detail element. Fortunately the fault's detail will only contain one child in this case, so I can hack up the WSDL and pretend the child is a fault in its own right, but this work around won't work in a more general case with several children. In the end and as far as I understand SOAP (i.e., superficially), it boils down to the lack of support for wrapped messages. > My cases all fail as soon as I engage the rampart1.1 module on the > client side, giving the error I'm afraid I don't use rampart myself and I don't have the source code for AXIOM at hand, so I can't see what's causing the class cast exception. This particular error shouldn't be hard to figure out by looking at the code, though. > > java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl > at > org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101) > at > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:312) > at example.BankServiceStub.withdraw(BankServiceStub.java:173) > at example.BankClient.main(BankClient.java:59) Thanks, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: [Axis2]Help handling faults as exceptions
Javier,
Did you ever figure this out? There is a faulthandling example in the
axis2-1.1 release that generates code that looks like yours and does
work. I have also been using the same wsdl/code pattern with success.
My cases all fail as soon as I engage the rampart1.1 module on the
client side, giving the error
java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl
at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:312)
at example.BankServiceStub.withdraw(BankServiceStub.java:173)
at example.BankClient.main(BankClient.java:59)
Are you using rampart or getting errors without it?
Mary
-
Mary R. Thompson<[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
--
Javier Kohen wrote:
Hi,
There is this webservice that I've written the WSDL for. I want to
handle the fault it returns as an exception on the client side. The code
generated by WSDL2Java from Axis1.1 that is supposed to convert the
AxisFault into an AuthenticationFailedMessageException (see below) seems
fishy to me, as it will never succeed. Namely it tries to map the QName
of the detail element with help of the faultExeptionNameMap (sic) when
this map only contains a reference to the faultcode class. This of
course fails, and thus the exception is never generated; the AxisFault
is re-thrown instead.
I don't understand why the detail is being used instead of the
faultcode. I believe the WSDL is correct, but please let me know if
there is something I'm doing wrong here.
When debugging the AxisFault catch block below I see that faultElt is
assigned an ElementA element, which isn't in the exception maps.
Moreover, the setFaultMessage method of
AuthenticationFailedMessageException is defined to take a
mypackage.AuthenticationFailed instance and not mypackage.ElementA, so
the code obviously expects faultElt to contain an AFME. Furthermore,
there is an explicit check for instance-of that exception at the end of
the block that is but dead code currently.
Even a hint on how to workaround the generated code manually for now
would be very appreciated. I couldn't find out how to extract the
AuthenticationFailed element from the AxisFault, which I need to pass to
fromOM, so my progress is temporarily blocked by this issue.
The generated code:
private void populateFaults(){
faultExeptionNameMap.put( new javax.xml.namespace.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException"
);
faultExeptionClassNameMap.put(new
javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException");
faultMessageMap.put( new javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.MyServiceStub$AuthenticationFailed"
);
faultExeptionNameMap.put( new javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException"
);
faultExeptionClassNameMap.put(new
javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException");
faultMessageMap.put( new javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.MyServiceStub$AuthenticationFailed"
);
faultExeptionNameMap.put( new javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException"
);
faultExeptionClassNameMap.put(new
javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.AuthenticationFailedMessageException");
faultMessageMap.put( new javax.xml.mypackage.QName(
"",
"AuthenticationFailed"),
"mypackage.MyServiceStub$AuthenticationFailed"
);
}
public mypackage.MyServiceStub.MyOperationResponse
MyOperation(...
// ...
}catch(org.apache.axis2.AxisFault f){
org.apache.axiom.om.OMElement faultElt = f.getDetail();
if (faultElt!=null){
if
(faultExeptionNameMap.containsKey(faultElt.getQName())){
[Axis2] How to deploy Axis2 in https
Hi all, I have problem deploying axis2 1.0 in https. I need to deploy my axis2 1.0 server over https application. I used following configuration in axis2.xml in client side. HTTP/1.1 chunked The web service works well when i use it in http. But when axis2 server is deployed in https, the client can not connect to server (axis2 1.0 where web services is deployed). I am using self signed certificate in client side. I added the certificate of the client in https server's trusted certificate key store. But could not connect to server. It throws nullPointerException while trying to connect web service. I tried using CA certified key in the client side. In this case, it works. I need to connect to axis2 1.0 server deployed over https with client that has self signed certificate. Does any one knows how to configure the client for this? Thanks in advance. Subash PRIVACY NOTICE This email and any attachments may be confidential and/or privileged. Use of the information contained in this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and delete this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] com.ctc.wstx.exc.WstxEOFException
Hi everyone,
Here's some additional info to my problem:
I made a simple but interesting experiment: I wrote a HTML form to post
something to the webservice
and debugged the AxisServlet.doPost() method as before.
This time the InputStream contained the data I posted.
The webservice failed of course, as the posted data was no valid soap
request.
But something seems to cut off the request body if it's containing XML.
Regards,
H. Herrmann
Hi everyone,
I get following exception as response when accessing the Version
webservice from the Axis 2-1.1
distribution:
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:308)
at sample.axisversion.VersionStub.getVersion(VersionStub.java:155)
at Test.start(Test.java:11)
at Test.main(Test.java:18)
I generated the stub classes with wsdl2java and wrote following test
class:
import sample.axisversion.VersionStub;
import sample.axisversion.VersionStub.GetVersionResponse;
public class Test {
public void start()
throws Exception
{
VersionStub versionStub = new
VersionStub("http://localhost:8080/axis2/services/Version";);
GetVersionResponse response = versionStub.getVersion();
System.out.println(response.get_return());
}
public static void main(String[] args)
throws Exception{
Test test = new Test();
test.start();
}
}
This is my system:
Windows XP (SP2)
Java 1.5.0 Update 10
Apache Tomcat 6.0.2
Axis 2-1.1 webapp (from war file)
Tomcat starts up without error messages, and the Axis2 webapp is
available. The Version service and
its operation getVersion is listed and marked as active.
The validation page shows following message:
There was a problem in Axis2 version service , may be the service not
available or some thing has gone
wrong. But this does not mean system is not working ! Try to upload
some other service and check to see
whether it is working.
The rest of this page seems to be ok (I also get the message "The core
axis2 libraries are present.").
I did some debugging and found out that in the
AxisServlet.doPost()-method the HttpServletRequest's
InputStream is empty.
I checked the communication with TCPMon - but the request seemed to be ok.
Here are the messages:
Request:
POST /axis2/services/Version HTTP/1.1
User-Agent: Axis2
Host: 127.0.0.1:
Transfer-Encoding: chunked
Content-Type: application/soap+xml;
charset=UTF-8;action="urn:getVersion";
c0
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>/>
0
Response:
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=63E04CA3673054DE46016A969755DF4B; Path=/axis2
Content-Type: application/soap+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 15 Dec 2006 16:43:19 GMT
Connection: close
320
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing/noneurn:uuid:759F1D5C854B55ED1511662009998903http://www.w3.org/2005/08/addressing/soap/faultsoapenv:Senderxml:lang="en-US">com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in
prolog
at [row,col {unknown-source}]:
[1,0]
0
Does anyone have a clue?
Thanks and best regards,
H. Herrmann
--
? TourismusSuite - Ihre Destination im Griff
++ Internet Booking Engine ++ Touristisches Content Management ++
Destinations Management
Erfahren Sie mehr unter www.tourismussuite.com
--
*Harald Herrmann*
Backend / Entwicklung
inexweb ralf emanuel GmbH
Hellersbergstraße 2a
D-41460 Neuss
Fon: +49 (0) 21 31 / 3 66 60-84
Fax: +49 (0) 21 31 / 3 66 60-88
www.inexweb.de
Re: Unknown message label
El vie, 15-12-2006 a las 14:18 +0200, schalk escribió: > Greetings All, > > When running the code below I get the following error: > Unknown message label In > OperationClient opClient = > sender.createClient(ServiceClient.ANON_OUT_ONLY_OP); > MessageContext mc = new MessageContext(); > MessageContext resp = > opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE); Given that you have an out-only operation, and by looking at the Javadoc for the WSDLConstants class, I'd think you need to pass MESSAGE_LABEL_OUT_VALUE instead. Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: Esta parte del mensaje está firmada digitalmente
Problems with exception mapping
Hi, I'm exposing a method of an EJB as a Web Service with Axis (actually with JBoss 3.2.1 and JBoss.NET which uses Axis). This method declares an exception which doesn't extend java.rmi.RemoteException so in the resulting WSDL it appears as a wsdl:fault element. Axis can't map automatically all the exception's fields (it has a java.util.Collection of an Error class I developed) so I wrote a custom Axis serializer, in order to produce the correct WSDL and the correct runtime serialization of exception content. WSDL now is correct but the serialize() method of my serializer is never called... Any idea? Or pointers to tutorials/other posts/...? Thanks, Andrea - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl and namespaces
Issue is closed. request parameters must be in same sequence as in wsdl... thx. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] com.ctc.wstx.exc.WstxEOFException
Hi everyone,
I get following exception as response when accessing the Version
webservice from the Axis 2-1.1
distribution:
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:308)
at sample.axisversion.VersionStub.getVersion(VersionStub.java:155)
at Test.start(Test.java:11)
at Test.main(Test.java:18)
I generated the stub classes with wsdl2java and wrote following test class:
import sample.axisversion.VersionStub;
import sample.axisversion.VersionStub.GetVersionResponse;
public class Test {
public void start()
throws Exception
{
VersionStub versionStub = new
VersionStub("http://localhost:8080/axis2/services/Version";);
GetVersionResponse response = versionStub.getVersion();
System.out.println(response.get_return());
}
public static void main(String[] args)
throws Exception{
Test test = new Test();
test.start();
}
}
This is my system:
Windows XP (SP2)
Java 1.5.0 Update 10
Apache Tomcat 6.0.2
Axis 2-1.1 webapp (from war file)
Tomcat starts up without error messages, and the Axis2 webapp is
available. The Version service and
its operation getVersion is listed and marked as active.
The validation page shows following message:
There was a problem in Axis2 version service , may be the service not
available or some thing has gone
wrong. But this does not mean system is not working ! Try to upload
some other service and check to see
whether it is working.
The rest of this page seems to be ok (I also get the message "The core
axis2 libraries are present.").
I did some debugging and found out that in the
AxisServlet.doPost()-method the HttpServletRequest's
InputStream is empty.
I checked the communication with TCPMon - but the request seemed to be ok.
Here are the messages:
Request:
POST /axis2/services/Version HTTP/1.1
User-Agent: Axis2
Host: 127.0.0.1:
Transfer-Encoding: chunked
Content-Type: application/soap+xml;
charset=UTF-8;action="urn:getVersion";
c0
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>/>
0
Response:
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=63E04CA3673054DE46016A969755DF4B; Path=/axis2
Content-Type: application/soap+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 15 Dec 2006 16:43:19 GMT
Connection: close
320
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing/noneurn:uuid:759F1D5C854B55ED1511662009998903http://www.w3.org/2005/08/addressing/soap/faultsoapenv:Senderxml:lang="en-US">com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in
prolog
at [row,col {unknown-source}]:
[1,0]
0
Does anyone have a clue?
Thanks and best regards,
H. Herrmann
RE: setting actor in the outgoing wsse headers
Hi Ruchith, I have related question though. Say I create my own wsse header and inject it in the outgoing message alongside with the wsse header created by rampart. Would an axis2 rampart just ignore my custom wsse header on the service side? If say I have UsernameToken action in the InflowConfiguration, and provide 2 wsse headers - one being the "default" and the other targeted towards a particular actor - would the service-side rampart just ignore the "actor"-ed one? George From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Thu 12/14/2006 4:49 PM To: axis-user@ws.apache.org Subject: Re: setting actor in the outgoing wsse headers This is not supported in Rampart right now... Please file a JIRA. The new configuration is based on WS-SecurityPolicy and I'm not sure how we can achieve this with policy. Maybe we should ask the WS-SX folks about it. Thanks, Ruchith On 12/15/06, George Stanchev <[EMAIL PROTECTED]> wrote: > > > > Hi, > > Is there a way to set the actor of the outgoing security headers using > rampart? > > I would like to create 2 security headers on an outgoing message - one with > the > default actor and another targeting a specific actor name. > > I am not able to find a way to do it via the (now deprecated) configuration > methods > using OutflowConfiguration() objects. > > Any suggestions? > > Thanks > > George Stanchev > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the sender > by reply e-mail and destroy all copies of the original message. > -- www.ruchith.org www.wso2.org - 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]
Spring framework-ws 1.0
Does anyone use Spring framework-WS 1.0 along with Axis2 here? We are new to Web Services and we want to follow certain design pattern or framework. framework. It was decided to use Axis2 and I just wonder if it worth the trouble to look into Spring framework and Spring framework-WS. Thanks for any comments. Danny
Setting nillable = false in WSDL
Hi All, I am using Axis 1.2 as my soap engine. The WSDL file generated by Axis sets all 'nillable' attribute for all elements to true. Is there any way I can get the 'nillable' property to true or false in a declarative fashion...i.e for some elements, I want it to be set to true and false for others. Thanks, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 HttpRequest
Hi Roshan, There is work around if you want to access the contents of HttpRequest object. You may place a ServletFilter before AxisServlet and modify the HttpRequest object as desired. Hope this helps, - Sridhar. On 12/14/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote: Is it possible to get the incoming HTTPRequest object from the OperationContext when the web service is invoked? Or how about the HttpSession? *Roshan Punnoose* Phone: 301-497-6039 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Security settings for Axis on Weblogic.
Hi. I'm using Axis v. 1-4 on a Weblogic 8.1 SP4. My webservice is a deployed method on a EJB, and this method calls some existing functionality on the EJB (deployed on Weblogic). My problem is that I need to set some security settings for the Axis, but I'm not sure how I can do this. When I call the method now, the webservice invokes the method on the EJB, and I get a unauthorized message because the user "guest" doesn't have permissions to call the method. So how do I set the username/password for Axis? Regards, Espen _ Alt i én. Få Yahoo! Mail med adressekartotek, kalender og notisblokk. http://no.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: module.xml not found on Axis2 / Weblogic 8.1
Hi,
In the case of WAR distribution, if you set
in weblogic.xml to true[1] then you shouldn't need to override default
CLASSPATH. Otherwise, I could manage to handle it by adding stax-api-1.0.jar
and xbean-2.1.0.jar to the CLASSPATH[2].
Actually, if you don't use WAR distribution and rather prepare your own EAR
package by embedding Axis2, then, AFAIK, it's not going to work.
Regards,
Ali Sadik Kumlali
[1] http://www.mail-archive.com/axis-user@ws.apache.org/msg21989.html
[2] http://www.mail-archive.com/axis-user@ws.apache.org/msg13720.html
- Original Message
From: zze-Basic DRISS S ext RD-MAPS-ISS <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Friday, December 15, 2006 11:16:14 AM
Subject: RE: module.xml not found on Axis2 / Weblogic 8.1
DIV { MARGIN:0px;}Hi,
Could you please specify which Axis2's library should I put before the
weblogic8 webservices jar in the classpath?
Thanks,
Driss
De : Ali Sadik Kumlali [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 14 décembre 2006 19:21
À : axis-user@ws.apache.org
Objet : Re: module.xml not found on Axis2 / Weblogic 8.1
Hi Slim,
You should use exploded WAR. Please, look at here[1] for more information.
Regards,
Ali Sadik Kumlali
[1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13935.html
- Original Message
From: Slim Driss <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Thursday, December 14, 2006 4:06:44 PM
Subject: module.xml not found on Axis2 / Weblogic 8.1
Hi,
I'm trying to use Axis2 with Weblogic 8.1 (jrockit 1.4.2_08). After deploying
the axis2.war and I've got the error listed below.
I found this link http://ws.apache.org/axis/java/install.html#WebLogic8.1 but
is treating Axis1 with Weblogic. So I've tried without succeeding to apply
those suggestions on Axis2 with Weblogic8.1.
Could you please point me to a solution to resolve this issue.
---
.
CLASSPATH=C:\apps\axis2-
1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2-1.1\lib\axis2-saaj-1.1.jar;;C:\bea_SIP2.2\JROCKI~1\lib\tools.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic_sp.jar;C:\bea_SIP2.2\wlss220\telco\lib\wcp_sip_core.jar;C:\bea_SIP2.2\wlss220\telco\auxlib\sipservlet.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic.jar;C:\bea_SIP2.2\wlss220\server\lib\jsafeFIPS.jar;C:\bea_SIP2.2\wlss220\common\eval\pointbase\lib\pbserver44.jar;C:\bea_SIP2.2\wlss220\com
mon\eval\pointbase\lib\pbclient44.jar;C:\bea_SIP2.2\JROCKI~1\jre\lib\rt.jar;C:\bea_SIP2.2\wlss220\server\lib\webservices.jar;C:\apps\axis2-1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2-
1.1\lib\axis2-saaj-1.1.jar;
.
PATH=C:\bea_SIP2.2\wlss220\server\bin;C:\bea_SIP2.2\JROCKI~1\jre\bin;C:\bea_SIP2.2\JROCKI~1\bin;C:\apps\apache-ant-1.6.5\bin;C:\apps\jdk1.5.0_09\bin;C:\apps\axis2-1.1\bin;C:\oracle\product\10.2.0\client_1\bin;C:\oracle\ora92\bin;C:\Program
Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program
Files\Microsoft SQL
Server\90\Tools\binn\;C:\bea_SIP2.2\wlss220\server\bin\oci920_8
.
***
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\[hostname]:[port]\console *
***
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 45 CET>
<14 dÚc. 2006 14 h 46 CET>
14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.WarBasedAxisConfigurator
getAxisConfiguration
GRAVE: org.apache.axis2.deployment.DeploymentException: module.xml not found
for the module :
zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing-
1.1.mar; nested exception is:
org.apache.axis2.deployment.DeploymentException: module.xml not found
for the module :
zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing-
1.1.mar; nested exception is:
org.apache.axis2.deployment.DeploymentException: module.xml not found
for the module :
zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing-
1.1.mar; nested exception is:
org.apache.axis2.deployment.DeploymentException: module.xml not found
for the module :
zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing-
1.1.mar: loading repository from classpath
14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.D
RE: module.xml not found on Axis2 / Weblogic 8.1
Hi, Could you please specify which Axis2's library should I put before the weblogic8 webservices jar in the classpath? Thanks, Driss De : Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Envoyé : jeudi 14 décembre 2006 19:21 À : axis-user@ws.apache.org Objet : Re: module.xml not found on Axis2 / Weblogic 8.1 Hi Slim, You should use exploded WAR. Please, look at here[1] for more information. Regards, Ali Sadik Kumlali [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13935.html - Original Message From: Slim Driss <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Thursday, December 14, 2006 4:06:44 PM Subject: module.xml not found on Axis2 / Weblogic 8.1 Hi, I'm trying to use Axis2 with Weblogic 8.1 (jrockit 1.4.2_08). After deploying the axis2.war and I've got the error listed below. I found this link http://ws.apache.org/axis/java/install.html#WebLogic8.1 but is treating Axis1 with Weblogic. So I've tried without succeeding to apply those suggestions on Axis2 with Weblogic8.1. Could you please point me to a solution to resolve this issue. --- . CLASSPATH=C:\apps\axis2- 1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2-1.1\lib\axis2-saaj-1.1.jar;;C:\bea_SIP2.2\JROCKI~1\lib\tools.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic_sp.jar;C:\bea_SIP2.2\wlss220\telco\lib\wcp_sip_core.jar;C:\bea_SIP2.2\wlss220\telco\auxlib\sipservlet.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic.jar;C:\bea_SIP2.2\wlss220\server\lib\jsafeFIPS.jar;C:\bea_SIP2.2\wlss220\common\eval\pointbase\lib\pbserver44.jar;C:\bea_SIP2.2\wlss220\com mon\eval\pointbase\lib\pbclient44.jar;C:\bea_SIP2.2\JROCKI~1\jre\lib\rt.jar;C:\bea_SIP2.2\wlss220\server\lib\webservices.jar;C:\apps\axis2-1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2- 1.1\lib\axis2-saaj-1.1.jar; . PATH=C:\bea_SIP2.2\wlss220\server\bin;C:\bea_SIP2.2\JROCKI~1\jre\bin;C:\bea_SIP2.2\JROCKI~1\bin;C:\apps\apache-ant-1.6.5\bin;C:\apps\jdk1.5.0_09\bin;C:\apps\axis2-1.1\bin;C:\oracle\product\10.2.0\client_1\bin;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\bea_SIP2.2\wlss220\server\bin\oci920_8 . *** * To start WebLogic Server, use a username and * * password assigned to an admin-level user. For * * server administration, use the WebLogic Server * * console at http:\\[hostname]:[port]\console* *** <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 46 CET> 14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.WarBasedAxisConfigurator getAxisConfiguration GRAVE: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar: loading repository from classpath 14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.DeploymentEngine loadFromClassPath INFO: Module validation failed Trying to engage a module which is not available : addressing <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> -- Thanks, Slim -- Cordialement, Slim DRISS __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --Translated Message--
WSDL type mapping for List
Hi Axis-Users, I have a simple web service operation which returns a string. This was working fine for me. Recently I needed to change the return type from String to a List(ArrayList). I duly generated the new wsdl and a new client and tried to invoke the newly deployed web service. But it gives me an AXIS fault. I checked the newly generated WSDL and the response element now shows the type as "xsd:anytype". Does this have anything to do with the axis fault that I am getting? Thanks, Chinmay. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: module.xml not found on Axis2 / Weblogic 8.1
Thanks Ali. Slim De : Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Envoyé : jeudi 14 décembre 2006 19:21 À : axis-user@ws.apache.org Objet : Re: module.xml not found on Axis2 / Weblogic 8.1 Hi Slim, You should use exploded WAR. Please, look at here[1] for more information. Regards, Ali Sadik Kumlali [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13935.html - Original Message From: Slim Driss <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Thursday, December 14, 2006 4:06:44 PM Subject: module.xml not found on Axis2 / Weblogic 8.1 Hi, I'm trying to use Axis2 with Weblogic 8.1 (jrockit 1.4.2_08). After deploying the axis2.war and I've got the error listed below. I found this link http://ws.apache.org/axis/java/install.html#WebLogic8.1 but is treating Axis1 with Weblogic. So I've tried without succeeding to apply those suggestions on Axis2 with Weblogic8.1. Could you please point me to a solution to resolve this issue. --- . CLASSPATH=C:\apps\axis2- 1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2-1.1\lib\axis2-saaj-1.1.jar;;C:\bea_SIP2.2\JROCKI~1\lib\tools.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic_sp.jar;C:\bea_SIP2.2\wlss220\telco\lib\wcp_sip_core.jar;C:\bea_SIP2.2\wlss220\telco\auxlib\sipservlet.jar;C:\bea_SIP2.2\wlss220\server\lib\weblogic.jar;C:\bea_SIP2.2\wlss220\server\lib\jsafeFIPS.jar;C:\bea_SIP2.2\wlss220\common\eval\pointbase\lib\pbserver44.jar;C:\bea_SIP2.2\wlss220\com mon\eval\pointbase\lib\pbclient44.jar;C:\bea_SIP2.2\JROCKI~1\jre\lib\rt.jar;C:\bea_SIP2.2\wlss220\server\lib\webservices.jar;C:\apps\axis2-1.1\lib\wstx-asl-3.0.1.jar;C:\apps\axis2-1.1\lib\stax-api-1.0.1.jar;C:\apps\axis2- 1.1\lib\axis2-saaj-1.1.jar; . PATH=C:\bea_SIP2.2\wlss220\server\bin;C:\bea_SIP2.2\JROCKI~1\jre\bin;C:\bea_SIP2.2\JROCKI~1\bin;C:\apps\apache-ant-1.6.5\bin;C:\apps\jdk1.5.0_09\bin;C:\apps\axis2-1.1\bin;C:\oracle\product\10.2.0\client_1\bin;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\bea_SIP2.2\wlss220\server\bin\oci920_8 . *** * To start WebLogic Server, use a username and * * password assigned to an admin-level user. For * * server administration, use the WebLogic Server * * console at http:\\[hostname]:[port]\console* *** <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 45 CET> <14 dÚc. 2006 14 h 46 CET> 14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.WarBasedAxisConfigurator getAxisConfiguration GRAVE: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/bea_SIP2.2/user_projects/domains/diameter/myserver/upload/axis2.war!/WEB-INF/modules/addressing- 1.1.mar: loading repository from classpath 14 dÚc. 2006 14:46:02 org.apache.axis2.deployment.DeploymentEngine loadFromClassPath INFO: Module validation failed Trying to engage a module which is not available : addressing <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> <14 dÚc. 2006 14 h 46 CET> -- Thanks, Slim -- Cordialement, Slim DRISS __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Unknown message label
Greetings All,
When running the code below I get the following error:
Unknown message label In
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
log.debug("Options set for ServiceClient...\n");
sender.addHeader(authorization);
OperationClient opClient = sender.createClient(ServiceClient.ANON_OUT_ONLY_OP);
MessageContext mc = new MessageContext();
mc.setServiceContext(opClient.getOperationContext().getServiceContext());
log.debug("Creating SOAPEnvelope...\n");
SOAPEnvelope envelope = factory.getDefaultEnvelope();
log.debug("Creating SOAPBody...\n");
SOAPBody body = envelope.getBody();
send.addChild(dataIdentifier);
send.addChild(xmlData);
body.addChild(send);
sender.addHeadersToEnvelope(envelope);
mc.setEnvelope(envelope);
opClient.addMessageContext(mc);
log.debug("Sending envelope...\n");
opClient.execute(true); // Blocking invocation
MessageContext resp =
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
--
Open WebMail Project (http://openwebmail.org)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
