Re: error creating message from generated client

[Amila Suriarachchi]

it seems this error happens when processing the request. reason seems to be
that reqeust send to and invalide soap end point and it sends back an html
page instead of valide soap message.

On 10/22/07, Kimberly Nicholls <[EMAIL PROTECTED]> wrote:
>
>  I am having trouble creating a SOAP message from a generated client when
> the message includes attachments -- the client throws "
> org.apache.axiom.soap.SOAPProcessingException: First Element must contain
> the local name, Envelope , but found html."
>

this means you have got an html page. have you set the end point correctly
in the stub?

I am using axis2 1.3, and I can make requests to other methods (without
> attachments) in the same service with no problems.
>
> Here's what I did:
>
> - set enableMTOM to true in axis2.xml
> - created method in my POJO service: public long createAttachment(long
> messageID, DataHandler attData)
> - generated client stub via wsdl2java
> - added these lines to client stub:
> _serviceClient.getOptions().setProperty(
> Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE
> );
>  _serviceClient.getOptions().setTimeOutInMilliSeconds(1);
> - created client that runs the method like this:
> DataHandler attData = new DataHandler(new
> FileDataSource(filename));
> long attachmentID = stub.createAttachment(messageID, attData);
>
> When I run the client, I get
>
> [INFO] OMException in getSOAPBuilder
> org.apache.axiom.soap.SOAPProcessingException: First Element must contain
> the local name, Envelope , but found html
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(
> StAXSOAPModelBuilder.java:219)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(
> StAXSOAPModelBuilder.java:177)
> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(
> StAXOMBuilder.java:163)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(
> StAXSOAPModelBuilder.java:161)
> at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(
> StAXSOAPModelBuilder.java:110)
> at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(
> BuilderUtil.java:609)
> at org.apache.axis2.transport.TransportUtils.createDocumentElement
> (TransportUtils.java:178)
> at org.apache.axis2.transport.TransportUtils.createSOAPMessage(
> TransportUtils.java:111)
> at org.apache.axis2.transport.TransportUtils.createSOAPMessage(
> TransportUtils.java:87)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
> OutInAxisOperation.java:326)
>

here the exception Occurs in handling the response not when sending .

at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:389)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:211)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:163)
> ...
> Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element
> must contain the local name, Envelope , but found html
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(
> StAXSOAPModelBuilder.java:219)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(
> StAXSOAPModelBuilder.java:177)
> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(
> StAXOMBuilder.java:163)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(
> StAXSOAPModelBuilder.java:161)
> at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(
> StAXSOAPModelBuilder.java:110)
> at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(
> BuilderUtil.java:609)
> at org.apache.axis2.transport.TransportUtils.createDocumentElement
> (TransportUtils.java:178)
> at org.apache.axis2.transport.TransportUtils.createSOAPMessage(
> TransportUtils.java:111)
> at org.apache.axis2.transport.TransportUtils.createSOAPMessage(
> TransportUtils.java:87)
> ... 6 more
>
>
> Running other methods in the same client with the same service work fine,
> if they don't have attachments.  The file I'm trying to send is a 2.5kjpg.  
> What am I doing wrong?
>
> Kimberly
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: org.apache.axis2.databinding.ADBException: Property cannot be null!

[Amila Suriarachchi]

On 10/23/07, Huitang Li <[EMAIL PROTECTED]> wrote:
>
> Excellent! Thanks very much. Somehow -Eosv does not solve the problem.


what is the  Axis2 version you use? this is available in Axis2 1.3.

So I put the nillable="true" in the element there, and it works.
>
>
>
>
>
> Amila Suriarachchi wrote:
> > this means your object structure do not have loaded the required fault
> > elements.
> >
> > see you schema there should be an element named fault without
> > minOccurs=0 or nillable=ture.
> > So ADB gives an exception because of this.
> >
> > if you want to remove this use -Eosv when genrating the code.
> >
> > Amia.
> >
> >
> > On 10/23/07, *Huitang Li* < [EMAIL PROTECTED]
> > > wrote:
> >
> > Hi,
> >
> > I created a web service code based on a wsdl, and it is run in resin
> > 3.1.3, and I have the soapmonitor activated.  When a web service
> > client
> > sent a soap message to it, it threw the following exception:
> >
> > java.lang.RuntimeException: Can not serialize OM Element Envelope
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.toString(
> OMElementImpl.java:916)
> > at
> > org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(
> SOAPMonitorHandler.java:101)
> > at org.apache.axis2.engine.Phase.invoke (Phase.java:292)
> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java
> :212)
> > at
> > org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:442)
> > at
> > org.apache.axis2.transport.http.AxisServlet.handleFault
> > (AxisServlet.java:403)
> > at
> > org.apache.axis2.transport.http.AxisServlet.processAxisFault(
> AxisServlet.java:366)
> > at
> > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java
> :154)
> > at javax.servlet.http.HttpServlet.service (HttpServlet.java:153)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
> > at
> > com.caucho.server.dispatch.ServletFilterChain.doFilter(
> ServletFilterChain.java:103)
> > at
> > com.caucho.server.security.SecurityFilterChain.doFilter
> > (SecurityFilterChain.java:134)
> > at
> > com.caucho.server.webapp.WebAppFilterChain.doFilter(
> WebAppFilterChain.java:178)
> > at
> > com.caucho.server.dispatch.ServletInvocation.service(
> ServletInvocation.java:241)
> > at
> > com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java
> :268)
> > at
> > com.caucho.server.port.TcpConnection.run(TcpConnection.java:586)
> > at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:690)
> > at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:612)
> > at java.lang.Thread.run(Thread.java:595)
> > Caused by: org.apache.axis2.databinding.ADBException: Property
> > cannot be
> > null!
> > at test.Fault.serialize (Fault.java:95)
> > at test.Fault$1.serialize(Fault.java:80)
> > at
> > org.apache.axis2.databinding.ADBDataSource.serialize(
> ADBDataSource.java:82)
> > at
> >
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume
> > (OMSourcedElementImpl.java:599)
> > at
> >
> org.apache.axiom.soap.impl.llom.SOAPFaultDetailImpl.internalSerialize(
> SOAPFaultDetailImpl.java:86)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
> OMElementImpl.java
> > :756)
> > at
> > org.apache.axiom.soap.impl.llom.SOAPFaultImpl.internalSerialize(
> SOAPFaultImpl.java:192)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
> OMElementImpl.java:756)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
> > (OMElementImpl.java:772)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
> OMElementImpl.java:756)
> > at
> > org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
> SOAPEnvelopeImpl.java
> > :210)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
> OMElementImpl.java:756)
> > at
> > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java
> :345)
> > at
> > org.apache.axiom.om.impl.llom.OMElementImpl.toString
> > (OMElementImpl.java:913)
> > ... 18 more
> >
> > This exception will not be shown when all elements in the requesting
> > soap message are filled with non-empty (no-blankspace) values.
> >
> > I notice that the exception is thrown from the following
> > axis2-generated
> > code:
> >
> >
> >public void serialize(final javax.xml.namespace.QNameparentQName,
> > final org.apache.axiom.om.OMFactory factory,
> >
> > org.apache.axis2.databinding.utils.writer.MTOMAwareXMLStreamWriter
> > xmlWriter)
> > throws javax.xml.stream.XMLStreamException,
> 

Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning "The service cannot be found for the endpoint reference"

[Upul Godage]

Actually the Axis2 web service engine is working fine. You can depoly aar in
the services directory and access them. (e.g. /axis2/services/Version?wsdl)

> From the request 
> (http://BLAHBLASH/axis2/services
)
>xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>The service cannot be found for the
> endpoint reference (EPR) /axis2/services
>   

Instead of deploying the axis2.war file directly, unzip the war file and
deploy as an exploded archive Context context =
embedded.createContext("/axis2",
"/path/to/axis2");

Also check whether there is an axis2-web directory in you exploded war
directory, which is only an admin console.

Upul

