[Axis2-1.4.1 Versus 1.5]

2009-09-03 Thread Vaibhav Arya
Hi All,

 

Currently I'm working with apache axis2 - 1.4.1. As we all know axis2 - 1.5
has been released, here I'm curious to know, what improvements have been
done in axis2-1.5?

 

Should I migrate to axis2 -1.5?

 

Thanks a lot...

 

Regards,

Vaibhav Kumar Arya

ASE, Gorgaon

 



===
Private, Confidential and Privileged. This e-mail and any files and attachments 
transmitted with it are confidential and/or privileged. They are intended 
solely for the use of the intended recipient. The content of this e-mail and 
any file or attachment transmitted with it may have been changed or altered 
without the consent of the author. If you are not the intended recipient, 
please note that any review, dissemination, disclosure, alteration, printing, 
circulation or Transmission of this e-mail and/or any file or attachment 
transmitted with it, is prohibited and may be unlawful. If you have received 
this e-mail or any file or attachment transmitted with it in error please 
notify OTS Solutions at i...@otssolutions.com
===


RE: MTOM support causing problem

2009-09-03 Thread Sanjay Gupta
Hi Chinmoy,
The problem happens  in methods that have nothing to do with mtom. They are 
simple service methods that return an objects array. I did putting debugging 
messages to make sure that service method worked fine.
Thanks
Sanjay

From: Chinmoy Chakraborty [mailto:cch...@gmail.com]
Sent: Wednesday, September 02, 2009 10:45 PM
To: axis-user@ws.apache.org
Subject: Re: MTOM support causing problem

Are you sure that your service method is working fine? are you sending 
attachemnt or receiving attachment or both?


On Thu, Sep 3, 2009 at 11:01 AM, Sanjay Gupta 
sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote:
Hi,
I enabled mtom support in axis2.xml and it's causing some problem in an already 
working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk 1.6.0.14. I 
have my axis2 pojo based services deployed in tomcat as an app. In the same 
tomcat I have a grails app that has some grails services exposed as web 
services using grails axis2 plugin. From my axis2 app I calls grails/axis2 
services(using wsdl2java generated stub)  internally and it worked fine without 
any issues till I enabled mtom support. Now it intermittently gives me the 
following error. I have tracked down the problem in the axis2 layer. Don't know 
if it is grails/axis2 plugin or axis2 app.  I see that everything is fine just 
before the return in grails service. I would really appreciate any help on this.
Thanks
Sanjay

2009-09-02 22:25:21,451 [http-8443-31] INFO  
org.apache.axis2.builder.BuilderUtil  - 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:251)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
   at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105)
   at 
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
   at 
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
   at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
   at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
   at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437)
   at 
com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216)
   at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown Source)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)
   at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
   at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
   at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
   at 
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
   at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at 

RE: [Axis2-1.4.1 Versus 1.5]

2009-09-03 Thread Sanjay Gupta
I also see this error in one the the tomcat log file.

