Re: Unable to make secure conversation using AXIS2 1.4
Hi Amitesh, In this post [1], Prabath, WSO2's security guru explains a scenario where he shows SecCon with a STS. Hope that is the scenario you are looking for. thanks, Nandana [1] - http://blog.facilelogin.com/2008/10/secure-conversation-with-sts.html On Fri, Jul 10, 2009 at 4:00 AM, amiteshksingh amiteshksi...@live.comwrote: Hi Nandana, Thanks for reply. Yes, I looked into the sample 04, but it doesn't uses the STS for getting SCT. Sample 06 uses the WS-Trust with MEX but it doesn't uses the SecConv. My requirement is using both sample. How can I build the client and service policy so that it will use all the three Spec. (Trust, MEX and SecConv)? I want to use as much as possible, the policy files to meet the requirement. I would appreciate if you can provide a sample policy file. Thanks, Amitesh Nunny wrote: 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 -- View this message in context: http://www.nabble.com/Unable-to-make-secure-conversation-using-AXIS2-1.4-tp24281945p24418920.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: Use Axis1 and Axis2 inside the same JBoss/Tomcat
I did exactly the same and have no issues. Some of my services had no return in axis1 and I couldn't make it work in axis2 so I changed them to resturn status. From: Nora Serinek [mailto:nseri...@berlin-sws.de] Sent: Wednesday, July 08, 2009 10:28 AM To: axis-user@ws.apache.org Subject: Use Axis1 and Axis2 inside the same JBoss/Tomcat Hi, We'd like to migrate from Axis 1.4 to Axis2. We'd like to migrate not all our web services at once so I wonder if it is possible to use Axis1 and Axis2 simultaneously within the same JVM. Thank you for your help Nora ### This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the system manager.
Re: WSDL gen error
Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace wsdl:definitions targetNamespace=http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types schema targetNamespace=http://xml.apache.org/xml-soap; ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