On 10/24/07, James Maes <[EMAIL PROTECTED]> wrote:
>
> After digging into the Axis code, it looks like the problem is caused by
> the
> following
>
> The RequestDispatch returned from
>
> httpServletRequest.getRequestDispatcher(Constants.AXIS_WEB_CONTENT_ROOT +
> jspName).include(httpServletRequest, httpServletResponse);
> in AbstractAgent.java (renderView method)
>
> is null.
>
> The following are the inputs that were passed into that call.
>
> Constants.AXIS_WEB_CONTENT_ROOT [/axis2-web/]
> jspName [listServices.jsp]
>
>
>
> I assume that this all points to something miss configured on my end on my
> part, but I am out of ideas.  Does this help shed any light on the issue
> for
> anyone?
>
>
>
>
>
> James Maes
> Software Architect
> Materialogic
> PH: 800-333-7144
> PH: 314-997-4342 Ext. 3422
> FX: 314-997-7814
>
>
> -Original Message-
> From: James Maes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 23, 2007 12:46 PM
> To: axis-user@ws.apache.org
> Subject: RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5
> server - axis2/services returning "The service cannot be found for the
> endpoint reference"
>
> When requesting the URL (http://BLAHBLAH/axis2/axis2-web/)
> I get this response
>
> HTTP Status 404 - /axis2/axis2-web/
>
> 
> 
> type Status report
> message /axis2/axis2-web/
> description The requested resource (/axis2/axis2-web/) is not available.
>
> 
> 
> Apache Tomcat/5.5.17
>
> And this on the server console
>
> [java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 :
> g.apache.catalina.core.StandardHostValve : Exception Processing
> ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp]
>  [java] java.lang.NullPointerException
>  [java] at
> org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java
> :363
> )
>  [java] at
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
> :284
> )
>  [java] at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :136
> )
>  [java] at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :105
> )
>  [java] at
> org.apache.catalina.core.StandardEngineValve.invoke(
> StandardEngineValve.java
> :107)
>  [java] at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
> :148)
>  [java] at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>  [java] at
>
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
> onnection(Http11BaseProtocol.java:664)
>  [java] at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
> PoolTcpEndpoint.jav
> a:527)
>  [java] at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
> (LeaderFollowerWo
> rkerThread.java:80)
>  [java] at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.jav
> a:684)
>  [java] at java.lang.Thread.run(Thread.java:595)
>
>
>
>
>
>
>
>
>
>
>
>
> James Maes
> Software Architect
> Materialogic
> PH: 800-333-7144
> PH: 314-997-4342 Ext. 3422
> FX: 314-997-7814
>
> From: Upul Godage [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 23, 2007 12:37 PM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5
> server - axis2/services returning "The service cannot be found for the
> endpoint reference"
>
> Check accessing these links in your server.
>
> http://blahblash/axis2/axis2-web/
> For console home page
>
> http://blahblash/axis2/services/listServices
> For deployed services
>
> Upul
> On 10/23/07, James Maes <[EMAIL PROTECTED]> wrote:
> Maybe someone can give a little insight into the issue(s) that I am
> having.
>
> We are trying to embed Axis2 (1.3) into a internal application via Tomcat
> (5.5)
> Tomcat seems to be working fine (it's used for other war deployments) and
> the axis2.war deploys fine (see below)
>
> Deployment code
> Context context = embedded.createContext("/axis2", "axis2.war");
> context.setReloadable(false);
> host.addChild (context);
>
> Wa

Axis2 1.3 wsdl2java generates code with missing methods

[Pantvaidya, Vishwajit]

I am using wsdl2java to generate java code from a wsdl using wsdl2java options 
"-o -ss -sd -ssi -f -uw -uri -ns2p". The result includes a MessageReceiverInOut 
class that is missing a method resulting in a compiletime error "method 
wrapIsUploadAllowed(OperationStatusType) is undefined for the type 
...MessageReceiverInOut".

I observed that this seems to happen when wsdl parts in different messages 
refer to the same complex type. In such cases, the wrap methods in the 
MessageReceiver class for the first operation is created while that for the 
other one is not created. E.g. in this case the method 
wrapUpload(OperationStatusType) gets created while 
wrapIsUploadAllowed(OperationStatusType) is missing.

Wsdl snippet is included below.

Is this a bug?






















>














... 












...








...
http://schemas.xmlsoap.org/soap/http"; style="document"/>


















...

[Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Raghu Upadhyayula]

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  http://10.5.2.182:80/webservices/services/MyWSService
  />



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

http://ws.qa.company.com/webservices/services/MyWSService
  />



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it, I've change the modifyUserWSDLPortAddress
property back to true.

 

Thanks in Advance.

Raghu

 

[Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).

[Raghu Upadhyayula]

Hi,

 

I have a problem with the soap:address location generated
when I browse the WSDL in the browser.



I'm using Axis2 1.3.



I'm looking at the WSDL in the browser using
http://ws.qa.company.com/webservices/services/MyWSService?wsdl



I get the WSDL and the soap:address location in the WSDL
looks like  http://10.5.2.182:80/webservices/services/MyWSService
  />



But then problem is with the IP Address coming in the
soap:address location 10.5.2.182 is not a public IP that is accessible
from Internet.



What changes should I do to change the soap:address location
to look like

http://ws.qa.company.com/webservices/MyWSService />



Another thing, I found is that this is working fine if I use
?wsdl2 in the URL above.

 

Note:

In my services.xml I have useOriginalWSDL property set to
true and modifyUserWSDLPortAddress was also set to true.



I've tried changing modifyUserWSDLPortAddress to false, but
what happened in that case was the soap:address location was not
modified at all.



The soap:address location case as
http://localhost:80/webservices/services/MyWSService
  because the
original WSDL had this address in the soap:address location, since the
localhost was coming as it it, I've change the modifyUserWSDLPortAddress
property back to true.

 

Thanks in Advance.

Raghu

How Axis Callback works?

[Ajay Joshi]

I have queried service using WSDL generated and can see XML Response out
put..
Using   

1. stub.query_my_record(my_Record_Query__Message5);

2. stub.startquery_my_record(my_Record_Query__Message5,
O_tempCallbackN1000C);

Here O_tempCallbackN1000C is callback object.


But I am not sure How Axis Callback works? Can Callback and its method
getClientData() can b used for getting java response object?
  
public my_Record_Query_ProviderCallbackHandler(Object clientData) {
this.clientData = clientData;
}

/**
 * Please use this constructor if you don't want to set any
clientData
 */
public my_Record_Query_ProviderCallbackHandler() {
this.clientData = null;
}

/**
 * Get the client data
 */
public Object getClientData() {
return clientData;
}

What I am trying to do is get the Java response object back from
stub/callback. Your help is greatly appreciated.

Regards
AJ

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

nested complex types

[csanders]

Hi all :).

I'm having some trouble getting nested complex types to work correctly.
I'm noticing that for members of the generated class, instead of using
the generated Wrapper class ( which it does generate ) , it uses
OMElement.

When I run wsdl2java I get several warnings about missing types, for
example :

[WARN] Type {urn:beagle}CompanyBasicInfo missing!

I noticed that the items that don't give me warnings are declared like
this:

  
   
 
 
   
  

and all the ones that it complains are missing are declared like:

  
   

 
 

...


   
  

The wsdl file I'm using was created by gSOAP, and I'm using Axis2-1.3,
and java1.6 on ubuntu amd64.

Thanks!
Charlie

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

RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning "The service cannot be found for the endpoint reference"

[James Maes]

After digging into the Axis code, it looks like the problem is caused by the
following

The RequestDispatch returned from 

httpServletRequest.getRequestDispatcher(Constants.AXIS_WEB_CONTENT_ROOT +
jspName).include(httpServletRequest, httpServletResponse); 
in AbstractAgent.java (renderView method) 

is null. 

The following are the inputs that were passed into that call. 

Constants.AXIS_WEB_CONTENT_ROOT [/axis2-web/]
jspName [listServices.jsp]



I assume that this all points to something miss configured on my end on my
part, but I am out of ideas.  Does this help shed any light on the issue for
anyone?





James Maes
Software Architect
Materialogic
PH: 800-333-7144
PH: 314-997-4342 Ext. 3422
FX: 314-997-7814


-Original Message-
From: James Maes [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 12:46 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5
server - axis2/services returning "The service cannot be found for the
endpoint reference"

When requesting the URL (http://BLAHBLAH/axis2/axis2-web/)
I get this response

HTTP Status 404 - /axis2/axis2-web/


type Status report
message /axis2/axis2-web/
description The requested resource (/axis2/axis2-web/) is not available.


Apache Tomcat/5.5.17

And this on the server console 

[java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 :
g.apache.catalina.core.StandardHostValve : Exception Processing
ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp]
 [java] java.lang.NullPointerException
 [java] at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363
)
 [java] at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284
)
 [java] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136
)
 [java] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
 [java] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
 [java] at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 [java] at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 [java] at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
