echo_rest and DELETE http_method

2009-11-20 Thread Ilia Gilderman
Hi
It looks like the DELETE pieces does not work. I tried with simple_axis2_server 
and mod_axis2 modules and echo_rest example. When I'm adding -mDELETE option I 
got internal servers error (500) from httpd. Is it known issue? What can be 
wrong with the sample?

Thanks

Ilia Gilderman, VP Product Development
xeround
4 Derech Hahoresh St.
P.O. Box 12621
Yehud, 56470 Israel
Office:   +972-3-5390617
Mobile: +972-54-4878091
ilia.gilder...@xeround.commailto:ilia.gilder...@xeround.com



Cannot run axis2 client (error 501)

2009-11-20 Thread P.N.


Hello!

When trying to connect to an axis-service (old axis version!) from an 
axis2-client I'm always getting the following error:



org.apache.axis2.AxisFault: Transport error: 501 Error: Not Implemented
at 
org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:295)
at 
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
at 
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)

at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)



What might be the cause for this?
Is it possible to get the full http messages?

Kind regards

Peter



Resuse of configurationcontext ends in out of memory error

2009-11-20 Thread Jens Goldhammer

Hello together,

We are using Axis2 1.4 as ws-client framework in a web application (deployed
in JBOSS) and have encountered a problem after making the
Axis2ConfigurationContext a singleton.

This approach was necessary because creating the configurationcontext needs
a lot of time and we don´t want to do it again and again... This was the
suggestion in a discussion on the mailing list of Axis2
(http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results)

So Iimplemented a static method which provides the configurationContext to
the caller. If the configurationcontext is created one time, we save it in a
static variable and use this in later calls. 

/**
 * reuse the configuration context of AXIS2 because it is expensive to
create a new one every time you create a
 * client stub. For more information look at url:
 *
http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results
 * 
 * @return a valid configuration context for the axis2 stubs
 * @throws AxisFault if creating the configuration context fails.
 */
static synchronized ConfigurationContext getConfigurationContext()
throws AxisFault {
if (configCtx == null) {

ClassLoader tccl =
Thread.currentThread().getContextClassLoader();
try {
// set local ClassLoader
ClassLoader bofModuleClassLoader =
RPlanWebServiceHelper.class.getClassLoader();
   
Thread.currentThread().setContextClassLoader(bofModuleClassLoader);

configCtx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);

} finally {
// restore thread context ClassLoader
Thread.currentThread().setContextClassLoader(tccl);
}
}

return configCtx;
}

The client stubs are created the following way:

ProjectServiceStub projectServiceStub = new
ProjectServiceStub(getConfigurationContext(), projectServiceUrl);
projectServiceStub.UpdateSchedule(updateScheduleType);

After some days we realized that there are very often out of memory errors
in that application. The application is a so called method server which runs
several jobs which are doing a lot of work with the axis2 client.

We analyzed the headdump of the java process and determine that the
axis2configuration instance needs a lot of memory at the time of the out of
memory error. See the attached file for more information. The hashtable
instance of allEndpoints is about 200 Megabyte. 

Please help me to find the problem? Is there a problem how we use the
configuration context or is this a bug in Axis2?

Thanks,
Jens


http://old.nabble.com/file/p26438102/headdump_analysis.html
headdump_analysis.html 
-- 
View this message in context: 
http://old.nabble.com/Resuse-of-configurationcontext-ends-in-out-of-memory-error-tp26438102p26438102.html
Sent from the Axis - User mailing list archive at Nabble.com.



Transport error: 404 Error: Not Found

2009-11-20 Thread Gonzalo Floria
Hello

Im trying to use AXIS's 2 wsdl2Java tool to build the client that will
consume a web service.

I've run the tool and it has generated the required classes (a singel .java
file).
I've added that to a project and many of the jar files under AXIS_HOME/lib
(until the code started building and then running).

Looks like it ready to work, but when I invoke any web service I get this
error:

INFO  [Nov 19 2009 20:55:04]: Unable to sendViaPost to url[http://
host/dir]
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found

(where host/dir have the right values).

The URL is ok, and I can invoke it without problems. Im using SOAPUI with
that same URL and it's working fine.

Where could be the problem?

Any hint will be much appreciated.


Thanks
Gonso
-- 
---
Gonzalo Floría Giráldez


Axis 2: Transport error: 404 Error: Not Found

2009-11-20 Thread gonso75

Hello

Im trying to use AXIS's 2 wsdl2Java tool to build the client that will
consume a web service.

I've run the tool and it has generated the required classes (a singel .java
file).
I've added that to a project and many of the jar files under AXIS_HOME/lib
(until the code started building and then running).

Looks like it ready to work, but when I invoke any web service I get this
error:

INFO  [Nov 19 2009 20:55:04]: Unable to sendViaPost to
url[http://host/dir]
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found

(where host/dir have the right values).

The URL is ok, and I can invoke it without problems. Im using SOAPUI with
that same URL and it's working fine.

Where could be the problem?

Any hint will be much appreciated.


Thanks
Gonso
-- 
View this message in context: 
http://old.nabble.com/Axis-2%3A-Transport-error%3A-404-Error%3A-Not-Found-tp26438327p26438327.html
Sent from the Axis - User mailing list archive at Nabble.com.



Session already invalidated

2009-11-20 Thread pcsantos

Hi all!

I'm a newbie user of Axis!
I'm running a .jws webservice with Axis 1.4 and Tomcat 4.

Checking tomcat's logfiles, there's an error message that keeps appearing
(see bellow).
I tried to research about it, and all I found was related to the webservice
scope being specificed to session instead of application or so, like:
parameter name=scope value=session/ 
However, I believe this kind of configuration is done with WSDD files...
Since I'm deploying a .jws directly, I have no such descriptor file.
Therefore, how can this error be happening as I'm not defining a specific
scope anywhere (and I assume the default behaviour is being applied, which
is probably not session)? 

Thanks in advance


Error message:
IllegalStateException: getAttribute: Session already invalidated
at
org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:953)
at
org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
at
org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(AxisHTTPSessionListener.java:43)
at
org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(AxisHTTPSessionListener.java:72)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:658)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:607)
at
org.apache.catalina.session.StandardManager.processExpires(StandardManager.java:793)
at
org.apache.catalina.session.StandardManager.run(StandardManager.java:870)
at java.lang.Thread.run(Thread.java:534)

-- 
View this message in context: 
http://old.nabble.com/Session-already-invalidated-tp26440187p26440187.html
Sent from the Axis - User mailing list archive at Nabble.com.



Resuse of configurationcontext ends in out of memory error

2009-11-20 Thread Jens Goldhammer

Hello together,

We are using Axis2 1.4 as ws-client framework in a web application (deployed
in JBOSS) and have encountered a problem after making the
Axis2ConfigurationContext a singleton.

This approach was necessary because creating the configurationcontext needs
a lot of time and we don´t want to do it again and again... This was the
suggestion in a discussion on the mailing list of Axis2
(http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results)

So Iimplemented a static method which provides the configurationContext to
the caller. If the configurationcontext is created one time, we save it in a
static variable and use this in later calls.

/**
 * reuse the configuration context of AXIS2 because it is expensive to
create a new one every time you create a
 * client stub. For more information look at url:
 *
http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results
 *
 * @return a valid configuration context for the axis2 stubs
 * @throws AxisFault if creating the configuration context fails.
 */
static synchronized ConfigurationContext getConfigurationContext()
throws AxisFault {
if (configCtx == null) {

ClassLoader tccl =
Thread.currentThread().getContextClassLoader();
try {
// set local ClassLoader
ClassLoader bofModuleClassLoader =
RPlanWebServiceHelper.class.getClassLoader();
   
Thread.currentThread().setContextClassLoader(bofModuleClassLoader);

configCtx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);

} finally {
// restore thread context ClassLoader
Thread.currentThread().setContextClassLoader(tccl);
}
}

