RE: [Axis2] JMS tutorial? [signed]

[Michael Laccetti [c]]

> I run axis2 in a few web applications - hibernate, struts, 
> spring etc. Its just a matter of having the modules and 
> services directory, along with axis2.xml, under your apps 
> WEB-INF. You'll also need to add the relevant parts from the 
> axis2.war web.xml into your apps web.xml .  If you want to 
> use the axis2 jsp's - like listServices - you need those 
> jsp's at the root of your apps war. 

I have tried that, but when I try to access the Axis2 servlet I get a null
pointer - specifically about a string index out of bounds [-1].  I can
provide the full exception if it will help.

> 
> This is something that could be documented - lets see what we 
> can come up with. In the mean time, feel free to ask. 
> 
> The JMS transport is something I haven't tried yet - but 
> would like to. I mostly use JMS as OpenJMS in tomcat, or with 
> JBoss. In the meantime, if someone has the JMS transport 
> working in a app and would like to document it
> - file a jira and if its good it will probably be accepted. 

I'm trying to build both synchronous and asynchronous services, hence the
need for JMS.  I'm using ActiveMQ with Geronimo, and that part has been
validated to work.  I guess the most important question is to that of
configuration - do I need to hardcode it in axis2.xml, can it be done in
another configuration file, or programmatically?

Mike



-- 
- [ SECURITY NOTICE ] -
To: [EMAIL PROTECTED]
For your security, [EMAIL PROTECTED]
digitally signed this message on 11 February 2006 at 01:25:03 UTC.
Verify this digital signature at http://www.ciphire.com/verify.
 [ CIPHIRE DIGITAL SIGNATURE ] 
Q2lwaGlyZSBTaWcuAjhheGlzLXVzZXJAd3MuYXBhY2hlLm9yZwBtaWNoYWVsQHMy
Zy1saW1pdGVkLmNvbQBlbWFpbCBib2R5ADoEAAB8AHwB7zztQzoEAAAW
AwACAAIAAgAghdiaB1RL1GJ5P/MlSIrm9xUfngywhKly/Ob9WJCPAegBAJNtVYWa
ZKKcHYtuC7hZmjSFW3h/Fm4Z8P/F+IkY81kzf7ywtK7BuEBzn9V+Fji2HGAnVt8x
HiALSTiO37fPvbVVU2lnRW5k
-- [ END DIGITAL SIGNATURE ] --

RE: [Axis2] JMS tutorial? [signed]

[Michael Laccetti [c]]

> Hi Michael,
> 
> Nice to hear that. But we have lot more to come and 
> stabilize, so I don't think this is the perfect time for 
> someone to come in to conclusion abt Axis2. We are getting 
> more and more better, with the valuable comments and 
> feedbacks from the users here.
> 
> -- Chinthaka

Well, I would have used Axis, given its more mature nature, but I have had
some serious difficulties in deploying it/using it with Geronimo.  Besides,
I'm up for getting a jump on technology.  :)

Mike



-- 
- [ SECURITY NOTICE ] -
To: [EMAIL PROTECTED]
For your security, [EMAIL PROTECTED]
digitally signed this message on 11 February 2006 at 01:20:58 UTC.
Verify this digital signature at http://www.ciphire.com/verify.
 [ CIPHIRE DIGITAL SIGNATURE ] 
Q2lwaGlyZSBTaWcuAjhheGlzLXVzZXJAd3MuYXBhY2hlLm9yZwBtaWNoYWVsQHMy
Zy1saW1pdGVkLmNvbQBlbWFpbCBib2R5AI4BAAB8AHwB+jvtQ44BAABx
AwACAAIAAgAghdiaB1RL1GJ5P/MlSIrm9xUfngywhKly/Ob9WJCPAegBAJNtVYWa
ZKKcHYtuC7hZmjSFW3h/Fm4Z8P/F+IkY81kzVrLoLJhTGgdm+pMoGIDIBWaL+/lf
ow8o2ZumCceaiSvzU2lnRW5k
-- [ END DIGITAL SIGNATURE ] --

Re: Arbitrary Authenitcation Types (based on SOAP Headers)

[Scott McCoy]