onnection(Http11BaseProtocol.java:664)
 [java] at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
 [java] at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:80)
 [java] at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
 [java] at java.lang.Thread.run(Thread.java:595)












James Maes
Software Architect
Materialogic
PH: 800-333-7144
PH: 314-997-4342 Ext. 3422
FX: 314-997-7814

From: Upul Godage [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 12:37 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5
server - axis2/services returning "The service cannot be found for the
endpoint reference"

Check accessing these links in your server.

http://blahblash/axis2/axis2-web/
For console home page

http://blahblash/axis2/services/listServices 
For deployed services

Upul
On 10/23/07, James Maes <[EMAIL PROTECTED]> wrote:
Maybe someone can give a little insight into the issue(s) that I am having.

We are trying to embed Axis2 (1.3) into a internal application via Tomcat
(5.5)
Tomcat seems to be working fine (it's used for other war deployments) and 
the axis2.war deploys fine (see below)

Deployment code
 Context context = embedded.createContext("/axis2", "axis2.war");
 context.setReloadable(false);
 host.addChild (context);

War being deployed
 [java] Oct-23-07 11:36:11.081 : INFO  : main :
org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache
Tomcat/5.5.17
 [java] Oct-23-07 11:36: 11.091 : INFO  : main :
org.apache.catalina.core.StandardHost : XML validation disabled
 [java] Oct-23-07 11:36:11.293 : INFO  : main :
rg.apache.catalina.startup.ContextConfig : No default web.xml
 [java] Oct-23-07 11:36:11.915 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3
 [java] Oct-23-07 11:36:11.925 : INFO  : main : 
g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3
 [java] Oct-23-07 11:36:11.949 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 
 [java] Oct-23-07 11:36:11.960 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3

RE: AXIS Fault "Required Attribute localType is null"

[Saket Raizada]

Hi Raghu,
The common.xsd contained this information for the value i was
setting and i see that the type value must be set. In the generated
StringType.java i see a function to set the type and i also see that it
sends an error "Required Attribute localType is null"  if the type is
not set.
 
 Thanks a lot for your help !
 
Below is the snippet from the Commons.xsd
 
- 

- 

- 

   
   
   
  
  
  
regards 
-Saket Raizada  


From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 1:08 PM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 



Hi Saket,

 

Can you also post your Common.xsd file which has the
definition of all the Types.

 

Thanks

Raghu

 



From: Saket Raizada [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 6:38 AM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 

 

Raghu,

I do not see the "type" variable in the WSDL. 

I have attached the WSDL file.

 

Thanks for the help !

regards 
-Saket Raizada 
309-763-5492 
Automation (Maintenance) 

 

 



From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 7:16 PM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 

Hi Saket,

 

Can you post your WSDL?  From the Axis Fault it looks like
you have a variable named "type" in the Incident object which is defined
as not nullable in WSDL and you are not setting that in your request.

 

Thanks

Raghu

 



From: Saket Raizada [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 3:48 PM
To: axis-user@ws.apache.org
Subject: AXIS Fault "Required Attribute localType is null" 

 

 

Hi Folks, 
I am using AXIS 2, 1.3 and created a client for an existing WebService 
I am trying to use the WebService to create an incident using the
example code below 
StringType contact = new StringType(); 
contact.setString("user1"); 
incident.setContact(contact); 
stub.createIncident(incident) 
I get an AXIS Fault "Required Attribute localType is null" , there is no
SOAP body message generated..., however if i comment out the line

//incident.setContact(contact) , the incident gets generated and i can
see the SOAP messages etc. 
I am using ADB binding and am out of ideas what localType is (it's not
part of incident or web service that i am trying to access) also no SOAP
BODY XML is generated.

Any pointers will be very helpful 
-machoq 

Re: Which style am I using?

[Anne Thomas Manes]

Dimitris,

The snippet of your WSDL isn't valid. This:



should be this:



We actually don't have enough information to determine if the style is
wrapped doc/literal. What is the name of the operation? If it is
"viewLesson", then most toolkits will interpret the style as wrapped
doc/literal. If you want all toolkits to recognize it as wrapped
doc/literal, then the part names should be "parameters" rather than
"part1", e.g.:



For more information on the wrapped style, see these links:

http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
http://pzf.fremantle.org/2007/05/handlign.html

Anne

On 10/23/07, Dimitris Mouchritsas <[EMAIL PROTECTED]> wrote:
> Hi everyone,
> I'm kind of new in web services so I need your help once again.
> Say I have the following wsdl:
> 
> 
> http://www.example.org ">
> 
> Blah blah
> 
> 
>   http://www.example.org "
> attributeFormDefault="qualified"
> elementFormDefault="qualified">
> 
>   
> 
>   
> 
>   
>
>  
>
>   
> 
>   
> 
> element="ns0:viewLessonResponse"/>
> 
> 
> 
> so I send and receive messages like (minus the soap envelope):
> 
>   1
> 
>
> Which style am I using? I think I'm using document/wrapped but am I right?
> I've read the
> developer works article on this but I'm not certain yet.  Thanks in advance.
> --
> Dimitris Mouchritsas
> Computer Services

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

RE: AXIS Fault "Required Attribute localType is null"

[Raghu Upadhyayula]

Hi Saket,

 

Can you also post your Common.xsd file which has the
definition of all the Types.

 

Thanks

Raghu

 



From: Saket Raizada [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 6:38 AM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 

 

Raghu,

I do not see the "type" variable in the WSDL. 

I have attached the WSDL file.

 

Thanks for the help !

regards 
-Saket Raizada 
309-763-5492 
Automation (Maintenance) 

 

 



From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 7:16 PM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 

Hi Saket,

 

Can you post your WSDL?  From the Axis Fault it looks like
you have a variable named "type" in the Incident object which is defined
as not nullable in WSDL and you are not setting that in your request.

 

Thanks

Raghu

 



From: Saket Raizada [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 3:48 PM
To: axis-user@ws.apache.org
Subject: AXIS Fault "Required Attribute localType is null" 

 

 

Hi Folks, 
I am using AXIS 2, 1.3 and created a client for an existing WebService 
I am trying to use the WebService to create an incident using the
example code below 
StringType contact = new StringType(); 
contact.setString("user1"); 
incident.setContact(contact); 
stub.createIncident(incident) 
I get an AXIS Fault "Required Attribute localType is null" , there is no
SOAP body message generated..., however if i comment out the line

//incident.setContact(contact) , the incident gets generated and i can
see the SOAP messages etc. 
I am using ADB binding and am out of ideas what localType is (it's not
part of incident or web service that i am trying to access) also no SOAP
BODY XML is generated.

Any pointers will be very helpful 
-machoq 

Re: [Axis2] - Incorrect operation name in SOAP response under Load

[ab]

We're encountering a strange issue during the Load Test of our Webservice 
(using Axis2) on IBM Websphere 6.1. Under high loads, the function name in the 
response is being returned incorrectly. For example,  if the SOAP request is 
for getABC(), the correct code is being executed by the webservice and the 
correct data is being returned but the name of the function in the SOAP 
response is getXYZ instead. Note, getXYZ is also a valid operation in the 
Webservice but the call was not made to it.  No errors in app server logs and 
under low volumes everything works great.

RESPONSE:

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

http://webservice.edars.eo/xsd";>  <- 
INSTEAD OF getABC ->



 <- INSTEAD OF getABC ->

  
  

Anyone seen this before or have any ideas as to how to tackle it? I've never 
encountered this in Axis 1.x and am wondering if there's some caching 
etc going on that may be causing it by multi-thread access. Saw below in JIRA  
and was wondering if there was any relation?? Appreciate your input.

AXIS2-2794 
- Axis2 contexts use 
unsyncronized HashMap instead of Hashtables

Created: 11/Jun/07 12:33 PM  
Updated: 11/Jun/07 02:44 PM























Component/s:





kernel











Affects Version/s:






1.3











Fix Version/s:





None































 Description 

« Hide







Axis2 context hierachy uses HashMaps to store the properties and since
HashMaps are not syncronized, the results of multitreaded access is not
undefinded. It is advisable to switch to Hashtables. However we have
not seen this error happens so far in our bug reports, which is indeed
stange enough. 













 Description 


 
 Axis2 context hierachy uses HashMaps to store the properties and since
HashMaps are not syncronized, the results of multitreaded access is not
undefinded. It is advisable to switch to Hashtables. However we have
not seen this error happens so far in our bug reports, which is indeed
stange enough. 


Show »









-Ab


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




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

RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning "The service cannot be found for the endpoint reference"

[James Maes]

When requesting the URL (http://BLAHBLAH/axis2/axis2-web/)
I get this response

HTTP Status 404 - /axis2/axis2-web/


type Status report
message /axis2/axis2-web/
description The requested resource (/axis2/axis2-web/) is not available.


Apache Tomcat/5.5.17

And this on the server console 

[java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 :
g.apache.catalina.core.StandardHostValve : Exception Processing
ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp]
 [java] java.lang.NullPointerException
 [java] at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363
)
 [java] at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284
)
 [java] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136
)
 [java] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
 [java] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
 [java] at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 [java] at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 [java] at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
onnection(Http11BaseProtocol.java:664)
 [java] at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
 [java] at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:80)
 [java] at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
 [java] at java.lang.Thread.run(Thread.java:595)












James Maes
Software Architect
Materialogic
PH: 800-333-7144
PH: 314-997-4342 Ext. 3422
FX: 314-997-7814

From: Upul Godage [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 12:37 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5
server - axis2/services returning "The service cannot be found for the
endpoint reference"

Check accessing these links in your server.

http://blahblash/axis2/axis2-web/
For console home page

http://blahblash/axis2/services/listServices 
For deployed services

Upul
On 10/23/07, James Maes <[EMAIL PROTECTED]> wrote:
Maybe someone can give a little insight into the issue(s) that I am having.

We are trying to embed Axis2 (1.3) into a internal application via Tomcat
(5.5)
Tomcat seems to be working fine (it's used for other war deployments) and 
the axis2.war deploys fine (see below)

Deployment code
 Context context = embedded.createContext("/axis2", "axis2.war");
 context.setReloadable(false);
 host.addChild (context);

War being deployed
 [java] Oct-23-07 11:36:11.081 : INFO  : main :
org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache
Tomcat/5.5.17
 [java] Oct-23-07 11:36: 11.091 : INFO  : main :
org.apache.catalina.core.StandardHost : XML validation disabled
 [java] Oct-23-07 11:36:11.293 : INFO  : main :
rg.apache.catalina.startup.ContextConfig : No default web.xml
 [java] Oct-23-07 11:36:11.915 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3
 [java] Oct-23-07 11:36:11.925 : INFO  : main : 
g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3
 [java] Oct-23-07 11:36:11.949 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 
 [java] Oct-23-07 11:36:11.960 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3
 [java] Oct-23-07 11:36:11.971 : INFO  : main : 
g.apache.axis2.deployment.ModuleDeployer : Deploying module:
metadataExchange-1.3
 [java] Oct-23-07 11:36:12.010 : INFO  : main :
org.apache.axis2.scripting.ScriptModule : script module activated 
 [java] Oct-23-07 11:36:12.189 : INFO  : main :
.apache.axis2.deployment.ServiceDeployer : Deploying Web service:
version.aar


The issue that I am having is that once axis is deployed, about the only 
things I can get to come back are the following

>From the request (http://BLAHBLASH/axis2/services)
http://www.w3.org/2003/05/soap-envelope";>
The service cannot be found for the
endpoint reference (EPR) /axis2/services
 

It looks like things are close to "working" and that I am just missing
something.  Can anyone help shed any light on this?





Also, not sure if this helps, but I also get the following when I try to 
just access the context url

>From the request (http://BLAHBLASH/axis2/)
HTTP Status 404 - /

New stup for each call

[Łabno, Bernard]

Hello,
Do I have to create new stub before each call ?

In my case i have EJB that calls webservice. If i save aquired port in 
attribute and use it in multiple calls i get some strange exception.

MainQueryEngineBean.doQuery().engine:[EMAIL PROTECTED]
PWC1635: Illegal access: this web application instance has been stopped 
already (the eventual following stack trace is caused by an error thrown for 
debugging purposes as well as to attempt to terminate the thread which caused 
the illegal access, and has no functional impact)
urlSet = [URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroWebApi.jar,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-ejb.jar,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroEngine-ejb.jar,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/MainQueryEngine-ejb_jar/,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroEngine-ejb_jar/,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-ejb_jar/,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/MainQueryEngine-ejb.jar,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-war_war/WEB-INF/classes/,
 
URLEntry : 
file:/opt/glassfish-v2-b58/domains/domain1/generated/ejb/j2ee-apps/BidBull/]
doneCalled = false 
 Parent -> EJBClassLoader : 
urlSet = []
doneCalled = false 
 Parent -> [EMAIL PROTECTED]
 AT Tue Oct 23 19:40:29 CEST 2007 
 
BY 
:com.sun.enterprise.loader.EJBClassLoader.printStackTraceToString(EJBClassLoader.java:812)
com.sun.enterprise.loader.EJBClassLoader.done(EJBClassLoader.java:172)
com.sun.enterprise.server.AbstractLoader.done(AbstractLoader.java:359)
com.sun.enterprise.server.ApplicationLoader.unload(ApplicationLoader.java:264)
com.sun.enterprise.server.TomcatApplicationLoader.unload(TomcatApplicationLoader.java:213)
com.sun.enterprise.server.ApplicationManager.applicationUndeployed(ApplicationManager.java:525)
com.sun.enterprise.server.ApplicationManager.applicationUndeployed(ApplicationManager.java:699)
com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:930)
com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStopEvent(ServerDeploymentTarget.java:332)
com.sun.enterprise.deployment.phasing.ApplicationStopPhase.runPhase(ApplicationStopPhase.java:136)
com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:652)
com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:699)
com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.stop(ApplicationsConfigMBean.java:767)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
$Proxy1.invoke(Unknown Source)
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
com.sun.enter

Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning "The service cannot be found for the endpoint reference"

[Upul Godage]

Check accessing these links in your server.

http://blahblash/axis2/axis2-web/
For console home page

http://blahblash/axis2/services/listServices
For deployed services

Upul
On 10/23/07, James Maes <[EMAIL PROTECTED]> wrote:
>
> Maybe someone can give a little insight into the issue(s) that I am
> having.
>
> We are trying to embed Axis2 (1.3) into a internal application via Tomcat
> (5.5)
> Tomcat seems to be working fine (it's used for other war deployments) and
> the axis2.war deploys fine (see below)
>
> Deployment code
>  Context context = embedded.createContext("/axis2", "axis2.war");
>  context.setReloadable(false);
>  host.addChild(context);
>
> War being deployed
>  [java] Oct-23-07 11:36:11.081 : INFO  : main :
> org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache
> Tomcat/5.5.17
>  [java] Oct-23-07 11:36:11.091 : INFO  : main :
> org.apache.catalina.core.StandardHost : XML validation disabled
>  [java] Oct-23-07 11:36:11.293 : INFO  : main :
> rg.apache.catalina.startup.ContextConfig : No default web.xml
>  [java] Oct-23-07 11:36:11.915 : INFO  : main :
> g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3
>  [java] Oct-23-07 11:36:11.925 : INFO  : main :
> g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3
>  [java] Oct-23-07 11:36:11.949 : INFO  : main :
> g.apache.axis2.deployment.ModuleDeployer : Deploying module:
> addressing-1.3
>  [java] Oct-23-07 11:36:11.960 : INFO  : main :
> g.apache.axis2.deployment.ModuleDeployer : Deploying module:
> soapmonitor-1.3
>  [java] Oct-23-07 11:36:11.971 : INFO  : main :
> g.apache.axis2.deployment.ModuleDeployer : Deploying module:
> metadataExchange-1.3
>  [java] Oct-23-07 11:36:12.010 : INFO  : main :
> org.apache.axis2.scripting.ScriptModule : script module activated
>  [java] Oct-23-07 11:36:12.189 : INFO  : main :
> .apache.axis2.deployment.ServiceDeployer : Deploying Web service:
> version.aar
>
>
> The issue that I am having is that once axis is deployed, about the only
> things I can get to come back are the following
>
> From the request (http://BLAHBLASH/axis2/services)
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
> The service cannot be found for the
> endpoint reference (EPR) /axis2/services
> 
>
> It looks like things are close to "working" and that I am just missing
> something.  Can anyone help shed any light on this?
>
>
>
>
>
> Also, not sure if this helps, but I also get the following when I try to
> just access the context url
>
> From the request (http://BLAHBLASH/axis2/)
> HTTP Status 404 - /axis2/
>
>
> 
> 
> type Status report
> message /axis2/
> description The requested resource (/axis2/) is not available.
>
>
> 
> 
> Apache Tomcat/5.5.17
>
> And a NPE from the console of the server of
>  [java] java.lang.NullPointerException
>  [java] at
> org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java
> :363
> )
>  [java] at
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java
> :284
> )
>  [java] at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :136
> )
>  [java] at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :105
> )
>  [java] at
> org.apache.catalina.core.StandardEngineValve.invoke(
> StandardEngineValve.java
> :107)
>  [java] at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
> :148)
>  [java] at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>  [java] at
>
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
> onnection(Http11BaseProtocol.java:664)
>  [java] at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
> PoolTcpEndpoint.jav
> a:527)
>  [java] at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
> (LeaderFollowerWo
> rkerThread.java:80)
>  [java] at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
> ThreadPool.jav
> a:684)
>  [java] at java.lang.Thread.run(Thread.java:595)
>
>
>
>
>
> James Maes
> Software Architect
> Materialogic
> PH: 800-333-7144
> PH: 314-997-4342 Ext. 3422
> FX: 314-997-7814
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: error creating message from generated client