Sep 2, 2009 11:34:53 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet axis2 threw exception
java.lang.NullPointerException
at 
org.apache.catalina.connector.Request.parseParameters(Request.java:2446)
at 
org.apache.catalina.connector.Request.getParameterNames(Request.java:1082)
at 
org.apache.catalina.connector.RequestFacade.getParameterNames(RequestFacade.java:371)
at 
javax.servlet.ServletRequestWrapper.getParameterNames(ServletRequestWrapper.java:178)
at 
org.springframework.web.multipart.support.DefaultMultipartHttpServletRequest.getParameterNames(DefaultMultipartHttpServletRequest.java:69)
at 
org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.tryMultipartParams(DefaultUrlMappingInfo.java:236)
at 
org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.checkDispatchAction(DefaultUrlMappingInfo.java:210)
at 
org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.getActionName(DefaultUrlMappingInfo.java:168)
at 
org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.populateParamsForMapping(DefaultUrlMappingInfo.java:138)
at 
org.codehaus.groovy.grails.web.mapping.DefaultUrlMappingInfo.configure(DefaultUrlMappingInfo.java:155)
at 
org.codehaus.groovy.grails.web.mapping.filter.UrlMappingsFilter.doFilterInternal(UrlMappingsFilter.java:112)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.codehaus.groovy.grails.web.sitemesh.GrailsPageFilter.parsePage(GrailsPageFilter.java:122)
at 
org.codehaus.groovy.grails.web.sitemesh.GrailsPageFilter.doFilter(GrailsPageFilter.java:85)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378)
at 
org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
at 
org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at 
org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101)
at 
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at 
org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105)
at 
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at 
org.springframework.security.ui.rememberme.RememberMeProcessingFilter.doFilterHttp(RememberMeProcessingFilter.java:109)
at 
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at 
org.springframework.security.wrapper.SecurityContextHolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareRequestFilter.java:91)
at 
org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)
at 
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:390)
at 
org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:277)
at 
org.codehaus.groovy.grails.plugins.springsecurity.GrailsAuthenticationProcessingFilter.super$3$doFilterHttp(GrailsAuthenticationProcessingFilter.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at 

Re: MTOM support causing problem

2009-09-03 Thread Chinmoy Chakraborty
Try complex type array instead of object array as return type...for quick
check you can use string array..



On Thu, Sep 3, 2009 at 12:05 PM, Sanjay Gupta
sanjay.gu...@billwiseinc.comwrote:

  Hi Chinmoy,

 The problem happens  in methods that have nothing to do with mtom. They are
 simple service methods that return an objects array. I did putting debugging
 messages to make sure that service method worked fine.

 Thanks

 Sanjay



 *From:* Chinmoy Chakraborty [mailto:cch...@gmail.com]
 *Sent:* Wednesday, September 02, 2009 10:45 PM
 *To:* axis-user@ws.apache.org
 *Subject:* Re: MTOM support causing problem



 Are you sure that your service method is working fine? are you sending
 attachemnt or receiving attachment or both?





 On Thu, Sep 3, 2009 at 11:01 AM, Sanjay Gupta 
 sanjay.gu...@billwiseinc.com wrote:

 Hi,
 I enabled mtom support in axis2.xml and it's causing some problem in an
 already working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk
 1.6.0.14. I have my axis2 pojo based services deployed in tomcat as an app.
 In the same tomcat I have a grails app that has some grails services exposed
 as web services using grails axis2 plugin. From my axis2 app I calls
 grails/axis2 services(using wsdl2java generated stub)  internally and it
 worked fine without any issues till I enabled mtom support. Now it
 intermittently gives me the following error. I have tracked down the problem
 in the axis2 layer. Don't know if it is grails/axis2 plugin or axis2 app.  I
 see that everything is fine just before the return in grails service. I
 would really appreciate any help on this.
 Thanks
 Sanjay

 2009-09-02 22:25:21,451 [http-8443-31] INFO
  org.apache.axis2.builder.BuilderUtil  - 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:251)
at
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
at
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
at
 org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
at
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
at
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105)
at
 org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
at
 org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
 com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437)
at
 com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216)
at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown
 Source)
at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
 org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)
at
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
at
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
at
 org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
 

Copying received large web service response objects to file system

2009-09-03 Thread Anand Navale
Hi,

We are using Axis2 1.4 (on JRE 5 runtime) as web service client for our 
application. One of the web services requires handling massive objects in the 
response. Right now we are getting out of memory error whenever we receive 
large web service response. Modifying the web service or increasing the JVM 
heap size is not an option for us. Does Axis2 web service client framework 
provide any mechanism for copying the received web service response to the file 
system and not build the entire response object in memory. Then in our 
application we could read the response from the file.

Thanks in advance,
Anand Navale.


Re: Copying received large web service response objects to file system

2009-09-03 Thread Amila Suriarachchi
On Thu, Sep 3, 2009 at 1:21 PM, Anand Navale naan...@novell.com wrote:

  Hi,

 We are using Axis2 1.4 (on JRE 5 runtime) as web service client for our
 application. One of the web services requires handling massive objects in
 the response. Right now we are getting out of memory error whenever we
 receive large web service response. Modifying the web service or increasing
 the JVM heap size is not an option for us. Does Axis2 web service client
 framework provide any mechanism for copying the received web service
 response to the file system and not build the entire response object in
 memory. Then in our application we could read the response from the file.

