date:20071127

Re: Reading attribute on a complex element

2007-11-27 Thread Sunil Pandit

Dimuthu

Thanks for your response. I modified your code to test with my xml .
However the axiom_document_get_root_element
call returns the root element without any children's .

Attached is a log  and xml file (See attached file: test.c).

Any idea ?

(See attached file: alltest.log)(See attached file: VPMSRequest.xml)
Thanks
Sunil Pandit
RD , CSC FSG Austin
(512)2755792

Computer Sciences Corporation
Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA
Registered in USA No: C-489-59



This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.





   
 Dimuthu Gamage  
 [EMAIL PROTECTED] 
 omTo 
   Apache AXIS C User List   
 11/27/2007 01:21  axis-c-user@ws.apache.org 
 AM cc 
   
   Subject 
 Please respond to Re: Reading attribute on a complex  
  Apache AXIS C   element 
User List 
 [EMAIL PROTECTED] 
pache.org 
   
   
   




Hi,
I checked your code and the xml. And it worked. Check the attachments.

I think your problem is the firstNode is not the one you think (Command).

If you have spaces in the xml, the axiom think they are text_node, And
currently the code gen is not handling that situation, I have to check
whether it s a bug or not.

If it is the case, just add following lines to get rid of the text_nodes,

while(axiom_node_get_node_type(first_node, env) != AXIOM_ELEMENT)
{
first_node = axiom_node_get_next_sibling(first_node, env);
}

And if you found the generated code is not working, please let the axis2-c
list know that issue, And hope you are updated with the tool from
http://people.apache.org/dist/axis2/nightly/

Thanks
Dimuthu

On Nov 27, 2007 11:33 AM, Sunil Pandit [EMAIL PROTECTED] wrote:
  Can someone guide me on how to read the attribute value on an element ?

  I have a web service that takes a complex element with an attribute.  The
  deserialization code generated by WSDL2C is not able to read this
  attribute.
  So I modified the code and none of the method including
  axiom_element_get_all_attributes returns the attributes.
  The axiom_element_get_all_attributes returns NULL.

  When I log the string form of the node passed to deserialize method , I
  can
  see all the sub elements and the attribute . Here is the code

  Any help is sincerely appreciated.

   parent_element = axiom_node_get_data_element(first_node, env);
   qname = axutil_qname_create_from_string(env,Sequence);
   if(qname != NULL)
   {
 parent_attri = axiom_element_get_attribute(parent_element,
  env,
  qname);
   }

   if(parent_attri == NULL)
   {
 attributes =
  axiom_element_get_all_attributes(parent_element,env);
   }

  Here is the string form of node passed to the deserialize method

  Mon Nov 26 23:32:54 2007] [info]  CommandType : String form of Element is
   Command Sequence=1
   Typeloadsession/Type
   ParameterC:\VPMS\workspace\Federated
  
Perf\Federated\Models\DADVDOCS_Master\DADVDOCS\DULDOCS_test_cases.VPM/Parameter

   /Command




  Regards
  Sunil Pandit
  RD , CSC FSG Austin
  (512)2755792

  Computer Sciences Corporation
  Registered Office: 2100 East Grand Avenue, El Segundo California 90245,
  USA
  Registered in USA No: C-489-59

C++ and C with gcc

2007-11-27 Thread tom.lake



I found that shared libraries built with g++ on Linux (Fedora Core 6)
contain a reference to __gxx_personality_v0. In order to load such a
library with dlopen the loading program should be built with the
library libstdc++.so (as far as I can see).

So it seems to be necessary to have a version of AXIS2/C with this
reference defined. It is easy to rebuild axis2c with -lstdc++ stuck
in a Makefile somewhere (say in util/src ), but some people might well
find the difficulty in working out what to do and getting such a system
going time-consuming, as I did.

It would be good to document this, and even better to put in a
configuration option for it (or did I miss it?).

Thanks for a very useful software framework all contributors!

Tom Lake


--
 Tom Lake   Interglossa Ltd   |email: [EMAIL PROTECTED]
 SnailPhone: 0118 956 1919|mob: 079 638 15599
 SnailMail: Interglossa Ltd   |
   2nd Floor, Chain St|web: http://www.glossa.co.uk
   Reading RG1 2HX|
--

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Microsoft interop gotcha - WSDL with minOccurs=0, type=xs:long

2007-11-27 Thread Mauro Molinari


Hi Jason,
the first problem is that .NET translates optional WSDL elements 
(i.e.: those with minOccurs=0 and maxOccurs=1 - please note 
maxOccurs=1 is the default, if not specified) with a second boolean 
parameter like xxxSpecified that states if the previous parameter has 
been specified or not.
This is because .NET 1.1 was not able to specify null for primitive 
types (like int, long, etc.; string is an exception), so the convention 
is the following:

- any value, xxxSpecified = false = means null
- a value, xxxSpecified = true = means value

.NET 2.0 behaves the same, probably because of some kind of 
retro-compatibility.


However, I would not consider that a big problem. If you are sure your 
parameters cannot be null, you can manually delete all minOccurs=0; 
otherwise, you may remove minOccurs=0 and substitute with 
nillable=true, but be careful: as I said before, .NET 1.1 cannot 
specify null for primitive types, so a .NET 1.1 client would not be able 
to specify null for, say, an int parameter marked as nillable=true. 
.NET 2.0 does not have this problem.


The second (and real) problem is that if you are writing your web 
services bottom up, Axis2 Java2WSDL always generates minOccurs=0 and, 
in some circumstances, this can lead to bigger problems that the one you 
described. Please also have a look to my bug report:

http://issues.apache.org/jira/browse/AXIS2-3300

Cheers.

--
Mauro Molinari
Software Developer
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis - Using attachments

2007-11-27 Thread [EMAIL PROTECTED]


Hi,
Thanks for your reply But i am using weblogic 8.1 SP6. My question is
how do i retain the name of the file while writing the file to the file
system ? I am able to write it with some dummy name of the file and not the
exact name which is in the source folder.


mgainty wrote:
 
 In catalina.policy did you assign write permissions for the folder
 C:/EDDHome ?
 this is more tomcat setup than axis specific I would suggest asking the
 same
 question on [EMAIL PROTECTED]
 
 M--
 - Original Message -
 From: [EMAIL PROTECTED] [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Monday, November 26, 2007 10:16 AM
 Subject: Re: Axis - Using attachments
 
 

 Can anyone please help me ? I can write it to the directory i want but i
 am
 unable to retain the name of the file.


 [EMAIL PROTECTED] wrote:
 
  Hi ,
  My requirement is to get a pdf from a service. The server sends a pdf
 and
  the client has to store the same in the file system. But i am unable to
  save the pdf in a location i want instead of the windows temp folder.
 Can
  some one help me on this pls. I have attached the Service class, the
  client and the wsdd.
 
  // Service Class
  public class PDFAttachmentsService {
 
  public DataHandler sendPdfs() throws MalformedURLException {
 
  String filename = C:/EDDHome/1_52043_1.pdf;
  DataHandler dataHandler = new DataHandler(new
 FileDataSource(filename));
 
  return dataHandler;
  }
  }
 
  // Client Class
  public class PDFAttachment {
 
  public static void main(String args[]) {
  try {
  Service service = new Service();
 
  Call call = (Call) service.createCall();
 
  call
 
 
 setTargetEndpointAddress(http://localhost:8080/axis/services/urn:PDFAttach
 mentsService);
 
  call.setOperationName(new QName(urn:PDFAttachmentsService,
  sendPdfs));
 
  QName qnameAttachment = new QName(urn:PDFAttachmentsService,
  DataHandler);
  call.registerTypeMapping(PDFAttachment.class, qnameAttachment,
  JAFDataHandlerSerializerFactory.class,
  JAFDataHandlerDeserializerFactory.class);
 
  call.setReturnType(qnameAttachment);
 
  Object ret = call.invoke(new Object[] {});
 
  if (null == ret) {
  System.out.println(Received null );
  throw new AxisFault(, Received null, null, null);
  }
 
  if (ret instanceof String) {
  System.out.println(Received problem response from server: 
  + ret);
  throw new AxisFault(, (String) ret, null, null);
  }
 
  if (!(ret instanceof DataHandler)) {
  // The wrong type of object that what was expected.
  System.out.println(Received problem response from server:
  + ret.getClass().getName());
  throw new AxisFault(,
  Received problem response from server:
  + ret.getClass().getName(), null, null);
 
  }
 
  DataHandler rdh = (DataHandler) ret;
 
  System.out.println(Received thro : + rdh.getClass().getName());
  } catch (Exception e) {
  System.err.println(e);
  e.printStackTrace();
  }
  }
  }
 
  // WSDD file
  !-- This deploys PDF attachment service.  --
  deployment xmlns=http://xml.apache.org/axis/wsdd/;
  xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
  xmlns:ns1=urn:PDFAttachmentsService 
service name=urn:PDFAttachmentsService provider=java:RPC 
  parameter name=className
  value=samples.pdfattachments.PDFAttachmentsService/
  parameter name=allowedMethods value=sendPdfs/
  parameter name=dataHandler type=ns1:DataHandler/
 
   typeMapping
 
 deserializer=org.apache.axis.encoding.ser.JAFDataHandlerDeserializerFactory
 
 languageSpecificType=java:javax.activation.DataHandler
  qname=ns1:DataHandler
 
 
 serializer=org.apache.axis.encoding.ser.JAFDataHandlerSerializerFactory
  encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
   /
/service
 
  /deployment
 
 

 --
 View this message in context:
 http://www.nabble.com/Axis---Using-attachments-tf4860902.html#a13951390
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Axis---Using-attachments-tf4860902.html#a13967066
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 Problem accessing the WSDL.

2007-11-27 Thread [EMAIL PROTECTED]


Can you pls post your WSDD or the Service class ? 
I have used Axis 1.4 with weblogic 8.1 and it works fine...


tinkugadu wrote:
 
 WHen i try to access the WSDL i get the StringIndexOUtOfBoundsException
 followed by the ClassCastException. WHen i try to access the
 csows/axis2-web/index.jsp from the Weblogic console then i just get the
 classcast exception
 
 my Environment:
 
 Webserver - Weblogic9
 
 axis version-  axis2 1.2
 
 I am not using axis2.xml 
 i have listed the two exceptions below.
 
  
 Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
 ndsAdmin [ACTIVE] ExecuteThread: '8' for queue:
 'weblogic.kernel.Default (self-tuning)' WLS Kernel  
 1196100514023 BEA-101020
 [EMAIL PROTECTED] - name:
 'csows.war', context-path: '/csows'] Servlet failed with Exception
 java.lang.StringIndexOutOfBoundsException: String index out of range: -11
 at java.lang.String.substring(String.java:1768)
 at java.lang.String.substring(String.java:1735)
 at
 org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(HTTPLocationBasedDispatcher.java:106)
 at
 org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(HTTPLocationBasedDispatcher.java:52)
 at
 org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java:100)
 at
 org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(RESTUtil.java:138)
 at
 org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:95)
 at
 org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest(AxisServlet.java:776)
 at
 org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
 at
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
 at
 weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
 at
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
 at
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
 at
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
 at
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at
 weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
 at
 weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
 at
 weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

 Nov 26, 2007 1:08:35 PM EST Error HTTP lnx552.dteco.com
 ndsAdmin [ACTIVE] ExecuteThread: '8' for queue:
 'weblogic.kernel.Default (self-tuning)' WLS Kernel  
 1196100515023 BEA-101107
 [EMAIL PROTECTED] - name:
 'csows.war', context-path: '/csows'] Problem occurred while serving the
 error page.
 java.lang.ClassCastException:
 org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
 at
 javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98)
 at
 javelin.jsp.JspTagLibraryFeature.parseTldFromWebXML(JspTagLibraryFeature.java:857)
 at
 javelin.jsp.JspTagLibraryFeature.initFromWebXML(JspTagLibraryFeature.java:841)
 at
 javelin.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:442)
 at
 javelin.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:241)
 at
 javelin.jsp.JspTagLibraryFeature.setCPL(JspTagLibraryFeature.java:42)
 at javelin.CPL.getFeature(CPL.java:1580)
 at javelin.jsp.JspParser.getTagLibraryFeature(JspParser.java:3364)
 at javelin.jsp.JspParser.getTagLibInfo(JspParser.java:2127)
 at javelin.jsp.JspParser.jspParse(JspParser.java:430)
 at javelin.jsp.JspParser._parse(JspParser.java:349)
 at javelin.jsp.JspParser.parse(JspParser.java:342)
 at javelin.jsp.JspAnalyzer.parseFile(JspAnalyzer.java:113)
 at javelin.jsp.JspAnalyzer.parse(JspAnalyzer.java:101)
 at javelin.ProxySourceFile.parse(ProxySourceFile.java:117)
 at javelin.SourceFile.getAst(SourceFile.java:542)
 at javelin.SourceFile.getAst(SourceFile.java:516)
 at javelin.ProxySourceFile.codeGen(ProxySourceFile.java:215)
 at javelin.SourceFile.codeGen(SourceFile.java:310)
 at
 javelin.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:1105)
 at javelin.client.Job.performJob(Job.java:81)
 
 Do you Guys think they are two seperate problems are they related
 