return configCtx;
}

The client stubs are created the following way:

ProjectServiceStub projectServiceStub = new
ProjectServiceStub(getConfigurationContext(), projectServiceUrl);
projectServiceStub.UpdateSchedule(updateScheduleType);

After some days we realized that there are very often out of memory errors
in that application. The application is a so called method server which runs
several jobs which are doing a lot of work with the axis2 client.

We analyzed the headdump of the java process and determine that the
axis2configuration instance needs a lot of memory at the time of the out of
memory error. See the attached file for more information. The hashtable
instance of allEndpoints is about 200 Megabyte.

Please help me to find the problem? Is there a problem how we use the
configuration context or is this a bug in Axis2?

Thanks,
Jens

http://old.nabble.com/file/p26440452/headdump_analysis.html
headdump_analysis.html 

-- 
View this message in context: 
http://old.nabble.com/Resuse-of-configurationcontext-ends-in-out-of-memory-error-tp26440452p26440452.html
Sent from the Axis - User mailing list archive at Nabble.com.



Re: Cannot run axis2 client (error 501)

2009-11-20 Thread Chinmoy Chakraborty
I guess you need to upgrade server side implementation to axis2 also.




On Fri, Nov 20, 2009 at 4:17 PM, P.N. peter.nabbef...@gmx.de wrote:


 Hello!

 When trying to connect to an axis-service (old axis version!) from an
 axis2-client I'm always getting the following error:


 org.apache.axis2.AxisFault: Transport error: 501 Error: Not Implemented
at
 org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:295)
at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
at
 org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)


 What might be the cause for this?
 Is it possible to get the full http messages?

 Kind regards

 Peter




Re: Problems when calling getOMElement

2009-11-20 Thread Amila Suriarachchi
here is a sample code

InDict inDict = new InDict();
ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring = new
ArrayOfKeyValueOfstringstring();
inDict.setInDict(arrayOfKeyValueOfstringstring);

KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 = new
KeyValueOfstringstring_type0[1];
keyValueOfstringstring_type0[0] = new
KeyValueOfstringstring_type0();
keyValueOfstringstring_type0[0].setKey(One Element Array);
keyValueOfstringstring_type0[0].setValue(One Element Array);


arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);

try {
OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
OMAbstractFactory.getOMFactory());
System.out.println(OMElement ==  + omElement.toString());
} catch (ADBException e) {
e.printStackTrace();
}

thanks,
Amila.

On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
andreas.veit...@gmail.comwrote:

 Håkon,

 I think you need to give a bit more context. What version of Axis2?
 What version of Axiom? Code snippet showing what you are trying to do,
 etc.

 Andreas

 2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
  Hi
 
  Anybody did this, go from adb object through a xslt transfomation?
 
  Or having problem getting values out from a XML message when the tyep
  attribute is used for the data type of the element.
 
  cheers, Håkon
 
  2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi
 
  To provide more information, we want to do xslt transformation to our
  generated client side object. And  as far as I know we need the
 OmElement of
  the generated type to do so, but when this don't give back the values
 just
  the XML with no values, there is not much to transform. So we need a
 hint on
  how this can be done.
 
 
 
  cheers, håkon
 
  2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi all,
 
  Any tips on this. stange if it won't work?
 
  2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi all,
 
  I've got a client that calls a ws and using adb as the
  databinding(client side), then we want to get a string representation
 of the
  obejct.  We execute object.getOMElement(), the method returns only the
 xml
  element and not the actual value inside the element. So this element
 here
 
 ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
  programblastp/ns2:BlastOutput_program
 
  Would returns this string
 
  ns2:BlastOutput_program/ns2:BlastOutput_program
 
  We where wondering if it had anything to to with the xsi:type
 attribute?
  Any tips on how to solve this, or another way of getting a string
  representatioon of the object using adb as the databinding?
 
  cheers, Håkon
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 




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


Error while trying to deploy in weblogic 10.3

2009-11-20 Thread Chinmoy Chakraborty
Could you tell me what is the implementation class
for javax.xml.stream.XMLStreamReader that AXIS2 uses? I got some error when
I try to deploy axis2 app in weblogic 10.3. Below is the error:

11...@09:48:17151336 ERROR [[ACTIVE] ExecuteThread: '53' for queue:
'weblogic.kernel.Default (self-tuning)']
labware.web.admin.WSWebFunctionTableBean - Error inside
WebFunctionTableBean.WebFunctionTableBean is
javax.xml.stream.XMLStreamException: Error at Line:12,
token:[OPENTAGBEGIN]Unbalanced ELEMENT got:args expected:return
org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: Error
at Line:12, token:[OPENTAGBEGIN]Unbalanced ELEMENT got:args expected:return
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:307)
at
org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:378)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:447)
at
org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:722)
at
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:655)
at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:602)
at
org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:104)
at
labware.web.ws.connector.WSConnection.getWebFunctions(WSConnection.java:187)
at
labware.web.admin.WSWebFunctionTableBean.init(WSWebFunctionTableBean.java:88)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at java.beans.Beans.instantiate(Beans.java:204)
at java.beans.Beans.instantiate(Beans.java:48)
at
com.sun.faces.config.ManagedBeanFactory.newInstance(ManagedBeanFactory.java:223)
at
com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:282)
at
com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:97)
at ecruiser.util.FacesUtils.resolveVariable(FacesUtils.java:111)
at
ecruiser.component.ClientEventSource.findClassForVar(ClientEventSource.java:571)
at
ecruiser.component.ClientEventSource.isMethodBinding(ClientEventSource.java:533)
at ecruiser.component.ClientEventSource.whenDo(ClientEventSource.java:456)
at
ecruiser.component.ClientEventSource.setBindingAttribute(ClientEventSource.java:738)
at ecruiser.component.ECComponent.setAttribute(ECComponent.java:523)
at
ecruiser.template.parser.JSFDocHandler.setAttributes(JSFDocHandler.java:314)
at
ecruiser.template.parser.JSFDocHandler.startElement(JSFDocHandler.java:186)
at ecruiser.template.parser.Parser.parse(Parser.java:251)
at
ecruiser.template.TemplateViewHandler.createView(TemplateViewHandler.java:228)
at
labware.web.control.WebLIMSViewHandler.createView(WebLIMSViewHandler.java:37)
at
com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:162)
at
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:109)
at javax.faces.component.UICommand.broadcast(UICommand.java:332)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:287)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:401)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at
labware.web.control.CustomCharacterEncodingFilter.doFilter(CustomCharacterEncodingFilter.java:31)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at

Re: Customizing end point location

2009-11-20 Thread Manuel Darveau
Did you found a solution? I am not able to deploy a webservice over an
ssl/https connection for this reason.

A message on this list from Andread Veithen (Nov 5) seems to indicate that
this is broken in 1.5 but will be fixed in 1.6. He refers to AXIS2-4465.

Manuel

On Wed, Sep 23, 2009 at 11:49 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com
 wrote:

 Hi,
 Deos any have any suggesion on how I can accomplish this. I would
 appreciate any help.
 Thanks
 Sanjay

 -Original Message-
 From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com]
 Sent: Monday, September 21, 2009 3:40 PM
 To: axis-user@ws.apache.org
 Subject: Customizing end point location

 Hi,
 I have pojo based servcies deployed in axis2 inside tomcat. The endpoint
 url inside autogenerated wsdl has http in soap12:address location even
 though I am using ssl on port 8443. Is there a way to change the http  to
 https. I am able to get proper port in the url by using hostname parameter
 in transportReceiver tag but not https. The service itself is working fine
 using https on port 8443.
 Sanjay



RE: Customizing end point location

2009-11-20 Thread Sanjay Gupta
No I didn't find any solution. I did see the JIRA as well. It was broken in 
1.4.1 as well.
Sanjay