yes. then you can not use data binding.

you can use a ServiceClient to send and receive OM Elements. Axiom works in
pull parsing. i.e it does not build the envelope until you call for. Once
you have the OMElement you can get the xml stream reader and write it to the
file system.

thanks,
Amila.


Thanks in advance,
 Anand Navale.



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/


unsubscribe

2009-09-03 Thread trevor.baden
unsubscribe



unsubscribe

2009-09-03 Thread D.H.T.M.Gameren
unsubscribe

==
The information transmitted via this e-mail is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, 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 received this in error, 
please contact the sender and delete the material from any computer.



unsubscribe

2009-09-03 Thread Sarathi Balasundaram



unsubscribe

2009-09-03 Thread Sasikumar.Natarajan

 



This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply 
e-mail and destroy all copies of the original message. 
Any unauthorized review, use, disclosure, dissemination, forwarding, printing 
or copying of this email or any action taken in reliance on this e-mail is 
strictly prohibited and may be unlawful.

Re: unsubscribe

2009-09-03 Thread Larry Meadors
axis-user-unsubscr...@ws.apache.org

On Thu, Sep 3, 2009 at 4:22 AM, sasikumar.natara...@cognizant.com wrote:


 This e-mail and any files transmitted with it are for the sole use of the
 intended recipient(s) and may contain confidential and privileged
 information.
 If you are not the intended recipient, please contact the sender by reply
 e-mail and destroy all copies of the original message.
 Any unauthorized review, use, disclosure, dissemination, forwarding,
 printing or copying of this email or any action taken in reliance on this
 e-mail is strictly prohibited and may be unlawful.



problem in generating a oneway web service from a java class in Axis 1.4

2009-09-03 Thread Akitoshi Yoshida
Hi,
When you deploy a service that has a void return type in Axis 1.4, I
noticed that its WSDL generator does not generate a oneway MEP WSDL
(i.e., having only the input element) but a normal request-response
MEP WSDL (i.e., having both the input and output elements). And when
the call is invoked, the service returns HTTP 200 with an empty SOAP
message instead of an HTTP 202 with no content.

I found a related issue AXIS-2538 in JIRA,  which talks about the
oneway issue for creating a java stub class from a oneway WSDL., but
didn't find the ticket for the other direction.