[Kimberly Nicholls]

No, the client throws the exception when trying to create the request 
message.  It doesn't actually reach the server.


Kimberly Nicholls

keith chapman wrote:
I presume this error occurs when you receive the response. Can you 
check the messages using TCP Monitor please and post it here.


Thanks,
Keith.

On 10/22/07, * Kimberly Nicholls* <[EMAIL PROTECTED] 
> wrote:


I am having trouble creating a SOAP message from a generated
client when the message includes attachments -- the client throws
"org.apache.axiom.soap.SOAPProcessingException: First Element must
contain the local name, Envelope , but found html."  I am using
axis2 1.3, and I can make requests to other methods (without
attachments) in the same service with no problems.

Here's what I did:

- set enableMTOM to true in axis2.xml
- created method in my POJO service: public long
createAttachment(long messageID, DataHandler attData) 
- generated client stub via wsdl2java

- added these lines to client stub:
_serviceClient.getOptions().setProperty(
Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
 _serviceClient.getOptions().setTimeOutInMilliSeconds(1);
- created client that runs the method like this:
DataHandler attData = new DataHandler(new
FileDataSource(filename));
long attachmentID = stub.createAttachment(messageID,
attData);

When I run the client, I get

[INFO] OMException in getSOAPBuilder
org.apache.axiom.soap.SOAPProcessingException: First Element must
contain the local name, Envelope , but found html
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:219)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:177)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:163)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:110)
at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:609)
at