-- 
View this message in context:

Re: Axis2 Problem accessing the WSDL.

2007-11-27 Thread keith chapman

Yes I believe this is fixed in 1.3. Please try the 1.3 release.

Thanks,
Keith.

On Nov 27, 2007 11:18 AM, Deepal Jayasinghe [EMAIL PROTECTED] wrote:

 Hi tinkugadu ,
 May be a bug in Axis2 1.2 release , if you can please try with Axis2 1.3

 Thanks
 Deepal
  WHen i try to access the WSDL i get the StringIndexOUtOfBoundsException
  followed by the ClassCastException. WHen i try to access the
  csows/axis2-web/index.jsp from the Weblogic console then i just get the
  classcast exception
 
  my Environment:
 
  Webserver - Weblogic9
 
  axis version-  axis2 1.2
 
  I am not using axis2.xml
  i have listed the two exceptions below.
 
 
  Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
  ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
 weblogic.kernel.Default
  (self-tuning)' WLS Kernel   1196100514023 BEA-101020
  [EMAIL PROTECTED] - name: '
 csows.war',
  context-path: '/csows'] Servlet failed with Exception
  java.lang.StringIndexOutOfBoundsException: String index out of range:
 -11
  at java.lang.String.substring(String.java:1768)
  at java.lang.String.substring(String.java:1735)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(
 HTTPLocationBasedDispatcher.java:106)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(
 HTTPLocationBasedDispatcher.java:52)
  at
  org.apache.axis2.engine.AbstractDispatcher.invoke(
 AbstractDispatcher.java:100)
  at
  org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(
 RESTUtil.java:138)
  at
  org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(
 RESTUtil.java:95)
  at
 
 org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest
 (AxisServlet.java:776)
  at
  org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
  at
  weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(
 StubSecurityHelper.java:225)
  at
  weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
 StubSecurityHelper.java:127)
  at
  weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :272)
  at
  weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :165)
  at
 
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run
 (WebAppServletContext.java:3153)
  at
  weblogic.security.acl.internal.AuthenticatedSubject.doAs(
 AuthenticatedSubject.java:321)
  at
  weblogic.security.service.SecurityManager.runAs(SecurityManager.java
 :121)
  at
  weblogic.servlet.internal.WebAppServletContext.securedExecute(
 WebAppServletContext.java:1973)
  at
  weblogic.servlet.internal.WebAppServletContext.execute(
 WebAppServletContext.java:1880)
  at
  weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
 :1310)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
 
  Nov 26, 2007 1:08:35 PM EST Error HTTP lnx552.dteco.com
  ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
 weblogic.kernel.Default
  (self-tuning)' WLS Kernel   1196100515023 BEA-101107
  [EMAIL PROTECTED] - name: '
 csows.war',
  context-path: '/csows'] Problem occurred while serving the error page.
  java.lang.ClassCastException:
  org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
  at
  javax.xml.parsers.DocumentBuilderFactory.newInstance(
 DocumentBuilderFactory.java:98)
  at
  javelin.jsp.JspTagLibraryFeature.parseTldFromWebXML(
 JspTagLibraryFeature.java:857)
  at
  javelin.jsp.JspTagLibraryFeature.initFromWebXML(
 JspTagLibraryFeature.java:841)
  at
  javelin.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:442)
  at
  javelin.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:241)
  at
  javelin.jsp.JspTagLibraryFeature.setCPL(JspTagLibraryFeature.java:42)
  at javelin.CPL.getFeature(CPL.java:1580)
  at javelin.jsp.JspParser.getTagLibraryFeature(JspParser.java
 :3364)
  at javelin.jsp.JspParser.getTagLibInfo(JspParser.java:2127)
  at javelin.jsp.JspParser.jspParse(JspParser.java:430)
  at javelin.jsp.JspParser._parse(JspParser.java:349)
  at javelin.jsp.JspParser.parse(JspParser.java:342)
  at javelin.jsp.JspAnalyzer.parseFile(JspAnalyzer.java:113)
  at javelin.jsp.JspAnalyzer.parse(JspAnalyzer.java:101)
  at javelin.ProxySourceFile.parse(ProxySourceFile.java:117)
  at javelin.SourceFile.getAst(SourceFile.java:542)
  at javelin.SourceFile.getAst(SourceFile.java:516)
  at javelin.ProxySourceFile.codeGen(ProxySourceFile.java:215)
  at javelin.SourceFile.codeGen(SourceFile.java:310)

OMElement to org.w3c.dom.Document

2007-11-27 Thread Fátima Milla Olaya


Hi,
I want to transform a OMElement to a dom document, I've tried this:
OMElement omquery = policyQuery.getPolicyQuery();
DocumentImpl omdoc=new DocumentImpl(omquery.getOMFactory());
Element queryelement = omdoc.getDocumentElement();

and I get this exception:
Exception in thread main org.apache.axis2.AxisFault: 
org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory cannot be 
cast to org.apache.axiom.om.impl.dom.factory.OMDOMFactory


My webservice exchanges two xml files. Thanks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Exception on JaxRpc invoke: trailing block elements must have an id attribute

2007-11-27 Thread _ext Mehliss, Sven

Hello Apache-Axis User,

 

I am writing my diploma thesis about the integration of the Oracle Process 
Manager into a J2EE environment in order to use the BPEL advantages.

 

Now I have a problem and I am not able to solve this. I use Axis 1.4 as web 
service framework on a WebSphere application server. 

I can invoke every web service without having problems. But when the web 
service includes a DTO object as return value, I get the following error 
message.

 

--

messages

- input

- Invoke_1_reserveCar_InputVariable

- part xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; name=in0

- in0 xmlns= xmlns:def=urn:TravelBooking xsi:type=def:CarReservationDTO 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

carType

Mini

/carType 

customerName

12

/customerName 

customerPhone

21

/customerPhone 

reservationEnd

2013-12-12T00:00:00.000+01:00

/reservationEnd 

reservationStart

2012-12-12T00:00:00.000+01:00

/reservationStart 

/in0 

/part 

/Invoke_1_reserveCar_InputVariable 

/input 

- fault

- remoteFault xmlns=http://schemas.oracle.com/bpel/extension;

- part name=summary

summary

exception on JaxRpc invoke: trailing block elements must have an id attribute

/summary 

/part 

/remoteFault 

/fault 

/messages

--

 

I guess, this is a Axis problem because Axis does not support 
minOccurs/maxOccurs on xsd:sequence elements right now.

Using the internal web service implementation of WebSphere raises no exception 
and everything works fine.

 

Have you got any suggestion to solve this problem?

 

Thank you very much.

 

Kind regards,

Sven Mehliß

RE: rampart + maven2 == Unable to obtain unarchiver

2007-11-27 Thread sietsenicolaas.tenhoeve

Hi Steve,

From my point of view it should be resolved automatically when you are
using an mar based artifact. Although I don't have any clue where to
post a JIRA for this. Maybe the plugin shouldn't exclude the dependency
as I stated in my previous message. That sounds reasonable to me.

Sietse