From: Manuel Darveau [mailto:manueldarv...@gmail.com]
Sent: Friday, November 20, 2009 9:01 AM
To: axis-user@ws.apache.org
Subject: Re: Customizing end point location

Did you found a solution? I am not able to deploy a webservice over an 
ssl/https connection for this reason.

A message on this list from Andread Veithen (Nov 5) seems to indicate that this 
is broken in 1.5 but will be fixed in 1.6. He refers to AXIS2-4465.

Manuel
On Wed, Sep 23, 2009 at 11:49 PM, Sanjay Gupta 
sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com wrote:
Hi,
Deos any have any suggesion on how I can accomplish this. I would appreciate 
any help.
Thanks
Sanjay

-Original Message-
From: Sanjay Gupta 
[mailto:sanjay.gu...@billwiseinc.commailto:sanjay.gu...@billwiseinc.com]
Sent: Monday, September 21, 2009 3:40 PM
To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org
Subject: Customizing end point location

Hi,
I have pojo based servcies deployed in axis2 inside tomcat. The endpoint url 
inside autogenerated wsdl has http in soap12:address location even though I 
am using ssl on port 8443. Is there a way to change the http  to https. I am 
able to get proper port in the url by using hostname parameter in 
transportReceiver tag but not https. The service itself is working fine using 
https on port 8443.
Sanjay



Re: Problems when calling getOMElement

2009-11-20 Thread Andreas Veithen
Does this problem occur with snapshot versions of Axis2 and Axiom?

Andreas

On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
 here is a sample code

 InDict inDict = new InDict();
     ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring = new
 ArrayOfKeyValueOfstringstring();
     inDict.setInDict(arrayOfKeyValueOfstringstring);

     KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 = new
 KeyValueOfstringstring_type0[1];
     keyValueOfstringstring_type0[0] = new
 KeyValueOfstringstring_type0();
     keyValueOfstringstring_type0[0].setKey(One Element Array);
     keyValueOfstringstring_type0[0].setValue(One Element Array);


 arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);

     try {
     OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
 OMAbstractFactory.getOMFactory());
     System.out.println(OMElement ==  + omElement.toString());
     } catch (ADBException e) {
     e.printStackTrace();
     }

 thanks,
 Amila.

 On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen andreas.veit...@gmail.com
 wrote:

 Håkon,

 I think you need to give a bit more context. What version of Axis2?
 What version of Axiom? Code snippet showing what you are trying to do,
 etc.

 Andreas

 2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
  Hi
 
  Anybody did this, go from adb object through a xslt transfomation?
 
  Or having problem getting values out from a XML message when the tyep
  attribute is used for the data type of the element.
 
  cheers, Håkon
 
  2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi
 
  To provide more information, we want to do xslt transformation to our
  generated client side object. And  as far as I know we need the
  OmElement of
  the generated type to do so, but when this don't give back the values
  just
  the XML with no values, there is not much to transform. So we need a
  hint on
  how this can be done.
 
 
 
  cheers, håkon
 
  2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi all,
 
  Any tips on this. stange if it won't work?
 
  2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
 
  Hi all,
 
  I've got a client that calls a ws and using adb as the
  databinding(client side), then we want to get a string representation
  of the
  obejct.  We execute object.getOMElement(), the method returns only
  the xml
  element and not the actual value inside the element. So this element
  here
 
     ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
  programblastp/ns2:BlastOutput_program
 
  Would returns this string
 
  ns2:BlastOutput_program/ns2:BlastOutput_program
 
  We where wondering if it had anything to to with the xsi:type
  attribute?
  Any tips on how to solve this, or another way of getting a string
  representatioon of the object using adb as the databinding?
 
  cheers, Håkon
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 
 
 
  --
  Håkon Sagehaug, Scientific Programmer
  Parallab, Bergen Center for Computational Science (BCCS)
  UNIFOB AS (University of Bergen Research Company)
  hakon.sageh...@bccs.uib.no, phone +47 55584125
 



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



Re: Problems when calling getOMElement

2009-11-20 Thread Håkon Sagehaug
hi

The problem is occurs using 1.4 and axiom 1.2.8. I can extract the values
using the java objects, but when I use the #getOmElement() I get the just
the XML without values, so my thought was the serialization or something
like this.

cheers, Hakon

2009/11/20 Andreas Veithen andreas.veit...@gmail.com

 Does this problem occur with snapshot versions of Axis2 and Axiom?

 Andreas

 On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
 amilasuriarach...@gmail.com wrote:
  here is a sample code
 
  InDict inDict = new InDict();
  ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring = new
  ArrayOfKeyValueOfstringstring();
  inDict.setInDict(arrayOfKeyValueOfstringstring);
 
  KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 = new
  KeyValueOfstringstring_type0[1];
  keyValueOfstringstring_type0[0] = new
  KeyValueOfstringstring_type0();
  keyValueOfstringstring_type0[0].setKey(One Element Array);
  keyValueOfstringstring_type0[0].setValue(One Element Array);
 
 
 
 arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
 
  try {
  OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
  OMAbstractFactory.getOMFactory());
  System.out.println(OMElement ==  + omElement.toString());
  } catch (ADBException e) {
  e.printStackTrace();
  }
 
  thanks,
  Amila.
 
  On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen 
 andreas.veit...@gmail.com
  wrote:
 
  Håkon,
 
  I think you need to give a bit more context. What version of Axis2?
  What version of Axiom? Code snippet showing what you are trying to do,
  etc.
 
  Andreas
 
  2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
   Hi
  
   Anybody did this, go from adb object through a xslt transfomation?
  
   Or having problem getting values out from a XML message when the tyep
   attribute is used for the data type of the element.
  
   cheers, Håkon
  
   2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi
  
   To provide more information, we want to do xslt transformation to our
   generated client side object. And  as far as I know we need the
   OmElement of
   the generated type to do so, but when this don't give back the values
   just
   the XML with no values, there is not much to transform. So we need a
   hint on
   how this can be done.
  
  
  
   cheers, håkon
  
   2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi all,
  
   Any tips on this. stange if it won't work?
  
   2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi all,
  
   I've got a client that calls a ws and using adb as the
   databinding(client side), then we want to get a string
 representation
   of the
   obejct.  We execute object.getOMElement(), the method returns only
   the xml
   element and not the actual value inside the element. So this
 element
   here
  
  ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
   programblastp/ns2:BlastOutput_program
  
   Would returns this string
  
   ns2:BlastOutput_program/ns2:BlastOutput_program
  
   We where wondering if it had anything to to with the xsi:type
   attribute?
   Any tips on how to solve this, or another way of getting a string
   representatioon of the object using adb as the databinding?
  
   cheers, Håkon
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
 
 
 
  --
  Amila Suriarachchi
  WSO2 Inc.
  blog: http://amilachinthaka.blogspot.com/
 




-- 
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125


Re: Problems when calling getOMElement

2009-11-20 Thread Andreas Veithen
Can you test this with a snapshot version?

Andreas