org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:178)
at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
at

org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326)
at

org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at

org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
...
Caused by: org.apache.axiom.soap.SOAPProcessingException: First
Element must contain the local name, Envelope , but found html
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:219)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:177)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:163)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161)
at

org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:110)
at
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:609)
at

org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:178)
at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
at

org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
... 6 more


Running other methods in the same client with the same service
work fine, if they don't have attachments.  The file I'm trying to
send is a 2.5k jpg.  What am I doing wrong?

Kimberly




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

[Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning "The service cannot be found for the endpoint reference"

[James Maes]

Maybe someone can give a little insight into the issue(s) that I am having. 

We are trying to embed Axis2 (1.3) into a internal application via Tomcat
(5.5)
Tomcat seems to be working fine (it's used for other war deployments) and
the axis2.war deploys fine (see below)

Deployment code
 Context context = embedded.createContext("/axis2", "axis2.war");
 context.setReloadable(false);
 host.addChild(context);

War being deployed
 [java] Oct-23-07 11:36:11.081 : INFO  : main :
org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache
Tomcat/5.5.17
 [java] Oct-23-07 11:36:11.091 : INFO  : main :
org.apache.catalina.core.StandardHost : XML validation disabled
 [java] Oct-23-07 11:36:11.293 : INFO  : main :
rg.apache.catalina.startup.ContextConfig : No default web.xml
 [java] Oct-23-07 11:36:11.915 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3
 [java] Oct-23-07 11:36:11.925 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3
 [java] Oct-23-07 11:36:11.949 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3
 [java] Oct-23-07 11:36:11.960 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3
 [java] Oct-23-07 11:36:11.971 : INFO  : main :
g.apache.axis2.deployment.ModuleDeployer : Deploying module:
metadataExchange-1.3
 [java] Oct-23-07 11:36:12.010 : INFO  : main :
org.apache.axis2.scripting.ScriptModule : script module activated
 [java] Oct-23-07 11:36:12.189 : INFO  : main :
.apache.axis2.deployment.ServiceDeployer : Deploying Web service:
version.aar


The issue that I am having is that once axis is deployed, about the only
things I can get to come back are the following

>From the request (http://BLAHBLASH/axis2/services)
http://www.w3.org/2003/05/soap-envelope";>
The service cannot be found for the
endpoint reference (EPR) /axis2/services 


It looks like things are close to "working" and that I am just missing
something.  Can anyone help shed any light on this?





Also, not sure if this helps, but I also get the following when I try to
just access the context url

>From the request (http://BLAHBLASH/axis2/)
HTTP Status 404 - /axis2/



type Status report
message /axis2/
description The requested resource (/axis2/) is not available.



Apache Tomcat/5.5.17

And a NPE from the console of the server of 
 [java] java.lang.NullPointerException
 [java] at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363
)
 [java] at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284
)
 [java] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136
)
 [java] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
 [java] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
 [java] at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 [java] at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 [java] at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
onnection(Http11BaseProtocol.java:664)
 [java] at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
 [java] at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:80)
 [java] at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
 [java] at java.lang.Thread.run(Thread.java:595)





James Maes
Software Architect
Materialogic
PH: 800-333-7144
PH: 314-997-4342 Ext. 3422
FX: 314-997-7814


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

Re: org.apache.axis2.databinding.ADBException: Property cannot be null!

[Huitang Li]

Excellent! Thanks very much. Somehow -Eosv does not solve the problem. 
So I put the nillable="true" in the element there, and it works.






Amila Suriarachchi wrote:
this means your object structure do not have loaded the required fault 
elements.


see you schema there should be an element named fault without 
minOccurs=0 or nillable=ture.

So ADB gives an exception because of this.

if you want to remove this use -Eosv when genrating the code.

Amia.


On 10/23/07, *Huitang Li* < [EMAIL PROTECTED] 
> wrote:


Hi,

I created a web service code based on a wsdl, and it is run in resin
3.1.3, and I have the soapmonitor activated.  When a web service
client
sent a soap message to it, it threw the following exception:

java.lang.RuntimeException: Can not serialize OM Element Envelope
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:916)
at

org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101)
at org.apache.axis2.engine.Phase.invoke (Phase.java:292)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at
org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:442)
at
org.apache.axis2.transport.http.AxisServlet.handleFault
(AxisServlet.java:403)
at

org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:366)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:154)
at javax.servlet.http.HttpServlet.service (HttpServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
at

com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:103)
at
com.caucho.server.security.SecurityFilterChain.doFilter
(SecurityFilterChain.java:134)
at

com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:178)
at

com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:241)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:268)
at
com.caucho.server.port.TcpConnection.run(TcpConnection.java:586)
at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java :690)
at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:612)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.databinding.ADBException: Property
cannot be
null!
at test.Fault.serialize (Fault.java:95)
at test.Fault$1.serialize(Fault.java:80)
at
org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:82)
at

org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume
(OMSourcedElementImpl.java:599)
at

org.apache.axiom.soap.impl.llom.SOAPFaultDetailImpl.internalSerialize(SOAPFaultDetailImpl.java:86)
at

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java
:756)
at