I modified the generator so that you get the correct oneway MEP WSDL
at the WSDL URL (http://...wsdl) and you get the correct HTTP 202
response when the call is successful.

other Axis 1.4 users might be interested in this oneway handling.


RE: Axis 2 Client on Mobile Devices

2009-09-03 Thread Adam Elnagger
Hey Demetris,
Thanks for the response. Though it is not the response I was hoping for, it
does answer my question. I wonder why there seems to be so little support
for reliable web services in the mobile industry. Regardless, this is key
information to have.

Thanks for your time!
Adam Elnagger

-Original Message-
From: Demetris [mailto:demet...@ece.neu.edu] 
Sent: Thursday, September 03, 2009 12:30 AM
To: axis-user@ws.apache.org
Subject: Re: Axis 2 Client on Mobile Devices


Hey Adam,

so what I have found out is that primarily the stacks of Axis/Axis2 
or CXF are not geared towards
the mobile device industry (under J2ME that is) either on the client or 
on the server side. I was able to
build efficient SOAP-based WS clients using the kSOAP2 API, however, 
using the Jalimo (GNU
classpath for Linux Java that is pretty close to J2SE) I was able to run 
Axis and Axis2 as clients
and as servers (bundles in OSGi containers). The problem I ran into when 
I was running these as
servers was that the XML parsers used by Jalimo (which is a similar 
issue I had with J2ME) are
not compatible with whatever WSDL or SOAP messages the client side was 
generating.
Please keep me posted of any other findings you may have - I have a 
few more myself that
had the same fate as the ones above so I figured it makes no sense to 
repeat them here.

Good luck

D G wrote:
 I have been pleading for help on this for months man and I didn't even 
 get back a hello. Hopefully you will have better luck. Once I get to a 
 laptop I will send you what I found so far.

 Thanks



 On Sep 2, 2009, at 11:28 AM, Adam Elnagger 
 aelnag...@lampreynetworks.com wrote:

 Hello,



 Is there any support/testing for building and running Axis 2 clients 
 on Mobile devices running Android, Windows Mobile, or Symbian? I am 
 researching using web service stacks on mobile devices which support 
 in particular WS-ReliableMessaging and MTOM.



 Thanks,

 Adam Elnagger






unsubscribe

2009-09-03 Thread Steve Buster



_
Windows Live: Keep your friends up to date with what you do online.
http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009

Query re Axis2 / ADB client

2009-09-03 Thread Martin Kidby


First of all I apologise for wasting people's time but I am still very
green when it comes to web services and Axis. 

I have been supplied with a WSDL and using WSDL2Java have generated my
client stub. Then I've written my client and all appears OK as I have
successfully tested it against the required remote service. 

However, one part of the service calls for an XML construct such as
this: 
  TAG1 ATTR1=ABC ATTR2=DEF
ATTR3=XYZ 
TAG2VALUE1/TAG2 
  /TAG1 

In the past I have only had to deal with elements such as TAG2 and its
value - no problem. 

I have never had to cater for the TAG1 situation, i.e. where it has
attributes (or are they sub-elements?). 

How and where do I need to define/set ATTR1, ABC, ATTR2, DEF etc. ? 

I have trawled around the internet but cannot seem to find the info I
need - probably because I'm using the wrong terminology. 

Any help at all would be greatly appreciated. 

Thanks in advance

Martin

Cambridge Online Systems Ltd is registered in England and Wales with company 
number 1381717
Registered office: 163 Cambridge Science Park, Milton Road Cambridge CB4 0GP

Disclaimer:
The contents of this e-mail are intended for the named addressee only. It 
contains information which may be confidential and which may also be privileged.
Unless you are the named addressee (or authorised to receive for the addressee) 
you may not copy or use it, or disclose it to anyone else.
If you received it in error please notify us immediately and then destroy it.
_
Cambridge Online Latest News:

Please visit our Website at http://www.cambridgeonline.net 

Axis2 deploymne without Web Admin

2009-09-03 Thread Ziggy
Hi,

Does anyone know how i can deploy the axis2.war onto tomcat without the web
admin pages? I dont want it be accessible via the browser at all. is this
just a configuration change?

Thank


RE: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with anyType in it

2009-09-03 Thread Martin Kidby
Hi.

I may be wide of the mark, but whilst I was researching my problem, I saw an 
article similar to your problem that suggested the use of 'Any' rather than 
'AnyType'

Hope it helps you.


-Original Message-
From: Michel Etienne [mailto:michel.etie...@dryade.net] 
Sent: 03 September 2009 15:47
To: axis-user@ws.apache.org; axis-...@ws.apache.org
Subject: Re: [AXIS2 1.4.1 - Xmlbeans] validating an input parameter with 
anyType in it

Hello

Since I had no answer yet, I repost my question .
Does anybody have an idea ?
Thanks

Best regards
Michel Etienne


Michel Etienne a écrit :
 Hello,
 I have a problem when I try to validate an input parameter with an 
 AnyType member

 I use Xmlbeans and I get this error on the server side (I made a 
 sample program to show the problem)

 2009-07-06 16:23:16,109 [HttpConnection-8080-1]  
 WARNServer -  Invalid object 
 demo.dryade.soap.impl.RequestDocumentImpl
  error: cvc-elt.4.2: Invalid xsi:type qname: 'typ:SpecificType' in 
 element RequestPart
 2009-07-06 16:23:16,125 [HttpConnection-8080-1]  
 WARNServer - Invalid content =
 soap:Request xmlns:soap=http://soap.dryade.demo; 
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
  RequestPart
typ:element6 xmlns:typ=http://types.dryade.demo;1/typ:element6
typ:element7 xmlns:typ=http://types.dryade.demo;test/typ:element7
typ:element8 xsi:type=typ:SpecificType 
 xmlns:typ=http://types.dryade.demo; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  typ:element4true/typ:element4
  typ:element5any test/typ:element5
/typ:element8
  /RequestPart
 /soap:Request

 if the server produce an output with the same AnyType , it validate 
 correctly :
 in an input-output transaction

 2009-07-06 16:23:16,125 [HttpConnection-8080-1]  INFO Server -  
 Valid object demo.dryade.soap.impl.RequestResponseDocumentImpl

 in an ouput-only transaction

 2009-07-06 16:23:16,250 [HttpConnection-8080-2]  INFO Server -  
 Valid object demo.dryade.soap.impl.NotifyDocumentImpl

 on the client side, the structures are always valid.

 I send you the entire code I used for this exemple; it is made with 
 AXIS2 1.4.1 on Windows XP platform with Java 1.6

 (I can send the entire project archive if necessary)

 Thanks for help

 Best regards
 Michel Etienne

Cambridge Online Systems Ltd is registered in England and Wales with company 
number 1381717
Registered office: 163 Cambridge Science Park, Milton Road Cambridge CB4 0GP

Disclaimer:
The contents of this e-mail are intended for the named addressee only. It 
contains information which may be confidential and which may also be privileged.
Unless you are the named addressee (or authorised to receive for the addressee) 
you may not copy or use it, or disclose it to anyone else.
If you received it in error please notify us immediately and then destroy it.
_
Cambridge Online Latest News:

Please visit our Website at http://www.cambridgeonline.net 

Re: Axis2 deploymne without Web Admin

2009-09-03 Thread Deepal jayasinghe
There is no configuration change, just delete the web-app and edit the
web.xml to remove the admin servlet.

Thanks,
Deepal
 Hi,

 Does anyone know how i can deploy the axis2.war onto tomcat without
 the web admin pages? I dont want it be accessible via the browser at
 all. is this just a configuration change?

 Thank


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org



Re: Axis 2 Client on Mobile Devices

2009-09-03 Thread Demetris


Hey Adam,

   at least hosting services on mobile devices I think the reason is 
because mobile devices are still
considered 'client' portals to services rather than servers. I am 
working on peer-to-peer architectures
connecting services across mobile devices and that's where my server 
issue comes from ;)


   Certainly stay in touch and let me know what else you find your end.

