Re: SAML with Axis2
I can't see the assertion in the header of the message. Could it be because
this information is encryptied?
The soap message is the following:
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/xmlns:xenc
=http://www.w3.org/2001/04/xmlenc#;
soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing;
wsse:Security xmlns:wsse=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
soapenv:mustUnderstand=1
wsu:Timestamp xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
wsu:Id=Timestamp-18655235
wsu:Created2008-02-11T08:29:14.629Z/wsu:Created
wsu:Expires2008-02-11T08:34:14.629Z/wsu:Expires
/wsu:Timestamp
xenc:EncryptedKey Id=EncKeyId-9949215
xenc:EncryptionMethod Algorithm=
http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p/
ds:KeyInfo xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
wsse:SecurityTokenReference
wsse:KeyIdentifier EncodingType=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary
ValueType=
http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1
HYL371NzoOs2+IA24VDkBGcUFQM=/wsse:KeyIdentifier
/wsse:SecurityTokenReference
/ds:KeyInfo
xenc:CipherData
xenc:CipherValue
NS8hopFGnXC0p1Wma5EppZyhltrqoG/Xc6awAEYNoP8ZG7OCIbss4n9EbiKvE/Cc7qoJaJF7hbjp0fpTASStbb4/mABDSw6ZhYmS5VOgZpKnSyiX1DVeyWpXZkJmw2pFfZwXwlV0Z7zL05+TtY+fA/ofPBlUCnrBJFYOaeUYMlA=
/xenc:CipherValue
/xenc:CipherData
/xenc:EncryptedKey
xenc:ReferenceList/
ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#; Id=
Signature-18871350
ds:SignedInfo
ds:CanonicalizationMethod Algorithm=
http://www.w3.org/2001/10/xml-exc-c14n#/
ds:SignatureMethod Algorithm=http://www.w3.org/2000/09/xmldsig#hmac-sha1
/
ds:Reference URI=#Id-14721926
ds:Transforms
ds:Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#/
/ds:Transforms
ds:DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1/
ds:DigestValuekTTbXVwC6Hqhw+aPoSClk+I1MQ8=/ds:DigestValue
/ds:Reference
ds:Reference URI=#Timestamp-18655235
ds:Transforms
ds:Transform Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#/
/ds:Transforms
ds:DigestMethod Algorithm=http://www.w3.org/2000/09/xmldsig#sha1/
ds:DigestValueQL1srEXsHEJxBVvISWC6qqC135Q=/ds:DigestValue
/ds:Reference
/ds:SignedInfo
ds:SignatureValuePl4+PwCkehIyXTKWaruQTsS7gGE=/ds:SignatureValue
ds:KeyInfo Id=KeyId-14301726
wsse:SecurityTokenReference xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
wsu:Id=STRId-18725445
wsse:Reference URI=#EncKeyId-9949215 ValueType=
http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-soap-message-security-1.1#EncryptedKey
/
/wsse:SecurityTokenReference
/ds:KeyInfo
/ds:Signature
/wsse:Security
wsa:Tohttp://localhost:8081/axis2/services/sample05?wsdl/wsa:To
wsa:MessageIDurn:uuid:7CD0DAE693C1E94AFF1202718554608/wsa:MessageID
wsa:Actionurn:echo/wsa:Action
/soapenv:Header
soapenv:Body xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
wsu:Id=Id-14721926
ns1:echo xmlns:ns1=http://sample05.policy.samples.rampart.apache.org;
param0Hello world1/param0
/ns1:echo
/soapenv:Body
/soapenv:Envelope
2008/2/12, Nandana Mihindukulasooriya [EMAIL PROTECTED]:
Hi Nuria,
I've some doubts about SAML with axis2. I need to know if the sample05
covers all the the SAML cases.
No, it covers only one scenario. For example, this uses SAML token as a
supporting token. There is another scenarios where SAML token can be
used as a protection token where it will be used to sign and encrypt
messages.
We first receive the SAML token response then we indicate, in the
options
the responseToken id
I don't know where we are sending to the server the SAML assertion in
the
soapMessage
When the id is set, Rampart message builders add the assertion to the
security
header according to the security policy. If you monitor the messages
exchanged
through TCPMon, then you can actually see the SAML assertion in the
security
header of the SOAP request to the service.
Another thing is to know what are the requestSecurityToken parameters.
In the client, we set these parameters using RST template.
private static OMElement getRSTTemplate() throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMElement elem =
fac.createOMElement(SP11Constants.REQUEST_SECURITY_TOKEN_TEMPLATE);
TrustUtil.createTokenTypeElement(RahasConstants.VERSION_05_02,
elem).setText(RahasConstants.TOK_TYPE_SAML_10);
TrustUtil.createKeyTypeElement(RahasConstants.VERSION_05_02, elem,
RahasConstants.KEY_TYPE_PUBLIC_KEY);
TrustUtil.createKeySizeElement(RahasConstants.VERSION_05_02, elem,
256);
return elem;
}
These parameters are defined in the WS Trust specification [1].
/nandana
[1] - specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf
http://nandana83.blogspot.com/
Re: Apache rampart without encryption - nullpointerException
Oh boy, hitting myself to the head now. I thought you could specifiy an encryptionToken OR a SignatureToken. i guess the jira issue can be set to completed. Sorry for that... I am using the X509 certificates with a private key. I'm gonna give it a try with the endorsingTokens. Tnx for your help that's 5 stars for you! Nunny wrote: Hi Thomas, So, this is something i don't get: I only add add a signatureToken and still rampart tries to add an encryptionToken?! It looks like it is impossible to add a signature without an encryptionToken. -- According to WS - Security Policy Specification, a symmetric binding has to have either a protection token or both encryption token and signature token. sp:SymmetricBinding ... wsp:Policy ( sp:EncryptionToken ... wsp:Policy ... /wsp:Policy /sp:EncryptionToken sp:SignatureToken ... wsp:Policy ... /wsp:Policy /sp:SignatureToken ) | ( sp:ProtectionToken ... wsp:Policy ... /wsp:Policy /sp:ProtectionToken ) ... /wsp:Policy /sp:SymmetricBinding This how the symmetric binding works when a protection token is defined. The web service client creates an encrypted key by encrypting a random key using the web service's public key. Then this encrypted key is used to sign and encrypt the messages back and forth. So only the web service need to have a key pair to do symmetric binding. If the web service need to authenticate the client, then a X509 token can be used as an endorsing supporting token. When an endorsing supporting token is used, the client signs the message signature again generating a second signature ( To do this client has to have the private key of his X509Token, so the client can be authenticated ). In your case, are you using web service's X509 certificate ? Thanks, /nandana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Apache-rampart-without-encryption--%3E-nullpointerException-tp15408083p15428346.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SAML with Axis2
Hello Nunny,
is there any sample available where the SAML token can be used as a
protection token for signing and encrypting messages?
Thanks,
Jens
Nunny wrote:
Hi Nuria,
I've some doubts about SAML with axis2. I need to know if the sample05
covers all the the SAML cases.
No, it covers only one scenario. For example, this uses SAML token as a
supporting token. There is another scenarios where SAML token can be
used as a protection token where it will be used to sign and encrypt
messages.
We first receive the SAML token response then we indicate, in the options
the responseToken id
I don't know where we are sending to the server the SAML assertion in the
soapMessage
When the id is set, Rampart message builders add the assertion to the
security
header according to the security policy. If you monitor the messages
exchanged
through TCPMon, then you can actually see the SAML assertion in the
security
header of the SOAP request to the service.
Another thing is to know what are the requestSecurityToken parameters.
In the client, we set these parameters using RST template.
private static OMElement getRSTTemplate() throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMElement elem =
fac.createOMElement(SP11Constants.REQUEST_SECURITY_TOKEN_TEMPLATE);
TrustUtil.createTokenTypeElement(RahasConstants.VERSION_05_02,
elem).setText(RahasConstants.TOK_TYPE_SAML_10);
TrustUtil.createKeyTypeElement(RahasConstants.VERSION_05_02, elem,
RahasConstants.KEY_TYPE_PUBLIC_KEY);
TrustUtil.createKeySizeElement(RahasConstants.VERSION_05_02, elem, 256);
return elem;
}
These parameters are defined in the WS Trust specification [1].
/nandana
[1] - specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf
http://nandana83.blogspot.com/
http://nandanasm.wordpress.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/SAML-with-Axis2-tp15314610p15429275.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
axis2 1.3 and session management
Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk]
Unable to generate WSDL for this service
Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp /parameter operation name=Send messageReceiver class= org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL ( http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml ( /serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo
org.apache.axis2.AxisFault
Hi Group, I am using Axis 2. I have deployed my web service I am able to get the wsdl from it. But, when I write a client program using the generated stub, I am getting following error: org.apache.axis2.AxisFault: Exception occurred while trying to invoke service method getSearchResult at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java :486) Please let me know what could be causing this exception. Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.
Re: axis2 1.3 and session management
Hi MT, What error did you get when following the instructions given in the article? AFAIK, we did not come across a session management issue in Axis2-1.3. regards Charitha Michelantonio Trizio wrote: Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.3 and session management
I want to deploy a service with soapsession. I write this in services.xml: service name=foo scope= soapsession /service and write this in the client: stub._getServiceClient().getOptions().setManageSession(true); I don't know if it is important, but I use axis2 plugin for eclipse to generate the stub for the client. The problem is that in the response, I never find code like this: wsa:ReplyTo wsa:Address http://www.w3.org/2005/08/addressing/anonymous /wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2= http://ws.apache.org/namespaces/axis2; urn:uuid:65E9C56F702A398A8B11513011677354 /axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo Where do I wrong? Thanks 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED]: Hi MT, What error did you get when following the instructions given in the article? AFAIK, we did not come across a session management issue in Axis2-1.3. regards Charitha Michelantonio Trizio wrote: Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk]
Re: SAML with Axis2
Hi Nandana,
I've a doubt about the STS. Do the service and client limited to deploy the
rahas module to use STS or they can use different type of SAML Authority?.
If the SAML authority is not STS could our client connect to this SAML
authority or is limited to the STS?
Thanks, Nuria
2008/2/12, Nandana Mihindukulasooriya [EMAIL PROTECTED]:
Hi Nuria,
I've some doubts about SAML with axis2. I need to know if the sample05
covers all the the SAML cases.
No, it covers only one scenario. For example, this uses SAML token as a
supporting token. There is another scenarios where SAML token can be
used as a protection token where it will be used to sign and encrypt
messages.
We first receive the SAML token response then we indicate, in the
options
the responseToken id
I don't know where we are sending to the server the SAML assertion in
the
soapMessage
When the id is set, Rampart message builders add the assertion to the
security
header according to the security policy. If you monitor the messages
exchanged
through TCPMon, then you can actually see the SAML assertion in the
security
header of the SOAP request to the service.
Another thing is to know what are the requestSecurityToken parameters.
In the client, we set these parameters using RST template.
private static OMElement getRSTTemplate() throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMElement elem =
fac.createOMElement(SP11Constants.REQUEST_SECURITY_TOKEN_TEMPLATE);
TrustUtil.createTokenTypeElement(RahasConstants.VERSION_05_02,
elem).setText(RahasConstants.TOK_TYPE_SAML_10);
TrustUtil.createKeyTypeElement(RahasConstants.VERSION_05_02, elem,
RahasConstants.KEY_TYPE_PUBLIC_KEY);
TrustUtil.createKeySizeElement(RahasConstants.VERSION_05_02, elem,
256);
return elem;
}
These parameters are defined in the WS Trust specification [1].
/nandana
[1] - specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf
http://nandana83.blogspot.com/
http://nandanasm.wordpress.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.3 and session management
Managing a SOAP session requires you to engage addressing modules on both the server side and client side. You can engage addressing at the client side as follows. stub._getServiceClient().engageModule(addressing); In server side, please add the following element in services.xml module ref=addressing/ regards Charitha Michelantonio Trizio wrote: I want to deploy a service with soapsession. I write this in services.xml: service name=foo scope= soapsession /service and write this in the client: stub._getServiceClient().getOptions().setManageSession(true); I don't know if it is important, but I use axis2 plugin for eclipse to generate the stub for the client. The problem is that in the response, I never find code like this: wsa:ReplyTo wsa:Address http://www.w3.org/2005/08/addressing/anonymous /wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2= http://ws.apache.org/namespaces/axis2; urn:uuid:65E9C56F702A398A8B11513011677354 /axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo Where do I wrong? Thanks 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi MT, What error did you get when following the instructions given in the article? AFAIK, we did not come across a session management issue in Axis2-1.3. regards Charitha Michelantonio Trizio wrote: Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to generate WSDL for this service
Rather than specifying a per-operation message receiver, try using the standard message receiver config from the sample pojo service: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Paul On Feb 12, 2008 9:24 AM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp/parameter operation name=Send messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL (http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AXIS2 https/ssl session establishment is very very slow
Hi all, I've implemented a SOAP Web Services client using AXIS2-1.3 libraries and WSDL2JAVA. The main problem is that https/ssl session establishment is very very slow, it takes 4.5 seconds! I've used the following option to reuse httpclient: stub = new myStub(url); org.apache.axis2.client.Options options = stub._getServiceClient().getOptions(); options.setProperty( org.apache.axis2.transport.http.HTTPConstants.REUSE_HTTP_CLIENT, true); The SOAP requests after session establishment are almost as fast as http, but the other problem is that the session times out after 60 sec. and it takes another 4.5 sec again to establish a new session. I've used the following options to change the time-out period, but no change in timeout period happened! int timeOutInMilliSeconds = 300*1000; options.setTimeOutInMilliSeconds(timeOutInMilliSeconds); // doesn't make any difference options.setProperty( org.apache.axis2.transport.http.HTTPConstants.SO_TIMEOUT, timeOutInMilliSeconds); // No change in timeout! options.setProperty( org.apache.axis2.transport.http.HTTPConstants.CONNECTION_TIMEOUT , timeOutInMilliSeconds); // No change in timeout! I've believe the problem is in the AXIS client configuration, because other clients such as JMeter and .NET clients don't have this problem; their ssl session establishment is very fast. I've read the AXIS2 documentation but couldn't figure out how to fix these problems. I really appreciate your help. Thanks Joe
Run Java2WSDL on Class in Jar File?
I need to run Java2WSDL on a class that is in a jar file because all the dependencies (imported classes) are also in the jar file. Is this possible to do? If so, can anyone show me the syntax? Thanks, Steve
RE: Service interface with throws Exception generates There are no parts for fault message message, when passed through java2wsdl/wsl2java.
I tried the same scenario with Axis2 1.3. In this release, WSDL2Java
actually produces source with no error. The service APIs, which throw
java.lang.Exception, are generated to throw ExceptionException0, which
extends java.lang.Exception. It seems that this shouldn't be necessary
to create the extra subclass, but I assume that this is occurring
because there still is a problem with java2wsdl's handling of
java.lang.Exception.
Thanks, Dave
From: Kraus, David [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 10:34 AM
To: axis-user@ws.apache.org
Subject: Service interface with throws Exception generates There are
no parts for fault message message, when passed through
java2wsdl/wsl2java.
I have seen that issue Axis-2672 deals with the same or similar issue.
I am using Axis2 1.2. Is there a fix being worked on for this problem?
If so, which release will it be in? Also, are there any workarounds?
Details below:
First I use Java2WSDL to create WSDL from a java interface (the same
problem occurs whether I use a class or an interface):
java2wsdl.bat -cn com.microstrategy.webservices.WsfDemo -cp . -of
WsfDemo.wsdl
...where WsfDemo source is:
package com.microstrategy.webservices;
import com.microstrategy.webservices.MWSProjectSessionInfo;
import com.microstrategy.webservices.MWSConnectInfo;
public interface WsfDemo {
public MWSProjectSessionInfo ConnectToProject(MWSConnectInfo cInfo)
throws Exception;
public void logout(String sessionState)throws Exception;
}
... the generated WSDL is attached...
Next, I turn around and run WSDL2Java on the generated WSDL.
wsdl2java.bat -uri WsfDemo.wsdl -s -ss -sd -u -uw -d adb -g
..which generates the error...
Using AXIS2_HOME: D:\axis2-1.2
Using JAVA_HOME:C:\Program Files\Java\jdk1.6.0_02
Feb 12, 2008 10:04:27 AM
org.apache.axis2.description.WSDL11ToAxisServiceBuilder
addQNameReference
SEVERE: There are no parts for fault message :
{http://webservices.microstrategy
.com}Exception
Feb 12, 2008 10:04:27 AM
org.apache.axis2.description.WSDL11ToAxisServiceBuilder
populateService
SEVERE:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingEx
ception: There are no parts for fault message :
{http://webservices.microstrateg
y.com}Exception
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:137)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: There are no parts for fault
message : {h
ttp://webservices.microstrategy.com}Exception
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:298)
at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:100)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:131)
... 2 more
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: There are no parts for fault message :
{http://webservices.microstra
tegy.com}Exception
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:920)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:533)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:374)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:334)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:288)
... 4 more
Thanks, Dave
RE: Axis2 1.3 -- Is ordering of elements madatory in SOAP BODY
Should the client ensure the order of the elements inside the Soap
envelope?
Ram
From: Ram Thakkalapalli (rthakkal)
Sent: Tuesday, February 12, 2008 2:29 AM
To: axis-user@ws.apache.org
Subject: Axis2 1.3 -- Is ordering of elements madatory in SOAP BODY
Hello,
Here is a Java API and generated WSDL snippet. Does the order of the
elements in WSDL is mandatory when constructing the SOAP envelope?
In my test setup, I have encountered that the order of the elements
seems to be mandatory? If Yes, Can we make the order optional and read
the values from element name instead of element index?
Java Class Snippet:
public stats[] retrieveCPUUtilization(String name, String timeframe )
{
return stats[];
}
WSDL snippet :
xs:element name=retrieveCPUUtilization
xs:complexType
xs:sequence
xs:element minOccurs=0 name=name nillable=true type=xs:string/
xs:element minOccurs=0 name=timeframe nillable=true
type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
Scenario 1:
For the a SOAP request ( generated from WSDL2Java Utillity )of the
format below with the order of the paramters matching the Java API
above, the values are parsed correctly on the server side ( the java api
sets name= xy-server and timeframe=hour )
soapenv:Body
retrieveCPUUtilization
xs:namexy-server/xs:name
xs:timeframehour/xs:timeframe
/retrieveCPUUtilization
/soapenv:Body
Scenario 2 :
For the a SOAP request ( generated using SOAPpy )of the format below
with the order of the paramters are NOT matching the Java API above, the
values are parsed INCORRECTLY on the server side( the Java API sets
name=hour, timeframe =xy-server )
soapenv:Body
retrieveCPUUtilization
xs:timeframehour/xs:timeframe
xs:namexy-server/xs:name
/retrieveCPUUtilization
/soapenv:Body
Please let me know nif I am missing anything here.
Thanks
Ram
AW: Async requests killing network
That seems to solve the problem.
I have to do some further testing, but a first quick run with
cleanupTransport() after each bunch of requests succeeded.
Also, I could not reproduce the error on Windows Vista systems.
So tomorrow I will investigate this further with the Windows 2000 system.
Thanks,
Matthias
-Ursprüngliche Nachricht-
Von: Paul Fremantle [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 11. Februar 2008 16:12
An: axis-user@ws.apache.org
Betreff: Re: Async requests killing network
Have you tried using ServiceClient.cleanupTransport() ?
Paul
On Feb 11, 2008 3:01 PM, Matthias Wermund [EMAIL PROTECTED] wrote:
Yes if the requests were made parallel, I'd agree that this is very heavy
load.
But in my case I do only a few requests parallel, and start the next bunch
only if they are completed.
So I assume there is any garbage left from the completed requests?
That would also explain why the error only appears after some time, and a
few hundred requests.
- Original Message -
From: Paul Fremantle [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, February 11, 2008 3:00 PM
Subject: Re: Async requests killing network
Actually Matthias, 5000 connections is a lot for an untuned OS.
You need to tune your OS to cope with this sort of load. In my
personal experience Linux stacks are easier to tune to very high
TCP/IP loads. You might want to take a look at the tuning we did here:
http://wso2.org/library/2259 (Linux but the principals apply), and
this Windows tool as well: http://www.dslreports.com/drtcp
Paul
On Feb 11, 2008 1:31 PM, Matthias Wermund [EMAIL PROTECTED] wrote:
Thanks for your suggestion, I will definately look into this.
Generally spoken, 5000 HTTP connections shouldn't be a problem for
Windows,
should it?
Or is this simply a buggy behaviour in the Axis2 HTTP transport?
- Original Message -
From: Paul Fremantle [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, February 11, 2008 2:06 PM
Subject: Re: Async requests killing network
I should point out you do this by commenting (the normal HTTP
transport) and uncommenting (the NIO transport) in axis2.xml.
Some users have also tried the Synapse 1.1.1/1.1.2 NIO HTTP
transport
which has a number of bugs fixed compared to the Axis2 version
thereof. You need to grab the JAR file from Synapse and copy the
right
axis2.xml config from Synapse's axis2.xml.
Paul
On Feb 11, 2008 12:19 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
You might want to try this out using the NIO HTTP transport. It
should
scale better for this kind of behaviour.
Paul
On Feb 11, 2008 11:11 AM, Matthias Wermund [EMAIL PROTECTED]
wrote:
Hi,
I'm having problems starting a big amount of async webservice
requests
via
Axis2 client in short time.
The requests are all started from the same Thread and should run
parallel in
only small amount.
As you can see below, I start about 1000 * 5 = 5000 requests,
but
only
a max
of 2-5 are called parallel.
For each dataset, a few information-requests are started
parallel,
but
I
ensure that each CallbackHandler has been finished,
before requesting the informations for the next dataset.
For the first several hundred requests this works fine, but
after
some
time,
my network (OS is Windows 2000) goes down,
which means that the complete OS looses the connection to the
local
network.
I guess this could be based in opening too much TCP connections
or
something
like this,
because if it affects the whole OS and not just my application,
it
has
to be
something with the network device or driver.
So basically my question is:
Is it ensured that the TCP connection is already closed when
CallbackHandler.onError or CallbackHandler.onComplete is called?
Or must I do this myself in any way?
Do you have any other clue what might be the problem here?
Thank you!
__
A quick mock-overview of how I start the threads:
ListDataset datasets;// approx. 500 - 1000 objects
...
for (Object data: datasets) {
ListCallback callbacks;
for (Information info: myRequestsForThisData) {//
approx.
2-5
objects
// Generating the Request Document
Request request = generateRequest(info);
// Generating a service Callback instance; the Callback
class
has an
attribute finished
Callback myCallback = new Callback();
// remembering the callback
callbacks.add(myCallback);
// starting the async request
stub.startRequest(request,myCallback);
[Axis2] Difference between various Timeouts
Hi, Can anyone let me know the difference between the below 3 timeouts (Axis2 1.3). 1) stub._getServiceClient().getOptions().setTimeOutInMilliSeconds(timeoutIn MilliSeconds); 2) stub._getServiceClient().getOptions().setProperty(org.apache.axis2.trans port.http.HttpConstants.SO_TIMEOUT, timeoutInMilliSeconds); 3) stub._getServiceClient().getOptions().setProperty(org.apache.axis2.trans port.http.HttpConstants.CONNECTION_TIMEOUT, timeoutInMilliSeconds); Thanks Raghu
Re: [axis2] axis2 1.3 custom complex type problem
Hi ,
When I debug Axis2 with your scenario I found an issue in Axis2 , so I
have fixed that and committed the change , you may try with nightly
builds or wait for Axis2 1.4
Thanks
Deepal
Hi all,
i have define a new class that has an member which is an array of
KeyValuePair. Where KeyValuePair has two member of type object (key and value).
WSDL is genereated as follows:
xs:complexType name=Hashtable
xs:sequence
xs:element maxOccurs=unbounded minOccurs=0 name=keyValuePairs nillable=true
type=ns2:KeyValuePair/
/xs:sequence
/xs:complexType
xs:complexType name=KeyValuePair
xs:sequence
xs:element minOccurs=0 name=key nillable=true type=xs:anyType/
xs:element minOccurs=0 name=value nillable=true
type=xs:anyType/
/xs:sequence
/xs:complexType
Service class method:
public Hashtable testHashtable2() {
KeyValuePair[] keyValuePairs = new KeyValuePair[] {
new KeyValuePair(TestStringKey, TestStringValue),
new KeyValuePair(new Integer(1), new Integer(2)),
new KeyValuePair(StringKayForinteger, new Integer(2)),
new KeyValuePair(new Integer(1), StringValueForInteger),
new KeyValuePair(new Integer(1), new String(StringValueForInteger))
};
return new Hashtable(keyValuePairs);
}
and SOAP Response:
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns:testHashtable2Response xmlns:ns=http://coaching.de;
ns:return type=de.coaching.Hashtable xmlns:ax22=http://vo.coaching.de/xsd;
xmlns:ax23=http://io.java/xsd; xmlns:ax21=http://coaching.de/xsd;
ax21:keyValuePairs type=de.coaching.KeyValuePair
ax21:keyTestStringKey/ax21:key
ax21:valueTestStringValue/ax21:value
/ax21:keyValuePairs
ax21:keyValuePairs type=de.coaching.KeyValuePair
ax21:key type=java.lang.Integer/
ax21:value type=java.lang.Integer/
/ax21:keyValuePairs
ax21:keyValuePairs type=de.coaching.KeyValuePair
ax21:keyStringKayForinteger/ax21:key
ax21:value type=java.lang.Integer/
/ax21:keyValuePairs
ax21:keyValuePairs type=de.coaching.KeyValuePair
ax21:key type=java.lang.Integer/
ax21:valueStringValueForInteger/ax21:value
/ax21:keyValuePairs
ax21:keyValuePairs type=de.coaching.KeyValuePair
ax21:key type=java.lang.Integer/
ax21:valueStringValueForInteger/ax21:value
/ax21:keyValuePairs
/ns:return
/ns:testHashtable2Response
/soapenv:Body
/soapenv:Envelope
So for String there are the values but not type and for Integer there are no
values but the type. Why is this?
Regards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Async requests killing network
I did'nt get an answer so Im reposting..
Is there a way to configure in NIO transport in axis2
*without* enabling the NIO connector in TC server.xml?
Thanks
Martin-
- Original Message -
From: Paul Fremantle [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, February 11, 2008 8:06 AM
Subject: Re: Async requests killing network
I should point out you do this by commenting (the normal HTTP
transport) and uncommenting (the NIO transport) in axis2.xml.
Some users have also tried the Synapse 1.1.1/1.1.2 NIO HTTP transport
which has a number of bugs fixed compared to the Axis2 version
thereof. You need to grab the JAR file from Synapse and copy the right
axis2.xml config from Synapse's axis2.xml.
Paul
On Feb 11, 2008 12:19 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
You might want to try this out using the NIO HTTP transport. It should
scale better for this kind of behaviour.
Paul
On Feb 11, 2008 11:11 AM, Matthias Wermund [EMAIL PROTECTED] wrote:
Hi,
I'm having problems starting a big amount of async webservice requests
via
Axis2 client in short time.
The requests are all started from the same Thread and should run
parallel in
only small amount.
As you can see below, I start about 1000 * 5 = 5000 requests, but only
a max
of 2-5 are called parallel.
For each dataset, a few information-requests are started parallel, but
I
ensure that each CallbackHandler has been finished,
before requesting the informations for the next dataset.
For the first several hundred requests this works fine, but after some
time,
my network (OS is Windows 2000) goes down,
which means that the complete OS looses the connection to the local
network.
I guess this could be based in opening too much TCP connections or
something
like this,
because if it affects the whole OS and not just my application, it has
to be
something with the network device or driver.
So basically my question is:
Is it ensured that the TCP connection is already closed when
CallbackHandler.onError or CallbackHandler.onComplete is called?
Or must I do this myself in any way?
Do you have any other clue what might be the problem here?
Thank you!
__
A quick mock-overview of how I start the threads:
ListDataset datasets;// approx. 500 - 1000 objects
...
for (Object data: datasets) {
ListCallback callbacks;
for (Information info: myRequestsForThisData) {// approx. 2-5
objects
// Generating the Request Document
Request request = generateRequest(info);
// Generating a service Callback instance; the Callback class
has an
attribute finished
Callback myCallback = new Callback();
// remembering the callback
callbacks.add(myCallback);
// starting the async request
stub.startRequest(request,myCallback);
}
// now wait until all Callbacks are finished (finished is true if
onError or onComplete has been called)
while (true) {
boolean allCompleted = true;
for(Callback callback: callbacks)
if (callback.isFinished()) {
allCompleted = false;
break;
}
if (allCompleted)
break;
Thread.sleep(25);
}
}
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[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: Unable to generate WSDL for this service
Hello, try setting userOriginalWSDL to true, maybe that would help. Carlo Fabian Paulo Carvalho wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp/parameter operation name=Send messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL (http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo
Using Axis C++ Server with Axis Java client
HiWhat I have done: Following the excellant tutorial at http://www.linux.com/feature/113947?depth=5order=1sortby=3render=flat titled Creating Web Service using Apache Axis-C++ , I have made the tutorial work . But in the tutorial, the client is also c++ and it uses the WSDL2WS tool to general client stubs. However, after some googling, I figured out that you need to use the java2wsdl to generate java stubs.But then, when i looked at the java tutorials , I am a bit perplexed. May I know what is the equivalent procedures to do for a Java client. It would be great if you could answer with respect to the above link. I am using Apache 2.0.63 and Axis 1.4 in Ubuntu(linux) environment. Thanks for all the help. Regards Hanifa __ Yahoo! Singapore Answers Real people. Real questions. Real answers. Share what you know at http://answers.yahoo.com.sg
problem with axis generating faulty WSDL
Hello. I got a problem where my Axis2 (1.3) server is generating wsdl files for services that i cant use to generate clients for the same services, mainly because the WSDL is mallformed. I use eclipse for development, and eclipse do complain on the WSDL-files as well. Here is the output for http://localhost:8080/axis2/services/Version?wsdl http://pastebin.com/f12734e55 And here is the output for '/home/ilon/tomcat/axis2-1.3/bin/./wsdl2java.sh -uri version.wsdl -d adb -s' http://pastebin.com/f129de119 I'm getting similar problems when trying to generate WSDL for my own services. If i could get a hint of where to search for answers in this matter i would be very happy. Ilon Sjögren. -- vuln.se
Service interface with throws Exception generates There are no parts for fault message message, when passed through java2wsdl/wsl2java.
I have seen that issue Axis-2672 deals with the same or similar issue.
I am using Axis2 1.2. Is there a fix being worked on for this problem?
If so, which release will it be in? Also, are there any workarounds?
Details below:
First I use Java2WSDL to create WSDL from a java interface (the same
problem occurs whether I use a class or an interface):
java2wsdl.bat -cn com.microstrategy.webservices.WsfDemo -cp . -of
WsfDemo.wsdl
...where WsfDemo source is:
package com.microstrategy.webservices;
import com.microstrategy.webservices.MWSProjectSessionInfo;
import com.microstrategy.webservices.MWSConnectInfo;
public interface WsfDemo {
public MWSProjectSessionInfo ConnectToProject(MWSConnectInfo cInfo)
throws Exception;
public void logout(String sessionState)throws Exception;
}
... the generated WSDL is attached...
Next, I turn around and run WSDL2Java on the generated WSDL.
wsdl2java.bat -uri WsfDemo.wsdl -s -ss -sd -u -uw -d adb -g
..which generates the error...
Using AXIS2_HOME: D:\axis2-1.2
Using JAVA_HOME:C:\Program Files\Java\jdk1.6.0_02
Feb 12, 2008 10:04:27 AM
org.apache.axis2.description.WSDL11ToAxisServiceBuilder
addQNameReference
SEVERE: There are no parts for fault message :
{http://webservices.microstrategy
.com}Exception
Feb 12, 2008 10:04:27 AM
org.apache.axis2.description.WSDL11ToAxisServiceBuilder
populateService
SEVERE:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingEx
ception: There are no parts for fault message :
{http://webservices.microstrateg
y.com}Exception
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:137)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: There are no parts for fault
message : {h
ttp://webservices.microstrategy.com}Exception
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:298)
at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:100)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerat
ionEngine.java:131)
... 2 more
Caused by:
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: There are no parts for fault message :
{http://webservices.microstra
tegy.com}Exception
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:920)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:533)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:374)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:334)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:288)
... 4 more
Thanks, Dave
WsfDemo.wsdl
Description: WsfDemo.wsdl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to generate WSDL for this service
Yes the answer is fairly simple. In the axis2.xml it defines default message receivers. You only overrode the MR for one operation. Now admittedly you only had the one operation, but Axis2 didn't realise. So it looked at the service, saw there is no MR defined for the service, looked at the default. The default is RawXML, which it cannot create WSDL for, so it decided that it couldn't generate WSDL. Does that make sense? Paul On Feb 12, 2008 2:29 PM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello Thanks for your quick answer. Your solution have resolved my problem. But I would like to know why. Do you know? thanks again regards On 2/12/08, Paul Fremantle [EMAIL PROTECTED] wrote: Rather than specifying a per-operation message receiver, try using the standard message receiver config from the sample pojo service: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Paul On Feb 12, 2008 9:24 AM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp/parameter operation name=Send messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL (http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paulo Carvalho 1 rue du Chateau 57710 Aumetz France www.antikuado.com www.sunofportugal.com -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
retrieving MTOM in a client
I'm using MTOM in a java client but when I try to retrieve the OMText at the client side i.e.: OMText binaryNode = (OMText) mapImage.getFirstOMChild(); I get a class cast exception, since the response is returning an OMElement and not OMText anyone come across this before? I've checked the soap message and it does actually include the binary data. Thanks in advance Adam
Re: Unable to generate WSDL for this service
Hello Thanks for your quick answer. Your solution have resolved my problem. But I would like to know why. Do you know? thanks again regards On 2/12/08, Paul Fremantle [EMAIL PROTECTED] wrote: Rather than specifying a per-operation message receiver, try using the standard message receiver config from the sample pojo service: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Paul On Feb 12, 2008 9:24 AM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp/parameter operation name=Send messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL (http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paulo Carvalho 1 rue du Chateau 57710 Aumetz France www.antikuado.com www.sunofportugal.com
RE: Is Axis for Me?
Azeez, Thanks so much for both of your responses. I'll be in touch if I need any help. Regards, Steve From: Afkham Azeez [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 12:27 AM To: axis-user@ws.apache.org Subject: Re: Is Axis for Me? On Tue, Feb 12, 2008 at 4:38 AM, Murphy Steve [EMAIL PROTECTED] wrote: I'm a web services beginner and I need to create client applications for existing web services that are running in a Web Logic server. I need to know: 1. Can I use Axis to create clients that use the web services? Yes, definitely. This is a basic requirement of any Web services framework 2. If the answer to question 1 is yes then which Axis2 download do I use? The last stable release was Axis2 1.3 (http://ws.apache.org/axis2/download/1_3/download.cgi) Thanks. -- Thanks Afkham Azeez http://azeez78.blogspot.com http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: Unable to generate WSDL for this service
Yes, thank you! regards. On 2/12/08, Paul Fremantle [EMAIL PROTECTED] wrote: Yes the answer is fairly simple. In the axis2.xml it defines default message receivers. You only overrode the MR for one operation. Now admittedly you only had the one operation, but Axis2 didn't realise. So it looked at the service, saw there is no MR defined for the service, looked at the default. The default is RawXML, which it cannot create WSDL for, so it decided that it couldn't generate WSDL. Does that make sense? Paul On Feb 12, 2008 2:29 PM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello Thanks for your quick answer. Your solution have resolved my problem. But I would like to know why. Do you know? thanks again regards On 2/12/08, Paul Fremantle [EMAIL PROTECTED] wrote: Rather than specifying a per-operation message receiver, try using the standard message receiver config from the sample pojo service: messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /messageReceivers Paul On Feb 12, 2008 9:24 AM, Paulo Carvalho [EMAIL PROTECTED] wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp/parameter operation name=Send messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL (http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paulo Carvalho 1 rue du Chateau 57710 Aumetz France www.antikuado.com www.sunofportugal.com -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paulo Carvalho 1 rue du Chateau 57710 Aumetz France www.antikuado.com www.sunofportugal.com
Re: Unable to generate WSDL for this service
Thanks for your answer. I had already try it before with no positive result. On 2/13/08, Jose Carlo Fabian [EMAIL PROTECTED] wrote: Hello, try setting userOriginalWSDL to true, maybe that would help. Carlo Fabian Paulo Carvalho wrote: Hello I am new using Axis2 and I am having a problem. I already search over the net to find the solution for my problem, but everything looks fine for me. 1 - I am using the last version of Axis2. 2 - I have a class called MyApp (in the app package) with the method Send 3 - My services.xml file is the following one: serviceGroup service name=MyService descriptionMy service/description parameter name=useOriginalWSDLfalse/parameter parameter name=ServiceClass locked=falseapp.MyApp /parameter operation name=Send messageReceiver class= org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation /service /serviceGroup 4 - The webservice is deployed with success 5 - When I try to access to this WSDL ( http://localhost:8084/MyWS/services/MyService?wsdl) I have the following message/reason appearing on my browser instead of the WSDL: error descriptionUnable to generate WSDL for this service/description reason If you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml ( /serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name). /reason /error Can anyone help me with that? Thanks Best regards Paulo -- Paulo Carvalho 1 rue du Chateau 57710 Aumetz France www.antikuado.com www.sunofportugal.com
Re: axis2 1.3 and session management
Michelantonio Trizio wrote: Thanks, but now on the client I have this message: org.apache.axis2.AxisFault: Unable to engage module : addressing How can I say to the client where is addressing-1.3.mar? I try both stub._getServiceClient().engageModule(addressing); and stub._getServiceClient().engageModule(addressing-1.3); Please make sure addressing-1.3.mar is in your class path. Also, try stub._getServiceClient().engageModule(Constants.MODULE_ADDRESSING). On the server side I enable addressing globally, Do I however need to add module ref=addressing/ in services.xml? No. If addressing is globally engaged, you don't want to engage it at the service level. Thanks a lot 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Managing a SOAP session requires you to engage addressing modules on both the server side and client side. You can engage addressing at the client side as follows. stub._getServiceClient().engageModule(addressing); In server side, please add the following element in services.xml module ref=addressing/ regards Charitha Michelantonio Trizio wrote: I want to deploy a service with soapsession. I write this in services.xml: service name=foo scope= soapsession /service and write this in the client: stub._getServiceClient().getOptions().setManageSession(true); I don't know if it is important, but I use axis2 plugin for eclipse to generate the stub for the client. The problem is that in the response, I never find code like this: wsa:ReplyTo wsa:Address http://www.w3.org/2005/08/addressing/anonymous /wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2= http://ws.apache.org/namespaces/axis2; urn:uuid:65E9C56F702A398A8B11513011677354 /axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo Where do I wrong? Thanks 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi MT, What error did you get when following the instructions given in the article? AFAIK, we did not come across a session management issue in Axis2-1.3. regards Charitha Michelantonio Trizio wrote: Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build
RE: .Net client
Hi group, I am using axis 1.4 generated services with code-first approach for ws development. For creating VB client, I used visual studio by adding web reference to the project pointing to my web service. It generated the client-side code, but the return from any of the ws methods is always null/nothing. Any pointers for resolving this problem would be helpful. Thanks, Ajit -Original Message- From: Charitha Kankanamge [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 4:24 PM To: axis-user@ws.apache.org Subject: Re: .Net client Hi Ajit, See my comments inline. [EMAIL PROTECTED] wrote: Hi Group, Is nillable=*true* in wsdl going to create problem as far as the compatibility with .Net goes? No. It will not give any problem. When I access my ws from a .Net client, I always get a response as null/nothing (even with primitive types). It works fine with Java client. Has anybody faced this problem? How did you create your service? is it a pojo or a generated service? Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.3 and session management
Thanks, but now on the client I have this message: org.apache.axis2.AxisFault: Unable to engage module : addressing How can I say to the client where is addressing-1.3.mar? I try both stub._getServiceClient().engageModule(addressing); and stub._getServiceClient().engageModule(addressing-1.3); On the server side I enable addressing globally, Do I however need to add module ref=addressing/ in services.xml? Thanks a lot 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED]: Managing a SOAP session requires you to engage addressing modules on both the server side and client side. You can engage addressing at the client side as follows. stub._getServiceClient().engageModule(addressing); In server side, please add the following element in services.xml module ref=addressing/ regards Charitha Michelantonio Trizio wrote: I want to deploy a service with soapsession. I write this in services.xml: service name=foo scope= soapsession /service and write this in the client: stub._getServiceClient().getOptions().setManageSession(true); I don't know if it is important, but I use axis2 plugin for eclipse to generate the stub for the client. The problem is that in the response, I never find code like this: wsa:ReplyTo wsa:Address http://www.w3.org/2005/08/addressing/anonymous /wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2= http://ws.apache.org/namespaces/axis2; urn:uuid:65E9C56F702A398A8B11513011677354 /axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo Where do I wrong? Thanks 2008/2/12, Charitha Kankanamge [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi MT, What error did you get when following the instructions given in the article? AFAIK, we did not come across a session management issue in Axis2-1.3. regards Charitha Michelantonio Trizio wrote: Hi, I'd like to know how to use session on axis2 1.3 I use this guide http://www.developer.com/java/web/article.php/3620661 , but it not works. Where can I find an explicit example? Thanks MT -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- It's creepy, but here we are, the Pilgrims, the crackpots of our time, trying to establish our own alternate reality. To build a world out of rocks and chaos. What it's going to be, I don't know. Even after all that rushing around, where we've ended up is the middle of nowhere in the middle of the night. And maybe knowing isn't the point. Where we're standing right now, in the ruins in the dark, what we build could be anything. [Choke - Chuck Palahniuk]
Axis2 1.3 -- Is ordering of elements madatory in SOAP BODY
Hello,
Here is a Java API and generated WSDL snippet. Does the order of the
elements in WSDL is mandatory when constructing the SOAP envelope?
In my test setup, I have encountered that the order of the elements
seems to be mandatory? If Yes, Can we make the order optional and read
the values from element name instead of element index?
Java Class Snippet:
public stats[] retrieveCPUUtilization(String name, String timeframe )
{
return stats[];
}
WSDL snippet :
xs:element name=retrieveCPUUtilization
xs:complexType
xs:sequence
xs:element minOccurs=0 name=name nillable=true type=xs:string/
xs:element minOccurs=0 name=timeframe nillable=true
type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
Scenario 1:
For the a SOAP request ( generated from WSDL2Java Utillity )of the
format below with the order of the paramters matching the Java API
above, the values are parsed correctly on the server side ( the java api
sets name= xy-server and timeframe=hour )
soapenv:Body
retrieveCPUUtilization
xs:namexy-server/xs:name
xs:timeframehour/xs:timeframe
/retrieveCPUUtilization
/soapenv:Body
Scenario 2 :
For the a SOAP request ( generated using SOAPpy )of the format below
with the order of the paramters are NOT matching the Java API above, the
values are parsed INCORRECTLY on the server side( the Java API sets
name=hour, timeframe =xy-server )
soapenv:Body
retrieveCPUUtilization
xs:timeframehour/xs:timeframe
xs:namexy-server/xs:name
/retrieveCPUUtilization
/soapenv:Body
Please let me know nif I am missing anything here.
Thanks
Ram
.Net client
Hi Group, Is nillable=true in wsdl going to create problem as far as the compatibility with .Net goes? When I access my ws from a .Net client, I always get a response as null/nothing (even with primitive types). It works fine with Java client. Has anybody faced this problem? Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.
Re: .Net client
Hi Ajit, See my comments inline. [EMAIL PROTECTED] wrote: Hi Group, Is nillable=*true* in wsdl going to create problem as far as the compatibility with .Net goes? No. It will not give any problem. When I access my ws from a .Net client, I always get a response as null/nothing (even with primitive types). It works fine with Java client. Has anybody faced this problem? How did you create your service? is it a pojo or a generated service? Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