That is the client answer, sure.Virtually what I was looking for, but I wanted the server answer.!I want to use wsdl2java to build a service I will deploy with axis, rather than connect to.  I am trying to figure out the most pragmatic fasion for building a "component", that I could stuff (possibly, in the ) that checks the headers, and *stops* the request from getting to the main handler under the instance that my authentication failed.
I really wanted to, if possible, use document or wrapped style services, rather than messages style services, also.Thanks!    Scott S. McCoyOn 2/10/06, 
Rave, Mark <[EMAIL PROTECTED]> wrote:
I don't know if this is what you are asking but it can't hurt to offer it.  I used WSDL2Java to generate the stubs and I also had to have authentication information in the SOAP header, this is how I did it but it might not be the best way:
  SomethingService service = new SomethingServiceLocator();  Something svc = service.getSomethingSOAPPort();  SomethingSoapBindingStub stub = (SomethingSoapBindingStub)svc;  SOAPHeaderElement she = new SOAPHeaderElement("namespace", "AuthInfo");
  SOAPElement ut = she.addChildElement("UserToken");  SOAPElement un = ut.addChildElement("UserName");  un.addTextNode("username");  SOAPElement pw = ut.addChildElement("Password");
  pw.addTextNode("password");  stub.setHeader(she);When I make the call something like this is generated:
http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:m="namespace">
usernamepassword
..Hope this helps.-Original Message-From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Scott McCoySent: Friday, February 10, 2006 2:06 PMTo: axis-user@ws.apache.orgSubject: Re: Arbitrary Authenitcation Types (based on SOAP Headers)
I didn't get a response to this, so I thought I'd re-post it.I just want a handler, before my handler, to get some values from the header and have the ability to stop the request.How does that happen?
On 2/8/06, Scott McCoy <[EMAIL PROTECTED]> wrote:Hello All,I have a specification that demands I use a SOAP Header element for credential verification, and from a technical perspective it needs to be highly reusable, with a technical requirement that it preceeds and stops processing of the SOAP Body.  I've found what seems to be just the ticket, which is simply adding a component via the < requestFlow/> element in WSDL or WSDD...But the problem I'm having is that I'm having difficulty finding documentation on doing this.
Essentially, I have the following (mock) request envelope:

Nevermind the details of the SOAP Body, handlers for this are easily generatable by WSDL2Java, but how do I deal with the SOAP Header in a respectible and logical fasion (Axis 
1.3) ?Thanks,Scott S. McCoy_This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Espanol - Deutsch - Nederlands - Francais - Italiano - Norsk - Svenska: www.cardinalhealth.com/legal/email

Re: [axis2] skip tests while building

[Davanum Srinivas]

"maven -Dmaven.test.skip=true"

On 2/10/06, Noah Levitt <[EMAIL PROTECTED]> wrote:
> How do you build axis2 without going through all the tests?
>
> Noah
>


--
Davanum Srinivas : http://wso2.com/blogs/

[axis2] skip tests while building

[Noah Levitt]

How do you build axis2 without going through all the tests?

Noah

Re: A request for comments on some wanted features

[robert]

Em Sexta 10 Fevereiro 2006 12:23, o Rodrigo Ruiz escreveu:
> Hi all,
>
> I have some web services with the following requirements:
>
> - Ability to receive very large attachments (several GB length).
> - Security provided by WSS4J

Message level security on attachments of several GB length ? Web services are  
not the right technology for this, IMHO. Consider sftp or something of the 
like. 

HTH,
robert 
http://www.braziloutsource.com/

Re: SOAP messages format

[Anne Thomas Manes]

You need to add one more level of wrapping so that your echoed values are returned in a single return bean:          
          
              
      On 2/10/06, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:H ...I made a new testing WSDL file (see attached file) and generated a WS using Axis from Eclipse. The test resulted in that I can send a SOAP message with two parameters, I can see the server receives them, but the response contains only the first parameter of the two expected.
Any ideas/suggestions?RegardsMensaje originalDe: [EMAIL PROTECTED]
Recibido: 09/02/2006 23:07Para: , Asunto: Re: SOAP messages formatWhen using document/literal, your message may have at most one message part. 
If you would like to design a programming interface that supports multiple input parameters, then you must design the WSDL to follow the WRAPPED convention. See my blog entry for more information: 
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html.AnneOn 2/9/06, 
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.


Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.

RE: Arbitrary Authenitcation Types (based on SOAP Headers)

[Rave, Mark]