Thanks

Adam Elnagger wrote:

Hey Demetris,
Thanks for the response. Though it is not the response I was hoping for, it
does answer my question. I wonder why there seems to be so little support
for reliable web services in the mobile industry. Regardless, this is key
information to have.

Thanks for your time!
Adam Elnagger

-Original Message-
From: Demetris [mailto:demet...@ece.neu.edu] 
Sent: Thursday, September 03, 2009 12:30 AM

To: axis-user@ws.apache.org
Subject: Re: Axis 2 Client on Mobile Devices


Hey Adam,

so what I have found out is that primarily the stacks of Axis/Axis2 
or CXF are not geared towards
the mobile device industry (under J2ME that is) either on the client or 
on the server side. I was able to
build efficient SOAP-based WS clients using the kSOAP2 API, however, 
using the Jalimo (GNU
classpath for Linux Java that is pretty close to J2SE) I was able to run 
Axis and Axis2 as clients
and as servers (bundles in OSGi containers). The problem I ran into when 
I was running these as
servers was that the XML parsers used by Jalimo (which is a similar 
issue I had with J2ME) are
not compatible with whatever WSDL or SOAP messages the client side was 
generating.
Please keep me posted of any other findings you may have - I have a 
few more myself that
had the same fate as the ones above so I figured it makes no sense to 
repeat them here.


Good luck

D G wrote:
  
I have been pleading for help on this for months man and I didn't even 
get back a hello. Hopefully you will have better luck. Once I get to a 
laptop I will send you what I found so far.


