Looking for a WSDL parser tool
Hi, I am looking out for a WSDL / XML parser tool, which will parse a wsdl file The parser should be able to achieve : 1) Remotely open the wsdl file (If I provide a http link) 2) Fetch the details of service name, port type, binding name, operation name,input and output parameter names, input and output parameter types, handle all kinds of bindings and operation styles. I am using the tool called WSDL2C, but this tool doesnt generate the parameter names and parameter types. Is anybody aware of a tool in C or Perl for that matter which will help me do the parsing ? There are tools in Java and PHP ... wonder why somebody didnt come up with a tool in C. Ramesh. Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/
AUTO: Manohar K Chintala/India/IBM is out of the office. (returning 09/07/2009)
I am out of the office until 09/07/2009. I will be on leave starting today till 8th July. During my vacation, my manager Sats will be the spoc for all projects I am handling. Note: This is an automated response to your message Looking for a WSDL parser tool sent on 7/7/09 15:13:47. This is the only notification you will receive while this person is away.
How do I deploy Axis2 on an Existing Application server running on RESIN?
Hi guys, I really need your help very badly. I have an existing application running on Resin server and I want to deploy Axis2 on the Resin Server. What I did was to drop the axis2.war on the webapps folder inside resin (resin/webapps). My problem is that when I started our application, I got the below error: [15:40:05.843] WebApp[http://localhost:90/axis] starting [15:40:07.859] WebApp[http://localhost:90/axis2] starting *[15:40:19.609] com.caucho.config.ConfigException: java.io http://java.io.Fi.FileNotFoundException:\\usr\local\resin\lib\resin.jar (The network path was not found)* [15:40:19.609] at com.caucho.config.TypeStrategyFactory.init(TypeStrategyFactory.java:162) When I removed axis2.war, I was able to successfully start our application so I am certain that it's axis2.war that is causing this problem. From the given logs above, \\usr\local\resin\lib\resin.jar is really an invalid directory because it should be \usr\local\resin\lib\resin.jar.Does anybody knows how to resolve this problem? This issue is bugging for days already. Thanks in advance for your help. -Claire
Re: How do I deploy Axis2 on an Existing Application server running on RESIN?
Probebly you have some problem with path. check the \usr\local\resin\lib\, if it exists or not. and find where you have installed the resin somewhere.. From: Claire Loto l...@taosolutions.biz To: axis-user@ws.apache.org Sent: Tuesday, July 7, 2009 10:40:12 AM Subject: How do I deploy Axis2 on an Existing Application server running on RESIN? Hi guys, I really need your help very badly. I have an existing application running on Resin server and I want to deploy Axis2 on the Resin Server. What I did was to drop the axis2.war on the webapps folder inside resin (resin/webapps). My problem is that when I started our application, I got the below error: [15:40:05.843] WebApp[http://localhost:90/axis] starting [15:40:07.859] WebApp[http://localhost:90/axis2] starting [15:40:19.609] com.caucho.config.ConfigException: java.io.FileNotFoundException:\\usr\local\resin\lib\resin.jar (The network path was not found) [15:40:19.609] at com.caucho.config.TypeStrategyFactory.init(TypeStrategyFactory.java:162) When I removed axis2.war, I was able to successfully start our application so I am certain that it's axis2.war that is causing this problem. From the given logs above, \\usr\local\resin\lib\resin.jar is really an invalid directory because it should be \usr\local\resin\lib\resin.jar.Does anybody knows how to resolve this problem? This issue is bugging for days already. Thanks in advance for your help. -Claire
Re: How do I deploy Axis2 on an Existing Application server running on RESIN?
Hi Lars, Thanks for the response on this. Really appreciate it. By the way, I have the directory *\usr\local\resin\lib\ *however, based from the below logs, resin (or axis2) is looking for \*\usr\local\resin\lib\ *which is a network directory. Also, my resin is installed in the root directory (c:\resin). I was wondering, which particular file or jar does resin look up to when deploying axis2? thanks, Claire Lars Ericsson wrote: Probebly you have some problem with path. check the \usr\local\resin\lib\, if it exists or not. and find where you have installed the resin somewhere.. *From:* Claire Loto l...@taosolutions.biz *To:* axis-user@ws.apache.org *Sent:* Tuesday, July 7, 2009 10:40:12 AM *Subject:* How do I deploy Axis2 on an Existing Application server running on RESIN? Hi guys, I really need your help very badly. I have an existing application running on Resin server and I want to deploy Axis2 on the Resin Server. What I did was to drop the axis2.war on the webapps folder inside resin (resin/webapps). My problem is that when I started our application, I got the below error: [15:40:05.843] WebApp[http://localhost:90/axis] starting [15:40:07.859] WebApp[http://localhost:90/axis2] starting *[15:40:19.609] com.caucho.config.ConfigException: java.io http://java.io.Fi.FileNotFoundException:\\usr\local\resin\lib\resin.jar (The network path was not found)* [15:40:19.609] at com.caucho.config.TypeStrategyFactory.init(TypeStrategyFactory.java:162) When I removed axis2.war, I was able to successfully start our application so I am certain that it's axis2.war that is causing this problem. From the given logs above, \\usr\local\resin\lib\resin.jar is really an invalid directory because it should be \usr\local\resin\lib\resin.jar.Does anybody knows how to resolve this problem? This issue is bugging for days already. Thanks in advance for your help. -Claire
[AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it
Hello,
I have a problem when I try to validate an input parameter with an
AnyType member
I use Xmlbeans and I get this error on the server side (I made a sample
program to show the problem)
2009-07-06 16:23:16,109 [HttpConnection-8080-1] WARN
Server - Invalid object demo.dryade.soap.impl.RequestDocumentImpl
error: cvc-elt.4.2: Invalid xsi:type qname: 'typ:SpecificType' in
element RequestPart
2009-07-06 16:23:16,125 [HttpConnection-8080-1] WARN
Server - Invalid content =
soap:Request xmlns:soap=http://soap.dryade.demo;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
RequestPart
typ:element6 xmlns:typ=http://types.dryade.demo;1/typ:element6
typ:element7 xmlns:typ=http://types.dryade.demo;test/typ:element7
typ:element8 xsi:type=typ:SpecificType
xmlns:typ=http://types.dryade.demo;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
typ:element4true/typ:element4
typ:element5any test/typ:element5
/typ:element8
/RequestPart
/soap:Request
if the server produce an output with the same AnyType , it validate
correctly :
in an input-output transaction
2009-07-06 16:23:16,125 [HttpConnection-8080-1] INFO Server - Valid object
demo.dryade.soap.impl.RequestResponseDocumentImpl
in an ouput-only transaction
2009-07-06 16:23:16,250 [HttpConnection-8080-2] INFO Server - Valid object
demo.dryade.soap.impl.NotifyDocumentImpl
on the client side, the structures are always valid.
I send you the entire code I used for this exemple; it is made with
AXIS2 1.4.1 on Windows XP platform with Java 1.6
(I can send the entire project archive if necessary)
Thanks for help
Best regards
Michel Etienne
Server source :
package demo.server;
import org.apache.log4j.Logger;
import java.util.ArrayList;
import javax.xml.namespace.QName;
import org.apache.xmlbeans.SchemaType;
import org.apache.xmlbeans.XmlBeans;
import org.apache.xmlbeans.XmlObject;
import org.apache.xmlbeans.XmlOptions;
import org.apache.xmlbeans.XmlValidationError;
import org.apache.xmlbeans.impl.common.QNameHelper;
import demo.dryade.soap.DemoServicesSkeletonInterface;
import demo.dryade.soap.NotifyDocument;
import demo.dryade.soap.RequestDocument;
import demo.dryade.soap.RequestResponseDocument;
import demo.dryade.soap.RequestResponseDocument.RequestResponse;
import demo.dryade.types.ComplexType1;
import demo.dryade.types.SpecificType;
public class Server implements DemoServicesSkeletonInterface
{
/**
* Logger for this class
*/
private static final Logger logger = Logger.getLogger(Server.class);
public static boolean checkXmlSchema(XmlObject object)
{
if (object == null)
{
logger.warn(validation null object);
return false;
}
ArrayListXmlValidationError validationErrors = new
ArrayListXmlValidationError();
XmlOptions validationOptions = new XmlOptions();
validationOptions.setErrorListener(validationErrors);
boolean validation = object.validate(validationOptions);
if (!validation)
{
StringBuffer errorTxt = new StringBuffer( Invalid object
+object.getClass().getName());
for (XmlValidationError error : validationErrors)
{
errorTxt.append(\n );
errorTxt.append(error.toString());
}
logger.warn(errorTxt);
logger.warn(Invalid content = \n+object.toString());
}
else
{
logger.info( Valid object +object.getClass().getName());
}
return validation;
}
@Override
public RequestResponseDocument Request(RequestDocument request)
{
checkXmlSchema(request);
RequestResponseDocument response =
RequestResponseDocument.Factory.newInstance();
RequestResponse reqResponse = response.addNewRequestResponse();
ComplexType1 part = reqResponse.addNewResponsePart();
part.addElement1(12);
part.setElement2(test);
SpecificType elt3 = SpecificType.Factory.newInstance();
elt3.setElement4(true);
elt3.setElement5(any test);
part.setElement3(elt3);
checkXmlSchema(response);
return response;
}
@Override
public void Notify(NotifyDocument notify)
{
checkXmlSchema(notify);
}
}
Client Source :
package demo.client;
import java.math.BigInteger;
import java.util.ArrayList;
import org.apache.log4j.Logger;
import org.apache.xmlbeans.XmlObject;
import org.apache.xmlbeans.XmlOptions;
import org.apache.xmlbeans.XmlValidationError;
import demo.dryade.soap.DemoServices;
import demo.dryade.soap.DemoServicesStub;
import demo.dryade.soap.NotifyDocument;
import demo.dryade.soap.RequestDocument;
import demo.dryade.soap.RequestResponseDocument;
import demo.dryade.soap.NotifyDocument.Notify;
import demo.dryade.soap.RequestDocument.Request;
import demo.dryade.types.ComplexType1;
import demo.dryade.types.ComplexType2;
import demo.dryade.types.SpecificType;
/**
* @author michel
*
*/
public class Client
{
/**
* Logger for this class
*/
private static final Logger logger = Logger.getLogger(Client.class);
public static boolean checkXmlSchema(XmlObject object)
{
if (object == null)
{
logger.warn(validation null object);
return false;
}
ArrayListXmlValidationError validationErrors = new
Re: How do I deploy Axis2 on an Existing Application server running on RESIN?
Hi Claire! i havn't worked with resin and Axis before. but can you define the resin_home_directory Check if you have define RESIN_HOME in your system-variable I belive axis2 will read the resin_home_directory, and it cannot find it and try use resin_home_directory as default..., it is somehting i can guess... From: Claire Loto l...@taosolutions.biz To: axis-user@ws.apache.org Sent: Tuesday, July 7, 2009 11:02:19 AM Subject: Re: How do I deploy Axis2 on an Existing Application server running on RESIN? Hi Lars, Thanks for the response on this. Really appreciate it. By the way, I have the directory \usr\local\resin\lib\ however, based from the below logs, resin (or axis2) is looking for \\usr\local\resin\lib\ which is a network directory. Also, my resin is installed in the root directory (c:\resin). I was wondering, which particular file or jar does resin look up to when deploying axis2? thanks, Claire Lars Ericsson wrote: Probebly you have some problem with path. check the \usr\local\resin\lib\, if it exists or not. and find where you have installed the resin somewhere.. From: Claire Loto l...@taosolutions.biz To: axis-user@ws.apache.org Sent: Tuesday, July 7, 2009 10:40:12 AM Subject: How do I deploy Axis2 on an Existing Application server running on RESIN? Hi guys, I really need your help very badly. I have an existing application running on Resin server and I want to deploy Axis2 on the Resin Server. What I did was to drop the axis2.war on the webapps folder inside resin (resin/webapps). My problem is that when I started our application, I got the below error: [15:40:05.843] WebApp[http://localhost:90/axis] starting [15:40:07.859] WebApp[http://localhost:90/axis2] starting [15:40:19.609] com.caucho.config.ConfigException: java.io.FileNotFoundException:\\usr\local\resin\lib\resin.jar (The network path was not found) [15:40:19.609] at com.caucho.config.TypeStrategyFactory.init(TypeStrategyFactory.java:162) When I removed axis2.war, I was able to successfully start our application so I am certain that it's axis2.war that is causing this problem. From the given logs above, \\usr\local\resin\lib\resin.jar is really an invalid directory because it should be \usr\local\resin\lib\resin.jar.Does anybody knows how to resolve this problem? This issue is bugging for days already. Thanks in advance for your help. -Claire
Error in axis 2 in WAS 5
How to resolve following error? [7/7/09 2:33:14:573 PDT] 31e948d7 WebGroup E SRVE0026E: [Servlet Error]-[/axis2-web/listSingleService.jsp]: javax.servlet.ServletException: /axis2-web/listSingleService.jsp at com.netegrity.was511.filter.ServletFilter.doFilter(ServletFilter.java:75) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstance Wrapper.java:132) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain. java:71) at com.cisco.tools.filter.AccessLogFilter.doFilter(AccessLogFilter.java:114) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstance Wrapper.java:132) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain. java:71) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch( WebAppRequestDispatcher.java:1027) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques tDispatcher.java:544) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest Dispatcher.java:210) at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:139) at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker java:332) at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(C achedInvocation.java:71) at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq uestProcessor.java:254) at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene r.java:334) at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav a:56) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:657) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:453) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:937)
Axis2, new client from new wsdl = bad xml queries
Hello (sorry for my bad english). I have actually a problem I am not able to solve. I had a client for a webservices, and everithing was ok. The webservice has changed a little, so I have generated e new client from the new wsdl (almost the same, just some more attributes in the response structures ) And now, I have an error. I think the problem comes from the server, but I am not sure, so if ou can give me some informations about this problem The better method to explain you the problem is certainly to show you the request/response with the old and the new client. The old: QUERY: ?xml version='1.0' encoding='UTF-8' ? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body Login xmlns=url/Query Username.../Username Password.../Password /Login /soapenv:Body /soapenv:Envelope RESPONSE: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body SessionID xmlns=url/Query.../SessionID /soapenv:Body /soapenv:Envelope THE NEW QUERY: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body quer:Login xmlns:quer=url/Query quer=url/Query quer:Username.../quer:Username quer:Password.../quer:Password /quer:Login /soapenv:Body /soapenv:Envelope RESPONSE: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body SessionID xmlns=url.../SessionID /soapenv:Body /soapenv:Envelope As you can see, the request is a little bit different, but it is the same thing. And the problem comes from the response: In the response with the new client, the sessionId element contains xmlns=url. But with the old client, it was xmlns=url/Query = Ant that was ok So finally, Axis compares the namesapece url/Query with the namespace of the answer url and returns me an error explining that the namespaces are not the sames The namespaces in the wsdls are the sames... Any help is welcome ;), Thanks in advance. -- View this message in context: http://www.nabble.com/Axis2%2C-new-client-from-new-wsdl-%3D%3E-bad-xml-queries-tp24371938p24371938.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Axis2, new client from new wsdl = bad xml queries
do you use the wsdl2java to make new java-files, for client? or how do you work? if you use wsdl2java, did you generate the whole java files... or not, if not, you should run wsdl2java and get the new java files. and everything should work as before. From: rageice rage...@rastamail.com To: axis-user@ws.apache.org Sent: Tuesday, July 7, 2009 1:54:16 PM Subject: Axis2, new client from new wsdl = bad xml queries Hello (sorry for my bad english). I have actually a problem I am not able to solve. I had a client for a webservices, and everithing was ok. The webservice has changed a little, so I have generated e new client from the new wsdl (almost the same, just some more attributes in the response structures ) And now, I have an error. I think the problem comes from the server, but I am not sure, so if ou can give me some informations about this problem The better method to explain you the problem is certainly to show you the request/response with the old and the new client. The old: QUERY: ?xml version='1.0' encoding='UTF-8' ? soapenv:Body Login xmlns=url/Query Username.../Username Password.../Password /Login /soapenv:Body /soapenv:Envelope RESPONSE: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body SessionID xmlns=url/Query.../SessionID /soapenv:Body /soapenv:Envelope THE NEW QUERY: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body quer:Login xmlns:quer=url/Query quer=url/Query quer:Username.../quer:Username quer:Password.../quer:Password /quer:Login /soapenv:Body /soapenv:Envelope RESPONSE: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header/ soapenv:Body SessionID xmlns=url.../SessionID /soapenv:Body /soapenv:Envelope As you can see, the request is a little bit different, but it is the same thing. And the problem comes from the response: In the response with the new client, the sessionId element contains xmlns=url. But with the old client, it was xmlns=url/Query = Ant that was ok So finally, Axis compares the namesapece url/Query with the namespace of the answer url and returns me an error explining that the namespaces are not the sames The namespaces in the wsdls are the sames... Any help is welcome ;), Thanks in advance. -- View this message in context: http://www.nabble.com/Axis2%2C-new-client-from-new-wsdl-%3D%3E-bad-xml-queries-tp24371938p24371938.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2 1.5 WSDL2Java errors
I'm getting all of these errors running WSDL2Java from the 1.5 bin. -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24373563.html Sent from the Axis - User mailing list archive at Nabble.com.
java.net.SocketException: Software caused connection abort: recv failed
Hi,
I get this error intermittently even when making calls to a webservice
available locally on my machine. I googled this but could not get any
conclusive answers.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Software caused connection abort: recv
failed
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Software
caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1373)
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.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:196)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
{http://xml.apache.org/axis/}hostname:mustang
java.net.SocketException: Software caused connection abort: recv failed
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:301)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
Caused by: java.net.SocketException: Software caused connection abort: recv
failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1373)
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.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:196)
... 12 more
Thanks!
Prashant
Re: AXIS2 - Security Policy Problem (Is this a bug?)
Hi Amitesh, Axis2/Rampart doesn't support policy alternatives, which is the feature you are referring to. When multiple policy alternatives present, it will only honor the first alternative. That is why your experiencing this behavior. One work around would be to have multiple bindings with these alternative policies and clients can choose which binding to talk to. thanks, Nandana On Mon, Jul 6, 2009 at 9:53 PM, amiteshksingh amiteshksi...@live.comwrote: Is anyone done this before? It seems bug to me, however I am not sure becaue I am new to AXIS2. amiteshksingh wrote: Hi, I have one Service which contains two separate policy for two different clients using the sp:ExactlyOne policy operator as given below Service Policy: wsp:Policy wsu:Id=SgnOnlyAnonymous xmlns:wsu= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsa= http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:sp= http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; wsp:ExactlyOne wsp:All wsp:ExactlyOne sp:AsymmetricBinding xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; wsp:Policy sp:InitiatorToken wsp:Policy sp:X509Token sp:IncludeToken= http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient wsp:Policy sp:RequireThumbprintReference/ sp:WssX509V3Token10/ /wsp:Policy /sp:X509Token /wsp:Policy /sp:InitiatorToken sp:RecipientToken wsp:Policy sp:X509Token sp:IncludeToken= http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never; wsp:Policy sp:RequireThumbprintReference/ sp:WssX509V3Token10/ /wsp:Policy /sp:X509Token /wsp:Policy /sp:RecipientToken sp:AlgorithmSuite wsp:Policy sp:TripleDesRsa15/ /wsp:Policy /sp:AlgorithmSuite sp:Layout wsp:Policy sp:Strict/ /wsp:Policy /sp:Layout sp:IncludeTimestamp/ sp:OnlySignEntireHeadersAndBody/ /wsp:Policy /sp:AsymmetricBinding sp:TransportBinding xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; wsp:Policy sp:TransportToken wsp:Policy !-- sp:HttpsToken RequireClientCertificate=false/ -- /wsp:Policy /sp:TransportToken sp:AlgorithmSuite wsp:Policy sp:Basic256/ /wsp:Policy /sp:AlgorithmSuite sp:Layout wsp:Policy sp:Lax/ /wsp:Policy /sp:Layout sp:IncludeTimestamp/ /wsp:Policy /sp:TransportBinding /wsp:ExactlyOne ramp:RampartConfig xmlns:ramp= http://ws.apache.org/rampart/policy; ramp:userservice/ramp:user ramp:encryptionUserclient/ramp:encryptionUser ramp:passwordCallbackClasscom.accenture.apsp.security.PWCBHandler/ramp:passwordCallbackClass ramp:signatureCrypto ramp:crypto provider=org.apache.ws.security.components.crypto.Merlin ramp:property name=org.apache.ws.security.crypto.merlin.keystore.typeJKS/ramp:property ramp:property
Re: Axis2 1.4 with Rampart 1.4
Hi Shilpa, It is an issue in SSL handshake. Can you set the system property javax.net.debug=ssl,handshake,record and attach the debug log. regards, Nandana On Mon, Jul 6, 2009 at 5:55 PM, shilpa.raghaven...@wipro.com wrote: Hi , I need to implement WS security so planning to use Rampart 1.4 with Axis2. i tried with example that i got through Google but getting the error, the stack trace as follows log4j:WARN No appenders could be found for logger (org.apache.axis2.deployment.FileSystemConfigurator). log4j:WARN Please initialize the log4j system properly. Exception in thread main org.apache.axis2.AxisFault: Remote host closed connection during handshake at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at tutorial.rampart.client.SecureServiceStub.add(SecureServiceStub.java:193) at tutorial.rampart.client.SecureServiceCGClient.main(SecureServiceCGClient.java:36) Caused by: com.ctc.wstx.exc.WstxIOException: Remote host closed connection during handshake at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:146) at org.apache.axiom.om.impl.dom.NodeImpl.serializeAndConsume(NodeImpl.java:817) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79) ... 19 more Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:742) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:622) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.FilterOutputStream.flush(FilterOutputStream.java:123) at org.apache.commons.httpclient.ChunkedOutputStream.flush(ChunkedOutputStream.java:191) at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99) at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214) at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311) ... 22 more Caused by: java.io.EOFException: SSL peer shut down incorrectly at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) ... 32 more some one share me the tutorial that tells us implementing Rampart 1.4 with Axis2 1.4 Thanks Regards, Shilpa * Please do not print this email unless it is absolutely necessary. * The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for
Re: Setting Username/password Programaticly
Hi Marcus, You are using the deprecated configuration of Apache Rampart. Apache Rampart recommends policy based configuration. The latter option only works with policy based configuration. If you have the option of moving in to policy based configuration, following tutorials might help you. Web Services Security with Apache Rampart - Part 1 (Transport Level Security) http://wso2.org/library/3190 Understanding WS - Security Policy Language http://wso2.org/library/3132 thanks, Nandana On Mon, Jul 6, 2009 at 7:29 PM, m4rkuz m4r...@gmail.com wrote: Hi Everyone, I'm trying to set username/password dynamically on my ws app I've googled a lot and find some workarounds but the only one that has worked for me contains deprecated code, and used a password call back handler that really mess with what i want to do, this is the code: * **OutflowConfiguration outflowConfig = new OutflowConfiguration();* * * * **outflowConfig.setActionItems(UsernameToken);* * * * **outflowConfig.setUser(username);* * * * **outflowConfig* * **.setPasswordCallbackClass(com.xxx.xxx.security.PWCBHandler);* * * * **outflowConfig.setPasswordType(PasswordText);* * * * ** _serviceClient.getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY, ** **outflowConfig.getProperty());* This works like a charm but I have to search for the username/password in base of some parameters I won't have available in the PWDCBHandler class, so what I'm looking for is a way to set the password directly w/o using a password call back handler. About this I've found some code that claims to do so: * **_serviceClient.getOptions().setUserName(15374159);* * ** * * ** _serviceClient.getOptions().setPassword(admin123);* but it''s not working for me... Any Ideas? I would really appreciate your input, Thanks in advance, ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. SCDJWS on going... -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Wrong response when authentication fails with Rampart (not SOAP but HTML)
Hi Giuseppe,
Are you using Axis2 1.4.1 and Rampart 1.3 ? Can you try with
Rampart 1.4 ?
regards,
Nandana
On Fri, Jul 3, 2009 at 4:51 PM, Giuseppe Gortan superbe...@gmail.comwrote:
Hi everybody.
I have a problem with axis2 (1.4.1) and rampart (1.3).
I put a simple policy in services.xml [1] and I wrote a
PasswordHandler [2]. Everything works fine if user and password are
correct. When the user doesn't exist (getUser returns
UserNotFoundException), the authentication process (correctly) fails,
but returning a HTML error page [5] instead of a SOAP response
message. The servlet engine logs an error message coming from the Axis
Servlet [4], and the SOAP client, that uses a library generated by
WSDL2Java, logs the error First Element must contain the local name,
Envelope , but found html [3].
I want to return to the client a custom SOAP error message if
authentication process fails. How can I do it?
Thanks,
Giuseppe
[1] Policy
parameter name=InflowSecurity
action
itemsUsernameToken/items
passwordCallbackClass
mypackage.myapp.PasswordHandler
/passwordCallbackClass
/action
/parameter
[2] PasswordHandler
public class PasswordHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int i = 0; i callbacks.length; i++) {
if (callbacks[i] instanceof WSPasswordCallback) {
try{
WSPasswordCallback pwcb =
(WSPasswordCallback) callbacks[i];
String username =
pwcb.getIdentifer();
String user = getUser(username);
String password =
getPlainPassword(user);
int passwordType = pwcb.getUsage();
if (passwordType ==
WSPasswordCallback.USERNAME_TOKEN) {
pwcb.setPassword(password);
} else {
throw new
UnsupportedCallbackException(callbacks[i],
Unrecognized Callback);
}
} catch (UserNotFoundException e){
throw new AxisFault(No user found,
e.getCause());
}
}
}
}
[3] First Element must contain the local name, Envelope , but found html
org.apache.axis2.AxisFault: First Element must contain the local name,
Envelope , but found html
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
mypackage.myapp.WebservicesStub.myRemoteWS(WebservicesStub.java:6642)
at mypackage.myapp.client.Client.main(Client.java:63)
Caused by: org.apache.axiom.soap.SOAPProcessingException: First
Element must contain the local name, Envelope , but found html
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105)
at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
... 6 more
[4] Error log
GRAVE: Servlet.service() for servlet AxisServlet threw exception
java.lang.NullPointerException
at
org.apache.rampart.RampartMessageData.init(RampartMessageData.java:308)
at
Re: Unable to make secure conversation using AXIS2 1.4
Hi Amitesh, Did you look at the Rampart policy sample 04 ? Which demonstrates the secure conversation features. regards, Nandana [1] - http://ws.apache.org/rampart/samples.html On Wed, Jul 1, 2009 at 9:15 PM, amiteshksingh amiteshksi...@live.comwrote: Please help me out by providing any working sample. I have seen lot of messages in this forum but I am not able to set the policy for provider. amiteshksingh wrote: Hi, I am new in AXIS2. I have run all the axis2 samples successfully. Now I am trying to run below use case, 1) Client sends a RST using WS- Policy and WS-MEX to STS (security token service) for SCT(security context token). 2) STS issues SCT with RSTR 3) Client uses the same SCT and start secure conversation with provider. I am trying to use STS issued SCT to start secure conversation with provider. I am not getting any sample for above use case. Any help would be highly appreciated. Thanks, Amitesh -- View this message in context: http://www.nabble.com/Unable-to-make-secure-conversation-using-AXIS2-1.4-tp24281945p24292113.html Sent from the Axis - User mailing list archive at Nabble.com. -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Wrong response when authentication fails with Rampart (not SOAP but HTML)
Hi Nandana,
I confirm the problem also with rampart 1.4
Regards
Giuseppe
On Tue, Jul 7, 2009 at 6:58 PM, Nandana
Mihindukulasooriyanandana@gmail.com wrote:
Hi Giuseppe,
Are you using Axis2 1.4.1 and Rampart 1.3 ? Can you try with
Rampart 1.4 ?
regards,
Nandana
On Fri, Jul 3, 2009 at 4:51 PM, Giuseppe Gortan superbe...@gmail.com
wrote:
Hi everybody.
I have a problem with axis2 (1.4.1) and rampart (1.3).
I put a simple policy in services.xml [1] and I wrote a
PasswordHandler [2]. Everything works fine if user and password are
correct. When the user doesn't exist (getUser returns
UserNotFoundException), the authentication process (correctly) fails,
but returning a HTML error page [5] instead of a SOAP response
message. The servlet engine logs an error message coming from the Axis
Servlet [4], and the SOAP client, that uses a library generated by
WSDL2Java, logs the error First Element must contain the local name,
Envelope , but found html [3].
I want to return to the client a custom SOAP error message if
authentication process fails. How can I do it?
Thanks,
Giuseppe
[1] Policy
parameter name=InflowSecurity
action
itemsUsernameToken/items
passwordCallbackClass
mypackage.myapp.PasswordHandler
/passwordCallbackClass
/action
/parameter
[2] PasswordHandler
public class PasswordHandler implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int i = 0; i callbacks.length; i++) {
if (callbacks[i] instanceof WSPasswordCallback) {
try{
WSPasswordCallback pwcb =
(WSPasswordCallback) callbacks[i];
String username =
pwcb.getIdentifer();
String user = getUser(username);
String password =
getPlainPassword(user);
int passwordType = pwcb.getUsage();
if (passwordType ==
WSPasswordCallback.USERNAME_TOKEN) {
pwcb.setPassword(password);
} else {
throw new
UnsupportedCallbackException(callbacks[i],
Unrecognized Callback);
}
} catch (UserNotFoundException e){
throw new AxisFault(No user found,
e.getCause());
}
}
}
}
[3] First Element must contain the local name, Envelope , but found html
org.apache.axis2.AxisFault: First Element must contain the local name,
Envelope , but found html
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
mypackage.myapp.WebservicesStub.myRemoteWS(WebservicesStub.java:6642)
at mypackage.myapp.client.Client.main(Client.java:63)
Caused by: org.apache.axiom.soap.SOAPProcessingException: First
Element must contain the local name, Envelope , but found html
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:251)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105)
at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
... 6 more
[4] Error log
GRAVE: Servlet.service() for servlet AxisServlet threw
Re: Setting Username/password Programaticly
Hi Nandana, I can't help to ask if there is a way to dynamically set the user and password w/o having a password call back handler... is there any? Thanks for your your valuable input. ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Tue, Jul 7, 2009 at 11:56 AM, Nandana Mihindukulasooriya nandana@gmail.com wrote: Hi Marcus, You are using the deprecated configuration of Apache Rampart. Apache Rampart recommends policy based configuration. The latter option only works with policy based configuration. If you have the option of moving in to policy based configuration, following tutorials might help you. Web Services Security with Apache Rampart - Part 1 (Transport Level Security) http://wso2.org/library/3190 Understanding WS - Security Policy Language http://wso2.org/library/3132 thanks, Nandana On Mon, Jul 6, 2009 at 7:29 PM, m4rkuz m4r...@gmail.com wrote: Hi Everyone, I'm trying to set username/password dynamically on my ws app I've googled a lot and find some workarounds but the only one that has worked for me contains deprecated code, and used a password call back handler that really mess with what i want to do, this is the code: * **OutflowConfiguration outflowConfig = new OutflowConfiguration();* * * * **outflowConfig.setActionItems(UsernameToken);* * * * **outflowConfig.setUser(username);* * * * **outflowConfig* * **.setPasswordCallbackClass(com.xxx.xxx.security.PWCBHandler);* * * * **outflowConfig.setPasswordType(PasswordText);* * * * ** _serviceClient.getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY, ** **outflowConfig.getProperty());* This works like a charm but I have to search for the username/password in base of some parameters I won't have available in the PWDCBHandler class, so what I'm looking for is a way to set the password directly w/o using a password call back handler. About this I've found some code that claims to do so: * **_serviceClient.getOptions().setUserName(15374159);* * ** * * ** _serviceClient.getOptions().setPassword(admin123);* but it''s not working for me... Any Ideas? I would really appreciate your input, Thanks in advance, ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. SCDJWS on going... -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Setting Username/password Programaticly
Hi Nandana, Don't mind my last message, reading carefully I've found everything I need in the example you provide.. Thanks again. ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Tue, Jul 7, 2009 at 1:10 PM, m4rkuz m4r...@gmail.com wrote: Hi Nandana, I can't help to ask if there is a way to dynamically set the user and password w/o having a password call back handler... is there any? Thanks for your your valuable input. ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Tue, Jul 7, 2009 at 11:56 AM, Nandana Mihindukulasooriya nandana@gmail.com wrote: Hi Marcus, You are using the deprecated configuration of Apache Rampart. Apache Rampart recommends policy based configuration. The latter option only works with policy based configuration. If you have the option of moving in to policy based configuration, following tutorials might help you. Web Services Security with Apache Rampart - Part 1 (Transport Level Security) http://wso2.org/library/3190 Understanding WS - Security Policy Languagehttp://wso2.org/library/3132 thanks, Nandana On Mon, Jul 6, 2009 at 7:29 PM, m4rkuz m4r...@gmail.com wrote: Hi Everyone, I'm trying to set username/password dynamically on my ws app I've googled a lot and find some workarounds but the only one that has worked for me contains deprecated code, and used a password call back handler that really mess with what i want to do, this is the code: * **OutflowConfiguration outflowConfig = new OutflowConfiguration();* * * * **outflowConfig.setActionItems(UsernameToken);* * * * **outflowConfig.setUser(username);* * * * **outflowConfig* * **.setPasswordCallbackClass(com.xxx.xxx.security.PWCBHandler);* * * * **outflowConfig.setPasswordType(PasswordText);* * * * ** _serviceClient.getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY, ** **outflowConfig.getProperty());* This works like a charm but I have to search for the username/password in base of some parameters I won't have available in the PWDCBHandler class, so what I'm looking for is a way to set the password directly w/o using a password call back handler. About this I've found some code that claims to do so: * **_serviceClient.getOptions().setUserName(15374159);* * ** * * ** _serviceClient.getOptions().setPassword(admin123);* but it''s not working for me... Any Ideas? I would really appreciate your input, Thanks in advance, ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. SCDJWS on going... -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
RE: Axis2 1.5 WSDL2Java errors
My portType tag will now work but only if I leave the default one in as well -- wsdl:portType name=NewWSDLFile wsdl:operation name=NewOperation wsdl:input message=tns:NewOperationRequest / wsdl:output message=tns:NewOperationResponse / /wsdl:operation /wsdl:portType It does give me the error again though when I put in the wsdl:port tag under wsdl:service. Does anyone see anything wrong with this? -- View this message in context: http://www.nabble.com/Axis2-1.5-WSDL2Java-errors-tp24295840p24380646.html Sent from the Axis - User mailing list archive at Nabble.com.
[Axis2] OppenOffice Webservice
Hi, I was wondering if someone had already implemented a web service client with Java macro from OpenOffice ? Thanks by advance
RE: Setting Username/password Programaticly
// Rampart module should be in the repository //acquire ConfigurationContext ConfigurationContext ctx = ConfigurationContextFactory.createConfigurationContextFromFileSystem(path/to/client, null); //acquire a stub to the deployed Service on secure port 8443 SecureServiceStub stub = new SecureServiceStub(ctx,https://localhost:8443/axis2/services/SecureService;); //acquire the client ServiceClient sc = stub._getServiceClient(); //engageModule sc.engageModule(rampart); Options options = sc.getOptions(); options.setUserName(apache); options.setPassword(password); sc.setOptions(options); //fill the Payload with the actual request OMElement response = sc.sendReceive(getPayload(Hello world)); *Saludos Cordiales desde EEUU* Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 7 Jul 2009 14:13:26 -0500 Subject: Re: Setting Username/password Programaticly From: m4r...@gmail.com To: axis-user@ws.apache.org Hi Nandana, Don't mind my last message, reading carefully I've found everything I need in the example you provide.. Thanks again. ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Tue, Jul 7, 2009 at 1:10 PM, m4rkuz m4r...@gmail.com wrote: Hi Nandana, I can't help to ask if there is a way to dynamically set the user and password w/o having a password call back handler... is there any? Thanks for your your valuable input. ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. On Tue, Jul 7, 2009 at 11:56 AM, Nandana Mihindukulasooriya nandana@gmail.com wrote: Hi Marcus, You are using the deprecated configuration of Apache Rampart. Apache Rampart recommends policy based configuration. The latter option only works with policy based configuration. If you have the option of moving in to policy based configuration, following tutorials might help you. Web Services Security with Apache Rampart - Part 1 (Transport Level Security) Understanding WS - Security Policy Language thanks, Nandana On Mon, Jul 6, 2009 at 7:29 PM, m4rkuz m4r...@gmail.com wrote: Hi Everyone, I'm trying to set username/password dynamically on my ws app I've googled a lot and find some workarounds but the only one that has worked for me contains deprecated code, and used a password call back handler that really mess with what i want to do, this is the code: OutflowConfiguration outflowConfig = new OutflowConfiguration(); outflowConfig.setActionItems(UsernameToken); outflowConfig.setUser(username); outflowConfig .setPasswordCallbackClass(com.xxx.xxx.security.PWCBHandler); outflowConfig.setPasswordType(PasswordText); _serviceClient.getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY, outflowConfig.getProperty()); This works like a charm but I have to search for the username/password in base of some parameters I won't have available in the PWDCBHandler class, so what I'm looking for is a way to set the password directly w/o using a password call back handler. About this I've found some code that claims to do so: _serviceClient.getOptions().setUserName(15374159); _serviceClient.getOptions().setPassword(admin123); but it''s not working for me... Any Ideas? I would really appreciate your input, Thanks in advance, ___ Marcus Sánchez Díaz. Enterprise Developer. SCJP - SCWCD. SCDJWS on going... -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org _ Hotmail® has ever-growing storage! Don’t worry about storage limits.
FW: [axis-2:file upload]
Hi All, Can any one please tell me how to send file as attachment (description is given below) in SOAP request using C# (.Net) client to apache axis2 java web service? Thanks Regards, Rajneesh Kumar _ From: Rajneesh Kumar [mailto:rajneesh.ku...@otssolutions.com] Sent: Thursday, July 02, 2009 12:33 PM To: axis-user@ws.apache.org Subject: [axis-2:file upload] HI All, My client application (developed in c# .Net) will have to read file (doc/pdf/tiff) from local drive and send the file data to axis-2 (running on a java based server somewhere else) as SOAP attachment, then the web method will create file with that data and store it on the server. Now I want to know how to accomplish this. I mean how my .Net client app will send that attachment and axis-2 web service will be able to process the file. Please provide some help. Thanx in Advance. -Rajneesh === Private, Confidential and Privileged. This e-mail and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this e-mail and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify OTS Solutions at i...@otssolutions.com === === Private, Confidential and Privileged. This e-mail and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this e-mail and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify OTS Solutions at i...@otssolutions.com === === Private, Confidential and Privileged. This e-mail and any files and attachments transmitted with it are confidential and/or privileged. They are intended solely for the use of the intended recipient. The content of this e-mail and any file or attachment transmitted with it may have been changed or altered without the consent of the author. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, circulation or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited and may be unlawful. If you have received this e-mail or any file or attachment transmitted with it in error please notify OTS Solutions at i...@otssolutions.com ===
how to retrieve rampart username/password from within a JAX-WS service?
All, On the Client Side: I am using JAX-WS Client + Axis Transport. On the Server Side: I am using JAX-WS webservice + Axis Transport. For WS-Security I am using Rampart on the client and the server side. I have a requirement that...once I authenticate the user...on the server I need to retrieve the username and the password from within the @WebService class for further processing. Is there a way I can achieve this from within JAX-WS service wrapped around by Axis2? Any configuration in Axis where I set this to happen? Any message context instance that I get is probably related to JAX-WS right?...since I am completely using JAX-WS web service implementations. I am confused...any help would really be appreciated! Thanks Preetham