I don't know if this is what you are asking but it can't hurt to offer it.  I 
used WSDL2Java to generate the stubs and I also had to have authentication 
information in the SOAP header, this is how I did it but it might not be the 
best way:

  SomethingService service = new SomethingServiceLocator();

  Something svc = service.getSomethingSOAPPort();

  SomethingSoapBindingStub stub = (SomethingSoapBindingStub)svc;
  SOAPHeaderElement she = new SOAPHeaderElement("namespace", "AuthInfo");
  SOAPElement ut = she.addChildElement("UserToken");
  SOAPElement un = ut.addChildElement("UserName");
  un.addTextNode("username");
  SOAPElement pw = ut.addChildElement("Password");
  pw.addTextNode("password");
  stub.setHeader(she);

When I make the call something like this is generated:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:m="namespace">



username
password



..


Hope this helps.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott McCoy
Sent: Friday, February 10, 2006 2:06 PM
To: axis-user@ws.apache.org
Subject: Re: Arbitrary Authenitcation Types (based on SOAP Headers)


I didn't get a response to this, so I thought I'd re-post it.

I just want a handler, before my handler, to get some values from the header 
and have the ability to stop the request.

How does that happen?


On 2/8/06, Scott McCoy <[EMAIL PROTECTED]> wrote:
Hello All,
I have a specification that demands I use a SOAP Header element for 
credential verification, and from a technical perspective it needs to be highly 
reusable, with a technical requirement that it preceeds and stops processing of 
the SOAP Body.  I've found what seems to be just the ticket, which is simply 
adding a component via the < requestFlow/> element in WSDL or WSDD...But the 
problem I'm having is that I'm having difficulty finding documentation on doing 
this. 

Essentially, I have the following (mock) request envelope:



 




 





Nevermind the details of the SOAP Body, handlers for this are easily 
generatable by WSDL2Java, but how do I deal with the SOAP Header in a 
respectible and logical fasion (Axis 1.3) ?


Thanks,
Scott S. McCoy

_

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the email by you is prohibited.

Espanol - Deutsch - Nederlands - Francais - Italiano - Norsk - Svenska: 
www.cardinalhealth.com/legal/email

Re: Arbitrary Authenitcation Types (based on SOAP Headers)

[Scott McCoy]

I didn't get a response to this, so I thought I'd re-post it.I just want a handler, before my handler, to get some values from the header and have the ability to stop the request.How does that happen?
On 2/8/06, Scott McCoy <[EMAIL PROTECTED]> wrote:
Hello All,    I have a specification that demands I use a SOAP Header element for credential verification, and from a technical perspective it needs to be highly reusable, with a technical requirement that it preceeds and stops processing of the SOAP Body.  I've found what seems to be just the ticket, which is simply adding a component via the <
requestFlow/> element in WSDL or WSDD...But the problem I'm having is that I'm having difficulty finding documentation on doing this.
    Essentially, I have the following (mock) request envelope:            
                    
            Nevermind the details of the SOAP Body, handlers for this are easily generatable by WSDL2Java, but how do I deal with the SOAP Header in a respectible and logical fasion (Axis 
1.3) ?    Thanks,    Scott S. McCoy

[Axis2-0.94] how to send faults?

[Andreas Bobek]

Hi all,

I want to send WS* specific faults to clients (e.g. 
wsa:DestinationUnreachable in case of WS-Addressing or 
wse:FilteringNotSupported in case of WS-Eventing).

Have I to use AxisEngine.createFaultMessageContext() or have I to use a 
specific mechanism. I can't find a related documentation.

Thanks, Andreas Bobek.

Re: SOAP messages format

[[EMAIL PROTECTED]]

H ...I made a new testing WSDL file (see attached file) and generated a WS using Axis from Eclipse. The test resulted in that I can send a SOAP message with two parameters, I can see the server receives them, but the response contains only the first parameter of the two expected.Any ideas/suggestions?RegardsMensaje originalDe: [EMAIL PROTECTED]Recibido: 09/02/2006 23:07Para: , <[EMAIL PROTECTED]>Asunto: Re: SOAP messages formatWhen using document/literal, your message may have at most one message part. If you would like to design a programming interface that supports multiple input parameters, then you must design the WSDL to follow the WRAPPED convention. See my blog entry for more information: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html.AnneOn 2/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.


Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.




http://localhost:8080/echosrvc.wsdl";
   xmlns:tns="http://localhost:8080/echosrvc.wsdl";
  xmlns:xsd1="http://localhost:8080/echosrvc.xsd";
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
   xmlns="http://schemas.xmlsoap.org/wsdl/";>

