Re: Axis2 and JBoss 4.0 and Asynchronous Webservices

2006-03-13 Thread Brian Shields 

Tony,
Thats great, Ill get stuck into it. Thats pretty much what I assumed 
would be the way to do it. The only problem I can forsee having is 
having a SessionBean as the Web Service endpoint rather than a POJO. It 
should still be straight forward though and a simple JNDI lookup should 
connect the SessionBean to the EntityBean application in the background. 
Once again my experience with J2EE is limited and JBoss even more so, so 
it will be a case of feeling round in the dark for a while.

Thanks for the pointers though,
Brian.

Antony Wilson wrote:


Brian,

I really did not do anything special for deploying Axis2 to JBoss 
4.0.3. I unzipped the Axis2 war into the JBoss "deploy" directory and 
deployed the Axis2 webservices to the Axis2 "services" directory (as 
described in the Axis2 docs). By default, JBoss 4.0.2+ uses tomcat's 
classloading implementation vice their own unified/flat classloader. 
This approach isolates the classes/libraries per web application...so 
you avoid the library/jar conflicts that can sometime arise from using 
a unified classloader (e.g., the default JBoss classloader). So as I 
understand it...it is basically like running on Axis2 on standalone 
Tomcat. If you are using an earlier version of JBoss 4.0.1sp1 or 
lower...you should modify a few lines in home>\server\default\deploy\jbossweb-tomcat50.sar\META-INF\jboss-service.xml 
as follows:



false
−

false

This will properly isolate the Axis2 classes and has worked for me. 
From this point on...I just followed the instructions is in the Axis2 
docs for deploying webservices.


As mentioned in my earlier email...I have had problems with the 
EchoNonBlockingDualClient example...at this point I'm reasonably 
convinced that it is due to the fact that the webservice is not 
asynchronous. After reading a few earlier threads, I believe I have to 
extend the AbstractInOutAsyncMessageReceiver to create an asynchronous 
service. Not that much fun:-( I really wish there was an example or 
default implementation in the Axis2 distro. But I guess it's a small 
price to pay for the power/flexibility of Axis2;-)


Hope this helps,
Tony

Brian Shields wrote:

Thats a bit disappointing, maybe i was a bit naive thinking it would 
be straight forward. I need to have a serious think how i will 
progress. I am not willing to stop using axis2, ive too much time 
invested now and everything set up the way i need it for my own 
research. Unfortunately i also have committments on a project that 
uses JBoss 4.0. How much of WS-Security is implemented in the most 
recent stable release of JBoss? How straightforward is it to 
implement security on existing (Web) SessionBeans? I particularly 
like the modular approach of axis2 which completely abstracts the 
security layer from the developer of the endpoint and vice versa.
Any other help, pointers etc (maybe a url to a walk thru of deploying 
axis2 on JBoss 4 ; ) ) greatly appreciated.

Regards,
Brian.

robert lazarski wrote:

I haven't mixed JBoss and Axis2 together yet - but I know both 
reasonably well independently. I've used JBoss and EJB with JWSDP alot.


Internally JBoss 4.0.x comes with Axis 1.x - though strangely their 
docs and examples favor JWSDP. Furthermore, It tends to be more 
natural to use a Statelful session bean with web services.


There are Handlers that are part of Java itself and can be used with 
Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a 
lot. However, axis2 does not currently support JAX-RPC. JBoss is 
pretty wired into JAX-RPC.


So to make Web Services function with JBoss and EJB you'll need to 
edit and create a lot of files, and using axis2 in jboss and ejb is 
a bit bleeding edge. Don't get me wrong - it'd be a cool project and 
yes I think it can be done. But if you don't know Jboss or axis2 
well, there are not going to be a lot of docs to help you. My 
personal experience on the jboss lists have not been good - they 
strongly encourage paid support.


Another option I would strongly consider is just use hibernate if 
you have a choice - instead of EJB. It'll be a lot simpler config. 
Sounds like your commited to EJB though.


If you still decide to use axis2 with jboss, look at the jboss guide 
chapter 12. Look at their files:


webservices.xml
ejb-jar.xml
jboss.xml

Know what config-*.xml does

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

On 3/13/06, * Brian Shields* < [EMAIL PROTECTED] 
> wrote:


Hi All,
I am currently using Axis2 and WSS4J as a test environment for some
secure services. I want to now deploy these secure services on a JBoss
4.0 AS. My experience with JBoss is limited, this work has been
carried
out by another member of the group. We have an ejb application which
uses a stateless session bean to implement the web services interface.
At the moment this is all deployed using JBossWS. Has anybody deployed
Axis2 as a service within JBoss 4.0? Is it straightforward. There
is the
option of changing t

Re: Axis2 and JBoss 4.0 and Asynchronous Webservices

2006-03-13 Thread Antony Wilson 

Brian,

I really did not do anything special for deploying Axis2 to JBoss 4.0.3. 
I unzipped the Axis2 war into the JBoss "deploy" directory and deployed 
the Axis2 webservices to the Axis2 "services" directory (as described in 
the Axis2 docs). By default, JBoss 4.0.2+ uses tomcat's classloading 
implementation vice their own unified/flat classloader. This approach 
isolates the classes/libraries per web application...so you avoid the 
library/jar conflicts that can sometime arise from using a unified 
classloader (e.g., the default JBoss classloader). So as I understand 
it...it is basically like running on Axis2 on standalone Tomcat. If you 
are using an earlier version of JBoss 4.0.1sp1 or lower...you should 
modify a few lines in home>\server\default\deploy\jbossweb-tomcat50.sar\META-INF\jboss-service.xml 
as follows:



false
−

false

This will properly isolate the Axis2 classes and has worked for me. From 
this point on...I just followed the instructions is in the Axis2 docs 
for deploying webservices.


As mentioned in my earlier email...I have had problems with the 
EchoNonBlockingDualClient example...at this point I'm reasonably 
convinced that it is due to the fact that the webservice is not 
asynchronous. After reading a few earlier threads, I believe I have to 
extend the AbstractInOutAsyncMessageReceiver to create an asynchronous 
service. Not that much fun:-( I really wish there was an example or 
default implementation in the Axis2 distro. But I guess it's a small 
price to pay for the power/flexibility of Axis2;-)


Hope this helps,
Tony

Brian Shields wrote:

Thats a bit disappointing, maybe i was a bit naive thinking it would 
be straight forward. I need to have a serious think how i will 
progress. I am not willing to stop using axis2, ive too much time 
invested now and everything set up the way i need it for my own 
research. Unfortunately i also have committments on a project that 
uses JBoss 4.0. How much of WS-Security is implemented in the most 
recent stable release of JBoss? How straightforward is it to implement 
security on existing (Web) SessionBeans? I particularly like the 
modular approach of axis2 which completely abstracts the security 
layer from the developer of the endpoint and vice versa.
Any other help, pointers etc (maybe a url to a walk thru of deploying 
axis2 on JBoss 4 ; ) ) greatly appreciated.

Regards,
Brian.

robert lazarski wrote:

I haven't mixed JBoss and Axis2 together yet - but I know both 
reasonably well independently. I've used JBoss and EJB with JWSDP alot.


Internally JBoss 4.0.x comes with Axis 1.x - though strangely their 
docs and examples favor JWSDP. Furthermore, It tends to be more 
natural to use a Statelful session bean with web services.


There are Handlers that are part of Java itself and can be used with 
Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a 
lot. However, axis2 does not currently support JAX-RPC. JBoss is 
pretty wired into JAX-RPC.


So to make Web Services function with JBoss and EJB you'll need to 
edit and create a lot of files, and using axis2 in jboss and ejb is a 
bit bleeding edge. Don't get me wrong - it'd be a cool project and 
yes I think it can be done. But if you don't know Jboss or axis2 
well, there are not going to be a lot of docs to help you. My 
personal experience on the jboss lists have not been good - they 
strongly encourage paid support.


Another option I would strongly consider is just use hibernate if you 
have a choice - instead of EJB. It'll be a lot simpler config. Sounds 
like your commited to EJB though.


If you still decide to use axis2 with jboss, look at the jboss guide 
chapter 12. Look at their files:


webservices.xml
ejb-jar.xml
jboss.xml

Know what config-*.xml does

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

On 3/13/06, * Brian Shields* < [EMAIL PROTECTED] 
> wrote:


Hi All,
I am currently using Axis2 and WSS4J as a test environment for some
secure services. I want to now deploy these secure services on a JBoss
4.0 AS. My experience with JBoss is limited, this work has been
carried
out by another member of the group. We have an ejb application which
uses a stateless session bean to implement the web services interface.
At the moment this is all deployed using JBossWS. Has anybody deployed
Axis2 as a service within JBoss 4.0? Is it straightforward. There
is the
option of changing to JBoss WS, but I am using other Axis2
features like
handlers that I would rather not drop.
Does anybody have any suggestions as to how I could go about this
transition? Any documentation on the web where this has been tried?
Regards,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

Re: Setting URN in EndpointReference class

2006-03-13 Thread Sricharan Anand 
Hi Eran,Thanks for your reply. To answer your question on why my EPR has 2 addresses, please see this blog(the .Net webservice I am communicating with is using a similar architecture):http://www.dynamic-cast.com/mt-archives/50.htmlAs you can infer from the above article/blog, the first URI below becomes the EndpointReference.Address, the second URI is the EndpointReference.Via.So i couldn't figure out how to set this in the EndpointReference class since the constructor only takes 1 string arg. Is the Via some kind of Reference property?Related to the Malformed URL exception below, you said  - So if you wanna include something like"urn:MyApplicationAPI", as your endpoint then you need to register a transport which supports urn scheme How do i do this(register transport for urn)?Thanks for all your help.Regds,SricharanEran Chinthaka <[EMAIL PROTECTED]><
 /b>
 wrote: Hi Sricharan,Let me explain how EndpointReference class (EPR) works with Axis2.It models the same EPR concept in WS-Addressing EndpointReference. Soyou can set only one address to that. I exactly can not understand whyyou need to have two addresses, for the same EPR, one for internal andone for external.Having set the address property of EPR, Axis2 uses that address toselect the proper transport to send the SOAP message to the endpoing.For example;EndpointReference toEPR = newEndpointReference("http://my-service-endpoint.org");options.setTo(toEPR);internally we search for a transport which supports the scheme of theURL. i.e. HTTP in this case. So if you wanna include somethinglike"urn:MyApplicationAPI", as your endpoint then you need to register atransport which supports urn scheme. Tha
 ts why
 you are getting theexception.If you just ignore the internal address (what do u mean by internaladdress), then this should work.EndpointReference epr = new EndpointReference(""https://myservices.test.com/wsetestharness/myapplicationapi.asmx"");_messageContext.setTo(new EndpointReference(uri1.toString()));HTH.ChinthakaSricharan Anand wrote:>How do we set an URN as part of EndpointReference class?>>Here is my problem:>I am writing a Axis2 client to consume a remote .Net based Webservice(running WSE 2.0)>>The endpoint of the service is something like this(taken from a C# client code which is working)>>'Me.Url = "">Me.Destination = New Microsoft.Web.Services2.Addressing.EndpointReference(New Uri("urn:MyApplicationAPI"), New
 Uri("https://myservices.test.com/wsetestharness/myapplicationapi.asmx"))>>The 1st URI(urn:MyApplicationAPI) in above code is the internal address of our webservice. The 2nd Uri in the above code is the external address of our WebService.>>I want to construct the same EndpointReference using the Axis2 classes. I have tried doing the following:>Uri uri1 = new URI("urn:MyApplicationAPI");>Uri uri2 = new URI("https://myservices.test.com/wsetestharness/myapplicationapi.asmx");>EndpointReference epr = new EndpointReference(uri1.toString()+uri2.toString());>_messageContext.setTo(new EndpointReference(uri1.toString()));>This does not work and i get the following exception: >org.apache.axis2.AxisFault: unknown protocol: urn; nested exception is: >java.net.MalformedURLException: unknown protocol: urn; nested exception is: >org.apache.axis2.AxisFault: unknown protocol: urn; nested exception is: 
 >
java.net.MalformedURLException: unknown protocol: urn>at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:245)>at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:449)  >->Relax. Yahoo! Mail virus scanning helps detect nasty viruses!>  >->Yahoo! Mail>Bring photos to life! New PhotoMail  makes sharing a breeze. >  >
		Relax. Yahoo! Mail 
virus scanning helps detect nasty viruses!
		Brings words and photos together (easily) with 
PhotoMail  - it's free and works with Yahoo! Mail.

WSDL2Java and SimpleType doing *strange* things.

2006-03-13 Thread Scott McCoy 
When given the declaration...              
            
      WSDL2Java generates a Bean class that has a get_value (named after the internal _value a less complex type declaration has?) and set_value method for accessing the value, but when deployed Axis outputs a wsdl that has an *attribute* named _value for the keyword complexType.
When given
        
            
    
WSDL2Java generates exactly what I expect, but then when deployed axis returns a wsdl that contains:

    
      
    
    
    
    
  
    
How do I get WSDL2Java to do what I want?  Heh.  I'd prefer to my markup to look like:The Keyword
But having an attribute named value containing the keyword is a close runner up in perferred behaviors.Thanks,    Scott S. McCoy

Bean deserialisation problem

2006-03-13 Thread Rui Alberto L. Goncalves 
Hi all!

Axis version: 1.3
tomcat: 5.5.7
jdk:1.5.0_02

I'm having problems while trying to deserialize a java bean using
complex types.
Bean:
MyBean.java
 - Operation : doSomething( InputDataObject )

InputDataObject has the following properties : - AuthenticationData auth
   - String a
   - boolean b
where the AuthenticationData has properties:
   String  c
   String  d
   String  e

The problem is: the value of attributes c, d and e are ALWAYS the value
of the first attribute that appears in the WSDL complexType definition.

sample:


 
 
 



attributes d and e will always have the same value as c

I'm sending in attach the deploy.wsdd that I'm using.

Hope that someone could give me a hint...

Thanks for any help you could provide.

Rui

RE: Too Many Parameters, failing during complie

2006-03-13 Thread Alick Buckley 



Hi,
 
I have 
not counted them, but Java does have limits.

Java limits the number of 
method parameters to 255 or 254 or less if parmeters are of type long for 
double.
This limits the number of member variables that an Axis 
generated bean class can support to 254, because a constructor is created using 
all the member variables.
The 255 method parameter limit is for static methods and 254 for 
non static methods
==
http://forum.java.sun.com/thread.jspa?threadID=606589&messageID=3315840