2009/11/20 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
 hi

 The problem is occurs using 1.4 and axiom 1.2.8. I can extract the values
 using the java objects, but when I use the #getOmElement() I get the just
 the XML without values, so my thought was the serialization or something
 like this.

 cheers, Hakon

 2009/11/20 Andreas Veithen andreas.veit...@gmail.com

 Does this problem occur with snapshot versions of Axis2 and Axiom?

 Andreas

 On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
 amilasuriarach...@gmail.com wrote:
  here is a sample code
 
  InDict inDict = new InDict();
      ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring =
  new
  ArrayOfKeyValueOfstringstring();
      inDict.setInDict(arrayOfKeyValueOfstringstring);
 
      KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 =
  new
  KeyValueOfstringstring_type0[1];
      keyValueOfstringstring_type0[0] = new
  KeyValueOfstringstring_type0();
      keyValueOfstringstring_type0[0].setKey(One Element Array);
      keyValueOfstringstring_type0[0].setValue(One Element Array);
 
 
 
  arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
 
      try {
      OMElement omElement = inDict.getOMElement(InDict.MY_QNAME,
  OMAbstractFactory.getOMFactory());
      System.out.println(OMElement ==  + omElement.toString());
      } catch (ADBException e) {
      e.printStackTrace();
      }
 
  thanks,
  Amila.
 
  On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
  andreas.veit...@gmail.com
  wrote:
 
  Håkon,
 
  I think you need to give a bit more context. What version of Axis2?
  What version of Axiom? Code snippet showing what you are trying to do,
  etc.
 
  Andreas
 
  2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
   Hi
  
   Anybody did this, go from adb object through a xslt transfomation?
  
   Or having problem getting values out from a XML message when the tyep
   attribute is used for the data type of the element.
  
   cheers, Håkon
  
   2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi
  
   To provide more information, we want to do xslt transformation to
   our
   generated client side object. And  as far as I know we need the
   OmElement of
   the generated type to do so, but when this don't give back the
   values
   just
   the XML with no values, there is not much to transform. So we need a
   hint on
   how this can be done.
  
  
  
   cheers, håkon
  
   2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi all,
  
   Any tips on this. stange if it won't work?
  
   2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
  
   Hi all,
  
   I've got a client that calls a ws and using adb as the
   databinding(client side), then we want to get a string
   representation
   of the
   obejct.  We execute object.getOMElement(), the method returns only
   the xml
   element and not the actual value inside the element. So this
   element
   here
  
      ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
   programblastp/ns2:BlastOutput_program
  
   Would returns this string
  
   ns2:BlastOutput_program/ns2:BlastOutput_program
  
   We where wondering if it had anything to to with the xsi:type
   attribute?
   Any tips on how to solve this, or another way of getting a string
   representatioon of the object using adb as the databinding?
  
   cheers, Håkon
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
  
  
   --
   Håkon Sagehaug, Scientific Programmer
   Parallab, Bergen Center for Computational Science (BCCS)
   UNIFOB AS (University of Bergen Research Company)
   hakon.sageh...@bccs.uib.no, phone +47 55584125
  
 
 
 
  --
  Amila Suriarachchi
  WSO2 Inc.
  blog: http://amilachinthaka.blogspot.com/
 



 --
 Håkon Sagehaug, Scientific Programmer
 Parallab, Bergen Center for Computational Science (BCCS)
 UNIFOB AS (University of Bergen Research Company)
 hakon.sageh...@bccs.uib.no, phone +47 55584125



Consuming a Service that takes AnyType

2009-11-20 Thread Meenakshisundaram, Pattabiraman
Hi,
I am using the Stub generated by WSDL2Java for a Service that takes AnyType.
The Service is expecting a Xml content ( Not a String/escaped). When I invoke 
the service through XmlSpy, it works. I used TCP Monitor to see the content 
transferred and I see that the tags are not escaped.
Do not know how to do the same thing with the Generated Client. I am passing it 
as a String. It is not working. Moreover, I notice that only the '' is 
escaped. The  goes unescaped.

Could anyone help me resolve this.

Thanks




RE: Consuming a Service that takes AnyType

2009-11-20 Thread McCoy, Daniel (HTSC)
Convert your request string to an OMElement. Let axis handle the
OMElement instead of the string.
 
String XMLRequest =
soapEnvelope+soapBody+lookRequestDoc.xmlText()+soapBodyClose+soapEnvClos
e;

OMElement elem = AXIOMUtil.stringToOM(XMLRequest);

 
Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.com mailto:daniel.mc...@thehartford.com 
 



From: Meenakshisundaram, Pattabiraman
[mailto:pattabiraman.meenakshisunda...@chartisinsurance.com] 
Sent: Friday, November 20, 2009 3:56 PM
To: axis-user@ws.apache.org
Subject: Consuming a Service that takes AnyType


Hi,
I am using the Stub generated by WSDL2Java for a Service that takes
AnyType. 
The Service is expecting a Xml content ( Not a String/escaped). When I
invoke the service through XmlSpy, it works. I used TCP Monitor to see
the content transferred and I see that the tags are not escaped. 
Do not know how to do the same thing with the Generated Client. I am
passing it as a String. It is not working. Moreover, I notice that only
the '' is escaped. The  goes unescaped. 
 
Could anyone help me resolve this.
 
Thanks
 
 

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.



Re: Customizing end point location

2009-11-20 Thread Manuel Darveau
I finally found a hack to fix https support. Note that in my case, I use
axis2 with an embedde jetty. This complicates the solution a bit. If you
want axis to start its own http server skip the first part.

First part: https support in axis2 embedded in jetty server:
What I did:
In the !-- Transport Ins -- section of the axis2.xml, I added this:
transportReceiver name=https class=com.xxx.HTTPSCustomListener
parameter name=port8444/parameter
/transportReceiver

Where HTTPSCustomListener is a custom class that extends axis's
CustomListener:

package com.xxx;
import org.apache.axis2.transport.http.CustomListener;
/**
 * We use this custom listener so the https schema is returned in the
endpoint definition and wsdl if generated
 * correctly with https schema.
 */
public class HTTPSCustomListener extends CustomListener {
public HTTPSCustomListener() {
super( 443, https );
}
}

And in the  !-- Transport Outs -- section, I added:

transportSender name=https

class=org.apache.axis2.transport.http.CommonsHTTPTransportSender
parameter name=PROTOCOLHTTP/1.1/parameter
parameter name=Transfer-Encodingchunked/parameter
/transportSender

In my case, we dont use the default https port so it is overriden in the
transportReceiver config to 8443. If you want the default port 443, you can
remove the parameter name=port8444/parameter.

Also, I did not want to have any http endpoint. I extended the default
AxisServlet to skip the part where it adds the http server:
@Override
public synchronized void init( ServletConfig config ) throws
ServletException {
/*
 * Start of copy from AxisServlet.init(ServletConfig).
 * Review this if we upgrade to axis 1.6
 */
try {
this.servletConfig = config;
ServletContext servletContext =
servletConfig.getServletContext();
this.configContext = (ConfigurationContext)
servletContext.getAttribute( CONFIGURATION_CONTEXT );
if ( configContext == null ) {
configContext = initConfigContext( config );
config.getServletContext().setAttribute(
CONFIGURATION_CONTEXT, configContext );
}
axisConfiguration = configContext.getAxisConfiguration();

ListenerManager listenerManager = new ListenerManager();
listenerManager.init( configContext );

/*
 * Start of hack to remove http endpoints from wsdl
 */
// Add HTTP
//TransportInDescription httpTransportInDescription = new
TransportInDescription( Constants.TRANSPORT_HTTP );
//httpTransportInDescription.setReceiver( this );
//listenerManager.addListener( httpTransportInDescription, true
);
/*
 * End of hack to remove http endpoints from wsdl
 */

listenerManager.start();
ListenerManager.defaultConfigurationContext = configContext;
agent = new ListingAgent( configContext );

initParams();

} catch ( Exception e ) {
throw new ServletException( e );
}

From your axis2.xml file, you can comment the http transport receiver.
However, you need keep the http transportSender. This sucks but it is needed
since CommonsHTTPTransportSender (used by the https transportSender) does a
msgContext.getConfigurationContext().getAxisConfiguration().getTransportOut(Constants.TRANSPORT_HTTP)
with Constants.TRANSPORT_HTTP hardcoded...

End of part one

Part two: Let axis start the https server and keep http end points:
In the !-- Transport Ins -- section:
transportReceiver name=https class=transport.http.SimpleHTTPServer
parameter name=hostname
https://your_server_hostname:443/your_servlet_context/parameter
/transportReceiver

This will start an https server (just a connector actually). You can add
parameter name=port8444/parameter to set a custom internal port. If
you do, set the custom port in the hostname *as it is seen from the client*.
Server and client port could be different if your firewall does some port
forwarding.