http://localhost:8080/echosrvc.xsd";
   xmlns="http://www.w3.org/2001/XMLSchema"; 
  xmlns:xsd1="http://localhost:8080/echosrvc.xsd";>


  

  
  

  
 

  

  
  

  
 


















http://schemas.xmlsoap.org/soap/http"/>

https://localhost:8080/echoBin"/>











https://localhost:8080/echosrvc"/>

Re: Help! - WebSphere 5.1.1 issue with attachments

[Mukesh Kumar Maniraj]

Sorry,
I meant responseMsg.countAttachments(), not esponseMsg.addAttachmentPart(),

-Mukesh
On 2/9/06, Pradeep Reddy <[EMAIL PROTECTED]> wrote:
Mukesh!Thanks for the response.If i dont call responseMsg.addAttachmentPart(),
i wont be able to add the attachment to the response. Is there any
other way to add attachmentpart to the response message to work around
this 1.2 bug?Could you point me to that 1.2 bug? This works on a weblogic server but not websphere.Regards,Pradeep
On 2/9/06, Mukesh Kumar Maniraj
 <[EMAIL PROTECTED]> wrote:

Pradeep,
You could try using this code,
 MessageContext msgContext =
MessageContext.getCurrentContext(); 

   
if (msgContext != null)
{  

 
    
msgContext.getService().setSendType(Attachments.SEND_TYPE_MIME);
   
Message responseMsg =
msgContext.getResponseMessage(); 
 
responseMsg.getAttachmentsImpl().setSendType(Attachments.SEND_TYPE_MIME);
   
AttachmentPart attachmentPart = new AttachmentPart(new DataHandler(new
   
FileDataSource()));
}

As note that do not use ,
responseMsg.addAttachmentPart() method, in Axis 1.2 a call to this
method results in the body of the message being skipped.


-MukeshOn 2/8/06, Pradeep Reddy
 <[EMAIL PROTECTED]
> wrote:Hi all,I am having trouble accessing the Response Message on WebSphere 
5.1.1.I am trying to send an attachment from server to the client. I add it to the response message using this familiar code snippet.
MessageContext msgContext = MessageContext.getCurrentContext();Message msg = msgContext.getResponseMessage();