http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html#88659
Limitations
fields: 65,535 (does not include inherited fields)
methods: 65,535 (does not include inherited methods)
method parameters: 255 (each long or double counts as two parameters) 
===
 
 

  -Original Message-From: Jerry DuVal 
  [mailto:[EMAIL PROTECTED]Sent: Tuesday, 14 March 2006 4:25 
  AMTo: axis-user@ws.apache.orgSubject: Too Many 
  Parameters, failing during complie
  
  I'm using the wsdl2Java ant task, 
  compiling the classes using javac.  During compile I get an 
  error
   
  compile:
      [mkdir] Created 
  dir: C:\Documents and 
  Settings\jduval\Desktop\java\build\cl
  sses
      [javac] 
  Compiling 286 source files to C:\Documents and 
  Settings\jduval\Desk
  op\java\build\classes
      [javac] 
  C:\Documents and 
  Settings\jduval\Desktop\java\build\gensrc\com\pace
  020\epace\object\JobComponent.java:578: 
  too many parameters
      
  [javac] public 
  JobComponent(
      
  [javac]    
  ^
      [javac] 1 
  error
   
   
  The constructor for this class 
  does have a lot of parameters.  Any help would be appreciated and thanks 
  ahead of time.
   
   

Re: Axis2 and JBoss 4.0

2006-03-13 Thread Brian Shields 
Thats a bit disappointing, maybe i was a bit naive thinking it would be 
straight forward. I need to have a serious think how i will progress. I 
am not willing to stop using axis2, ive too much time invested now and 
everything set up the way i need it for my own research. Unfortunately i 
also have committments on a project that uses JBoss 4.0. How much of 
WS-Security is implemented in the most recent stable release of JBoss?  
How straightforward is it to implement security on existing (Web) 
SessionBeans? I particularly like the modular approach of axis2 which 
completely abstracts the security layer from the developer of the 
endpoint and vice versa.
Any other help, pointers etc (maybe a url to a walk thru of deploying 
axis2 on JBoss 4 ; ) ) greatly appreciated.

Regards,
Brian.

robert lazarski wrote:

I haven't mixed JBoss and Axis2 together yet - but I know both 
reasonably well independently. I've used JBoss and EJB with JWSDP alot.


Internally JBoss 4.0.x comes with Axis 1.x - though strangely their 
docs and examples favor JWSDP. Furthermore, It tends to be more 
natural to use a Statelful session bean with web services.


There are Handlers that are part of Java itself and can be used with 
Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a 
lot. However, axis2 does not currently support JAX-RPC. JBoss is 
pretty wired into JAX-RPC.


So to make Web Services function with JBoss and EJB you'll need to 
edit and create a lot of files, and using axis2 in jboss and ejb is a 
bit bleeding edge. Don't get me wrong - it'd be a cool project and yes 
I think it can be done. But if you don't know Jboss or axis2 well, 
there are not going to be a lot of docs to help you. My personal 
experience on the jboss lists have not been good - they strongly 
encourage paid support.


Another option I would strongly consider is just use hibernate if you 
have a choice - instead of EJB. It'll be a lot simpler config. Sounds 
like your commited to EJB though.


If you still decide to use axis2 with jboss, look at the jboss guide 
chapter 12. Look at their files:


webservices.xml
ejb-jar.xml
jboss.xml

Know what config-*.xml does

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

On 3/13/06, * Brian Shields* < [EMAIL PROTECTED] 
> wrote:


Hi All,
I am currently using Axis2 and WSS4J as a test environment for some
secure services. I want to now deploy these secure services on a JBoss
4.0 AS. My experience with JBoss is limited, this work has been
carried
out by another member of the group. We have an ejb application which
uses a stateless session bean to implement the web services interface.
At the moment this is all deployed using JBossWS. Has anybody deployed
Axis2 as a service within JBoss 4.0? Is it straightforward. There
is the
option of changing to JBoss WS, but I am using other Axis2
features like
handlers that I would rather not drop.
Does anybody have any suggestions as to how I could go about this
transition? Any documentation on the web where this has been tried?
Regards,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.




--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

failure when trying to build axis2

2006-03-13 Thread Loreno Oliveira 
Hi,when I try to build the axis source I got the following problem:+| Executing multiproject:install-callback Apache Axis 2.0 - WSDL| Memory: 8M/11M+
Attempting to download XmlSchema-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is not knownWARNING: Failed to download 
XmlSchema-SNAPSHOT.jar.Attempting to download ws-policy-SNAPSHOT.jar.Response content length is not knownResponse content length is not knownResponse content length is not knownResponse content length is not known
WARNING: Failed to download ws-policy-SNAPSHOT.jar.BUILD FAILEDFile.. C:\Documents and Settings\Loreno Oliveira\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jellyElement... maven:reactor
Line.. 217Column 9The build cannot continue because of the following unsatisfied dependencies:XmlSchema-SNAPSHOT.jarws-policy-SNAPSHOT.jarTotal time: 1 minutes 34 secondsFinished at: Mon Mar 13 15:08:23 BRT 2006
C:\axis2-src>Does anybody knows why these two jars are not being downloaded??Thanks in advance..Loreno

[Axis2] Sender=null trying to use version 0.95-SNAPSHOT

2006-03-13 Thread tore.larsen 
Title: [Axis2] Sender=null trying to use version 0.95-SNAPSHOT







Hei, 


I have tried to use generated stub from my client class:




 /* Create the client stub for service invokation */

    DLExternalInformationStub stub = new DLExternalInformationStub(null, endpointServiceURL);


    /* get serviceClient */

    ServiceClient serviceClient = stub._getServiceClient();

    

    /* set client options */

    Options clientOptions = new Options();

    clientOptions.setTimeOutInMilliSeconds(connectionTimeout);

    clientOptions.setTranportOut(new TransportOutDescription(new QName(Constants.TRANSPORT_HTTP)));

    clientOptions.setTransportIn(new TransportInDescription(new QName(Constants.TRANSPORT_HTTP)));

    clientOptions.setUseSeparateListener(false);    

    serviceClient.setOptions(clientOptions);

    stub._setServiceClient(serviceClient);


    /* Service invocation */

    QueryExternalInformationResponseDocument responseDoc = stub.queryExternalInformation(requestDoc);




I receive 'null' in response and the soap-message never leaves my client side implementation. I have debugged it and found that in the AxisEngine class the following method invoke the remote service:




    public void send(MessageContext msgContext) throws AxisFault {


   ...


    if (!msgContext.isPaused()) {


    // write the Message to the Wire

    TransportOutDescription transportOut = msgContext.getTransportOut();

    TransportSender sender = transportOut.getSender();


    // This boolean property only used in client side fireAndForget invocation

    //It will set a property into message context and if some one has set the

    //property then transport sender will invoke in a diffrent thread

    Object isTranportBlocking = msgContext.getProperty(

    MessageContext.TRANSPORT_NON_BLOCKING);

    if (isTranportBlocking != null && ((Boolean) isTranportBlocking).booleanValue()) {

    msgContext.getConfigurationContext().getThreadPool().execute(

    new TranportNonBlockingInvocationWorker(msgContext, sender));

    } else {

    sender.invoke(msgContext);

    }

    }

    }





The problem is that the sender object is NULL at the time it is ment to be used to invoke. 


A bug or am I lacking any configuration in my client class using the generated stub?



Best regards / vennlig hilsen

Tore Larsen

Senior Software Engineer
Comptel Communication AS

e-mail    :  [EMAIL PROTECTED]

Re: Axis2 and JBoss 4.0

2006-03-13 Thread robert lazarski 
I haven't mixed JBoss and Axis2 together yet - but I know both
reasonably well independently. I've used JBoss and EJB with JWSDP alot.


Internally JBoss 4.0.x comes with Axis 1.x - though strangely their
docs and examples favor JWSDP. Furthermore, It tends to be more natural
to use a Statelful session bean with web services. 

There are Handlers that are part of Java itself and can be used with
Axis 1 and JWSDP - javax.xml.rpc.handler.Handler is one I've used a
lot. However, axis2 does not currently support JAX-RPC. JBoss is pretty
wired into JAX-RPC. 

So to make Web Services function with JBoss and EJB you'll need to edit
and create a lot of files, and using axis2 in jboss and ejb is a bit
bleeding edge. Don't get me wrong - it'd be a cool project and yes I
think it can be done. But if you don't know Jboss or axis2 well, there
are not going to be a lot of docs to help you. My personal experience
on the jboss lists have not been good - they strongly encourage paid
support. 

Another option I would strongly consider is just use hibernate if you
have a choice - instead of EJB. It'll be a lot simpler config. Sounds
like your commited to EJB though. 

If you still decide to use axis2 with jboss, look at the jboss guide chapter 12. Look at their files:

webservices.xml
ejb-jar.xml
jboss.xml

Know what config-*.xml does 

HTH,
Robert
http://www.braziloutsource.com/On 3/13/06, 
Brian Shields <
[EMAIL PROTECTED]> wrote:Hi All,I am currently using Axis2 and WSS4J as a test environment for some
secure services. I want to now deploy these secure services on a JBoss4.0 AS. My experience with JBoss is limited, this work has been carriedout by another member of the group. We have an ejb application which
uses a stateless session bean to implement the web services interface.At the moment this is all deployed using JBossWS. Has anybody deployedAxis2 as a service within JBoss 4.0? Is it straightforward. There is the
option of changing to JBoss WS, but I am using other Axis2 features likehandlers that I would rather not drop.Does anybody have any suggestions as to how I could go about thistransition? Any documentation on the web where this has been tried?
Regards,Brian.--Brian Shields BSc. MSc.,PhD Candidate,Department of Information Technology,National University of Ireland,Galway,Ireland.

autptyping question

2006-03-13 Thread Siddhartha Subramanian 








Using
1.3 and turning on Autotyping (axis.doAutoTypes) on the client wsdd makes axis
base64 encode the headers, is there some way this disable this encoding? 

 

Any information will be helpful

 

Regards, 

Siddhartha G.
Subramanian (Sid) 
MCP Base - Web Services
.Do or do not.
There is no try. . ~ Yoda to Luke

 

Re: Anne can u please tell me what is interoperable data type.

2006-03-13 Thread Anne Thomas Manes 
If the response comes back as a Dataset type, then you will have to parse and process the response using DOM.On 3/12/06, Giri <
[EMAIL PROTECTED]> wrote:Hianne pls gieve me suggestions ,is there any major modification in the dot net coding.(becoz they have already coded using data set).

 
as we agreed in the document,now we have to proceed with data set only.pls
now how do i get the information in generated code.pls help me to write client code
 
shall i use MessageElment[]   = obj.get_any();
 
then all data'as are instring format.
 
 
 
regards
Giri babu 
On 3/12/06, Anne Thomas Manes <[EMAIL PROTECTED]
> wrote:

A .Net Dataset is the datatype used by ADO.NET. It contains proprietary data management information, and it should not be exposed via a SOAP/WSLD interface. The Dataset should be converted into an array of structures. 
 
Anne

On 3/10/06, Giri <[EMAIL PROTECTED]> wrote:
 


hi
 
   Anne this is very urgent,can u please tell me what is interoperable data type.
please give me suggestions for dot.Net web services how it should be?
Which condition he has to set?
dataset means - it has Objects is it?
 
 
 
regards

Giri babu.v 

Re: null namespace generated for qualified elements

2006-03-13 Thread Anne Thomas Manes 
Now, according to your WSDL, the child element of the SOAP Body should be called "tns:PutSCIRequest". But your child element is call "tns:PutConfigRequest". Anne
On 3/13/06, Vikas Singh <[EMAIL PROTECTED]> wrote:
Anne, Thanks for your help.I tried changes suggested by you but it did not work.WSDL file:

http://schemas.xmlsoap.org/wsdl/soap/"
	xmlns:tns="
http://myns/schemas/2006/02/26/sciwsdl"	xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"	xmlns:xsd="
http://www.w3.org/2001/XMLSchema" name="NewWSDLFile"	targetNamespace="
http://myns/schemas/2006/02/26/sciwsdl"	xmlns:xsd1="

http://myns/schemas/2006/3/3/sci">		targetNamespace="
http://myns/schemas/2006/02/26/sciwsdl"			xmlns:scx="
http://myns/schemas/2006/3/3/sci"			elementFormDefault="qualified">			namespace="
http://myns/schemas/2006/3/3/sci"schemaLocation="
http://localhost:8080/jce/sci.xsd" />			

		
			
		

		

			
		transport="
http://schemas.xmlsoap.org/soap/http
" />	soapAction="
http://myns/schemas/2006/02/26/sciwsdl/putSCI
" />	
		
	name="config">
			location="http://localhost:8080/jce/services/config" />
			
Pre-serialization request body : 
http://myns/schemas/2006/02/26/sciwsdl
">http://myns/schemas/2006/3/3/sci/"	xmlns:thttp="

http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd
"	serviceGroup="travelDepartment">
		false
			true
			Post-serialization request body 

(in ) :
http://myns/schemas/2006/02/26/sciwsdl
">
http://localhost:8080/jce/sci.xsd"
serviceGroup="travelDepartment"
xmlns:scx="http://myns/schemas/2006/3/3/sci/"
xmlns:thttp="http://myns/schemas/2006/3/3/transport/http/"> 
   xmlns:scx="">		
  xmlns:thttp="">			
xmlns:thttp=""
>false			
xmlns:thttp="">true			

 	
  
   


I get the following exception:org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="scx",rawname="xmlns:scx"" is invalid. Prefixed namespace bindings may not be empty.
When I change the pre-serialization request body to contain explicit namespace defintions for all the elements :

http://myns/schemas/2006/02/26/sciwsdl">http://myns/schemas/2006/3/3/sci/
"	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd
"	serviceGroup="travelDepartment">
	http://myns/schemas/2006/3/3/sci/">
  	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >
		  xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >false		 	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/
" >true			Axis, post serialization does not insert any empty namespace defintions but the handler method is not found.
Couldn't find an appropriate operation for XML QName {
http://myns/schemas/2006/02/26/sciwsdl}PutConfigRequest
when I tried changing  http://myns/schemas/2006/02/26/sciwsdl
">to http://myns/schemas/2006/02/26/sciwsdl">it worked.
But the issue is I have to 
hack all the elements with the namespace definition.Thanks,Vikas+++=

Vikas,When using the message style interface, your application is responsible forconstructing the SOAP Body exactly as you've defined it in your WSDL.According to your WSDL, the Body should contain an element called
http://myns/schemas/2006/3/3/sci/sciwsdl}PutConfigRequest (not putConfig).Note that your WSDL has a critical namespace error: you don't declare the
"tns" namespace (the WSDL target namespace).
AnneOn 3/11/06, Vikas Singh <[EMAIL PROTECTED]> wrote:> > Hi,> 
> Following is the WSDL:> > > > http://schemas.xmlsoap.org/wsdl/soap/"
> xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 name="NewWSDLFile"> targetNamespace=" 
http://myns/schemas/2006/3/3/sci//sciwsdl"> xmlns:xsd1=" http://myns/schemas/2006/3/3/sci/sci
> ">> > > targetNamespace=" http://myns/schemas/2006/3/3/sci/sciwsdl"> > xmlns:scx="
http://myns/schemas/2006/3/3/sci/
 "> elementFormDefault="qualified">> > namespace=" 
http://myns/schemas/2006/3/3/sci/sci<
http://myns/schemas/2006/3/3/sci//s \> ci> "> schemaLocation="
http://localhost:8080/schemas/sci.xsd " />> 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > transport="http://schemas.xmlsoap.org/soap/http
 " />> 
> > soapAction=" http://myns/schemas/2006/3/3/sci/putSCI"
 />> > 
> > > > > > 

> > > > > > name="config">> > 

> > location=" http://localhost:8080/jce/services/config"
 />> > > > 
> > > > > > I wrap my request xml (which goes into the envelop body into a putConfig> to help it identify the 'Message' type method on the server.

> public SOAPBodyElement[] putConfig(SOAPBodyElement[] bodies)> > > The xml which I set in the SOAPBodyElement

[0] is> > > > xmlns:scx=" http://myns/schemas/20

Re: An RFC example needed!

2006-03-13 Thread Anne Thomas Manes 
Niels,You're right -- the Apache SOAP page should provide a warning that tells you to use Axis 1 instead. Axis 2 isnt feature-complete yet, so I don't think it's appropriate to put the same warning on the Axis 1 page. Axis 1 is Apache's current production release SOAP engine. Given that you've already started working with Axis 1, I suggest you stick with it rather than re-writing your app for Axis 2. 
When trying to enable interoperability with .NET, it's always a good idea to adopt the "WSDL First" approach. You can use java2wsdl to generate a first pass at a WSDL file, but then you should tweak the WSDL to ensure that it supports the structures you want. And yes, you want to request the "wrapped" style, and you want to name each of your arguments. 
After you have refined your WSDL file, then you want to use wsdl2java to regenerate your service skeleton and WSDD file. Perhaps if you posted your WSDL and WSDD files we could provide you with a little more assistance. 
AnneOn 3/13/06, Niels Baloe <[EMAIL PROTECTED]> wrote:
Hi all,I have a problem.Last week I needed to implement a webservice, I saw Apache SOAP, heared somegood things about it, so I used it to implement my webservice, and it workedquite fine in no-time. Then I needed to do things with a WSDL and I found
out about Apache Axis. Hmmm, well, so I shifted to Axis. No big problems,one day later Axis was running the thing, and I could generate a WSDL (andback) too. Note: why the heck doesn't the Apache SOAP frontpage say: "DON't
USE THIS, USE AXIS INSTEAD!" I recommend it.Anyway, now I have to communicate with a .NET service. So I've set thecommunication to 'wrapped', and thanks to some text-based java-code Ialready had (because the Axis exception doesn't say anything else then
'null'!!-- it should just wrap the HTTP response which contains the textualerror from the server), I found out that .NET needs a specific name asthe first argument of the function instead of the automatic 'arg0' (grrr),
and that it needed capitals in some header stuff. So today I wrote a customserialiser too to provide the capitals in the header. Pf. And it worksquite fine in the text-only tester (sending exactly what Axis generates),
but not in Axis. Why? The only difference in the two messages (text andAxis) is HTTP/1.1 versus HTTP/1.0. And I suspect it is a shared IP. Anyway,I didn't succeed in changing the header to 1.1 inside Axis...
So, today I found out about Axis2. Yes, a bit stupid yes, but then again,why doesn't the Axis1 frontpage say anything about it (the first line wouldbe a nice place;) ). But, Axis2 has a different way of deploying, and
currently I first want to get an example running. But, there are no examplesthat use the word 'call' or that throw around an object. [ Note: I can't useAxis1 and Axis2 together as well, because of a namespace-clash with the
logging, so I have to switch to Axis2 in the end. ] Anyway, does anyone havean example? Yes I know about the user guide examples, but these do notdemonstrate something with sending and receiving objects. We are not in the
stone ages, I'm not going to parse a tree myself, I need objects. I justneed an example like the 'address' example in ApacheSOAP/Axis1.4, which hasa class Address {..} which is thrown aroundPS. Another thing: why doesn't the Java2WSDL contain a main() anymore? It's
quite convenient.Thank you very much for any advice. Either an example, or notifying of howto set Axis1.4 to HTTP/1.1 would be really very great!All the best,Niels Gorisse_
Don't just search. Find. Check out the new MSN Search!http://search.msn.com/

Re: An RFC example needed!

2006-03-13 Thread robert lazarski 
Take a look at the migration guide: 

http://ws.apache.org/axis2/0_93/migration.html

There will be a new axis2 release in the upcomming days, and this page
will have an axis 1.x to axis2 data binding (wsdl) example. In the
meantime, you can take a peek here: 

http://issues.apache.org/jira/browse/AXIS2-485?page=all

BTW, the address example in the axis 1.x uses WSDL style 'rpc encoded'
. For the time being you need to use document / literal with axis2 . 

HTH,
Robert
http://www.braziloutsource.com/On 3/13/06, Niels Baloe <[EMAIL PROTECTED]
> wrote:Hi all,I have a problem.Last week I needed to implement a webservice, I saw Apache SOAP, heared some
good things about it, so I used it to implement my webservice, and it workedquite fine in no-time. Then I needed to do things with a WSDL and I foundout about Apache Axis. Hmmm, well, so I shifted to Axis. No big problems,
one day later Axis was running the thing, and I could generate a WSDL (andback) too. Note: why the heck doesn't the Apache SOAP frontpage say: "DON'tUSE THIS, USE AXIS INSTEAD!" I recommend it.
Anyway, now I have to communicate with a .NET service. So I've set thecommunication to 'wrapped', and thanks to some text-based java-code Ialready had (because the Axis exception doesn't say anything else then
'null'!!-- it should just wrap the HTTP response which contains the textualerror from the server), I found out that .NET needs a specific name asthe first argument of the function instead of the automatic 'arg0' (grrr),
and that it needed capitals in some header stuff. So today I wrote a customserialiser too to provide the capitals in the header. Pf. And it worksquite fine in the text-only tester (sending exactly what Axis generates),
but not in Axis. Why? The only difference in the two messages (text andAxis) is HTTP/1.1 versus HTTP/1.0. And I suspect it is a shared IP. Anyway,I didn't succeed in changing the header to 1.1 inside Axis...
So, today I found out about Axis2. Yes, a bit stupid yes, but then again,why doesn't the Axis1 frontpage say anything about it (the first line wouldbe a nice place;) ). But, Axis2 has a different way of deploying, and
currently I first want to get an example running. But, there are no examplesthat use the word 'call' or that throw around an object. [ Note: I can't useAxis1 and Axis2 together as well, because of a namespace-clash with the
logging, so I have to switch to Axis2 in the end. ] Anyway, does anyone havean example? Yes I know about the user guide examples, but these do notdemonstrate something with sending and receiving objects. We are not in the
stone ages, I'm not going to parse a tree myself, I need objects. I justneed an example like the 'address' example in ApacheSOAP/Axis1.4, which hasa class Address {..} which is thrown aroundPS. Another thing: why doesn't the Java2WSDL contain a main() anymore? It's
quite convenient.Thank you very much for any advice. Either an example, or notifying of howto set Axis1.4 to HTTP/1.1 would be really very great!All the best,Niels Gorisse_
Don't just search. Find. Check out the new MSN Search!http://search.msn.com/