Thanks



On Sep 2, 2009, at 11:28 AM, Adam Elnagger 
aelnag...@lampreynetworks.com wrote:




Hello,



Is there any support/testing for building and running Axis 2 clients 
on Mobile devices running Android, Windows Mobile, or Symbian? I am 
researching using web service stacks on mobile devices which support 
in particular WS-ReliableMessaging and MTOM.




Thanks,

Adam Elnagger


  


  




Re: Axis 2 Client on Mobile Devices

2009-09-03 Thread Danny García Hernández
Hi, i 'am running Axis2 client into Windows Mobile using J9 JVM and all 
is working perfect (MTOM included).


I don´t have maked any test with server stack into mobile device but you 
are saying appear very interesting.


Can (oe want) you explain any more?

Regards
Danny



Demetris escribió:


Hey Adam,

   at least hosting services on mobile devices I think the reason is 
because mobile devices are still
considered 'client' portals to services rather than servers. I am 
working on peer-to-peer architectures
connecting services across mobile devices and that's where my server 
issue comes from ;)


   Certainly stay in touch and let me know what else you find your end.

Thanks

Adam Elnagger wrote:

Hey Demetris,
Thanks for the response. Though it is not the response I was hoping 
for, it
does answer my question. I wonder why there seems to be so little 
support
for reliable web services in the mobile industry. Regardless, this is 
key

information to have.

Thanks for your time!
Adam Elnagger

-Original Message-
From: Demetris [mailto:demet...@ece.neu.edu] Sent: Thursday, 
September 03, 2009 12:30 AM

To: axis-user@ws.apache.org
Subject: Re: Axis 2 Client on Mobile Devices


Hey Adam,

so what I have found out is that primarily the stacks of 
Axis/Axis2 or CXF are not geared towards
the mobile device industry (under J2ME that is) either on the client 
or on the server side. I was able to
build efficient SOAP-based WS clients using the kSOAP2 API, however, 
using the Jalimo (GNU
classpath for Linux Java that is pretty close to J2SE) I was able to 
run Axis and Axis2 as clients
and as servers (bundles in OSGi containers). The problem I ran into 
when I was running these as
servers was that the XML parsers used by Jalimo (which is a similar 
issue I had with J2ME) are
not compatible with whatever WSDL or SOAP messages the client side 
was generating.
Please keep me posted of any other findings you may have - I have 
a few more myself that
had the same fate as the ones above so I figured it makes no sense to 
repeat them here.


Good luck

D G wrote:
 
I have been pleading for help on this for months man and I didn't 
even get back a hello. Hopefully you will have better luck. Once I 
get to a laptop I will send you what I found so far.


Thanks



On Sep 2, 2009, at 11:28 AM, Adam Elnagger 
aelnag...@lampreynetworks.com wrote:


   

Hello,



Is there any support/testing for building and running Axis 2 
clients on Mobile devices running Android, Windows Mobile, or 
Symbian? I am researching using web service stacks on mobile 
devices which support in particular WS-ReliableMessaging and MTOM.




Thanks,

Adam Elnagger


  


  







Re: Axis2 deploymne without Web Admin

2009-09-03 Thread Ziggy
Hi,

Which is the webapp?

Here is the directory structure i have

webapps
- axis2
-- axis2-web
-- META-INF
-- WEB-INF
- docs
- examples
--
--
- ROOT

Which one do i delete? and what change do i make in web.xml

On Thu, Sep 3, 2009 at 4:20 PM, Deepal jayasinghe deep...@gmail.com wrote:

 There is no configuration change, just delete the web-app and edit the
 web.xml to remove the admin servlet.

 Thanks,
 Deepal
  Hi,
 
  Does anyone know how i can deploy the axis2.war onto tomcat without
  the web admin pages? I dont want it be accessible via the browser at
  all. is this just a configuration change?
 
  Thank


 --
 Thank you!


 http://blogs.deepal.org
 http://deepal.org




unsubscribe

2009-09-03 Thread Clement