msg.getAttachmentsImpl().setSendType(Attachments.SEND_TYPE_MIME);   
           AttachmentPart part = new AttachmentPart(new DataHandler(new ArtifactDataSource(
ais.getInfo().getName(),ais.getInputStream(),ais.getContentType().toString(;//ArtifactDataSource is a custom implementation of datasourcepart.setContentId



(ais.getInfo().getName());msg.addAttachmentPart(part);msg.saveChanges();



this code returns an attachment on weblogic 8.1. On WebSphere
5.1.1, i am getting back a response with no xml message in it. I just
get back these headers with no xml message or the attachment.
HTTP/1.1 200 OKDate: Wed, 08 Feb 2006 20:48:43 GMTServer: IBM_HTTP_SERVER/1.3.28.1  Apache/1.3.28 (Unix)Connection: closeContent-Type: multipart/related; type="text/xml"; start=""; boundary=
1446154572.1139431723394.JavaMail.test.blutoTo debug, I retained only these calls:
MessageContext msgContext = MessageContext.getCurrentContext();
Message msg = msgContext.getResponseMessage();This returned an empty soap message.HTTP/1.1 200 OKDate: Wed, 08 Feb 2006 22:00:48 GMTServer: IBM_HTTP_SERVER/1.3.28.1  Apache/1.3.28 (Unix)
Connection: closeContent-Type: text/xml; charset=utf-8


http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="


http://www.w3.org/2001/XMLSchema-instance">
So when i call
getResponseMessage(), its going through a seperate path and giving me a
brand new response. I am using axis 1.2 RC2.Any help on what i can do to work around this problem would be greatly appreciated. 
Thanks,Pradeep

RE: custom SoapFault in Axis2

[donnerdrummel2000-mailing]

Hi Magnus,

The problem you probably have is that your fault is a
SOAP 1.1 fault. The Axis2 AxisFault is mapped to
SOAP1.2 Fault wich is a superset of the 1.1 one. To
create a 'real' SOAP1.1 Fault have a look at
org.apache.axis2.soap.impl.dom.soap11.SOAP11FaultImpl

Ted
--- Magnus Olsson <[EMAIL PROTECTED]>
schrieb:

> Hi,
> 
> is it possible to create the following SOAP Fault in
> axis2?
> 
> 
xmlns:soap="">
> 
>   
>   
xmlns:c="">
> 
>c:InvalidInsuranceId 
>Illegal insurance
> number 
> 
> 
xmlns:foo="">
> 
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  
> 
>
>   
>  
> 
> I tried with the following service, which didn't
> succeed.
> 
> public void pingF(OMElement element) throws
> AxisFault
> {
> AxisFault fault = new AxisFault("Illegal
> insurance number");
> QName code = new
>
QName("http://www.company.se/faultcodes/2005-12-01/";,
> "InvalidInsuranceId", "c");
> fault.setFaultCode(code);
> 
> OMFactory factory =
> OMAbstractFactory.getOMFactory();  
> OMNamespace ns =
>
factory.createOMNamespace("http://schemas.foo.org/foo/2005-12-01/","ssek";);
> OMElement root =
> factory.createOMElement("FaultData",ns);
> 
> OMElement elt1 =
> factory.createOMElement("faultingMessage", null);
> root.addChild(elt1);
> 
> fault.setDetail(root);
> throw fault;
> }
> 
> 
> regards,
> 
> Magnus
> 







___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: [1.3] How to pass the authentication information, i.e. username, to the service?

[Paul Spencer]

Rodrigo,
You had a type-o in the method name. The correct method is:
  MessageContext.getCurrentContext().getUsername();

This is exactly what I was need :)

Thank you,

Paul Spencer

Rodrigo Ruiz wrote:

Hi Paul,

The method is:

MessageContext.getCurrentContext.getUserName();

Regards,
Rodrigo Ruiz

Paul Spencer wrote:

I have a webservice the requires authentication.  My service need 
access  to the username for auditing purposes.  I am using the 
WSDLJava utility to generate the source.


How can my service get access to the authenticated username?

Paul Spencer

Axis2: NullPointer in Eclipse code generation

[Damien Evans]

Hi,

 

I’m doing some MTOM stuff, and am starting to
experiment with Axis2 (v0.9.4) as the toolkit.  So far I like everything I
see.

 

When I tried using the Eclipse plugin to generate code for either
of the attached WSDL files from whitemesa.net, I get a NullPointerException
dialog box.  Generating code from WSDL files from other web services (that
do not deal with binary content) works just fine.

 

I have a couple of questions…  First off, does
anyone have any insights as to this failure?  Second, is there a way that
I can turn on logging in the Eclipse code generation plugin?

 

Any assistance would be appreciated.

 

-- Damien

 








mtom-test-doc1.wsdl
Description: mtom-test-doc1.wsdl


mtom-test-cr.wsdl
Description: mtom-test-cr.wsdl

custom SoapFault in Axis2

[Magnus Olsson]

Hi,

is it possible to create the following SOAP Fault in axis2?

http://schemas.xmlsoap.org/soap/envelope/>"> 
  
  http://www.company.se/faultcodes/2005-12-01/>"> 
   c:InvalidInsuranceId 
   Illegal insurance number 

http://schemas.foo.org/foo/2005-12-01/>"> 
  
  
  
  
  
  
  
  
  
  
  
  
 

   
  
 

I tried with the following service, which didn't succeed.

public void pingF(OMElement element) throws AxisFault
{
AxisFault fault = new AxisFault("Illegal insurance number");
QName code = new QName("http://www.company.se/faultcodes/2005-12-01/";, 
"InvalidInsuranceId", "c");
fault.setFaultCode(code);

OMFactory factory = OMAbstractFactory.getOMFactory();  
OMNamespace ns = 
factory.createOMNamespace("http://schemas.foo.org/foo/2005-12-01/","ssek";);
OMElement root = factory.createOMElement("FaultData",ns);

OMElement elt1 = factory.createOMElement("faultingMessage", null);
root.addChild(elt1);

fault.setDetail(root);
throw fault;
}


regards,

Magnus

content-transfer-encoding: base64

[Argo]

Hi all,

Is it possible specify to Content-Transfer-Encoding:base64 for ws
attachment with Axis 1.3?

I have a generated client class with method with DataHandler.
DataHandler DataSource is simple ByteArrayDataSource. Bytes are encoded
as base64. 


-- Argo

Re: [Axis2] JMS tutorial?

[robert]

> I do accept that we lag in documentations, coz we are concentrating more
> and more on improving Axis2. Iksrazal (ohh, sorry Lazarski ;-) ) and
> Chatra and helping with us to improve our documentations these days.
>

I run axis2 in a few web applications - hibernate, struts, spring etc. Its 
just a matter of having the modules and services directory, along with 
axis2.xml, under your apps WEB-INF. You'll also need to add the relevant 
parts from the axis2.war web.xml into your apps web.xml .  If you want to use 
the axis2 jsp's - like listServices - you need those jsp's at the root of 
your apps war. 

This is something that could be documented - lets see what we can come up 
with. In the mean time, feel free to ask. 

The JMS transport is something I haven't tried yet - but would like to. I 
mostly use JMS as OpenJMS in tomcat, or with JBoss. In the meantime, if 
someone has the JMS transport working in a app and would like to document it 
- file a jira and if its good it will probably be accepted. 

HTH,
robert
http://www.braziloutsource.com/

Em Sexta 10 Fevereiro 2006 03:16, o Eran Chinthaka escreveu:
> Hi Michael,
>
> Michael Laccetti wrote:
> >On another note, is there any documentation on how to integrate Axis2 with
> >an existing web application?
>
> If you want to integrate Axis2, look in to the implementation in
> AxisServlet.doPost.
>
> I do accept that we lag in documentations, coz we are concentrating more
> and more on improving Axis2. Iksrazal (ohh, sorry Lazarski ;-) ) and
> Chatra and helping with us to improve our documentations these days.
>
> But if you have problems, you are always welcome to ask them here.
>
> -- Chinthaka
>
> >Thanks,
> >
> >Michael
> >
> >-Original Message-
> >From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> >Sent: February 9, 2006 11:04 PM
> >To: axis-user@ws.apache.org
> >Subject: Re: [Axis2] JMS tutorial?
> >
> >See
> >http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/java/modules/int
> >eg ration/test/org/apache/axis2/jms/
> >it has a unit test that starts the jms listener and runs a test.
> >activemq has to be started, you need to tweak entries in axis2.xml as
> >well.
> >
> >thanks,
> >dims
> >
> >On 2/9/06, Michael Laccetti <[EMAIL PROTECTED]> wrote:
> >>I've been doing some research into the best WS framework/implementation,
> >
> >and
> >
> >>Axis2 comes up as a winner.  Originally I chose Axis, but it didn't play
> >
> >too
> >
> >>nicely with Geronimo.  Now, the real question:  is there any
> >> documentation on using the JMS transport?  I've seen the SMTP one, which
> >> is well done,
> >
> >but
> >
> >>doesn't quite work for me.  I know that there is a global configuration
> >
> >for
> >
> >>the transport in the axis2.xml file; can it be configured elsewhere?  Or
> >
> >can
> >
> >>the configuration be done programmatically as well?
> >>
> >>
> >>
> >>Thanks,
> >>
> >>
> >>
> >>Michael
> >
> >--
> >Davanum Srinivas : http://wso2.com/blogs/

-- 

Re: [1.3] How to pass the authentication information, i.e. username, to the service?

[Rodrigo Ruiz]

Hi Paul,

The method is:

MessageContext.getCurrentContext.getUserName();

Regards,
Rodrigo Ruiz

Paul Spencer wrote:

I have a webservice the requires authentication.  My service need 
access  to the username for auditing purposes.  I am using the 
WSDLJava utility to generate the source.


How can my service get access to the authenticated username?

Paul Spencer

[1.3] How to pass the authentication information, i.e. username, to the service?

[Paul Spencer]

I have a webservice the requires authentication.  My service need access 
 to the username for auditing purposes.  I am using the WSDLJava 
utility to generate the source.


How can my service get access to the authenticated username?

Paul Spencer

A request for comments on some wanted features

[Rodrigo Ruiz]

Hi all,

I have some web services with the following requirements:

- Ability to receive very large attachments (several GB length).
- Security provided by WSS4J

I am currently using Axis 1.2, and planning to use Axis 2 once a
stable release is published.


Playing with these services, I have noticed some security
limitations/vulnerabilities in Axis, related to the processing of
attachments.

Having a web service installed on a Tomcat server, I have successfully
performed the following attacks with very simple client applications:

- I have sent a request with a 10MB file repeated 1024 times with
 different names. This leads to 10Gb of temp files created in the
 "attachments" directory. They are correctly deleted after the
 request is processed, but in the meantime, they are wasting hard
 disk.

- I have performed the previous test in 200 threads, and caused the
 server disk space to be reduced to 0, and my server to stop
 responding.

For these simple DoS attacks, the client application did not need to
send valid authentication data. WS-Security handlers do not start
processing until all attachments have been received.


I have also noticed that sending a large file with MIME attachments
takes almost twice the time needed to receive one.
I guess the cause is that Axis attachment implementation uses
DataHandlers for accessing the file, and DataHandlers do not have a
method for getting the file length. This means that the whole file
must be read twice: the first time to get its length, and the second
one to actually send it.
MIME attachments are the only ones supported by the "Attachments
Profile 1.0", and they require each part length to be specified before
sending the actual part data.


Said this, I would like to know the opinion of other users in this
forum about including some features in Axis 2 (or prepare Axis 2 so
it is possible to implement them):

- Restrict the number of accepted attachments in a per-method basis.
 If a request arrives with more attachments than allowed, we can
 directly reject it by closing the connection.

- Invoke some kind of handler, or filter, just after receiving the
 SOAP headers, and before starting to process the message body.
 This way, the request can be early rejected if it does not have
 valid credentials.

- Create a "KnownLengthDataSource" with a method "getLength(), so
 when used, the attachments implementation will be able to get the
 data length without a slow read.

- Alternative implementations of the server attachments support. In
 this case, the idea would be to have a "lazy" implementation that
 would allow the engine to invoke the service method *before*
 attachments are actually read.
 I would love such an implementation, as it would allow me to
 implement an "attachment forwarding" service without writing and
 reading (twice) a temporary file.


Any comment would be greatly appreciated

Regards,
Rodrigo Ruiz

Re: Element undefined in WSDL2Java

[Chris Mannion]

Thanks Anne,
 
I was hoping I was doing something stupid but I 
just couldn't see it.
Chris MannionIT Junction020 8452 4274

  - Original Message - 
  From: 
  Anne Thomas 
  Manes 
  To: axis-user@ws.apache.org 
  Sent: Friday, February 10, 2006 1:30 
  PM
  Subject: Re: Element undefined in 
  WSDL2Java
  Your namespace declaration for the xsd schema is wrong.It 
  should be:
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"Anne
  On 2/10/06, Chris 
  Mannion < 
  [EMAIL PROTECTED]> wrote:
  Hi 
AllI'm trying to use the WSDL2Java tool to generate both client 
stubs and server-side skeletons from a wsdl file that I have written and 
I'm getting aconfusing error.  The error message 
isjava.io.IOException: Element {urn:formTypeWs}Transactions is 
referenced butnot 
defined.atorg.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:670)My 
full wsdl file is attached below.  I know the error is 
specificallygenerated from the point where I use the Transactions 
element in the 'getFormTypesOut' message (because by commenting this 
part of the file out,I can negate the error and hit errors from later in 
the file) and it seemsto be claiming that Transactions hasn't been 
defined when, as you can see I have defined it within the schema at the 
top of the file.  There may be amistake in how I've defined 
Transactions but what makes it really confusingis that the 
FormTypesRequest element is defined in exaclty the same way and doesn't 
cause an error (minor differences such as Transactions containing 
amax="unbounded" flag aren't the cause as the error still occurs 
withmax="1"), so I'm a little stumped as to what the object is 
about.  Any suggestions would be very much 
appreciated.  ThanksChris MannionIT Junction020 
8452 4274xmlns:impl="urn:formTypeWs"xmlns:intf="urn:formTypeWs"xmlns:apachesoap="http://xml.apache.org/xml-soap"xmlns:wsdlsoap=" 
http://schemas.xmlsoap.org/wsdl/soap/"xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"xmlns:xsd=" 
http://www.w3c.org/2001/XMLSchema"xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">       
  type="xsd:string"/>type="xsd:date"/> 
   
    
   type="xsd:string"/> 
   
 
 
          
type="impl:TransactionTypes">  transport=" 
http://schemas.xml.org/soap/http"/>    
       
   
     binding="impl:TransactionTypesSoapBinding">   
http://server:8081/services/formTypeWs 
"/>  

Re: Element undefined in WSDL2Java

[Anne Thomas Manes]

Your namespace declaration for the xsd schema is wrong.It should be:xmlns:xsd="http://www.w3.org/2001/XMLSchema"
AnneOn 2/10/06, Chris Mannion <
[EMAIL PROTECTED]> wrote:Hi AllI'm trying to use the WSDL2Java tool to generate both client stubs and
server-side skeletons from a wsdl file that I have written and I'm getting aconfusing error.  The error message isjava.io.IOException: Element {urn:formTypeWs}Transactions is referenced butnot defined.
atorg.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:670)My full wsdl file is attached below.  I know the error is specificallygenerated from the point where I use the Transactions element in the
'getFormTypesOut' message (because by commenting this part of the file out,I can negate the error and hit errors from later in the file) and it seemsto be claiming that Transactions hasn't been defined when, as you can see I
have defined it within the schema at the top of the file.  There may be amistake in how I've defined Transactions but what makes it really confusingis that the FormTypesRequest element is defined in exaclty the same way and
doesn't cause an error (minor differences such as Transactions containing amax="unbounded" flag aren't the cause as the error still occurs withmax="1"), so I'm a little stumped as to what the object is about.  Any
suggestions would be very much appreciated.  ThanksChris MannionIT Junction020 8452 4274 xmlns:impl="urn:formTypeWs" xmlns:intf="urn:formTypeWs" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:wsdlsoap="
http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="
http://www.w3c.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">   
      type="xsd:string"/>type="xsd:date"/>        
  type="xsd:string"/>    
       
     
      
  type="impl:TransactionTypes">  transport="
