Re: /services/ intermittent display

[Mike Barton]

WSABI, like Axis, lives within the context of the webapp. So, it is 
possible to have multiple instances under a single web container.


--Mike

Michael Oliver wrote:

Great, what about more than one?

We have a Component Framework where each Component is a stand alone
webapp and each component has its own server-config.wsdd 


Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]

-Original Message-
From: Mike Barton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:51 PM

To: axis-user@ws.apache.org
Subject: Re: /services/ intermittent display

Michael,

Yes... you can configure WSABI to read (and modify) arbitrary wsdd 
files.  Simply open "wsabi-configure.properties" file under 
/WEB-INF/classes directory of WSABI with your favorite editor and modify


the following properties:

providerClass=org.allesta.wsabi.axis.configure.provider.AxisFileProvider
wsddConfigPath=
wsddConfigName=

Note that this assumes WSABI app has read (and write) access to 
server-config.wsdd file.


--Mike.

Michael Oliver wrote:


Mike,

WSAbi looks great, however it looks like it only works with axis
installed as a stand alone application at /webapps/axis/ 


I have axis added to existing webapp at a different path, can WSAbi be
configured for that?

Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]

-Original Message-
From: Mike Barton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:16 PM

To: axis-user@ws.apache.org
Subject: Re: /services/ intermittent display

Michael,

Try using WSABI, which allows you manage Axis via a simple web based 
GUI.  This should get you going really fast.  WSABI is available at:


Download: http://sourceforge.net/projects/wsabi4axis
Information: http://www.allesta.com
Live Demo: http://demo.wsabi.org


--Mike


Michael Oliver wrote:


I have built and deployed a web service as part of an existing Web 
Application.




I deployed the web service using the AdminClient and deploy.wsdd



The Web Service is accessible and 
/services/AlariusAssignmentsServicces?wsdl works


And the service methods are accessible and also work.



What puzzles me is that before I did the AdminClient deploy of the 
deploy.wsdd I got a page at /services/ that said




"No service is available at this URL"



After I did the AdminClient deploy.wsdd I saw the attached 
server-config.wsdd and /services/ alone gave a display that showed the




services and links to get the wsdl



But after restarting Tomcat, the services still work, but the page at 
/services/ has reverted to "No service is available at this URL"




Log4j debug org.apache.axis shows that AxisServlet is running and 
appears to be processing through the server-config.wsdd but the


display 




doesn't change.



I would like to get that page display running again for demo purposes 
and while it doesn't seem to affect the processing of the web


services, 




it is a comfort thing that if the display shows its there, I may be


able 




to skip actually exercising it depending on the audience for the demo.



Michael Oliver

CTO

Alarius Systems LLC

6800 E. Lake Mead Blvd, #1096

Las Vegas, NV 89156

Phone:(702)643-7425

Fax:(702)974-0341

*Note new email changed from [EMAIL PROTECTED]

Re: Basic Authentication

[huagang]

I guess,
maybe you can try to set  "username"  in wsdd file like

  

and set  "passwd" in   users.lst file


致
礼！
 
 
?  　　huagang
{/-◎◎-\}  [EMAIL PROTECTED]
 ( (oo) )   　　2005-05-26
?
62125151-6226
  
才智，德之资也；德者，才之师也

=== 2005-05-25 05:18:00 您在来信中写道：===

>Hi,
> 
> I'm trying to access Microsoft sharepoint webservice  from an axis
>client. I need to authenticate using Basic /NTLM authentication. I'm
>trying to set username and password 
>call.setUsername("username");
>call.setPassword("passwd");
> 
>I also tried -
>call.setProperty("USERNAME_PROPERTY", "username");
>call.setProperty("PASSWORD_PROPERTY", "password");
> 
>I still get 401 error Please help me how to deal with this. I have also
>attached the code and error below.
> 
>Thanks.
>Jyothi
> 
>
>
>--
>log4j:WARN No appenders could be found for logger
>(org.apache.axis.i18n.ProjectResourceBundle)
>log4j:WARN Please initialize the log4j system properly.
>AxisFault
> faultCode: {http://xml.apache.org/axis/}HTTP
> faultSubcode:
> faultString: (401)Unauthorized
> faultActor:
> faultNode:
> faultDetail:
>{}:return code:  401
>401 Unauthorized
>{http://xml.apache.org/axis/}HttpErrorCode:401
> 
>(401)Unauthorized
>at
>org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java
>:732)
>at
>org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
>at
>org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
>ava:32)
>at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>at org.apache.axis.client.Call.invoke(Call.java:2748)
>at org.apache.axis.client.Call.invoke(Call.java:2424)
>at org.apache.axis.client.Call.invoke(Call.java:2347)
>at org.apache.axis.client.Call.invoke(Call.java:1804)
>at SoapWsdlClient.(SoapWsdlClient.java:23)
>at SoapWsdlClient.main(SoapWsdlClient.java:36)
>Press any key to continue . . .
> 
> 
>
>
>--
> 
> 
> 
>import java.net.*;
>import org.apache.axis.client.*;
>import javax.xml.namespace.*;
> 
> 
>public class SoapWsdlClient
>{
>public SoapWsdlClient()
>{
>try
>{
> 
> 
>String endPointAddress =
>"http:///_vti_bin/search.asmx";
>Service service = new Service();
>Call call = ( Call )service.createCall();
>call.setTargetEndpointAddress( endPointAddress );
>call.setUsername("username");
>call.setPassword("passwd");
> 
>call.setSOAPActionURI("urn:Microsoft.Search/Query");
>call.setOperationName( new
>QName("urn:Microsoft.Search.Query", "Query") );
>String returned = ( String) call.invoke( new Object[] { "
>xmlns=\"urn:Microsoft.Search.Query\" Revision=\"1000\">domain=\"QDomain\">urn:Microsoft.Search.Respon
>se.Document.Documentlanguage=\"en-US\" type=\"STRING\">cannot
>print1500
>" } );
>System.out.println( "Soap returned: " + returned );
> 
> 
>}
>catch (Exception e)
>{
>e.printStackTrace();
>}
>}
> 
>public static void main(String[] args)
>{
>SoapWsdlClient SoapWsdlClient = new SoapWsdlClient();
>}
>}
> 
>
>-
>Jyothishree Honnavalli
>RightAnswers, LLC
>67 Walnut Avenue
>Suite 210
>Clark, NJ 07066
>Ph: 732-396-9010 Ext. 167
>Fax 732-396-9011
>
>-
> 
>
>
>
>AEROSPACE?€INFORMATION?€CO., LTD.
> virus-free and secure email 
>

= = = = = = = = = = = = = = = = = = = =





AEROSPACE　INFORMATION　CO., LTD.
 virus-free and secure email 

Axis 1.2 servlet client fails.

[Bob Carpenter]

Hi,

I use Axis 1.2, JVM 1.4.2, WinXP.

I'm having a problem with making some soap client calls from within a
servlet. These are the three services I call:

http://samples.gotdotnet.com/quickstart/aspplus/samples/services/MathService
/VB/MathService.asmx?WSDL
http://dev.fargeo.com/WebServices/1138_01_Nimblus_KingCo/MapServer.asmx?WSDL
https://secure.webiris.com/IRISWebServices/ValidateIRISUser/ValidateIRISUser
.asmx?WSDL

All services work fine if used in a desktop (non-servlet) client, but if I
call the services from a servlet client (Struts Action or Form classes) then
the MapServer and ValidateIRISUser services both get a result of null (for
example [ns1:getMapByCenterPointResult: null]) BUT the MathService work fine
in all cases.

I've tried getting this to work with JBoss 3.22, JBoss 4.02, and Weblogic
8.1 - same results each time.

I must be missing something fundamental about calling SOAP services from
servlets?

Any ideas?

Thanks,

--BobC

RE: Weblogic 8.1.2 and Axis 1.2

[Bob Carpenter]

Hi Sam,

It seems to be working OK. I can access (most) soap providers without
problem. I say most because I will be submitting a question to the list soon
about some problems my client calls are having, but I don't think the
problems are related to using Axis the way that I am. I'm only working in
SOAP client mode, not sure what would happen if I were to setup a service.

I do plan to use weblogic soap services at some point, but haven't needed to
yet.

--BobC


-Original Message-
From: Ayers, Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 10:42 AM
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Interesting...

Doesn't putting the jar files ahead in the startweblogic classpath cause the
weblogic server to pick up the classes in the axis jar files (instead of
usting its own)?

If so, does weblogic seem to behave OK running the axis classes instead of
its own? Or, do you just avoid using weblogic web services if you use this
technique?

Sam

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 1:27 PM
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

I was NOT able to get it to work with the web.xml having this:


true
/container-descriptor>

If you remove it, and place the axis jars like I mentioned below, then it
should work.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 8:02 AM
To: 'axis-user@ws.apache.org'
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Bob,

Thanks for the reply but unfortunately  no joy.
I did as you suggested but that just introduced problems for my
initialisation servlet.
Once change since I originally posted is that I replaced the
NoClassDefFoundError with a NullPointerException by also deploying the
wsdl4j.jar along with the other five jars (axis.jar saaj.jar
commons-logging.jar commons-discovery.jar jaxrpc.jar) in my WEB-INF\lib
directory.
My server now appears to get further that it did before with my client
getting back an AxisFault with a faultCode of Server.userException.  The
start of the faultDetail is
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.axis.message.MessageElement.addTextNode(Ljava.lang.String;)Ljavax
.xml.soap.SOAPElement;(MessageElement.java:1387)
at
org.apache.axis.message.SOAPHandler.addTextNode()V(SOAPHandler.java:148)
at
org.apache.axis.message.SOAPHandler.endElement(Ljava.lang.String;Ljava.lang.
String;Lorg.apache.axis.encoding.DeserializationContext;)V(SOAPHandler.java:
112)
at org.apache.axis.encoding.DeserializationContext.endElement
Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DeserializationCont
ext.java:1087)
at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement
.

I did find in JIRA a bug with Axis 1.2RC2 that seems similar but from what i
can read that should now be fixed so I'm really at a loss at how to proceed.

I don't want to add an APP-INF directory to my deployed ear file as that is
weblogic specific and I want the structure of my file to be generic so it
can be deployed on either weblogic or websphere.

Aoife

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 15:01
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars being
in the WEB-INF/lib should work, but doesn't. So, someone suggested the
brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there and
added the six in the CLASSPATH of the app's startWebLogic.cmd and it now
works.

If anyone knows a more elegant way to bundle these in the EAR, please let
share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is the

RE: /services/ intermittent display

[Michael Oliver]

Great, what about more than one?

We have a Component Framework where each Component is a stand alone
webapp and each component has its own server-config.wsdd 

Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]

-Original Message-
From: Mike Barton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:51 PM
To: axis-user@ws.apache.org
Subject: Re: /services/ intermittent display

Michael,

Yes... you can configure WSABI to read (and modify) arbitrary wsdd 
files.  Simply open "wsabi-configure.properties" file under 
/WEB-INF/classes directory of WSABI with your favorite editor and modify

the following properties:

providerClass=org.allesta.wsabi.axis.configure.provider.AxisFileProvider
wsddConfigPath=
wsddConfigName=

Note that this assumes WSABI app has read (and write) access to 
server-config.wsdd file.