Hope it help!

Manuel


On Fri, Nov 20, 2009 at 12:25 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com
 wrote:

  No I didn't find any solution. I did see the JIRA as well. It was broken
 in 1.4.1 as well.

 Sanjay



 *From:* Manuel Darveau [mailto:manueldarv...@gmail.com]
 *Sent:* Friday, November 20, 2009 9:01 AM

 *To:* axis-user@ws.apache.org
 *Subject:* Re: Customizing end point location



 Did you found a solution? I am not able to deploy a webservice over an
 ssl/https connection for this reason.

 A message on this list from Andread Veithen (Nov 5) seems to indicate that
 this is broken in 1.5 but will be fixed in 1.6. He refers to AXIS2-4465.

 Manuel

 On Wed, Sep 23, 2009 at 11:49 PM, Sanjay Gupta 
 sanjay.gu...@billwiseinc.com wrote:

 Hi,
 Deos any have any suggesion on how I can accomplish this. I would
 appreciate any 

deploying Axis under WebLogic

2009-11-20 Thread Vance
Is there documentation somewhere describing how to deploy Axis (1.x) under 
WebLogic 10 ?


  

RE: deploying Axis under WebLogic

2009-11-20 Thread McCoy, Daniel (HTSC)
Check this link out. Pretty comprehensive.
 
http://charithaka.blogspot.com/2008/07/how-to-deploy-apache-axis2-on-web
logic.html
 
Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.com mailto:daniel.mc...@thehartford.com 
 



From: Vance [mailto:aroc...@yahoo.com] 
Sent: Friday, November 20, 2009 6:35 PM
To: axis-user@ws.apache.org
Subject: deploying Axis under WebLogic


Is there documentation somewhere describing how to deploy Axis (1.x)
under WebLogic 10 ?


This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.



RE: deploying Axis under WebLogic

2009-11-20 Thread Vance
Will do, thanks, Dan

--- On Fri, 11/20/09, McCoy, Daniel (HTSC) daniel.mc...@htsco.com wrote:


From: McCoy, Daniel (HTSC) daniel.mc...@htsco.com
Subject: RE: deploying Axis under WebLogic
To: axis-user@ws.apache.org
Date: Friday, November 20, 2009, 6:38 PM



Check this link out. Pretty comprehensive.
 
http://charithaka.blogspot.com/2008/07/how-to-deploy-apache-axis2-on-weblogic.html
 

Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.com
 



From: Vance [mailto:aroc...@yahoo.com] 
Sent: Friday, November 20, 2009 6:35 PM
To: axis-user@ws.apache.org
Subject: deploying Axis under WebLogic







Is there documentation somewhere describing how to deploy Axis (1.x) under 
WebLogic 10 ?

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.




  

RE: deploying Axis under WebLogic

2009-11-20 Thread McCoy, Daniel (HTSC)
Hello,

I have written a custom handler to deal with a soap header with
mustunderstand=1
The problem that I'm haviing is after the server (hosting the service)
starts it deploys the service and upon deployment my customhandler
causes a ClassNotFoundException

Here's a partial stack trace I have changed some names for securioty
purposes.
I am deploying on Weblogic server 10.3

My question(s) is(are) this... What do I need in order for this class to
be found by axis2? 

Should I be packging the handler under an apache package
(org.apache.axis2.handlers)?  

Thanks!
DFM

 org.apache.axis2.deployment.DeploymentException:
com.company.level.utility.MyHandler
 at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:183)
 at
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfi
gBuilder.java:513)
 at
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisCon
figBuilder.java:544)
 at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB
uilder.java:145)
 at
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D
eploymentEngine.java:641)
 at
org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxis
Configurator.java:157)
 at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
t.java:516)
 at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
 at
org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
ava:55)
 at
weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubS
ecurityHelper.java:283)
 at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at
weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityH
elper.java:64)
 at
weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLife
cycleHelper.java:58)
 at
weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper
.java:48)
 at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl
.java:521)
 at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ
letContext.java:1893)
 at
weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(Web
AppServletContext.java:1870)
 at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
rvletContext.java:1790)
 at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
t.java:2999)
 at
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1
371)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
 at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:37)
 at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
 at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
Driver.java:200)
 at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
tenerInvoker.java:117)
 at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
 at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:37)
 at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
 at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModule
sFlow.java:27)
 at
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
635)
 at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:37)
 at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.jav
a:212)
 at
weblogic.application.internal.EarDeployment.activate(EarDeployment.java:
16)
 at
weblogic.application.internal.DeploymentStateChecker.activate(Deployment
StateChecker.java:162)
 at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppCo
ntainerInvoker.java:79)
 at
weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDepl
oyment.java:184)
 at
weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServer
Lifecycle(BasicDeployment.java:361)
 at
weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(Deplo
ymentAdapter.java:51)
 at
weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploymen
tAdapter.java:196)
 at
weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTra
nsition.java:30)
 at
weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps
(ConfiguredDeployments.java:233)
 at
weblogic.management.deploy.internal.ConfiguredDeployments.activate(Confi
guredDeployments.java:169)
 at
weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Configu
redDeployments.java:123)
 at
weblogic.management.deploy.internal.DeploymentServerService.resume(Deplo
ymentServerService.java:173)
 at

RE: deploying Axis under WebLogic

2009-11-20 Thread Martin Gainty

if i can convince you to use maven build environment i would suggest packaging 
all of the classes and service.xml into aar archive and then use the admin 
interface to deploy

in which case you can use the maven-aar plugin
http://ws.apache.org/axis2/tools/1_4/maven-plugins/maven-aar-plugin.html

i would look at the pom.xml in $AXIS2_HOME/modules/samples/version for a 
running pom.xml to use

hth
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 Subject: RE: deploying Axis under WebLogic
 Date: Fri, 20 Nov 2009 18:53:46 -0500
 From: daniel.mc...@htsco.com
 To: axis-user@ws.apache.org
 
 Hello,
 
 I have written a custom handler to deal with a soap header with
 mustunderstand=1
 The problem that I'm haviing is after the server (hosting the service)
 starts it deploys the service and upon deployment my customhandler
 causes a ClassNotFoundException
 
 Here's a partial stack trace I have changed some names for securioty
 purposes.
 I am deploying on Weblogic server 10.3
 
 My question(s) is(are) this... What do I need in order for this class to
 be found by axis2? 
 
 Should I be packging the handler under an apache package
 (org.apache.axis2.handlers)?  
 
 Thanks!
 DFM
 
  org.apache.axis2.deployment.DeploymentException:
 com.company.level.utility.MyHandler
  at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:183)
  at
 org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfi
 gBuilder.java:513)
  at
 org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisCon
 figBuilder.java:544)
  at
 org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB
 uilder.java:145)
  at
 org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D
 eploymentEngine.java:641)
  at
 org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxis
 Configurator.java:157)
  at
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
 t.java:516)
  at
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
  at
 org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
 ava:55)
  at
 weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubS
 ecurityHelper.java:283)
  at
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
 bject.java:321)
  at weblogic.security.service.SecurityManager.runAs(Unknown Source)
  at
 weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityH
 elper.java:64)
  at
 weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLife
 cycleHelper.java:58)
  at
 weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper
 .java:48)
  at
 weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl
 .java:521)
  at
 weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ
 letContext.java:1893)
  at
 weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(Web
 AppServletContext.java:1870)
  at
 weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
 rvletContext.java:1790)
  at
 weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
 t.java:2999)
  at
 weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1
 371)
  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
  at
 weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
 river.java:204)
  at
 weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
 er.java:37)
  at
 weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
 iver.java:60)
  at
 weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
 Driver.java:200)
  at
 weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
 tenerInvoker.java:117)
  at
 weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
 river.java:204)
  at
 weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
 

Re: Error while trying to deploy in weblogic 10.3