-Original Message-
From: Stephen More [mailto:[EMAIL PROTECTED] 
Sent: 26 November 2007 19:01
To: axis-user@ws.apache.org
Subject: Re: rampart + maven2 == Unable to obtain unarchiver

 I think the problem is a missing dependency. A quick look at the pom 
 file of the addressing plugin pointed me into the 
 axis2-mar-maven-plugin. It is excluded into the dependencies, but I 
 don't know why.

Should I add this as a JIRA issue ?

 Thus adding the following snippet might solve the error:

 dependency
   groupIdorg.apache.axis2/groupId
   artifactIdaxis2-mar-maven-plugin/artifactId
   version1.3/version
 /dependency

Yes, this solved my problem.

-Thanks
Steve More

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: OMElement to org.w3c.dom.Document

2007-11-27 Thread Evgeniy Vyborov

Hi,

I think the simplest way to transform OMElement to DOM Element is to use static 
method toDOM(OMElement element) from org.apache.axis2.util.XMLUtils class.

Regards,
Eugene

Fátima Milla Olaya [EMAIL PROTECTED] wrote: Hi,
I want to transform a OMElement to a dom document, I've tried this:
OMElement omquery = policyQuery.getPolicyQuery();
DocumentImpl omdoc=new DocumentImpl(omquery.getOMFactory());
Element queryelement = omdoc.getDocumentElement();
 
and I get this exception:
Exception in thread main org.apache.axis2.AxisFault: 
org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory cannot be 
cast to org.apache.axiom.om.impl.dom.factory.OMDOMFactory

My webservice exchanges two xml files. Thanks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



   
-
Get easy, one-click access to your favorites.  Make Yahoo! your homepage.

RE: Microsoft interop gotcha - WSDL with minOccurs=0, type=xs:long

2007-11-27 Thread sietsenicolaas.tenhoeve

Nice explanation Mauro!

Your explanation shows the value of a good defined WSDL spec. This is
the case because the WSDL is used to specify the contract. In one of my
earlier messages I explained and linked to some information about strong
typed WSDL files.

Therefore I think the approach to use java2wsdl is wrong. Because you're
first writing an implementation and then build a contract around it. You
should do that in reverse order and thus start with specifying the WSDL
and generate code from that (well-defined) contract. This also abstracts
from any implementation language which adds even more value imho.

This doesn't solve your problem but I hope it gives you a view from
another perspective.

Just my two cents...

Regards,
Sietse

-Original Message-
From: Mauro Molinari [mailto:[EMAIL PROTECTED] 
Sent: 27 November 2007 08:07
To: axis-user@ws.apache.org
Subject: Re: Microsoft interop gotcha - WSDL with minOccurs=0,
type=xs:long

Hi Jason,
the first problem is that .NET translates optional WSDL elements
(i.e.: those with minOccurs=0 and maxOccurs=1 - please note
maxOccurs=1 is the default, if not specified) with a second boolean
parameter like xxxSpecified that states if the previous parameter has
been specified or not.
This is because .NET 1.1 was not able to specify null for primitive
types (like int, long, etc.; string is an exception), so the convention
is the following:
- any value, xxxSpecified = false = means null
- a value, xxxSpecified = true = means value

.NET 2.0 behaves the same, probably because of some kind of
retro-compatibility.

However, I would not consider that a big problem. If you are sure your
parameters cannot be null, you can manually delete all minOccurs=0;
otherwise, you may remove minOccurs=0 and substitute with
nillable=true, but be careful: as I said before, .NET 1.1 cannot
specify null for primitive types, so a .NET 1.1 client would not be able
to specify null for, say, an int parameter marked as nillable=true. 
.NET 2.0 does not have this problem.

The second (and real) problem is that if you are writing your web
services bottom up, Axis2 Java2WSDL always generates minOccurs=0 and,
in some circumstances, this can lead to bigger problems that the one you
described. Please also have a look to my bug report:
http://issues.apache.org/jira/browse/AXIS2-3300

Cheers.

--
Mauro Molinari
Software Developer
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Released Axis2 jars

2007-11-27 Thread alan

Why is axis2-adb-1.3.jar
missing from
http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.axis2/jars/
?

Alan M. Feldstein
Cosmic Horizon
http://www.alanfeldstein.com/
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 WSDL2Java error during service skeliton/stub generation

2007-11-27 Thread Mauro Molinari


Amila Suriarachchi ha scritto:

First of all now I have fixed the unwrapping problem and you should be
able to generate the code correctly with a nighly build.


Hi Amila,
unfortunately I'm still experiencing problems: this seems not to be fixed...

When you have empty return types, Axis2 doesn't unwrap the output to 
void, even if I specify -uw. Unwrapping of input parameters, instead, 
seems to work fine.


I'm attaching a WSDL that shows the problem. There are two methods:
- aMethod defines a response of an anonymous empty type; Axis2 generates 
a method that returns AMethodResponse, instead of void
- bMethod defines a response of type EmptyType: Axis2 generates a method 
that returns EmptyType, instead of void


I tried also with the latest nightly build...

I also found out that this can actually be a problem, because in order 
to get parameters unwrapped by .NET correctly, it is mandatory to 
specify both request and response messages with a part with name 
parameters. The part may refer to empty types, in order to be 
unwrapped to void by .NET. If you remove the part from the request or 
response message (so that Axis2 correctly generates void), .NET still 
generates void, but does not unwrap the output or input parameters 
respectively.


For instance, suppose you have:

wsdl:message name=logoutRequest
  part name=parameters element=txsns:logout /
/wsdl:message
wsdl:message name=logoutResponse /

in .NET this is translated to:
public void logout(logout logout1) (where type logout is a bean)

If Axis2 could unwrap empty types correctly, it would not be a problem 
to define something like:


wsdl:message name=logoutRequest
  part name=parameters element=txsns:logout /
/wsdl:message
wsdl:message name=logoutResponse
  part name=parameters element=txsns:logoutResponse /
/wsdl:message

with schema:

xsd:element name=logout
  xsd:complexType
sequence
  element name=ticket type=xsd:string /
/sequence
  /xsd:complexType
/xsd:element
xsd:element name=logoutResponse
  xsd:complexType/
/xsd:element

in order to get:

public void logout(string ticket) = .NET
and
public void logout(String ticket) = Java with Axis2

Thanks in advance!

--
Mauro Molinari
Software Developer
[EMAIL PROTECTED]
?xml version=1.0 encoding=UTF-8 standalone=no?
wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
  xmlns:tns=http://mauro/Prova;
  xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
  xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=ProvaService
  targetNamespace=http://mauro/Prova;
  xmlns:txsns=http://mauro/Prova/type;
  wsdl:types
xsd:schema targetNamespace=http://mauro/Prova/type;
  xmlns:txsns=http://mauro/Prova/type;
  xsd:element name=aMethod
xsd:complexType
  xsd:sequence
xsd:element name=a type=xsd:string /
  /xsd:sequence
/xsd:complexType
  /xsd:element

  xsd:element name=aMethodResponse
xsd:complexType /
  /xsd:element

  xsd:complexType name=EmptyType /

  xsd:element name=bMethod
xsd:complexType
  xsd:sequence
xsd:element name=a type=xsd:string /
  /xsd:sequence
/xsd:complexType
  /xsd:element

  xsd:element name=bMethodResponse type=txsns:EmptyType /
/xsd:schema
  /wsdl:types

  wsdl:message name=aMethodRequest
wsdl:part element=txsns:aMethod name=parameters /
  /wsdl:message
  wsdl:message name=aMethodResponse
wsdl:part element=txsns:aMethodResponse name=parameters /
  /wsdl:message
  wsdl:message name=bMethodRequest
wsdl:part name=parameters element=txsns:bMethod/wsdl:part
  /wsdl:message
  wsdl:message name=bMethodResponse
wsdl:part name=parameters element=txsns:bMethodResponse/wsdl:part
  /wsdl:message
  wsdl:portType name=ProvaService
wsdl:operation name=aMethod
  wsdl:input message=tns:aMethodRequest /
  wsdl:output message=tns:aMethodResponse /
/wsdl:operation
wsdl:operation name=bMethod
  wsdl:input message=tns:bMethodRequest/wsdl:input
  wsdl:output message=tns:bMethodResponse/wsdl:output
/wsdl:operation
  /wsdl:portType
  wsdl:binding name=ProvaServiceSOAP type=tns:ProvaService

soap:binding style=document
  transport=http://schemas.xmlsoap.org/soap/http; /
wsdl:operation name=aMethod

  soap:operation soapAction=http://mauro/Prova/aMethod; /
  wsdl:input
soap:body use=literal /
  /wsdl:input
  wsdl:output
soap:body use=literal /
  /wsdl:output
/wsdl:operation

wsdl:operation name=bMethod
  soap:operation soapAction=http://mauro/Prova/bMethod; /

  wsdl:input
soap:body use=literal /
  /wsdl:input
  wsdl:output

soap:body use=literal /
  /wsdl:output
/wsdl:operation
  /wsdl:binding

  wsdl:service name=ProvaService
wsdl:port binding=tns:ProvaServiceSOAP name=ProvaServiceSOAP
  soap:address location=http://www.example.org/; /
/wsdl:port
  /wsdl:service
/wsdl:definitions

SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Wang Han

Hi guys,

Service echo is deployed at:
http://localhost:8080/axis/services/echo, SOAPMonitor is at
http://localhost:8080/axis/SOAPMonitor.
I can use SOAPMonitor to monitor all soap messages between echo
service and its client.

For some special requirement, I need re-deploy the echo service to
http://localhost:8080/echo.
I implement it successfully by modifying tomcat/conf/server.xml and
webapps/axis/web.xml.

But the SOAPMonitor is not there any more. I  try to access it by
http://localhost:8080/SOAPMonitor,
It always gives me load applet failed error message.

Could someone tell me how can I find back the SOAPMonitor? thanks a lot!

Tomcat6.0 + axis1.4.
tomcat/conf/server.xml:
  Host name=localhost  appBase=webapps/axis
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
 Context path=/ docBase=./

webapps/axis/WEB-INF/web.xml:
  servlet-mapping
   servlet-nameAxisServlet/servlet-name
   !-- use it when need SOAPMon url-pattern/services/*/url-pattern --
   url-pattern/*/url-pattern
  /servlet-mapping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Changing Axis SOAP from rpc/encoded to document/literal or wrapped

2007-11-27 Thread Anne Thomas Manes

My guess is that your provider class
(com.workingmouse.webservice.axis.SpringBeanRPCProvider) only knows
how to produce rpc/encoded messages. You will need to replace it. I
suggest you use style=wrapped rather than style=document.
Otherwise you will need to change your application code .

Anne

On Nov 26, 2007 3:47 AM, TAnnison [EMAIL PROTECTED] wrote:

 I'm a SOAP newbie, working on a project that has already been configured by
 coders that have since departed. And I'm floundering about a bit, and
 wondering if you could possibly give me some advice?

 We have a Java project built with the Spring framework, using Axis in order
 to provide webservices for access via SOAP. As I understand it (ie not very
 well!) Axis works to accept these SOAP messages from the client and
 transform them into calls on our Java methods, and do the reverse with the
 responses! And to handle SOAP calls going outwards in a similar way. Which
 is excellent, and it works well with the config files we have already set
 up.

 All our webservices all talk to each other just fine, and will talk also to
 an external service using rpc/encoded. But now I need to make them talk to
 other things also, that want document/literal or wrapped styles, and don't
 like multirefs, and so on. So I tried changing the sendMultiRefs and
 style and use settings in our axis config file, server-config.wsdd :

 globalConfiguration
 parameter name=sendXsiTypes value=true/
 parameter name=sendMultiRefs value=false/  [was true]
 parameter name=sendXMLDeclaration value=true/
 parameter name=axis.sendMinimizedElements value=true/
 /globalConfiguration

 service name=TestMessageSender provider=Handler style=document
 use=literal [was just rpc]
 parameter name=handlerClass
 value=com.workingmouse.webservice.axis.SpringBeanRPCProvider/
 parameter name=springBean value=testMessageSender/
 parameter name=springBeanClass
 value=uk.co.wibblewibble.AxisTestMessageSender/
 parameter name=allowedMethods value=*/
 parameter name=scope value=application/
 /service


 But none of them seem to have any effect whatsoever! Whatever I set, I still
 get SOAP sent that looks like this :

 ?xml version=1.0 encoding=UTF-8?
 soapenv:Envelope 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:Body
 ns1:getResponse
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
 xmlns:ns1=http://hostName/recieverLiteral;
 link xsi:type=xsd:stringLink/link
 cCode href=#id0/
 dCode href=#id1/
 pNumber xsi:type=xsd:stringPoster/pNumber
 replyMessage xsi:type=xsd:stringtest message information to
 send/replyMessage
 authenticationUser
 xsi:type=xsd:stringAdmin/authenticationUser
 /ns1:getResponse
 multiRef id=id0 soapenc:root=0
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
 xsi:type=xsd:decimal
 xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;1/multiRef
 multiRef id=id1 soapenc:root=0
 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
 xsi:type=xsd:decimal
 xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;6/multiRef
 /soapenv:Body
 /soapenv:Envelope

 I'm confused, and just wondering if these are not taking effect because the
 choice of SpringBeanRPCProvider as the handlerClass (whatever these things
 are!) is overriding them. Could you possibly tell me if this is the case?

 I'd also greatly appreciate any help you could possibly give me on how to
 proceed with changing the SOAP styles, as I'm really in the dark about the
 whole thing. All the advice I see anywhere seems to say that what I've done
 is all that's needed, and yet nothing changes!

 Thanks!
 --
 View this message in context: 
 http://www.nabble.com/Changing-Axis-SOAP-from-rpc-encoded-to-document-literal-or-wrapped-tf4873899.html#a13945944
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Changing Axis SOAP from rpc/encoded to document/literal or wrapped

2007-11-27 Thread TAnnison


Thanks, Anne

Oddly enough, I did locate and try a SpringBeanMsgProvider just yesyerday,
and that's meant to handle the other sorts of messages. But it made no
difference at all to the XML it put out! Which is mystifying to me. I'm
wondering if maybe the wsdd only controls Axis for incoming messages or
something, though the inclusion of a sendMultirefs is a bit of a puzzler
if that's the case. :)

All very confusing! Wish I had a working example of Spring, Axis and both
sending  receiving service code...

Cheers
Tracey


Anne Thomas Manes wrote:
 
 My guess is that your provider class
 (com.workingmouse.webservice.axis.SpringBeanRPCProvider) only knows
 how to produce rpc/encoded messages. You will need to replace it. I
 suggest you use style=wrapped rather than style=document.
 Otherwise you will need to change your application code .
 
 Anne
 

-- 
View this message in context: 
http://www.nabble.com/Changing-Axis-SOAP-from-rpc-encoded-to-document-literal-or-wrapped-tf4873899.html#a13971788
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread [EMAIL PROTECTED]


I guess it should work fine with IE. If not, refer to Appendix: Enabling the
SOAP Monitor' under User Guide in your docs folder.

Wang Han wrote:
 
 Hi guys,
 
 Service echo is deployed at:
 http://localhost:8080/axis/services/echo, SOAPMonitor is at
 http://localhost:8080/axis/SOAPMonitor.
 I can use SOAPMonitor to monitor all soap messages between echo
 service and its client.
 
 For some special requirement, I need re-deploy the echo service to
 http://localhost:8080/echo.
 I implement it successfully by modifying tomcat/conf/server.xml and
 webapps/axis/web.xml.
 
 But the SOAPMonitor is not there any more. I  try to access it by
 http://localhost:8080/SOAPMonitor,
 It always gives me load applet failed error message.
 
 Could someone tell me how can I find back the SOAPMonitor? thanks a lot!
 
 Tomcat6.0 + axis1.4.
 tomcat/conf/server.xml:
   Host name=localhost  appBase=webapps/axis
 unpackWARs=true autoDeploy=true
 xmlValidation=false xmlNamespaceAware=false
  Context path=/ docBase=./
 
 webapps/axis/WEB-INF/web.xml:
   servlet-mapping
servlet-nameAxisServlet/servlet-name
!-- use it when need SOAPMon url-pattern/services/*/url-pattern
 --
url-pattern/*/url-pattern
   /servlet-mapping
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Wang Han

Hi Vaibhav,

load applet failed occurs when I use firefox.
But I can't access the SOAPMonitor either by IE -- it brings me to a
searching page immediately
with http://localhost:8080; in the searching bar once I try to open
the link in IE.

I do read the appendix and deployed the service successfully before
setting the virtual host.

After setting the virtual host, I try to re-deploy the SOAPMonitor
according to the appendix as below:
1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
2. executing java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/AdminService deploy-monitor.wsdd
successfully.
3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
then failed.

Please correct me if I made any mistake here,Thanks.

On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 I guess it should work fine with IE. If not, refer to Appendix: Enabling the
 SOAP Monitor' under User Guide in your docs folder.


 Wang Han wrote:
 
  Hi guys,
 
  Service echo is deployed at:
  http://localhost:8080/axis/services/echo, SOAPMonitor is at
  http://localhost:8080/axis/SOAPMonitor.
  I can use SOAPMonitor to monitor all soap messages between echo
  service and its client.
 
  For some special requirement, I need re-deploy the echo service to
  http://localhost:8080/echo.
  I implement it successfully by modifying tomcat/conf/server.xml and
  webapps/axis/web.xml.
 
  But the SOAPMonitor is not there any more. I  try to access it by
  http://localhost:8080/SOAPMonitor,
  It always gives me load applet failed error message.
 
  Could someone tell me how can I find back the SOAPMonitor? thanks a lot!
 
  Tomcat6.0 + axis1.4.
  tomcat/conf/server.xml:
Host name=localhost  appBase=webapps/axis
  unpackWARs=true autoDeploy=true
  xmlValidation=false xmlNamespaceAware=false
   Context path=/ docBase=./
 
  webapps/axis/WEB-INF/web.xml:
servlet-mapping
 servlet-nameAxisServlet/servlet-name
 !-- use it when need SOAPMon url-pattern/services/*/url-pattern
  --
 url-pattern/*/url-pattern
/servlet-mapping
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

 --
 View this message in context: 
 http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 1.3 Rest Support

2007-11-27 Thread John Pfeifer

I recently upgraded from Axis2 1.1 to 1.3.  In version 1.1 I configured the 
RestServlet to handle all requests to /rest/*.  

The web services themselves aren't truely restful, but I need to be able to 
support both SOAP and POX.  Basically what I want is for my web service to 
support both SOAP and POX without having to modify my code.  This was working 
perfectly before as Axis2 stripped off the SOAP Envelop for SOAP requests and 
left Rest requests alone.  This is the behavior that I want, but I am having 
difficulty figuring out how to configure the server side.

Since upgrading to 1.3, I discovered that the RestServlet no longer exists.  In 
addition, I am having difficulty figuring out how to configure the server side. 
 Are SOAP and Rest request handled by a single endpoint now?  If so, the axis2 
documentation says REST Web Services do not have Headers and the payload is 
sent directly., does this mean that Rest services don't have a SOAP Envelope, 
or that HTTP SOAP Headers are absent?

I would appreciate it if someone could point me in the right direction, or 
refer me to some documentation that has a bit more detail than the RESTful Web 
Services Support page in the Axis2 docs.

Thanks,

John

Re: Axis2 1.3 Rest Support

2007-11-27 Thread keith chapman

Hi John,

Yes both SOAP and REST request are handled by the same endpoint and there is
no /soap/ or /rest/ in the request URL now.

Yes REST services don't require a SOAP envelop and you can send the request
via GET , POST, PUT or DELETE.

The easiest way to test REST is to go to
http://localhost:8080/axis2/services/version/getVersion on the browser. This
will send a GET to the version service which would respond using a POX
response.

If you want true REST behaviour where you can send parameters in the path
segment or as customized query parameters you shpu;d have a look at
WSDL 2.0HTTPBinding. If you deploy a service using WSDL
2.0 Axis2 can handle request as described in your WSDL.

for eg. Axis2 default URL to get the version of the version service would be
http://localhost:8080/axis2/services/version/getVersion but if you deployed
this service via a WSDL 2.0 you can alter the request URL to suite your
needs.

If you need more help please let me know. I'll be glad to assist you.

Thanks,
Keith.

On Nov 27, 2007 9:07 PM, John Pfeifer [EMAIL PROTECTED] wrote:

  I recently upgraded from Axis2 1.1 to 1.3.  In version 1.1 I configured
 the RestServlet to handle all requests to /rest/*.

 The web services themselves aren't truely restful, but I need to be able
 to support both SOAP and POX.  Basically what I want is for my web service
 to support both SOAP and POX without having to modify my code.  This was
 working perfectly before as Axis2 stripped off the SOAP Envelop for SOAP
 requests and left Rest requests alone.  This is the behavior that I want,
 but I am having difficulty figuring out how to configure the server side.

 Since upgrading to 1.3, I discovered that the RestServlet no longer
 exists.  In addition, I am having difficulty figuring out how to configure
 the server side.  Are SOAP and Rest request handled by a single endpoint
 now?  If so, the axis2 documentation says REST Web Services do not have
 Headers and the payload is sent directly., does this mean that Rest
 services don't have a SOAP Envelope, or that HTTP SOAP Headers are absent?

 I would appreciate it if someone could point me in the right direction, or
 refer me to some documentation that has a bit more detail than the RESTful
 Web Services Support page in the Axis2 docs.

 Thanks,

 John




-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

[Axis2 1.3] REST + POJO + Attachments

2007-11-27 Thread albert quinn

  Hi all !! :

  I'm wondering if it could be possible to develop a POJO Web Service
like this (using Axis2 RC1.3) :

class POJOWebService {

...

  public CustomType pojoWebServiceOperation(DataHandler dhArray[])  {

  // do something with the received files

  }

...

}

  and then, calling this Web Service Operation from a HTML page with a
form sending the files with POST.

  Could this work?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis use RMI?

2007-11-27 Thread Antonio Manuel Muñiz Martín

Thanks for your replies.

Saludos Martin! ;-)

2000/11/26, Martin Gainty [EMAIL PROTECTED]:

  This is by design
 http://ws.apache.org/axis/java/install.html
 RMI and CORBA both have tight binding to transport plumbing as well
 as proprietary serialisation/deserialisation restrictions
 Axis was designed to run free of transport binding implementation as well
 as deserialisation algorithms

 Saludos!
 *Martín*
 - Original Message -

 *From:* Antonio Manuel Muñiz Martín [EMAIL PROTECTED]
 *To:* axis-user axis-user@ws.apache.org
 *Sent:* Monday, November 26, 2007 10:41 AM
 *Subject:* Axis use RMI?

 Hi.

 When you generate an axis client using XMLBeans as data binding, you call
 web service operations with this statement:

 ServiceStub = new ServiceStub();
 stub.operation();

 This lines throws java.rmi.RemoteException

 Axis uses Java RMI?

Re: OMElement to org.w3c.dom.Document

2007-11-27 Thread Fátima Milla Olaya


Thanks,it's worked.

Evgeniy Vyborov a écrit :

Hi,

I think the simplest way to transform OMElement to DOM Element is to 
use static method toDOM(OMElement element) from 
org.apache.axis2.util.XMLUtils class.


Regards,
Eugene

*/Fátima Milla Olaya [EMAIL PROTECTED]/* wrote:

Hi,
I want to transform a OMElement to a dom document, I've tried this:
OMElement omquery = policyQuery.getPolicyQuery();
DocumentImpl omdoc=new DocumentImpl(omquery.getOMFactory());
Element queryelement = omdoc.getDocumentElement();

and I get this exception:
Exception in thread main org.apache.axis2.AxisFault:
org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory
cannot be
cast to org.apache.axiom.om.impl.dom.factory.OMDOMFactory

My webservice exchanges two xml files. Thanks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Get easy, one-click access to your favorites. Make Yahoo! your 
homepage. http://us.rd.yahoo.com/evt=51443/*http://www.yahoo.com/r/hs 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Silly question about how to shutdown axis

2007-11-27 Thread Kjell Nilsson

This is probably a silly newbee question but how do I shutdown a  
standalone axis server.


I have implemented the ServiceLifeCycle interface so I can do late  
late cleanup database

and jms stuff, and this works nice.

Since I have developed on a Mac the Unix command 'kill' takes down the  
axisserver nice and
clean, calling my shutDown() method. But my problem is that I will  
deploy this axis2server on
OpenVMS and there is not a 'kill' command there, only a 'delete/entry'  
command that does

like 'kill -9', and thats not nice since the server dies abruptly.

So what strategy shall I use? Implement an operation that will  
shutdown axis2 from inside?
If so what method can I call to stop the server and how do I get hold  
of the objects that

has the stop method? Or is there a static method somewhere to call?

Any hint will be fine ;-)

Kind regards
--kjell



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: problem with axis and sockets

2007-11-27 Thread tina--


thank you Michelle Mazzucco!!
-- 
View this message in context: 
http://www.nabble.com/problem-with-axis-and-sockets-tf4840115.html#a13975682
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: add webservice to web application

2007-11-27 Thread LUSS


Finallyy
Thank you for the link it is very very useful

- I edited web.xml and added
- I created the folders same as the example
- I created services.xml
- I rebuilt the project (not with mavin with netbeans)
- And it worked... It was easier than expected, i spent long time with it...

Thanks!
Lucien


[EMAIL PROTECTED] wrote:
 
 There is some info here which you might be interested in
 
 http://wso2.org/library/90
 Thanks
 Gaurav
 
 LUSS wrote:
 hello,
 I have a web application deployed on tomcat/webapps folder, my client
 asked me to publish a method as webservice within this web application,
 i'm
 using Axis2, i generated the wsdl and the services.xml correctly but i
 don't
 know how to publish the method from the application deployed on
 tomcat\webapps\MyApplication and not from
 webapps\axis2\WEB-INF\services\MyApplication.aar
 Thank you for your help.
   
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/add-webservice-to-web-application-tf4877871.html#a13975683
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AxisFault: already connected

2007-11-27 Thread tina--


what does this mean? 
-- 
View this message in context: 
http://www.nabble.com/AxisFault%3A-already-connected-tf4883262.html#a13975783
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Axis2 1.3 Rest Support

2007-11-27 Thread John Pfeifer

Keith,

Thanks for the info.  I deployed the axis2.war file and the Version service 
works properly.  The axis2.xml is identical to the one that I use in my war 
file.  I am still having the same issue with my web service however.  Perhaps 
the snippet below may explain what is happening.  It looks like Axis wants to 
use the SOAPBuilder for the POX request.  I have confirmed that I am sending 
XML without SOAP Envelope, so I am not sure why it's attempting to use the 
SOAPBuilder.  Any ideas?  

11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: 
'weblogic.kernel.Default (self-tuning)'|DEBUG|builder.BuilderUtil|Input 
contentType (text/xml)|
11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: 
'weblogic.kernel.Default 
(self-tuning)'|DEBUG|builder.BuilderUtil|CharSetEncoding defaulted (UTF-8)|
11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: 
'weblogic.kernel.Default 
(self-tuning)'|DEBUG|transport.TransportUtils|createSOAPEnvelope using Builder 
(class org.apache.axis2.builder.SOAPBuilder) selected from type 
(application/xml)|
11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: 
'weblogic.kernel.Default (self-tuning)'|DEBUG|builder.BuilderUtil|char set 
encoding set from default =UTF-8|
11/27/07 12:24:15:390|[ACTIVE] ExecuteThread: '2' for queue: 
'weblogic.kernel.Default 
(self-tuning)'|DEBUG|http.AxisServlet|org.apache.axis2.AxisFault: First Element 
must contain the local name, Envelope , but found 
PayCaptureRequestServiceRequest|


Thanks,

John



-Original Message-
From: keith chapman [mailto:[EMAIL PROTECTED]
Sent: Tue 11/27/2007 11:07 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.3 Rest Support
 
Hi John,

Yes both SOAP and REST request are handled by the same endpoint and there is
no /soap/ or /rest/ in the request URL now.

Yes REST services don't require a SOAP envelop and you can send the request
via GET , POST, PUT or DELETE.

The easiest way to test REST is to go to
http://localhost:8080/axis2/services/version/getVersion on the browser. This
will send a GET to the version service which would respond using a POX
response.

If you want true REST behaviour where you can send parameters in the path
segment or as customized query parameters you shpu;d have a look at
WSDL 2.0HTTPBinding. If you deploy a service using WSDL
2.0 Axis2 can handle request as described in your WSDL.

for eg. Axis2 default URL to get the version of the version service would be
http://localhost:8080/axis2/services/version/getVersion but if you deployed
this service via a WSDL 2.0 you can alter the request URL to suite your
needs.

If you need more help please let me know. I'll be glad to assist you.

Thanks,
Keith.

On Nov 27, 2007 9:07 PM, John Pfeifer [EMAIL PROTECTED] wrote:

  I recently upgraded from Axis2 1.1 to 1.3.  In version 1.1 I configured
 the RestServlet to handle all requests to /rest/*.

 The web services themselves aren't truely restful, but I need to be able
 to support both SOAP and POX.  Basically what I want is for my web service
 to support both SOAP and POX without having to modify my code.  This was
 working perfectly before as Axis2 stripped off the SOAP Envelop for SOAP
 requests and left Rest requests alone.  This is the behavior that I want,
 but I am having difficulty figuring out how to configure the server side.

 Since upgrading to 1.3, I discovered that the RestServlet no longer
 exists.  In addition, I am having difficulty figuring out how to configure
 the server side.  Are SOAP and Rest request handled by a single endpoint
 now?  If so, the axis2 documentation says REST Web Services do not have
 Headers and the payload is sent directly., does this mean that Rest
 services don't have a SOAP Envelope, or that HTTP SOAP Headers are absent?

 I would appreciate it if someone could point me in the right direction, or
 refer me to some documentation that has a bit more detail than the RESTful
 Web Services Support page in the Axis2 docs.

 Thanks,

 John




-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

winmail.dat-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Running Savan (WS-Eventing) Samples

2007-11-27 Thread Enrique Rodríguez Lasterra

I can run the savan example with few little changes. But I have some
errors/doubts

1.- I can subscribe Listeners to Publisher, but when i ask for the listener
status i always get null.

2.-In the WSDL i don't see any namespace/import of ws-eventing, why?

3.- Publisher porttype should have the EventSource=true attribute, isn't
it?

There is no much information about savan and ws-eventing, so any help is
appreciated.

Regards, Enrique.

-- 
___
Enrique Rodriguez Lasterra
lasterra AT javahispano DOT org
http://www.javahispano.org
Asociación sin ánimo de lucro sobre java
Spanish non profit association about java

Re: Silly question about how to shutdown axis

2007-11-27 Thread Martin Gainty

unless its 2am and you need to stop a runaway task you should quiesce your
axis2 webapp to allow the connections to be closed *gracefully*
e.g.
assuming your axis2 webapp is called axis2 which is running on localhost
port 8080 put this in your browser
http://localhost:8080/manager/html/stop?path=/axis2

Tack
M--
- Original Message -
From: Kjell Nilsson [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, November 27, 2007 12:33 PM
Subject: Silly question about how to shutdown axis


 This is probably a silly newbee question but how do I shutdown a
 standalone axis server.

 I have implemented the ServiceLifeCycle interface so I can do late
 late cleanup database
 and jms stuff, and this works nice.

 Since I have developed on a Mac the Unix command 'kill' takes down the
 axisserver nice and
 clean, calling my shutDown() method. But my problem is that I will
 deploy this axis2server on
 OpenVMS and there is not a 'kill' command there, only a 'delete/entry'
 command that does
 like 'kill -9', and thats not nice since the server dies abruptly.

 So what strategy shall I use? Implement an operation that will
 shutdown axis2 from inside?
 If so what method can I call to stop the server and how do I get hold
 of the objects that
 has the stop method? Or is there a static method somewhere to call?

 Any hint will be fine ;-)

 Kind regards
 --kjell



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 Problem accessing the WSDL.

2007-11-27 Thread tinkugadu



Hi,

I tried using Axis2 1.3 jars, when i tried getting the WSDL , then i get the
following exception on the browser. I still see the old classCastException,
still in the logs. 

Exceptionorg.apache.axis2.AxisFault: The endpoint reference (EPR) for the
Operation not found is /csows/services/EnrollmentMgtService?WSDL and the WSA
Action = null at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:86)
at org.apache.axis2.engine.Phase.invoke(Phase.java:308) at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:125)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:119)
at
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:799)
at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:179)/Exception 




keith chapman wrote:
 
 Yes I believe this is fixed in 1.3. Please try the 1.3 release.
 
 Thanks,
 Keith.
 
 On Nov 27, 2007 11:18 AM, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
 
 Hi tinkugadu ,
 May be a bug in Axis2 1.2 release , if you can please try with Axis2 1.3

 Thanks
 Deepal
  WHen i try to access the WSDL i get the StringIndexOUtOfBoundsException
  followed by the ClassCastException. WHen i try to access the
  csows/axis2-web/index.jsp from the Weblogic console then i just get the
  classcast exception
 
  my Environment:
 
  Webserver - Weblogic9
 
  axis version-  axis2 1.2
 
  I am not using axis2.xml
  i have listed the two exceptions below.
 
 
  Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
  ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
 weblogic.kernel.Default
  (self-tuning)' WLS Kernel   1196100514023 BEA-101020
  [EMAIL PROTECTED] - name: '
 csows.war',
  context-path: '/csows'] Servlet failed with Exception
  java.lang.StringIndexOutOfBoundsException: String index out of range:
 -11
  at java.lang.String.substring(String.java:1768)
  at java.lang.String.substring(String.java:1735)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(
 HTTPLocationBasedDispatcher.java:106)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(
 HTTPLocationBasedDispatcher.java:52)
  at
  org.apache.axis2.engine.AbstractDispatcher.invoke(
 AbstractDispatcher.java:100)
  at
  org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(
 RESTUtil.java:138)
  at
  org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(
 RESTUtil.java:95)
  at
 
 org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest
 (AxisServlet.java:776)
  at
  org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
  at
  weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(
 StubSecurityHelper.java:225)
  at
  weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
 StubSecurityHelper.java:127)
  at
  weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :272)
  at
  weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :165)
  at
 
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run
 (WebAppServletContext.java:3153)
  at
  weblogic.security.acl.internal.AuthenticatedSubject.doAs(
 AuthenticatedSubject.java:321)
  at
  weblogic.security.service.SecurityManager.runAs(SecurityManager.java
 :121)
  at
  weblogic.servlet.internal.WebAppServletContext.securedExecute(

RE: Axis2 Problem accessing the WSDL.

2007-11-27 Thread Raghu Upadhyayula

Hi tinkugadu,

From the exception it appears to me that you are trying to get
the wsdl using ?WSDL but you have to use ?wsdl (it is case sensitive).

Thanks
Raghu

-Original Message-
From: tinkugadu [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 27, 2007 1:16 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 Problem accessing the WSDL.



Hi,

I tried using Axis2 1.3 jars, when i tried getting the WSDL , then i get
the
following exception on the browser. I still see the old
classCastException,
still in the logs. 

Exceptionorg.apache.axis2.AxisFault: The endpoint reference (EPR) for
the
Operation not found is /csows/services/EnrollmentMgtService?WSDL and the
WSA
Action = null at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.
java:86)
at org.apache.axis2.engine.Phase.invoke(Phase.java:308) at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.
java:125)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil
.java:119)
at
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.process
URLRequest(AxisServlet.java:799)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
ubSecurityHelper.java:225)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
elper.java:127)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
72)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:1
65)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:3153)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
letContext.java:1973)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
ext.java:1880)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:179)/Exception 




keith chapman wrote:
 
 Yes I believe this is fixed in 1.3. Please try the 1.3 release.
 
 Thanks,
 Keith.
 
 On Nov 27, 2007 11:18 AM, Deepal Jayasinghe [EMAIL PROTECTED]
wrote:
 
 Hi tinkugadu ,
 May be a bug in Axis2 1.2 release , if you can please try with Axis2
1.3

 Thanks
 Deepal
  WHen i try to access the WSDL i get the
StringIndexOUtOfBoundsException
  followed by the ClassCastException. WHen i try to access the
  csows/axis2-web/index.jsp from the Weblogic console then i just get
the
  classcast exception
 
  my Environment:
 
  Webserver - Weblogic9
 
  axis version-  axis2 1.2
 
  I am not using axis2.xml
  i have listed the two exceptions below.
 
 
  Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
  ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
 weblogic.kernel.Default
  (self-tuning)' WLS Kernel   1196100514023 BEA-101020
  [EMAIL PROTECTED] - name: '
 csows.war',
  context-path: '/csows'] Servlet failed with Exception
  java.lang.StringIndexOutOfBoundsException: String index out of
range:
 -11
  at java.lang.String.substring(String.java:1768)
  at java.lang.String.substring(String.java:1735)
  at
 
org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(
 HTTPLocationBasedDispatcher.java:106)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(
 HTTPLocationBasedDispatcher.java:52)
  at
  org.apache.axis2.engine.AbstractDispatcher.invoke(
 AbstractDispatcher.java:100)
  at
  org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(
 RESTUtil.java:138)
  at
  org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(
 RESTUtil.java:95)
  at
 

org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processUR
LRequest
 (AxisServlet.java:776)
  at
 
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
  at
 
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(
 StubSecurityHelper.java:225)
  at
  weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
 StubSecurityHelper.java:127)
  at
 
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :272)
  at
 
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java
 :165)
  at

Progress monitoring for Axis2 OperationClient.execute()?

2007-11-27 Thread Marc Missire

Hi,

I have an application that uses Soap With Attachments to do file transfer.
I'm trying to determine how to monitor the file download progress; the call
to OperationClient.execute() takes, for example, 20 seconds, and I need to
display a progress bar duirng that time.

I am familiar with these techniques:

1) Using the Axis2 file caching option. I thought I'd monitor the attachment
file, as it grew. I tried this with a 22mb file. The temporary file was
written, but not until the entire time had elapsed and the whole file had
been transferring to the client. Must be buffering it. Maybe this would be
useful with really large files, but it didn't help me.

2) Splitting the download into sections and doing it with multiple calls. I
am considering this, but it doesn't sound ideal.


Is there a way to do this? I certainly can determine how big the file is
before the download starts. But is there a way to monitor progress once the
client has disappeared into OperationClient.execute()?

Thanks,
Marc

Axis Version 1 Question/Problem

2007-11-27 Thread deklotz


Hello.

I have been working on this problem for days now and it seems as if I'm
taking one step 
forward and two back. I could use your help please. The short story is that
I'm trying
to logout a josso session id via a web service from within a servlet and it
fails seemingly
within the Axis layer before contacting the outside world.

Here is the mysterious error from my tomcat log:

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.apache.axis.ConfigurationException:
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication

What I have and what I know:
- Tomcat 5.5.15
- Java 1.5
- A third party webapp (JOSSO 1.5) that provides single-sign-on services
with an exposed 
web service. (using I think Axis 1.2)
- My own web application servlet that is attempting to call one of the
exposed services on a 
different server. 
- That my call, from within my own servlet, fails down inside of the Axis
call:
(org.apache.axis.client.Call.invoke(Call.java:1804)).
- That if I test the web service directly using something like e-tester
(from empirix), the web 
service works.
- That I think... I  have setup ant helper task correctly to generate the
stub classes (using 
the same wsdl that I tested above).
- That I'm about to go crazy.

So I guess the really quick question is if the above exception, which is
repeated, makes any 
sense? I am posting long details at the bottom.


Regards,

-Dennis 


-

build.xml snippet: 
 
target name=generate-axis-stubs description=build Axis stubs 
!-- Generate Stub/Skeleton pair for the SSOIdentityProvider Service -- 
axis-wsdl2java 
output=${build.home} 
testcase=false 
verbose=true 
url=${basedir}/wsdl/SSOIdentityProvider.wsdl 
serverside=true 
skeletondeploy=true 
classpath path=${compile.classpath}/ 
/axis-wsdl2java 
/target  

---

servlet code snippet: 
 
URL endpoint = new URL
(http://10.16.207.59/josso/services/SSOIdentityProvider;); 
SSOIdentityProviderService webService = new
SSOIdentityProviderServiceLocator();  
SSOIdentityProvider impl = webService.getSSOIdentityProvider(endpoint);

impl.globalSignoff(jossoSessionCookie.getValue()); 

---

AxisFault 
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException 
faultSubcode: 
faultString: org.apache.axis.ConfigurationException:
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication 
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
 
at
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125) 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
 
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
 
at
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
 
at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365) 
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126) 
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
org.josso.gateway.identity.service.ws.impl.SSOIdentityProviderSoapBindingStub.globalSignoff(SSOIdentityProviderSoapBindingStub.java:303)
 
 

---

The global signoff method from SSOIdentityProviderSoapbindingStub.java

public void globalSignoff (java.lang.String in0) throws
java.rmi.RemoteException,
   
org.josso.gateway.identity.service.ws.impl.IdentityProvisioningException
{
if (super.cachedEndpoint == null)
{
throw new org.apache.axis.NoEndPointException();
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[2]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI();

RE: Axis2 Problem accessing the WSDL.

2007-11-27 Thread tinkugadu


raghu,

that did not solve the problem. 

Raghu Upadhyayula wrote:
 
 Hi tinkugadu,
 
   From the exception it appears to me that you are trying to get
 the wsdl using ?WSDL but you have to use ?wsdl (it is case sensitive).
 
 Thanks
 Raghu
 
 -Original Message-
 From: tinkugadu [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, November 27, 2007 1:16 PM
 To: axis-user@ws.apache.org
 Subject: Re: Axis2 Problem accessing the WSDL.
 
 
 
 Hi,
 
 I tried using Axis2 1.3 jars, when i tried getting the WSDL , then i get
 the
 following exception on the browser. I still see the old
 classCastException,
 still in the logs. 
 
 Exceptionorg.apache.axis2.AxisFault: The endpoint reference (EPR) for
 the
 Operation not found is /csows/services/EnrollmentMgtService?WSDL and the
 WSA
 Action = null at
 org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.
 java:86)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:308) at
 org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at
 org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at
 org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.
 java:125)
 at
 org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil
 .java:119)
 at
 org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.process
 URLRequest(AxisServlet.java:799)
 at
 org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
 ubSecurityHelper.java:225)
 at
 weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
 elper.java:127)
 at
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
 72)
 at
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:1
 65)
 at
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
 un(WebAppServletContext.java:3153)
 at
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
 bject.java:321)
 at
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
 )
 at
 weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
 letContext.java:1973)
 at
 weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
 ext.java:1880)
 at
 weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
 :1310)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at
 weblogic.work.ExecuteThread.run(ExecuteThread.java:179)/Exception 
 
 
 
 
 keith chapman wrote:
 
 Yes I believe this is fixed in 1.3. Please try the 1.3 release.
 
 Thanks,
 Keith.
 
 On Nov 27, 2007 11:18 AM, Deepal Jayasinghe [EMAIL PROTECTED]
 wrote:
 
 Hi tinkugadu ,
 May be a bug in Axis2 1.2 release , if you can please try with Axis2
 1.3

 Thanks
 Deepal
  WHen i try to access the WSDL i get the
 StringIndexOUtOfBoundsException
  followed by the ClassCastException. WHen i try to access the
  csows/axis2-web/index.jsp from the Weblogic console then i just get
 the
  classcast exception
 
  my Environment:
 
  Webserver - Weblogic9
 
  axis version-  axis2 1.2
 
  I am not using axis2.xml
  i have listed the two exceptions below.
 
 
  Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
  ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
 weblogic.kernel.Default
  (self-tuning)' WLS Kernel   1196100514023 BEA-101020
  [EMAIL PROTECTED] - name: '
 csows.war',
  context-path: '/csows'] Servlet failed with Exception
  java.lang.StringIndexOutOfBoundsException: String index out of
 range:
 -11
  at java.lang.String.substring(String.java:1768)
  at java.lang.String.substring(String.java:1735)
  at
 
 org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(
 HTTPLocationBasedDispatcher.java:106)
  at
  org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(
 HTTPLocationBasedDispatcher.java:52)
  at
  org.apache.axis2.engine.AbstractDispatcher.invoke(
 AbstractDispatcher.java:100)
  at
  org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(
 RESTUtil.java:138)
  at
  org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(
 RESTUtil.java:95)
  at
 

 org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processUR
 LRequest
 (AxisServlet.java:776)
  at
 
 org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
  at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
  at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
  at
 
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(
 StubSecurityHelper.java:225)
  at
  weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
 StubSecurityHelper.java:127)
  at

Re: Running Savan (WS-Eventing) Samples

2007-11-27 Thread Martin Gainty

Please post relevant code and WSDL

M-
  - Original Message - 
  From: Enrique Rodríguez Lasterra 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, November 27, 2007 1:08 PM
  Subject: Running Savan (WS-Eventing) Samples

  I can run the savan example with few little changes. But I have some 
errors/doubts

  1.- I can subscribe Listeners to Publisher, but when i ask for the listener 
status i always get null.

  2.-In the WSDL i don't see any namespace/import of ws-eventing, why?

  3.- Publisher porttype should have the EventSource=true attribute, isn't it?

  There is no much information about savan and ws-eventing, so any help is 
appreciated. 

  Regards, Enrique.

  -- 
  ___
  Enrique Rodriguez Lasterra
  lasterra AT javahispano DOT org
  http://www.javahispano.org
  Asociación sin ánimo de lucro sobre java
  Spanish non profit association about java

Re: Axis2 Problem accessing the WSDL.

2007-11-27 Thread Martin Gainty

check all referenced xsd from invoked wsdl
one or more xsd which which will contain mustUnderstand attribute which
should be set to
0 if currently set to 1
or
optional if currently set to required

M--
- Original Message -
From: tinkugadu [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, November 27, 2007 4:15 PM
Subject: Re: Axis2 Problem accessing the WSDL.




 Hi,

 I tried using Axis2 1.3 jars, when i tried getting the WSDL , then i get
the
 following exception on the browser. I still see the old
classCastException,
 still in the logs.

 Exceptionorg.apache.axis2.AxisFault: The endpoint reference (EPR) for the
 Operation not found is /csows/services/EnrollmentMgtService?WSDL and the
WSA
 Action = null at

org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java
:86)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:308) at
 org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at
 org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at

org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java
:125)
 at

org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.jav
a:119)
 at

org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLR
equest(AxisServlet.java:799)
 at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at

weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSe
curityHelper.java:225)
 at

weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelpe
r.java:127)
 at

weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
 at

weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
 at

weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:3153)
 at

weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:321)
 at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at

weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletC
ontext.java:1973)
 at

weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.
java:1880)
 at

weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:131
0)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at
 weblogic.work.ExecuteThread.run(ExecuteThread.java:179)/Exception




 keith chapman wrote:
 
  Yes I believe this is fixed in 1.3. Please try the 1.3 release.
 
  Thanks,
  Keith.
 
  On Nov 27, 2007 11:18 AM, Deepal Jayasinghe [EMAIL PROTECTED]
wrote:
 
  Hi tinkugadu ,
  May be a bug in Axis2 1.2 release , if you can please try with Axis2
1.3
 
  Thanks
  Deepal
   WHen i try to access the WSDL i get the
StringIndexOUtOfBoundsException
   followed by the ClassCastException. WHen i try to access the
   csows/axis2-web/index.jsp from the Weblogic console then i just get
the
   classcast exception
  
   my Environment:
  
   Webserver - Weblogic9
  
   axis version-  axis2 1.2
  
   I am not using axis2.xml
   i have listed the two exceptions below.
  
  
   Nov 26, 2007 1:08:34 PM EST Error HTTP lnx552.dteco.com
   ndsAdmin [ACTIVE] ExecuteThread: '8' for queue: '
  weblogic.kernel.Default
   (self-tuning)' WLS Kernel   1196100514023 BEA-101020
   [EMAIL PROTECTED] - name: '
  csows.war',
   context-path: '/csows'] Servlet failed with Exception
   java.lang.StringIndexOutOfBoundsException: String index out of range:
  -11
   at java.lang.String.substring(String.java:1768)
   at java.lang.String.substring(String.java:1735)
   at
   org.apache.axis2.engine.HTTPLocationBasedDispatcher.parseRequestURL(
  HTTPLocationBasedDispatcher.java:106)
   at
   org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(
  HTTPLocationBasedDispatcher.java:52)
   at
   org.apache.axis2.engine.AbstractDispatcher.invoke(
  AbstractDispatcher.java:100)
   at
   org.apache.axis2.transport.http.util.RESTUtil.dispatchAndVerify(
  RESTUtil.java:138)
   at
   org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(
  RESTUtil.java:95)
   at
  
 
org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLReq
uest
  (AxisServlet.java:776)
   at
  
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
   at
  
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(
  StubSecurityHelper.java:225)
   at
   weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
  StubSecurityHelper.java:127)
   at
  
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java

Monitoring Web Services

2007-11-27 Thread Raghu Upadhyayula

Hi,

 

I've developed webservices using Axis2 1.3 version.

 

The way my webservices work is the user first need to login using
username  password.  This login method returns a sessionId.  Then the
user can call the subsequent webservices APIs by passing the sessionId
in the SOAP Header, and after everything is done, the user needs to
logout (using the logout webservices API).

 

Question: 

Is there any tool that can monitor webservice calls? OR I should write
my own module to do this?

 

In case of my webservices I need to know the following things.

 

For a given start and end date

- What customers are using the WS API (creating sessions)? What
accounts? What users? What pod?

- How frequently are they using it? Number of sessions over period?

- When are they using? Session start and end times 

- What are they doing within the WS API session? 

- What calls are they making?

- How many times to they call each method within a session?

- What are the input parameters to each call?

- Were any exceptions returned? If so what ones?

 

Thanks

Raghu

Re: Running Savan (WS-Eventing) Samples

2007-11-27 Thread Enrique Rodríguez Lasterra

Helo Martin, the code is the example of savan from its svn.

I attached the PublisherService WSDL. As far as i know it should have some
ws-eventing information (import eventing schema, add EventSource=true attr
on Port Type operations,etc)

Regards.



2007/11/27, Martin Gainty [EMAIL PROTECTED]:

  Please post relevant code and WSDL

 M-

 - Original Message -
  *From:* Enrique Rodríguez Lasterra [EMAIL PROTECTED]
 *To:* axis-user@ws.apache.org
 *Sent:* Tuesday, November 27, 2007 1:08 PM
 *Subject:* Running Savan (WS-Eventing) Samples

 I can run the savan example with few little changes. But I have some
 errors/doubts

 1.- I can subscribe Listeners to Publisher, but when i ask for the
 listener status i always get null.

 2.-In the WSDL i don't see any namespace/import of ws-eventing, why?

 3.- Publisher porttype should have the EventSource=true attribute, isn't
 it?

 There is no much information about savan and ws-eventing, so any help is
 appreciated.

 Regards, Enrique.

 --
 ___
 Enrique Rodriguez Lasterra
 lasterra AT javahispano DOT org
 http://www.javahispano.org
 Asociación sin ánimo de lucro sobre java
 Spanish non profit association about java




-- 
___
Enrique Rodriguez Lasterra
lasterra AT javahispano DOT org
http://www.javahispano.org
Asociación sin ánimo de lucro sobre java
Spanish non profit association about java
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns0=http://eventing.sample; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:ns1=http://org.apache.axis2/xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; targetNamespace=http://eventing.sample;
wsdl:documentationPublisherService/wsdl:documentation
wsdl:types
xs:schema xmlns:ns=http://eventing.sample; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://eventing.sample;
xs:complexType name=Exception
xs:sequence
xs:element minOccurs=0 name=Exception nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
xs:element name=Exception
xs:complexType
xs:sequence
xs:element minOccurs=0 name=Exception nillable=true type=ns:Exception/
/xs:sequence
/xs:complexType
/xs:element
xs:element name=dummyMethod
xs:complexType
xs:sequence
xs:element minOccurs=0 name=dummyMethod nillable=true type=xs:anyType/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
/wsdl:types
wsdl:message name=dummyMethodRequest
wsdl:part name=parameters element=ns0:dummyMethod/
/wsdl:message
wsdl:message name=Exception
wsdl:part name=parameters element=ns0:Exception/
/wsdl:message
wsdl:portType name=PublisherServicePortType
wsdl:operation name=dummyMethod
wsdl:input message=ns0:dummyMethodRequest wsaw:Action=urn:dummyMethod/
wsdl:fault message=ns0:Exception name=Exception wsaw:Action=urn:dummyMethodException/
/wsdl:operation
/wsdl:portType
wsdl:binding name=PublisherServiceSOAP11Binding type=ns0:PublisherServicePortType
soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/
wsdl:operation name=dummyMethod
soap:operation soapAction=urn:dummyMethod style=document/
wsdl:input
soap:body use=literal/
/wsdl:input
wsdl:fault name=Exception
soap:fault use=literal name=Exception/
/wsdl:fault
/wsdl:operation
/wsdl:binding
wsdl:binding name=PublisherServiceSOAP12Binding type=ns0:PublisherServicePortType
soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/
wsdl:operation name=dummyMethod
soap12:operation soapAction=urn:dummyMethod style=document/
wsdl:input
soap12:body use=literal/
/wsdl:input
wsdl:fault name=Exception
soap12:fault use=literal name=Exception/
/wsdl:fault
/wsdl:operation
/wsdl:binding
wsdl:binding name=PublisherServiceHttpBinding type=ns0:PublisherServicePortType
http:binding verb=POST/
wsdl:operation name=dummyMethod
http:operation location=PublisherService/dummyMethod/
wsdl:input
mime:content type=text/xml part=dummyMethod/
/wsdl:input
/wsdl:operation
/wsdl:binding
wsdl:service name=PublisherService

Re: Running Savan (WS-Eventing) Samples

2007-11-27 Thread Martin Gainty

Hi Enrique-

I ran the wsdl2java on the attached WSDL and didnt see any of the savan types
the WSDL which defines types,message.portType,binding,port,service needs to 
include relevant element and operational references to savan schema (which I 
could not locate)
good example is located at
http://www.w3.org/TR/wsdl

Dims would you know the location of the savan schema?

?
M-
  - Original Message - 
  From: Enrique Rodríguez Lasterra 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, November 27, 2007 7:32 PM
  Subject: Re: Running Savan (WS-Eventing) Samples


  Helo Martin, the code is the example of savan from its svn.

  I attached the PublisherService WSDL. As far as i know it should have some 
ws-eventing information (import eventing schema, add EventSource=true attr on 
Port Type operations,etc) 

  Regards.




  2007/11/27, Martin Gainty [EMAIL PROTECTED] : 
Please post relevant code and WSDL

M-
  - Original Message - 
  From: Enrique Rodríguez Lasterra 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, November 27, 2007 1:08 PM
  Subject: Running Savan (WS-Eventing) Samples


  I can run the savan example with few little changes. But I have some 
errors/doubts

  1.- I can subscribe Listeners to Publisher, but when i ask for the 
listener status i always get null.

  2.-In the WSDL i don't see any namespace/import of ws-eventing, why?

  3.- Publisher porttype should have the EventSource=true attribute, 
isn't it?

  There is no much information about savan and ws-eventing, so any help is 
appreciated. 

  Regards, Enrique.

  -- 
  ___
  Enrique Rodriguez Lasterra
  lasterra AT javahispano DOT org
  http://www.javahispano.org
  Asociación sin ánimo de lucro sobre java
  Spanish non profit association about java 



  -- 
  ___
  Enrique Rodriguez Lasterra
  lasterra AT javahispano DOT org
  http://www.javahispano.org
  Asociación sin ánimo de lucro sobre java
  Spanish non profit association about java 


--


  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Wang Han

Hi guys,
Any clue please?

On Nov 27, 2007 10:44 PM, Wang Han [EMAIL PROTECTED] wrote:

 Hi Vaibhav,

 load applet failed occurs when I use firefox.
 But I can't access the SOAPMonitor either by IE -- it brings me to a
 searching page immediately
 with http://localhost:8080; in the searching bar once I try to open
 the link in IE.

 I do read the appendix and deployed the service successfully before
 setting the virtual host.

 After setting the virtual host, I try to re-deploy the SOAPMonitor
 according to the appendix as below:
 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
 2. executing java org.apache.axis.client.AdminClient
 -lhttp://localhost:8080/AdminService deploy-monitor.wsdd
 successfully.
 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
 then failed.

 Please correct me if I made any mistake here,Thanks.

 On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
  I guess it should work fine with IE. If not, refer to Appendix:
 Enabling the
  SOAP Monitor' under User Guide in your docs folder.
 
 
  Wang Han wrote:
  
   Hi guys,
  
   Service echo is deployed at:
   http://localhost:8080/axis/services/echo, SOAPMonitor is at
   http://localhost:8080/axis/SOAPMonitor.
   I can use SOAPMonitor to monitor all soap messages between echo
   service and its client.
  
   For some special requirement, I need re-deploy the echo service to
   http://localhost:8080/echo.
   I implement it successfully by modifying tomcat/conf/server.xml and
   webapps/axis/web.xml.
  
   But the SOAPMonitor is not there any more. I  try to access it by
   http://localhost:8080/SOAPMonitor,
   It always gives me load applet failed error message.
  
   Could someone tell me how can I find back the SOAPMonitor? thanks a
 lot!
  
   Tomcat6.0 + axis1.4.
   tomcat/conf/server.xml:
 Host name=localhost  appBase=webapps/axis
   unpackWARs=true autoDeploy=true
   xmlValidation=false xmlNamespaceAware=false
Context path=/ docBase=./
  
   webapps/axis/WEB-INF/web.xml:
 servlet-mapping
  servlet-nameAxisServlet/servlet-name
  !-- use it when need SOAPMon
 url-pattern/services/*/url-pattern
   --
  url-pattern/*/url-pattern
 /servlet-mapping
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
  
 
  --
  View this message in context:
 http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
  Sent from the Axis - User mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 1.3 Rest Support

2007-11-27 Thread keith chapman

Hi John,

Can you use TCP Monitor and track your request please. text/xml is the
content type of SOAP 1.1, but some send rest request also as SOAP 1.1 hence
we do a bit of a check in Axis2. SOAP 1.1 mandates the soapaction http
header. So if the request contentType is text/xml and the request has a
soapaction httpheader axis2 will treat it as a SAOP request and hence the
SOAPBuilder will get called. On the otherhand if the request contentType is
text/xml and there is no soapaction http header then Axis2 wil treat this as
a pox request and the ApplicationXMLBuilder will get called.

I presume this is the problem your facing, hence please check your request
using TCP Monitor.

Thanks,
Keith.

On Nov 27, 2007 11:11 PM, John Pfeifer [EMAIL PROTECTED]
wrote:

 Keith,

 Thanks for the info.  I deployed the axis2.war file and the Version
 service works properly.  The axis2.xml is identical to the one that I use
 in my war file.  I am still having the same issue with my web service
 however.  Perhaps the snippet below may explain what is happening.  It looks
 like Axis wants to use the SOAPBuilder for the POX request.  I have
 confirmed that I am sending XML without SOAP Envelope, so I am not sure why
 it's attempting to use the SOAPBuilder.  Any ideas?

 11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: '
 weblogic.kernel.Default (self-tuning)'|DEBUG|builder.BuilderUtil|Input
 contentType (text/xml)|
 11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: '
 weblogic.kernel.Default(self-tuning)'|DEBUG|builder.BuilderUtil|CharSetEncoding
  defaulted (UTF-8)|
 11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: '
 weblogic.kernel.Default(self-tuning)'|DEBUG|transport.TransportUtils|createSOAPEnvelope
  using
 Builder (class org.apache.axis2.builder.SOAPBuilder) selected from type
 (application/xml)|
 11/27/07 12:24:15:389|[ACTIVE] ExecuteThread: '2' for queue: '
 weblogic.kernel.Default (self-tuning)'|DEBUG|builder.BuilderUtil|char set
 encoding set from default =UTF-8|
 11/27/07 12:24:15:390|[ACTIVE] ExecuteThread: '2' for queue: '
 weblogic.kernel.Default(self-tuning)'|DEBUG|http.AxisServlet|org.apache.axis2.AxisFault:
  First
 Element must contain the local name, Envelope , but found
 PayCaptureRequestServiceRequest|


 Thanks,

 John



 -Original Message-
 From: keith chapman [mailto:[EMAIL PROTECTED]
 Sent: Tue 11/27/2007 11:07 AM
 To: axis-user@ws.apache.org
 Subject: Re: Axis2 1.3 Rest Support

 Hi John,

 Yes both SOAP and REST request are handled by the same endpoint and there
 is
 no /soap/ or /rest/ in the request URL now.

 Yes REST services don't require a SOAP envelop and you can send the
 request
 via GET , POST, PUT or DELETE.

 The easiest way to test REST is to go to
 http://localhost:8080/axis2/services/version/getVersion on the browser.
 This
 will send a GET to the version service which would respond using a POX
 response.

 If you want true REST behaviour where you can send parameters in the path
 segment or as customized query parameters you shpu;d have a look at
 WSDL 2.0HTTPBinding. If you deploy a service using WSDL
 2.0 Axis2 can handle request as described in your WSDL.

 for eg. Axis2 default URL to get the version of the version service would
 be
 http://localhost:8080/axis2/services/version/getVersion but if you
 deployed
 this service via a WSDL 2.0 you can alter the request URL to suite your
 needs.

 If you need more help please let me know. I'll be glad to assist you.

 Thanks,
 Keith.

 On Nov 27, 2007 9:07 PM, John Pfeifer [EMAIL PROTECTED]
 wrote:

   I recently upgraded from Axis2 1.1 to 1.3.  In version 1.1 I configured
  the RestServlet to handle all requests to /rest/*.
 
  The web services themselves aren't truely restful, but I need to be able
  to support both SOAP and POX.  Basically what I want is for my web
 service
  to support both SOAP and POX without having to modify my code.  This was
  working perfectly before as Axis2 stripped off the SOAP Envelop for SOAP
  requests and left Rest requests alone.  This is the behavior that I
 want,
  but I am having difficulty figuring out how to configure the server
 side.
 
  Since upgrading to 1.3, I discovered that the RestServlet no longer
  exists.  In addition, I am having difficulty figuring out how to
 configure
  the server side.  Are SOAP and Rest request handled by a single endpoint
  now?  If so, the axis2 documentation says REST Web Services do not have
  Headers and the payload is sent directly., does this mean that Rest
  services don't have a SOAP Envelope, or that HTTP SOAP Headers are
 absent?
 
  I would appreciate it if someone could point me in the right direction,
 or
  refer me to some documentation that has a bit more detail than the
 RESTful
  Web Services Support page in the Axis2 docs.
 
  Thanks,
 
  John
 



 --
 Keith Chapman
 WSO2 Inc.
 Oxygen for Web Services Developers.
 http://wso2.org/

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Martin Gainty

Han-

In axis2 soapmonitor is an independent module which is engaged to the selected 
service
as Version is installed as as default service if you want to engage soapmonitor 
module for the axisService 'Version' place this in browser
http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitoraxisService=Versionsubmit=+Engage+

M--

  - Original Message - 
  From: Wang Han 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, November 27, 2007 8:47 PM
  Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.


  Hi guys,
  Any clue please?


  On Nov 27, 2007 10:44 PM, Wang Han [EMAIL PROTECTED] wrote:

Hi Vaibhav,

load applet failed occurs when I use firefox.
But I can't access the SOAPMonitor either by IE -- it brings me to a
searching page immediately
with  http://localhost:8080; in the searching bar once I try to open
the link in IE.

I do read the appendix and deployed the service successfully before
setting the virtual host.

After setting the virtual host, I try to re-deploy the SOAPMonitor 
according to the appendix as below:
1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
2. executing java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/AdminService deploy-monitor.wsdd 
successfully.
3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
then failed.

Please correct me if I made any mistake here,Thanks. 


On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 I guess it should work fine with IE. If not, refer to Appendix: Enabling 
the 
 SOAP Monitor' under User Guide in your docs folder.


 Wang Han wrote:
 
  Hi guys,
 
  Service echo is deployed at:
  http://localhost:8080/axis/services/echo, SOAPMonitor is at
  http://localhost:8080/axis/SOAPMonitor.
  I can use SOAPMonitor to monitor all soap messages between echo 
  service and its client.
 
  For some special requirement, I need re-deploy the echo service to
  http://localhost:8080/echo .
  I implement it successfully by modifying tomcat/conf/server.xml and
  webapps/axis/web.xml.
 
  But the SOAPMonitor is not there any more. I  try to access it by
  http://localhost:8080/SOAPMonitor,
  It always gives me load applet failed error message.
 
  Could someone tell me how can I find back the SOAPMonitor? thanks a 
lot! 
 
  Tomcat6.0 + axis1.4.
  tomcat/conf/server.xml:
Host name=localhost  appBase=webapps/axis
  unpackWARs=true autoDeploy=true 
  xmlValidation=false xmlNamespaceAware=false
   Context path=/ docBase=./
 
  webapps/axis/WEB-INF/web.xml: 
servlet-mapping
 servlet-nameAxisServlet/servlet-name
 !-- use it when need SOAPMon url-pattern/services/*/url-pattern
  -- 
 url-pattern/*/url-pattern
/servlet-mapping
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

 --
 View this message in context: 
http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
 Sent from the Axis - User mailing list archive at Nabble.com .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED] 
 For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread robert lazarski

The axis 1.x version of the soap monitor is pretty silent on errors -
I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
nothing else is listening on port 5001 or try moving to a different
port to see if that helps. Double check your servlet setup in the
web.xml file. Firefox has an applet console which is sometimes helpful
in showing what the errors are.

HTH,
Robert

On Nov 27, 2007 9:07 PM, Martin Gainty [EMAIL PROTECTED] wrote:


 Han-

 In axis2 soapmonitor is an independent module which is engaged to the
 selected service
 as Version is installed as as default service if you want to engage
 soapmonitor module for the axisService 'Version' place this in browser
 http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitoraxisService=Versionsubmit=+Engage+

 M--


 - Original Message -
 From: Wang Han
 To: axis-user@ws.apache.org
 Sent: Tuesday, November 27, 2007 8:47 PM
 Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.

 Hi guys,
 Any clue please?


 On Nov 27, 2007 10:44 PM, Wang Han [EMAIL PROTECTED] wrote:

  Hi Vaibhav,
 
  load applet failed occurs when I use firefox.
  But I can't access the SOAPMonitor either by IE -- it brings me to a
  searching page immediately
  with  http://localhost:8080; in the searching bar once I try to open
  the link in IE.
 
  I do read the appendix and deployed the service successfully before
  setting the virtual host.
 
  After setting the virtual host, I try to re-deploy the SOAPMonitor
  according to the appendix as below:
  1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
  2. executing java org.apache.axis.client.AdminClient
  -lhttp://localhost:8080/AdminService deploy-monitor.wsdd 
  successfully.
  3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
  then failed.
 
  Please correct me if I made any mistake here,Thanks.
 
 
 
 
  On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  
   I guess it should work fine with IE. If not, refer to Appendix:
 Enabling the
   SOAP Monitor' under User Guide in your docs folder.
  
  
   Wang Han wrote:
   
Hi guys,
   
Service echo is deployed at:
http://localhost:8080/axis/services/echo, SOAPMonitor is at
http://localhost:8080/axis/SOAPMonitor.
I can use SOAPMonitor to monitor all soap messages between echo
service and its client.
   
For some special requirement, I need re-deploy the echo service to
http://localhost:8080/echo .
I implement it successfully by modifying tomcat/conf/server.xml and
webapps/axis/web.xml.
   
But the SOAPMonitor is not there any more. I  try to access it by
http://localhost:8080/SOAPMonitor,
It always gives me load applet failed error message.
   
Could someone tell me how can I find back the SOAPMonitor? thanks a
 lot!
   
Tomcat6.0 + axis1.4.
tomcat/conf/server.xml:
  Host name=localhost  appBase=webapps/axis
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
 Context path=/ docBase=./
   
webapps/axis/WEB-INF/web.xml:
  servlet-mapping
   servlet-nameAxisServlet/servlet-name
   !-- use it when need SOAPMon
 url-pattern/services/*/url-pattern
--
   url-pattern/*/url-pattern
  /servlet-mapping
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
   
  
   --
   View this message in context:
 http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
   Sent from the Axis - User mailing list archive at Nabble.com .
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Monitoring Web Services

2007-11-27 Thread Charitha Kankanamge


Raghu Upadhyayula wrote:


Hi,

I’ve developed webservices using Axis2 1.3 version.

The way my webservices work is the user first need to login using 
username  password. This login method returns a sessionId. Then the 
user can call the subsequent webservices APIs by passing the sessionId 
in the SOAP Header, and after everything is done, the user needs to 
logout (using the logout webservices API).


*Question: *

Is there any tool that can monitor webservice calls? OR I should write 
my own module to do this?


1. WSO2 web services application server (WSAS) provides SOAP Tracer 
which can be used to monitor message transmission. Refer 
http://wso2.org/library/2742


2. Axis2 SoapMonitor module will also be a good candidate. Refer 
http://ws.apache.org/axis2/1_3/soapmonitor-module.html



In case of my webservices I need to know the following things.

For a given start and end date

- What customers are using the WS API (creating sessions)? What 
accounts? What users? What pod?


- How frequently are they using it? Number of sessions over period?

- When are they using? Session start and end times

- What are they doing within the WS API session?

- What calls are they making?

- How many times to they call each method within a session?

- What are the input parameters to each call?

- Were any exceptions returned? If so what ones?

Thanks

Raghu




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] 1.3 bug - services.xml mentions ECMServiceMessageReceiverInOnly which is missing from wsdl2java generated code

2007-11-27 Thread Pantvaidya, Vishwajit

I used Axis2 1.3 release wsdl2java to generate code and services.xml and find 
that the code is missing the ECMServiceMessageReceiverInOnly class. So when I 
build the aar and deploy it I get java.lang.ClassNotFoundException: 
...ECMServiceMessageReceiverInOnly.

services.xml has:
messageReceiver mep=http://www.w3.org/ns/wsdl/in-only 
class=...ECMServiceMessageReceiverInOnly/
messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; 
class=...ECMServiceMessageReceiverInOut/
But the wsdl2java generated code has the ECMServiceMessageReceiverRobustInOnly 
class instead of ECMServiceMessageReceiverInOnly.

Then I tried wsdl2java with the Nov 9 nightly build and it deployed fine. I saw 
that the generated services.xml has:
messageReceiver mep=http://www.w3.org/ns/wsdl/in-out; 
class=...ECMServiceMessageReceiverInOut/
messageReceiver mep=http://www.w3.org/ns/wsdl/robust-in-only; 
class=...ECMServiceMessageReceiverRobustInOnly/
and both the messagereceiver classes are generated by wsdl2java.

Is this a known problem in axis2-1.3 that was fixed later? If not - I could add 
it to the note I am planning to submit on the migration to axis2.


- Vish.

Re: Silly question about how to shutdown axis

2007-11-27 Thread Kjell Nilsson


Thanx for your answer

I tried it but it did not work.

Probably because I run the server without an administrative site, just  
the

SimpleAxisServer standalone, outside of any container and such.

So if that is the only way to stop the server I think Ill have to  
implement

it in an operation myself.

MVH
--kjell



On 27 nov 2007, at 21.25, Martin Gainty wrote:

unless its 2am and you need to stop a runaway task you should  
quiesce your

axis2 webapp to allow the connections to be closed *gracefully*
e.g.
assuming your axis2 webapp is called axis2 which is running on  
localhost

port 8080 put this in your browser
http://localhost:8080/manager/html/stop?path=/axis2

Tack
M--
- Original Message -
From: Kjell Nilsson [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, November 27, 2007 12:33 PM
Subject: Silly question about how to shutdown axis



This is probably a silly newbee question but how do I shutdown a
standalone axis server.

I have implemented the ServiceLifeCycle interface so I can do late
late cleanup database
and jms stuff, and this works nice.

Since I have developed on a Mac the Unix command 'kill' takes down  
the

axisserver nice and
clean, calling my shutDown() method. But my problem is that I will
deploy this axis2server on
OpenVMS and there is not a 'kill' command there, only a 'delete/ 
entry'

command that does
like 'kill -9', and thats not nice since the server dies abruptly.

So what strategy shall I use? Implement an operation that will
shutdown axis2 from inside?
If so what method can I call to stop the server and how do I get hold
of the objects that
has the stop method? Or is there a static method somewhere to call?

Any hint will be fine ;-)

Kind regards
--kjell



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Wang Han

Hi Robert  Martin,

Thanks for your reply.

Robert:
I also wonder this... I changed the web.xml and
http://localhost:8080/axis/service/echo is changed to
http://localhost:8080/echo.
But originally the SOAPMonitor is deployed at
http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so where
should it be after I re-deployed the service? any suggestion is welcome :)

Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
have a service which is deployed at http://localhost:8080/echo, I can
monitor it by
http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitoraxisService=echosubmit=+Engagehttp://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitoraxisService=Versionsubmit=+Engage+
regardless where the service is deployed?
I have no idea about axis2 since I always work with axis1.4, is axis2 better
than axis1.4 ?

Thanks!
Han

On Nov 28, 2007 10:19 AM, robert lazarski [EMAIL PROTECTED] wrote:

 The axis 1.x version of the soap monitor is pretty silent on errors -
 I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
 nothing else is listening on port 5001 or try moving to a different
 port to see if that helps. Double check your servlet setup in the
 web.xml file. Firefox has an applet console which is sometimes helpful
 in showing what the errors are.

 HTH,
 Robert

 On Nov 27, 2007 9:07 PM, Martin Gainty [EMAIL PROTECTED] wrote:
 
 
  Han-
 
  In axis2 soapmonitor is an independent module which is engaged to the
  selected service
  as Version is installed as as default service if you want to engage
  soapmonitor module for the axisService 'Version' place this in browser
 
 http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitoraxisService=Versionsubmit=+Engage+
 
  M--
 
 
  - Original Message -
  From: Wang Han
  To: axis-user@ws.apache.org
  Sent: Tuesday, November 27, 2007 8:47 PM
  Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.
 
  Hi guys,
  Any clue please?
 
 
  On Nov 27, 2007 10:44 PM, Wang Han [EMAIL PROTECTED] wrote:
 
   Hi Vaibhav,
  
   load applet failed occurs when I use firefox.
   But I can't access the SOAPMonitor either by IE -- it brings me to a
   searching page immediately
   with  http://localhost:8080; in the searching bar once I try to open
   the link in IE.
  
   I do read the appendix and deployed the service successfully before
   setting the virtual host.
  
   After setting the virtual host, I try to re-deploy the SOAPMonitor
   according to the appendix as below:
   1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
   2. executing java org.apache.axis.client.AdminClient
   -lhttp://localhost:8080/AdminService deploy-monitor.wsdd 
   successfully.
   3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
   then failed.
  
   Please correct me if I made any mistake here,Thanks.
  
  
  
  
   On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] [EMAIL PROTECTED]
 wrote:
   
I guess it should work fine with IE. If not, refer to Appendix:
  Enabling the
SOAP Monitor' under User Guide in your docs folder.
   
   
Wang Han wrote:

 Hi guys,

 Service echo is deployed at:
 http://localhost:8080/axis/services/echo, SOAPMonitor is at
 http://localhost:8080/axis/SOAPMonitor.
 I can use SOAPMonitor to monitor all soap messages between echo
 service and its client.

 For some special requirement, I need re-deploy the echo service to
 http://localhost:8080/echo .
 I implement it successfully by modifying tomcat/conf/server.xml
 and
 webapps/axis/web.xml.

 But the SOAPMonitor is not there any more. I  try to access it by
 http://localhost:8080/SOAPMonitor,
 It always gives me load applet failed error message.

 Could someone tell me how can I find back the SOAPMonitor? thanks
 a
  lot!

 Tomcat6.0 + axis1.4.
 tomcat/conf/server.xml:
   Host name=localhost  appBase=webapps/axis
 unpackWARs=true autoDeploy=true
 xmlValidation=false xmlNamespaceAware=false
  Context path=/ docBase=./

 webapps/axis/WEB-INF/web.xml:
   servlet-mapping
servlet-nameAxisServlet/servlet-name
!-- use it when need SOAPMon
  url-pattern/services/*/url-pattern
 --
url-pattern/*/url-pattern
   /servlet-mapping


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



   
--
View this message in context:
 
 http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
Sent from the Axis - User mailing list archive at Nabble.com .
   
   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For

48 matches

Mail list logo