--Mike.

Michael Oliver wrote:
> Mike,
> 
> WSAbi looks great, however it looks like it only works with axis
> installed as a stand alone application at /webapps/axis/ 
> 
> I have axis added to existing webapp at a different path, can WSAbi be
> configured for that?
> 
> Michael Oliver
> CTO
> Alarius Systems LLC
> 6800 E. Lake Mead Blvd, #1096
> Las Vegas, NV 89156
> Phone:(702)643-7425
> Fax:(702)974-0341
> *Note new email changed from [EMAIL PROTECTED]
> 
> -Original Message-
> From: Mike Barton [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 25, 2005 3:16 PM
> To: axis-user@ws.apache.org
> Subject: Re: /services/ intermittent display
> 
> Michael,
> 
> Try using WSABI, which allows you manage Axis via a simple web based 
> GUI.  This should get you going really fast.  WSABI is available at:
> 
> Download: http://sourceforge.net/projects/wsabi4axis
> Information: http://www.allesta.com
> Live Demo: http://demo.wsabi.org
> 
> 
> --Mike
> 
> 
> Michael Oliver wrote:
> 
>>I have built and deployed a web service as part of an existing Web 
>>Application.
>>
>> 
>>
>>I deployed the web service using the AdminClient and deploy.wsdd
>>
>> 
>>
>>The Web Service is accessible and 
>>/services/AlariusAssignmentsServicces?wsdl works
>>
>>And the service methods are accessible and also work.
>>
>> 
>>
>>What puzzles me is that before I did the AdminClient deploy of the 
>>deploy.wsdd I got a page at /services/ that said
>>
>> 
>>
>>"No service is available at this URL"
>>
>> 
>>
>>After I did the AdminClient deploy.wsdd I saw the attached 
>>server-config.wsdd and /services/ alone gave a display that showed the
> 
> 
>>services and links to get the wsdl
>>
>> 
>>
>>But after restarting Tomcat, the services still work, but the page at 
>>/services/ has reverted to "No service is available at this URL"
>>
>> 
>>
>>Log4j debug org.apache.axis shows that AxisServlet is running and 
>>appears to be processing through the server-config.wsdd but the
> 
> display 
> 
>>doesn't change.
>>
>> 
>>
>>I would like to get that page display running again for demo purposes 
>>and while it doesn't seem to affect the processing of the web
> 
> services, 
> 
>>it is a comfort thing that if the display shows its there, I may be
> 
> able 
> 
>>to skip actually exercising it depending on the audience for the demo.
>>
>> 
>>
>>Michael Oliver
>>
>>CTO
>>
>>Alarius Systems LLC
>>
>>6800 E. Lake Mead Blvd, #1096
>>
>>Las Vegas, NV 89156
>>
>>Phone:(702)643-7425
>>
>>Fax:(702)974-0341
>>
>>*Note new email changed from [EMAIL PROTECTED]
>>
>> 
>>
> 
> 
> 
> 
> 

Re: /services/ intermittent display

[Mike Barton]

Michael,

Yes... you can configure WSABI to read (and modify) arbitrary wsdd 
files.  Simply open "wsabi-configure.properties" file under 
/WEB-INF/classes directory of WSABI with your favorite editor and modify 
the following properties:


providerClass=org.allesta.wsabi.axis.configure.provider.AxisFileProvider
wsddConfigPath=
wsddConfigName=

Note that this assumes WSABI app has read (and write) access to 
server-config.wsdd file.


--Mike.

Michael Oliver wrote:

Mike,

WSAbi looks great, however it looks like it only works with axis
installed as a stand alone application at /webapps/axis/ 


I have axis added to existing webapp at a different path, can WSAbi be
configured for that?

Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]

-Original Message-
From: Mike Barton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:16 PM

To: axis-user@ws.apache.org
Subject: Re: /services/ intermittent display

Michael,

Try using WSABI, which allows you manage Axis via a simple web based 
GUI.  This should get you going really fast.  WSABI is available at:


Download: http://sourceforge.net/projects/wsabi4axis
Information: http://www.allesta.com
Live Demo: http://demo.wsabi.org


--Mike


Michael Oliver wrote:

I have built and deployed a web service as part of an existing Web 
Application.




I deployed the web service using the AdminClient and deploy.wsdd



The Web Service is accessible and 
/services/AlariusAssignmentsServicces?wsdl works


And the service methods are accessible and also work.



What puzzles me is that before I did the AdminClient deploy of the 
deploy.wsdd I got a page at /services/ that said




"No service is available at this URL"



After I did the AdminClient deploy.wsdd I saw the attached 
server-config.wsdd and /services/ alone gave a display that showed the




services and links to get the wsdl



But after restarting Tomcat, the services still work, but the page at 
/services/ has reverted to "No service is available at this URL"




Log4j debug org.apache.axis shows that AxisServlet is running and 
appears to be processing through the server-config.wsdd but the


display 


doesn't change.



I would like to get that page display running again for demo purposes 
and while it doesn't seem to affect the processing of the web


services, 


it is a comfort thing that if the display shows its there, I may be


able 


to skip actually exercising it depending on the audience for the demo.



Michael Oliver

CTO

Alarius Systems LLC

6800 E. Lake Mead Blvd, #1096

Las Vegas, NV 89156

Phone:(702)643-7425

Fax:(702)974-0341

*Note new email changed from [EMAIL PROTECTED]

RE: /services/ intermittent display

[Michael Oliver]

Mike,

WSAbi looks great, however it looks like it only works with axis
installed as a stand alone application at /webapps/axis/ 

I have axis added to existing webapp at a different path, can WSAbi be
configured for that?

Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from [EMAIL PROTECTED]

-Original Message-
From: Mike Barton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:16 PM
To: axis-user@ws.apache.org
Subject: Re: /services/ intermittent display

Michael,

Try using WSABI, which allows you manage Axis via a simple web based 
GUI.  This should get you going really fast.  WSABI is available at:

Download: http://sourceforge.net/projects/wsabi4axis
Information: http://www.allesta.com
Live Demo: http://demo.wsabi.org


--Mike


Michael Oliver wrote:
> I have built and deployed a web service as part of an existing Web 
> Application.
> 
>  
> 
> I deployed the web service using the AdminClient and deploy.wsdd
> 
>  
> 
> The Web Service is accessible and 
> /services/AlariusAssignmentsServicces?wsdl works
> 
> And the service methods are accessible and also work.
> 
>  
> 
> What puzzles me is that before I did the AdminClient deploy of the 
> deploy.wsdd I got a page at /services/ that said
> 
>  
> 
> "No service is available at this URL"
> 
>  
> 
> After I did the AdminClient deploy.wsdd I saw the attached 
> server-config.wsdd and /services/ alone gave a display that showed the

> services and links to get the wsdl
> 
>  
> 
> But after restarting Tomcat, the services still work, but the page at 
> /services/ has reverted to "No service is available at this URL"
> 
>  
> 
> Log4j debug org.apache.axis shows that AxisServlet is running and 
> appears to be processing through the server-config.wsdd but the
display 
> doesn't change.
> 
>  
> 
> I would like to get that page display running again for demo purposes 
> and while it doesn't seem to affect the processing of the web
services, 
> it is a comfort thing that if the display shows its there, I may be
able 
> to skip actually exercising it depending on the audience for the demo.
> 
>  
> 
> Michael Oliver
> 
> CTO
> 
> Alarius Systems LLC
> 
> 6800 E. Lake Mead Blvd, #1096
> 
> Las Vegas, NV 89156
> 
> Phone:(702)643-7425
> 
> Fax:(702)974-0341
> 
> *Note new email changed from [EMAIL PROTECTED]
> 
>  
> 

Re: /services/ intermittent display

[Mike Barton]

Michael,

Try using WSABI, which allows you manage Axis via a simple web based 
GUI.  This should get you going really fast.  WSABI is available at:


Download: http://sourceforge.net/projects/wsabi4axis
Information: http://www.allesta.com
Live Demo: http://demo.wsabi.org


--Mike


Michael Oliver wrote:
I have built and deployed a web service as part of an existing Web 
Application.


 


I deployed the web service using the AdminClient and deploy.wsdd

 

The Web Service is accessible and 
/services/AlariusAssignmentsServicces?wsdl works


And the service methods are accessible and also work.

 

What puzzles me is that before I did the AdminClient deploy of the 
deploy.wsdd I got a page at /services/ that said


 


“No service is available at this URL”

 

After I did the AdminClient deploy.wsdd I saw the attached 
server-config.wsdd and /services/ alone gave a display that showed the 
services and links to get the wsdl


 

But after restarting Tomcat, the services still work, but the page at 
/services/ has reverted to “No service is available at this URL”


 

Log4j debug org.apache.axis shows that AxisServlet is running and 
appears to be processing through the server-config.wsdd but the display 
doesn’t change.


 

I would like to get that page display running again for demo purposes 
and while it doesn’t seem to affect the processing of the web services, 
it is a comfort thing that if the display shows its there, I may be able 
to skip actually exercising it depending on the audience for the demo.


 


Michael Oliver

CTO

Alarius Systems LLC

6800 E. Lake Mead Blvd, #1096

Las Vegas, NV 89156

Phone:(702)643-7425

Fax:(702)974-0341

*Note new email changed from [EMAIL PROTECTED]

 

Problem adding new transport & handler

[Eric . Hardesty]

I'm trying to add a new transport, which I am able
to configure and have the endpoint recognized but I'm not getting my Sender
called since based on traces no chain is being added.  I am trying
to follow the JMS example since this is going to be SOAP over some endpoint
specific communication method.  All the examples I've seen have the
client setting the transport before the Call process is created but I didn't
think that was necessary based on the jms example.  Is there any "magic"
that needs to be done or should it be as simple as including the 
& 
in both server-config.wsdd and client-config.wsdd and then setting the
endpoint in the call to be "test://whateverisneeded"?  Thanks.

Eric

RE: .NET and attachments to Axis....

[Jeremy Hynoski]

You will need WSE2.0 and Visual Studio 2003 to do decent DIME attachments,
but here's what I use:

Note: this is using:
using Microsoft.Web.Services2.Attachments;
using Microsoft.Web.Services2.Dime; 

 DimeAttachment attach = new