Re: Why Can't I run WSDL2Java on this WSDL?

2006-03-13 Thread Anne Thomas Manes 
Jason,You have multiple schemas with a targetNamespace of "http://www.opengis.net/wcs". Make sure that you haven't defined the same element or type more than once. 
Also, you must import the "gml" schema into the "wcs" schemas in order to reference elements and types from the "gml" schema.  Likewise, you must import the "xlink" schema into the "wcs" and "gml" schemas in order to reference elements and types from the "xlink" schema.
AnneOn 3/13/06, Jason J. Kahler <[EMAIL PROTECTED]> wrote:
It always gives me the same error:org.apache.axis.wsdl.toJava.DuplicateFileException: Duplicate file name:.\net\opengis\www\gml\DirectPositionType2.java.Hint: you may have mapped two namespaces with elements of the same name
to the same package name.atorg.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:110)atorg.apache.axis.wsdl.toJava.JavaBeanWriter.generate(JavaBeanWriter.java:1406)at
org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.java:113)atorg.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421)at org.apache.axis.wsdl.gen.Parser.generateTypes
(Parser.java:547)at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:432)at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run
(Parser.java:362)at java.lang.Thread.run(Unknown Source)Attached is the WSDL

Axis2 and JBoss 4.0

2006-03-13 Thread Brian Shields 