_
Tchattez en direct en en vidéo avec vos amis !  
http://www.windowslive.fr/messenger/

RE: MTOM support causing problem

2009-09-03 Thread Sanjay Gupta
My problem was fixed after I changed enableMTOM to optional from true in 
axis2.xml.

From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com]
Sent: Wednesday, September 02, 2009 11:36 PM
To: axis-user@ws.apache.org
Subject: RE: MTOM support causing problem

Hi Chinmoy,
The problem happens  in methods that have nothing to do with mtom. They are 
simple service methods that return an objects array. I did putting debugging 
messages to make sure that service method worked fine.
Thanks
Sanjay

From: Chinmoy Chakraborty [mailto:cch...@gmail.com]
Sent: Wednesday, September 02, 2009 10:45 PM
To: axis-user@ws.apache.org
Subject: Re: MTOM support causing problem

Are you sure that your service method is working fine? are you sending 
attachemnt or receiving attachment or both?


On Thu, Sep 3, 2009 at 11:01 AM, Sanjay Gupta 
sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote:
Hi,
I enabled mtom support in axis2.xml and it's causing some problem in an already 
working application. I am using axis2 1.4.1, tomcat 6.0.18 and jdk 1.6.0.14. I 
have my axis2 pojo based services deployed in tomcat as an app. In the same 
tomcat I have a grails app that has some grails services exposed as web 
services using grails axis2 plugin. From my axis2 app I calls grails/axis2 
services(using wsdl2java generated stub)  internally and it worked fine without 
any issues till I enabled mtom support. Now it intermittently gives me the 
following error. I have tracked down the problem in the axis2 layer. Don't know 
if it is grails/axis2 plugin or axis2 app.  I see that everything is fine just 
before the return in grails service. I would really appreciate any help on this.
Thanks
Sanjay

2009-09-02 22:25:21,451 [http-8443-31] INFO  
org.apache.axis2.builder.BuilderUtil  - 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:251)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:209)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createNextOMElement(StAXSOAPModelBuilder.java:191)
   at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:172)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)
   at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:105)
   at 
org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:677)
   at 
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:182)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
   at 
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
   at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
   at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
   at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
   at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
com.bwse.wsclient.service.ConnectSmStub.findTransactions(ConnectSmStub.java:1437)
   at 
com.bwse.ws.ConnectSmService.findTransactions(ConnectSmService.java:1216)
   at sun.reflect.GeneratedMethodAccessor2230.invoke(Unknown Source)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)
   at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
   at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
   at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
   at 
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
   at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 

Re: Axis 2 Client on Mobile Devices

2009-09-03 Thread Demetris


Hey Danny,

that's really good info - I was not able to run client code on the Sun 
J2ME successfully. Only with the Jalimo
I mentioned. I know also PocketJava and Sprint's Titan are Windows 
Mobile based and the latter utilizes
OSGi containers. I am running all this on top of Linux for the Nokia 
N800 device.


If you are successful on your end running server-side stack onto the 
mobile device can you please let us know?

That would be super.

Take care

Danny García Hernández wrote:
Hi, i 'am running Axis2 client into Windows Mobile using J9 JVM and 
all is working perfect (MTOM included).


I don´t have maked any test with server stack into mobile device but 
you are saying appear very interesting.


Can (oe want) you explain any more?

Regards
Danny



Demetris escribió:


Hey Adam,

   at least hosting services on mobile devices I think the reason is 
because mobile devices are still
considered 'client' portals to services rather than servers. I am 
working on peer-to-peer architectures
connecting services across mobile devices and that's where my server 
issue comes from ;)


   Certainly stay in touch and let me know what else you find your end.

Thanks

Adam Elnagger wrote:

Hey Demetris,
Thanks for the response. Though it is not the response I was hoping 
for, it
does answer my question. I wonder why there seems to be so little 
support
for reliable web services in the mobile industry. Regardless, this 
is key

information to have.

Thanks for your time!
Adam Elnagger

-Original Message-
From: Demetris [mailto:demet...@ece.neu.edu] Sent: Thursday, 
September 03, 2009 12:30 AM