DimeAttachment("text/xml",TypeFormat.MediaType,@"C:mypathnameMyUploadFile.xm
l");
 attach.Id = Guid.NewGuid().ToString();
 mySoapClient.RequestSoapContext.Attachments.Add(attach);
 ReferencedBinary outgoingDoc = new ReferencedBinary();
 outgoingDoc.location = attach.Id;
 DocumentSubmissionResponse response =
mySoapClient.myRoutineThatUsesAttachments(param1,param2,outgoingDoc);

Note, you will need to ensure Axis server can accept DIME. .NET cannot speak
MIME out of the box.

Jeremy

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 12:46 PM
To: axis-user@ws.apache.org
Subject: .NET and attachments to Axis

Anyone have an example of how to send an attachment in a .NET client to send
to an Axis Server?

I don't care what .NET language since they are pretty much similar.

  Cliff

---
Clifford Grimm
Centera Integration Architect
EMC Centera Engineering
EMC² 
Where Information Lives
* Office: 508-249-5159 (toll free 877-362-2887 x45159)
* Cell: 978-618-1336
* Fax: 508-249-5495
* E-mail: [EMAIL PROTECTED] 
*  Instant Messaging: [EMAIL PROTECTED]

.NET and attachments to Axis....

[Grimm_Clifford]

Anyone have an example of how to send an attachment in a .NET client to send
to an Axis Server?

I don't care what .NET language since they are pretty much similar.

  Cliff

---
Clifford Grimm 
Centera Integration Architect 
EMC Centera Engineering 
EMC²   
Where Information Lives 
* Office: 508-249-5159 (toll free 877-362-2887 x45159) 
* Cell: 978-618-1336
* Fax: 508-249-5495
* E-mail: [EMAIL PROTECTED]  
*  Instant Messaging: [EMAIL PROTECTED]

/services/ intermittent display

[Michael Oliver]

I have built and deployed a web service as
part of an existing Web Application.

 

I deployed the web service using the AdminClient
and deploy.wsdd 

 

The Web Service is accessible and
/services/AlariusAssignmentsServicces?wsdl works 

And the service methods are accessible and
also work.

 

What puzzles me is that before I did the AdminClient
deploy of the deploy.wsdd I got a page at /services/ that said 

 

“No service is available at this URL”

 

After I did the AdminClient deploy.wsdd I
saw the attached server-config.wsdd and /services/ alone gave a display that
showed the services and links to get the wsdl 

 

But after restarting Tomcat, the services
still work, but the page at /services/ has reverted to “No service is
available at this URL”

 

Log4j debug org.apache.axis shows that AxisServlet
is running and appears to be processing through the server-config.wsdd but the
display doesn’t change.

 

I would like to get that page display
running again for demo purposes and while it doesn’t seem to affect the
processing of the web services, it is a comfort thing that if the display shows
its there, I may be able to skip actually exercising it depending on the
audience for the demo.

 



Michael Oliver

CTO

Alarius Systems LLC

6800 E. Lake Mead Blvd, #1096

Las Vegas, NV 89156

Phone:(702)643-7425

Fax:(702)974-0341

*Note new email changed from
[EMAIL PROTECTED]



 

RE: multiRef namespace question

[Mark Ford]

Can you clarify what you mean by "children of the accessor elements
correspond to the structure defined in the schema that defines the accessor
element type structures." 

Do you mean that they correspond to the structure irrespective of namespace
qualification? 


-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 10:07 AM
To: axis-user@ws.apache.org; Jan Delannoy
Subject: Re: multiRef namespace question

Actually, it's the opposite. If you specify elementFormDefault="qualified",
then all elements defined within the schema by default are namespace
qualified. And to override the default, you would need to specify
form="unqualified" on the specific element.

Note that when using RPC style, you don't have a schema for the SOAP element
structure. The only thing the schema specifies is type information. The RPC
convention sets namespaces according to these
rules:

- the child element of the  is a generated element (the method
name element) which has a namespace equal to the value of the namespace
attribute in the  definition and a local name equal to the value of
the name attribute in the  definition.
- the parameter accesssor elements (the children of the method name
element) are generated elements. These elements are always unqualified.
Their local names are equal to the value of the name attribute on the 
definition.
- children of the accessor elements correspond to the structure defined in
the schema that defines the accessor element type structures.

Anne

On 5/25/05, Jan Delannoy <[EMAIL PROTECTED]> wrote:
> If I'm not mistaking, when the schema elementFormDefault is set to 
> qualified this only means that the global element declarations (i.e.
> those that are direct children of the schema element) should be 
> namespace qualified.  The local declarations (defined inside other 
> elements or complexTypes) default back to not qualified.  So unless 
> the local elements specifically have the form="qualified" attribute 
> declared on them, they are not namespace qualified. I've noticed that 
> Axis handles this by 'unsetting' the namespace on local elements, like
> this:
> 
> http://some.namespace.uri";>
>   
> ...
>   
> 
> 
> I've also noticed that some tools don't like these kinds of XMLs. In 
> my case I solved it by explicitly setting the form="qualfied" on my 
> local declarations too.
> 
> Hope this helps...
> Jan
> 
> 
> 
> On 5/24/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> > In my application, I am deserializing the incoming RPC encoded 
> > messages into a DOM and then validating the DOM against the schema. 
> > I'm not using any generated code in this process, rather I register 
> > a custom deserializer to handle complex types and produce a Document.
> >
> > My problem is that validation fails in cases where the 
> > elementFormDefault for the schema is set to qualified. This requires 
> > that all child elements of a given element have the same namespace 
> > as their parent. The messages that I receive from axis generated 
> > drivers do not provide any namespace information for the multiRef
elements.
> >
> > Here's the output from the soap monitor:
> >
> > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >   
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> > 
> >  
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="ns1:DocumentDataIn"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> > 
> > 
> >  
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="xsd:float"
> >
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>123.45
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="xsd:int"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>10
> >   
> >
> >
> > The resulting DOM looks like this:
> >
> > 
> >   10
> >   123.45
> > 
> >
> > But it should look like this:
> >
> >  > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> >   10
> >   123.45
> > 
> >
> > It seems to me that the inbound message is wrong since there is no 
> > way to convey to the receiver that data1 and data2 are qualified. 
> > The SOAP 1.1 spec clearly states that the accessor elements that 
> > contain the href should not be namespace qualified but it also has 
> > an example that shows a namespace prefix being used in the multifRef 
> > encoding element 
> > (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383520). The 
> > SerializationContext in axis uses the same QName for multiRefs and 
> > it has the empty namespace. It seems like there should be a way for the
multiR

RE: Weblogic 8.1.2 and Axis 1.2

[Ayers, Sam]

Interesting...

Doesn't putting the jar files ahead in the startweblogic classpath cause the 
weblogic server to pick up the classes in the axis jar files (instead of usting 
its own)?

If so, does weblogic seem to behave OK running the axis classes instead of its 
own? Or, do you just avoid using weblogic web services if you use this 
technique?

Sam

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 1:27 PM
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

I was NOT able to get it to work with the web.xml having this:


true
/container-descriptor>

If you remove it, and place the axis jars like I mentioned below, then it
should work.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 8:02 AM
To: 'axis-user@ws.apache.org'
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Bob,

Thanks for the reply but unfortunately  no joy.
I did as you suggested but that just introduced problems for my
initialisation servlet.
Once change since I originally posted is that I replaced the
NoClassDefFoundError with a NullPointerException by also deploying the
wsdl4j.jar along with the other five jars (axis.jar saaj.jar
commons-logging.jar commons-discovery.jar jaxrpc.jar) in my WEB-INF\lib
directory.
My server now appears to get further that it did before with my client
getting back an AxisFault with a faultCode of Server.userException.  The
start of the faultDetail is
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.axis.message.MessageElement.addTextNode(Ljava.lang.String;)Ljavax
.xml.soap.SOAPElement;(MessageElement.java:1387)
at
org.apache.axis.message.SOAPHandler.addTextNode()V(SOAPHandler.java:148)
at
org.apache.axis.message.SOAPHandler.endElement(Ljava.lang.String;Ljava.lang.
String;Lorg.apache.axis.encoding.DeserializationContext;)V(SOAPHandler.java:
112)
at org.apache.axis.encoding.DeserializationContext.endElement
Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DeserializationCont
ext.java:1087)
at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement
.

I did find in JIRA a bug with Axis 1.2RC2 that seems similar but from what i
can read that should now be fixed so I'm really at a loss at how to proceed.

I don't want to add an APP-INF directory to my deployed ear file as that is
weblogic specific and I want the structure of my file to be generic so it
can be deployed on either weblogic or websphere.

Aoife

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 15:01
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars being
in the WEB-INF/lib should work, but doesn't. So, someone suggested the
brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there and
added the six in the CLASSPATH of the app's startWebLogic.cmd and it now
works.

If anyone knows a more elegant way to bundle these in the EAR, please let
share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be privileged
and is intended only for the user of the recipient named above.  If you are
not the intended recipient or a representative of the intended recipient,
you have received this e-mail in error and must not copy, use or disclose
the contents of this e-mail to anybody else.  If you have received this
e-mail in error, please notify the sender immediately by return e-mail and
permanently delete the copy you receiv

RE: Weblogic 8.1.2 and Axis 1.2

[Bob Carpenter]

Hi Aoife,

I was NOT able to get it to work with the web.xml having this:


true
/container-descriptor>

If you remove it, and place the axis jars like I mentioned below, then it
should work.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 8:02 AM
To: 'axis-user@ws.apache.org'
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Bob,

Thanks for the reply but unfortunately  no joy.
I did as you suggested but that just introduced problems for my
initialisation servlet.
Once change since I originally posted is that I replaced the
NoClassDefFoundError with a NullPointerException by also deploying the
wsdl4j.jar along with the other five jars (axis.jar saaj.jar
commons-logging.jar commons-discovery.jar jaxrpc.jar) in my WEB-INF\lib
directory.
My server now appears to get further that it did before with my client
getting back an AxisFault with a faultCode of Server.userException.  The
start of the faultDetail is
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.axis.message.MessageElement.addTextNode(Ljava.lang.String;)Ljavax
.xml.soap.SOAPElement;(MessageElement.java:1387)
at
org.apache.axis.message.SOAPHandler.addTextNode()V(SOAPHandler.java:148)
at
org.apache.axis.message.SOAPHandler.endElement(Ljava.lang.String;Ljava.lang.
String;Lorg.apache.axis.encoding.DeserializationContext;)V(SOAPHandler.java:
112)
at org.apache.axis.encoding.DeserializationContext.endElement
Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DeserializationCont
ext.java:1087)
at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement
.

I did find in JIRA a bug with Axis 1.2RC2 that seems similar but from what i
can read that should now be fixed so I'm really at a loss at how to proceed.

I don't want to add an APP-INF directory to my deployed ear file as that is
weblogic specific and I want the structure of my file to be generic so it
can be deployed on either weblogic or websphere.

Aoife

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 15:01
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars being
in the WEB-INF/lib should work, but doesn't. So, someone suggested the
brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there and
added the six in the CLASSPATH of the app's startWebLogic.cmd and it now
works.

If anyone knows a more elegant way to bundle these in the EAR, please let
share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be privileged
and is intended only for the user of the recipient named above.  If you are
not the intended recipient or a representative of the intended recipient,
you have received this e-mail in error and must not copy, use or disclose
the contents of this e-mail to anybody else.  If you have received this
e-mail in error, please notify the sender immediately by return e-mail and
permanently delete the copy you received.  This e-mail has been swept for
computer viruses.  However, you should carry out your own virus checks.
Registered in Ireland, No. 205721.  http://www.FINEOS.com
**

namespace prefix question

[Jan Delannoy]

Hi,

I'm using an Axis generated stub class to call a web service. The
generated messages use namespace prefixes like ns1, ns2, ns3, etc.
even when it's the same namespace.  Can I force Axis to use a
namespace prefix of my choice for a given namespace? I'm using Axis
1.2 final.

Many thanks,
Jan

I need a Client .Net with Axis web service

[Pippo Plutone]

Hi all,

I have a AXIS web service (with provider="java:MSG" and not 
provider="java:RPC") and my method of web service is:


public Document echoDocument(Document doc) throws RemoteException {
   return doc;
}

I want a client .Net that use this web service?
I've searched everywhere but nothing.

Can you help me?

thanks Pasquy.

_
Ricerche online più semplici e veloci con MSN Toolbar! 
http://toolbar.msn.it/

complex type (help please)

[Omar Bennani]

what can i do to use complex type in my client java
side ?
should I use wsdl2java ?
help






_ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, 
photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com
http://schemas.xmlsoap.org/wsdl/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; name="ICalculservice" targetNamespace="http://tempuri.org/"; xmlns:tns="http://tempuri.org/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:ns1="urn:MyTypes">
  

  

  

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

  
  

  
  
  
  
  
  
  
  
  
  

  

  
  


  
  

  
  

  
  

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

  
  
http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:CalculIntf-ICalcul"/>
  
  
http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:CalculIntf-ICalcul"/>
  

  
  

  http://localhost:8088/cgi-bin/Project3.exe/soap/ICalcul"/>

  

Using Axis Fault

[Ferruh Zamangoer]

Hi,

 

I want to know if the steps which use to throw a
Fault is right. I write a interface in with two methods like:

 

1.)

public interface CUserService

{

    public boolean addUser(String
pseudonym, User user) throws CUserException;

    public boolean removeUser(String
pseudonym) throws CUserException;

}

 

2.) In the class CUserException I write the following:

public class CUserException extends RemoteException

{

    public
 CUserException(String message)

    {

        super(message);

}

}

 

3.)  After that I use Java2WSDL and generate my
wsdl file.

4.) I use WSDL2Java to generate the client and server
stubs. I see that in the wsdd file is an entry like:

 



   
xmlns:ns="http://exception.confuoco"

   
qname="ns:CUserException"

   
type="java:confuoco.exception.CUserException"

   
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"

   
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"

   
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"

 
/>

5.) Then I deploy the
service. 

5.) I see that my CUserException
class was overwritten by WSDL2Java.

6.) I write in my CUserServiceSoapBindingImpl a “if else” to test the fault like: 

 

public boolean addUser(java.lang.String pseudonym,
confuoco.webservice.User user) throws confuoco.exception.CUserException {

    

        if(user
!= null)

        {

        System.out.println("User
is not null");

        }

        else

        {

        System.out.println("User is null ");

        CUserException
cue = new CUserException();

        cue.setFaultString("User
object is null ");

        throw
cue;

        }

        

        return
false;

    }

 

7.) on the Client side I catch the Axis Fault with:

 

try

    {

   

   CUserServiceServiceLocator
locator = new CUserServiceServiceLocator();

   CUserService
cUserService = locator.getCUserService();

   User
user = null;

   cUserService.addUser("Test",
null);

   

    }

    

    catch(ServiceException
se)

    {

   se.printStackTrace();

    }

    catch(AxisFault
af)

    {

   System.out.println("AXisFault:
" + af.getFaultString());

   

    }

 

Console: 

Ouput: User object is null.

 

 

Is that the right way to throw a Fault and catch If
 I use cue.setMessage ("User object is null "); instead cue.setFaultString("User
object is null "); and want to catch it on the client side I become for
the result not the string a null object is returned? 

 

 

Thanks for any help.

 

Regards

Ferruh

 

 








CUserException.java
Description: Binary data

Re: Basic Authentication

[YIXING MA]

Hi guys,
 
Can anyone tells me how to reject a soap message in 
Axis Handler?
 
Thanks,
Yixing Ma 

RE: Weblogic 8.1.2 and Axis 1.2

[Aoife Kavanagh (Ext. 987)]

Hi Bob,

Thanks for the reply but unfortunately  no joy.
I did as you suggested but that just introduced problems for my
initialisation servlet.
Once change since I originally posted is that I replaced the
NoClassDefFoundError with a NullPointerException by also deploying the
wsdl4j.jar along with the other five jars (axis.jar saaj.jar
commons-logging.jar commons-discovery.jar jaxrpc.jar) in my WEB-INF\lib
directory. 
My server now appears to get further that it did before with my client
getting back an AxisFault with a faultCode of Server.userException.  The
start of the faultDetail is
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.axis.message.MessageElement.addTextNode(Ljava.lang.String;)Ljavax
.xml.soap.SOAPElement;(MessageElement.java:1387)
at
org.apache.axis.message.SOAPHandler.addTextNode()V(SOAPHandler.java:148)
at
org.apache.axis.message.SOAPHandler.endElement(Ljava.lang.String;Ljava.lang.
String;Lorg.apache.axis.encoding.DeserializationContext;)V(SOAPHandler.java:
112)
at org.apache.axis.encoding.DeserializationContext.endElement
Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DeserializationCont
ext.java:1087)
at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement
.

I did find in JIRA a bug with Axis 1.2RC2 that seems similar but from what i
can read that should now be fixed so I'm really at a loss at how to proceed.

I don't want to add an APP-INF directory to my deployed ear file as that is
weblogic specific and I want the structure of my file to be generic so it
can be deployed on either weblogic or websphere.

Aoife

-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 15:01
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars being
in the WEB-INF/lib should work, but doesn't. So, someone suggested the
brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there and
added the six in the CLASSPATH of the app's startWebLogic.cmd and it now
works.

If anyone knows a more elegant way to bundle these in the EAR, please let
share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be privileged
and is intended only for the user of the recipient named above.  If you are
not the intended recipient or a representative of the intended recipient,
you have received this e-mail in error and must not copy, use or disclose
the contents of this e-mail to anybody else.  If you have received this
e-mail in error, please notify the sender immediately by return e-mail and
permanently delete the copy you received.  This e-mail has been swept for
computer viruses.  However, you should carry out your own virus checks.
Registered in Ireland, No. 205721.  http://www.FINEOS.com
**

Re: multiRef namespace question

[Jan Delannoy]

You're right, of course, I'm confusing things again. Global elements
are always qualified, and the elementFormDefault and
attributeFormDefault attributes apply to the local elements.

And I see now that my problem was something completely different than
Marks. The example I gave where the child element unsets the namespace
happened because in my WSDL file I defined the A element as being of a
type TypeA that I was importing from a different namespace and I now
discovered that the schema for the other namespace had
elementFormDefault set to "unqualified".  This is why the B element
had the xmlns="" attribute, as B was a local element in the other
namespace, and as such had to be unqualfied...

Phew, these web service thingies can sure get complex if you ask me... ;-)

Regards,
Jan



On 5/25/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> Actually, it's the opposite. If you specify
> elementFormDefault="qualified", then all elements defined within the
> schema by default are namespace qualified. And to override the
> default, you would need to specify form="unqualified" on the specific
> element.
> 
> Note that when using RPC style, you don't have a schema for the SOAP
> element structure. The only thing the schema specifies is type
> information. The RPC convention sets namespaces according to these
> rules:
> 
> - the child element of the  is a generated element (the
> method name element) which has a namespace equal to the value of the
> namespace attribute in the  definition and a local name equal
> to the value of the name attribute in the  definition.
> - the parameter accesssor elements (the children of the method name
> element) are generated elements. These elements are always
> unqualified. Their local names are equal to the value of the name
> attribute on the  definition.
> - children of the accessor elements correspond to the structure
> defined in the schema that defines the accessor element type
> structures.
> 
> Anne
> 
> On 5/25/05, Jan Delannoy <[EMAIL PROTECTED]> wrote:
> > If I'm not mistaking, when the schema elementFormDefault is set to
> > qualified this only means that the global element declarations (i.e.
> > those that are direct children of the schema element) should be
> > namespace qualified.  The local declarations (defined inside other
> > elements or complexTypes) default back to not qualified.  So unless
> > the local elements specifically have the form="qualified" attribute
> > declared on them, they are not namespace qualified. I've noticed that
> > Axis handles this by 'unsetting' the namespace on local elements, like
> > this:
> >
> > http://some.namespace.uri";>
> >   
> > ...
> >   
> > 
> >
> > I've also noticed that some tools don't like these kinds of XMLs. In
> > my case I solved it by explicitly setting the form="qualfied" on my
> > local declarations too.
> >
> > Hope this helps...
> > Jan
> >
> >
> >
> > On 5/24/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> > > In my application, I am deserializing the incoming RPC encoded messages 
> > > into
> > > a DOM and then validating the DOM against the schema. I'm not using any
> > > generated code in this process, rather I register a custom deserializer to
> > > handle complex types and produce a Document.
> > >
> > > My problem is that validation fails in cases where the elementFormDefault
> > > for the schema is set to qualified. This requires that all child elements 
> > > of
> > > a given element have the same namespace as their parent. The messages 
> > > that I
> > > receive from axis generated drivers do not provide any namespace 
> > > information
> > > for the multiRef elements.
> > >
> > > Here's the output from the soap monitor:
> > >
> > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > >   
> > >   > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> > > 
> > >  
> > >   > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > > xsi:type="ns1:DocumentDataIn"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> > > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> > > 
> > > 
> > >  
> > >   > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > > xsi:type="xsd:float"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>123.45
> > >   > > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > > xsi:type="xsd:int"
> > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>10
> > >   
> > >
> > >
> > > The resulting DOM looks like this:
> > >
> > > 
> > >   10
> > >   123.45
> > > 
> > >
> > > But it should look like this:
> > >
> > >  > > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> > >   10
> > >   123.45
> > > 
> > >

REPOST: Some Questions Regarding Wrapped Literal and Axis

[Sagar Pidaparthi]

HI,

I would appreciate an answer to my questions below please.  

Regards

Sagar  


Hi,

I have a few questions and would appreciate answers from any one.


When I use Wrapped Literal in Axis 1.2, after I generate wsdl using
jav2wsdl and run wsdl2java, the deploy.wsdd file contains classes with
Method names of the service.  It is possible for me deploy my service,
if I delete these entries from deploy.wsdd.  It is my observation, that
the service works fine after deployment.  

Alternatively, I can jar these method name classes and put them in the
class path of the server and then it is possible to deploy my service
which contains all the method entries in the deploy.wsdd.  The service
works fine in this approach too.

My question is, which of these above two approaches is correct or
intended way of deployment?

Secondly, what is the purpose these classes which bear the method names
of the methods in my service?  These entries are not generated for Rpc
style.

I hope somebody can answer these questions.

Regards

Sagar

Complex types with client java

[Omar Bennani]

I have to write a java client to send and receive an
array of object but there is no XSD type to use with
call.addParameter() and
call.setReturnType()
how can i do ? some one has an example ?
help please






_ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, 
photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com
http://schemas.xmlsoap.org/wsdl/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; name="ICalculservice" targetNamespace="http://tempuri.org/"; xmlns:tns="http://tempuri.org/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:ns1="urn:MyTypes">
  

  

  

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

  
  

  
  
  
  
  
  
  
  
  
  

  

  
  


  
  

  
  

  
  

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

  
  
http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:CalculIntf-ICalcul"/>
  
  
http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:CalculIntf-ICalcul"/>
  

  
  

  http://localhost:8088/cgi-bin/Project3.exe/soap/ICalcul"/>

  

Basic Authentication

[Jyothishree Honnavalli]

 

Hi ,

 

I found on apache axis-user mail archives
discussion on Basic authentication. I looked at one of the solutions and tried using the stub as
well…still getting 401 error. Please  let me know how you figured it out.

 

import org.apache.axis.client.*;

import javax.xml.namespace.*;

 

import
com.microsoft.webservices.SharePointPortalServer.WebQueryService.*;

 

 

public class SoapWsdlClient

{

   public String callWebService(String
qry)

 

   {

 

    String
result= null;

       try

       {

 

     QueryServiceLocator os  
= new QueryServiceLocator();

     QueryServiceSoapStub stub =
(QueryServiceSoapStub)   os.getQueryServiceSoap();

 

    stub.setUsername("username");

    stub.setPassword("password");

    result
= stub.query(qry);

    }

    catch
(Exception e)

    {

    e.printStackTrace();

    }

    return result;

   }

 

 

 

    public
static void main(String[] args)

    {

    String
queryxml ="urn:Microsoft.Search.Response.Document.Documentcannot print1500";

    SoapWsdlClient
SoapWsdlClient = new SoapWsdlClient();

    String
result= SoapWsdlClient.callWebService(queryxml);

    System.out.println(result);

    }

 

}

 

 

 

 

-Original Message-
From: Jyothishree Honnavalli 
Sent: Tuesday, May 24, 2005 5:18 PM
To: axis-user@ws.apache.org
Subject: Basic Authentication

 

Hi,

 


I’m trying to access Microsoft sharepoint webservice  from an axis client. I need to authenticate
using Basic /NTLM authentication. I’m trying to set username and password


    call.setUsername("username");

    call.setPassword("passwd");

 

I also tried –

    call.setProperty("USERNAME_PROPERTY",
"username");

    call.setProperty("PASSWORD_PROPERTY",
"password");

 

I still get 401 error Please help me how to deal with this.
I have also attached the code and error below.

 

Thanks.

Jyothi

 

--

log4j:WARN No appenders could be found for logger
(org.apache.axis.i18n.ProjectResourceBundle)

log4j:WARN Please initialize the log4j system properly.

AxisFault

 faultCode:
{http://xml.apache.org/axis/}HTTP

 faultSubcode:

 faultString:
(401)Unauthorized

 faultActor:

 faultNode:

 faultDetail:

   
{}:return code:  401

401 Unauthorized

   
{http://xml.apache.org/axis/}HttpErrorCode:401

 

(401)Unauthorized

    at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:732)

    at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)

    at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

    at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)

    at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)

    at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)

    at