Hi All,
I am currently using Axis2 and WSS4J as a test environment for some 
secure services. I want to now deploy these secure services on a JBoss 
4.0 AS. My experience with JBoss is limited, this work has been carried 
out by another member of the group. We have an ejb application which 
uses a stateless session bean to implement the web services interface. 
At the moment this is all deployed using JBossWS. Has anybody deployed 
Axis2 as a service within JBoss 4.0? Is it straightforward. There is the 
option of changing to JBoss WS, but I am using other Axis2 features like 
handlers that I would rather not drop.
Does anybody have any suggestions as to how I could go about this 
transition? Any documentation on the web where this has been tried?

Regards,
Brian.

--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

An RFC example needed!

2006-03-13 Thread Niels Baloe 

Hi all,

I have a problem.

Last week I needed to implement a webservice, I saw Apache SOAP, heared some 
good things about it, so I used it to implement my webservice, and it worked 
quite fine in no-time. Then I needed to do things with a WSDL and I found 
out about Apache Axis. Hmmm, well, so I shifted to Axis. No big problems, 
one day later Axis was running the thing, and I could generate a WSDL (and 
back) too. Note: why the heck doesn't the Apache SOAP frontpage say: "DON't 
USE THIS, USE AXIS INSTEAD!" I recommend it.


Anyway, now I have to communicate with a .NET service. So I've set the 
communication to 'wrapped', and thanks to some text-based java-code I 
already had (because the Axis exception doesn't say anything else then 
'null'!!-- it should just wrap the HTTP response which contains the textual 
error from the server), I found out that .NET needs a specific name as 
the first argument of the function instead of the automatic 'arg0' (grrr), 
and that it needed capitals in some header stuff. So today I wrote a custom 
serialiser too to provide the capitals in the header. Pf. And it works 
quite fine in the text-only tester (sending exactly what Axis generates), 
but not in Axis. Why? The only difference in the two messages (text and 
Axis) is HTTP/1.1 versus HTTP/1.0. And I suspect it is a shared IP. Anyway, 
I didn't succeed in changing the header to 1.1 inside Axis...


So, today I found out about Axis2. Yes, a bit stupid yes, but then again, 
why doesn't the Axis1 frontpage say anything about it (the first line would 
be a nice place;) ). But, Axis2 has a different way of deploying, and 
currently I first want to get an example running. But, there are no examples 
that use the word 'call' or that throw around an object. [ Note: I can't use 
Axis1 and Axis2 together as well, because of a namespace-clash with the 
logging, so I have to switch to Axis2 in the end. ] Anyway, does anyone have 
an example? Yes I know about the user guide examples, but these do not 
demonstrate something with sending and receiving objects. We are not in the 
stone ages, I'm not going to parse a tree myself, I need objects. I just 
need an example like the 'address' example in ApacheSOAP/Axis1.4, which has 
a class Address {..} which is thrown around



PS. Another thing: why doesn't the Java2WSDL contain a main() anymore? It's 
quite convenient.


Thank you very much for any advice. Either an example, or notifying of how 
to set Axis1.4 to HTTP/1.1 would be really very great!


All the best,

Niels Gorisse

_
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

Re: How to Deploy Axis1.3 webservice on HTTPS enabled Tomcat server

2006-03-13 Thread Junaid . Bhatra 
See the section on Security in the Axis Wiki
http://wiki.apache.org/ws/FrontPage/Axis

It has a section on deploying and accessing Web Services over SSL

- Junaid



   
 Rhimbo
 <[EMAIL PROTECTED] 
 >  To 
   axis-user@ws.apache.org 
 03/11/2006 04:49   cc 
 PM
   Subject 
   Re: How to Deploy Axis1.3   
 Please respond to webservice on HTTPS enabled Tomcat  
 [EMAIL PROTECTED] server  
  he.org   
   
   
   
   
   