2009-11-20 Thread Amila Suriarachchi
Axis2 uses wstx-asl-3.2.4.jar as the stax implementation?

What is the Axis2 version you use? Axis2 1.5 should work properly with web
logic with the web logic stax implementation.

thanks,
Amila.

On Fri, Nov 20, 2009 at 8:51 PM, Chinmoy Chakraborty cch...@gmail.comwrote:

 Could you tell me what is the implementation class
 for javax.xml.stream.XMLStreamReader that AXIS2 uses? I got some error when
 I try to deploy axis2 app in weblogic 10.3. Below is the error:

 11...@09:48:17151336 ERROR [[ACTIVE] ExecuteThread: '53' for queue:
 'weblogic.kernel.Default (self-tuning)']
 labware.web.admin.WSWebFunctionTableBean - Error inside
 WebFunctionTableBean.WebFunctionTableBean is
 javax.xml.stream.XMLStreamException: Error at Line:12,
 token:[OPENTAGBEGIN]Unbalanced ELEMENT got:args expected:return
 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: Error
 at Line:12, token:[OPENTAGBEGIN]Unbalanced ELEMENT got:args expected:return
 at
 org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
  at
 org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:307)
 at
 org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
  at
 org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:378)
 at
 org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:447)
  at
 org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:722)
 at
 org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:655)
  at
 org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:602)
 at
 org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:104)
  at
 labware.web.ws.connector.WSConnection.getWebFunctions(WSConnection.java:187)
 at
 labware.web.admin.WSWebFunctionTableBean.init(WSWebFunctionTableBean.java:88)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
  at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
  at java.lang.Class.newInstance0(Class.java:355)
 at java.lang.Class.newInstance(Class.java:308)
  at java.beans.Beans.instantiate(Beans.java:204)
 at java.beans.Beans.instantiate(Beans.java:48)
  at
 com.sun.faces.config.ManagedBeanFactory.newInstance(ManagedBeanFactory.java:223)
 at
 com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:282)
  at
 com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:97)
 at ecruiser.util.FacesUtils.resolveVariable(FacesUtils.java:111)
  at
 ecruiser.component.ClientEventSource.findClassForVar(ClientEventSource.java:571)
 at
 ecruiser.component.ClientEventSource.isMethodBinding(ClientEventSource.java:533)
  at
 ecruiser.component.ClientEventSource.whenDo(ClientEventSource.java:456)
 at
 ecruiser.component.ClientEventSource.setBindingAttribute(ClientEventSource.java:738)
  at ecruiser.component.ECComponent.setAttribute(ECComponent.java:523)
 at
 ecruiser.template.parser.JSFDocHandler.setAttributes(JSFDocHandler.java:314)
  at
 ecruiser.template.parser.JSFDocHandler.startElement(JSFDocHandler.java:186)
 at ecruiser.template.parser.Parser.parse(Parser.java:251)
  at
 ecruiser.template.TemplateViewHandler.createView(TemplateViewHandler.java:228)
 at
 labware.web.control.WebLIMSViewHandler.createView(WebLIMSViewHandler.java:37)
  at
 com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:162)
 at
 com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:109)
  at javax.faces.component.UICommand.broadcast(UICommand.java:332)
 at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:287)
  at
 javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:401)
 at
 com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
  at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
 at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
  at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
 at
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
  at
 weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
  at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
  at
 labware.web.control.CustomCharacterEncodingFilter.doFilter(CustomCharacterEncodingFilter.java:31)
 at
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
  at
 

Re: Cannot run axis2 client (error 501)

2009-11-20 Thread Amila Suriarachchi
On Fri, Nov 20, 2009 at 4:17 PM, P.N. peter.nabbef...@gmx.de wrote:


 Hello!

 When trying to connect to an axis-service (old axis version!) from an
 axis2-client I'm always getting the following error:


 org.apache.axis2.AxisFault: Transport error: 501 Error: Not Implemented
at
 org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:295)
at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
at
 org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)


 What might be the cause for this?
 Is it possible to get the full http messages?


use[1] to compare the request/response messages with new/old axis versions.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/download.cgi


 Kind regards

 Peter




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


Re: Resuse of configurationcontext ends in out of memory error

2009-11-20 Thread Amila Suriarachchi
Can you try with Axis2 1.5? There was a memory leak in 1.4 and fixed for
1.5.

thanks,
Amila.

On Fri, Nov 20, 2009 at 5:20 PM, Jens Goldhammer 
goldhammer...@googlemail.com wrote:


 Hello together,

 We are using Axis2 1.4 as ws-client framework in a web application
 (deployed
 in JBOSS) and have encountered a problem after making the
 Axis2ConfigurationContext a singleton.

 This approach was necessary because creating the configurationcontext needs
 a lot of time and we don´t want to do it again and again... This was the
 suggestion in a discussion on the mailing list of Axis2
 (
 http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results
 )

 So Iimplemented a static method which provides the configurationContext to
 the caller. If the configurationcontext is created one time, we save it in
 a
 static variable and use this in later calls.

/**
 * reuse the configuration context of AXIS2 because it is expensive to
 create a new one every time you create a
 * client stub. For more information look at url:
 *

 http://markmail.org/message/57afv4yi3t76b7nk#query:+page:1+mid:57afv4yi3t76b7nk+state:results
 *
 * @return a valid configuration context for the axis2 stubs
 * @throws AxisFault if creating the configuration context fails.
 */
static synchronized ConfigurationContext getConfigurationContext()
 throws AxisFault {
if (configCtx == null) {

ClassLoader tccl =
 Thread.currentThread().getContextClassLoader();
try {
// set local ClassLoader
ClassLoader bofModuleClassLoader =
 RPlanWebServiceHelper.class.getClassLoader();

 Thread.currentThread().setContextClassLoader(bofModuleClassLoader);

configCtx =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
 null);

} finally {
// restore thread context ClassLoader
Thread.currentThread().setContextClassLoader(tccl);
}
}

return configCtx;
}

 The client stubs are created the following way:

ProjectServiceStub projectServiceStub = new
 ProjectServiceStub(getConfigurationContext(), projectServiceUrl);
projectServiceStub.UpdateSchedule(updateScheduleType);

 After some days we realized that there are very often out of memory errors
 in that application. The application is a so called method server which
 runs
 several jobs which are doing a lot of work with the axis2 client.

 We analyzed the headdump of the java process and determine that the
 axis2configuration instance needs a lot of memory at the time of the out of
 memory error. See the attached file for more information. The hashtable
 instance of allEndpoints is about 200 Megabyte.

 Please help me to find the problem? Is there a problem how we use the
 configuration context or is this a bug in Axis2?

 Thanks,
 Jens

 http://old.nabble.com/file/p26440452/headdump_analysis.html
 headdump_analysis.html

 --
 View this message in context:
 http://old.nabble.com/Resuse-of-configurationcontext-ends-in-out-of-memory-error-tp26440452p26440452.html
 Sent from the Axis - User mailing list archive at Nabble.com.




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


Re: Axis 2: Transport error: 404 Error: Not Found