org.apache.axiom.soap.impl.llom.SOAPFaultImpl.internalSerialize(SOAPFaultImpl.java:192)
at

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:772)
at

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at

org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java
:210)
at

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString
(OMElementImpl.java:913)
... 18 more

This exception will not be shown when all elements in the requesting
soap message are filled with non-empty (no-blankspace) values.

I notice that the exception is thrown from the following
axis2-generated
code:


   public void serialize(final javax.xml.namespace.QName parentQName,
final org.apache.axiom.om.OMFactory factory,

org.apache.axis2.databinding.utils.writer.MTOMAwareXMLStreamWriter
xmlWriter)
throws javax.xml.stream.XMLStreamException,
org.apache.axis2.databinding.ADBException {
//We can safely assume an element has only one type associated
with it
if (localFault == null) {
throw new org.apache.axis2.databinding.ADBException(
"Property cannot be null!");
<  the line where the exception is thrown.
}

 localFault.serialize(MY_QNAME, factory, xmlWriter);
}


My question is: In the line where the exception is thrown, why is the
parameter localFault null? Ho

Re: JBoss and Apache Axis compatibility

[M N]

I am using JBOSS and Axis 1.4 and they work fine. Its just plain java objects 
communication between jboss and axis so I am not sure why you are concerned 
with rpc
encoding style..
  
Arun Sivaraman <[EMAIL PROTECTED]> wrote:
  

I'm in the midst of integrating two components, one runs in JBoss and other
components exposes some web services deployed in Axis. When i integrate
them, there will be a communication between component deployed in JBOSS and
Web services exposed via Axis.

If i understand correctly, AXIS by default uses RPC service style and JBOSS
uses document/literal encoding format. So there is a notion of soap-wsdl
encoding format change required here.

All i wanted to know is that,
1.Is there any compatibility issues (if any) between JBOSS and Axis ?
2.JBOSS-Axis interaction with respect to the soap encoding format ?
3.Some explanation on SOAP encodingStyle ?

Expecting ur favorable reply

Regards
Arun
Email :[EMAIL PROTECTED]
-- 
View this message in context: 
http://www.nabble.com/JBoss-and-Apache-Axis-compatibility-tf4675459.html#a13358175
Sent from the Axis - User mailing list archive at Nabble.com.


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



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

AXIS1 Problem with generated sources: Params were mixed up within super constructor.

[Alexey Zavizionov]

Hello,

I have a troble while building the sources generated by Axis1 1.4.
There's a problem with super constructor, it looks like params were
mixed up within.

For example, there are two classes: one is MarkupContext which extends
MimeResponse.

Constructor of MimeResponse is generated in such a way that described
attribute is at the end.
But, constructor of MarkupContext invokes super with the attribute
placed as a first param.

==
  

  
  
  
  
  
  
  
  
  


  
  

  

  

  
  

  

  
  
==

Regards,
Alexey.

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

My fresh token is already invalid!!! (Rampart throws NPE)

[Massimiliano Masi]

Hi All,

I have the SAML2 token issuer. I request it using STSClient:

Token responseToken = stsClient.requestSecurityToken(servicePolicy,   
sts, stsPolicy, service);


Then I add it to the TokenStorage:

TokenStorage store = TrustUtil.getTokenStore(ctx);
store.add(responseToken); // now store contains my SAML2 token

The problem is when I try to get the list of valid tokens:

Token[] tokens = store.getValidTokens();