Hi Mohit,

I don't really know the answer to your question but I did see
something on this page:

http://ws.apache.org/axis/java/building-axis.html

Under "Building with JSEE" it says this:

This is needed for https support.

   1. Download the required Class libraries
  (jsse.jar, jnet.jar,jcert.jar) to $(axis.home)/java/lib.

   You can download this from http://java.sun.com/products/jsse/
   Recommended version : 1.0.3


I don't know if this helps.  Sorry.

Vartan


--- Mohit_Goyal <[EMAIL PROTECTED]> wrote:

> Hi all... i have developed a webservice which needs to be deployed over
> https on Tomcat 5 server. I tried using the same stepa which we follow
> for a regular deployment over http but i keep getting exceptions when
> running the
>
> java org.apache.axis.client.AdminClient
> -lhttps://domain:443/axis/services/Servicename deploy.wsdd
>
> Can anyone who has done deployment over Tomcat or faced similar problem
> tell me what steps to follow to deploy the service over https
>
>
> Thanks a lot in advance
> Mohit
>
>
> DISCLAIMER:
> This email (including any attachments) is intended for the sole use of
> the intended recipient/s and may contain material that is CONFIDENTIAL
> AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or
> copying or distribution or forwarding of any or all of the contents in
> this message is STRICTLY PROHIBITED. If you are not the intended
> recipient, please contact the sender by email and delete all copies;
> your cooperation in this regard is appreciated.
>


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Re: [Axis2] EchoNonBlockingDualClient problem

2006-03-13 Thread robert lazarski 
Could you start another thread with an axis2 prefix mentioning jboss ?
I know jboss with web services ok, but it was with either axis 1 or
jwsdp - not axis2 . Are you using wsdl and ejb ? 

Robert
http://www.braziloutsource.com/On 3/13/06, Brian Shields <
[EMAIL PROTECTED]> wrote:Tony,Apologies for jumping into this thread on an unrelated issue but i
notice you have axis2 deployed on JBoss 4.0. I am about to undertakethis task and was wondering if there was any resources on the web tohelp in it. I dont have a lot of experience with JBoss so not looking
forward to it!!Regards,BrianAntony Wilson wrote:>> I have not been able to get the EchonNonBlockingDualClient example to> work as described in the documentation.  In my setup, I have Axis2
> deployed to JBoss 4.0.3 and I have modified the> userguide.example1.MyService to delay for about 10 seconds before> responding (leaving the 'echo' method).  After packaging and deploying> the 
MyService.aar to Axis2, I run EchoNonBlockingDualClient> example...slightly modified to add a print statement within the while> loop...like so>>public static void main(String[] args) {>try {
>OMElement payload = ClientUtil.getEchoOMElement();>>Options options = new Options();>options.setTo(targetEPR);>options.setTransportInProtocol
(Constants.TRANSPORT_HTTP);>options.setUseSeparateListener(true);>>//Callback to handle the response>Callback callback = new Callback() {>public
void onComplete(AsyncResult result) {>try
{>StringWriter
writer = new StringWriter();>> result.getResponseEnvelope().serialize(XMLOutputFactory.newInstance()>.createXMLStreamWriter(writer));>writer.flush
();>System.out.println(writer.toString());>>>}
catch (XMLStreamException e) {>onError(e);>}>}>>public
void onError(Exception e) {>e.printStackTrace();>}>};>>//Non-Blocking Invocation>ServiceClient sender = new ServiceClient();
>sender.setOptions(options);>sender.sendReceiveNonblocking(payload, callback);>>//Wait till the callback receives the response.>while (!callback.isComplete()) {
>System.out.println("waiting...");>Thread.sleep(1000);>}>//Need to close the Client Side Listener.>> We I run it the code appears to block/wait at the
> "sender.sendRecieveNonBlocking(...)" line for about 10 seconds. When> the program continues,  I never see any print statements since the> "callback.isComplete()" is true by the time it gets to that point in
> the code.  The really bizarre part is that if I use> "options.setUseSeparateListener(false)"...the behavior is exactly what> I was originally expecting...I see several "waiting..." print
> statements before the callback's onComplete is invoked.  My> operational scenario requires a dual channel transport since my> webservice calls can be really long...therefore using a single two-way
> transport (e.g., options.setUseSeparateListener(false)) is not a> viable option.>> Bottomline, I can't seem to get the two-way dual channel stuff> (EchoNonBlockingDualClient) to work for me.  I must be missing
> something obvious...but I don't see what it is.  Any help would be> appreciated.>> Thanks,> Tony>>--Brian Shields BSc. MSc.,PhD Candidate,Department of Information Technology,
National University of Ireland,Galway,Ireland.

Re: [Axis2] EchoNonBlockingDualClient problem

2006-03-13 Thread Brian Shields 

Tony,
Apologies for jumping into this thread on an unrelated issue but i 
notice you have axis2 deployed on JBoss 4.0. I am about to undertake 
this task and was wondering if there was any resources on the web to 
help in it. I dont have a lot of experience with JBoss so not looking 
forward to it!!

Regards,
Brian

Antony Wilson wrote:



I have not been able to get the EchonNonBlockingDualClient example to 
work as described in the documentation.  In my setup, I have Axis2 
deployed to JBoss 4.0.3 and I have modified the 
userguide.example1.MyService to delay for about 10 seconds before 
responding (leaving the 'echo' method).  After packaging and deploying 
the MyService.aar to Axis2, I run EchoNonBlockingDualClient 
example...slightly modified to add a print statement within the while 
loop...like so


   public static void main(String[] args) {
   try {
   OMElement payload = ClientUtil.getEchoOMElement();

   Options options = new Options();
   options.setTo(targetEPR);
   options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
   options.setUseSeparateListener(true);

   //Callback to handle the response
   Callback callback = new Callback() {
   public void onComplete(AsyncResult result) {
   try {
   StringWriter writer = new StringWriter();
   
result.getResponseEnvelope().serialize(XMLOutputFactory.newInstance()

   .createXMLStreamWriter(writer));
   writer.flush();
   System.out.println(writer.toString());


   } catch (XMLStreamException e) {
   onError(e);
   }
   }

   public void onError(Exception e) {
   e.printStackTrace();
   }
   };

   //Non-Blocking Invocation
   ServiceClient sender = new ServiceClient();
   sender.setOptions(options);
   sender.sendReceiveNonblocking(payload, callback);

   //Wait till the callback receives the response.
   while (!callback.isComplete()) {
   System.out.println("waiting...");
   Thread.sleep(1000);
   }
   //Need to close the Client Side Listener.

We I run it the code appears to block/wait at the 
"sender.sendRecieveNonBlocking(...)" line for about 10 seconds. When 
the program continues,  I never see any print statements since the 
"callback.isComplete()" is true by the time it gets to that point in 
the code.  The really bizarre part is that if I use 
"options.setUseSeparateListener(false)"...the behavior is exactly what 
I was originally expecting...I see several "waiting..." print 
statements before the callback's onComplete is invoked.  My 
operational scenario requires a dual channel transport since my 
webservice calls can be really long...therefore using a single two-way 
transport (e.g., options.setUseSeparateListener(false)) is not a 
viable option.


Bottomline, I can't seem to get the two-way dual channel stuff 
(EchoNonBlockingDualClient) to work for me.  I must be missing 
something obvious...but I don't see what it is.  Any help would be 
appreciated.


Thanks,
Tony




--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

org.xml.sax.SAXParseException: Premature end of file.

2006-03-13 Thread Hans Rupp 
Hello,

i've got the following problem. I'm using Axis1.3. I generated the client-
and server-classes for my webservice
with wsdl2java. I also wrote a simple proxy, which forwards the request and
sends back the response, to get through my firewall. I got the following
problem:

When i use my client without the proxy everything is fine. But when i use
the proxy, the client cannot understand
the answer. I checked the the messages from client to proxy and vice versa
using the tcpmon and the messages from
the proxy to the service and vice versa using the soapmonitor, and all
messages look correct to me. But when
the client gets the response from the proxy, it throws the following
exception:

org.xml.sax.SAXParseException: Premature end of file.
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at Retailer7.wsdl.RetailerSOAPStub.quotation(RetailerSOAPStub.java:219)
... 7 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseEx
ception(Unknown Source)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unkno
wn Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
 Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
 Source)
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersi
on(Unknown Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown 
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
.java:227)


at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
... 16 more
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: org.xml.sax.SAXParseException: Premature end of file.
 faultActor: 
 faultNode: 
 faultDetail: 
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException:
Premature end of file.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseEx
ception(Unknown Source)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unkno
wn Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
 Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
 Source)
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersi
on(Unknown Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown 
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at Retailer7.wsdl.RetailerSOAPStub.quotation(RetailerSOAPStub.java:219)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingM

Re: axis2 and mtom

2006-03-13 Thread Brian Shields 

Thanks Thilina,
MTOM was obviously not switched by default in my deployment.
I will explore Secure MTOM, it seems perfect for my needs.
Regards,
Brian.

Thilina Gunarathne wrote:


Hi Brian,
See my comments below...
 
On 3/12/06, *Brian Shields* <[EMAIL PROTECTED] 
> wrote:


Hi all,
I am having some trouble sending attachments with axis2 messages.
Until
now I have been sending a large xml string as a parameter of a web
service call. I recently applied security to this and I am getting
a lot
of errors when the string parameter goes beyond a certain size. What I
am exploring as a work around is sending the xml file as an
attachment
using MTOM. From some v quick research i think this is the best
approach
when security is involved.

 
You can also consider using Secure MTOM directly if you r going for 
encryption... An encrypted payload(cipher value) is a binary content. 
Normally in the context of web services people encode the 
payloadcipher value using base64 and send it..Now with MTOM we can 
directly send the encrypted payload as an binary attachment. Axis2 
provides secure MTOM support...


My problem is on the parsing of this message. I am getting a
"ContentID
is null" message. Is this because I have not specified the MIME
type in
the Client? 

 
AFAIK this does not matter a lot when using data handlers...


My client code looks like...

OMElement value = fac.createOMElement("Text", omNs);
DataHandler dh = new DataHandler(new ByteArrayDataSource(
s.getBytes()));
OMText text = fac.createText(dh, true);
value.addChild(text);
where s is a String.

The server code to parse this looks like...
OMElement binaryElement = element.getFirstElement();
OMText binaryNode = (OMText) binaryElement.getFirstOMChild();

 
>>> binaryNode.setOptimize(true);


DataHandler actualDH = (DataHandler)binaryNode.getDataHandler();

 
Do u have MTOM enabled in the client side. MTOM is switched ON by 
default , but it's worth checking... You can use HttpTracer (aka 
TCPMON) to see the wire level message. For me it seems ur message 
still transmits without MTOM optimisation.
 