org.apache.axis.client.Call.invokeEngine(Call.java:2765)

    at
org.apache.axis.client.Call.invoke(Call.java:2748)

    at
org.apache.axis.client.Call.invoke(Call.java:2424)

    at
org.apache.axis.client.Call.invoke(Call.java:2347)

    at
org.apache.axis.client.Call.invoke(Call.java:1804)

    at
SoapWsdlClient.(SoapWsdlClient.java:23)

    at
SoapWsdlClient.main(SoapWsdlClient.java:36)

Press any key to continue . . .

 

 

--

 

 

 

import java.net.*;

import org.apache.axis.client.*;

import javax.xml.namespace.*;

 

 

public class SoapWsdlClient

{

public SoapWsdlClient()

{

try

{

 

 

    String
endPointAddress = "http:///_vti_bin/search.asmx";

    Service
service = new Service();

    Call
call = ( Call )service.createCall();

    call.setTargetEndpointAddress(
endPointAddress );

    call.setUsername("username");

    call.setPassword("passwd");

 

    call.setSOAPActionURI("urn:Microsoft.Search/Query");

    call.setOperationName(
new QName("urn:Microsoft.Search.Query", "Query") );

    String
returned = ( String) call.invoke( new Object[] { " urn:Microsoft.Search.Response.Document.Documentcannot
print1500"
} );

    System.out.println(
"Soap returned: " + returned );

 

 

}

catch (Exception e)

{

e.printStackTrace();

}

}

 

public static void main(String[] args)

{

SoapWsdlClient

Re: Question about generated Java w/ WSDL2Java

[Anne Thomas Manes]

I suggest you log a bug.

On 5/25/05, Kador, Daniel <[EMAIL PROTECTED]> wrote:
> Anne,
> 
> Thank you very much for your help.  I'll try to clean up the WSDL and
> see if that helps.
> 
> As for the extraneous '>' bug, I'm most definitely using Axis 1.2.  I
> knew that this was supposedly fixed in the 1.2 release, which is why I
> am confused as to why they are appearing.  Should I just chalk this up
> to a malformed WSDL, or do you think this is something the Axis
> developers need to worry about?
> 
> Thanks again,
> Dan
> 
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 25, 2005 9:44 AM
> To: axis-user@ws.apache.org
> Subject: Re: Question about generated Java w/ WSDL2Java
> 
> 
> A few recommendations:
> 
> Things work a lot more easily if you use the "wrapped" style rather than
> "unwrapped". In the "wrapped" style, the input element name must be the
> same as your operation name. So, for the GetPurpose operation, you input
> element should be called GetPurpose rather than GetPurposeRequest.
> 
> In your definitions  section, you create a schema with the
> targetNamespace of "http://www.ieee.org/DRAFT/Service";, and then you
> import the same namespace, which is not a valid construct. You should
>  it rather than  it. Alternatively, you can define the
> schema's targetNamespace to be the same as your WSDL namespace and use
> the . Regardless of the approach, the schema elements will
> remain assigned to the "http://www.ieee.org/DRAFT/Service"; namespace.
> 
> In your services , you should not specify a namespace attribute
> on the  and  definitions. (You use the namespace
> attribute only when using rpc style.
> 
> I'm pretty sure that the bug that caused the generation of the
> extraneous ">" characters in the WSDD has been fixed. Please make sure
> you are using Axis 1.2 final.
> 
> Anne
> 
> On 5/25/05, Kador, Daniel <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I hope this won't be too long, but I've got a few questions.  I've got
> 
> > my WSDL broken into two parts - definitions and services.  I've
> > attached them below, as well as the schema I'm using.
> >
> > Using the command "java apache.axis.org.wsdl.WSDL2Java -s -S true
> > AIEstateService.wsdl", I generate the Java code with stubs and a
> > skeleton.  My question lies in the realm of what is actually
> > generated. I've also attached the generated deploy.wsdd, so you can
> > see what I'm talking about.
> >
> > As an aside, if I try to deploy this service and run a test client on
> > it, I get the following error: "No such operation 'GetPurposeRequest'"
> 
> > (obviously this happens when I attempt to use the GetPurposeRequest()
> > function).
> >
> > I assumed the problem might be in the deploy.wsdd.  In some of the
> > typeMappings, the qname value has an (I think) extraneous '>'.  It's
> > my understanding that this is not correct, and in fact makes the WSDD
> > invalid, but I'm certainly not sure, as I can deploy the service and
> > view its WSDL through the Axis web interface with no problems.
> >
> > Does anybody have any insight into what I'm doing wrong, or how to fix
> 
> > the problems I'm having?
> >
> > Thanks,
> > Dan
> >
> >
> >
>

RE: Weblogic 8.1.2 and Axis 1.2

[Keith Hatton]

I believe you can create an APP-INF/lib folder in the EAR file, Jars in
there should be visible to all components in the EAR.

Hope this helps
Keith


-Original Message-
From: Bob Carpenter [mailto:[EMAIL PROTECTED] 
Sent: 25 May 2005 15:01
To: axis-user@ws.apache.org
Subject: RE: Weblogic 8.1.2 and Axis 1.2


Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars
being in the WEB-INF/lib should work, but doesn't. So, someone suggested
the brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there
and added the six in the CLASSPATH of the app's startWebLogic.cmd and it
now works.

If anyone knows a more elegant way to bundle these in the EAR, please
let share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.
I'm deploying an EAR file that contains the following: a number of
message driven beans and a war file containing an init servlet and my
application libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which
they then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some
web searches and I can't find anything that fixes this.  I saw the issue
about the conflict between weblogic webservices.jar and Axis's saaj.jar
and added the section 
true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be
privileged and is intended only for the user of the recipient named
above.  If you are not the intended recipient or a representative of the
intended recipient, you have received this e-mail in error and must not
copy, use or disclose the contents of this e-mail to anybody else.  If
you have received this e-mail in error, please notify the sender
immediately by return e-mail and permanently delete the copy you
received.  This e-mail has been swept for computer viruses.  However,
you should carry out your own virus checks. Registered in Ireland, No.
205721.  http://www.FINEOS.com
**

Re: multiRef namespace question

[Anne Thomas Manes]

Actually, it's the opposite. If you specify
elementFormDefault="qualified", then all elements defined within the
schema by default are namespace qualified. And to override the
default, you would need to specify form="unqualified" on the specific
element.

Note that when using RPC style, you don't have a schema for the SOAP
element structure. The only thing the schema specifies is type
information. The RPC convention sets namespaces according to these
rules:

- the child element of the  is a generated element (the
method name element) which has a namespace equal to the value of the
namespace attribute in the  definition and a local name equal
to the value of the name attribute in the  definition.
- the parameter accesssor elements (the children of the method name
element) are generated elements. These elements are always
unqualified. Their local names are equal to the value of the name
attribute on the  definition.
- children of the accessor elements correspond to the structure
defined in the schema that defines the accessor element type
structures.

Anne

On 5/25/05, Jan Delannoy <[EMAIL PROTECTED]> wrote:
> If I'm not mistaking, when the schema elementFormDefault is set to
> qualified this only means that the global element declarations (i.e.
> those that are direct children of the schema element) should be
> namespace qualified.  The local declarations (defined inside other
> elements or complexTypes) default back to not qualified.  So unless
> the local elements specifically have the form="qualified" attribute
> declared on them, they are not namespace qualified. I've noticed that
> Axis handles this by 'unsetting' the namespace on local elements, like
> this:
> 
> http://some.namespace.uri";>
>   
> ...
>   
> 
> 
> I've also noticed that some tools don't like these kinds of XMLs. In
> my case I solved it by explicitly setting the form="qualfied" on my
> local declarations too.
> 
> Hope this helps...
> Jan
> 
> 
> 
> On 5/24/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> > In my application, I am deserializing the incoming RPC encoded messages into
> > a DOM and then validating the DOM against the schema. I'm not using any
> > generated code in this process, rather I register a custom deserializer to
> > handle complex types and produce a Document.
> >
> > My problem is that validation fails in cases where the elementFormDefault
> > for the schema is set to qualified. This requires that all child elements of
> > a given element have the same namespace as their parent. The messages that I
> > receive from axis generated drivers do not provide any namespace information
> > for the multiRef elements.
> >
> > Here's the output from the soap monitor:
> >
> > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >   
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> > 
> >  
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="ns1:DocumentDataIn"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> > 
> > 
> >  
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="xsd:float"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>123.45
> >   > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> > xsi:type="xsd:int"
> > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>10
> >   
> >
> >
> > The resulting DOM looks like this:
> >
> > 
> >   10
> >   123.45
> > 
> >
> > But it should look like this:
> >
> >  > xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> >   10
> >   123.45
> > 
> >
> > It seems to me that the inbound message is wrong since there is no way to
> > convey to the receiver that data1 and data2 are qualified. The SOAP 1.1 spec
> > clearly states that the accessor elements that contain the href should not
> > be namespace qualified but it also has an example that shows a namespace
> > prefix being used in the multifRef encoding element
> > (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383520). The
> > SerializationContext in axis uses the same QName for multiRefs and it has
> > the empty namespace. It seems like there should be a way for the multiRef
> > element to have a namespace prefix.
> >
> > My workaround is to have my custom deserializer check the type of each
> > element that I'm deserializing to see if it has a form="qualified" in the
> > schema or if the schema's elementFormDefault="qualified".
> >
> > I would appreciate any suggestions or other feedback, thanks.
> >
> >
>

RE: multiRef namespace question

[Mark Ford]

The elementFormDefault atttribute on the schema only applies to local
elements, not global elements. See http://www.w3.org/TR/xmlschema-0/ Section
3.1 Target Namespaces & Unqualified Locals.

-Original Message-
From: Jan Delannoy [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 3:36 AM
To: axis-user@ws.apache.org
Subject: Re: multiRef namespace question

If I'm not mistaking, when the schema elementFormDefault is set to qualified
this only means that the global element declarations (i.e.
those that are direct children of the schema element) should be namespace
qualified.  The local declarations (defined inside other elements or
complexTypes) default back to not qualified.  So unless the local elements
specifically have the form="qualified" attribute declared on them, they are
not namespace qualified. I've noticed that Axis handles this by 'unsetting'
the namespace on local elements, like
this:

http://some.namespace.uri";>
  
...
  


I've also noticed that some tools don't like these kinds of XMLs. In my case
I solved it by explicitly setting the form="qualfied" on my local
declarations too.

Hope this helps...
Jan



On 5/24/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> In my application, I am deserializing the incoming RPC encoded 
> messages into a DOM and then validating the DOM against the schema. 
> I'm not using any generated code in this process, rather I register a 
> custom deserializer to handle complex types and produce a Document.
> 
> My problem is that validation fails in cases where the 
> elementFormDefault for the schema is set to qualified. This requires 
> that all child elements of a given element have the same namespace as 
> their parent. The messages that I receive from axis generated drivers 
> do not provide any namespace information for the multiRef elements.
> 
> Here's the output from the soap monitor:
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>   
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> 
>  
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="ns1:DocumentDataIn"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> 
> 
>  
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="xsd:float"
>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>123.45
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="xsd:int"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>10
>   
>
> 
> The resulting DOM looks like this:
> 
> 
>   10
>   123.45
> 
> 
> But it should look like this:
> 
>  xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
>   10
>   123.45
> 
> 
> It seems to me that the inbound message is wrong since there is no way 
> to convey to the receiver that data1 and data2 are qualified. The SOAP 
> 1.1 spec clearly states that the accessor elements that contain the 
> href should not be namespace qualified but it also has an example that 
> shows a namespace prefix being used in the multifRef encoding element 
> (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383520). The 
> SerializationContext in axis uses the same QName for multiRefs and it 
> has the empty namespace. It seems like there should be a way for the 
> multiRef element to have a namespace prefix.
> 
> My workaround is to have my custom deserializer check the type of each 
> element that I'm deserializing to see if it has a form="qualified" in 
> the schema or if the schema's elementFormDefault="qualified".
> 
> I would appreciate any suggestions or other feedback, thanks.
> 
>

RE: Weblogic 8.1.2 and Axis 1.2

[Bob Carpenter]

Hi Aoife,

You and I are working similar problems. I posted my question on BEA's
dev2dev forum. No one really had a good explanation - the axis' jars being
in the WEB-INF/lib should work, but doesn't. So, someone suggested the
brute-force method of adding the jars to the classpath of the app by
including them in CLASSPATH of the startWebLogic.cmd.

So, I added a folder /lib, put the six Axis 1.2 jars there and
added the six in the CLASSPATH of the app's startWebLogic.cmd and it now
works.

If anyone knows a more elegant way to bundle these in the EAR, please let
share the info.

--BobC

-Original Message-
From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 4:59 AM
To: 'axis-user@ws.apache.org'
Subject: Weblogic 8.1.2 and Axis 1.2


Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be privileged
and is intended only for the user of the recipient named above.  If you are
not the intended recipient or a representative of the intended recipient,
you have received this e-mail in error and must not copy, use or disclose
the contents of this e-mail to anybody else.  If you have received this
e-mail in error, please notify the sender immediately by return e-mail and
permanently delete the copy you received.  This e-mail has been swept for
computer viruses.  However, you should carry out your own virus checks.
Registered in Ireland, No. 205721.  http://www.FINEOS.com
**

RE: Question about generated Java w/ WSDL2Java

[Kador, Daniel]

Anne,

Thank you very much for your help.  I'll try to clean up the WSDL and
see if that helps.

As for the extraneous '>' bug, I'm most definitely using Axis 1.2.  I
knew that this was supposedly fixed in the 1.2 release, which is why I
am confused as to why they are appearing.  Should I just chalk this up
to a malformed WSDL, or do you think this is something the Axis
developers need to worry about?

Thanks again,
Dan

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 25, 2005 9:44 AM
To: axis-user@ws.apache.org
Subject: Re: Question about generated Java w/ WSDL2Java


A few recommendations:

Things work a lot more easily if you use the "wrapped" style rather than
"unwrapped". In the "wrapped" style, the input element name must be the
same as your operation name. So, for the GetPurpose operation, you input
element should be called GetPurpose rather than GetPurposeRequest.

In your definitions  section, you create a schema with the
targetNamespace of "http://www.ieee.org/DRAFT/Service";, and then you
import the same namespace, which is not a valid construct. You should
 it rather than  it. Alternatively, you can define the
schema's targetNamespace to be the same as your WSDL namespace and use
the . Regardless of the approach, the schema elements will
remain assigned to the "http://www.ieee.org/DRAFT/Service"; namespace.

In your services , you should not specify a namespace attribute
on the  and  definitions. (You use the namespace
attribute only when using rpc style.

I'm pretty sure that the bug that caused the generation of the
extraneous ">" characters in the WSDD has been fixed. Please make sure
you are using Axis 1.2 final.

Anne

On 5/25/05, Kador, Daniel <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I hope this won't be too long, but I've got a few questions.  I've got

> my WSDL broken into two parts - definitions and services.  I've 
> attached them below, as well as the schema I'm using.
> 
> Using the command "java apache.axis.org.wsdl.WSDL2Java -s -S true 
> AIEstateService.wsdl", I generate the Java code with stubs and a 
> skeleton.  My question lies in the realm of what is actually 
> generated. I've also attached the generated deploy.wsdd, so you can 
> see what I'm talking about.
> 
> As an aside, if I try to deploy this service and run a test client on 
> it, I get the following error: "No such operation 'GetPurposeRequest'"

> (obviously this happens when I attempt to use the GetPurposeRequest() 
> function).
> 
> I assumed the problem might be in the deploy.wsdd.  In some of the 
> typeMappings, the qname value has an (I think) extraneous '>'.  It's 
> my understanding that this is not correct, and in fact makes the WSDD 
> invalid, but I'm certainly not sure, as I can deploy the service and 
> view its WSDL through the Axis web interface with no problems.
> 
> Does anybody have any insight into what I'm doing wrong, or how to fix

> the problems I'm having?
> 
> Thanks,
> Dan
> 
> 
>

Re: WSDL 1.1 Operation Overloading Support

[Anne Thomas Manes]

You should avoid using operation overloading.

On 5/25/05, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> Hi All, 
> I need some help with information on level of support on Operation
> Overloading in Axis Java 1.1. 
> WSDL 1.1 seem to support operation overloading. Does Axis Java 1.1
> support this? What about Axis Java 1.2? 
>   
> I greatly appriciate any answers or pointers to some documentation on
> this. 
> Thanks, 
> Samisa...
> 
> 
>  
> Do You Yahoo!?
>  Yahoo! Small Business - Try our new Resources site! 
> 
>

Re: Document-oriented services using Axis 2.0

[Anne Thomas Manes]

Try using Axis 1.2.

On 5/25/05, Kiran Kumar <[EMAIL PROTECTED]> wrote:
>  
>  
> Hello Friends, I read in Apache Axis 2.0 introduction document, it now
> supports document-oriented webservices. I am really happy about it. But I am
> failed to get any sample example or instructions on how to use
> document-oriented (both client and server side) services. If you have any
> example, can you please pass on. 
>   
> Thank you 
> Kiran 
> 
>  
> 
> This e-mail, and any attachments thereto, is confidential and is intended
> only for the individual(s) named.  If you are not the intended recipient,
> please let us know by e-mail reply and delete it from your system; do not
> copy/save this e-mail or disclose its contents to anyone.  E-mail
> transmissions cannot be guaranteed to be secure or error-free as the
> transmission could be interrupted, corrupted, lost, destroyed, altered,
> arrive late or contain viruses.  ObjectWave does not accept liability for
> any errors or omissions in the contents of this e-mail which arise as a
> result of e-mail transmission.  The views expressed in this e-mail do not
> necessarily reflect those of ObjectWave or its affiliates. 
> 
> 

Re: Question about generated Java w/ WSDL2Java

[Anne Thomas Manes]

A few recommendations:

Things work a lot more easily if you use the "wrapped" style rather
than "unwrapped". In the "wrapped" style, the input element name must
be the same as your operation name. So, for the GetPurpose operation,
you input element should be called GetPurpose rather than
GetPurposeRequest.

In your definitions  section, you create a schema with the
targetNamespace of "http://www.ieee.org/DRAFT/Service";, and then you
import the same namespace, which is not a valid construct. You should
 it rather than  it. Alternatively, you can define
the schema's targetNamespace to be the same as your WSDL namespace and
use the . Regardless of the approach, the schema elements will
remain assigned to the "http://www.ieee.org/DRAFT/Service"; namespace.

In your services , you should not specify a namespace
attribute on the  and  definitions. (You use the
namespace attribute only when using rpc style.

I'm pretty sure that the bug that caused the generation of the
extraneous ">" characters in the WSDD has been fixed. Please make sure
you are using Axis 1.2 final.

Anne

On 5/25/05, Kador, Daniel <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I hope this won't be too long, but I've got a few questions.  I've got
> my WSDL broken into two parts - definitions and services.  I've attached
> them below, as well as the schema I'm using.
> 
> Using the command "java apache.axis.org.wsdl.WSDL2Java -s -S true
> AIEstateService.wsdl", I generate the Java code with stubs and a
> skeleton.  My question lies in the realm of what is actually generated.
> I've also attached the generated deploy.wsdd, so you can see what I'm
> talking about.
> 
> As an aside, if I try to deploy this service and run a test client on
> it, I get the following error: "No such operation 'GetPurposeRequest'"
> (obviously this happens when I attempt to use the GetPurposeRequest()
> function).
> 
> I assumed the problem might be in the deploy.wsdd.  In some of the
> typeMappings, the qname value has an (I think) extraneous '>'.  It's my
> understanding that this is not correct, and in fact makes the WSDD
> invalid, but I'm certainly not sure, as I can deploy the service and
> view its WSDL through the Axis web interface with no problems.
> 
> Does anybody have any insight into what I'm doing wrong, or how to fix
> the problems I'm having?
> 
> Thanks,
> Dan
> 
> 
>

Document-oriented services using Axis 2.0

[Kiran Kumar]

Hello Friends, I read in Apache Axis 2.0 
introduction document, it now supports document-oriented webservices. I am 
really happy about it. But I am failed to get any sample example or instructions 
on how to use document-oriented (both client and server side) services. If you 
have any example, can you please pass on.
 
Thank you
Kiran

This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named.  If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone.  E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses.  ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission.  The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates.

Question about generated Java w/ WSDL2Java

[Kador, Daniel]

Hi,

I hope this won't be too long, but I've got a few questions.  I've got
my WSDL broken into two parts - definitions and services.  I've attached
them below, as well as the schema I'm using.

Using the command "java apache.axis.org.wsdl.WSDL2Java -s -S true
AIEstateService.wsdl", I generate the Java code with stubs and a
skeleton.  My question lies in the realm of what is actually generated.
I've also attached the generated deploy.wsdd, so you can see what I'm
talking about.

As an aside, if I try to deploy this service and run a test client on
it, I get the following error: "No such operation 'GetPurposeRequest'"
(obviously this happens when I attempt to use the GetPurposeRequest()
function).

I assumed the problem might be in the deploy.wsdd.  In some of the
typeMappings, the qname value has an (I think) extraneous '>'.  It's my
understanding that this is not correct, and in fact makes the WSDD
invalid, but I'm certainly not sure, as I can deploy the service and
view its WSDL through the Axis web interface with no problems.

Does anybody have any insight into what I'm doing wrong, or how to fix
the problems I'm having?

Thanks,
Dan


CEM4-2e.xsd
Description: CEM4-2e.xsd


AIEstateDefinitions.wsdl
Description: AIEstateDefinitions.wsdl


AIEstateService.wsdl
Description: AIEstateService.wsdl


deploy.wsdd
Description: deploy.wsdd

Axis Fault in Document Style

[Fiore Paolo]

Title: Axis Fault in Document Style





Hi, to everybody


I would to know if/how is possible to 'throw a customized Exception' from a WS in document/literal style to onother WS in document/literal.

To be more clear, I created an object Fault_message starting from an xsd file and creating a java object(Fault_message) using WSDL2Java. After this I extended Fault_message through AxisFault as you can see in attached file.

When a WS try to throw an Exception using this Fault_message there are a lot of problem of deserialization(I suppose).
In mine code I have two rows like:


StatusList app = new StatusList(array);
throw new Fault_message(Constants.MAGIC_FAULT_BPEL_MUST_RECOVER_BY_APPLICATION,
            "The application must resend the applicative message.",app,"atomic");



It seems that the error was generated during the deserialization, as you can see in the folloing rows:


<<
AxisFault
 faultCode: {http://org/atosorigin/serviceware/t4ws/vbl/fault_message_type}Fault
_message
 faultSubcode:
 faultString: The application must resend the applicative message.
 faultActor:
 faultNode:
 faultDetail:
    {}string:43



The application must resend the applicative message.
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder
.java:221)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.
java:128)
    at org.apache.axis.encoding.DeserializationContext.endElement(Deserializ
ationContext.java:1083)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknow
n Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
    at org.apache.axis.encoding.DeserializationContext.parse(Deserialization
Context.java:226)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:653)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnders
tandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:173)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2719)
    at org.apache.axis.client.Call.invoke(Call.java:2702)
    at org.apache.axis.client.Call.invoke(Call.java:2378)
    at org.apache.axis.client.Call.invoke(Call.java:2301)
    at org.apache.axis.client.Call.invoke(Call.java:1758)
    at org.atosorigin.serviceware.t4ws.demo.client_bpel.Vas_transaction_bpel
BPBindingStub.BPRequestReponse(Vas_transaction_bpelBPBindingStub.java:171)
    at org.atosorigin.serviceware.t4ws.demo.client_bpel.Vas_transaction_bpel
BPTestCase.test1vas_transaction_bpelBPPortBPRequestReponse(Vas_transaction_bpelB
PTestCase.java:45)
    at org.atosorigin.serviceware.t4ws.demo.TelcoMobileActivationServiceBpel
ProcessServlet.doPost(TelcoMobileActivationServiceBpelProcessServlet.java:127)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:407)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:825)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:738)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:526)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
    