for (int i=0; iI don't enter in the for loop. When I try to send the message to the  
endpoint, I got this:


16:21:15,931 INFO  [XUAAssertions]  
Payloadxmlns:axis2ns1="http://tiani/xds";>WSO2 WSAS  
Rocks!!!

16:21:15,954 ERROR [STDERR] java.lang.NullPointerException
16:21:15,956 ERROR [STDERR] at  
org.apache.rampart.builder.SymmetricBindingBuilder.initializeTokens(SymmetricBindingBuilder.java:681)
16:21:15,957 ERROR [STDERR] at  
org.apache.rampart.builder.SymmetricBindingBuilder.build(SymmetricBindingBuilder.java:73)



In SymmetricBindingBuilder at the line 681 I have:

SecureConversationToken secConvTok =
 (SecureConversationToken) sigTok;

 try {  <-- this is the 681
 String id = RampartUtil.getSecConvToken(rmd, secConvTok);
 rmd.setSecConvTokenId(id);

I'm using rampart 1.3, and the code is from three days ago. It shouldn't be
here. Is not WS-SecConv.

My policy is:

 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";

xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>


 
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>







   
 
   
sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>
   
 
   
xmlns="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
   
 
  xmlns="http://www.w3.org/2005/08/addressing";>
   
  http://foo.bar/we/don/t/process/this/yet
   
  
   
  
   
  
   
 
   
xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust";>
   
  urn:oasis:names:tc:SAML:2.0:assertion
   
  


   
  


   
  



   
  















This message was sent using IMP, the Internet Messaging Program.



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

RE: AXIS Fault "Required Attribute localType is null"

[Saket Raizada]

Raghu,
I do not see the "type" variable in the WSDL. 
I have attached the WSDL file.
 
Thanks for the help !

regards 
-Saket Raizada 
309-763-5492 
Automation (Maintenance) 

 



From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 7:16 PM
To: axis-user@ws.apache.org
Subject: RE: AXIS Fault "Required Attribute localType is null" 



Hi Saket,

 

Can you post your WSDL?  From the Axis Fault it looks like
you have a variable named "type" in the Incident object which is defined
as not nullable in WSDL and you are not setting that in your request.

 

Thanks

Raghu

 



From: Saket Raizada [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 3:48 PM
To: axis-user@ws.apache.org
Subject: AXIS Fault "Required Attribute localType is null" 

 

 

Hi Folks, 
I am using AXIS 2, 1.3 and created a client for an existing WebService 
I am trying to use the WebService to create an incident using the
example code below 
StringType contact = new StringType(); 
contact.setString("user1"); 
incident.setContact(contact); 
stub.createIncident(incident) 
I get an AXIS Fault "Required Attribute localType is null" , there is no
SOAP body message generated..., however if i comment out the line

//incident.setContact(contact) , the incident gets generated and i can
see the SOAP messages etc. 
I am using ADB binding and am out of ideas what localType is (it's not
part of incident or web service that i am trying to access) also no SOAP
BODY XML is generated.

Any pointers will be very helpful 
-machoq 

http://openview.hp.com/xmlns/SM/1"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:cmn="http://openview.hp.com/xmlns/SM/1/Common"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:ns="http://openview.hp.com/xmlns/SM/1"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://schemas.xmlsoap.org/wsdl/  http://schemas.xmlsoap.org/wsdl/";>http://www.w3.org/2001/XMLSchema"; attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://openview.hp.com/xmlns/SM/1"; version="2007-04-14 Rev 1" xmlns="http://openview.hp.com/xmlns/SM/1"; xmlns:cmn="http://openview.hp.com/xmlns/SM/1/Common"; xmlns:xmime="http://www.w3.org/2005/05/xmlmime";>http://www.w3.org/2005/05/xmlmime"; schemaLocation="http://www.w3.org/2005/05/xmlmime"/>http://openview.hp.com/xmlns/SM/1/Common"; schemaLocation="http://xyz.com:111/SM/1/Common.xsd"/>http://schemas.xmlsoap.org/soap/http"/>http://xyz.com:111/SM/1/ws"/>-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Best way to realize stateful servicesarchitecturewithmassivedata?

[Yogesh . Dhake]

Steps similar to MTOM sample with file caching enabled. Received 
dataStream is loaded in XML object for further transformation.



regards
Yogesh



"robert lazarski" <[EMAIL PROTECTED]> 
10/22/2007 05:17 PM
Please respond to
axis-user@ws.apache.org


To
axis-user@ws.apache.org
cc

Subject
Re: Best way to realize stateful servicesarchitecturewithmassivedata?






That's pretty kool. Did you use any streaming to avoid putting the data in 
memory and building the tree? Or did you just more or less follow the same 
steps in the mtom tutorial? 

Robert 

On 10/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
wrote:

Hi 

We were in similar situation we were planning to transfer 1GB file as SOAP 
as attachment. 

1)  Axis2 give pretty good support using MTOM and SWA for transferring any 
size file.  1GB file transferred in 67sec on local network. File caching 
feature is great. 
2) But it is not good idea to transfer SOAP with such large attachment. We 
also hit some our app server & service bus handling limitation. So we 
decided to process data in chunk.  We get file data in chunk and till we 
get all data correctly we dont send confirm to end point (which really 
delete file on source system . End of our getFile operation / confirming 
file received at server ). Same way on reverse we put data in chunk to 
some temp file on destination endpoint.  after placing all data at end we 
rename it to required file. 

Let me know your thoughts 

Regards 
Yogesh Dhake 



"Walker, Jeff" <[EMAIL PROTECTED]> 
10/22/2007 11:46 AM 

Please respond to
axis-user@ws.apache.org



To
 
cc

Subject
RE: Best way to realize stateful servicesarchitecturewithmassivedata?








Michele,
I'm not sure JMS is a viable alternative if large amounts of data are
transferred. That statement would imply there is some sort of size
cutoff. There isn't. Just remember, that with JMS you can have persisted
queues and then all of that data would have to be stored temporarily.
Personally, I think some of the lessons from JMS (message queuing in
general) can be applied to web services; keep the msgs as small as
possible.

Large data transfer (across the network) is a serious problem. There is
no easy solution that I've seen. Having said that, there are quite a few
posters who have used attachments with their web services. I have used
the older DIME format, but other posters have used the newer MTOM. I
would be interested to see what their performance was like, with large
files (ie. around a Gigabyte, say). Since MTOM chunks up the files,
transferring any sized file should theoretically be possible.

Does anyone have any opinions on using MTOM for transferring Gb and and
multi-Gb files??
-jeff




-Original Message-
From: Michele Mazzucco [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 11:21 AM
To: axis-user@ws.apache.org
Subject: RE: Best way to realize stateful
servicesarchitecturewithmassivedata?

Jeff,

I mentioned JMS as possible choice if one has to transfer large amount
of data since it is asynchronous.

Michele

On Mon, 2007-10-22 at 11:10 -0400, Walker, Jeff wrote:
> You mentioned WS over JMS. Again, added delay, since another protocol
> layer is employed. 


-
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]


==
 

This transmittal and any attachments may contain confidential, privileged 
or sensitive information and is solely for the use of the intended 
recipient. If you are not the intended recipient, you are hereby notified 
that you have received this transmittal and any attachments in error and 
any review, dissemination, distribution or copying thereof is strictly 
prohibited. If you have received this transmittal and any attachments in 
error please notify the sender and immediately destroy the message and all 
its attachments. Any opinions herein expressed may be those of the author 
and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank 
(USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho 
Financial Group ("Mizuho"). Mizuho accepts no responsibility for the 
accuracy or completeness of any information herein contained. 
E-Mail received by or sent from officer of Mizuho Securities USA Inc. 
(which is a registered U.S. broker-dealer and the entity through which 
Mizuho generally conducts its investment banking, capital markets, and 
securities business in the United States) is electronically archived and 
recorded and is subject to review and monitoring by and/or disclosure to 
persons other than the recipient, including (but not limited to) Mizuho 
Securities USA Inc. supervisory personnel. Such communicat

Re: [axis2 1.3] Metadata echange documentation

[Deepal jayasinghe]

Hi sanka,
Do we have any document on this ?

Thanks
Deepal
> Hi all,
>
> I need any documentation on the Metadata exchange module of axis2 1.3
> (mex).
>
> thanks in advance
>
> Regards,
> Nencho


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

Re: Using Amazon Web Service Java Library with Apache Axis2

[Sanka Samaranayke]

Hi,

Did you try including that library in lib folder in your service aar file?

--Sanka



Gia Hieu Dinh wrote:

Hi all,
I'm looking for invoking the Amazon Web Service inside my Axis2 web service.
Amazon provides a java library to connect to the web services. 
http://developer.amazonwebservices.com/connect/entry.jspa?entryID=880&ref=featured

I have developed a standalone application with this library and it works
fine. However, when I invoke it inside the Axis2 Web Service, I cannot reach
the Amazon Web Service. 
I have copy these library to axis2/web-inf/lib and %TOMCAT_HOME%/share/lib,

but nothing happens.
Could you please help me figure out how to use this library? 
Thanks. 
Harry


  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

Re: Axis2: howto handle custom mustUnderstand Headers

[Sanka Samaranayke]

And I believe you should process it via custom module since Axis2 verifies 
whether all headers with mustUnderstand attribute set to true, have been 
processed before Message Receiver being invoked.


Cheers,
-- Sanka


ROSSILLE Samuel wrote:

Hi

messageContext.getEnvelope().getHeader().examineAllHeaderBlocks()
gives you an Iterator over all the SOAPHeaderBlock of the message

hb.getMustUnderstand()
tells you if a the SOAPHeaderBlock hb must be understood.

hb.setProcessed()
tells Axis that your program understands a the SOAPHeaderBlock hb and has correctly completed it's processing. 


Regards
Samuel Rossille

-Message d'origine-
De : Andreas Schultz [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 16 octobre 2007 15:54

À : axis-user@ws.apache.org
Objet : Axis2: howto handle custom mustUnderstand Headers

Hi all,

I need to handle custom header fields that have the mustUnderstand
attribute set to true(1).
Currently such an invocation triggers a fault:
org.apache.axis2.AxisFault: Must Understand check failed for header : MyID

Searching the maillinglist has turned up a references to a
MustUnderstandChecker, but i don't understand how i tell it what
header elements are supported.

Is there a magic trick to tell axis which headers my service likes?

Regards
Andreas

-
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]


  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

RE: Compiler Warnings After Code Generation

[Hart, Leo]

Ah...so I need to wait until they bring it up to 1.5.  I'll look on the
project timeline and see if they indicate that somewhere.  
 
Thanks!


  _  

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 22, 2007 10:01 PM
To: axis-user@ws.apache.org
Subject: Re: Compiler Warnings After Code Generation


The reason is that Axis2 is JDK 1.4 compatible and hence it does
not use Generics. There warnings pop up because your project uses JDK
1.5 and the code generated by Axis2 is JDK 1.4 compatible (Without
Generics).

Thanks, 
Keith.


On 10/22/07, Hart, Leo <[EMAIL PROTECTED]> wrote: 

Hello,
 
I've used the wsdl2java command-line tool to create a
client stub for my WSDL.  The code works fine, however now I have
hundreds of warnings in Eclipse and my ant builds, pointing to the
generated code.  Some of these include:

*   Class is a raw type. References to generic type
Class should be parameterized 
*   Empty block should be documented 
*   HashSet is a raw type. References to generic
type HashSet should be parameterized 
*   The local variable other is never read

Now I realize that I can go into the compiler settings
within Eclipse and turn off these warnings for a project, but I would
like to receive these warning for code my team has generated.  Does
anyone have any suggestions around suppressing/fixing these warnings?
 
Thanks,
Leo




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

Re: [axis2] Define policy in services.xml on operation level

[Sanka Samaranayke]

Hi Nencho,

It seems that you've set the  parameter to 'true' which 
outputs the WSDL document in the service aar for any ?wsdl requests.

Obviously that doesn't include the policies that you've defined within the 
operation definition in the services.xml.

Best,
Sanka




Nencho Lupanov wrote:

Hi all,
 
do you know wheather it is valid to attach a policy in services.xml 
descriptor on operation level ,
i tryed this just by embedding the policy tag as a child of the 
operation tag, just like i would done it on a service level but
it is not reflected in the wsdl - is that a problem in the wsdl 
generation or i am doing something wrong?

You may found my services.xml attached
 
thanks,

Nencho


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



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

[axis2 1.3] Metadata echange documentation

[Nencho Lupanov]

Hi all,

I need any documentation on the Metadata exchange module of axis2 1.3
(mex).

thanks in advance

Regards,
Nencho

RE: Getting teh following error trying to set the transport properties dynamically

[Ajeet Phansalkar]

Sending again as earlier one didn't go through

 

Thanks & Regards,

Ajeet Phansalkar

 

  _  

From: Ajeet Phansalkar [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 23, 2007 10:35 AM
To: 'axis-user@ws.apache.org'
Subject: Getting teh following error trying to set the transport properties
dynamically

 

Hi,

 

I have created a Stubs using ADB binding from .NET webservice wsdl.When
running the  client to access the webservice 

I got the error on "Unknown host exception".It looked like the client was
unable to go through the proxy to the webservice.The web service is outside
my client's network,hence using the proxy.

To resolve this problem I assumed that the stubs would be using the
axis2.xml file ,so I set the configurations in transport sender there. But
still the problem persisted as my java client is a standalone and not in a
J2EE app server. So I am trying to set the transport sender properties
dynamically in code. But now I get the following error:

 

og4j:WARN No appenders could be found for logger
(org.apache.axis2.description.AxisService).

log4j:WARN Please initialize the log4j system properly.

org.apache.axis2.AxisFault: Transport out has not been set

  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)

  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:374)

  at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
peration.java:211)

  at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)

  at