You can try doing a hack by adding this line in between the 3d and 4th 
lines in the above given server code...

binaryNode.setOptimize(true);
 
I don't recomend this usage in the long run.. But give it a try.. If 
it does not give the same error, then it means ur message was not 
optimized earlier...
 
 
~Thilina



--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/ 

http://thilinag.blogspot.com/ 
http://www.bloglines.com/blog/Thilina  



--
Brian Shields BSc. MSc.,
PhD Candidate,
Department of Information Technology,
National University of Ireland,
Galway,
Ireland.

Re: Setting URN in EndpointReference class

2006-03-13 Thread Eran Chinthaka 
Hi Sricharan,

Let me explain how EndpointReference class (EPR) works with Axis2.

It models the same EPR concept in WS-Addressing EndpointReference. So
you can set only one address to that. I exactly can not understand why
you need to have two addresses, for the same EPR, one for internal and
one for external.
Having set the address property of EPR, Axis2 uses that address to
select the proper transport to send the SOAP message to the endpoing.
For example;
EndpointReference toEPR = new
EndpointReference("http://my-service-endpoint.org";);
options.setTo(toEPR);

internally we search for a transport which supports the scheme of the
URL. i.e. HTTP in this case. So if you wanna include something
like"urn:MyApplicationAPI", as your endpoint then you need to register a
transport which supports urn scheme. Thats why you are getting the
exception.

If you just ignore the internal address (what do u mean by internal
address), then this should work.

EndpointReference epr = new 
EndpointReference(""https://myservices.test.com/wsetestharness/myapplicationapi.asmx"";);
_messageContext.setTo(new EndpointReference(uri1.toString()));


HTH.
Chinthaka


Sricharan Anand wrote:

>How do we set an URN as part of EndpointReference class?
>
>Here is my problem:
>I am writing a Axis2 client to consume a remote .Net based Webservice(running 
>WSE 2.0)
>
>The endpoint of the service is something like this(taken from a C# client code 
>which is working)
>
>'Me.Url = "https://myservices.test.com/wsetestharness/myapplicationapi.asmx";
>Me.Destination = New Microsoft.Web.Services2.Addressing.EndpointReference(New 
>Uri("urn:MyApplicationAPI"), New 
>Uri("https://myservices.test.com/wsetestharness/myapplicationapi.asmx";))
>
>The 1st URI(urn:MyApplicationAPI) in above code is the internal address of our 
>webservice. The 2nd Uri in the above code is the external address of our 
>WebService.
>
>I want to construct the same EndpointReference using the Axis2 classes. I have 
>tried doing the following:
>Uri uri1 = new URI("urn:MyApplicationAPI");
>Uri uri2 = new 
>URI("https://myservices.test.com/wsetestharness/myapplicationapi.asmx";);
>EndpointReference epr = new EndpointReference(uri1.toString()+uri2.toString());
>_messageContext.setTo(new EndpointReference(uri1.toString()));
>This does not work and i get the following exception: 
>org.apache.axis2.AxisFault: unknown protocol: urn; nested exception is: 
>java.net.MalformedURLException: unknown protocol: urn; nested exception 
> is: 
>org.apache.axis2.AxisFault: unknown protocol: urn; nested exception is: 
>java.net.MalformedURLException: unknown protocol: urn
>at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:245)
>at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:449)
>
>
>
>   
>-
>Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
>   
>-
>Yahoo! Mail
>Bring photos to life! New PhotoMail  makes sharing a breeze. 
>  
>


signature.asc
Description: OpenPGP digital signature

Re: null namespace generated for qualified elements

2006-03-13 Thread Vikas Singh 
Anne, Thanks for your help.I tried changes suggested by you but it did not work.WSDL file:
http://schemas.xmlsoap.org/wsdl/soap/"	xmlns:tns="
http://myns/schemas/2006/02/26/sciwsdl"	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"	xmlns:xsd="
http://www.w3.org/2001/XMLSchema" name="NewWSDLFile"	targetNamespace="http://myns/schemas/2006/02/26/sciwsdl"	xmlns:xsd1="
http://myns/schemas/2006/3/3/sci">		targetNamespace="http://myns/schemas/2006/02/26/sciwsdl"			xmlns:scx="
http://myns/schemas/2006/3/3/sci"			elementFormDefault="qualified">			namespace="
http://myns/schemas/2006/3/3/sci"schemaLocation="http://localhost:8080/jce/sci.xsd" />			
		
	
		
			
		transport="http://schemas.xmlsoap.org/soap/http
" />	soapAction="http://myns/schemas/2006/02/26/sciwsdl/putSCI
" />	
			name="config">
			location="http://localhost:8080/jce/services/config" />			
Pre-serialization request body : http://myns/schemas/2006/02/26/sciwsdl
">http://myns/schemas/2006/3/3/sci/"	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd"	serviceGroup="travelDepartment">
		false			true
			Post-serialization request body 
(in ) :http://myns/schemas/2006/02/26/sciwsdl
">
http://localhost:8080/jce/sci.xsd"
serviceGroup="travelDepartment"
xmlns:scx="http://myns/schemas/2006/3/3/sci/"
xmlns:thttp="http://myns/schemas/2006/3/3/transport/http/"> 
   xmlns:scx="">		
  xmlns:thttp="">			
xmlns:thttp="">false			
xmlns:thttp="">true			

 	
  
   


I get the following exception:org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="scx",rawname="xmlns:scx"" is invalid. Prefixed namespace bindings may not be empty.
When I change the pre-serialization request body to contain explicit namespace defintions for all the elements :
http://myns/schemas/2006/02/26/sciwsdl">http://myns/schemas/2006/3/3/sci/"	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" 	schemaLocation="http://localhost:8080/jce/sci.xsd"	serviceGroup="travelDepartment">
	http://myns/schemas/2006/3/3/sci/">  	xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >		  xmlns:thttp="