http://schemas.xml.org/soap/http"/>    
             
  binding="impl:TransactionTypesSoapBinding">   http://server:8081/services/formTypeWs
"/>   

Element undefined in WSDL2Java

[Chris Mannion]

Hi All

I'm trying to use the WSDL2Java tool to generate both client stubs and
server-side skeletons from a wsdl file that I have written and I'm getting a
confusing error.  The error message is
java.io.IOException: Element {urn:formTypeWs}Transactions is referenced but
not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.j
ava:670)

My full wsdl file is attached below.  I know the error is specifically
generated from the point where I use the Transactions element in the
'getFormTypesOut' message (because by commenting this part of the file out,
I can negate the error and hit errors from later in the file) and it seems
to be claiming that Transactions hasn't been defined when, as you can see I
have defined it within the schema at the top of the file.  There may be a
mistake in how I've defined Transactions but what makes it really confusing
is that the FormTypesRequest element is defined in exaclty the same way and
doesn't cause an error (minor differences such as Transactions containing a
max="unbounded" flag aren't the cause as the error still occurs with
max="1"), so I'm a little stumped as to what the object is about.  Any
suggestions would be very much appreciated.  Thanks

Chris Mannion
IT Junction
020 8452 4274


http://xml.apache.org/xml-soap";
 xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
 xmlns:xsd="http://www.w3c.org/2001/XMLSchema";
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
 
  
   

 
  
  
  
 

   

   

 
  
 

   
  
 

 
  
 

 
  
 

 
  
   
   
  
 

 
  http://schemas.xml.org/soap/http"/>
  
   
   

   
   

   
  
 

 
  
   http://server:8081/services/formTypeWs"/>
  
 