2009-11-20 Thread Amila Suriarachchi
On Fri, Nov 20, 2009 at 4:30 PM, gonso75 gonzalo.flo...@gmail.com wrote:


 Hello

 Im trying to use AXIS's 2 wsdl2Java tool to build the client that will
 consume a web service.

 I've run the tool and it has generated the required classes (a singel .java
 file).
 I've added that to a project and many of the jar files under AXIS_HOME/lib
 (until the code started building and then running).

 Looks like it ready to work, but when I invoke any web service I get this
 error:

 INFO  [Nov 19 2009 20:55:04]: Unable to sendViaPost to
 url[http://host/dir]
 org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found

 (where host/dir have the right values).

 The URL is ok, and I can invoke it without problems. Im using SOAPUI with
 that same URL and it's working fine.

 Where could be the problem?


check the request and response messages using tcpmon[1]

[1] http://ws.apache.org/commons/tcpmon/download.cgi

thanks,
Amila.


 Any hint will be much appreciated.


 Thanks
 Gonso
 --
 View this message in context:
 http://old.nabble.com/Axis-2%3A-Transport-error%3A-404-Error%3A-Not-Found-tp26438327p26438327.html
 Sent from the Axis - User mailing list archive at Nabble.com.




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


Re: Invoke with token

2009-11-20 Thread Amila Suriarachchi
On Thu, Nov 19, 2009 at 9:29 PM, suma.subraman...@thomsonreuters.comwrote:

  Hi

 I think I have tried with CXF and not with Axis2. Looks like both are from
 Apache.
 Being a newbie to Java as well as web service, can anyone guide with
 creating java class from the wsdl and the xsd files please?


this may help

Amila.

[1]
http://wso2.org/library/tutorials/reference-guide-axis2-code-generation-parameters-part-1
[2] http://wso2.org/library/2873


 Also is it possible to invoke the web service by adding dynamic token?

 Thanks,
 Suma





 This email was sent to you by Thomson Reuters, the global news and
 information company.
 Any views expressed in this message are those of the individual sender,
 except where the sender specifically states them to be the views of Thomson
 Reuters.




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


Re: Please help for deploying Axis2 on SunOne Server

2009-11-20 Thread Amila Suriarachchi
try using this
tribes-6.0.16.jar and juli-6.0.16.jar

thanks,
Amila.

On Thu, Nov 19, 2009 at 4:53 PM, a f tafa...@gmail.com wrote:

 Dear all,

 I am deploying Axis2 1.5 on SunOne 6.1 sp10 server. But I am having
 problems due to clustering configuration in axis2.xml. Somehow, Axis2 is
 running depending on Apache Tomcat. Since, my service can work without any
 problem on Apache Tomcat server but not on SunOne server. When I deployed it
 on SunOne server it is giving an exception as below:

 javax.servlet.ServletException: WEB2778: Servlet.init() for servlet
 AxisServlet threw exception
 at
 org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
 at
 org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
 at
 org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3553)
 at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:3841)
 at com.iplanet.ias.web.WebModule.start(WebModule.java:260)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
 at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
 at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
 at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
 at
 com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
 at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
 - Root Cause -
 *java.lang.NoClassDefFoundError:
 org/apache/catalina/tribes/ChannelException*
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:169)
 at
 org.apache.axis2.deployment.ClusterBuilder.buildCluster(ClusterBuilder.java:71)
 at
 org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:181)
 at
 org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641)
 at
 org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:157)
 at
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516)
 at
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
 at
 org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
 at
 org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
 at
 org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3553)
 at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:3841)
 at com.iplanet.ias.web.WebModule.start(WebModule.java:260)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
 at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
 at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
 at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
 at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
 at
 com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
 at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
 Caused by: java.lang.ClassNotFoundException:
 org.apache.catalina.tribes.ChannelException
 at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1465)
 at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1301)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
 ... 21 more




 *if I copy catalina-tribes.jar, which contains *ChannelException class,*file 
 from Apache Tomcat to my webapp's lib directory on SunOne, I am getting
 another type of exception as below:
 *
 failure ( 8636): for host 10.1.5.15 trying to GET
 /TESTCM/services/ABCServices22/getUserInformation, service-j2ee reports:
 StandardWrapperValve[AxisServlet]: WEB2792: Servlet.service() for servlet
 AxisServlet threw exception
 java.lang.NullPointerException
 at
 org.apache.axis2.clustering.context.DefaultContextManager.updateContexts(DefaultContextManager.java:81)
 at
 org.apache.axis2.clustering.context.Replicator.replicate(Replicator.java:81)
 at
 org.apache.axis2.receivers.AbstractMessageReceiver.replicateState(AbstractMessageReceiver.java:71)
 at
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:41)
 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.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136)
 at
 

Re: client side handler

2009-11-20 Thread Amila Suriarachchi
On Thu, Nov 19, 2009 at 4:10 PM, Valerio Synclab v.viane...@synclab.itwrote:

  Hi all,



 I am trying to add an handler in my axis2 client and in order to do this I
 followed the “Writing Your Own Axis2 Module” tutorial adapting it for the
 client side.



 The problem is that the handler is not called at all during the web service
 invocation.



 Here is what I have done:



 This is the handler code

 **

 public class Handler extends AbstractHandler implements
 org.apache.axis2.engine.Handler{

 private String name;

 public InvocationResponse invoke(MessageContext arg0)
 throws AxisFault {


 System.out.println(arg0.getEnvelope().toString());

return InvocationResponse.CONTINUE;

 }

 public void revoke(MessageContext msgContext) {


 System.out.println(msgContext.getEnvelope().toString());

 }

 public String getName() {

 return name;

 }

 public void setName(String name) {

 this.name = name;

 }

 }



 This is the module.xml





 ***

 module name=test class=obg.test.client.TestModule 

inflow

 handler name=InFlowTestHandler class=obg.test.client.Handler

 order phase=testPhase /

 /handler

/inflow



outflow

 handler name=OutFlowTestHandler class=obg.test.client.Handler

 order phase=testPhase/

 /handler

/outflow



Outfaultflow

 handler name=FaultOutFlowTestHandler
 class=obg.test.client.Handler

 order phase=testPhase/

 /handler

/Outfaultflow



INfaultflow

 handler name=FaultInFlowTestHandler
 class=obg.test.client.Handler

 order phase=testPhase/

 /handler

/INfaultflow

 /module





 This is what I added into axis.xml for each phaseOrder



 I tried both



 phase name=testPhase

 handler name=InFlowTestHandler
 class=obg.test.client.Handler

   order phase=testPhase /

   /handler

 /phase



 and



  phase name=testPhase/



 Finally I create my stub in this way:



 ConfigurationContext ctx = null;

try {

ctx =
 ConfigurationContextFactory.createConfigurationContextFromFileSystem(……/axis2.xml);

} catch (AxisFault e1) {

// TODO Auto-generated catch
 block

e1.printStackTrace();

}

// TODO Auto-generated method stub

try{

SMSServiceStub stub = new
 SMSServiceStub(ctx, ……?wsdl);

do
stub._getServiceClient().engangeModule(test);

Amila.



 * *

 What else Do I have to do?



 Any suggestions?

 Best regards



 Valerio






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


RE: deploying Axis under WebLogic

2009-11-20 Thread McCoy, Daniel (HTSC)
Thanks for the info but we don't have maven approved for use in our standard 
IDE. I do use maven personally though (as opposed to professionally). 
I found a fairly elegant solution to the issue. Since this custom handler is 
meant to extend Axis2 native functionality I moved the class into the axis2web 
project and refered to it there. Worked like a charm and now I have the 
extension I need. :o)
 
Peace!
DFM
 
Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.com mailto:daniel.mc...@thehartford.com 
 



From: Martin Gainty [mailto:mgai...@hotmail.com] 
Sent: Friday, November 20, 2009 7:37 PM
To: axis-user@ws.apache.org
Subject: RE: deploying Axis under WebLogic


if i can convince you to use maven build environment i would suggest packaging 
all of the classes and service.xml into aar archive and then use the admin 
interface to deploy

in which case you can use the maven-aar plugin
http://ws.apache.org/axis2/tools/1_4/maven-plugins/maven-aar-plugin.html

i would look at the pom.xml in $AXIS2_HOME/modules/samples/version for a 
running pom.xml to use