Weblogic 8.1.2 and Axis 1.2

[Aoife Kavanagh (Ext. 987)]

Hi,

I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment.  I'm
deploying an EAR file that contains the following: a number of message
driven beans and a war file containing an init servlet and my application
libs including my axis jars.

My transport is SOAP over JMS so my beans receive JMS messages which they
then forward on via Axis.

Using Axis 1.1 everything worked fine.
Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for
org/apache/axis/description/OperationDesc in my bean.  I've done some web
searches and I can't find anything that fixes this.  I saw the issue about
the conflict between weblogic webservices.jar and Axis's saaj.jar and added
the section 

true
/container-descriptor>
to my weblogic.xml.  This makes no difference whatsoever.  Is there some
equivalent for the application classes?  

Any help appreciated.
Thanks,
Aoife



**
The information contained in this e-mail is confidential, may be privileged and 
is intended only for the user of the recipient named above.  If you are not the 
intended recipient or a representative of the intended recipient, you have 
received this e-mail in error and must not copy, use or disclose the contents 
of this e-mail to anybody else.  If you have received this e-mail in error, 
please notify the sender immediately by return e-mail and permanently delete 
the copy you received.  This e-mail has been swept for computer viruses.  
However, you should carry out your own virus checks. 
Registered in Ireland, No. 205721.  http://www.FINEOS.com
**

