Re: Order of SOAPHeader and SOAPBody
Hi Eran,
Could you tell me what files are modified to fix this bug?
Regards,
Xinjun
On 4/6/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> Hi Xinjun,
>
> We can not fix any bugs in releases (unfortunately). But I fixed that in
> the latest svn head. So you need to build against the current svn.
> Do not worry, checking out Axis2 sources and building it is very simple,
> as we have maven as our build tool.
>
> (But in case, if you get any problems, please ask it here ;) )
>
> -- Chinthaka
>
> Xinjun Chen wrote:
> > Hi Eran,
> >
> > Thank you!
> > Did you fix the bug in Axis2 0.94 or 0.95? I am using Axis2 0.94. Must
> > I upgrade to 0.95?
> >
> > Regards,
> > Xinjun
> >
> > On 4/6/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> >> Hi Xinjun,
> >>
> >> There was a known bug in SOAPEnvelope, which is the same pointed out
> >> also. I fixed it and now you can add SOAPHeader now to SOAPEnvelope and
> >> that will be added properly now.
> >>
> >> -- Chinthaka
> >>
> >> Xinjun Chen wrote:
> >>> I found a walk-around.
> >>>
> >>> envelope.getBody().insertSiblingBefore(headerElm);
> >>>
> >>> This will add the header OMElement into the envelope. However, the
> >>> Header added is only considered as a child element of envelope, not a
> >>> SOAPHeader. Thus if I call envelope.getHeader(), I will get exception.
> >>>
> >>> Regards,
> >>> Xinjun
> >>>
> >>> On 4/5/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
> I am using the following function to add UsernameToken to my security
> header. But the processed envelope get some problems.
> 1. The Header is placed after the body. How can I insert SOAPHeader
> before SOAPBody?
> 2. The security header defines the xmlns:xsd and xmlns:xsi again,
> which have already been defined in .
>
> Could you give me some advice on how to solve the above two problems?
>
> Attached:
>
> 1) The function used for adding username token to the envelope:
>
> public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
> envelope) throws Exception {
> Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
> WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
> if (token.isDigested()) {
> builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
> } else {
> builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
> }
>
> builder.build(domDoc, token.getUsername(), token.getPassword());
> Element header = (Element)
> (domDoc.getElementsByTagName("wsse:Security").item(0));
> OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
> SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
> factory.createSOAPHeader(envelope);
> envelope.getHeader().addChild(headerElm);
> }
>
> 2): The original soap envelope:
>
> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> http://services/helloworld";>
> Hello world!
>
>
>
>
> 3): The processed soap envelope:
>
> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> http://services/helloworld";>
> Hello world!
>
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> xinjun Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password
>
> >>
> >>
> >>
> >>
> >
>
>
>
>
>
RE: The was not specified. while Java2WSDL
Hi, I am in the process of creating WSDL from Java through *Java2WSDL*. My command line script is - java org.apache.axis.wsdl.Java2WSDL -n "https://tools-dev.cisco.com/cws/ces/services/CESService" -l "CESService" -m "createCollaborationSpace" -i "com.cisco.es.livelink.LiveLinkConfigEngine_CCO" I have specified -i option for class-of-portType but still I am getting following exception. Please guide me or give any pointer. The was not specified.Java2WSDL emitterUsage: java org.apache.axis.wsdl.Java2WSDL [options] class-of-portTypeOptions: -h, --help print this message and exit -I, --input input WSDL filename -o, --output output WSDL filename -l, --location service location url -P, --portTypeName portType name (obtained from class-of-portType if not specif ied) -b, --bindingName binding name (--servicePortName value + "SOAPBinding" if not specified) -S, --serviceElementName service element name (defaults to --servicePortName value + "Service") -s, --servicePortName service port name (obtained from --location if not specified ) -n, --namespace target namespace -p, --PkgtoNS = package=namespace, name value pairs -m, --methods space or comma separated list of methods to export -a, --all look for allowed methods in inherited class -w, --outputWsdlMode output WSDL mode: All, Interface, Implementation -L, --locationImport location of interface wsdl -N, --namespaceImpl target namespace for implementation wsdl -O, --outputImpl output Implementation WSDL filename, setting this causes --o utputWsdlMode to be ignored -i, --implClass optional class that contains implementation of methods in cl ass-of-portType. The debug information in the class is used to obtain the method parameter names, which are used to set the WSDL part names. -x, --exclude space or comma separated list of methods not to export -c, --stopClasses space or comma separated list of class names which will stop inheritance search if --all switch is given -T, --typeMappingVersion indicate 1.1 or 1.2. The default is 1.1 (SOAP 1.1 JAX-RPC c ompliant 1.2 indicates SOAP 1.1 encoded.) -A, --soapAction value of the operations soapAction field. Values are DEFAULT , OPERATION or NONE. OPERATION forces soapAction to the name of the operation. DEFAULT causes the soapAction to be set according to the operations meta data (usually ""). NONE fo rces the soapAction to "". The default is DEFAULT. -y, --style The style of binding in the WSDL, either DOCUMENT, RPC, or W RAPPED. -u, --use The use of items in the binding, either LITERAL or ENCODED -e, --extraClasses A space or comma separated list of class names to be added t o the type section. -C, --importSchema A file or URL to an XML Schema that should be physically imp orted into the generated WSDLDetails: portType element name= <--portTypeName value> OR binding element name= <--bindingName value> OR <--servicePortName value>SoapBinding service element name= <--serviceElementName value> OR <--portTypeName value>Service port element name= <--servicePortName value> address location = <--location value> --- CCWLL Services Dev Group | Zensar-Cisco ODC | (D) +91 (020) 5609 8245 Don't worry about the world coming to an end today. It's already tomorrow in Australia
Re: Axis2 & DIME Attachments
Axis2 does not support DIME. Currently supports MIME as the only attachment packaging format... AFAIK nobody is working on impelmenting DIME support... ~Thilina On 4/5/06, Alessandro Busato <[EMAIL PROTECTED]> wrote: > Hello, > I've implemented an axis 1.1 client towards a gSoapService which > returns DIME attachments; looks like it is working well! > > I've re-implemented the client using OMElement of Axis2 , > but the ServiceClient is not able to create correctly the SOAPMessage, > it throws the following error: "org.apache.axis2.AxisFault: Invalid > UTF-8 middle " > > In the axis1.1 into the Call object I've set > _call.setProperty(Call.ATTACHMENT_ENCAPSULATION_FORMAT, > Call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME); > > I believe this could be the cause since I cannot find how to do the same > in Axis2. > > Any suggestions, > kind regards > Alessandro > -- "May the SourcE be with u" http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
Re: Order of SOAPHeader and SOAPBody
Hi Xinjun,
We can not fix any bugs in releases (unfortunately). But I fixed that in
the latest svn head. So you need to build against the current svn.
Do not worry, checking out Axis2 sources and building it is very simple,
as we have maven as our build tool.
(But in case, if you get any problems, please ask it here ;) )
-- Chinthaka
Xinjun Chen wrote:
> Hi Eran,
>
> Thank you!
> Did you fix the bug in Axis2 0.94 or 0.95? I am using Axis2 0.94. Must
> I upgrade to 0.95?
>
> Regards,
> Xinjun
>
> On 4/6/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>> Hi Xinjun,
>>
>> There was a known bug in SOAPEnvelope, which is the same pointed out
>> also. I fixed it and now you can add SOAPHeader now to SOAPEnvelope and
>> that will be added properly now.
>>
>> -- Chinthaka
>>
>> Xinjun Chen wrote:
>>> I found a walk-around.
>>>
>>> envelope.getBody().insertSiblingBefore(headerElm);
>>>
>>> This will add the header OMElement into the envelope. However, the
>>> Header added is only considered as a child element of envelope, not a
>>> SOAPHeader. Thus if I call envelope.getHeader(), I will get exception.
>>>
>>> Regards,
>>> Xinjun
>>>
>>> On 4/5/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
I am using the following function to add UsernameToken to my security
header. But the processed envelope get some problems.
1. The Header is placed after the body. How can I insert SOAPHeader
before SOAPBody?
2. The security header defines the xmlns:xsd and xmlns:xsi again,
which have already been defined in .
Could you give me some advice on how to solve the above two problems?
Attached:
1) The function used for adding username token to the envelope:
public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
envelope) throws Exception {
Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
if (token.isDigested()) {
builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
} else {
builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
}
builder.build(domDoc, token.getUsername(), token.getPassword());
Element header = (Element)
(domDoc.getElementsByTagName("wsse:Security").item(0));
OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
factory.createSOAPHeader(envelope);
envelope.getHeader().addChild(headerElm);
}
2): The original soap envelope:
>>> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://services/helloworld";>
Hello world!
3): The processed soap envelope:
>>> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://services/helloworld";>
Hello world!
>>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
xinjun>>> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password
>>
>>
>>
>>
>
signature.asc
Description: OpenPGP digital signature
RE: [SPAM] - Re: [SPAM] - Re: Problems getting user exceptions to work - Found word(s) check out in the Text body - Found word(s) check out in the subject
Hello! I decided to piggy-back on this thread... I am having similar problems. Thom, What did you mean? I suppose recommend changing WSDL definition but a) my WSDL is auto-published so I can't really change it and b) even if I do, it does not change the XML that server generates and that is totally language-specific which kinda violates the purpose. Or did you mean something else? I am using Axis 1.3. I have following questions: 1) Is there a way to set server to use SOAP 1.2 (RTFMs are welcome, just tell where)? 2) Is there a way to specify custom values for faultcode/faultstring? Best I could get was my exception being serialized into XML under details but then I have to process it as XML :-\ 3) Overall, I need to publish a web service that is going to be used from different platforms. Is my best bet to just give up faults altogether and use some custom base result structure with generic error passing engine? Any recommendations (again, RTFMs are welcome) I do not expect much success since the envelope XSD itself is pretty limiting (http://schemas.xmlsoap.org/soap/envelope, toward the end), it's just those two fields and freeform XML "details". SOAP 1.2 looks a little better but without documentation it did not help much either. Any recommendations/insights are welcome. Thank you, -Michael ___ Tell a man there are 300 billion stars in the universe and he'll believe Tell him a bench has wet paint on it and he'll have to touch to be sure -- /usr/bin/fortune -Original Message- From: Thom Hehl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 30, 2006 1:47 PM To: axis-user@ws.apache.org Subject: Re: [SPAM] - Re: [SPAM] - Re: Problems getting user exceptions to work - Found word(s) check out in the Text body - Found word(s) check out in the subject Have a look at this: Give him This: _original type def from imported xsd___ _also needed in wsdl file___ *(in the portType operation definition for a method throwing a fault)* *(in the binding operation definintion for a method throwing a fault)* Jack Lund wrote: > See, I'm not really sure. The JAX/RPC spec is kinda hazy on how > exceptions are handled, and how the soap fault maps to an exception. > Here's what I'm seeing come back from the server: > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > >soapenv:Server.userException >com.foobar.ecommerce.beans.InvalidDateException: A > valid date must be specified in the form of MM/DD/. > > xsi:type="ns1:InvalidDateException" xmlns:ns1="urn:ClaimsData"/> > xmlns:ns2="http://xml.apache.org/axis/";>staportal01.stratarc.net > > > > > > > And here's what the corresponding part of the WSDL looks like: > > > xmlns="http://www.w3.org/2001/XMLSchema";> > http://hib.ecommerce.foobar.com"/> >namespace="http://portal01.foobar.com:8080/axis/services/ClaimsData"/> > http://dao.ecommerce.foobar.com"/> > http://beans.ecommerce.foobar.com"/> > http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > > > > > > > > > > > > > > > > What makes me think the serialization isn't working is that the > definition of the InvalidDateException is pretty much empty. However, > it also looks like there's enough information in the passed soap > message to be able to deserialize the exception properly, so I don't > really know what's going on here. > > Do you (or anybody) have an example of what a "good" soap fault mapped > from a java exception looks like? > > Thanks. > > -Jack > > > Thom Hehl wrote: > >> Hmmm. Check your SOAP messae. Our problem is that we're sending the >> correct data from the server and the error happens during >> deserialization. If that's not it, it's a different problem. >> >> Jack Lund wrote: >> >>> Thanks! I'd love to hear the workaround - I've tried everything I >>> can. It looks like the problem is that the server side doesn't >>> really know how to serialize the exception, even though it should. >>> >>> -Jack >>> >>> Thom Hehl wrote: >>> We had EXACTLY the same problem! We just found it and found a work-around, but believe this to be a bug in AXIS that should be fixed. The guy on our team that found it was going to write something up for the list. I'll ask him to step this up a bit as it would be of benefit to you. Jack Lund wrote: > Yeah, I can see that that would be easier. Unfortunately, I have > no control over the exceptions being thrown - I just need the > client-side to be able to catch them *as* the exceptions that are > originally thrown. I also am doing dynamic proxying rather than > stubs/skeletons, so
Re: Order of SOAPHeader and SOAPBody
Hi Ruchith, Your reference is extremely useful! Thank you very much. What I am trying to is to use security module at the server side, and use some other handlers at the client side. I am testing the interoperability between my proprietary module and the Axis2 security module. Am i on the right track to do the work? Regards, Xinjun On 4/6/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi, > > If you are using Axis2 you can use the Axis2 security module [1] to do this. > > Please see this simple how-to [2] document and try it out. > > Example: > client's configured axis2.xml file - [3] > the service's services.xml file - [4] > > Thanks, > Ruchith > > [1] > http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/wss4j/0_95/security-0.95.mar > [2] http://ws.apache.org/axis2/0_95/security-module.html > [3] > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test-resources/security/s1.client.axis2.xml > [4] > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test-resources/security/s1.service.xml > > On 4/5/06, Daniel Destro <[EMAIL PROTECTED]> wrote: > > Hi Xinjun, > > > > As I can see you are trying to add some Security to your Web Services, > > right? > > > > Are you doing a User Authentication / Authorization using this > > UsernameToken? > > > > I need to do that! > > > > How do add UsernameToken into to the SOAP request and how do u read / > > validate UsernameToken from the SOAP request (server-side) ??? > > > > Thanks > > Daniel > > >
Re: Order of SOAPHeader and SOAPBody
Hi Daniel,
I take advantage of WSS4J to add UsernameToken to the SOAPEnvelope.
Some sample codes:
Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
// Add the UserNameToken.
WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
if (token.isDigested()) {
builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
} else {
builder.setPasswordType(WSConstants.PASSWORD_TEXT);
}
builder.build(domDoc, token.getUsername(), token.getPassword());
Element header = (Element)
(domDoc.getElementsByTagName("SOAP-ENV:Header").item(0));
//SOAPHeader header = Axis2Util.getSOAPFactory(envelope);
//SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
envelope.getBody().insertSiblingBefore(headerElm);
These are only some experimental codes.
I assume the SOAPEnvelope has been constructed. What these code
snippet is more of a handler. There may be other ways to do it. As
Ruchith said, you can also take advantage of Axis2 security module.
Regards,
Xinjun
On 4/6/06, Daniel Destro <[EMAIL PROTECTED]> wrote:
> Hi Xinjun,
>
> As I can see you are trying to add some Security to your Web Services,
> right?
>
> Are you doing a User Authentication / Authorization using this
> UsernameToken?
>
> I need to do that!
>
> How do add UsernameToken into to the SOAP request and how do u read /
> validate UsernameToken from the SOAP request (server-side) ???
>
> Thanks
> Daniel
>
Re: Order of SOAPHeader and SOAPBody
Hi Eran,
Thank you!
Did you fix the bug in Axis2 0.94 or 0.95? I am using Axis2 0.94. Must
I upgrade to 0.95?
Regards,
Xinjun
On 4/6/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> Hi Xinjun,
>
> There was a known bug in SOAPEnvelope, which is the same pointed out
> also. I fixed it and now you can add SOAPHeader now to SOAPEnvelope and
> that will be added properly now.
>
> -- Chinthaka
>
> Xinjun Chen wrote:
> > I found a walk-around.
> >
> > envelope.getBody().insertSiblingBefore(headerElm);
> >
> > This will add the header OMElement into the envelope. However, the
> > Header added is only considered as a child element of envelope, not a
> > SOAPHeader. Thus if I call envelope.getHeader(), I will get exception.
> >
> > Regards,
> > Xinjun
> >
> > On 4/5/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
> >> I am using the following function to add UsernameToken to my security
> >> header. But the processed envelope get some problems.
> >> 1. The Header is placed after the body. How can I insert SOAPHeader
> >> before SOAPBody?
> >> 2. The security header defines the xmlns:xsd and xmlns:xsi again,
> >> which have already been defined in .
> >>
> >> Could you give me some advice on how to solve the above two problems?
> >>
> >> Attached:
> >>
> >> 1) The function used for adding username token to the envelope:
> >>
> >> public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
> >> envelope) throws Exception {
> >>Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
> >>WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
> >>if (token.isDigested()) {
> >>builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
> >>} else {
> >>builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
> >>}
> >>
> >>builder.build(domDoc, token.getUsername(), token.getPassword());
> >>Element header = (Element)
> >> (domDoc.getElementsByTagName("wsse:Security").item(0));
> >>OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
> >>SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
> >>factory.createSOAPHeader(envelope);
> >>envelope.getHeader().addChild(headerElm);
> >> }
> >>
> >> 2): The original soap envelope:
> >>
> >> >> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >>
> >> http://services/helloworld";>
> >> Hello world!
> >>
> >>
> >>
> >>
> >> 3): The processed soap envelope:
> >>
> >> >> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >>
> >> http://services/helloworld";>
> >> Hello world!
> >>
> >>
> >> >> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >> xinjun >> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password
> >>
> >
>
>
>
>
>
Can't compile web service with exception
Hi all,
I too am having trouble with exceptions. I can't even get past
compilation now. I added a simple method to my interface
definition:
Family.java:
public void testException() throws Exception;
Here's the implementation:
FamilyImpl.java:
public void testException() throws Exception
{
throw new Exception("Well take that!");
}
I did:
$ java org.apache.axis.wsdl.Java2WSDL -o family.wsdl \
--implClass disney.dis.family.FamilyImpl \
-l"http://localhost:8080/axis/services/familyAccounts"; \
-p"disney.dis.family" urn:familyAccounts \
disney.dis.family.Family
to generate the family.wsdl file. Then I did:
$ java org.apache.axis.wsdl.WSDL2Java -o . -d Session -s \
-p disney.dis.family family.wsdl
When I compile, I get these errors:
FamilyAccountsSoapBindingImpl.java:123: testException() in
disney.dis.family.FamilyAccountsSoapBindingImpl cannot implement
testException() in disney.dis.family.Family; overridden method does not
throw java.lang.Exception
public void testException() throws java.lang.Exception
^
FamilyImpl.java:1105: testException() in disney.dis.family.FamilyImpl
cannot implement testException() in disney.dis.family.Family; overridden
method does not throw java.lang.Exception
public void testException() throws Exception
Apparently the compiler thinks that my method prototype in the
Family.java interface definition doesn't throw Exception. But it
does (above).
More strangely, here is the prototype from the _generated_
Family.java file:
public void testException() throws java.rmi.RemoteException;
WSDL2Java added "throws java.rmi.RemoteException" but not
"throws Exception".
Why is WSDL2Java not adding the "throws Exception" to the
method prototype in the generated Family.java interface file?
I followed a few threads the past several days about "tweaking
the wsdl file to get exception handling correct." I admit I
didn't quite follow.
Is there something I need to do after generating the wsdl file,
before running the WSDL2Java command, to get exceptions to work?
Here is excerpt from the generated WSDL below:
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:familyAccounts" use="encoded"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:familyAccounts" use="encoded"/>
Thanks,
Vartan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Can't compile code with exceptions
Hi all, I too am having trouble with exceptions. I can't even compile my code. I added one method to my interface as follows: Family.java: __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: Re[2]: Problem using deployed Axis web services
http://ws.apache.org/axis/java/reference.html
-t builds testClient
good luck,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Martin Wunderlich
Sent: Wednesday, April 05, 2006 3:57 PM
To: Jinyuan Zhou
Subject: Re[2]: Problem using deployed Axis web services
Thanks a lot for the quick replies, Jinyuan.
I checked WSDL2Java for the JUnit option you mentioned, but couldn't
find it.
As for the URL I call the web service with, it's a bit different from
the one you provided. I tried the following:
http://localhost/WSTest/services/SayHello2?method=hello&in0=Bla
and
http://localhost/WSTest/services/SayHello2?method=hello&in=Bla
Neither of this works.
I have also pasted the client code below. This only returns a null
value.
Cheers,
Martin
> The generated code won't get Endpoint address right. Yours is
> http://localhost/WSTest/services/SayHello2.
> See if the following code or something simailar can help:
> call.setTargetEndpointAddress( new
> java.net.URL("http://localhost/WSTest/services/SayHello2";)
import javax.xml.rpc.ParameterMode;
import org.apache.axis.Constants;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
public class TestClient
{
public static void main(String [] args)
{
try
{
String endpoint =
"http://localhost/WSTest/services/SayHello2";;
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress( new
java.net.URL(endpoint) );
call.setOperationName("hello");
call.addParameter( "in", Constants.XSD_STRING,
ParameterMode.IN );
call.setReturnType( Constants.XSD_STRING );
String ret = (String) call.invoke( new Object[]
{ "bla" } );
System.out.println("return: " + ret);
} catch (Exception e)
{
System.err.println(e.toString());
}
}
}
Re[2]: Problem using deployed Axis web services
Thanks a lot for the quick replies, Jinyuan.
I checked WSDL2Java for the JUnit option you mentioned, but couldn't
find it.
As for the URL I call the web service with, it's a bit different from
the one you provided. I tried the following:
http://localhost/WSTest/services/SayHello2?method=hello&in0=Bla
and
http://localhost/WSTest/services/SayHello2?method=hello&in=Bla
Neither of this works.
I have also pasted the client code below. This only returns a null
value.
Cheers,
Martin
> The generated code won't get Endpoint address right. Yours is
> http://localhost/WSTest/services/SayHello2.
> See if the following code or something simailar can help:
> call.setTargetEndpointAddress( new
> java.net.URL("http://localhost/WSTest/services/SayHello2";)
import javax.xml.rpc.ParameterMode;
import org.apache.axis.Constants;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
public class TestClient
{
public static void main(String [] args)
{
try
{
String endpoint =
"http://localhost/WSTest/services/SayHello2";;
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress( new
java.net.URL(endpoint) );
call.setOperationName("hello");
call.addParameter( "in", Constants.XSD_STRING,
ParameterMode.IN );
call.setReturnType( Constants.XSD_STRING );
String ret = (String) call.invoke( new Object[] { "bla"
} );
System.out.println("return: " + ret);
} catch (Exception e)
{
System.err.println(e.toString());
}
}
}
RE: (OT) Making WSDL pretty?
Jay, Thanks for the links, I'll take a look at them. Actually, I was looking for something that formats the WSDL so the datatype definition section resembles more a classical datatype definition. The graphical view of the Eclipse WSDL editor is a good example (a little tree view with pretty-looking boxes and arrows). Unfortunately it doesn't have a "print" option, or an "export to PDF" option. ... that I know of, of course! :-) Thanks, Hernan --- Jay Glanville <[EMAIL PROTECTED]> wrote: > If you want to change the indenting of the WSDL to > make it easier to > read, use something like HTML Tidy > (http://tidy.sf.net). It can handle > XML as input and output formats. > > If you want something to extract the > values > out of your WSDL and generate a set of HTML pages > for human-readable > consumption, do a Google on "wsdldoc". I think IBM > had such a tool in > it's "emerging tool kit". I believe that bluetetra > also has one > (http://www.bluetetra.com/). > > JDG > > > -Original Message- > > From: Hernan Bay Area Guy > [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 05, 2006 12:37 PM > > To: axis-user@ws.apache.org > > Subject: (OT) Making WSDL pretty? > > > > > > Hello, > > > > (Apologies for the semi-offtopic post...) > > > > Does anybody know of a tool that one can use to > > generate a human-readable version of a WSDL file? > > > > I am working on a little SOAP service to wrap > around a > > number-crunching engine (written in Perl and C). > The > > programmer of the engine is even less experienced > on > > WSDL than I am, so it would be useful to be able > to > > have a nicely formatted version of the service's > WSDL > > file so we can discuss the signatures of the > > operations, for example. > > > > So far the options I found were: > > > > - Print Screen's of the Eclipse WSDL editor > > > > - A little ad-hoc XML parser that I wrote from > some > > code samples from the 'Net (so far it generates > > Twiki-fied text that I can cut&paste to our Twiki) > > > > Obviously none of these options is too elegant, > and > > Google is not being much help here either :-( > > > > Is there an "official" tool for this type of job? > > > > Thanks in advance, > > > > Hernan > > > > > > __ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: Problem using deployed Axis web services
The generated code won't get Endpoint address right. Yours is
http://localhost/WSTest/services/SayHello2.
See if the following code or something simailar can help:
call.setTargetEndpointAddress( new
java.net.URL("http://localhost/WSTest/services/SayHello2";)
-Original Message-
From: Jinyuan Zhou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 10:57 AM
To: axis-user@ws.apache.org; Martin Wunderlich
Subject: RE: Problem using deployed Axis web services
I think wsdl2java has an option to create Junit test case. Try start from
there to write a client code. However
http://localhost/WSTest/services/SayHello2?in=bla does not send an http request
in the way web service expected.
It expect an soap message as content and content type like text/xml or
applicaton/xml.
-Original Message-
From: Martin Wunderlich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 10:42 AM
To: Jay Glanville
Subject: Problem using deployed Axis web services
Dear all,
my first posting here, so please bear with me, in case I should break any
unwritten rules.
I am currently trying to get my first web services up and running on Tomcat 5.
I created a simple Java class to return a String:
public class SayHello2
{
public String hello(String in)
{
return ("Hello, " + in);
}
}
>From this class I created the WSDL with Java2Wsdl. I created the deployment
>descriptor using Wsdl2Java and deployed the whole thing using the Axis
>AdminClient. Finally, I compiled the resulting classes from step 2 and copied
>them to the directory that corresponds to the package name.
The web service is listed together with the method in the list provided by
Axis. However, I can not access the method, neither entering the direct URL
(http://localhost/WSTest/services/SayHello2?in=bla), nor using the stub classes
generated by Axis, nor using a org.apache.axis.client.Call. I am quite lost.
Does anyone have any ideas what I could check? I've pasted the WSDL below, just
in case there's any hint in there. (I can access this wsdl alright with
http://localhost/WSTest/services/SayHello2?wsdl).
Cheers,
N.
http://xml.apache.org/xml-soap"; xmlns:impl="urn:testPackage"
xmlns:intf="urn:testPackage"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://localhost/WSTest/services/SayHello2"/>
--
--
Martin Wunderlich, M.A.
Translation/Localisation EN <-> DE
www.martinwunderlich.com
--
Free / open-source software for translation/localisation:
www.martinwunderlich.com/foss-links.html
--
Random aphorism:
"Es ist ein Wunder, dass Neugier die Schulbildung überlebt."
"It is a miracle that curiosity survives formal education."
- Albert Einstein
--
RE: Problem using deployed Axis web services
I think wsdl2java has an option to create Junit test case. Try start from
there to write a client code. However
http://localhost/WSTest/services/SayHello2?in=bla does not send an http request
in the way web service expected.
It expect an soap message as content and content type like text/xml or
applicaton/xml.
-Original Message-
From: Martin Wunderlich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 10:42 AM
To: Jay Glanville
Subject: Problem using deployed Axis web services
Dear all,
my first posting here, so please bear with me, in case I should break any
unwritten rules.
I am currently trying to get my first web services up and running on Tomcat 5.
I created a simple Java class to return a String:
public class SayHello2
{
public String hello(String in)
{
return ("Hello, " + in);
}
}
>From this class I created the WSDL with Java2Wsdl. I created the deployment
>descriptor using Wsdl2Java and deployed the whole thing using the Axis
>AdminClient. Finally, I compiled the resulting classes from step 2 and copied
>them to the directory that corresponds to the package name.
The web service is listed together with the method in the list provided by
Axis. However, I can not access the method, neither entering the direct URL
(http://localhost/WSTest/services/SayHello2?in=bla), nor using the stub classes
generated by Axis, nor using a org.apache.axis.client.Call. I am quite lost.
Does anyone have any ideas what I could check? I've pasted the WSDL below, just
in case there's any hint in there. (I can access this wsdl alright with
http://localhost/WSTest/services/SayHello2?wsdl).
Cheers,
N.
http://xml.apache.org/xml-soap"; xmlns:impl="urn:testPackage"
xmlns:intf="urn:testPackage"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://localhost/WSTest/services/SayHello2"/>
--
--
Martin Wunderlich, M.A.
Translation/Localisation EN <-> DE
www.martinwunderlich.com
--
Free / open-source software for translation/localisation:
www.martinwunderlich.com/foss-links.html
--
Random aphorism:
"Es ist ein Wunder, dass Neugier die Schulbildung überlebt."
"It is a miracle that curiosity survives formal education."
- Albert Einstein
--
Problem using deployed Axis web services
Dear all,
my first posting here, so please bear with me, in case I should break
any unwritten rules.
I am currently trying to get my first web services up and running on
Tomcat 5. I created a simple Java class to return a String:
public class SayHello2
{
public String hello(String in)
{
return ("Hello, " + in);
}
}
From this class I created the WSDL with Java2Wsdl. I created the deployment
descriptor using Wsdl2Java and deployed the whole thing using the Axis
AdminClient. Finally, I compiled the resulting classes from step 2 and copied
them to the directory that corresponds to the package name.
The web service is listed together with the method in the list provided by
Axis. However, I can not access the method, neither entering the direct URL
(http://localhost/WSTest/services/SayHello2?in=bla), nor using the stub classes
generated by Axis, nor using a org.apache.axis.client.Call. I am quite lost.
Does anyone have any ideas what I could check? I've pasted the WSDL below, just
in case there's any hint in there. (I can access this wsdl alright with
http://localhost/WSTest/services/SayHello2?wsdl).
Cheers,
N.
http://xml.apache.org/xml-soap"; xmlns:impl="urn:testPackage"
xmlns:intf="urn:testPackage"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:testPackage" use="encoded"/>
http://localhost/WSTest/services/SayHello2"/>
--
--
Martin Wunderlich, M.A.
Translation/Localisation EN <-> DE
www.martinwunderlich.com
--
Free / open-source software for translation/localisation:
www.martinwunderlich.com/foss-links.html
--
Random aphorism:
"Es ist ein Wunder, dass Neugier die Schulbildung überlebt."
"It is a miracle that curiosity survives formal education."
- Albert Einstein
--
RE: (OT) Making WSDL pretty?
If you want to change the indenting of the WSDL to make it easier to read, use something like HTML Tidy (http://tidy.sf.net). It can handle XML as input and output formats. If you want something to extract the values out of your WSDL and generate a set of HTML pages for human-readable consumption, do a Google on "wsdldoc". I think IBM had such a tool in it's "emerging tool kit". I believe that bluetetra also has one (http://www.bluetetra.com/). JDG > -Original Message- > From: Hernan Bay Area Guy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 05, 2006 12:37 PM > To: axis-user@ws.apache.org > Subject: (OT) Making WSDL pretty? > > > Hello, > > (Apologies for the semi-offtopic post...) > > Does anybody know of a tool that one can use to > generate a human-readable version of a WSDL file? > > I am working on a little SOAP service to wrap around a > number-crunching engine (written in Perl and C). The > programmer of the engine is even less experienced on > WSDL than I am, so it would be useful to be able to > have a nicely formatted version of the service's WSDL > file so we can discuss the signatures of the > operations, for example. > > So far the options I found were: > > - Print Screen's of the Eclipse WSDL editor > > - A little ad-hoc XML parser that I wrote from some > code samples from the 'Net (so far it generates > Twiki-fied text that I can cut&paste to our Twiki) > > Obviously none of these options is too elegant, and > Google is not being much help here either :-( > > Is there an "official" tool for this type of job? > > Thanks in advance, > > Hernan > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com >
Re: Order of SOAPHeader and SOAPBody
Hi, If you are using Axis2 you can use the Axis2 security module [1] to do this. Please see this simple how-to [2] document and try it out. Example: client's configured axis2.xml file - [3] the service's services.xml file - [4] Thanks, Ruchith [1] http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/wss4j/0_95/security-0.95.mar [2] http://ws.apache.org/axis2/0_95/security-module.html [3] https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test-resources/security/s1.client.axis2.xml [4] https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test-resources/security/s1.service.xml On 4/5/06, Daniel Destro <[EMAIL PROTECTED]> wrote: > Hi Xinjun, > > As I can see you are trying to add some Security to your Web Services, > right? > > Are you doing a User Authentication / Authorization using this > UsernameToken? > > I need to do that! > > How do add UsernameToken into to the SOAP request and how do u read / > validate UsernameToken from the SOAP request (server-side) ??? > > Thanks > Daniel >
AW: [Axis2-0.95] how to ectract SOAP fault information at client side?
Hi Eran, it was not considered to be a hint. It was a suggestion, since the todo was formulated as a question. Currently there is no possibility to extract the SOAP fault details (Code, SubCode, Detail, Reason) at client-side. That's why for me the answer to the todo-question is 'yes'. I set options.isExceptionToBeThrownOnSOAPFault to true (although as I saw it is the default value). But the returned exception consists only of a message string and not of all the fault details which were sent back to the client. Regards, Andreas Bobek. > -Ursprüngliche Nachricht- > Von: Eran Chinthaka [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 5. April 2006 18:09 > An: axis-user@ws.apache.org > Betreff: Re: [Axis2-0.95] how to ectract SOAP fault > information at client side? > > > Andreas Bobek wrote: > > Hi, > > > > > > > > In AxisFault(Throwable cause) only the message is extracted > from cause... > > > > There again is a todo item: > > "TODO: handle AxisFaults or SOAPFaultException > implementations differently?" > > > > YES ;-) > > Is this a hint or you wanna say sth else ? > > > > > Or is there another possibility to get the SOAP fault information? > > options.isExceptionToBeThrownOnSOAPFault(false) > > -- Chinthaka > >
Re: Order of SOAPHeader and SOAPBody
Hi Xinjun,As I can see you are trying to add some Security to your Web Services, right?Are you doing a User Authentication / Authorization using this UsernameToken?I need to do that!How do add UsernameToken into to the SOAP request and how do u read / validate UsernameToken from the SOAP request (server-side) ??? ThanksDaniel
(OT) Making WSDL pretty?
Hello, (Apologies for the semi-offtopic post...) Does anybody know of a tool that one can use to generate a human-readable version of a WSDL file? I am working on a little SOAP service to wrap around a number-crunching engine (written in Perl and C). The programmer of the engine is even less experienced on WSDL than I am, so it would be useful to be able to have a nicely formatted version of the service's WSDL file so we can discuss the signatures of the operations, for example. So far the options I found were: - Print Screen's of the Eclipse WSDL editor - A little ad-hoc XML parser that I wrote from some code samples from the 'Net (so far it generates Twiki-fied text that I can cut&paste to our Twiki) Obviously none of these options is too elegant, and Google is not being much help here either :-( Is there an "official" tool for this type of job? Thanks in advance, Hernan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Generating Web Service with Axis 1.3
Hi Chris,Thanks for your answer.But, IMO, tools should work for us as much as possible. I don´t want to write WSDD files myself, I want some tool to make that for me. Axis can do that, but still there is some job to be done. RegardsDanielOn 4/5/06, Chris Smith <[EMAIL PROTECTED]> wrote: Daniel Destro wrote:> Axis code generation process seems to be a little bit cumbersome,> because, first of all, I have to create the WSDL, then the> server-side classes are generated from the WSDL. It would be much > easier if we could do it with only one single step and it could also> use my original business class instead of make me add code to> delegate the calls from the XXXImpl class to the business class. If you already have both the WSDL and the implementation classes, then youdon't need to use WSDL2Java at all. Instead, you would just write a WSDDfile pointing to your existing WSDL and Java code. You would need to include type mappings in that file, potentially using bean serializers oreven custom serializers if your data classes are not beans. This will notbe a trivial process, since you need to match your existing code to the existing WSDL interface, and there may be problems on either side.WSDL2Java is meant to generate Java code, if it doesn't already exist... forexample, if you've built the interface specification first as a WSDL file and a set of related XSDs, and then you want to build an implementation fromthere.--www.designacourse.comThe Easiest Way To Train Anyone... Anywhere. Chris Smith - Lead Software Developer/Technical TrainerMindIQ Corporation
Re: [Axis2-0.95] how to ectract SOAP fault information at client side?
Andreas Bobek wrote: > Hi, > > > > In AxisFault(Throwable cause) only the message is extracted from cause... > > There again is a todo item: > "TODO: handle AxisFaults or SOAPFaultException implementations differently?" > > YES ;-) Is this a hint or you wanna say sth else ? > > Or is there another possibility to get the SOAP fault information? options.isExceptionToBeThrownOnSOAPFault(false) -- Chinthaka signature.asc Description: OpenPGP digital signature
Re: Order of SOAPHeader and SOAPBody
Hi Xinjun,
There was a known bug in SOAPEnvelope, which is the same pointed out
also. I fixed it and now you can add SOAPHeader now to SOAPEnvelope and
that will be added properly now.
-- Chinthaka
Xinjun Chen wrote:
> I found a walk-around.
>
> envelope.getBody().insertSiblingBefore(headerElm);
>
> This will add the header OMElement into the envelope. However, the
> Header added is only considered as a child element of envelope, not a
> SOAPHeader. Thus if I call envelope.getHeader(), I will get exception.
>
> Regards,
> Xinjun
>
> On 4/5/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
>> I am using the following function to add UsernameToken to my security
>> header. But the processed envelope get some problems.
>> 1. The Header is placed after the body. How can I insert SOAPHeader
>> before SOAPBody?
>> 2. The security header defines the xmlns:xsd and xmlns:xsi again,
>> which have already been defined in .
>>
>> Could you give me some advice on how to solve the above two problems?
>>
>> Attached:
>>
>> 1) The function used for adding username token to the envelope:
>>
>> public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
>> envelope) throws Exception {
>>Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
>>WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
>>if (token.isDigested()) {
>>builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
>>} else {
>>builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
>>}
>>
>>builder.build(domDoc, token.getUsername(), token.getPassword());
>>Element header = (Element)
>> (domDoc.getElementsByTagName("wsse:Security").item(0));
>>OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
>>SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
>>factory.createSOAPHeader(envelope);
>>envelope.getHeader().addChild(headerElm);
>> }
>>
>> 2): The original soap envelope:
>>
>> > xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>>
>> http://services/helloworld";>
>> Hello world!
>>
>>
>>
>>
>> 3): The processed soap envelope:
>>
>> > xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>>
>> http://services/helloworld";>
>> Hello world!
>>
>>
>> > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>> xinjun> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password
>>
>
signature.asc
Description: OpenPGP digital signature
RE: [Axis2] 0.95 Service and Client from WSDL - problems executing
Hi Sebastian, Looks like you are doing something similar to me. I've just deployed a skeleton service today built the same way with only minor problems (my own fault) along the way. It looks like your xmlbeans have been missed off the build path or are not where expected. Did you use the generated ant build.xml to build your archive? Regards, Ken -Original Message- From: Sebastian J. Schultheiss [mailto:[EMAIL PROTECTED] Sent: 05 April 2006 13:14 To: axis-user@ws.apache.org Subject: [Axis2] 0.95 Service and Client from WSDL - problems executing Hello, we have created a WSDL file (attached) to be used by an example web service that we would like to extend eventually. We used WSDL2Java to create the client and the service, with the xmlbeans Databinding. Maybe you can try to build it this way too and let us know if it should work in theory. After deploying the .aar in Axis2, we tried to connect to the server, but only got this exception report back. Please let us know if you need any additional information in order to tell us more. ... Thanks a lot for your time! -- Sebastian
Axis2 & DIME Attachments
Hello, I've implemented an axis 1.1 client towards a gSoapService which returns DIME attachments; looks like it is working well! I've re-implemented the client using OMElement of Axis2 , but the ServiceClient is not able to create correctly the SOAPMessage, it throws the following error: "org.apache.axis2.AxisFault: Invalid UTF-8 middle " In the axis1.1 into the Call object I've set _call.setProperty(Call.ATTACHMENT_ENCAPSULATION_FORMAT, Call.ATTACHMENT_ENCAPSULATION_FORMAT_DIME); I believe this could be the cause since I cannot find how to do the same in Axis2. Any suggestions, kind regards Alessandro
Re: Generating Web Service with Axis 1.3
Daniel Destro wrote: Axis code generation process seems to be a little bit cumbersome, because, first of all, I have to create the WSDL, then the server-side classes are generated from the WSDL. It would be much easier if we could do it with only one single step and it could also use my original business class instead of make me add code to delegate the calls from the XXXImpl class to the business class. If you already have both the WSDL and the implementation classes, then you don't need to use WSDL2Java at all. Instead, you would just write a WSDD file pointing to your existing WSDL and Java code. You would need to include type mappings in that file, potentially using bean serializers or even custom serializers if your data classes are not beans. This will not be a trivial process, since you need to match your existing code to the existing WSDL interface, and there may be problems on either side. WSDL2Java is meant to generate Java code, if it doesn't already exist... for example, if you've built the interface specification first as a WSDL file and a set of related XSDs, and then you want to build an implementation from there. -- www.designacourse.com The Easiest Way To Train Anyone... Anywhere. Chris Smith - Lead Software Developer/Technical Trainer MindIQ Corporation
wsrf webservice client
Hi, I'm trying to create a WSRF webservice client, and since AXIS2 supports ws-addressing it might be a good choice. Does anyone have experience creating WSRF webservices client using AXIS2? Asaf Lahav VP R&D, Prima Grid LTD. Cellular: 972-54-4717955 Phone: 972-3-6540255 Fax: 972-3-6540254
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL
This has been fixed in latest SVN :)
-- dims
On 4/5/06, Andreas Bobek <[EMAIL PROTECTED]> wrote:
>
> Both, code generation and deploying of WSDL 1.1 / SOAP 1.2 services is now
> working in 0.95 :-)
>
> BUT,
>
> if I use AxisService.printWSDL(OutputStream out, String requestIP)
> I get a WSDL with SOAP 1.1 binding!
> Furthermore, if there is no SOAP 1.1 namespace declared in the original WSDL
> file, I get an exception
>
> WSDLException: faultCode=OTHER_ERROR: Can't find prefix for
> 'http://schemas.xmlsoap.org/wsdl/soap/'. Namespace prefixes must be set on
> the Definition object using the addNamespace(...) method.:
> at
> org.apache.axis2.description.AxisService.printUsingWSDLDefinition(AxisServic
> e.java:497)
> at
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:427)
> ...
>
>
> I suppose this a limitation of WSDL4J ?
>
> Just for info,
> Andreas Bobek.
>
>
>
> > -Ursprüngliche Nachricht-
> > Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> > Gesendet: Dienstag, 28. März 2006 06:16
> > An: axis-user@ws.apache.org
> > Betreff: Re: [Axis2-0.94] service deploy fails when ports
> > bound to SOAP 1.2 in WSDL
> >
> > oh I didnt know that :(
> >
> > Davanum Srinivas wrote:
> >
> > >Deepal,
> > >
> > >Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
> > >
> > >-- dims
> > >
> > >On 3/26/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>yes , thats a bug in Axis2 and we will fix that before 1.0.
> > >>
> > >>Andreas Bobek wrote:
> > >>
> > >>
> > >>
> > >>>Hi,
> > >>>
> > >>>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> > >>>
> > >>>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; instead of
> > >>>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/";
> > >>>
> > >>>Code generation works well.
> > >>>Deploying with bindings to SOAP 1.1 works well, too.
> > >>>
> > >>>But when bind to SOAP 1.2 I get follow exception:
> > >>>
> > >>>org.apache.wsdl.impl.WSDLProcessingException: no port with soap
> > >>>binding found
> > >>> at
> > >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> > ce(AxisSer
> > >>>viceBui
> > >>>lder.java:219)
> > >>> at
> > >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> > ce(AxisSer
> > >>>viceBui
> > >>>lder.java:127)
> > >>> at
> > >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> > rocessWSDL
> > >>>File(Ar
> > >>>chiveReader.java:267)
> > >>> at
> > >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> > rocessWSDL
> > >>>s(Archi
> > >>>veReader.java:333)
> > >>> at
> > >>>org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deplo
> > ymentEngine.java:
> > >>>383)
> > >>>..
> > >>>
> > >>>which I think means WSDL-SOAP 1.2 is not known.
> > >>>
> > >>>Debugging inside AxisServiceBuilder:
> > >>>javax.wsdl.extensions.UnknownExtensibilityElement
> > >>>UnknownExtensibilityElement
> > >>>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> > >>>
> > >>>Is this a limitation in Axis up to now?
> > >>>
> > >>>Thank you, Andreas Bobek.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>--
> > >>Thanks,
> > >>Deepal
> > >>
> > >>~Future is Open~
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >--
> > >Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal
> > ...
> > ~Future is Open~
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
axis2 - asynchronous messaging
Hi all, I would like to use the callback features, but my architecture uses a piece of software acting like a "broker" to handle incoming requests: A B Client --> Broker -> Node satisfying the request (N) | | | | |C (reply) | <--- Can the node N use the callback to return the result to the client? If no, what should I do? Could fireAndForget() messages (A, B and C) be fine (in case together with options like relatesTo, messageId, etc.)? Any suggestions are welcome. Thanks in advance, Michele
AW: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL
Both, code generation and deploying of WSDL 1.1 / SOAP 1.2 services is now
working in 0.95 :-)
BUT,
if I use AxisService.printWSDL(OutputStream out, String requestIP)
I get a WSDL with SOAP 1.1 binding!
Furthermore, if there is no SOAP 1.1 namespace declared in the original WSDL
file, I get an exception
WSDLException: faultCode=OTHER_ERROR: Can't find prefix for
'http://schemas.xmlsoap.org/wsdl/soap/'. Namespace prefixes must be set on
the Definition object using the addNamespace(...) method.:
at
org.apache.axis2.description.AxisService.printUsingWSDLDefinition(AxisServic
e.java:497)
at
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:427)
...
I suppose this a limitation of WSDL4J ?
Just for info,
Andreas Bobek.
> -Ursprüngliche Nachricht-
> Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 28. März 2006 06:16
> An: axis-user@ws.apache.org
> Betreff: Re: [Axis2-0.94] service deploy fails when ports
> bound to SOAP 1.2 in WSDL
>
> oh I didnt know that :(
>
> Davanum Srinivas wrote:
>
> >Deepal,
> >
> >Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
> >
> >-- dims
> >
> >On 3/26/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> >
> >
> >>yes , thats a bug in Axis2 and we will fix that before 1.0.
> >>
> >>Andreas Bobek wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> >>>
> >>>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; instead of
> >>>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/";
> >>>
> >>>Code generation works well.
> >>>Deploying with bindings to SOAP 1.1 works well, too.
> >>>
> >>>But when bind to SOAP 1.2 I get follow exception:
> >>>
> >>>org.apache.wsdl.impl.WSDLProcessingException: no port with soap
> >>>binding found
> >>> at
> >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> ce(AxisSer
> >>>viceBui
> >>>lder.java:219)
> >>> at
> >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> ce(AxisSer
> >>>viceBui
> >>>lder.java:127)
> >>> at
> >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> rocessWSDL
> >>>File(Ar
> >>>chiveReader.java:267)
> >>> at
> >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> rocessWSDL
> >>>s(Archi
> >>>veReader.java:333)
> >>> at
> >>>org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deplo
> ymentEngine.java:
> >>>383)
> >>>..
> >>>
> >>>which I think means WSDL-SOAP 1.2 is not known.
> >>>
> >>>Debugging inside AxisServiceBuilder:
> >>>javax.wsdl.extensions.UnknownExtensibilityElement
> >>>UnknownExtensibilityElement
> >>>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> >>>
> >>>Is this a limitation in Axis up to now?
> >>>
> >>>Thank you, Andreas Bobek.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>--
> >>Thanks,
> >>Deepal
> >>
> >>~Future is Open~
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >--
> >Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ...
> ~Future is Open~
>
>
Question about Apache Axis 1.2 Solaris 10 support
Title: Question about Apache Axis 1.2 Solaris 10 support Hi All, I'm from R&D of Nortel. We have been using Apache Axis 1.2 in our product. Now we are planning to upgrade our platform from Solaris 9 to Solaris 10. So I am not sure if there will be any impact on Apache Axis 1.2? In other words, is Apache Axis 1.2 fully compatible with Solaris 10? Could anyone who knows this information please help me out with my question? Or could you please tell me from where I can find this information? Thank you in advance for your time and great support. Best Regards, Hui Xie
Generating Web Service with Axis 1.3
Hi all,Using the option "-s" and "-S true" with WSDL2Java tool, it creates the server-side and Skeleton classes. A XXXImpl class is created and I always have to modify it to add code to delegate the calls to my original business class. I have not tested yet, but as I can see, if I omit "-S true" (skeleton), Axis call directly the XXXImpl class. Is that right? What is the difference between this option and the skeleton option?Axis code generation process seems to be a little bit cumbersome, because, first of all, I have to create the WSDL, then the server-side classes are generated from the WSDL. It would be much easier if we could do it with only one single step and it could also use my original business class instead of make me add code to delegate the calls from the XXXImpl class to the business class. Another point, when my method returns a custom type (i.e.: ProductInfo), it creates a new similiar class (same name), just to add some code related to SOAP into it. But if this ProductInfo class is not in the same directory as my business class is, Axis overwrites it. Why is that? Axis is cool, but sometimes are confusing or make me work more. I´d expect this kind of tool do the whole code generation, ready to be deployed, the same way Oracle JDeveloper works.ThanksDaniel
[Axis2] 0.95 Service and Client from WSDL - problems executing
Hello, we have created a WSDL file (attached) to be used by an example web service that we would like to extend eventually. We used WSDL2Java to create the client and the service, with the xmlbeans Databinding. Maybe you can try to build it this way too and let us know if it should work in theory. After deploying the .aar in Axis2, we tried to connect to the server, but only got this exception report back. Please let us know if you need any additional information in order to tell us more. root cause java.lang.NoClassDefFoundError axis2.apache.org.xsd.PredictEpitopesRequestDocument$Factory.parse(PredictEpitopesRequestDocument.java:150) svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.fromOM(SVMHCServicePortMessageReceiverInOut.java:142) svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.invokeBusinessLogic(SVMHCServicePortMessageReceiverInOut.java:51) org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:408) org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:288) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160) javax.servlet.http.HttpServlet.service(HttpServlet.java:709) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs.Apache Tomcat/5.5.15 at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:310) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:205) ... 5 more Caused by: org.apache.axis2.AxisFault: Transport error 500 . Error Message is Apache Tomcat/5.5.15 - Error report HTTP Status 500 - type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception javax.servlet.ServletException: Servlet execution threw an exception root cause java.lang.NoClassDefFoundError axis2.apache.org.xsd.PredictEpitopesRequestDocument$Factory.parse(PredictEpitopesRequestDocument.java:150) svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.fromOM(SVMHCServicePortMessageReceiverInOut.java:142) svmhc.complex.service.SVMHCServicePortMessageReceiverInOut.invokeBusinessLogic(SVMHCServicePortMessageReceiverInOut.java:51) org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:408) org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:288) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160) javax.servlet.http.HttpServlet.service(HttpServlet.java:709) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs.Apache Tomcat/5.5.15 at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:131) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:304) ... 6 more Thanks a lot for your time! -- Sebastian http://org.apache.axis2/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://org.apache.axis2/"; targetNamespace="http://org.apache.axis2/";> http://www.w3.org/2001/XMLSchema"; xmlns:ns1="http://org.apache.axis2/xsd"; targetNamespace="http://org.apache.axis2/xsd"; elementFormDefault="unqualified" attributeFormDefault="unqualified"> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://www.org.apache.axis2"/> http://www.org.apache.axis2"/> http://localhost/axis2/services/SVMHCServiceComplex:localhost/axis2/services/SVMHCServiceComplex"; />
Re: communication between java and other programs
You may use Sockets for communicatoion or even Web Services, with Axis.On 4/5/06, Christian Wilmes <[EMAIL PROTECTED] > wrote:Hi,I've got a Java progrom written. Now I want that my program is abel to react on actions happens in another program (p.e. c++, c#). That program isn'twritten up to know. It have to be also possible that the c++/c#-programreact on actions in my Java program.In a Forum i've red that will be possible with axis. Is that right? Better using axis2 or axis1.x? Is there anywhere a tutorialhow to do something like that?Please excuse my bad english.Best RegardsChristian--Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
communication between java and other programs
Hi, I've got a Java progrom written. Now I want that my program is abel to react on actions happens in another program (p.e. c++, c#). That program isn't written up to know. It have to be also possible that the c++/c#-program react on actions in my Java program. In a Forum i've red that will be possible with axis. Is that right? Better using axis2 or axis1.x? Is there anywhere a tutorial how to do something like that? Please excuse my bad english. Best Regards Christian -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
[Axis2-0.95] how to ectract SOAP fault information at client side?
Hi,
I successfully created a customized SOAP 1.2 fault message at server-side
(Code, SubCode, Reason and Detail). However, up to now I can't find a way to
ectract these information at client-side. Here I use a ServiceClient which
throws (as expected) an AxisFault when invoking the sendReceive method.
I retraced the invocations in the source code and found out following calls:
ServiceClient.sendReceive(OMElement elem)
in ServiceClient.sendReceive(QName operation, OMElement elem) =>
mepClient.execute(true); in line 445
in OutInAxisOperationClient.execute(boolean block) => throw new
AxisFault(ex); in line 276
In AxisFault(Throwable cause) only the message is extracted from cause...
There again is a todo item:
"TODO: handle AxisFaults or SOAPFaultException implementations differently?"
YES ;-)
Or is there another possibility to get the SOAP fault information?
I'd like to have something like this:
catch(AxisFault f){
f.getCode
f.getSubCode(s)
...
}
or at least an accessible response MessageContext.
Thank you, Andreas Bobek.
The was not specified
Hi, I am in the process of creating WSDL from Java through *Java2WSDL*. My command line script is - java org.apache.axis.wsdl.Java2WSDL -n "https://tools-dev.cisco.com/cws/ces/services/CESService" -l "CESService" -m "createCollaborationSpace" -i "com.cisco.es.livelink.LiveLinkConfigEngine_CCO" I have specified -i option for class-of-portType but still I am getting following exception. Please guide me or give any pointer. The was not specified.Java2WSDL emitterUsage: java org.apache.axis.wsdl.Java2WSDL [options] class-of-portTypeOptions: -h, --help print this message and exit -I, --input input WSDL filename -o, --output output WSDL filename -l, --location service location url -P, --portTypeName portType name (obtained from class-of-portType if not specif ied) -b, --bindingName binding name (--servicePortName value + "SOAPBinding" if not specified) -S, --serviceElementName service element name (defaults to --servicePortName value + "Service") -s, --servicePortName service port name (obtained from --location if not specified ) -n, --namespace target namespace -p, --PkgtoNS = package=namespace, name value pairs -m, --methods space or comma separated list of methods to export -a, --all look for allowed methods in inherited class -w, --outputWsdlMode output WSDL mode: All, Interface, Implementation -L, --locationImport location of interface wsdl -N, --namespaceImpl target namespace for implementation wsdl -O, --outputImpl output Implementation WSDL filename, setting this causes --o utputWsdlMode to be ignored -i, --implClass optional class that contains implementation of methods in cl ass-of-portType. The debug information in the class is used to obtain the method parameter names, which are used to set the WSDL part names. -x, --exclude space or comma separated list of methods not to export -c, --stopClasses space or comma separated list of class names which will stop inheritance search if --all switch is given -T, --typeMappingVersion indicate 1.1 or 1.2. The default is 1.1 (SOAP 1.1 JAX-RPC c ompliant 1.2 indicates SOAP 1.1 encoded.) -A, --soapAction value of the operations soapAction field. Values are DEFAULT , OPERATION or NONE. OPERATION forces soapAction to the name of the operation. DEFAULT causes the soapAction to be set according to the operations meta data (usually ""). NONE fo rces the soapAction to "". The default is DEFAULT. -y, --style The style of binding in the WSDL, either DOCUMENT, RPC, or W RAPPED. -u, --use The use of items in the binding, either LITERAL or ENCODED -e, --extraClasses A space or comma separated list of class names to be added t o the type section. -C, --importSchema A file or URL to an XML Schema that should be physically imp orted into the generated WSDLDetails: portType element name= <--portTypeName value> OR binding element name= <--bindingName value> OR <--servicePortName value>SoapBinding service element name= <--serviceElementName value> OR <--portTypeName value>Service port element name= <--servicePortName value> address location = <--location value> --- CCWLL Services Dev Group | Zensar-Cisco ODC | (D) +91 (020) 5609 8245 Don't worry about the world coming to an end today. It's already tomorrow in Australia
Re: Order of SOAPHeader and SOAPBody
I found a walk-around.
envelope.getBody().insertSiblingBefore(headerElm);
This will add the header OMElement into the envelope. However, the
Header added is only considered as a child element of envelope, not a
SOAPHeader. Thus if I call envelope.getHeader(), I will get exception.
Regards,
Xinjun
On 4/5/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
> I am using the following function to add UsernameToken to my security
> header. But the processed envelope get some problems.
> 1. The Header is placed after the body. How can I insert SOAPHeader
> before SOAPBody?
> 2. The security header defines the xmlns:xsd and xmlns:xsi again,
> which have already been defined in .
>
> Could you give me some advice on how to solve the above two problems?
>
> Attached:
>
> 1) The function used for adding username token to the envelope:
>
> public void addUsernameTokens(UsernameToken token, final SOAPEnvelope
> envelope) throws Exception {
>Document domDoc = Axis2Util.getDocumentFromSOAPEnvelope(envelope);
>WSSAddUsernameToken builder = new WSSAddUsernameToken("", false);
>if (token.isDigested()) {
>builder.setPasswordType(WSConstants.PASSWORD_DIGEST);
>} else {
>builder.setPasswordTyp(WSConstants.PASSWORD_TEXT);
>}
>
>builder.build(domDoc, token.getUsername(), token.getPassword());
>Element header = (Element)
> (domDoc.getElementsByTagName("wsse:Security").item(0));
>OMElement headerElm = (OMElement) (Axis2Util.toOM(header));
>SOAPFactory factory = Axis2Util.getSOAPFactory(envelope);
>factory.createSOAPHeader(envelope);
>envelope.getHeader().addChild(headerElm);
> }
>
> 2): The original soap envelope:
>
> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> http://services/helloworld";>
> Hello world!
>
>
>
>
> 3): The processed soap envelope:
>
> xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> http://services/helloworld";>
> Hello world!
>
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> xinjun Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password
>
[Axis2] current svn snapshot build failure
Hi, trying to build axis2 from todays svn update failed with following error: BUILD FAILED File.. C:\Administrator\.maven\cache\maven-multi project-plugin-1.3.1\plugin.jelly Element... maven:reactor Line.. 217 Column 9 Unable to obtain goal [multiproject:install-callback] -- C:\Administrator\.maven\cache\maven-test-plugin-1.6.2\plugin.jelly:181:54: There were test failures. Total time: 6 minutes 11 seconds Finished at: Wed Apr 05 10:50:17 CEST 2006 Is this a known Problem or did I anything wrong? Thanks Ted ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