com.choicepoint.bixg.axis2.webservice.SearchAPI1Stub.CustomSearch(SearchAPI1
Stub.java:764)

  at com.choicepoint.bixg.axis2.client.Client.doInOnly(Client.java:64)

  at com.choicepoint.bixg.axis2.client.Client.main(Client.java:20)

 

 

Following is the  piece of code in stub which I am trying to set the
properties

 

public SearchAPI1Stub(org.apache.axis2.context.ConfigurationContext
configurationContext,

java.lang.String targetEndpoint, boolean useSeparateListener)

throws org.apache.axis2.AxisFault {

 //To populate AxisService

 populateAxisService();

 populateFaults();

 

_serviceClient = new
org.apache.axis2.client.ServiceClient(configurationContext,_service);





configurationContext =
_serviceClient.getServiceContext().getConfigurationContext();

 

_serviceClient.getOptions().setTo(new
org.apache.axis2.addressing.EndpointReference(

targetEndpoint));

 
_serviceClient.getOptions().setUseSeparateListener(useSeparateListener);



//Set the soap version

 
_serviceClient.getOptions().setSoapVersionURI(org.apache.axiom.soap.SOAP12Co
nstants.SOAP_ENVELOPE_NAMESPACE_URI);



//_serviceClient.getOptions().setSenderTransport(new
TransportOutDescription(new QName(Constants.TRANSPORT_HTTP)));

 
_serviceClient.getOptions().setProperty(HTTPConstants.HTTP_PROTOCOL_VERSION,
HTTPConstants.HEADER_PROTOCOL_11);

 

HttpTransportProperties.ProxyProperties proxyProperties = new
HttpTransportProperties.ProxyProperties();

proxyProperties.setProxyName("proxyname");

proxyProperties.setProxyPort(proxyport);

proxyProperties.setDomain("domain name");

HttpTransportProperties.Authenticator

auth = new HttpTransportProperties.Authenticator();

auth.setUsername("username");

auth.setPassword("password"); 

//  set if realm or domain is known

 
_serviceClient.getOptions().setProperty(org.apache.axis2.transport.http.HTTP
Constants.AUTHENTICATE, auth);

 
_serviceClient.getOptions().setProperty(HTTPConstants.PROXY,proxyProperties)
;



}

Request help in figuring out this issue.

 

Thanks & Regards,

Ajeet Phansalkar


http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_

This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete  this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at [EMAIL PROTECTED] and delete this mail. 
_

Re: How to use WSDL to validate soap message?

[Dimitris Mouchritsas]

Eran Chinthaka wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Please read a doc on data binding and please

1. do not cross post
2. do not use dev-list to ask non-architectural questions.

Chinthaka

Wenshuang Sun wrote:
  

Hi,

How to use WSDL to validate the soap message in axis2, is the API
about the function  provided?

Thanks.

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





-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHHZ85jON2uBzUhh8RAtRGAJ9cQZIkS6+HQVieeCgzRFoPU4tuzACgldY2
Q9NuWsytX9oEaM19DTE5u/w=
=y11O
-END PGP SIGNATURE-

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


  
I've actually used the lib from Xerces. You need xml-apis.jar from 
there. Then I placed my .xsd files in the root of the archive file (aar) 
and my validation method is like this:


public String validate(String schemaFile, OMElement xml) {

   String returnMessage = null;
   try {
   SchemaFactory schemaFactory = 
SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema";);


   Schema schemaXSD   = 
schemaFactory.newSchema(this.getClass().getResource("/" + schemaFile));

   Validator validator= schemaXSD.newValidator();
   DocumentBuilder parser = 
DocumentBuilderFactory.newInstance().newDocumentBuilder();
   InputSource docSource  = new InputSource(new 
StringReader(xml.toString()));

   Document document  = parser.parse(docSource);
   validator.validate(new DOMSource(document));
   } catch (Exception e) {
   e.printStackTrace();
   returnMessage = e.toString();
   // Clear the org.xml.sax.SAXParseException from the string
   returnMessage = returnMessage.replaceAll(
   "org\\.xml\\.sax\\.SAXParseException: ", "");
   }
   return returnMessage;
   }

For small messages I have not noticed a delay in the validation. But I 
still need to check with attachments. Also notice the "/" in the 
getResource. This

is crucial for finding the schema file in the archive.

[AXIS2] Using a custom truststore

[Alistair Young]

Hi there,

is it possible to specify a truststore for a client at run time other  
than using:


System.setProperty("javax.net.ssl.trustStore", "...");

you can't use the above in a multi client environment as they all  
overwrite each others' truststore details.


is there any way to tell stub._getServiceClient() to use a specific  
truststore without using System properties?


thanks,

Alistair


--
mov eax,1
mov ebx,0
int 80h

minOccurs="0" attribute and .NET

[Mauro Molinari]

Hello to all!

I recently experienced a problem trying to do the following:
- expose a POJO as a webservice, generating the WSDL with Axis2 Java2WSDL
- create a client with .NET WebService Studio 2.0

Suppose my Java methods signatures are these:

public Integer a(String, Integer)
public String b(Integer, String)
(please note: the actual methods declare to launch some exceptions, too)

Axis2 Java2WSDL adds the minOccurs="0" for each element of each complex 
type, both for the input parameters and for the output parameters.


When generating clients using .NET WebService Studio 2.0, the result is 
the following:
- all the generated C# methods input parameters are doubled, except for 
the string ones: the doubled parameters are booleans whose meaning is: 
"is the previous parameter specified or not?"
- all the generated C# methods return parameters are void, except for 
the string ones


The actual result are clients with methods like these:

void a(string, Integer32, Boolean)
string b(Integer32, Boolean, string)

We could discuss if this is a correct behaviour by .NET WebService 2.0 
or not, however, my question is this: why does Axis2 Java2WSDL specify 
minOccurs="0" for each parameter? What I would expect is that every 
method parameter (either input ones or return ones) IS mandatory.


Does Axis2 specify minOccurs="0" with the meaning of: "it may be null"? 
Or are there other specific reasons?

Is there a way to customize this aspect of the WSDL generation?

Thanks in advance for any reply.

--
Mauro Molinari
Software Developer
[EMAIL PROTECTED]

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

Which style am I using?

[Dimitris Mouchritsas]

Hi everyone,
I'm kind of new in web services so I need your help once again.
Say I have the following wsdl:


http://www.example.org";>

Blah blah


  http://www.example.org";
attributeFormDefault="qualified" elementFormDefault="qualified">

  

  

  
   
 
  
  

  

   



so I send and receive messages like (minus the soap envelope):

  1


Which style am I using? I think I'm using document/wrapped but am I right?
I've read the
developer works article on this but I'm not certain yet.  Thanks in advance.
-- 
Dimitris Mouchritsas
Computer Services

Re: How to use WSDL to validate soap message?

[Eran Chinthaka]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Please read a doc on data binding and please

1. do not cross post
2. do not use dev-list to ask non-architectural questions.

Chinthaka

Wenshuang Sun wrote:
> Hi,
> 
> How to use WSDL to validate the soap message in axis2, is the API
> about the function  provided?
> 
> Thanks.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHHZ85jON2uBzUhh8RAtRGAJ9cQZIkS6+HQVieeCgzRFoPU4tuzACgldY2
Q9NuWsytX9oEaM19DTE5u/w=
=y11O
-END PGP SIGNATURE-

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