WSDL 1.1 Operation Overloading Support

[Samisa Abeysinghe]

Hi All,
    I need some help with information on level of support on Operation Overloading in Axis Java 1.1.
    WSDL 1.1 seem to support operation overloading. Does Axis Java 1.1 support this? What about Axis Java 1.2?
 
    I greatly appriciate any answers or pointers to some documentation on this.
Thanks,
Samisa...
		Do You Yahoo!? Yahoo! Small Business - Try our new Resources site!

RE: Header & attributes in SOAP msg

[Anand, Rajesh]

Title: Message



    Gigi,
 
    In most examples I've seen call.addparamter method to add 
parameters for the remote method call.
 
However, in my case I've an extra element as mentioned 
below, before the parameters in the body of soap.
 
Can I add this extra element using addBODYElement in the 
soap body??? If yes, how do I do this??
 
If not how else I can do this???
 
regards, 
 
 
Rajesh 
Anand Email:[EMAIL PROTECTED] 

  
  -Original Message-From: Luigi Della 
  Monica [mailto:[EMAIL PROTECTED] Sent: 25 May 
  2005 11:26To: axis-user@ws.apache.orgSubject: RE: Header 
  & attributes in SOAP msg
  
  …logger is an 
  instance of a Log4J logger.
   
  To save on file you 
  can do:
   
  FileOutputStream os = 
  new FileOutputStream(new File("filename.xml"));
  msgContext.getMessage().writeTo( 
  os );
  os.close();
   
  sorry, but I didn’t 
  understood the other question.
   
  Bye, 
  Gigi
  
  
  
  
  From: Anand, Rajesh 
  [mailto:[EMAIL PROTECTED] Sent: mercoledì 25 maggio 2005 
  12.16To: 
  axis-user@ws.apache.orgSubject: RE: Header & attributes in 
  SOAP msg
   
  
      
  Thanks for your code.
  
   
  
      So I can add this to 
  my soap client app and write it to txt file. which class does this belong to - 
  logger.info???
  
   
  
   
  
      One other thing, if 
  you notice the body of soap msg
  
      SOAP-ENV:Body> 
      
      
  xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/"> 
  
      Do 
  you know what method I can use to add before the parameters are 
  added???
  
   
  
      Thanks for your 
  help.
  
   
  
      
  Regards,
  
   
  Rajesh 
  Anand Email:[EMAIL PROTECTED] 
  
-Original 
Message-From: Luigi 
Della Monica [mailto:[EMAIL PROTECTED] Sent: 25 May 2005 10:58To: axis-user@ws.apache.orgSubject: RE: Header & attributes in 
SOAP msg
Hi,
You can easily add 
an handler on the response. I have tested it on the request but I think that 
work also on the response.
 
This is a code 
snippet of my handler. I serialize on my log but you can write on 
file.
 
public class 
EnvelopeLoggerHandler extends BasicHandler {
    
public void invoke(MessageContext msgContext) throws 
AxisFault
    
{
    
try {
    
logger.info( " START DUMP " );
    
logger.info(msgContext.getMessage().getSOAPPart().getEnvelope().toString();
    
logger.info( " END DUMP " );
    
} catch (Exception e) {
    
throw AxisFault.makeFault(e);
    
}
    
}
}
 
To deploy handler 
you must add handler into server-config.wsdd:

 
And add the handler 
to your service on the response flow:
  

   

  

 
Bye, 
Gigi
 
 




From: Anand, Rajesh 
[mailto:[EMAIL PROTECTED] Sent: mercoledì 25 maggio 2005 
11.32To: 
axis-user@ws.apache.orgSubject: Header & attributes in 
SOAP msg
 

    
Folks, 
    
Is there a way to see soap msg 
before it goes out, maybe write it out to a .txt file to view 
it. 
    
The soap msg I need to create 
has attributes and special headers defined. 
    
Here is the snippet of what I 
need to generate. 
    
Any help with working example 
would be great. 
    
xmlns:EDSI-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/EDSIHeader_2_0/">     
GetIndexService 
    
1.0 
    
2002-06-14T10:18:48-05:00 
    
     
    
xmlns:PRO-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/ProtocolHeaders_1_0/" 
SOAP-ENV:mustUnderstand = "1">
    
GMI_Test 
    
     
     
     
    
xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">     
BP0001W 
    
2005-05-01 
    
2005-05-23 
    
Level 
    
Bloomberg 
    
 
 
    
Thanks for your help in 
advance. 
 
Rajesh 
Anand Email:[EMAIL PROTECTED] 






If you are not an intended recipient of this e-mail, 
please notify the sender, delete it and do not read, act upon, print, 
disclose, copy, retain or redistribute it. Click here for important 
additional terms relating to this e-mail. http://www.ml.com/email_terms/

RE: Header & attributes in SOAP msg

[Luigi Della Monica]

Title: Message








…logger is an
instance of a Log4J logger.

 

To save on file you can
do:

 

FileOutputStream os = new
FileOutputStream(new File("filename.xml"));

msgContext.getMessage().writeTo(
os );

os.close();

 

sorry, but I didn’t
understood the other question.

 

Bye, Gigi









From:
Anand, Rajesh [mailto:[EMAIL PROTECTED] 
Sent: mercoledì 25 maggio 2005
12.16
To: axis-user@ws.apache.org
Subject: RE: Header &
attributes in SOAP msg



 



    Thanks for your code.





 





    So I can add this to my
soap client app and write it to txt file. which class does this belong to - logger.info???





 





 





    One other thing, if you
notice the body of soap msg





    SOAP-ENV:Body> 
   

   
xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">






    Do you know what method
I can use to add before the parameters are added???





 





    Thanks for your help.





 





    Regards,





 



Rajesh
Anand 
Email:[EMAIL PROTECTED] 



-Original
Message-
From: Luigi Della Monica
[mailto:[EMAIL PROTECTED] 
Sent: 25 May 2005 10:58
To: axis-user@ws.apache.org
Subject: RE: Header &
attributes in SOAP msg

Hi,

You can easily add an
handler on the response. I have tested it on the request but I think that work
also on the response.

 

This is a code snippet of
my handler. I serialize on my log but you can write on file.

 

public class
EnvelopeLoggerHandler extends BasicHandler {

    public
void invoke(MessageContext msgContext) throws AxisFault

    {

   
try {

   
logger.info( " START DUMP " );

   
logger.info(msgContext.getMessage().getSOAPPart().getEnvelope().toString();

   
logger.info( " END DUMP " );

   
} catch (Exception e) {

   
throw AxisFault.makeFault(e);

   
}

    }

}

 

To deploy handler you
must add handler into server-config.wsdd:



 

And add the handler to
your service on the response flow:

 


   

 


 

Bye, Gigi

 

 









From:
Anand, Rajesh [mailto:[EMAIL PROTECTED] 
Sent: mercoledì 25 maggio 2005
11.32
To: axis-user@ws.apache.org
Subject: Header & attributes
in SOAP msg



 



   
Folks, 

   
Is there a way to see soap msg before it goes out, maybe write it out to
a .txt file to view it. 

   
The soap msg I need to create has attributes and special headers
defined. 

   
Here is the snippet of what I need to generate. 

   
Any help with working example would be great. 


   
xmlns:EDSI-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/EDSIHeader_2_0/">

   
GetIndexService

   
1.0

   
2002-06-14T10:18:48-05:00

   
 
   

   
xmlns:PRO-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/ProtocolHeaders_1_0/"
SOAP-ENV:mustUnderstand = "1">

   
GMI_Test

   
 
   
 
   
 
   

   
xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">

   
BP0001W

   
2005-05-01 
   
2005-05-23 
   
Level

   
Bloomberg

   
 

 

   
Thanks for your help in advance. 

 

Rajesh Anand 
Email:[EMAIL PROTECTED] 















If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for
important additional terms relating to this e-mail. http://www.ml.com/email_terms/

RE: Header & attributes in SOAP msg

[Anand, Rajesh]

Title: Message



    Thanks for your code.
 
    So I can add this to my soap client app and write it to txt 
file. which class does this belong to - logger.info???
 
 
    One other thing, if you notice the body of soap 
msg
    SOAP-ENV:Body>     
    
xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/"> 

    Do you know what method I can use to add before the 
parameters are added???
 
    Thanks for your help.
 
    Regards,
 
Rajesh 
Anand Email:[EMAIL PROTECTED] 

  
  -Original Message-From: Luigi Della 
  Monica [mailto:[EMAIL PROTECTED] Sent: 25 May 
  2005 10:58To: axis-user@ws.apache.orgSubject: RE: Header 
  & attributes in SOAP msg
  
  Hi,
  You can easily add an 
  handler on the response. I have tested it on the request but I think that work 
  also on the response.
   
  This is a code 
  snippet of my handler. I serialize on my log but you can write on 
  file.
   
  public class 
  EnvelopeLoggerHandler extends BasicHandler {
      
  public void invoke(MessageContext msgContext) throws 
  AxisFault
      
  {
      
  try {
      
  logger.info( " START DUMP " );
      
  logger.info(msgContext.getMessage().getSOAPPart().getEnvelope().toString();
      
  logger.info( " END DUMP " );
      
  } catch (Exception e) {
      
  throw AxisFault.makeFault(e);
      
  }
      
  }
  }
   
  To deploy handler you 
  must add handler into server-config.wsdd:
  
   
  And add the handler 
  to your service on the response flow:
    
  
     
  
    
  
   
  Bye, 
  Gigi
   
   
  
  
  
  
  From: Anand, Rajesh 
  [mailto:[EMAIL PROTECTED] Sent: mercoledì 25 maggio 2005 
  11.32To: 
  axis-user@ws.apache.orgSubject: Header & attributes in SOAP 
  msg
   
  
      
  Folks, 
      
  Is there a way to see soap msg 
  before it goes out, maybe write it out to a .txt file to view 
  it. 
      
  The soap msg I need to create has 
  attributes and special headers defined. 
      
  Here is the snippet of what I need 
  to generate. 
      
  Any help with working example 
  would be great. 
      
  xmlns:EDSI-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/EDSIHeader_2_0/">     
  GetIndexService 
      
  1.0 
      
  2002-06-14T10:18:48-05:00 
      
       
      
  xmlns:PRO-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/ProtocolHeaders_1_0/" 
  SOAP-ENV:mustUnderstand = "1">
      
  GMI_Test 
      
       
       
       
      
  xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">     
  BP0001W 
      
  2005-05-01 
      
  2005-05-23 
      
  Level 
      
  Bloomberg 
      
   
   
      
  Thanks for your help in 
  advance. 
   
  Rajesh 
  Anand Email:[EMAIL PROTECTED] 
  
  
  
  
  
  
  If you are not an intended recipient of this e-mail, 
  please notify the sender, delete it and do not read, act upon, print, 
  disclose, copy, retain or redistribute it. Click here for important additional 
  terms relating to this e-mail. http://www.ml.com/email_terms/
  
  
  
  

need some help

[Anish Jindal]

Can anyone of you tell me some link
where i can find some tutorial for java web service programming with axis(not
the command tools).
Problem: Actually i m trying to make
a tool which can publish web service given a class file. And automatically
generate a client code for
invoking web service provided wsdl file.
And i m trying to make a gui for providing this feature.
I m quit familiar wirh all command line
tool provided by axis but a normal programmer of java and dont know how
to use api's provided by 
axis to do my job.
Thank you in advance.
Anish Jindal

RE: Header & attributes in SOAP msg

[Luigi Della Monica]

Title: Header & attributes in SOAP msg








Hi,

You can easily add an
handler on the response. I have tested it on the request but I think that work
also on the response.

 

This is a code snippet of
my handler. I serialize on my log but you can write on file.

 

public class
EnvelopeLoggerHandler extends BasicHandler {

    public void
invoke(MessageContext msgContext) throws AxisFault

    {

    try {

    logger.info(
" START DUMP " );

   
logger.info(msgContext.getMessage().getSOAPPart().getEnvelope().toString();

    logger.info(
" END DUMP " );

    } catch
(Exception e) {

    throw
AxisFault.makeFault(e);

    }

    }

}

 

To deploy handler you
must add handler into server-config.wsdd:



 

And add the handler to
your service on the response flow:

  

   

  

 

Bye, Gigi

 

 









From:
Anand, Rajesh [mailto:[EMAIL PROTECTED] 
Sent: mercoledì 25 maggio 2005
11.32
To: axis-user@ws.apache.org
Subject: Header & attributes
in SOAP msg



 



   
Folks, 

   
Is there a way to see soap msg before it goes out, maybe write it out to
a .txt file to view it. 

   
The soap msg I need to create has attributes and special headers
defined. 

   
Here is the snippet of what I need to generate. 

   
Any help with working example would be great. 


   
xmlns:EDSI-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/EDSIHeader_2_0/">

   
GetIndexService

   
1.0

   
2002-06-14T10:18:48-05:00

   
 
   

   
xmlns:PRO-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/ProtocolHeaders_1_0/"
SOAP-ENV:mustUnderstand = "1">

   
GMI_Test

   
 
   
 
   
 
   

   
xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">

   
BP0001W

   
2005-05-01 
   
2005-05-23 
   
Level

   
Bloomberg

   
 

 

   
Thanks for your help in advance. 

 

Rajesh Anand 
Email:[EMAIL PROTECTED] 















If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for
important additional terms relating to this e-mail. http://www.ml.com/email_terms/

Header & attributes in SOAP msg

[Anand, Rajesh]

Title: Header & attributes in SOAP msg






    Folks,


    Is there a way to see soap msg before it goes out, maybe write it out to a .txt file to view it.


    The soap msg I need to create has attributes and special headers defined.


    Here is the snippet of what I need to generate.


    Any help with working example would be great. 




    xmlns:EDSI-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/EDSIHeader_2_0/">

    GetIndexService

    1.0

    2002-06-14T10:18:48-05:00

    

    

    xmlns:PRO-HDR = "http://namespace.worldnet.ml.com/EDSI/Standards/Headers/ProtocolHeaders_1_0/" SOAP-ENV:mustUnderstand = "1">

    GMI_Test

    

    

    

    

    xmlns:getIndex = "http://namespace.worldnet.ml.com/EDSI/Product/Services/GetIndexData_v1_0/">

    BP0001W

    2005-05-01

    2005-05-23

    Level

    Bloomberg

    



    Thanks for your help in advance.




Rajesh Anand

Email:[EMAIL PROTECTED]






If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/

Re: multiRef namespace question

[Jan Delannoy]

If I'm not mistaking, when the schema elementFormDefault is set to
qualified this only means that the global element declarations (i.e.
those that are direct children of the schema element) should be
namespace qualified.  The local declarations (defined inside other
elements or complexTypes) default back to not qualified.  So unless
the local elements specifically have the form="qualified" attribute
declared on them, they are not namespace qualified. I've noticed that
Axis handles this by 'unsetting' the namespace on local elements, like
this:

http://some.namespace.uri";>
  
...
  


I've also noticed that some tools don't like these kinds of XMLs. In
my case I solved it by explicitly setting the form="qualfied" on my
local declarations too.

Hope this helps...
Jan



On 5/24/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> In my application, I am deserializing the incoming RPC encoded messages into
> a DOM and then validating the DOM against the schema. I'm not using any
> generated code in this process, rather I register a custom deserializer to
> handle complex types and produce a Document.
> 
> My problem is that validation fails in cases where the elementFormDefault
> for the schema is set to qualified. This requires that all child elements of
> a given element have the same namespace as their parent. The messages that I
> receive from axis generated drivers do not provide any namespace information
> for the multiRef elements.
> 
> Here's the output from the soap monitor:
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>   
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> 
>  
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="ns1:DocumentDataIn"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
> 
> 
>  
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="xsd:float"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>123.45
>   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xsi:type="xsd:int"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>10
>   
>
> 
> The resulting DOM looks like this:
> 
> 
>   10
>   123.45
> 
> 
> But it should look like this:
> 
>  xmlns:ns1="http://www.active-endpoints.com/wsdl/unit_complex_return";>
>   10
>   123.45
> 
> 
> It seems to me that the inbound message is wrong since there is no way to
> convey to the receiver that data1 and data2 are qualified. The SOAP 1.1 spec
> clearly states that the accessor elements that contain the href should not
> be namespace qualified but it also has an example that shows a namespace
> prefix being used in the multifRef encoding element
> (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383520). The
> SerializationContext in axis uses the same QName for multiRefs and it has
> the empty namespace. It seems like there should be a way for the multiRef
> element to have a namespace prefix.
> 
> My workaround is to have my custom deserializer check the type of each
> element that I'm deserializing to see if it has a form="qualified" in the
> schema or if the schema's elementFormDefault="qualified".
> 
> I would appreciate any suggestions or other feedback, thanks.
> 
>