To: axis-user@ws.apache.org
Subject: Re: Axis 2 Client on Mobile Devices


Hey Adam,

so what I have found out is that primarily the stacks of 
Axis/Axis2 or CXF are not geared towards
the mobile device industry (under J2ME that is) either on the client 
or on the server side. I was able to
build efficient SOAP-based WS clients using the kSOAP2 API, however, 
using the Jalimo (GNU
classpath for Linux Java that is pretty close to J2SE) I was able to 
run Axis and Axis2 as clients
and as servers (bundles in OSGi containers). The problem I ran into 
when I was running these as
servers was that the XML parsers used by Jalimo (which is a similar 
issue I had with J2ME) are
not compatible with whatever WSDL or SOAP messages the client side 
was generating.
Please keep me posted of any other findings you may have - I 
have a few more myself that
had the same fate as the ones above so I figured it makes no sense 
to repeat them here.


Good luck

D G wrote:
 
I have been pleading for help on this for months man and I didn't 
even get back a hello. Hopefully you will have better luck. Once I 
get to a laptop I will send you what I found so far.


Thanks



On Sep 2, 2009, at 11:28 AM, Adam Elnagger 
aelnag...@lampreynetworks.com wrote:


  

Hello,



Is there any support/testing for building and running Axis 2 
clients on Mobile devices running Android, Windows Mobile, or 
Symbian? I am researching using web service stacks on mobile 
devices which support in particular WS-ReliableMessaging and MTOM.




Thanks,

Adam Elnagger


  


  










Re: Axis2 deploymne without Web Admin

2009-09-03 Thread Deepal Jayasinghe
I thought you were referring to axis2.war

anyway, what you have to do it delete the directory I marked below and
edit the web.xml as I mentioned earlier.

Ziggy wrote:
 Hi,

 Which is the webapp?

 Here is the directory structure i have

 webapps
 - axis2
 -- axis2-web
delete axis2-web
 -- META-INF
 -- WEB-INF
edit the web.xml here
 - docs
 - examples
 --
 --
 - ROOT

 Which one do i delete? and what change do i make in web.xml

 On Thu, Sep 3, 2009 at 4:20 PM, Deepal jayasinghe deep...@gmail.com
 mailto:deep...@gmail.com wrote:

 There is no configuration change, just delete the web-app and edit the
 web.xml to remove the admin servlet.

 Thanks,
 Deepal
  Hi,
 
  Does anyone know how i can deploy the axis2.war onto tomcat without
  the web admin pages? I dont want it be accessible via the browser at
  all. is this just a configuration change?
 
  Thank


 --
 Thank you!


 http://blogs.deepal.org
 http://deepal.org



-- 
Thank you!


http://blogs.deepal.org
http://deepal.org



Re: Copying received large web service response objects to file system

2009-09-03 Thread Anand Navale
Thanks Amila. The suggestion is really useful. Would also like to know if there 
is any recommended approach when dealing with large web service response 
objects using Axis2 as web service client. 
 
Thanks
Anand Navale


 Amila Suriarachchi amilasuriarach...@gmail.com 9/3/2009 1:34 PM 


On Thu, Sep 3, 2009 at 1:21 PM, Anand Navale naan...@novell.com wrote:


Hi,

We are using Axis2 1.4 (on JRE 5 runtime) as web service client for our 
application. One of the web services requires handling massive objects in the 
response. Right now we are getting out of memory error whenever we receive 
large web service response. Modifying the web service or increasing the JVM 
heap size is not an option for us. Does Axis2 web service client framework 
provide any mechanism for copying the received web service response to the file 
system and not build the entire response object in memory. Then in our 
application we could read the response from the file.

yes. then you can not use data binding.

you can use a ServiceClient to send and receive OM Elements. Axiom works in 
pull parsing. i.e it does not build the envelope until you call for. Once you 
have the OMElement you can get the xml stream reader and write it to the file 
system.

thanks,
Amila.




Thanks in advance,
Anand Navale.



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/