problem sending attachments with Axis 1.2 when using non Axis clients

[Frederik Colardyn]

Hello,
 
We've got a problem when using Axis 1.2 as 
a webservice to send attachments to non Axis clients.
 
Our wsdl defines the binary attachment as 
xsd:hexBinary, which translates to  when deployed and asking the wsdl from the 
webservice.
 
The problem is the soap envelope it sends 
back to the client, it mentions xsi:type="ns1:Source" xmlns="" xmlns:ns1="http://xml.apache.org/xml-soap"/, which gives an 
error on the client:
 failed to deserialize 
xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure 
for xml type ['http://xml.apache.org/xml-soap']:Source
 
Axis seems to enforce a apache.org specific 
decoding for the attachment, which is not cross platform. I think the webservice 
would work just fine if it just didn't supply any xsi:type nor xmlns, but i 
don't know if Axis can be configured not to. trying to set sendXsiTypes 
to false in the wsdd didn't work.
 
 
Anyone having success sending attachments 
from a Axis 1.2 server to a non Axis client? Upgrading to Axis 2 is not an 
option.
 
Client: weblogic
 
Source WSDL: 
  
 
Generated WSDL when asking ?WSDL from Axis 
servlet:
  
 
Returned evenvelope by Axis 
1.2:
http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
     http://telenet.be/idtv/portal/usagelogging/">   
   http://xml.apache.org/xml-soap"/>  
   
 

<2FBC23FC4668CB8099EC63E11378CF34>attachment...
Frederik Colardyn
J2EE developer / Technical Consultant
www.cronos.be
www.hwbot.org