http://myns/schemas/2006/3/3/transport/http/" >false		 	xmlns:thttp="http://myns/schemas/2006/3/3/transport/http/
" >true			Axis, post serialization does not insert any empty namespace defintions but the handler method is not found.
Couldn't find an appropriate operation for XML QName {http://myns/schemas/2006/02/26/sciwsdl}PutConfigRequest
when I tried changing  http://myns/schemas/2006/02/26/sciwsdl">to http://myns/schemas/2006/02/26/sciwsdl">it worked.But the issue is I have to 
hack all the elements with the namespace definition.Thanks,Vikas+++=
Vikas,When using the message style interface, your application is responsible forconstructing the SOAP Body exactly as you've defined it in your WSDL.According to your WSDL, the Body should contain an element called
http://myns/schemas/2006/3/3/sci/sciwsdl}PutConfigRequest (not putConfig).Note that your WSDL has a critical namespace error: you don't declare the"tns" namespace (the WSDL target namespace).
AnneOn 3/11/06, Vikas Singh <[EMAIL PROTECTED]> wrote:> > Hi,> > Following is the WSDL:> > > > http://schemas.xmlsoap.org/wsdl/soap/"> xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"> xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="NewWSDLFile"> targetNamespace=" 
http://myns/schemas/2006/3/3/sci//sciwsdl"> xmlns:xsd1=" http://myns/schemas/2006/3/3/sci/sci> ">> > > targetNamespace=" http://myns/schemas/2006/3/3/sci/sciwsdl"> > xmlns:scx="http://myns/schemas/2006/3/3/sci/
 "> elementFormDefault="qualified">> > namespace=" http://myns/schemas/2006/3/3/sci/sci<
http://myns/schemas/2006/3/3/sci//s \> ci> "> schemaLocation="http://localhost:8080/schemas/sci.xsd " />> 
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > transport="http://schemas.xmlsoap.org/soap/http " />> 
> > soapAction=" http://myns/schemas/2006/3/3/sci/putSCI" />> > 
> > > > > > 
> > > > > > name="config">> > 
> > location=" http://localhost:8080/jce/services/config" />> > > > 
> > > > > > I wrap my request xml (which goes into the envelop body into a putConfig> to help it identify the 'Message' type method on the server.
> public SOAPBodyElement[] putConfig(SOAPBodyElement[] bodies)> > > The xml which I set in the SOAPBodyElement
[0] is> > > > xmlns:scx=" http://myns/schemas/2006/3/3/sci/"> xmlns:xsi="> 
http://www.w3.org/2001/XMLSchema-instance "> serviceGroup="travelDepartment" >> > > xmlns:thttp=" http://myns/schemas/2006/3/3/transport">> false> > 
> > > > > > On the client side log I see org.apache.axis.ConfigurationException: N

Re: WS-Addressing headers in generated Stub(Cont.)

2006-03-13 Thread Deepal Jayasinghe 
Hi Chinthka ,

I think you are the best person to answer this question :)

Sricharan Anand wrote:

> Thanks Deepal for your reply. I tried what you said below and still
> couldn't get it to work - maybe i am doing something basically wrong.
>
> Here is the issue in more detail:
>
> Like I said before, I am writing a Axis2 client to communicate with a
> remote .Net service. This service is expecting the following WS-A headers:
>
> http://www.myservice.com/TestHarness/MyApplication
>  uuid:84ce994b-7615-42a4-be78-45621febe
>   
>
> http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous
>   
>   urn:MyApplicationAPI
> The location of the service i.e actual URL is different(given below):
> soap:address location
> ="*https://myservices.test.com/testharness/myapplicationapi.asmx";
>
>
> This is how i set the WS-A headers in my client(stub) code:
>
> EndpointReference epr = new EndpointReference("urn:MyApplicationAPI");
> _messageContext.setWSAAction("http://www.myservice.com/TestHarness/MyApplication";);
>  
>  _messageContext.setTo(epr);
>   
> _messageContext.setMessageID("uuid:84ce996b-7615-42a4-be78-45621febe3fe");
>   
> *When I run the above code I get this exception:
> >>>
> Exception in thread "main" org.apache.axis2.AxisFault: no protocol:
> urn; nested exception is:
> java.net.MalformedURLException: no protocol: urn; nested exception
> is:
>   &n bsp; org.apache.axis2.AxisFault: no protocol: urn; nested
> exception is:
> java.net.MalformedURLException: no protocol: urn
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:245)
> */
>
> If I change the EPR as follows:
>
> EndpointReference epr = new
> EndpointReference("/**https://myservices.test.com/testharness/myapplicationapi.asmx**/";);
>
> and run I get the following exception:
> >>>
> Exception in thread "main" org.apache.axis2.AxisFault: Destination
> Unreachable --> WSE817: The  header must match the Actor
> attribute on this receiver. The  header contained
> "https://myservices.test.com/testharness/myapplicationapi.asmx";
> whereas the Actor attribute was "urn:MyApplicationAPI".
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295)
> <
>
> So I am confused as to how to set the "WSA To" . The rest of the WSA
> headers are getting set properly(i can see this when i print out the
> SOAP Envelope)
>
>
> Any help would be appreciated.
>
> Thanks,
> Sri
>
>
>
>
>
>
>
> Deepal Jayasinghe <[EMAIL PROTECTED]>/* wrote: You have do one more
> thing :) , that is you have to engage addressing in
> order to have addressing functionality , using following code you can do
> that.
> 1. In the latest code
> stb._getServiceClient().engageModule("addressing");
> 2. In 0.94
> stb.engageModule("addressing");
>
> Sricharan Anand wrote:
>
> > Hi,
> >
> > I am using Axis2 version 0.94 to communicate with a remote .Net
> > Webservice. The remote service is using WS-Addressing.
> >
> > I used the wsdl2java tool, gave the WSDL location and generated the
> > stub to communicate with this service. When i execute the stub, it
> > says "Deploying module addressing" - but i am not sure that its
> > hitting the remote service since i don't get any response back.
> >
> > I don't see the WS-A headers(wsa:To, wsa:Action, wsa:MessageID) added
> > in the stub. Are these getting added anywhere in the stub? If not, do
> > i have to add these headers explicitly?
> >
> > I assumed that since WS-A is builtin - these headers should be
> > automatically added.
> >
> > I am new to using Axis2 and any help would be appreciated.
> >
> > Thanks,
> > Sri
> >
> > 
> > Yahoo! Mail
> > Use Photomail
> >
> > to share photos without annoying attachments.
>
>
> -- 
> Thanks,
> Deepal
> 
> ~Future is Open~
>
>
>
> 
> Yahoo! Mail
> Use Photomail
> 
> to share photos without annoying attachments. 


-- 
Thanks,
Deepal

~Future is Open~

Re: WSDL2Java changed WSDL

2006-03-13 Thread Deepal Jayasinghe 
pls read (http://www.developer.com/open/article.php/3589126  item 3)

when we auto generate we can not get back the original WSDL , but I dont
think there will be interoperability problem with that.

Lianghwa Jou wrote:

> Hi,
>
> When followed the used guide and deployed the sample
> "Axis2SampleDocLit.wsdl", I noticed that the wsdl from axis2 service
> page does not match the original wsdl file. Why is that ? Won't this
> cause interoperability problem ?
>
>
> ljou
>
>
>

-- 
Thanks,
Deepal

~Future is Open~

Re: [Axis 2] Exposing an existing java service

2006-03-13 Thread Deepal Jayasinghe 
First you have to write a services.xml , in your case it may like below;


   net.foo.SchedulerServiceWs
  [optionla]
   
  http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
  


Next create a service archive file , then you are done :)


Stuart Robertson wrote:

> We're currently using Axis 1.2 to expose a java web service directly,
> with the WSDL generated at runtime (yes, I know "wsdl first" is the
> best practice :-).  I'm trying to find out how this would be done with
> Axis 2.  I've found plenty of docs about data binding using AXIOM and
> XmlBeans, but haven't seen anything describing this sort of
> transparent binding.  Here's how we're setting up Axis 1.2 to do what
> I'm hoping to also do using Axis 2 (this is from our server-config.wsdd):
>
>  
>   
>   
>   
>   
>   urn:FooService
>languageSpecificType="java:net.foo.ScheduleInfoTO"/>
>  


-- 
Thanks,
Deepal

~Future is Open~

Re: Attachment Exception: End of physical stream

2006-03-13 Thread Rodrigo Ruiz 

Hi Dave, maybe the following link can be of help for your problem :-)

http://wiki.apache.org/ws/FrontPage/Axis/AttachmentProblems

Regards,
Rodrigo Ruiz