RE: MTOM + WS-Security
Hello all, Can anyone point to a sample of how to use WS-security (Signature and Encryption with X509 certificates) using the Rampart 1.4/axis2 1.4.1 combination with MTOM. We have used WS-Security successfully in the past for web services dealing with only text data. However, with binary date using MTOM, we run in to the Signature verification failure error. Thanks Sriram From: Sriram Vaidyanathan [mailto:sriram.vaidyanat...@copart.com] Sent: Wednesday, January 14, 2009 10:38 AM To: axis-user@ws.apache.org Subject: MTOM + WS-Security Hello Axis Users, I am working on a project to receive attachments and we are using MTOM with Axis2 1.4.1 However, WS-Security does not seem to work if there are attachments in the request. Is this a known issue or if not, any help on this would be appreciated. Thanks Sriram
MTOM + WS-Security
Hello Axis Users, I am working on a project to receive attachments and we are using MTOM with Axis2 1.4.1 However, WS-Security does not seem to work if there are attachments in the request. Is this a known issue or if not, any help on this would be appreciated. Thanks Sriram
Threshold for File size in MTOM
Hello Axis Users, I am new to MTOM processing using Axis2. In MTOM, is there a way to specify the maximum attachment size on the server so that anything exceeding that size is rejected. Can this achieved by configuration or should I need to use a custom handler to enforce this limit. Any insight on this would be appreciated. Thanks Sriram
Upgrading from Axis2 1.1 to Axis2 1.4
Hello Axis2 team, I am working on upgrading the Axis2 version from 1.1 to 1.4 in our web service applications. We have been using the basic style of Rampart configuration using Inflow and Outflow parameters for WS-Security. After upgrading to Axis2 1.4 version, when we try to generate a message from our client (a web application running in a resin container) with WS -Security headers, we see the following exception being thrown. Caused by: java.lang.NullPointerException at com.caucho.xml.QAttributedNode.getAttributeNS(QAttributedNode.java:88) at org.apache.xml.security.algorithms.SignatureAlgorithm.getURI(Unknown Source) at org.apache.xml.security.algorithms.SignatureAlgorithm.init(Unknown Source) at org.apache.xml.security.signature.SignedInfo.init(Unknown Source) at org.apache.xml.security.signature.XMLSignature.init(Unknown Source) at org.apache.ws.security.message.WSSecSignature.prepare(WSSecSignature.jav a:341) at org.apache.ws.security.message.WSSecSignature.build(WSSecSignature.java: 721) at org.apache.ws.security.action.SignatureAction.execute(SignatureAction.ja va:54) at org.apache.ws.security.handler.WSHandler.doSenderAction(WSHandler.java:1 97) at org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java :201) at org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.ja va:64) The outflow security configuration is specified dynamically in the code as shown below. outflowConfig.setActionItems(Signature); outflowConfig.setPasswordCallbackClass(com.test.security.PasswordCallbac kHandler); outflowConfig.setSignaturePropFile(security.properties)); outflowConfig.setSignatureKeyIdentifier(DirectReference); outflowConfig.setUser(privatealias); Is there some required libraries that I have missed? Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan
Multiple versions of the same service
Hello Axis2 team, Congratulations on getting the Axis2 1.4 release out! I had a question related to versioning. Does the newly released Axis2 1.4 version support multiple versions of the same service? I had followed the JIRA at the link http://issues.apache.org/jira/browse/AXIS2-1810 but was not sure if this was fixed in the latest release. Thanks and Regards Sriram
Setting Timestamp expiry limit.
Hello, I am using WS- Security Policy style configuration for setting the WS-Security headers. Is there any way I can set the timestamp expiration limit in the policy file. Any help on this would be appreciated. Thanks in Advance Sriram smime.p7s Description: S/MIME cryptographic signature
RE: Configuration in Rampart 1.1
Hi Sanka, Could you please point me to an example as to how we can specify the security constraints as part of the WSDL? Thanks Sriram -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sunday, March 18, 2007 9:45 PM To: axis-user@ws.apache.org Cc: Sanka Samaranayake Subject: Re: Configuration in Rampart 1.1 Hi, Actually this is now possible by providing the WSDL. Therefore I don't think we need to change the axis2 client configuration. Maybe Sanka (Mr. Policy) can explain this a bit more. Thanks, Ruchith On 3/15/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Ruchith, Is there a patch version out yet for the problem to secure only Outgoing messages and not incoming messages by configuring the Client side policy.xml. Thanks Sriram Vaidyanathan -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 3:20 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Good question ! IMHO we don't have a way to do this right now... Will create a JIRA issue to fix it. Thanks, Ruchith On 2/5/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Ruchith, The message label works well for the service side where only the incoming messages are expected to be secured. Suppose if I want the client to only secure outgoing messages and not expect any security for incoming messages, is it possible to specify the message label defintion in the client's policy.xml? Thanks Sriram Vaidyanathan -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit y-utility-1.0.xsd xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit y-utility-1.0.xsd xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services
RE: Configuration in Rampart 1.1
Hi Ruchith, The message label works well for the service side where only the incoming messages are expected to be secured. Suppose if I want the client to only secure outgoing messages and not expect any security for incoming messages, is it possible to specify the message label defintion in the client's policy.xml? Thanks Sriram Vaidyanathan -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy 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; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings, we may have to create different Policy.xml files. After that according to the service the client is going to invoke you can load the relevant Policy file as follows. StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile); Policy clientPolicy = PolicyEngine.getPolicy(builder.getDocumentElement()); //setting the object Options options = new Options(); options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, clientPolicy); Schemas are available at, http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html Cheers, Dimuthu On 1/18/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically
RE: Configuration in Rampart 1.1
Hi Ruchith, When I try to give a message level policy for an operation like shown below:, I get an exception at server startup which says java.lang.UnsupportedOperationException: Not yet implemented . operation name=echo mep=http://www.w3.org/2004/08/wsdl/in-out; actionMappingurn:echo/actionMapping outputActionMappinghttp://ws.sample/echoResponse/outputActionMapping !-- Message Level Policy (Only for Incoming messages -- message label=in wsp:Policy wsu:Id=ServicePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation Any help on this would be appreciated. Thanks Sriram Vaidyanathan -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy 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; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings, we may have to create different Policy.xml files. After that according to the service the client is going to invoke you can load the relevant Policy file as follows. StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile); Policy clientPolicy = PolicyEngine.getPolicy
RE: Configuration in Rampart 1.1
Hi, Ignore the previous mail... The problem was because I gave the message label as in instead of In Thanks, Sriram Vaidyanathan -Original Message- From: Sriram Vaidyanathan Sent: Wednesday, January 31, 2007 11:00 PM To: 'axis-user@ws.apache.org' Subject: RE: Configuration in Rampart 1.1 Hi Ruchith, When I try to give a message level policy for an operation like shown below:, I get an exception at server startup which says java.lang.UnsupportedOperationException: Not yet implemented . operation name=echo mep=http://www.w3.org/2004/08/wsdl/in-out; actionMappingurn:echo/actionMapping outputActionMappinghttp://ws.sample/echoResponse/outputActionMapping !-- Message Level Policy (Only for Incoming messages -- message label=in wsp:Policy wsu:Id=ServicePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation Any help on this would be appreciated. Thanks Sriram Vaidyanathan -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy 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; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings
RE: Configuration in Rampart 1.1
Hi Ruchith, I have raised a JIRA for the problem: https://issues.apache.org/jira/browse/RAMPART-18 Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5428 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2007 8:51 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi, We need to do this. JIRA please :-) Thanks, Ruchith On 1/27/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Thanks Ruchith. Another question I had is, If I had defined custom fault to be thrown from an operation and those faults are currently not getting secured. Is there a way to secure the outgoing faults from the service with the same security policy used for securing outgoing messages.? Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5428 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy 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; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings, we may have to create different Policy.xml files. After that according to the service the client is going to invoke you can load the relevant Policy file as follows. StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile); Policy
RE: Configuration in Rampart 1.1
Thanks Ruchith. Another question I had is, If I had defined custom fault to be thrown from an operation and those faults are currently not getting secured. Is there a way to secure the outgoing faults from the service with the same security policy used for securing outgoing messages.? Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5428 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 6:34 PM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, This should be possible by specifying message level policies in the services.xml. Simply remove the EncryptedParts and SignedParts assertions from the service level policy and include those assertions at the message level. For example: service operation name=echo message label=in wsp:Policy wsu:Id=InputMessagePolicy 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; sp:SignedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:SignedParts sp:EncryptedParts xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; sp:Body/ /sp:EncryptedParts /wsp:Policy /message /operation wsp:Policy wsu:Id=ServicePolicy 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; . . . . /wsp:Policy /service Please make sure that you don't have a sp:OnlySignEntireHeadersAndBody/ assertion in the binding policy as well. Thanks, Ruchith On 1/25/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings, we may have to create different Policy.xml files. After that according to the service the client is going to invoke you can load the relevant Policy file as follows. StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile); Policy clientPolicy = PolicyEngine.getPolicy(builder.getDocumentElement()); //setting the object Options options = new Options(); options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, clientPolicy); Schemas are available at, http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html Cheers, Dimuthu On 1/18/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum
RE: Configuration in Rampart 1.1
Hello Ruchith /Dimuthu, Thanks for your responses!! I was just using the Policy sample03, which does both the Signature and the Encryption, and it works very well. My question is there a way for me to specify to the service to only expect Inflow messages to be secured and not secure Outflow messages like it was possible in the Rampart 1.0 configuration. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 2:56 AM To: axis-user@ws.apache.org Subject: Re: Configuration in Rampart 1.1 Hi Sriram, Note that you must use Rampart policy[1] in configuring rampart along with the standard WS-SecurityPolicy. The WS-SecPolicy stuff are not really straight forward. Therefore I believe we will be maintaining the rampart-1.0 configuration for a few more versions :-). However the rampart-1.0 configuration causes a few issues when we try to interop with other implementations. For example if the endpoint policy requires a signed Timestamp with strict header layout, the rampart-1.0 configuration fails to satisfy those requirements. Therefore the best option Thanks, Ruchith [1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd On 1/18/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote: Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf). Since your services require different security settings, we may have to create different Policy.xml files. After that according to the service the client is going to invoke you can load the relevant Policy file as follows. StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile); Policy clientPolicy = PolicyEngine.getPolicy(builder.getDocumentElement()); //setting the object Options options = new Options(); options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, clientPolicy); Schemas are available at, http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html Cheers, Dimuthu On 1/18/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Must Understand check failed error
Hi, I am getting the following error when I am using a Client to send a SOAP 1.2 standard message to a service which uses Axis2 1.1 and Rampart 1.1 ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header / soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USMust Understand check failed soapenv : MustUnderstand/soapenv:Text /soapenv:Reason soapenv:Detail /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope I know the mustUnderstand attribute has different values in SOAP 1.1 and SOAP 1.2. Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan -Original Message- From: Sriram Vaidyanathan Sent: Wednesday, January 17, 2007 5:07 PM To: 'axis-user@ws.apache.org' Subject: Configuration in Rampart 1.1 Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Must Understand check failed error
Hi, Pls ignore the below post.. It was a valid error caused by a silly mistake from my side... Thanks Sriram From: Sriram Vaidyanathan Sent: Mon 1/22/2007 10:05 PM To: 'axis-user@ws.apache.org' Subject: Must Understand check failed error Hi, I am getting the following error when I am using a Client to send a SOAP 1.2 standard message to a service which uses Axis2 1.1 and Rampart 1.1 ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header / soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USMust Understand check failed soapenv : MustUnderstand/soapenv:Text /soapenv:Reason soapenv:Detail /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope I know the mustUnderstand attribute has different values in SOAP 1.1 and SOAP 1.2. Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan -Original Message- From: Sriram Vaidyanathan Sent: Wednesday, January 17, 2007 5:07 PM To: 'axis-user@ws.apache.org' Subject: Configuration in Rampart 1.1 Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hi Paul, I have raised a JIRA for the issue (https://issues.apache.org/jira/browse/AXIS2-1993) Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 17, 2007 1:38 AM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you raise a JIRA? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Paul, I switched from Axis2 1.1.1 to Axis21.1 and tried to build with the xsd:include and it worked without any issues. So this seems to be a problem with Axis2 1.1.1. So should a JIRA be filed this in Axis2 1.1.1? Also, if I go ahead and upgrade to Axis2 1.1 instead of Axis2 1.1.1 for my project, are there any issues with 1.1 that I need to be aware of before making the upgrade. Appreciate your help so far. Thanks. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 10:11 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram You are right. I managed to recreate your problem. I think there is a bug in the XMLBeans databinding. Try using xsd:import instead of include: xsd:import schemaLocation=SampleService.xsd namespace=http://www.sample.com/test; / Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Thanks for the response. If I remove the SampleService.xsd from the folder, then I get the expection as you posted. See [1] below. But if I have the file present, then I get a different version of the same exception. See [2] below. So, I am wondering if I have the file present, is it hiding some other problem. ? [1] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\cieca\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:114) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema[2]): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.: java.io.FileNotFoundException: This file was not found: file:/C:/cvs/aps/sample/wsdl/src/main/config/SampleService.xsd [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:97) [2] [INFO] Executing tasks [echo] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\sample\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Jan 16, 2007 9:31:48 PM org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver resolveEntity [java] INFO: Resolving schema with publicId [null] and systemId [\SampleService.xsd] [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException
Configuration in Rampart 1.1
Hi, I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class. From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated. Thanks and Regards Sriram Vaidyanathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hello, I tried to migrate to axis2 1.1.1 with XMLBeans as the data-binding framework. My WSDL actually references XSDs in it through a relative path. When I run the WSDL2Java command I get a FileNotFoundException. This used to work before with one of the Axis2 1.0 nightly build versions I had earlier. This is the exception stacktrace: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82) [java] ... 3 more [java] Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \BMSDispositionService.xsd (The system cannot find the file specified) [java] at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242) [java] ... 8 more [java] Caused by: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \SampleService.xsd (The system cannot find the file specified) Any help on this would be appreciated... Thanks, Sriram
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hi Paul, Here is the snippet, which is used to include the XSD in the WSDL. xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://www.sample.com/test; version=2.1.0 xsd:include schemaLocation=SampleService.xsd / /xsd:schema Both the WSDL and the XSD are in the same folder. I am just posting the snippet, as the WSDL itself is pretty large. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 7:21 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you post the WSDL/XSD? Thanks Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello, I tried to migrate to axis2 1.1.1 with XMLBeans as the data-binding framework. My WSDL actually references XSDs in it through a relative path. When I run the WSDL2Java command I get a FileNotFoundException. This used to work before with one of the Axis2 1.0 nightly build versions I had earlier. This is the exception stacktrace: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82) [java] ... 3 more [java] Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \BMSDispositionService.xsd (The system cannot find the file specified) [java] at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242) [java] ... 8 more [java] Caused by: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \SampleService.xsd (The system cannot find the file specified) Any help on this would be appreciated... Thanks, Sriram -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hi Paul, Tried that option too... same error. Actually we were using one of the Axis2 1.0 nightly versions and it used to resolve the relative directory without a problem. Could there be a problem that I am only using the selected jars from Axis21.1.1 distribution. Thanks Sriram Vaidyanathan -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 8:13 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Can you try ./SampleService.xsd just in case that fixes it? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Here is the snippet, which is used to include the XSD in the WSDL. xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://www.sample.com/test; version=2.1.0 xsd:include schemaLocation=SampleService.xsd / /xsd:schema Both the WSDL and the XSD are in the same folder. I am just posting the snippet, as the WSDL itself is pretty large. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 7:21 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you post the WSDL/XSD? Thanks Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello, I tried to migrate to axis2 1.1.1 with XMLBeans as the data-binding framework. My WSDL actually references XSDs in it through a relative path. When I run the WSDL2Java command I get a FileNotFoundException. This used to work before with one of the Axis2 1.0 nightly build versions I had earlier. This is the exception stacktrace: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82) [java] ... 3 more [java] Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \BMSDispositionService.xsd (The system cannot find the file specified) [java] at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242) [java] ... 8 more [java] Caused by: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \SampleService.xsd (The system cannot find the file specified) Any help on this would be appreciated... Thanks, Sriram -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
No, I am using only 1.1.1 jars From 1.1.1 release since we have XmlBeans as the data-binding framework, I don't use the axis2-jibx1.1.1.jar and axis2-adb1.1.1.jar Thanks Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 8:24 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. I don't understand what you mean. Do you have a mix of 1.0 and 1.1.1 jars? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Tried that option too... same error. Actually we were using one of the Axis2 1.0 nightly versions and it used to resolve the relative directory without a problem. Could there be a problem that I am only using the selected jars from Axis21.1.1 distribution. Thanks Sriram Vaidyanathan -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 8:13 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Can you try ./SampleService.xsd just in case that fixes it? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Here is the snippet, which is used to include the XSD in the WSDL. xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://www.sample.com/test; version=2.1.0 xsd:include schemaLocation=SampleService.xsd / /xsd:schema Both the WSDL and the XSD are in the same folder. I am just posting the snippet, as the WSDL itself is pretty large. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 7:21 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you post the WSDL/XSD? Thanks Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello, I tried to migrate to axis2 1.1.1 with XMLBeans as the data-binding framework. My WSDL actually references XSDs in it through a relative path. When I run the WSDL2Java command I get a FileNotFoundException. This used to work before with one of the Axis2 1.0 nightly build versions I had earlier. This is the exception stacktrace: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82) [java] ... 3 more [java] Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \BMSDispositionService.xsd (The system cannot find the file specified) [java] at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242) [java] ... 8 more [java] Caused by: org.apache.xmlbeans.XmlException: error: Problem parsing referenced XML resource - java.io.FileNotFoundException: \SampleService.xsd (The system cannot find the file specified) Any help on this would be appreciated
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hi Paul, So it seems you got that same error which I am getting right?? Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 9:07 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram I just took an existing WSDL and added your snippet into it. Then I tried the Axis2-1.1.1 wsdl2java.bat I got this error: Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/wsdlexercise/'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 'file:/C:/wsdlexercise/'.: java.io.FileNotFoundException: This file was not found: file:/C:/wsdlexercise/SampleService.xsd In other words, exactly as it should, it looked in the same path as the WSDL file. So I can't replicate your problem. Paul On 1/17/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: No, I am using only 1.1.1 jars From 1.1.1 release since we have XmlBeans as the data-binding framework, I don't use the axis2-jibx1.1.1.jar and axis2-adb1.1.1.jar this should not cause any problem. Can you send a small sample wsdl and an xsd file to reproduce your problem? I tried with some sample but they pick the xsd file correctly. Thanks Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 8:24 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. I don't understand what you mean. Do you have a mix of 1.0 and 1.1.1 jars? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Tried that option too... same error. Actually we were using one of the Axis2 1.0 nightly versions and it used to resolve the relative directory without a problem. Could there be a problem that I am only using the selected jars from Axis21.1.1 distribution. Thanks Sriram Vaidyanathan -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] ] Sent: Tuesday, January 16, 2007 8:13 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Can you try ./SampleService.xsd just in case that fixes it? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Here is the snippet, which is used to include the XSD in the WSDL. xsd:schema xmlns:xsd= http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace= http://www.sample.com/test; version=2.1.0 xsd:include schemaLocation=SampleService.xsd / /xsd:schema Both the WSDL and the XSD are in the same folder. I am just posting the snippet, as the WSDL itself is pretty large. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto: [EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 7:21 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you post the WSDL/XSD? Thanks Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello, I tried to migrate to axis2 1.1.1 with XMLBeans as the data-binding framework. My WSDL actually references XSDs in it through a relative path. When I run the WSDL2Java command I get a FileNotFoundException. This used to work before with one of the Axis2 1.0 nightly build versions I had earlier. This is the exception stacktrace: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main (WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
(Method.java:585) [java] at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) [java] at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:160) [java] ... 8 more [java] Java Result: 1 Thanks Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 9:20 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. No! Exactly the opposite. I didn't have a SampleService.xsd but wsdl2java was looking in the right place for it. When I add a SampleService.xsd it finds it successfully. Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, So it seems you got that same error which I am getting right?? Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 9:07 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram I just took an existing WSDL and added your snippet into it. Then I tried the Axis2-1.1.1 wsdl2java.bat I got this error: Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/wsdlexercise/'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 'file:/C:/wsdlexercise/'.: java.io.FileNotFoundException: This file was not found: file:/C:/wsdlexercise/SampleService.xsd In other words, exactly as it should, it looked in the same path as the WSDL file. So I can't replicate your problem. Paul On 1/17/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: No, I am using only 1.1.1 jars From 1.1.1 release since we have XmlBeans as the data-binding framework, I don't use the axis2-jibx1.1.1.jar and axis2-adb1.1.1.jar this should not cause any problem. Can you send a small sample wsdl and an xsd file to reproduce your problem? I tried with some sample but they pick the xsd file correctly. Thanks Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 8:24 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. I don't understand what you mean. Do you have a mix of 1.0 and 1.1.1 jars? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Tried that option too... same error. Actually we were using one of the Axis2 1.0 nightly versions and it used to resolve the relative directory without a problem. Could there be a problem that I am only using the selected jars from Axis21.1.1 distribution. Thanks Sriram Vaidyanathan -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] ] Sent: Tuesday, January 16, 2007 8:13 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Can you try ./SampleService.xsd just in case that fixes it? Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Here is the snippet, which is used to include the XSD in the WSDL. xsd:schema xmlns:xsd= http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace= http://www.sample.com/test; version=2.1.0 xsd:include schemaLocation=SampleService.xsd / /xsd:schema Both the WSDL and the XSD are in the same folder. I am just posting the snippet, as the WSDL itself is pretty large. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto: [EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 7:21 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram Please can you
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Hi Paul, So, if the SampleService.xsd also references further xsds with the xsd:include statement, then they will also fail right ? Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 10:11 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram You are right. I managed to recreate your problem. I think there is a bug in the XMLBeans databinding. Try using xsd:import instead of include: xsd:import schemaLocation=SampleService.xsd namespace=http://www.sample.com/test; / Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Thanks for the response. If I remove the SampleService.xsd from the folder, then I get the expection as you posted. See [1] below. But if I have the file present, then I get a different version of the same exception. See [2] below. So, I am wondering if I have the file present, is it hiding some other problem. ? [1] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\cieca\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:114) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema[2]): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.: java.io.FileNotFoundException: This file was not found: file:/C:/cvs/aps/sample/wsdl/src/main/config/SampleService.xsd [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:97) [2] [INFO] Executing tasks [echo] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\sample\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Jan 16, 2007 9:31:48 PM org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver resolveEntity [java] INFO: Resolving schema with publicId [null] and systemId [\SampleService.xsd] [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82) [java] ... 3 more [java] Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: Problem parsing referenced
RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.
Paul, I switched from Axis2 1.1.1 to Axis21.1 and tried to build with the xsd:include and it worked without any issues. So this seems to be a problem with Axis2 1.1.1. So should a JIRA be filed this in Axis2 1.1.1? Also, if I go ahead and upgrade to Axis2 1.1 instead of Axis2 1.1.1 for my project, are there any issues with 1.1 that I need to be aware of before making the upgrade. Appreciate your help so far. Thanks. Thanks, Sriram Vaidyanathan Software Engineer - Java Copart Auto Auctions, Inc. 4665 Business Center Drive Fairfield, CA 94534 www.copart.com http://www.copart.com/ (707) 639-5248 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 10:11 PM To: axis-user@ws.apache.org Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework. Sriram You are right. I managed to recreate your problem. I think there is a bug in the XMLBeans databinding. Try using xsd:import instead of include: xsd:import schemaLocation=SampleService.xsd namespace=http://www.sample.com/test; / Paul On 1/17/07, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Paul, Thanks for the response. If I remove the SampleService.xsd from the folder, then I get the expection as you posted. See [1] below. But if I have the file present, then I get a different version of the same exception. See [2] below. So, I am wondering if I have the file present, is it hiding some other problem. ? [1] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\cieca\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:114) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema[2]): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.: java.io.FileNotFoundException: This file was not found: file:/C:/cvs/aps/sample/wsdl/src/main/config/SampleService.xsd [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:97) [2] [INFO] Executing tasks [echo] Running AXIS Tool WSDL2Java with Axis2 Home as C:\axis2-1.1.1 [delete] Deleting directory C:\cvs\aps\sample\wsdl\xmlbeans_gen_src [java] Retrieving schema at 'SampleService.xsd', relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'. [java] Jan 16, 2007 9:31:48 PM org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver resolveEntity [java] INFO: Resolving schema with publicId [null] and systemId [\SampleService.xsd] [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException [java] at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) [java] ... 2 more [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java
SSL Client Transport in Axis2
Hi all, How can i set up the client that wants to talk to a service through SSL transport. The certificate needs to be loaded in to a truststore. Does Axis2 provide a way to set this up.? Any help on this would be appreciated.. Thanks in Advance Sriram
RE: SocketTimeout exception occurs during Serviceclient.sendReceiveNonBlocking call
Yes, Thilina. Thanks that did the trick setting the timeout in options. Thanks Sriram -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 5:06 AM To: axis-user@ws.apache.org Subject: Re: SocketTimeout exception occurs during Serviceclient.sendReceiveNonBlocking call Hope you are using the sendRecieveNonBlocking without seperate listener.. Try increasing the time out value using the options.setTimeOutInMilliSeconds().. ~Thilina On 11/22/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I am experiencing SocketTimeout exceptions during the serviceclient.sendRecieveNonBlocking call. This doesn't happen everytime but intermittently. Is it related to some timeout value set at the server end ? Any help on this would be appreciated. The full exception Stacktrace: java.net.SocketTimeoutException: Read timed out; nested exception is: org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:228) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:819) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:351) at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:430) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:332) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:207) ... 6 more Thanks Sriram -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SocketTimeout exception occurs during Serviceclient.sendReceiveNonBlocking call
Hi, I am experiencing SocketTimeout exceptions during the serviceclient.sendRecieveNonBlocking call. This doesn't happen everytime but intermittently. Is it related to some timeout value set at the server end ? Any help on this would be appreciated. The full exception Stacktrace: java.net.SocketTimeoutException: Read timed out; nested exception is: org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:228) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:819) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:351) at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:430) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:332) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:207) ... 6 more Thanks Sriram
Rampart 1.1 nightly with Axis2 1.1
Hi Will the Rampart 1.1 SNAPSHOT be compatible on with the Axis21.1 release? Pls advice. Thanks Sriram
RE: Signature verification fails when used with Encryption
tns:EchoRequest wsu:Id=Id:2e589c1b-e9ba-440b-af85-9df73672e675 xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xenc:EncryptedData Id=EncryptedContent-585c6db0-cd8e-4ff1-b56a-a65c45c8af2e Type=http://www.w3.org/2001/04/xmlenc#Content; xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#aes128-cbc; / xenc:CipherData xenc:CipherValue2BPpey3b0xyHs+7gaO3w6d4cgYQwjdPQn1fq8/AkEPU=/xenc:CipherValue /xenc:CipherData /xenc:EncryptedData /tns:EchoRequest /soap:Body /soap:Envelope -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 4:48 AM To: axis-user@ws.apache.org Subject: Re: Signature verification fails when used with Encryption Hi, Looking at the msg you sent ... the signature seems to be referring to the cert using the subject key identifier. In this case you MUST have the service's cert in the client's keystore and your signaturePropertyFile has to point to that. Also since there are two timestamp headers ... your action items will have to be as : Timestamp Signature Encrypt Timestamp to be able to successfully process the message. Thanks, Ruchith On 11/10/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello, I am using a Web service-testing tool, which is based on .NET to talk to a Web service in Axis2 The web service implements WS-Security using Rampart. When I set the service side actions to Signature Timestamp or Encrypt Timestamp and have my .NET tool send a message with the corresponding security actions, I get a successful response. No problems there... But when I set the service side actions to Signature Encrypt Timestamp and then have the .NET tool to send a message with the same corresponding actions, I get a Signature verification failed message. rg.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; nested exception is: org.apache.ws.security.WSSecurityException: The signature verification failed Could it be possible that there is a bug in the .NET based testing tool which when using Encryption along with Signature is messing up the signed content. Also I see that the tool is adding two Timestamp Headers. Could that be an issue? Below is the request message from the .NET based testing tool that fails. Any help on this would be appreciated. Thanks Sriram ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://ws.test.com/test/; soap:Header wsse:Security soap:mustUnderstand=1 xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; wsu:Timestamp wsu:Id=Timestamp-cbc739c1-2813-4b07-8588-4b10b6193c85 xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Created2006-11-10T08:11:53Z/wsu:Created wsu:Expires2006-11-10T08:16:53Z/wsu:Expires /wsu:Timestamp wsse:BinarySecurityToken ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3; EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-f98f02e3-53cb-4e03-9f80-4685fa96ff4fMIIDgTCCAuqgAwIBAgIBAjANBgkqhkiG9w0BAQQFADCBlDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRIwEAYDVQQHEwlGYWlyZmllbGQxEzARBgNVBAoTCkNvcGFydCxJbmMxDDAKBgNVBAsTA01JUzESMBAGA1UEAxMJQ29wYXJ0IElUMS0wKwYJKoZIhvcNAQkBFh53ZWJzZXJ2aWNlc2phdmF0ZWFtQGNvcGFydC5jb20wHhcNMDYwOTI5MTU1MzQ2WhcNMDcwOTI5MTU1MzQ2WjBUMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExEzARBgNVBAoTCkNvcGFydCxJbmMxDDAKBgNVBAsTA01JUzEVMBMGA1UEAxMMQVBTIFByb2R1Y2VyMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDgoCNz31aHmXscbh3NACbtIbXmipQ4rF1s4X1fgMe4eSOlpuqa2L0P9IdfJQ7NzhDNqLpfUMlyDf0WFNplxKLTk4URWC1IaW3eOKIeJr5E8hJM5UlEqjkxstdMC5Mye/asfi5x+dV0oSLwBO5NLmz4kIJmsSo7w60gVusA5lIBeQIDAQABo4IBIDCCARwwCQYDVR0TBAIwADAsBglghkgBhvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFOvkxv6oyMF4GOjwtLgfTxFfgxHxMIHBBgNVHSMEgbkwgbaAFG/XrNLKNVaMoEImPQLiQ8T/r0GloYGapIGXMIGUMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExEjAQBgNVBAcTCUZhaXJmaWVsZDETMBEGA1UEChMKQ29wYXJ0LEluYzEMMAoGA1UECxMDTUlTMRIwEAYDVQQDEwlDb3BhcnQgSVQxLTArBgkqhkiG9w0BCQEWHndlYnNlcnZpY2VzamF2YXRlYW1AY29wYXJ0LmNvbYIBADANBgkqhkiG9w0BAQQFAAOBgQCh3nAvrbniJsIVh5YTCdLyjp06ycnKw+tATqP4DYDV9mzikZ4NTROfWNOfeFUxj0Osp/GxVo0l63hcw+enqlYi26ClHTUn5U3209Z4ssa0neVlcMxyX3POY/Xy0a4W+/mqaIN+VK2bJkgukWB6bVgM4YnIkJduYHM4myuejJ0FoQ==/wsse:BinarySecurityToken xenc:EncryptedKey xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#rsa
RE: Building WSDL using latest axis2 nightly
Hi Using the latest 1.0 axis2 nightly builds, I am getting the following error when the server starts up. org.apache.axis2.deployment.DeploymentException: The Dispatch phase is not found on the global InFlow phase of the axis2.xml file. Make sure the phase is within the axis2.xml file.: loading repository from classpath Could someone please help me with this? Thanks in Advance Sriram -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 8:12 PM To: axis-user@ws.apache.org Subject: Re: Building WSDL using latest axis2 nightly Please re-run wsdl2java (in the new dist) against your wsdl. Please don't use the old generated code. thanks, dims On 10/25/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I downloaded the latest nightly axis2-SNAPSHOT.jar and tried to compile my existing WSDL, but I get the following error when it tries to compile the generated stub class. Cannot find symbol: getElement (org.apache.axiom.soap.SOAPEnvelope,java.lang.String) The failure happens because the method. getElement(org.apache.axiom.soap.SOAPEnvelope,java.lang.String) is not found in the org.apache.axis2.client.Stub class. Am i missing a Jar file with the latest nightly snapshots because the axis21.0.jar from the stable release was not giving the problem? Any help on this would be appreciated. Thanks Sriram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building WSDL using latest axis2 nightly
Found the problem, just found out the axis2.xml has undergone changes with respect to the phase Names. Thanks Sriram -Original Message- From: Sriram Vaidyanathan Sent: Thursday, October 26, 2006 10:57 AM To: 'axis-user@ws.apache.org' Subject: RE: Building WSDL using latest axis2 nightly Hi Using the latest 1.0 axis2 nightly builds, I am getting the following error when the server starts up. org.apache.axis2.deployment.DeploymentException: The Dispatch phase is not found on the global InFlow phase of the axis2.xml file. Make sure the phase is within the axis2.xml file.: loading repository from classpath Could someone please help me with this? Thanks in Advance Sriram -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 8:12 PM To: axis-user@ws.apache.org Subject: Re: Building WSDL using latest axis2 nightly Please re-run wsdl2java (in the new dist) against your wsdl. Please don't use the old generated code. thanks, dims On 10/25/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I downloaded the latest nightly axis2-SNAPSHOT.jar and tried to compile my existing WSDL, but I get the following error when it tries to compile the generated stub class. Cannot find symbol: getElement (org.apache.axiom.soap.SOAPEnvelope,java.lang.String) The failure happens because the method. getElement(org.apache.axiom.soap.SOAPEnvelope,java.lang.String) is not found in the org.apache.axis2.client.Stub class. Am i missing a Jar file with the latest nightly snapshots because the axis21.0.jar from the stable release was not giving the problem? Any help on this would be appreciated. Thanks Sriram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SOAPMonitor mar file for latest Axis2 1.0 nighty
Hi, In the nightly build location, I am nit able to locate the latest SoapMonitor.mar file that is compatible with the latest axis2 1.0 nightly builds. Could someone please let me know where I can get the MAR file? Thanks in Advance. Sriram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SOAPMonitor mar file for latest Axis2 1.0 nighty
Thanks for the response. Could you pls give me the link for this? Sriram -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 5:03 PM To: axis-user@ws.apache.org Subject: Re: SOAPMonitor mar file for latest Axis2 1.0 nighty I just checked and you can find it in the expanded nightly 1.1 war under /WEB-INF/modules . Robert On 10/26/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, In the nightly build location, I am nit able to locate the latest SoapMonitor.mar file that is compatible with the latest axis2 1.0 nightly builds. Could someone please let me know where I can get the MAR file? Thanks in Advance. Sriram - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rampart module
Hi Ruchith, Thanks a lot for the response. That solved the issue. I have another question regarding using a single client to send secure messages to different services and each service expects the incoming message to be encrypted. But in my client's axis2.xml for the OutflowSecurity parameter the encryptionUser can specify the alias for any one of the service's public certificate. Is there any way this alias can be supplied dynamically based on a condition instead of having it hardcoded in the axis2.xml. Any insight on this would be appreciated. Thanks Sriram From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wed 10/18/2006 9:51 PM To: axis-user@ws.apache.org Subject: Re: Rampart module Hi Sriram, Seems like the body is encrypted twice! That's why you cannot find the the second DataReference (EncryptedContent-35c3b4c0-4192-48b3-ab5d-629c7abcc6e2) in the message - since its encrypted. Therefore please try changing the items in the inflow configuration to : itemsSignature Encrypt Encrypt Timestamp/items Thanks, Ruchith On 10/19/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Ruchith, Pasted below is the generated message from the .NET client with the extra encryptedKey element and on the server side, the axis2 xml is configured for InflowSecurity as itemsSignature Encrypt Timestamp/items Thanks Sriram ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/03/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Action wsu:Id=Id-392264f7-703f-4ac0-b84d-810f91fe8f86http://abc.testservice.com/echo/wsa:Action wsa:MessageID wsu:Id=Id-5d8a4918-a4f4-46d6-b275-66a3bba829c5uuid:a9d09b03-8924-4bdb-b29b-2a88d4c9d457/wsa:MessageID wsa:ReplyTo wsu:Id=Id-9579ae46-5658-4e12-9119-64e2d440e89e wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous/wsa:Address /wsa:ReplyTo wsa:To wsu:Id=Id-e0ea75ce-232b-45c7-a069-475e602b6f49https://abc.testservice.com/services/SampleService/wsa:To wsse:Security soap:mustUnderstand=1 wsu:Timestamp wsu:Id=Timestamp-3655fce3-efaa-4ee4-8143-2d9bb5b0ccb6 wsu:Created2006-10-18T13:36:56Z/wsu:Created wsu:Expires2006-10-18T13:41:56Z/wsu:Expires /wsu:Timestamp wsse:BinarySecurityToken ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3; EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-d51b1d39-71ff-46d8-9e13-64bd8b3ff398MIIBujCCAWigAwIBAgIQ8RrjeUJb0JNNW53UzT9SWzAJBgUrDgMCHQUAMBYxFDASBgNVBAMTC1Jvb3QgQWdlbmN5MB4XDTA2MTAwMjE1NDcxNVoXDTM5MTIzMTIzNTk1OVowHTEbMBkGA1UEAxMSQ0RUVGVzdENlcnRpZmljYXRlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAUVXoOkoffCVPxzmGLGaPtLT8vF3h+Im8gbByZu/CBZWjPmqHRk62NsBr5923NtsMJR52fuMgaYbivSk9xxJfd4Q0OD35Y1sqx/veUOPW0N1kTdB5r51KadOU05C4/B3hBOJYq/FEpPwMYLEgZbUH2tDKbo8Qj+ntJmkD9yYQJQIDAQABo0swSTBHBgNVHQEEQDA+gBAS5AktBh0dTwCNYSHcFmRjoRgwFjEUMBIGA1UEAxMLUm9vdCBBZ2VuY3mCEAY3bACqAGSKEc+41KpcNfQwCQYFKw4DAh0FAANBADuVU60NZd3oX90ZJNasST6EsvNKpKLE7WtjXIS/QpxgLA3xwuTUQViGSZ5rKw7Z3TNy3LDxA4K8TY/Kh7fo9Xg=/wsse:BinarySecurityToken xenc:EncryptedKey xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-1_5; / KeyInfo xmlns=http://www.w3.org/2000/09/xmldsig#; wsse:SecurityTokenReference wsse:KeyIdentifier ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier; EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary;6+TG/qjIwXgY6PC0uB9PEV+DEfE=/wsse:KeyIdentifier /wsse:SecurityTokenReference /KeyInfo xenc:CipherData xenc:CipherValueNQ5JNFqRvllJ00dhS9pQ1Ux+n+on1dwSayYMFZ7JK9whQYC8ZXiiw3IwXXdrGYRtyuKqvdoPn1rZyBh+KWMguISsTz2SclRhsBmg2UpBuzUKabedVxdY2nU6wsI55i2JX0qLZhGURdVYZ0B/hKsQMWunYGjncEcJGuO1GAyFFFI=/xenc:CipherValue /xenc:CipherData xenc:ReferenceList xenc:DataReference URI=#EncryptedContent-8b343733-6984-4b42-9b35-83bb20fa5f0f / /xenc:ReferenceList /xenc:EncryptedKey xenc:EncryptedKey xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-1_5; / KeyInfo
RE: Rampart module
Hi Thanks for the response. Where can I download the axis2-security-SNAPSHOT.jar for using the OutflowConfiguration and InflowConfiguration classes? The nightly downloads site from people.apache.org is not available. ? Please let me know. Thanks Sriram -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 5:23 AM To: axis-user@ws.apache.org Subject: Re: Rampart module Hi Sriram, We cannot specify service specific parameters in the axis2.xml file. Therefore we have an alternative way to configure the clients when talking to multiple services. You can use two helper classes to generate the parameters dynamically and set them in the options object of the client before invoking the service. Please have a look at sample11 of this [1] presentation. Thanks, Ruchith [1] http://www.wso2.net/presentations/rampart/java/2006/08/04/secure-ws On 10/25/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Ruchith, Thanks a lot for the response. That solved the issue. I have another question regarding using a single client to send secure messages to different services and each service expects the incoming message to be encrypted. But in my client's axis2.xml for the OutflowSecurity parameter the encryptionUser can specify the alias for any one of the service's public certificate. Is there any way this alias can be supplied dynamically based on a condition instead of having it hardcoded in the axis2.xml. Any insight on this would be appreciated. Thanks Sriram From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wed 10/18/2006 9:51 PM To: axis-user@ws.apache.org Subject: Re: Rampart module Hi Sriram, Seems like the body is encrypted twice! That's why you cannot find the the second DataReference (EncryptedContent-35c3b4c0-4192-48b3-ab5d-629c7abcc6e2) in the message - since its encrypted. Therefore please try changing the items in the inflow configuration to : itemsSignature Encrypt Encrypt Timestamp/items Thanks, Ruchith On 10/19/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi Ruchith, Pasted below is the generated message from the .NET client with the extra encryptedKey element and on the server side, the axis2 xml is configured for InflowSecurity as itemsSignature Encrypt Timestamp/items Thanks Sriram ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/03/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Action wsu:Id=Id-392264f7-703f-4ac0-b84d-810f91fe8f86http://abc.testservice.com/echo/wsa:Action wsa:MessageID wsu:Id=Id-5d8a4918-a4f4-46d6-b275-66a3bba829c5uuid:a9d09b03-8924-4bdb-b29b-2a88d4c9d457/wsa:MessageID wsa:ReplyTo wsu:Id=Id-9579ae46-5658-4e12-9119-64e2d440e89e wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous/wsa:Address /wsa:ReplyTo wsa:To wsu:Id=Id-e0ea75ce-232b-45c7-a069-475e602b6f49https://abc.testservice.com/services/SampleService/wsa:To wsse:Security soap:mustUnderstand=1 wsu:Timestamp wsu:Id=Timestamp-3655fce3-efaa-4ee4-8143-2d9bb5b0ccb6 wsu:Created2006-10-18T13:36:56Z/wsu:Created wsu:Expires2006-10-18T13:41:56Z/wsu:Expires /wsu:Timestamp wsse:BinarySecurityToken ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3; EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-d51b1d39-71ff-46d8-9e13-64bd8b3ff398MIIBujCCAWigAwIBAgIQ8RrjeUJb0JNNW53UzT9SWzAJBgUrDgMCHQUAMBYxFDASBgNVBAMTC1Jvb3QgQWdlbmN5MB4XDTA2MTAwMjE1NDcxNVoXDTM5MTIzMTIzNTk1OVowHTEbMBkGA1UEAxMSQ0RUVGVzdENlcnRpZmljYXRlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAUVXoOkoffCVPxzmGLGaPtLT8vF3h+Im8gbByZu/CBZWjPmqHRk62NsBr5923NtsMJR52fuMgaYbivSk9xxJfd4Q0OD35Y1sqx/veUOPW0N1kTdB5r51KadOU05C4/B3hBOJYq/FEpPwMYLEgZbUH2tDKbo8Qj+ntJmkD9yYQJQIDAQABo0swSTBHBgNVHQEEQDA+gBAS5AktBh0dTwCNYSHcFmRjoRgwFjEUMBIGA1UEAxMLUm9vdCBBZ2VuY3mCEAY3bACqAGSKEc+41KpcNfQwCQYFKw4DAh0FAANBADuVU60NZd3oX90ZJNasST6EsvNKpKLE7WtjXIS/QpxgLA3xwuTUQViGSZ5rKw7Z3TNy3LDxA4K8TY/Kh7fo9Xg=/wsse:BinarySecurityToken xenc:EncryptedKey xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-1_5; / KeyInfo xmlns=http://www.w3.org/2000/09/xmldsig
Building WSDL using latest axis2 nightly
Hi, I downloaded the latest nightly axis2-SNAPSHOT.jar and tried to compile my existing WSDL, but I get the following error when it tries to compile the generated stub class. Cannot find symbol: getElement (org.apache.axiom.soap.SOAPEnvelope,java.lang.String) The failure happens because the method. getElement(org.apache.axiom.soap.SOAPEnvelope,java.lang.String) is not found in the org.apache.axis2.client.Stub class. Am i missing a Jar file with the latest nightly snapshots because the axis21.0.jar from the stable release was not giving the problem? Any help on this would be appreciated. Thanks Sriram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building WSDL using latest axis2 nightly
Thanks that solved the issue... Now I am getting a javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found error. Is this because I am missing a newer version of a stax utils jar file. Thanks Sriram -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 8:12 PM To: axis-user@ws.apache.org Subject: Re: Building WSDL using latest axis2 nightly Please re-run wsdl2java (in the new dist) against your wsdl. Please don't use the old generated code. thanks, dims On 10/25/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, I downloaded the latest nightly axis2-SNAPSHOT.jar and tried to compile my existing WSDL, but I get the following error when it tries to compile the generated stub class. Cannot find symbol: getElement (org.apache.axiom.soap.SOAPEnvelope,java.lang.String) The failure happens because the method. getElement(org.apache.axiom.soap.SOAPEnvelope,java.lang.String) is not found in the org.apache.axis2.client.Stub class. Am i missing a Jar file with the latest nightly snapshots because the axis21.0.jar from the stable release was not giving the problem? Any help on this would be appreciated. Thanks Sriram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rampart module
Thanks for the response, Ruchith. I had a question with the WSDoAllReceiver. There is a check for matching the Actions in the right order, which throws a WSDoAllReceiver: security processing failed (actions mismatch)) in case the actions don't match with the actual results and the configured actions. We are having a .NET client trying to send the message but it always fails for the actions mismatch check. On looking at it they have an extra xenc:encryptedKey element, which is having a referenceData URI, but the URI doesn't match to any particular element in the document. We have the Server axis2.xml configured as itemsSignature Encrypt Timestamp/items Could the extra encrypted element in the request be causing this Actions Mismatch error. Any help on this would be appreciated. Thanks Sriram -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:47 AM To: axis-user@ws.apache.org Subject: Re: Rampart module Hi Sriram, On 10/18/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hi, Where can I get the source files for the Rampart Module? Trunk: https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/security 1.1 Branch: https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/security Also, any idea when will the Rampart 1.1 version coming out? I think we can release rampart a week or two after the Axis2 1.1 release. Thanks, Ruchith Thanks Sriram -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Monday, October 16, 2006 10:45 PM To: axis-user@ws.apache.org Subject: Re: Rampart module Please try this : http://people.apache.org/repository/org.apache.axis2/mars/rampart-1.1-SNAPSHOT.mar Thanks, Ruchith On 10/17/06, Marcel Casado [EMAIL PROTECTED] wrote: Hi, Where I can find a snapshot of the Rampart module that works fine with an snapshot of Axis2 1.1 ? Thanks, -Marcel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rampart module
=#Id-392264f7-703f-4ac0-b84d-810f91fe8f86 Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValueXPsgAkRid9zqbvBCCcRAtfuDdvc=/DigestValue /Reference Reference URI=#Id-5d8a4918-a4f4-46d6-b275-66a3bba829c5 Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValue4oqh/ZBIeqGO8aZBizjab2nA1Do=/DigestValue /Reference Reference URI=#Id-9579ae46-5658-4e12-9119-64e2d440e89e Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValueHAK41b2OHRKQ32hMS/jf0Mz0Gp4=/DigestValue /Reference Reference URI=#Id-e0ea75ce-232b-45c7-a069-475e602b6f49 Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValuecwCmR+Yko4zoBey8wOVizE6zPTw=/DigestValue /Reference Reference URI=#Timestamp-3655fce3-efaa-4ee4-8143-2d9bb5b0ccb6 Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValueveIjhp8Ubw/V2Sa6kdArohMD6nw=/DigestValue /Reference Reference URI=#Id-89cc079d-6dea-406e-ad20-5b7c7a925767 Transforms Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; / /Transforms DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; / DigestValuejeT3j5JGalurE0pODG0gS1qmeCw=/DigestValue /Reference /SignedInfo SignatureValuevGgQHG8/MvSsM8xXaahSyGZ408ji8LfbX7yfxcnJ40c7CDCDYwoj75ZmZD7T7u1Igzmn7CmM7rzFCcb+MM34bj7HVChMTAuw8bluKEHksTzJItqwSYxWmPb2QHyuGaea8ahy3CFmr+FNCujZ/kfEZQ98CmtXmj9idtMvTzJkBbQ=/SignatureValue KeyInfo wsse:SecurityTokenReference wsse:Reference URI=#SecurityToken-d51b1d39-71ff-46d8-9e13-64bd8b3ff398 ValueType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3; / /wsse:SecurityTokenReference /KeyInfo /Signature /wsse:Security /soap:Header soap:Body wsu:Id=Id-89cc079d-6dea-406e-ad20-5b7c7a925767 xenc:EncryptedData Id=EncryptedContent-8b343733-6984-4b42-9b35-83bb20fa5f0f Type=http://www.w3.org/2001/04/xmlenc#Content; xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xenc:EncryptionMethod Algorithm=http://www.w3.org/2001/04/xmlenc#aes128-cbc; / xenc:CipherData xenc:CipherValue/tc/143BkwW4h6qmKy4bi+iLMEYI8xe5XdIy83kwDlSZZpFgA9RePh9c0Z+whSlZ3nQ7j3FPnODKA9eknQh02BHZwcmp2GcdghfnB8HNGm7rnKSJmXUkG6C5FzPWqI84lhYToQTJh/rpmbwMzav1uBqVvPWzeUaYRFnGTvNlEkddDuOfOXaX+VY7BahU/ExCXANlk1LY9nGrm+j5dda7uQjbKNTzsULFXvqgyKLU4S4Zq9zcy2bFHqTXavJotQnafIRQheSRzHdk2FkhJOYYAzAdStLfYS4Tzx4x2L2w8ZrqnkdHgLn8I0Hq05XGHI2c5GxOt5CqXkuCQ93ZlR1DLY+5nnnVaWIk75vjePIrw8kmXgpcy2/bI7AYnZxWJpSpzXXGvOiznvcF7iQubgi674j0PPrA7cbGlY+fS4pAIUaRAM00wMyjPQcs6jPJrjvV5Ndj+6siCl9Ptj6BPpCmPHxS+wW0zXeVGpPn1u9nquvQXsTEhldknsc7p/gIOSf8wQmlPJAjOvAe+4lUHnGBkq6mF7A+9uqbt2xCuzbMMEKg9pRCVCtM2GVdhGNSSsKLmuPpdnTzAdKlcHPHaIx659kcAKKcq0XTXDZInOJK7ggkwwPQKSeLajwkVIbCs8UTOuUErI39t2m79T3Wvy5JTC+6ptCSbSM1J7dsV2IKrN5NmoyWSsIzbKC4RSOGEL/P/xenc:CipherValue /xenc:CipherData /xenc:EncryptedData /soap:Body /soap:Envelope -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 6:57 PM To: axis-user@ws.apache.org Subject: Re: Rampart module Hi Sriram, Yes, the extra EncryptedKey with a RefList (meaning there's content that is encrypted with that key) can be causing the action mismatch. Can you please post the message generated by the .NET client? Thanks, Ruchith On 10/18/06, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Thanks for the response, Ruchith. I had a question with the WSDoAllReceiver. There is a check for matching the Actions in the right order, which throws a WSDoAllReceiver: security processing failed (actions mismatch)) in case the actions don't match with the actual results and the configured actions. We are having a .NET client trying to send the message but it always fails for the actions mismatch check. On looking at it they have an extra xenc:encryptedKey element, which is having a referenceData URI, but the URI doesn't match to any
RE: Rampart module
Hi, Where can I get the source files for the Rampart Module? Also, any idea when will the Rampart 1.1 version coming out? Thanks Sriram -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Monday, October 16, 2006 10:45 PM To: axis-user@ws.apache.org Subject: Re: Rampart module Please try this : http://people.apache.org/repository/org.apache.axis2/mars/rampart-1.1-SNAPSHOT.mar Thanks, Ruchith On 10/17/06, Marcel Casado [EMAIL PROTECTED] wrote: Hi, Where I can find a snapshot of the Rampart module that works fine with an snapshot of Axis2 1.1 ? Thanks, -Marcel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.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]