hth
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité


Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.





 Subject: RE: deploying Axis under WebLogic
 Date: Fri, 20 Nov 2009 18:53:46 -0500
 From: daniel.mc...@htsco.com
 To: axis-user@ws.apache.org
 
 Hello,
 
 I have written a custom handler to deal with a soap header with
 mustunderstand=1
 The problem that I'm haviing is after the server (hosting the service)
 starts it deploys the service and upon deployment my customhandler
 causes a ClassNotFoundException
 
 Here's a partial stack trace I have changed some names for securioty
 purposes.
 I am deploying on Weblogic server 10.3
 
 My question(s) is(are) this... What do I need in order for this class to
 be found by axis2? 
 
 Should I be packging the handler under an apache package
 (org.apache.axis2.handlers)? 
 
 Thanks!
 DFM
 
 org.apache.axis2.deployment.DeploymentException:
 com.company.level.utility.MyHandler
 at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:183)
 at
 org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfi
 gBuilder.java:513)
 at
 org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisCon
 figBuilder.java:544)
 at
 org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB
 uilder.java:145)
 at
 org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D
 eploymentEngine.java:641)
 at
 org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxis
 Configurator.java:157)
 at
 org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
 t.java:516)
 at
 org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
 at
 org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.j
 ava:55)
 at
 weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubS
 ecurityHelper.java:283)
 at
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
 bject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at
 weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityH
 elper.java:64)
 at
 weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLife
 cycleHelper.java:58)
 at
 weblogic.servlet.internal.StubLifecycleHelper.init(StubLifecycleHelper
 .java:48)
 at
 weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl
 .java:521)
 at
 weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ
 letContext.java:1893)
 at
 weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(Web
 AppServletContext.java:1870)
 at
 weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
 rvletContext.java:1790)
 at
 weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
 t.java:2999)
 at
 

Re: WSDL2Axis generation of stub for enumeration type

2009-11-20 Thread Amila Suriarachchi
Please log a jira with your wsdl or a sample wsdl to reproduce the issue.

thanks,
Amila.

On Thu, Nov 19, 2009 at 4:28 AM, techycee chaitra_mat...@yahoo.com wrote:


 I have WSDL which has some enumeration types e.g.
xs:simpleType name=ThresholdType
xs:restriction base=xs:positiveInteger
xs:minInclusive value=5 /
xs:maxInclusive value=750 /
/xs:restriction
/xs:simpleType

xs:simpleType name=EngineIntensityType
xs:restriction base=xs:string
xs:enumeration value=Exact /
xs:enumeration value=Close /
xs:enumeration value=Extensive /
/xs:restriction
/xs:simpleType

 The stub which is generated using Axis2 is having problems. It is trying to
 use

 org.apache.axis2.databinding.utils.ConverterUtil.convertToEngineIntensityType
 which is not a valid method at all.
 How do i eliminate this problem without changing WSDL or the stub? Is there
 a specific way enumeration types should be handled during stub generation?
 Also i am generating it using ADB binding.


 --
 View this message in context:
 http://old.nabble.com/WSDL2Axis-generation-of-stub-for-enumeration-type-tp26417347p26417347.html
 Sent from the Axis - User mailing list archive at Nabble.com.




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


Re: Where are the locator and the service?

2009-11-20 Thread Amila Suriarachchi
On Tue, Nov 17, 2009 at 9:36 PM, P.N. peter.nabbef...@gmx.de wrote:


 Hello!

 I want to create a WS client from wsdl using:
 WSDL2Java -uri file:///C:/Dokumente%20und%20Einstellungen/.../xxx.wsdl -d
 xmlbeans -s -o C:\my-sources

 Though there's a service defined, no locator or service file are created.

 Here's a snippet from my wsdl (guessing this should be the needed part,
 i.e. schemas, service with name):

 ?xml version=1.0 encoding=UTF-8?
 wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
 xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=
 http://www.w3.org/2001/XMLSchema;
 ... 
!--WSDL created by Apache Axis version: 1.3 Built on Oct 05, 2005
 (05:23:37 EDT)--
wsdl:types
...
/wsdl:types
...
wsdl:service name=Export
...
/wsdl:service
 /wsdl:definitions


 I've tested with one wsdl file resulting in a very big (some MB!) java
 source, when using ADB, so I'd prefer using XmlBeans.


try -u option.

thanks,
Amila.


 Kind regards

 Peter Nabbefeld




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


Re: use abstract in complextype

2009-11-20 Thread Amila Suriarachchi
Please create a jira with wsdl if you have this problem with Axis2 1.5.

thanks,
Amila.

On Wed, Nov 18, 2009 at 4:09 PM, Kang, YongLiang ylk...@telenav.cn wrote:

 Hi guys,


 I use axis2 v1.4

 I claim a complex type as abstract in xsd and derived some subclass from
 it. Then I use soapUi for testing.
 In soapUI when I set the subtype and request, everything works fine.
 However I found I can set the field as the 'abstract' type and do the
 request.
 I suppose to received some warning in soapUI. However it reaches my
 axis2 server directly.
 I use wsdl2java to generate code. I checked the generated code and found
 this:

   public static FieldBase parse(javax.xml.stream.XMLStreamReader
 reader) throws java.lang.Exception{
FieldBase object =
null;
...
...
// handle attribute id
java.lang.String tempAttribId =

reader.getAttributeValue(null,id);

   if (tempAttribId!=null){
 java.lang.String content = tempAttribId;

 object.setId(

 org.apache.axis2.databinding.utils.ConverterUtil.convertToLong(tempAttri
 bId));

 Seems the auto generated code declare a null object and set value for it
 directly. No matter how soapUI works. I think it is a bug in axis2
 code-gen part.
 Please correct me if I am wrong about some parts.

 soap with normal subtype:   field xsi:type=v101: fieldText id=1 ...
 soap with abstract subtype:  field id=1 ...

 xsd sample:
  complexType name=fieldBase abstract=true
complexContent
extension base=comm10:tExtensibleElement
sequence
...
complexType name=fieldText
complexContent
extension base=tns: fieldBase 
...

 Best wishes!

 Peter Y.L.Kang
 msn: peter_ylk...@hotmail.com
 Software Engineer, Sever Dept.




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


Re: Apache Axis2 ECCN

2009-11-20 Thread Amila Suriarachchi
2009/11/17 ta-hir...@hitachijoho.com

 Dear Apache Axis2 Users

 Hi, my name is Takayuki Hirano, and I work at Hitachijoho, Japan.
 I am writing to ask you what is the export control classification number
 for the Apache Axis2. (ECCN) I need to know this in order to obtain the
 legal clearance to embedded Apache Axis2 in our test framework.


Any apache project is under the Apache licence which does not require any
legal clearance to use for any purpose.

thanks,
Amila.


 We appreciate your prompt attention to this matter.

 Sincerely yours.




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


Re: WS works in Axis 2 1.3 and 1.4.1 but has timeout in Axis 1.5.1?

2009-11-20 Thread Amila Suriarachchi
On Fri, Nov 13, 2009 at 11:02 PM, pwillemann philwillem...@yahoo.comwrote:


 I used WSDL2Java to create all my Web service classes.  I do not have any
 custom code.  Everything in my project is autogenerated.  My web service
 works fine in Axis 2 version 1.3 and Axis 2 version 1.4.1.  When I migrated
 to 1.5.1 I get timeouts.  Specifically the error says:

 HTTPSender.sendViaPost INFO - Unable to sendViaPost to
 url[http://127.0.0.1:8080/mywebservice/]
 org.apache.commons.httpclient.ConnectionPoolTimeoutException:  Timeout
 waiting for connection.

 I looked to see if there was a migration guide from 1.3/1.4 to 1.5 that
 addresses this issue, however I have been unable to find one.  This web
 service has worked for almost a year, but I am curious if the new version
 of
 Axis has revealed some sort of flaw or if there is an actual problem in
 1.5.1.

 Has anyone had a similar problem or has anyone solved this problem? Any
 help
 would be appreciated very much.  Thanks!


call stub._getServiceClient().cleanupTransport();
after service invocation.

thanks,
Amila.


 Sincerely yours
 Phil Willemann

 --
 View this message in context:
 http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26340326.html
 Sent from the Axis - User mailing list archive at Nabble.com.




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