Re: [Axis2] Passing complex type HashMap

[Deepal Jayasinghe]

Hi Sathija ;

None of the default message receivers does not support this scenario and
we have no idea to implement that. So  in this case you need to write
your own message receiver to support this .

Thanks
Deepal

>Hello,
>
>I need to pass a HashMap as one of the parameters to my web service call.
>How can I do that?
>
>Thanks,
>Sathija.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



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

Re: How to access http header from a service class.

[Deepal Jayasinghe]

Hi  Augusto ;

Inside the service impl class you can get access to the current message
context

MessageContext msgCtx = MessageContext.getCurrentContext();

and from the msg context you can get the http req , so from that you can
get whatever the headers that you want.
HttpServletRequest obj =(HttpServletRequest)
msgCtx.getProperty("transport.http.servletRequest");

Thanks
Deepal

> Hi all,
>
> Exist a way to access the http header from my service class when using
> Axis2?
>
> I want to get some client informations from the http header.
>
> Thanks,
> Augusto Arcoverde da Rocha
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



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

Re: [Axis2] including jars in .aar?

[Deepal Jayasinghe]

Hi andrewb;
You can put your jar file inside your service archive file as follows;
MyService.aar
  META-INF
services.xml
 lib
   your.jar

Thanks
Deepal

>Hi,
>
>My service class depends on a particular .jar file. How do I include that .jar 
>in the .aar file (or do I have to just have it be in my JBoss classpath 
>separately from the .aar)?
>
>Thanks,
>
>Andrew B.
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



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

RE: Java2WSDL can't expand other interfaces referenced from an interface?

[subir.sasikumar]

Title: Re: [Axis2] Help using AXIOMXPath








Can you post your
java2wsdl task and let us know what options you are using?

 









From: Sonali J.
Kanaujia [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006
9:58 PM
To: axis-user@ws.apache.org
Subject: RE:Java2WSDL can't expand
other interfaces referenced from an interface?



 



Re-sending the issue. Please respond
how to expand referenced interfaces, using Java2WSDL. 





 





Thanks,





Sonali





 









From: Sonali J.
Kanaujia [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 08, 2006
9:31 PM
To: axis-user@ws.apache.org
Subject: Java2WSDL can't expand
other interfaces referenced from an interface?

Hi,

I'm using Axis 1.2.1 Java2WSDL tool on an interface that has
methods that reference other interfaces. When I run the tool it complains that
it can't convert the other interfaces to xml schema types as they are not
beans classes (See error/warning below).

Is there any option/mechanism
to auto-convert other interfaces to portTypes(?) and related xml
schema elements as well, except converting all the referenced interfaces to
impl bean classes.

-Sonali

Nov 8, 2006 3:23:44 PM
org.apache.axis.wsdl.fromJava.Emitter writePartToMessage 



WARNING: Please register a typemapping/beanmapping for
[Lcom.sonicsw.bpel.service.mgmtapi.runtime.IProcessInstanceCounts;'
Nov 8, 2006 3:23:44 PM org.apache.axis.wsdl.fromJava.Types isBeanCompatible





WARNING: The class
com.sonicsw.bpel.service.mgmtapi.runtime.IProcessInstanceCounts does not
contain a default constructor, which is a requirement for a bean class. 
The class cannot be converted into an xml schema type.  An xml schema
anyType will be used to define this class in the wsdl file.










The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 
www.wipro.com

Re: Service Archive Wizard - eclipse Plug-in trouble.

[Lahiru Sandakith Gallege]

Hi Phil,
Pls try  Axis2 nightly builds. The problem is fixed in the current SVN.

From the latest source you can build the plugins by following the

readme.txt located on module/tool directory.

Thanks
Lahiru Sandakith

On 11/7/06, Phil Rosen <[EMAIL PROTECTED]> wrote:

Here you go:

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

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 10:30 AM
To: axis-user@ws.apache.org
Subject: Re: Service Archive Wizard - eclipse Plug-in trouble.

Please log a JIRA.. Select the component as IDE plugins.

~Thilina

On 11/7/06, Phil Rosen <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am trying to build and deploy a service on axis2 using the eclipse SAW
> plugin. When I view it in Axis2, it is listed as a faulty service with a
> deployment error (full error at bottom). When I inspect the JAR I find
> that
> the Services.xml is empty (I had checked the generate Services.xml option
> in
> the wizard).
>
>
>
> Any thoughts? Is it a result of the plugin or am I doing something
> fundamentally wrong?
>
>
>
>
>
> Thanks in advance!
>
>
>
> The error:
>
> Error: org.apache.axis2.deployment.DeploymentException:
> com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
> at [row,col {unknown-source}]: [1,0]; nested exception is:
> org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
> at [row,col {unknown-source}]: [1,0] at
> 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:124)
> at
> 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:620)
> at
> 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:195)
> at
> 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:207)
> at
> 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:155)
> at
> 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:91)
> at
> 
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:142)
> at
> 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:42)
> at
> 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:213)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:182)
> at
> 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
> at
> 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3951)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4225)
> at
> 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
> at
> 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
> at
> org.apache.catalina.startup.Catalina.start(Catalina.java:551)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source) at java.lang.reflect.Method.invoke(Unknown Source) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
> at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
> Caused by: org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
> at [row,col {unknown-source}]: [1,0] at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
> at
> 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144)
> at
> 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322)
> at
> 
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:85)
> at
> 
org.apache.axis2.deployment.repository.util

Re: Bug in New Version of Eclipse Code Generator

[Lahiru Sandakith Gallege]

Hi Jerome,
The nightly build fix this problem. The problem was due to a package
name refactoring in Axis2 source. You can build your own plugin from
the axis2 source by following the readme.txt at the
AXIS2_HOME/module/tool.

Thanks
Lahiru Sandakith

On 11/10/06, Jerome Soller <[EMAIL PROTECTED]> wrote:


One other bit of more detail.  The exact class that it can not load is
described as.
Plug-in Axis2_Codegen_Wizard was unable to load class
org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.
org.apache.axis2/util/CommandLineOptionConstants$Java2WSDLConstants

Jerome



Jerome Soller wrote:
>
> I recently tried the newest Eclipse Axis2 code generator for RC2, with
> Eclipse 3.2 It
> does not start due to an exception in finding Java2WSDLConstants . Is
> there a newer version available?
>
> Jerome Soller ([EMAIL PROTECTED])
>

--
View this message in context: 
http://www.nabble.com/Bug-in-New-Version-of-Eclipse-Code-Generator-tf2604133.html#a7266542
Sent from the Axis - User mailing list archive at Nabble.com.


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





--
Regards
Lahiru Sandakith

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

Re: Axis2-1.1 with Weblogic 9.2

[Charitha Kankanamge]

Thanks Dims. It worked fine when I added weblogic.xml with 
  parameter. I was able to deploy services, 
generate stubs (ADB) and invoking the services through clients in 
Axis2-1.1/Weblogic92 setup.


Thanks again,
Charitha

Davanum Srinivas wrote:
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/webapp/conf/weblogic.xml 



-- dims

On 11/8/06, Charitha Kankanamge <[EMAIL PROTECTED]> wrote:

Hi all,

I was trying to test Axis2-1.1 with Weblogic 9.2 on Ubuntu. I installed
weblogic 9.2 and configured a domain in development mode. Then I copied
axis2.war into /bea/user_projects/domain/mydomain/autodeploy directory.
When I restarted the server, I was able to access axis2 admin console
home page and was able to login to the console.
However when I selected a service (eg:-version) and clicked on it,
'Internal server error' page is displayed and following exception
appeared in the logs.

[EMAIL PROTECTED] - appName:
'_appsdir_axis2_war', name: 'axis2.war', context-path: '/axis2'] Root
cause of ServletException.
java.lang.NoSuchMethodError:
javax.xml.stream.XMLOutputFactory.newInstance(Ljava/lang/String;Ljava/lang/ClassLoader;)Ljavax/xml/stream/XMLOutputFactory; 

at 
org.apache.axiom.om.util.StAXUtils.getXMLOutputFactory(StAXUtils.java:97) 


at
org.apache.axiom.om.util.StAXUtils.createXMLStreamWriter(StAXUtils.java:111) 

at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:381)
at 
org.apache.axis2.description.AxisService.getWSDL(AxisService.java:711)
at 
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:580)


As I understand, this error occurs, due to weblogic ships with jars
which conflict with jars present in Axis2 (As stated in the Axis2
Application server specific configuration guide).
'Axis2 Application server specific configuration guide' instructs to set
 to true in weblogic.xml. However it does not
give a proper instructions on how to do that (How to configure
weblogic.xml completely, where to put it etc..)

I would be thankful if you can send me a sample weblogic.xml file with
necessary axis2 configuration or please point me to a correct source
where I can get these information.

Thanks in advance,
Charitha



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









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

Re: Multiple 'rows' of data to .NET client

[Ravi.S]

Hi Chris,

I am also looking for a service which could return multiple rows from
database. If you were able to make it work please help by posting the code.

Thanks in advance.
Regards,
Ravi S

chris-101 wrote:
> 
> Thanks for you help.  Unfortunately, I've been unable to figure out still.
> I've seen from the archives that you've helped out many people with this
> similar issue.  You'd think that I'd be able to piece together a working
> formula from all of those but I'm still not getting something.
> Does anybody know of a full blown, working WSDL and WSDD example that
> simply
> defines a service that is able to return an XML document to a .NET client?
> I've about given up on piecing it together myself.  If I had a simple
> working example, I think things would register and I could build from it.
> I'm usually pretty good at figuring things out, but this has just got
> me going in circles.  Sorry for being dense, but I'm at my wits end.
> 
> 
> 
> On 8/1/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>>
>> #1 -- Don't use SOAP Encoding. Use document/literal.
>> Edit any WSDL that Axis generates (e.g., change apachesoap:document to
>> xsd:anytype). Better yet, define your WSDL first and generate all your
>> code from the WSDL.
>>
>> Anne
>>
>> On 8/1/06, c <[EMAIL PROTECTED]> wrote:
>> > Hello,
>> >
>> > My Environment
>> > -
>> > Axis 1.4 Java
>> > Tomcat 5.5
>> > Visual C# with Visual Studio 2005 (as SOAP client)
>> >
>> > I'm brand new to web services and having a heck of a time doing
>> something
>> > that I thought would be very simple.  My web service needs to accept
>> > database query, execute the query and return the results.
>> >
>> > Since there is no standard way of communicating resultsets via SOAP,
>> I'm
>> > trying to implement my own data structure for doing so.  I've been
>> > successful implementing 'simple' web services and calling them from a
>> C#
>> > client.  By 'simple', I mean returning a string or an array of strings.
>> > However, this does me no good for multiple rows of data.
>> >
>> > Here's what I've tried:
>> >
>> > I've tried returning String[][] with the auto-generated WSDL but .NET
>> chokes
>> > on this.
>> >
>> >  I've tried returning String[][] with a custom WSDL but .NET chokes on
>> this.
>> > The WSDL I made was based off the post at the following url but .NET
>> gives
>> > me some kind of "Unbounded groups are not supported with encoded SOAP"
>> > error.
>> >
>> http://mail-archives.apache.org/mod_mbox/ws-axis-user/200207.mbox/[EMAIL 
>> PROTECTED]
>> >
>> > I've tried returning an XML document as org.w3c.dom.Element and
>> > org.w3c.dom.Document.  But this returns some kind of an apache-specific
>> data
>> > type that .NET chokes on.
>> >
>> > I've searched the far corners of the Internet but I can't find any
>> reliable
>> > answers.  Surely I must be missing big because I'm sure that the type
>> of
>> > data I'm trying to exchange here is not uncommon.
>> >
>> > I may have to resort to just cramming everything into one big string
>> and
>> > handle my own character escaping and row delimiters, etc.  But it
>> doesn't
>> > seem like I should have to do that.
>> >
>> > Would love some ideas.  Thanks.
>> >
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Multiple-%27rows%27-of-data-to-.NET-client-tf2031938.html#a7270999
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: returning xml rowset in soap message

[Ravi.S]

Hi Plork,

Were you able to do this. I am also looking for a similar web service.
Please help. If possible please provide some sample code.

Regards,
Ravi


plork123 wrote:
> 
> Hi all,
> 
> I'm writing a web service that will return data from a db table - the 
> resultset can be quite large
> 
> I want to return the data as an XML DOM, but not sure how.  Or return the 
> resultset in the SOAP message e.g. ROWSET format
> 
> I've seen an example of what i would like to do, but it has no examples
> 
> http://webservices.oracle.com/ws/emp/oracle.ws.scott.OTNDeptEmp
> 
> What would be the best way to go here?
> 
> Has anyone any examples to get me going?
> 
> Thanks for any help
> 
> _
> It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! 
> http://messenger.msn.co.uk
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/returning-xml-rowset-in-soap-message-tf76200.html#a7270958
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Extending class to write new listener throws NoClassDefFoundError

[Davanum Srinivas]

Please throw the debug on in the log4j.properties and
commons-logging.properties and post the stack trace.

thanks,
dims

On 11/9/06, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote:

Hi,
I am writing a new transport listener. The listener extends my framework
class and implements TransportListener interface like this...
public class TIAF2AXIS2Listener extends TIAFDefaultDriver implements
TransportListener

Then I declared it in axis2.xml file like this...

6062





When I start SimpleAxis2Server it fails to start the transports and
throws NoClassDefFoundError for class
org.apache.axis2.transport.tcp.TIAF2AXIS2Listener.

Any ideas on how to resolve this ?

-yogen


NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

RE: [Axis2] including jars in .aar?

[John Pfeifer]

Are you deploying the .aar file into the axis2 war distribution's
WEB-INF/services directory?  If so, make sure that your webapp is
configured to use the webapp classloader first.  I am using weblogic and
this property is configured in the weblogic.xml file.  Also, are you
using spring-axis integration?  If so, I have experienced some
classloader issues here as well.  If you are using axis-spring
integration, I would recommend getting the latest build along with the
documentation.

Jp4

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 5:45 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] including jars in .aar?

Thanks for the quick reply. I figured that out after posting my message.
However, I've done that, and the classes in the external .jar are still
not being loaded by Axis2, after deploying the service (getting
ClassNotFoundException). Is there anything else I have to do?

Thanks

- Start Original Message -
Sent: Thu, 9 Nov 2006 17:30:18 -0500
From: "John Pfeifer" <[EMAIL PROTECTED]>
To: ,

Subject: RE: [Axis2] including jars in .aar?

> 
> It should be in the lib directory inside your jar file.
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thu 11/9/2006 5:31 PM
> To: axis-user@ws.apache.org
> Subject: [Axis2] including jars in .aar?
>  
> Hi,
> 
> My service class depends on a particular .jar file. How do I include
that .jar in the .aar file (or do I have to just have it be in my JBoss
classpath separately from the .aar)?
> 
> Thanks,
> 
> Andrew B.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

- End Original Message -

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


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

Extending class to write new listener throws NoClassDefFoundError

[Yadav, Yogendra \(IT\)]

Hi,
I am writing a new transport listener. The listener extends my framework
class and implements TransportListener interface like this...
public class TIAF2AXIS2Listener extends TIAFDefaultDriver implements
TransportListener
 
Then I declared it in axis2.xml file like this...

6062





When I start SimpleAxis2Server it fails to start the transports and
throws NoClassDefFoundError for class
org.apache.axis2.transport.tcp.TIAF2AXIS2Listener. 

Any ideas on how to resolve this ?

-yogen


NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

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

Re: [Axis2] including jars in .aar?

[andrewb]

Thanks for the quick reply. I figured that out after posting my message. 
However, I've done that, and the classes in the external .jar are still not 
being loaded by Axis2, after deploying the service (getting 
ClassNotFoundException). Is there anything else I have to do?

Thanks

- Start Original Message -
Sent: Thu, 9 Nov 2006 17:30:18 -0500
From: "John Pfeifer" <[EMAIL PROTECTED]>
To: ,

Subject: RE: [Axis2] including jars in .aar?

> 
> It should be in the lib directory inside your jar file.
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thu 11/9/2006 5:31 PM
> To: axis-user@ws.apache.org
> Subject: [Axis2] including jars in .aar?
>  
> Hi,
> 
> My service class depends on a particular .jar file. How do I include that 
> .jar in the .aar file (or do I have to just have it be in my JBoss classpath 
> separately from the .aar)?
> 
> Thanks,
> 
> Andrew B.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

- End Original Message -

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

How to deploy on 2 different axis

[Gupta, Rahul]

Hi all

I have 2 different axis running on Apache i.e Axis1 and Axis2. Now I want to 
deploy two different web services, one on Axis1 and other on Axis2. Now the 
problem is how can I tell the wsdd files to deploy on which Axis. Is their any 
path that I have to define on these files or do I have change some other files.
Can anybody help me in this problem

Thanks
R.G 

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

RE: [Axis2] including jars in .aar?

[John Pfeifer]

Title: RE: [Axis2] including jars in .aar?







It should be in the lib directory inside your jar file.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thu 11/9/2006 5:31 PM
To: axis-user@ws.apache.org
Subject: [Axis2] including jars in .aar?

Hi,

My service class depends on a particular .jar file. How do I include that .jar in the .aar file (or do I have to just have it be in my JBoss classpath separately from the .aar)?

Thanks,

Andrew B.

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

[Axis2] including jars in .aar?

[andrewb]

Hi,

My service class depends on a particular .jar file. How do I include that .jar 
in the .aar file (or do I have to just have it be in my JBoss classpath 
separately from the .aar)?

Thanks,

Andrew B.

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

Re: Latest Release Date

[Davanum Srinivas]

Working furiously on some more documentation. Don't think we will need
an RC3. Thilina is going to do a dry run for 1.1 final this weekend.
ETA, Hopefully early next week if not this weekend.

thanks,
-- dims

On 11/9/06, Dale Herrig <[EMAIL PROTECTED]> wrote:



Axis Team,

What is the latest on the 1.1 release.



Regards,

Dale



--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Latest Release Date

[Dale Herrig]

Axis 
Team,
 
What is the latest 
on the 1.1 release.
 
 

Regards,
 
Dale 

Re: Bug in New Version of Eclipse Code Generator

[Jerome Soller]

One other bit of more detail.  The exact class that it can not load is
described as.
Plug-in Axis2_Codegen_Wizard was unable to load class
org.apache.axis2.tool.codegen.eclipse.CodeGenWizard.
org.apache.axis2/util/CommandLineOptionConstants$Java2WSDLConstants

Jerome



Jerome Soller wrote:
> 
> I recently tried the newest Eclipse Axis2 code generator for RC2, with
> Eclipse 3.2 It
> does not start due to an exception in finding Java2WSDLConstants . Is
> there a newer version available?
> 
> Jerome Soller ([EMAIL PROTECTED])
> 

-- 
View this message in context: 
http://www.nabble.com/Bug-in-New-Version-of-Eclipse-Code-Generator-tf2604133.html#a7266542
Sent from the Axis - User mailing list archive at Nabble.com.


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

Bug in New Version of Eclipse Code Generator

[Jerome Soller]

I recently tried the newest Eclipse Axis2 code generator for RC2, with
Eclipse 3.2 It
does not start due to an exception in finding Java2WSDLConstants . Is
there a newer version available?

Jerome Soller ([EMAIL PROTECTED])
-- 
View this message in context: 
http://www.nabble.com/Bug-in-New-Version-of-Eclipse-Code-Generator-tf2604133.html#a7266234
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Axis2 unexpected subelement error

[Dennis Sosnoski]

Most XML processors will balk at elements that aren't present in the 
schema definition. The exceptions are older SOAP frameworks (including 
the original flavor of Axis, I think) and some newer frameworks that 
have decided to basically degrade schemas (JAX-WS/JAXB does this by 
default).


With JiBX data binding you can use a "flexible" unmarshalling flag to 
say that unknown elements within a particular grouping should be 
ignored. See 
http://jibx.sourceforge.net/tutorial/binding-extras.html#mixing for 
details on this. This *does* seem to be a fairly common requirement for 
certain business areas (I know several major users of JiBX in the travel 
industry who rely on this, for instance).


 - Dennis

Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117



Moore, Don H wrote:

The elements are in order.

Let me explain the problem a little more clearly. I generated code using
a wsdl that does not include the field cdCustType because that field was
not in the data.  The data now includes that field, but my application
does not need it and there is nothing in the generated code about this
field. The generated code throws the error when the parser comes to
cdCustType.

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 10:48 AM

To: axis-user@ws.apache.org
Subject: Re: Axis2 unexpected subelement error

Moore,

It depends on the schema. *IF* your schema (in your wsdl) says, they are
needed only then we throw an exception. We also throw an exception if
the schema specifies a certain order and the runtime soap message does
not have the same order.

-- dims

On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:
  
I have an issue with generated Java code using wsdl2Java and Axis2 
1.0. I've also tried using Axis2 1.1, Nov 2 2006 build, and have the


same problem.
  
From posts I've found in the archives, I see this has been reported a 
few times before, but I haven't found a solution.


Essentially, if additional fields get added to the data which were not



  
in the wsdl when the java files were generated with Axis2, then the 
code blows up with the java.lang.RuntimeException: Unexpected


subelement error.
  
Obviously, I can regenerate the java code using a new wsdl. But, as 
long as those additional fields are not needed in my application, then



  

I really shouldn't have to be continuously regenerating the java code.



  

Shouldn't the additional fields just be ignored by the parser?




--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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

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


  


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

namespaces break XML Digital signatures

[Mike Straw]

Axis Gurus and Users,

I hate to beat a dead horse about Axis and namespaces, but I have not 
seen an answer to the question of how to tell Axis not to add namespaces 
when invoking a service with Call.invoke(...).


In my particular case it is breaking the verification of the XML digital 
signature in a document.  (For reasons that are unimportant to this 
discussion, I can not use handlers to sign and verify the document/message.)


FYI:  I am using Axis 1.4 and XML digital signature library from Sun's 
Java Web Services Developer Pack 2.0.


Can anyone help?

If Axis 1.4 is a lost cause for this namespace issue, is there hope in 
Axis 2?



--
Mike Straw
KeyWay Security Inc.
(614) 882-7125
[EMAIL PROTECTED]


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

Problem with array in custom type in .net client

[szymono]

Hi,

first of all - sorry for my english...


Ok, I have java axis webservice with some methods. One of them is:

public GetFreeNumbersOutDTO getFreeNumbers(String iterationGuid, int
category,
int quantity) { ...

which return GetFreeNumbersOutDTO.

Structure of this object:

class GetFreeNumberOutDTO {

   Status status;

   Msisdn[] msisdn;

...
}

class Status {

   int code;

   String text;

...
}

class Msisdn {

   String msisdnNo;

...
}


I wrote client application in java and webservice returns property values.

But I allso use .net webservicestudio to testing webservice and there is
some problem with my service:

above method returns the following object on response:

GetFreeNumbersOutDTO result {
   Msisdn[] results;
   Status status {
   code: 1;
   text: OK;
   }
} 

but should be:

GetFreeNumbersOutDTO result {
  Msisdn[3] results {
  Msisdn {
   msisdnNo: 82000;
  },
  Msisdn {
   msisdnNo: 82001
  },
  Msisdn {
   msisdnNo: 82002
  }
   }
  Status status {
  code: 1;
  text: OK;
  }
} 


Why? here is some xml from request and response:

Request:

http://schemas.xmlsoap.org/soap/envelope/";;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";;
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>;
 
   http://blstream.com/soa/activation/";>;
 iter1
 1
 3
   
 


Response:

http://schemas.xmlsoap.org/soap/envelope/";;
xmlns:xsd="http://www.w3.org/2001/XMLSchema";;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>;
 
   http://blstream.com/soa/activation/";>;
 
   
 
   82000
 
 
   82001
 
 
   82002
 
   
   
 1
 OK
   
 
   
 



As you can see array should not be empty - .net has some problem with
deserializing object but why? Maybe i have wrong configuration:


WSDD:


http://xml.apache.org/axis/wsdd/";;
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>;

   
   
   
   
   
   
   
   
   

   
   
   


   
   
   
   http://blstream.com/soa/activation/;
   
   http://blstream.com/soa/activation/";;
 
languageSpecificType="java:ecrm.soa.webservice.activation.dto.GetFreeNumbersOutDTO"/>

   http://blstream.com/soa/activation/";;
  
languageSpecificType="java:ecrm.core.common.dto.Status"/>
   
   http://blstream.com/soa/activation/";;
 
languageSpecificType="java:ecrm.soa.webservice.activation.dto.MsisdnWithSim"/>
   
   http://blstream.com/soa/activation/";;
  
languageSpecificType="java:ecrm.soa.webservice.activation.dto.Msisdn"/>
   
   

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   




WSDL:


http://blstream.com/soa/activation/";;
xmlns:apachesoap="http://xml.apache.org/xml-soap";;
xmlns:impl="http://blstream.com/soa/activation/";;
xmlns:intf="http://blstream.com/soa/activation/";;
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";;
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";;
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>;


 http://blstream.com/soa/activation/";;
xmlns="http://www.w3.org/2001/XMLSchema";>;
  
   

 
 
 

   
  
  
   

 

   
  
  
   

   
  
  
   

   
  
  
   


   
  
  
   


   
  
  
   

 
 

   
  
  
   

 

   
  
  
   

 
 

   
  
  
   

 
  
  
 

   
  
  
   

 

   
  
  
   

 

   
  
  
   

 

   
  
 


  

 

  

  

 

  

  

 

  

  

 

  

  

 

  

  

 

  

  

 

  

  

 

  

  

 





 

 





 

 





 

 





 

  

  

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

 





   





   



 

 





   





   



 

 





   





   



 

 





   





   



 

  

  

 

http://localhost:8080/ecrm-soa/ActivationService"/>;

 

  






I tested it in axis 1.2.1, 1.3 and 1.4 - always is the same wrong results in
webservicestudio of course.


Tnaks for hel

Axis2, Adb, nillable attribut and enumeration and exception

[VF]

Hi,

please, is it correct,that Axis2 returns this exception? :

http://schemas.xmlsoap.org/soap/envelope/";>
   
   
  
 soapenv:Client
 java.lang.IllegalArgumentException
 
  
   



I have these type for example in wsdl with enumeration:











and this type used in complex type, but with nillable attribut:


 
   
 
 
 
 
 

 











 



So it should be correct to send null value in todo_info in tuser type, but
this exception is in ADB - Axis 2 thrown. 


 Vladi


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

How to access http header from a service class.

[Augusto Arcoverde da Rocha]

Hi all,

Exist a way to access the http header from my service class when using Axis2?

I want to get some client informations from the http header.

Thanks,
Augusto Arcoverde da Rocha

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

RE: WSDL2Java support JMS binding

[Spies, Brennan]

Yeah, I was wondering the same thing myself... ;)

Short answer probably is...not in 1.1. 


Brennan Spies
Sr. Programmer Analyst
Shared Application Services


-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 10:19 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java support JMS binding

You can follow the JIRA:
https://issues.apache.org/jira/browse/AXIS2-1381

thanks,
dims

On 11/9/06, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> I would like to know, when is axis2 WSDL2Java tool going to support JMS
> binding from WSIF?
>
> thanks
>
> Kamal
>
> 
> The information contained in this message may be privileged
> and confidential and protected from disclosure. If the reader
> of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that any reproduction,
> dissemination or distribution of this communication is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by replying to the message and
> deleting it from your computer. Thank you. Tellabs
> 
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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


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

RE: Do we have XML Injection thread on AXIS 1.X Soap Servers?

[Venkatesh Jayaraman \(jvenky\)]

 I could find the answers
in FAQ.

Special XML attacks

XML messages have a
few intrinsic weakness, that Web Service creators should know about. None of
these problems are unique to SOAP; anyone processing incoming XML needs to know
and resist these.


 Large XML Documents
 Have a client post an XML doc of extreme length/depth
 ...
 This does bad things to DOM parsers and memory consumption on the server:
 a DoS attack. The issue here is that the costs of handling a large XML
 document are much greater than the cost of generating one. 
 Entity Expansion Attacks.
 If an XML doc header declares some recursive entity declarations, and the
 file refers to them, then bad things happen. Axis became immune to this
 between versions 1.0 and 1.1. 
 Entities referring to the
 filesystem.
 Here you declare an entity referring to a local file, then expand it.
 Result: you may be able to probe for files, perhaps even get a copy of it
 in the error response. As Axis does not support entities any more, it
 resists this. If your code has any way of resolving URLs from incoming
 messages, you may recreate this problem. 


The other thing to
know about XML is that string matching is not enough to be sure that the
content is safe, because of the many ways to reformat the same XML.

 

Thanks

 

-Venky









From: Venkatesh
Jayaraman (jvenky) 
Sent: Thursday, November 09, 2006
9:57 AM
To: axis-user@ws.apache.org
Subject: RE: Do we have XML
Injection thread on AXIS 1.X Soap Servers?



 

Does AXIS take care of this internally?

Thanks for the answers in advance.

 

-Venky

 









From: Venkatesh
Jayaraman (jvenky) 
Sent: Thursday, November 09, 2006
9:51 AM
To: 'axis-user@ws.apache.org'
Subject: Do we have XML Injection
thread on AXIS 1.X Soap Servers?



 

Security
Issue Posed by Nested Entity Definitions

While
XML does not allow recursive entity definitions, it does permit nested entity
definitions, which produces the potential for Denial of Service attacks on a
server which accepts XML data from external sources. For example, a SOAP
document like the following that has very deeply nested entity definitions can
consume 100% of CPU time and large amounts of memory in entity expansions:





  



  



  



  



  ...



  



  



  ]>



 



 



 



 &x1;



 



 



  

A
system that doesn't take in external XML data need not be concerned with the
issue, but one that does can utilize one of the following safeguards to prevent
the problem:

New system property to limit entity
expansion 

The entityExpansionLimit system property lets existing applications constrain the total number
of entity expansions without recompiling the code. The parser throws a fatal
error once it has reached the entity expansion limit. (By default, the limit is
set to 64000.) 

To set the entity expansion limit using the system property, use an option like
the following on the java command line: -DentityExpansionLimit=10 

 

New parser property to disallow DTDs 

The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming
XML document contains a DOCTYPE declaration. (The default value for this
property is false.) This property is typically useful for SOAP based
applications where a SOAP message must not contain a Document Type Declaration.

New feature for Secure Processing 

JAXP 1.3 includes a new secure
processing feature in which an application can configure the
SAXParserFactory or DocumentBuilderFactory
to get an XML processor that behaves in a secured fashion.  Setting this
feature to true sets the entity expansion limit to 64000.  Note that the
default limit can be increased using the entityExpansionLimit system property.

 

 

 

 

http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html

 

 

Thanks

 

-Venky (Venkatesh Jayaraman)

 

 

Re: WSDL2Java support JMS binding

[Davanum Srinivas]

You can follow the JIRA:
https://issues.apache.org/jira/browse/AXIS2-1381

thanks,
dims

On 11/9/06, Kang, Kamaljeet K. <[EMAIL PROTECTED]> wrote:



Hi,

I would like to know, when is axis2 WSDL2Java tool going to support JMS
binding from WSIF?

thanks

Kamal


The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs






--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

WSDL2Java support JMS binding

[Kang, Kamaljeet K.]

Title: Re: [Axis2] Help using AXIOMXPath



Hi,
 
I would like to know, when is axis2 WSDL2Java tool 
going to support JMS binding from WSIF?
 
thanks
 
Kamal
 
 
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs

Re: Do we have XML Injection thread on AXIS 1.X Soap Servers?

[Davanum Srinivas]

yes.

On 11/9/06, Venkatesh Jayaraman (jvenky) <[EMAIL PROTECTED]> wrote:





Does AXIS take care of this internally?

Thanks for the answers in advance.



-Venky



 


From: Venkatesh Jayaraman (jvenky)
 Sent: Thursday, November 09, 2006 9:51 AM
 To: 'axis-user@ws.apache.org'
 Subject: Do we have XML Injection thread on AXIS 1.X Soap Servers?



Security Issue Posed by Nested Entity Definitions

While XML does not allow recursive entity definitions, it does permit nested
entity definitions, which produces the potential for Denial of Service
attacks on a server which accepts XML data from external sources. For
example, a SOAP document like the following that has very deeply nested
entity definitions can consume 100% of CPU time and large amounts of memory
in entity expansions: 




 




 




 




 ...




 




 




 ]>



















&x1;

















A system that doesn't take in external XML data need not be concerned with
the issue, but one that does can utilize one of the following safeguards to
prevent the problem:

New system property to limit entity expansion

The entityExpansionLimit system property lets existing applications
constrain the total number of entity expansions without recompiling the
code. The parser throws a fatal error once it has reached the entity
expansion limit. (By default, the limit is set to 64000.)

 To set the entity expansion limit using the system property, use an option
like the following on the java command line: -DentityExpansionLimit=10



New parser property to disallow DTDs

The application can also set the
http://apache.org/xml/features/disallow-doctype-decl parser
property to true. A fatal error is then thrown if the incoming XML document
contains a DOCTYPE declaration. (The default value for this property is
false.) This property is typically useful for SOAP based applications where
a SOAP message must not contain a Document Type Declaration.

New feature for Secure Processing

JAXP 1.3 includes a new secure processing feature in which an application
can configure the SAXParserFactory or DocumentBuilderFactory to get an XML
processor that behaves in a secured fashion.  Setting this feature to true
sets the entity expansion limit to 64000.  Note that the default limit can
be increased using the entityExpansionLimit system property.









http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html





Thanks



-Venky (Venkatesh Jayaraman)







--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

RE: Do we have XML Injection thread on AXIS 1.X Soap Servers?

[Venkatesh Jayaraman \(jvenky\)]

Does AXIS take care of this internally?

Thanks for the answers in advance.

 

-Venky

 









From: Venkatesh
Jayaraman (jvenky) 
Sent: Thursday, November 09, 2006
9:51 AM
To: 'axis-user@ws.apache.org'
Subject: Do we have XML Injection
thread on AXIS 1.X Soap Servers?



 

Security
Issue Posed by Nested Entity Definitions

While
XML does not allow recursive entity definitions, it does permit nested entity
definitions, which produces the potential for Denial of Service attacks on a
server which accepts XML data from external sources. For example, a SOAP
document like the following that has very deeply nested entity definitions can
consume 100% of CPU time and large amounts of memory in entity expansions:



 

 

 

 

 ...

 

 

 ]>







&x1;





 

A
system that doesn't take in external XML data need not be concerned with the
issue, but one that does can utilize one of the following safeguards to prevent
the problem:

New system property to limit entity
expansion 

The entityExpansionLimit system property lets existing applications constrain the total number
of entity expansions without recompiling the code. The parser throws a fatal
error once it has reached the entity expansion limit. (By default, the limit is
set to 64000.) 

To set the entity expansion limit using the system property, use an option like
the following on the java command line: -DentityExpansionLimit=10 

 

New parser property to disallow DTDs 

The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming
XML document contains a DOCTYPE declaration. (The default value for this
property is false.) This property is typically useful for SOAP based
applications where a SOAP message must not contain a Document Type Declaration.

New feature for Secure Processing 

JAXP 1.3 includes a new secure
processing feature in which an application can configure the
SAXParserFactory or DocumentBuilderFactory
to get an XML processor that behaves in a secured fashion.  Setting this
feature to true sets the entity expansion limit to 64000.  Note that the
default limit can be increased using the entityExpansionLimit system property.

 

 

 

 

http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html

 

 

Thanks

 

-Venky (Venkatesh Jayaraman)

 

 

Re: Do we have XML Injection thread on AXIS 1.X Soap Servers?

[Davanum Srinivas]

we already take care of this in Axis1 and Axis2.

-- dims

On 11/9/06, Venkatesh Jayaraman (jvenky) <[EMAIL PROTECTED]> wrote:




Security Issue Posed by Nested Entity Definitions

While XML does not allow recursive entity definitions, it does permit nested
entity definitions, which produces the potential for Denial of Service
attacks on a server which accepts XML data from external sources. For
example, a SOAP document like the following that has very deeply nested
entity definitions can consume 100% of CPU time and large amounts of memory
in entity expansions: 

 

 

 

 ...

 

 

 ]>







&x1;








A system that doesn't take in external XML data need not be concerned with
the issue, but one that does can utilize one of the following safeguards to
prevent the problem:

New system property to limit entity expansion

The entityExpansionLimit system property lets existing applications
constrain the total number of entity expansions without recompiling the
code. The parser throws a fatal error once it has reached the entity
expansion limit. (By default, the limit is set to 64000.)

 To set the entity expansion limit using the system property, use an option
like the following on the java command line: -DentityExpansionLimit=10



New parser property to disallow DTDs

The application can also set the
http://apache.org/xml/features/disallow-doctype-decl parser
property to true. A fatal error is then thrown if the incoming XML document
contains a DOCTYPE declaration. (The default value for this property is
false.) This property is typically useful for SOAP based applications where
a SOAP message must not contain a Document Type Declaration.

New feature for Secure Processing

JAXP 1.3 includes a new secure processing feature in which an application
can configure the SAXParserFactory or DocumentBuilderFactory to get an XML
processor that behaves in a secured fashion.  Setting this feature to true
sets the entity expansion limit to 64000.  Note that the default limit can
be increased using the entityExpansionLimit system property.









http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html





Thanks



-Venky (Venkatesh Jayaraman)







--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

WSDLException

[oslezka]

oslezka wrote:


I made simplest service
class StockQuoteService  have two methods
public void subscribe(OMElement in)
public OMElement getQuote(OMElement in)
and
services.xml

   locked="false">stock.StockQuoteService

   
   class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>

   

   class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>

   


When I trying cteate stub by invoke WSDL2Java.bat -uri 
http://localhost/axis2/services/StockQuoteService?wsdl -o  
E:\Projects\axis2\src\client

I take error message
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:96) 


   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: WSDLException (at /error): faultCode=INVALID_WSDL: Expected 
element '{http://schemas.xmlsoap.org/wsdl/}definitions'.:
   at com.ibm.wsdl.xml.WSDLReaderImpl.checkElementName(Unknown 
Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown 
Source)

   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:238) 

   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:81) 



Where this element expected - in services.xml?
Or what happening at all?




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

Re: Axis response xml tag in wrong format

[oslezka]

I made simplest service
class StockQuoteService  have two methods
public void subscribe(OMElement in)
public OMElement getQuote(OMElement in)
and
services.xml

   locked="false">stock.StockQuoteService

   
   class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>

   

   class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>

   


When I trying cteate stub by invoke WSDL2Java.bat -uri 
http://localhost/axis2/services/StockQuoteService?wsdl -o  
E:\Projects\axis2\src\client

I take error message
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:96)

   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: WSDLException (at /error): faultCode=INVALID_WSDL: Expected 
element '{http://schemas.xmlsoap.org/wsdl/}definitions'.:

   at com.ibm.wsdl.xml.WSDLReaderImpl.checkElementName(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:238)
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:81)


Where this element expected - in services.xml?
Or what happening at all?

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

Do we have XML Injection thread on AXIS 1.X Soap Servers?

[Venkatesh Jayaraman \(jvenky\)]

Security
Issue Posed by Nested Entity Definitions

While
XML does not allow recursive entity definitions, it does permit nested entity
definitions, which produces the potential for Denial of Service attacks on a
server which accepts XML data from external sources. For example, a SOAP
document like the following that has very deeply nested entity definitions can
consume 100% of CPU time and large amounts of memory in entity expansions:


 
 
 
 
 ...
 
 
 ]>



&x1;


 

A
system that doesn't take in external XML data need not be concerned with the
issue, but one that does can utilize one of the following safeguards to prevent
the problem:

New system property to limit entity
expansion 

The entityExpansionLimit system property lets existing applications constrain the total number
of entity expansions without recompiling the code. The parser throws a fatal
error once it has reached the entity expansion limit. (By default, the limit is
set to 64000.) 

To set the entity expansion limit using the system property, use an option like
the following on the java command line: -DentityExpansionLimit=10 

 

New parser property to disallow DTDs 

The application can also set the http://apache.org/xml/features/disallow-doctype-decl parser property to true. A fatal error is then thrown if the incoming
XML document contains a DOCTYPE declaration. (The default value for this
property is false.) This property is typically useful for SOAP based
applications where a SOAP message must not contain a Document Type Declaration.

New feature for Secure Processing 

JAXP 1.3 includes a new secure
processing feature in which an application can configure the
SAXParserFactory or DocumentBuilderFactory
to get an XML processor that behaves in a secured fashion.  Setting this
feature to true sets the entity expansion limit to 64000.  Note that the
default limit can be increased using the entityExpansionLimit system property.

 

 

 

 

http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html

 

 

Thanks

 

-Venky (Venkatesh Jayaraman)

 

 

Axis response xml tag in wrong format

[Recep Ayaz]

I have a difficulty in getting the response message in Axis 1.3 for a request on Tomcat 4.1.   Axis changes the response element name to  Return,
regardless of what it said in the WSDL.(  My incoming xml root elemnt name is "OTA_PingRQ" and  my response xml root elemnt name is "OTA_PingRQReturn".)Is this a default setting for axis ? If So, How can we manipulate this behaviour ?
Request, Reponse and part of the wsdl are below.Do you have any idea How we can solve this issue ?
   
   ...
   soap:Header>
   
   "http://otabase.otapax">
   "http://194.140.227.17/axis/services/OTA">are you there !!!
   
   soap:Body>
soap:Envelope>



"http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
"http://otabase.otapax" xmlns:ns1="http://www.hititcs.com/TestRecep"
>
I am here 
     
    
    


Thanks ,Recep Ayaz

Does Rampart with Axis2 allow integration with LDAP/AD?

[Karr, David]

Forgive me if there's a simple answer to this.  I have only superficial
knowledge of Axis2 and Rampart.

Are there convenient strategies to use Axis2 and Rampart to process
UserNameToken in WS-Security, authenticating to LDAP (Active Directory)?
Past that, is it practical to use the groups info from LDAP for
authorization for services?

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

Please give link to good tutorials for AXIS2

[oslezka]

Please give link to good tutorials for AXIS2

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

Re: Axis2 unexpected subelement error

[Davanum Srinivas]

Because it finds something that should not be there according to the
schema. Unless you originally had a schema that allowed a bag of any
elements, codegen will try to do the right thing. in this case, throw
an error that the xml you get is not according to the schema you
specified.

-- dims

On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:

The elements are in order.

Let me explain the problem a little more clearly. I generated code using
a wsdl that does not include the field cdCustType because that field was
not in the data.  The data now includes that field, but my application
does not need it and there is nothing in the generated code about this
field. The generated code throws the error when the parser comes to
cdCustType.

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 10:48 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 unexpected subelement error

Moore,

It depends on the schema. *IF* your schema (in your wsdl) says, they are
needed only then we throw an exception. We also throw an exception if
the schema specifies a certain order and the runtime soap message does
not have the same order.

-- dims

On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:
>
>
> I have an issue with generated Java code using wsdl2Java and Axis2
> 1.0. I've also tried using Axis2 1.1, Nov 2 2006 build, and have the
same problem.
> From posts I've found in the archives, I see this has been reported a
> few times before, but I haven't found a solution.
>
> Essentially, if additional fields get added to the data which were not

> in the wsdl when the java files were generated with Axis2, then the
> code blows up with the java.lang.RuntimeException: Unexpected
subelement error.
> Obviously, I can regenerate the java code using a new wsdl. But, as
> long as those additional fields are not needed in my application, then

> I really shouldn't have to be continuously regenerating the java code.

> Shouldn't the additional fields just be ignored by the parser?


--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Axis - Session Timeout Listener

[Alexander Hachmann]

Hello,
I wondering if it is possible to ad any listener to the AxisSession that
will be
Invoked before the Session Times out?

I am holding objects that need to be told.

Thanks,
Alexander


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

RE: Axis2 unexpected subelement error

[Moore, Don H]

The elements are in order.

Let me explain the problem a little more clearly. I generated code using
a wsdl that does not include the field cdCustType because that field was
not in the data.  The data now includes that field, but my application
does not need it and there is nothing in the generated code about this
field. The generated code throws the error when the parser comes to
cdCustType.

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 10:48 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 unexpected subelement error

Moore,

It depends on the schema. *IF* your schema (in your wsdl) says, they are
needed only then we throw an exception. We also throw an exception if
the schema specifies a certain order and the runtime soap message does
not have the same order.

-- dims

On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:
>
>
> I have an issue with generated Java code using wsdl2Java and Axis2 
> 1.0. I've also tried using Axis2 1.1, Nov 2 2006 build, and have the
same problem.
> From posts I've found in the archives, I see this has been reported a 
> few times before, but I haven't found a solution.
>
> Essentially, if additional fields get added to the data which were not

> in the wsdl when the java files were generated with Axis2, then the 
> code blows up with the java.lang.RuntimeException: Unexpected
subelement error.
> Obviously, I can regenerate the java code using a new wsdl. But, as 
> long as those additional fields are not needed in my application, then

> I really shouldn't have to be continuously regenerating the java code.

> Shouldn't the additional fields just be ignored by the parser?


--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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

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

Re: Axis2 unexpected subelement error

[Davanum Srinivas]

Moore,

It depends on the schema. *IF* your schema (in your wsdl) says, they
are needed only then we throw an exception. We also throw an exception
if the schema specifies a certain order and the runtime soap message
does not have the same order.

-- dims

On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:



I have an issue with generated Java code using wsdl2Java and Axis2 1.0. I've
also tried using Axis2 1.1, Nov 2 2006 build, and have the same problem.
From posts I've found in the archives, I see this has been reported a few
times before, but I haven't found a solution.

Essentially, if additional fields get added to the data which were not in
the wsdl when the java files were generated with Axis2, then the code blows
up with the java.lang.RuntimeException: Unexpected subelement error.
Obviously, I can regenerate the java code using a new wsdl. But, as long as
those additional fields are not needed in my application, then I really
shouldn't have to be continuously regenerating the java code. Shouldn't the
additional fields just be ignored by the parser?



--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

RE:Java2WSDL can't expand other interfaces referenced from an interface?

[Sonali J. Kanaujia]

Title: Re: [Axis2] Help using AXIOMXPath



Re-sending the issue. Please respond how to expand referenced interfaces, using Java2WSDL. 

 
Thanks,
Sonali



From: Sonali J. Kanaujia 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 9:31 
PMTo: axis-user@ws.apache.orgSubject: Java2WSDL can't 
expand other interfaces referenced from an interface?

Hi,
I'm 
using Axis 1.2.1 Java2WSDL tool on an interface that has methods that reference 
other interfaces. When I run the tool it complains that it can't convert the 
other interfaces to xml schema types 
as they are not beans classes (See error/warning below).
Is there any option/mechanism to auto-convert other interfaces to portTypes(?) and 
related xml schema elements as well, except converting all the referenced 
interfaces to impl bean classes.
-Sonali
Nov 8, 2006 3:23:44 
PM org.apache.axis.wsdl.fromJava.Emitter writePartToMessage 


WARNING: Please 
register a typemapping/beanmapping for 
[Lcom.sonicsw.bpel.service.mgmtapi.runtime.IProcessInstanceCounts;'Nov 8, 
2006 3:23:44 PM org.apache.axis.wsdl.fromJava.Types 
isBeanCompatible

WARNING: The class 
com.sonicsw.bpel.service.mgmtapi.runtime.IProcessInstanceCounts does not contain 
a default constructor, which is a requirement for a bean class.  The class 
cannot be converted into an xml schema type.  An xml schema anyType will be 
used to define this class in the wsdl 
file.

Re: Axis2 Book?

[Ruchith Fernando]

Hi,

I'm not sure about books on these products.

Try http://www.wso2.net/ ... it contains a lot fo articles on Axis2,
Rampart etc.

Thanks,
Ruchith

On 11/9/06, Philipp Perner <[EMAIL PROTECTED]> wrote:

Hi guys,

Does anyone know a really good book, which explains the usage of axis2
with java?
Furthermore it could be useful if the book is written in connection with
the usage of eclipse, tomcat, ...

Another Book I'm trying to find should be about Web-Service Security
and/or rampart.

Is there any literal resource available?
I'm looking forward to any response which proposes a rather new book on
axis2, wss4j, rampart,...

Please write everything you can think of!!!

Kind regards, Philipp


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





--
www.ruchith.org

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

[Axis2] Dynamic registration of handlers with Axis2/Rampart

[Andrew Fielden]

The following test code registers a callback handler in order to add a
username token to the outgoing SOAP message.
My question is how this could be achieved when using Axis2 and Rampart.
The Axis2 API is quite different to Axis, and all the examples I can
find revolve around the existence of a client deployment descriptor. In
the context of my application, the target web service is dynamic and not
known until run-time. 

In particular, how do programmatically access the handler chain?

Any code fragments or advice would be appreciated.

Andrew.


import java.io.BufferedWriter;
import java.io.ByteArrayInputStream;
import java.io.FileWriter;
import java.io.IOException;
import java.io.StringBufferInputStream;
import java.net.MalformedURLException;
import java.net.URL;
import java.rmi.RemoteException;
import java.util.List;

import javax.xml.namespace.QName;
import javax.xml.rpc.Call;
import javax.xml.rpc.ServiceException;

import org.apache.axis.client.Service;
import org.apache.log4j.BasicConfigurator;
import org.apache.log4j.Logger;

public class WSClient
{
static
{
BasicConfigurator.configure();
}

private static final Logger log = Logger.getLogger(WSClient.class);

public static void main(String[] args)
{


String webService = "StockQuoteServiceService";
String port = "StockQuoteService";
String operation = "getQuote";

log.debug("Beginning work");

QName servQN = new
QName("http://stockquote",webService);

log.debug("Web service service: " + servQN.toString());

QName portQN = new QName(servQN.getNamespaceURI(),
port);

log.debug("Web service port: " + portQN.toString());

Service service = null;


try {
System.out.println("about to generate certificate");
service = new
Service("https://localhost:9443/SecureStockQuote/services/StockQuoteServ
ice/wsdl/StockQuoteService.wsdl",servQN);
System.out.println("Loaded service ok");
} catch (ServiceException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
service.setCacheWSDL(false);

List list =
service.getHandlerRegistry().getHandlerChain(portQN);
list.add(new
javax.xml.rpc.handler.HandlerInfo(WSSCallbackHandler.class,null,null));

Call call = null;

try
{
call = service.createCall(portQN, operation);
System.out.println("Created call ok");
} 
catch (ServiceException e3)
{
// TODO Auto-generated catch block
e3.printStackTrace();
}

System.out.println("Web service operation: " + operation);

try
{
Object result = call.invoke(new Object[] {});
System.out.println("Response is: "+result);
} 
catch (RemoteException e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}

}
}


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

Re: Axis2 unexpected subelement error

[sridhar vudutha]

Moore,
  Check if all the XML elements are in order (according to the schema definition) and also check if all the required elements are there.
  I got this error and got rid of it with the above corrections.
 
Hope this helps,
Sridhar. 
On 11/9/06, Moore, Don H <[EMAIL PROTECTED]> wrote:


I have an issue with generated Java code using wsdl2Java and Axis2 1.0. I've also tried using Axis2 1.1, Nov 2 2006 build, and have the same problem. From posts I've found in the archives, I see this has been reported a few times before, but I haven't found a solution.

 
Essentially, if additional fields get added to the data which were not in the wsdl when the java files were generated with Axis2, then the code blows up with the java.lang.RuntimeException
: Unexpected subelement error. Obviously, I can regenerate the java code using a new wsdl. But, as long as those additional fields are not needed in my application, then I really shouldn't have to be continuously regenerating the java code. Shouldn't the additional fields just be ignored by the parser?

Axis2 unexpected subelement error

[Moore, Don H]

I have an issue with 
generated Java code using wsdl2Java and Axis2 1.0. I've also tried using Axis2 
1.1, Nov 2 2006 build, and have the same problem. From posts I've found in the 
archives, I see this has been reported a few times before, but I haven't found a 
solution.
 
Essentially, if additional 
fields get added to the data which were not in the wsdl when the java files were 
generated with Axis2, then the code blows up with the java.lang.RuntimeException: 
Unexpected subelement error. Obviously, I can regenerate the java code using a 
new wsdl. But, as long as those additional fields are not needed in my 
application, then I really shouldn't have to be continuously regenerating the 
java code. Shouldn't the additional fields just be ignored by the 
parser?

Re: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a subelement that doesn't conform to the WSDL

[Davanum Srinivas]

You should use ADB on the server-side. RPCMessageReceiver  is not used
when you generate code using wsdl to create the service.

-- dims

On 11/9/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:

Hi Dims,

I'm not sure how this workaround will help as I am currently using
WSDL2Java and ADB.

Shahar

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 3:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a
subelement that doesn't conform to the WSDL

Shahar,

we deferred AXIS2-1606 and hence will defer this as well. Solution for
now is to please use WSDL2Java and use ADB generated code (or any
other data binding). We will deal with this issue immediately after
1.1 release.

thanks,
dims

On 11/9/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> Will this issue be resolved soon? If I can't change the WSDL and
change
> elements' names then I cannot provide a robust API through my web
services.
>
>
>
> Thanks and regards,
>
> Shahar Kedar
>
>


--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Re: problems generating wsdl

[Davanum Srinivas]

that's a pending issue. would appreciate if you could log an enhcancement issue.

-- dims

On 11/9/06, Philipp Perner <[EMAIL PROTECTED]> wrote:

Yeah,

You are brilliant!!!

Is there any reason why datahandler doesn't work? In Axis1 v.1.4 it
worked perfectly
Which datatypes are supported for input/output parameters?

regards, Philipp

Davanum Srinivas schrieb:
> replace the DataHandler with a byte[] and see if that helps.
>
> -- dims
>
> On 11/9/06, Philipp Perner <[EMAIL PROTECTED]> wrote:
>> How do you generate wsdl file?
>>
>> I have a service class, which has some methods. For example a
>> datahandler should be returned and a beanclass i designed.
>> When i generate wsdl file with java2wsdl from command line the generated
>> wsdl file is invalid and cannot be transformed to service classes by
>> WSDL2Java.bat:
>>
>> Command to generate WSDL from Java Code:
>> java -cp {required libs} org.apache.ws.java2wsdl.Java2WSDL -tn
>> http://Pseudonymisierung.pseudo.service.axis.healthgate -tp ns -stn
>> http://Pseudonymisierung.pseudo.service.axis.healthgate/types -stp types
>> -o ../ -l "http://localhost:8081/axis2/services/"; -sn
>> "Pseudonymisierung" -cn healthgate.axis.service.pseudo.Pseudonymisierung
>> -of pseudo.wsdl
>>
>> --> No error
>>
>> Command to generate Java Code from WSDL:
>> 
D:\Development\eclipse3.2\WebService\WEB-INF>D:\downloads\axis2-1.1-SNAPSHOT\bin\WSDL2Java.bat
>>
>> -uri pseudo.wsdl -ss -sd -d xmlbeans -o \generated -p
>> healthgate.axis.service.pseudo.Pseudonymisierung
>>
>> Using AXIS2_HOME:   D:\downloads\axis2-std-1.0-bin
>> Using JAVA_HOME:D:\Java\j2sdk1.4.2_12
>> Exception in thread "main"
>> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
>> WSDL
>> at
>> 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94)
>>
>> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
>> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
>> Caused by: org.apache.axis2.AxisFault: Schema for namespace
>> 'http://net.java/xsd' already contains type 'URLStreamHandlerFactory;
>> nested exception is:
>> java.lang.RuntimeException: Schema for namespace
>> 'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
>> at
>> 
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243)
>>
>> at
>> 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87)
>>
>> ... 2 more
>> Caused by: java.lang.RuntimeException: Schema for namespace
>> 'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
>> at
>> org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:244)
>> at
>> 
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:110)
>>
>> at
>> 
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:250)
>>
>> at
>> 
org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuilder.java:959)
>>
>> at
>> 
org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisServiceBuilder.java:1067)
>>
>> at
>> 
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:221)
>>
>> ... 3 more
>>
>>
>> any clues to fix this problem?
>> Please help, because I'm stuck in there since monday...
>>
>> regards, philipp
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>


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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Axis2 Book?

[Philipp Perner]

Hi guys,

Does anyone know a really good book, which explains the usage of axis2 
with java?
Furthermore it could be useful if the book is written in connection with 
the usage of eclipse, tomcat, ...


Another Book I'm trying to find should be about Web-Service Security 
and/or rampart.


Is there any literal resource available?
I'm looking forward to any response which proposes a rather new book on 
axis2, wss4j, rampart,...


Please write everything you can think of!!!

Kind regards, Philipp


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

RE: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a subelement that doesn't conform to the WSDL

[Kedar, Shahar]

Hi Dims,

When is the 1.1 release scheduled to be formally released?

Thanks,
Shahar

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 3:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a
subelement that doesn't conform to the WSDL

Shahar,

we deferred AXIS2-1606 and hence will defer this as well. Solution for
now is to please use WSDL2Java and use ADB generated code (or any
other data binding). We will deal with this issue immediately after
1.1 release.

thanks,
dims

On 11/9/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> Will this issue be resolved soon? If I can't change the WSDL and
change
> elements' names then I cannot provide a robust API through my web
services.
>
>
>
> Thanks and regards,
>
> Shahar Kedar
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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


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

RE: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a subelement that doesn't conform to the WSDL

[Kedar, Shahar]

Hi Dims,

I'm not sure how this workaround will help as I am currently using
WSDL2Java and ADB.

Shahar

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 3:21 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a
subelement that doesn't conform to the WSDL

Shahar,

we deferred AXIS2-1606 and hence will defer this as well. Solution for
now is to please use WSDL2Java and use ADB generated code (or any
other data binding). We will deal with this issue immediately after
1.1 release.

thanks,
dims

On 11/9/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> Will this issue be resolved soon? If I can't change the WSDL and
change
> elements' names then I cannot provide a robust API through my web
services.
>
>
>
> Thanks and regards,
>
> Shahar Kedar
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)

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


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

Plans for Axis2 release 1.1 ?

[Gul Onural]

Title: Plans for Axis2 release 1.1 ?








What is the latest plan for the Axis2 1.1 release ? Can somebody comment on this ?


Cheers,


Gul

Re: problems generating wsdl

[Philipp Perner]

Yeah,

You are brilliant!!!

Is there any reason why datahandler doesn't work? In Axis1 v.1.4 it 
worked perfectly

Which datatypes are supported for input/output parameters?

regards, Philipp

Davanum Srinivas schrieb:

replace the DataHandler with a byte[] and see if that helps.

-- dims

On 11/9/06, Philipp Perner <[EMAIL PROTECTED]> wrote:

How do you generate wsdl file?

I have a service class, which has some methods. For example a
datahandler should be returned and a beanclass i designed.
When i generate wsdl file with java2wsdl from command line the generated
wsdl file is invalid and cannot be transformed to service classes by
WSDL2Java.bat:

Command to generate WSDL from Java Code:
java -cp {required libs} org.apache.ws.java2wsdl.Java2WSDL -tn
http://Pseudonymisierung.pseudo.service.axis.healthgate -tp ns -stn
http://Pseudonymisierung.pseudo.service.axis.healthgate/types -stp types
-o ../ -l "http://localhost:8081/axis2/services/"; -sn
"Pseudonymisierung" -cn healthgate.axis.service.pseudo.Pseudonymisierung
-of pseudo.wsdl

--> No error

Command to generate Java Code from WSDL:
D:\Development\eclipse3.2\WebService\WEB-INF>D:\downloads\axis2-1.1-SNAPSHOT\bin\WSDL2Java.bat 


-uri pseudo.wsdl -ss -sd -d xmlbeans -o \generated -p
healthgate.axis.service.pseudo.Pseudonymisierung

Using AXIS2_HOME:   D:\downloads\axis2-std-1.0-bin
Using JAVA_HOME:D:\Java\j2sdk1.4.2_12
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing 
WSDL

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94) 


at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory;
nested exception is:
java.lang.RuntimeException: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
at
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243) 


at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87) 


... 2 more
Caused by: java.lang.RuntimeException: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
at
org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:244)
at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:110) 


at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:250) 


at
org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuilder.java:959) 


at
org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisServiceBuilder.java:1067) 


at
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:221) 


... 3 more


any clues to fix this problem?
Please help, because I'm stuck in there since monday...

regards, philipp


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








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

Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected

[AS-IT-3-9-20 Loesche, Mathias]

Hello,

as I've read in other posts there resson can be a false wsdd file which 
does not match to the gotten soap xml. I've generated the wsdl with the 
axis Admin client with the following wsdd file



http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>

use="literal">


















using the command line
java -classpath $AXISCLASSPATH org.apache.axis.client.AdminClient -l 
http://127.0.0.1:8080/axis/servlet/AxisServlet deploy_service.wsdd


That generates the following wsdl:

targetNamespace="http://localhost:8080/axis/services/HelloWorldXmlEnc";>

−

−

−
http://aa";>


−
targetNamespace="http://localhost:8080/axis/services/HelloWorldXmlEnc";>




−



−



−

−





−

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

−


−



−





−

−
name="HelloWorldXmlEnc">
location="http://localhost:8080/axis/services/HelloWorldXmlEnc"/>





Please, if anybody as an idea where to look respond .

Regards
Mathias


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

[Axis2] Passing complex type HashMap

[Sathija Pavuluri]

Hello,

I need to pass a HashMap as one of the parameters to my web service call.
How can I do that?

Thanks,
Sathija.


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

RE: Axis2 HTTPS client error: Parser already accessed!

[Lee, Michael]

Davanum Srinivas wrote:

> Do you send any login information. Do you use the 
> HttpTransportProperties.Authenticator to set any user name password?
> If you do, HttpTransportProperties.Authenticator has a 
> setAllowedRetry flag, please try switching that on.

I do not send any login information. I just need to use HTTPS for
secure transport.

> thanks,
> dims

Thanks,

Mike


This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

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

RE: SOAPMonitor query

[Kedar Ambekar]

Thanks for replying Kinichiro..

As per my understanding, client needs to direct the request to TCPMON &
server address needs to be specified to TCPMON.
For this I need to change both the apps all the time to direct messages
towards TCPMON whenever I have to see the messages. That is not
possible.

Is there any option which is similar to seeing SOAP messages on the wire
?Capture tools won't capture packets exchanged on the same machine. 

Regards,
Kedar

-Original Message-
From: Kinichiro Inoguchi [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 09, 2006 7:40 PM
To: axis-user@ws.apache.org
Subject: Re: SOAPMonitor query

Hi Kedar,

How about using TCPMON ?
http://www.apache.org/dist/ws/commons/tcpmon/1_0/

--- Kedar Ambekar <[EMAIL PROTECTED]> wrote:

> 
> Hi All,
>  
> I have 2 web-applications which talk to each other over web-service in

> both the directions.The applications use AXIS 1.4 & are deployed on 
> Tomcat 5.
> I want to use SOAPMonitor to see the SOAP messages getting exchanged 
> between 2 apps.
>  
> Is it possible to use SOAPMonitor as a separate application outside my

> 2 applications?
>  
> To make it generic, can Axis handler be part of separate application 
> outside a web-application exposing web service interface?
>  
> Thanks,
> Kedar



Tech Mahindra, formerly Mahindra-British Telecom.
 
Disclaimer:

This message and the information contained herein is proprietary and 
confidential and subject to the Tech Mahindra policy statement, you may review 
at http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html
 externally and http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html
 internally within Tech Mahindra.



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

Re: [Axis2] Help using AXIOMXPath

[Brian Bacsu]

Gul

Thanks, placing the message in an OMDocument
seems to work.

Brian Bacsu







"Gul Onural"
<[EMAIL PROTECTED]> 
11/08/2006 08:50 PM



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





To
Brian Bacsu/FSG/[EMAIL PROTECTED]


cc



Subject
Re: [Axis2] Help using AXIOMXPath








Brian, 
Similar to the following code worked for me.
Please give it a try. Note that I am using Axis2 RC1.1 nightly, but you
need to try to see if it makes any difference. If it does then you may
need to upgrade to nightly:
        AXIOMXPath xpathExp
= null; 
        OMFactory fac = OMAbstractFactory.getOMFactory();

        OMDocument doc = fac.createOMDocument();

        doc.addChild(OM_Message);

        try {

            xpathExp = new AXIOMXPath(yourXpathString);

            xpathExp.addNamespace("whatever");

            OMElement selectedNode = (OMElement)
xpathExp.selectSingleNode(doc); 
            if (selectedNode != null) {

                System.out

                    
   .println("my node : " + selectedNode.getText() +
'\n'); 
            } 
        } catch (JaxenException e) {

           ... 
        } 

Re: SOAPMonitor query

[Kinichiro Inoguchi]

Hi Kedar,

How about using TCPMON ?
http://www.apache.org/dist/ws/commons/tcpmon/1_0/

--- Kedar Ambekar <[EMAIL PROTECTED]> wrote:

> 
> Hi All,
>  
> I have 2 web-applications which talk to each other over web-service
> in
> both the directions.The applications use AXIS 1.4 & are deployed on
> Tomcat 5.
> I want to use SOAPMonitor to see the SOAP messages getting exchanged
> between 2 apps.
>  
> Is it possible to use SOAPMonitor as a separate application outside
> my 2
> applications?
>  
> To make it generic, can Axis handler be part of separate application
> outside a web-application exposing web service interface?
>  
> Thanks,
> Kedar
> 
> 
>

> 
> Tech Mahindra, formerly Mahindra-British Telecom.
>  
> Disclaimer:
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Tech Mahindra policy statement, you
> may review at 
href="http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html
> externally and 
href="http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html
> internally within Tech Mahindra.
> 
>




 

Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

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

Re: Axis2 HTTPS client error: Parser already accessed!

[Davanum Srinivas]

Martin,

please see my email on this thread :) No need to hack the code (hopefully!)

-- dims

On 11/9/06, Martin Gainty <[EMAIL PROTECTED]> wrote:

Mike-

Most probably an unhandled exception when OMElement serializes..a solution is 
available at
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200606.mbox/[EMAIL 
PROTECTED]

Anyone else?
M-
This e-mail communication and any attachments may contain confidential and 
privileged information for the use of the
designated recipients named above. If you are not the intended recipient, you 
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination, 
distribution or copying of it or its
contents
- Original Message -
From: "Lee, Michael" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, November 09, 2006 8:54 AM
Subject: Axis2 HTTPS client error: Parser already accessed!



Problem:

  I am trying to use HTTPS for the client side of an Axis2 web-service.

  Running the service over HTTP works fine. I am currently configuring
the client
  use http by setting the targetEndPoint as
  "https://localhost:8443/axis2/services/billing"; in my client Stub
(generated using
  WSDL2Java).

  But when I try to use HTTPS,  an exception is thrown by the client.

  The error seems to be very similar to the bug (AXIS2-1380) where the
error was caused by
  calling a service through a proxy.  However I am not using a proxy.

  I am trying to determine if this is a problem with my code, with
Tomcat or with Axis2.

  Has anyone else come across this problem?


Platform:

Java JDK 1.5.0_09
Tomcat 5.5.17 (non-native mode) (cannot use native DDL with HTTPS
due to Tomcat bug)
Axis2.0 version 1.0
Windows XP SP2

Keystore and Tomcat configuration:

  I generated the keystore using the instructions on the Tomcat website
  (http://tomcat.apache.org/tomcat-5.0-doc/ssl-howto.html)

  The command issued was:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA

The generated keystore file was then copied to the Tomcat conf
directory.

The Tomcat server.xml was configured as follows:





Exception thrown by Axis2 client:

Refund In Transaction ID: TRANS912397548D
Exception in thread "main" xxx.xxx.xxx.xxx.xxx.billing.BillingException:
Problem refunding transaction Id: TRANS912397548D to service:
https://localhost:8443/axis2/services/billing
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:133)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.refund(TestAxisB
illingService.java:46)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.main(TestAxisBil
lingService.java:107)
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:223)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyA
xisOperation.java:352)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.generated.BillingStub.refund(BillingStu
b.java:156)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:130)
... 2 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
ithCommons(CommonsHTTPTransportSender.java:305)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:207)
... 6 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.ax

Re: Axis2 HTTPS client error: Parser already accessed!

[Martin Gainty]

Mike-

Most probably an unhandled exception when OMElement serializes..a solution is 
available at
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200606.mbox/[EMAIL 
PROTECTED]

Anyone else?
M-
This e-mail communication and any attachments may contain confidential and 
privileged information for the use of the 
designated recipients named above. If you are not the intended recipient, you 
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination, 
distribution or copying of it or its 
contents
- Original Message - 
From: "Lee, Michael" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, November 09, 2006 8:54 AM
Subject: Axis2 HTTPS client error: Parser already accessed!



Problem:
 
  I am trying to use HTTPS for the client side of an Axis2 web-service.

  Running the service over HTTP works fine. I am currently configuring
the client
  use http by setting the targetEndPoint as 
  "https://localhost:8443/axis2/services/billing"; in my client Stub
(generated using
  WSDL2Java).
 
  But when I try to use HTTPS,  an exception is thrown by the client.

  The error seems to be very similar to the bug (AXIS2-1380) where the
error was caused by
  calling a service through a proxy.  However I am not using a proxy.
 
  I am trying to determine if this is a problem with my code, with
Tomcat or with Axis2.
 
  Has anyone else come across this problem?


Platform:
 
Java JDK 1.5.0_09
Tomcat 5.5.17 (non-native mode) (cannot use native DDL with HTTPS
due to Tomcat bug)
Axis2.0 version 1.0
Windows XP SP2
 
Keystore and Tomcat configuration:
 
  I generated the keystore using the instructions on the Tomcat website 
  (http://tomcat.apache.org/tomcat-5.0-doc/ssl-howto.html)
 
  The command issued was:
 
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
 
The generated keystore file was then copied to the Tomcat conf
directory.

The Tomcat server.xml was configured as follows:
 


 

Exception thrown by Axis2 client:
 
Refund In Transaction ID: TRANS912397548D
Exception in thread "main" xxx.xxx.xxx.xxx.xxx.billing.BillingException:
Problem refunding transaction Id: TRANS912397548D to service:
https://localhost:8443/axis2/services/billing
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:133)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.refund(TestAxisB
illingService.java:46)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.main(TestAxisBil
lingService.java:107)
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:223)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyA
xisOperation.java:352)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.generated.BillingStub.refund(BillingStu
b.java:156)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:130)
... 2 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
ithCommons(CommonsHTTPTransportSender.java:305)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:207)
... 6 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity
.writeRequest(SOAPOverHTTPSender.java:194)
at
org.apache.

Re: [Axis2] How to forward results?

[Michele Mazzucco]

jira AXIS2-1658 created

michele

Davanum Srinivas wrote:
> yep. that's the only release we made to date :) all the RC's  for 1.1
> are release candidates
> 
> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> Here http://archive.apache.org/dist/ws/axis2/ there's only the 1.0
>> version.
>>
>> Michele
>>
>> Michele Mazzucco wrote:
>> > Dims,
>> >
>> > where can I can an old version of axis2?, just to figure out what the
>> > problem is
>> >
>> >
>> > Thanks,
>> > Michele
>> >
>> > Davanum Srinivas wrote:
>> >> Michele,
>> >>
>> >> You know the drill :) JIRA + Sample code please.
>> >>
>> >> -- dims
>> >>
>> >> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> >>> Hi all,
>> >>>
>> >>> I'm not able to forward a result to an EPR different from where the
>> >>> original message comes from. I'll try to explain better:
>> >>> I've node A (client) which sends a message to node B (in-only with
>> >>> addressing informations), which in turn sends a different message
>> to a
>> >>> node C.
>> >>> When the result is ready, node C sends it to node B, which (I'm
>> >>> simplifying) should send the result to node A.
>> >>> Now, until now I've been using a RawXMLINOutMessageReceiver message
>> >>> receiver, while the method signature was
>> >>>
>> >>> void result(OMElement)
>> >>>
>> >>> and it used to work by using
>> >>>
>> >>> options.setRelationships + the A's EPR. But now I get an AxisFault
>> >>> saying an operation with the signature OMElement result(OMElement)
>> does
>> >>> not exist.
>> >>> I've tried to change the message receiver to in-only, but if I do
>> this
>> >>> the forward operation is ignored (see also the
>> >>> RawXMLInOnlyMessageReceiver java doc).
>> >>>
>> >>>
>> >>> This issue has been discussed several times (i.e. [1, 2]) on this
>> >>> mailing list and the result was that it's actually possible.
>> >>>
>> >>>
>> >>> Any clue?
>> >>>
>> >>>
>> >>> Michele
>> >>>
>> >>>
>> >>>
>> >>> [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
>> >>> [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >>> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>>
>> >>>
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

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

Re: Axis2 HTTPS client error: Parser already accessed!

[Davanum Srinivas]

Do you send any login information. Do you use the
HttpTransportProperties.Authenticator to set any user name password?
If you do, HttpTransportProperties.Authenticator has a setAllowedRetry
flag, please try switching that on.

thanks,
dims

On 11/9/06, Lee, Michael <[EMAIL PROTECTED]> wrote:


Problem:

  I am trying to use HTTPS for the client side of an Axis2 web-service.

  Running the service over HTTP works fine. I am currently configuring
the client
  use http by setting the targetEndPoint as
  "https://localhost:8443/axis2/services/billing"; in my client Stub
(generated using
  WSDL2Java).

  But when I try to use HTTPS,  an exception is thrown by the client.

  The error seems to be very similar to the bug (AXIS2-1380) where the
error was caused by
  calling a service through a proxy.  However I am not using a proxy.

  I am trying to determine if this is a problem with my code, with
Tomcat or with Axis2.

  Has anyone else come across this problem?


Platform:

Java JDK 1.5.0_09
Tomcat 5.5.17 (non-native mode) (cannot use native DDL with HTTPS
due to Tomcat bug)
Axis2.0 version 1.0
Windows XP SP2

Keystore and Tomcat configuration:

  I generated the keystore using the instructions on the Tomcat website
  (http://tomcat.apache.org/tomcat-5.0-doc/ssl-howto.html)

  The command issued was:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA

The generated keystore file was then copied to the Tomcat conf
directory.

The Tomcat server.xml was configured as follows:





Exception thrown by Axis2 client:

Refund In Transaction ID: TRANS912397548D
Exception in thread "main" xxx.xxx.xxx.xxx.xxx.billing.BillingException:
Problem refunding transaction Id: TRANS912397548D to service:
https://localhost:8443/axis2/services/billing
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:133)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.refund(TestAxisB
illingService.java:46)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.main(TestAxisBil
lingService.java:107)
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:223)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyA
xisOperation.java:352)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.generated.BillingStub.refund(BillingStu
b.java:156)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:130)
... 2 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is:
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
ithCommons(CommonsHTTPTransportSender.java:305)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:207)
... 6 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is:
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity
.writeRequest(SOAPOverHTTPSender.java:194)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest
Body(EntityEnclosingMethod.java:495)
at
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase
.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java
:993)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe
thodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho
dDirector.java:1

SOAPMonitor query

[Kedar Ambekar]

Hi 
All,
 
I 
have 2 web-applications which talk to each other over web-service in both the 
directions.The applications use AXIS 1.4 & are deployed on Tomcat 
5.
I 
want to use SOAPMonitor to see the SOAP messages getting exchanged between 2 
apps.
 
Is it 
possible to use SOAPMonitor as a separate application outside my 2 
applications?
 
To 
make it generic, can Axis handler be part of separate application 
outside a web-application exposing web service interface?
 
Thanks,
Kedar



Tech Mahindra, formerly Mahindra-British Telecom.
 
Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review at http://www.techmahindra.com/Disclaimer.html externally and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.

RE: problem with https

[subir.sasikumar]

Hi Abid,

Welcome.

I doubt Point 3 of your mail.

Are you telling regarding http://x.y.z.w/services/ />

I don't think you have to manually change this.

You can check once with out manually changing this URL and accessing
your service from your server.

If you notice, the stubs generated should have a option where you can
override the targetEndPointAddress with another URL.

Please do correct me if I am wrong.

Thanks,
Subir S

-Original Message-
From: Abid Hussain [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 7:16 PM
To: axis-user@ws.apache.org
Subject: Re: problem with https

Hi Subir,

thanks a lot for helping me.

It worked like you said:
1. Install the webservice locally using java2wsdl and wsdl2java.
2. Deploy the service locally using the AdminClient (which lets Axis
generate the server-config.wsdd).
3. Change the service-URL in wsdl and ServiceLocator from local URL to
remote URL.
4. Build a war and install it on the remote server.

It seems that one needs a running server to let Axis generate the
server-config.wsdd what I think is a bit unhandy - because you have to
change the service-URL by hand after deploying it locally there is no
elegant way to do the deployment completely automatically.

Maybe it's easier with Axis2 - however, I'm glad that it now works.

Best regards,

Abid

[EMAIL PROTECTED] schrieb:
> Hi Abid,
>
> You can use the deploy.wsdd that may be generated using your java2wsdl
> task. (with option -s or -S..i don't remember exactly).
> Now deploy your web services using the deployment ant task that you
use.
> This would generate a new WEB-INF/server-config.wsdd file with your
> latest service changes (it appends your service changes). Now just
make
> a war file of this (including the server-config and install in your
> server. This means that already the configuration of the services to
be
> deployed would be part of your war file.
>
> So then it will be automatically deployed when your server starts up.
>
> I hope this helps.
>
> Regards,
> Subir S
>
> -Original Message-
> From: Abid Hussain [mailto:[EMAIL PROTECTED]
>
> Sent: Monday, November 06, 2006 7:33 PM
> To: axis-user@ws.apache.org
> Subject: Re: problem with https
>
> Hi again,
>
> thanks for giving me the hint to enable the remote administration.
>
> As I said, I'm new to Axis and maybe I have misunderstood the
deployment
>
> of services.
>
> Like I described below, I deploy the service in the following order:
> 1. Install the webservice in my webapp using java2wsdl and wsdl2java.
> 2. Install the webapp-war on the remote server.
> 3. Deploy the service by remote access using
>
> org.apache.axis.client.AdminClient.
>
> Is it possible to deploy the service locally BEFORE installing the
>
> webapp on the remote server? Like this:
> 1. Install the webservice in my webapp using java2wsdl and wsdl2java.
> 2. Deploy the service in the webapp.
> 3. Install the webapp-war on the remote server.
>
> Because then, the problem maybe would be solved easily.
>
> Regards,
>
> Abid
>
> [EMAIL PROTECTED] schrieb:
>> Hi Abid,
>>
>
>
>
>> /Oops I really misread your query. I thought you said that you cannot
>
>> access the webservices deployed in https enabled server./
>>
>
>
>
>> Well for your query [I hope you are not able to deploy your
> webservices
>
>> from a remote place], please enable the remote admin related
parameter
>
>> for the adminservice in server-config.wsdd
>>
>
>
>
>> 
>>
>
>>   
>>
>
>> *   [This is
> default
>
>> 'false' for security. Make it 'true' in your server]*
>>
>
>>   
>>
>
>>   http://xml.apache.org/axis/wsdd/
>>
>
>>  
>>
>
>
>
>> I hope this helps.
>>
>
>
>
>> Thanks
>>
>
>> Subir
>>
>
>
>
>> -Original Message-
>> From: Abid Hussain [mailto:[EMAIL PROTECTED]
>> Sent: Monday, November 06, 2006 5:46 PM
>> To: axis-user@ws.apache.org
>> Subject: Re: problem with https
>>
>
>
>
>> Hallo again,
>>
>
>
>
>> thanks for helping me.
>>
>
>
>
>>>  Is it a standard server, third party server (I mean the
certificates
> are
>
>>>  standard ones)?
>
>> Actually I'm not sure, what you mean by standard respectively third
>>
>
>> party server. It's a Tomcat 5.5 and it's using a Thawte Certificate.
>>
>
>>>  OR
>
>>>  Is it a test server (where you might have generated the test server
>
>>>  certificate)?
>
>> No, it's not a test server.
>>
>
>
>>>  One more thing is your server expecting client authentication also?
>
>> The server is inside a VPN. But the machine which I'm trying tor run
> the
>
>> deployment from is part of the VPN. Besides from this, there is no
>>
>
>> authentication necessary.
>>
>
>
>
>> I don't know if it's important for the subject, but here is the
> relevant
>
>> part from the web.xml.
>>
>
>
>
>> 
>>
>
>> 
>>
>
>>   
>>
>
>>   
>>
>
>>
>>
>
>>Apache-Axis Servlet
>>
>
>>AxisServlet
>>
>
>>
>>
>
>>  
>
>> org.apache.axis.transport.http.AxisServlet
>>

Re: [Axis2] How to forward results?

[Davanum Srinivas]

yep. that's the only release we made to date :) all the RC's  for 1.1
are release candidates

On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:

Here http://archive.apache.org/dist/ws/axis2/ there's only the 1.0 version.

Michele

Michele Mazzucco wrote:
> Dims,
>
> where can I can an old version of axis2?, just to figure out what the
> problem is
>
>
> Thanks,
> Michele
>
> Davanum Srinivas wrote:
>> Michele,
>>
>> You know the drill :) JIRA + Sample code please.
>>
>> -- dims
>>
>> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>>> Hi all,
>>>
>>> I'm not able to forward a result to an EPR different from where the
>>> original message comes from. I'll try to explain better:
>>> I've node A (client) which sends a message to node B (in-only with
>>> addressing informations), which in turn sends a different message to a
>>> node C.
>>> When the result is ready, node C sends it to node B, which (I'm
>>> simplifying) should send the result to node A.
>>> Now, until now I've been using a RawXMLINOutMessageReceiver message
>>> receiver, while the method signature was
>>>
>>> void result(OMElement)
>>>
>>> and it used to work by using
>>>
>>> options.setRelationships + the A's EPR. But now I get an AxisFault
>>> saying an operation with the signature OMElement result(OMElement) does
>>> not exist.
>>> I've tried to change the message receiver to in-only, but if I do this
>>> the forward operation is ignored (see also the
>>> RawXMLInOnlyMessageReceiver java doc).
>>>
>>>
>>> This issue has been discussed several times (i.e. [1, 2]) on this
>>> mailing list and the result was that it's actually possible.
>>>
>>>
>>> Any clue?
>>>
>>>
>>> Michele
>>>
>>>
>>>
>>> [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
>>> [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

WSDL generation: Please, help

[JabberW]

Hi all.
I'll try to represent my question very clear - my previous attempt
left unanswered
(http://marc.theaimsgroup.com/?l=axis-user&m=116300481013374&w=2).

Say, I have a simple service to expose:
  class MySvc {
   public String myOp(Data_A)
  } // class MySvc

where:
   public class Data_A {
  public  void setVal_1(String s){}
  public String getVal_1(){}
   }. // class Data_A

There is an additional data type may be received as an argument: the
Data_A class extender:
   public class Data_B extends Data_A {
  public void setVal_2(String s){}
  public String getVal_2(){}
   } // class Data_B

To add this type generation I have to add it as an extra-class. So,
the command I have to run is:

java2wsdl.bat -cp classes/  -o . -cn MySvc -xc Data_B.


BUT. There is no the   element in the
Data_B definition, generated by Java2WSDL is:
 




 
So this type can't be sent within a request.

What is my mistake? How can this issue be solved? I beleive I should
specify any additional flags in the command line?
Note: Axis 1.2.1 I used till now handles this issue pretty well.

Greatly appreciate any inputs,
Sincerely,
Alex

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

Axis2 HTTPS client error: Parser already accessed!

[Lee, Michael]

Problem:
 
  I am trying to use HTTPS for the client side of an Axis2 web-service.

  Running the service over HTTP works fine. I am currently configuring
the client
  use http by setting the targetEndPoint as 
  "https://localhost:8443/axis2/services/billing"; in my client Stub
(generated using
  WSDL2Java).
 
  But when I try to use HTTPS,  an exception is thrown by the client.

  The error seems to be very similar to the bug (AXIS2-1380) where the
error was caused by
  calling a service through a proxy.  However I am not using a proxy.
 
  I am trying to determine if this is a problem with my code, with
Tomcat or with Axis2.
 
  Has anyone else come across this problem?


Platform:
 
Java JDK 1.5.0_09
Tomcat 5.5.17 (non-native mode) (cannot use native DDL with HTTPS
due to Tomcat bug)
Axis2.0 version 1.0
Windows XP SP2
 
Keystore and Tomcat configuration:
 
  I generated the keystore using the instructions on the Tomcat website 
  (http://tomcat.apache.org/tomcat-5.0-doc/ssl-howto.html)
 
  The command issued was:
 
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
 
The generated keystore file was then copied to the Tomcat conf
directory.

The Tomcat server.xml was configured as follows:
 


 

Exception thrown by Axis2 client:
 
Refund In Transaction ID: TRANS912397548D
Exception in thread "main" xxx.xxx.xxx.xxx.xxx.billing.BillingException:
Problem refunding transaction Id: TRANS912397548D to service:
https://localhost:8443/axis2/services/billing
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:133)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.refund(TestAxisB
illingService.java:46)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.TestAxisBillingService.main(TestAxisBil
lingService.java:107)
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:223)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyA
xisOperation.java:352)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.generated.BillingStub.refund(BillingStu
b.java:156)
at
xxx.xxx.xxx.xxx.xxx.billing.axis.AxisBillingService.refund(AxisBillingSe
rvice.java:130)
... 2 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!; nested exception is: 
org.apache.axis2.AxisFault: problem accessing the parser. Parser
already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
ithCommons(CommonsHTTPTransportSender.java:305)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common
sHTTPTransportSender.java:207)
... 6 more
Caused by: org.apache.axis2.AxisFault: problem accessing the parser.
Parser already accessed!; nested exception is: 
javax.xml.stream.XMLStreamException: problem accessing the parser.
Parser already accessed!
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity
.writeRequest(SOAPOverHTTPSender.java:194)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest
Body(EntityEnclosingMethod.java:495)
at
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase
.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java
:993)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe
thodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho
dDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3
96)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3
46)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac
tHTTPSender.java:

Re: [Axis2] How to forward results?

[Davanum Srinivas]

that's the problem with nightly builds, once the next build is done,
we lose the old one...unless it is 1.0 you are looking for, you will
need to get the code from svn based on either a revision # or a date
and build it yourself.

thanks,
dims

On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:

Dims,

where can I can an old version of axis2?, just to figure out what the
problem is


Thanks,
Michele

Davanum Srinivas wrote:
> Michele,
>
> You know the drill :) JIRA + Sample code please.
>
> -- dims
>
> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I'm not able to forward a result to an EPR different from where the
>> original message comes from. I'll try to explain better:
>> I've node A (client) which sends a message to node B (in-only with
>> addressing informations), which in turn sends a different message to a
>> node C.
>> When the result is ready, node C sends it to node B, which (I'm
>> simplifying) should send the result to node A.
>> Now, until now I've been using a RawXMLINOutMessageReceiver message
>> receiver, while the method signature was
>>
>> void result(OMElement)
>>
>> and it used to work by using
>>
>> options.setRelationships + the A's EPR. But now I get an AxisFault
>> saying an operation with the signature OMElement result(OMElement) does
>> not exist.
>> I've tried to change the message receiver to in-only, but if I do this
>> the forward operation is ignored (see also the
>> RawXMLInOnlyMessageReceiver java doc).
>>
>>
>> This issue has been discussed several times (i.e. [1, 2]) on this
>> mailing list and the result was that it's actually possible.
>>
>>
>> Any clue?
>>
>>
>> Michele
>>
>>
>>
>> [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
>> [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Re: [Axis2] How to forward results?

[Michele Mazzucco]

Here http://archive.apache.org/dist/ws/axis2/ there's only the 1.0 version.

Michele

Michele Mazzucco wrote:
> Dims,
> 
> where can I can an old version of axis2?, just to figure out what the
> problem is
> 
> 
> Thanks,
> Michele
> 
> Davanum Srinivas wrote:
>> Michele,
>>
>> You know the drill :) JIRA + Sample code please.
>>
>> -- dims
>>
>> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>>> Hi all,
>>>
>>> I'm not able to forward a result to an EPR different from where the
>>> original message comes from. I'll try to explain better:
>>> I've node A (client) which sends a message to node B (in-only with
>>> addressing informations), which in turn sends a different message to a
>>> node C.
>>> When the result is ready, node C sends it to node B, which (I'm
>>> simplifying) should send the result to node A.
>>> Now, until now I've been using a RawXMLINOutMessageReceiver message
>>> receiver, while the method signature was
>>>
>>> void result(OMElement)
>>>
>>> and it used to work by using
>>>
>>> options.setRelationships + the A's EPR. But now I get an AxisFault
>>> saying an operation with the signature OMElement result(OMElement) does
>>> not exist.
>>> I've tried to change the message receiver to in-only, but if I do this
>>> the forward operation is ignored (see also the
>>> RawXMLInOnlyMessageReceiver java doc).
>>>
>>>
>>> This issue has been discussed several times (i.e. [1, 2]) on this
>>> mailing list and the result was that it's actually possible.
>>>
>>>
>>> Any clue?
>>>
>>>
>>> Michele
>>>
>>>
>>>
>>> [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
>>> [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

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

Re: [Axis2] How to forward results?

[Michele Mazzucco]

Dims,

where can I can an old version of axis2?, just to figure out what the
problem is


Thanks,
Michele

Davanum Srinivas wrote:
> Michele,
> 
> You know the drill :) JIRA + Sample code please.
> 
> -- dims
> 
> On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I'm not able to forward a result to an EPR different from where the
>> original message comes from. I'll try to explain better:
>> I've node A (client) which sends a message to node B (in-only with
>> addressing informations), which in turn sends a different message to a
>> node C.
>> When the result is ready, node C sends it to node B, which (I'm
>> simplifying) should send the result to node A.
>> Now, until now I've been using a RawXMLINOutMessageReceiver message
>> receiver, while the method signature was
>>
>> void result(OMElement)
>>
>> and it used to work by using
>>
>> options.setRelationships + the A's EPR. But now I get an AxisFault
>> saying an operation with the signature OMElement result(OMElement) does
>> not exist.
>> I've tried to change the message receiver to in-only, but if I do this
>> the forward operation is ignored (see also the
>> RawXMLInOnlyMessageReceiver java doc).
>>
>>
>> This issue has been discussed several times (i.e. [1, 2]) on this
>> mailing list and the result was that it's actually possible.
>>
>>
>> Any clue?
>>
>>
>> Michele
>>
>>
>>
>> [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
>> [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

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

Re: problem with https

[Abid Hussain]

Hi Subir,

thanks a lot for helping me.

It worked like you said:
1. Install the webservice locally using java2wsdl and wsdl2java.
2. Deploy the service locally using the AdminClient (which lets Axis 
generate the server-config.wsdd).
3. Change the service-URL in wsdl and ServiceLocator from local URL to 
remote URL.

4. Build a war and install it on the remote server.

It seems that one needs a running server to let Axis generate the 
server-config.wsdd what I think is a bit unhandy - because you have to 
change the service-URL by hand after deploying it locally there is no 
elegant way to do the deployment completely automatically.


Maybe it's easier with Axis2 - however, I'm glad that it now works.

Best regards,

Abid

[EMAIL PROTECTED] schrieb:

Hi Abid,

You can use the deploy.wsdd that may be generated using your java2wsdl
task. (with option -s or -S..i don't remember exactly).
Now deploy your web services using the deployment ant task that you use.
This would generate a new WEB-INF/server-config.wsdd file with your
latest service changes (it appends your service changes). Now just make
a war file of this (including the server-config and install in your
server. This means that already the configuration of the services to be
deployed would be part of your war file.

So then it will be automatically deployed when your server starts up.

I hope this helps.

Regards,
Subir S

-Original Message-
From: Abid Hussain [mailto:[EMAIL PROTECTED]

Sent: Monday, November 06, 2006 7:33 PM
To: axis-user@ws.apache.org
Subject: Re: problem with https

Hi again,

thanks for giving me the hint to enable the remote administration.

As I said, I'm new to Axis and maybe I have misunderstood the deployment

of services.

Like I described below, I deploy the service in the following order:
1. Install the webservice in my webapp using java2wsdl and wsdl2java.
2. Install the webapp-war on the remote server.
3. Deploy the service by remote access using

org.apache.axis.client.AdminClient.

Is it possible to deploy the service locally BEFORE installing the

webapp on the remote server? Like this:
1. Install the webservice in my webapp using java2wsdl and wsdl2java.
2. Deploy the service in the webapp.
3. Install the webapp-war on the remote server.

Because then, the problem maybe would be solved easily.

Regards,

Abid

[EMAIL PROTECTED] schrieb:

Hi Abid,






/Oops I really misread your query. I thought you said that you cannot



access the webservices deployed in https enabled server./






Well for your query [I hope you are not able to deploy your

webservices


from a remote place], please enable the remote admin related parameter



for the adminservice in server-config.wsdd











  




*   [This is

default


'false' for security. Make it 'true' in your server]*




  




  http://xml.apache.org/axis/wsdd/




 






I hope this helps.






Thanks




Subir






-Original Message-
From: Abid Hussain [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 5:46 PM
To: axis-user@ws.apache.org
Subject: Re: problem with https






Hallo again,






thanks for helping me.






 Is it a standard server, third party server (I mean the certificates

are


 standard ones)?



Actually I'm not sure, what you mean by standard respectively third




party server. It's a Tomcat 5.5 and it's using a Thawte Certificate.




 OR



 Is it a test server (where you might have generated the test server



 certificate)?



No, it's not a test server.





 One more thing is your server expecting client authentication also?



The server is inside a VPN. But the machine which I'm trying tor run

the


deployment from is part of the VPN. Besides from this, there is no




authentication necessary.






I don't know if it's important for the subject, but here is the

relevant


part from the web.xml.
















  




  




   




   Apache-Axis Servlet




   AxisServlet




   



  



org.apache.axis.transport.http.AxisServlet




  




  




   




   Axis Admin Servlet




   AdminServlet




   



  



org.apache.axis.transport.http.AdminServlet




   100




  






  






  




   AxisServlet




   /servlet/AxisServlet




  




  




   AxisServlet




   *.jws




  




  




   AxisServlet




   /services/*




  




  




   AdminServlet




   /servlet/AdminServlet




  




  











Best regards,






Abid Hussain







 Regards,



 Subir S




 -Original Message-



 From: Abid Hussain [mailto:[EMAIL PROTECTED]




 Sent: Friday, N

Re: [Axis2] How to forward results?

[Davanum Srinivas]

Michele,

You know the drill :) JIRA + Sample code please.

-- dims

On 11/9/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:

Hi all,

I'm not able to forward a result to an EPR different from where the
original message comes from. I'll try to explain better:
I've node A (client) which sends a message to node B (in-only with
addressing informations), which in turn sends a different message to a
node C.
When the result is ready, node C sends it to node B, which (I'm
simplifying) should send the result to node A.
Now, until now I've been using a RawXMLINOutMessageReceiver message
receiver, while the method signature was

void result(OMElement)

and it used to work by using

options.setRelationships + the A's EPR. But now I get an AxisFault
saying an operation with the signature OMElement result(OMElement) does
not exist.
I've tried to change the message receiver to in-only, but if I do this
the forward operation is ignored (see also the
RawXMLInOnlyMessageReceiver java doc).


This issue has been discussed several times (i.e. [1, 2]) on this
mailing list and the result was that it's actually possible.


Any clue?


Michele



[1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
[2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html

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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Re: problems generating wsdl

[Davanum Srinivas]

replace the DataHandler with a byte[] and see if that helps.

-- dims

On 11/9/06, Philipp Perner <[EMAIL PROTECTED]> wrote:

How do you generate wsdl file?

I have a service class, which has some methods. For example a
datahandler should be returned and a beanclass i designed.
When i generate wsdl file with java2wsdl from command line the generated
wsdl file is invalid and cannot be transformed to service classes by
WSDL2Java.bat:

Command to generate WSDL from Java Code:
java -cp {required libs} org.apache.ws.java2wsdl.Java2WSDL -tn
http://Pseudonymisierung.pseudo.service.axis.healthgate -tp ns -stn
http://Pseudonymisierung.pseudo.service.axis.healthgate/types -stp types
-o ../ -l "http://localhost:8081/axis2/services/"; -sn
"Pseudonymisierung" -cn healthgate.axis.service.pseudo.Pseudonymisierung
-of pseudo.wsdl

--> No error

Command to generate Java Code from WSDL:
D:\Development\eclipse3.2\WebService\WEB-INF>D:\downloads\axis2-1.1-SNAPSHOT\bin\WSDL2Java.bat
-uri pseudo.wsdl -ss -sd -d xmlbeans -o \generated -p
healthgate.axis.service.pseudo.Pseudonymisierung

Using AXIS2_HOME:   D:\downloads\axis2-std-1.0-bin
Using JAVA_HOME:D:\Java\j2sdk1.4.2_12
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory;
nested exception is:
java.lang.RuntimeException: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
at
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87)
... 2 more
Caused by: java.lang.RuntimeException: Schema for namespace
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
at
org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:244)
at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:110)
at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:250)
at
org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuilder.java:959)
at
org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisServiceBuilder.java:1067)
at
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:221)
... 3 more


any clues to fix this problem?
Please help, because I'm stuck in there since monday...

regards, philipp


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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Re: XFire Web Service and Axis Client

[Davanum Srinivas]

Don't use the mime headers, you can set up parameters in the options

http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters

-- dims

On 11/9/06, Marcos <[EMAIL PROTECTED]> wrote:

Hello,

I'm trying to implement a client with Axis for a web service implemented
with XFire. I generate service stubs with any problem and I can login
and call most of the web services but I'm having problems with those
that use XFire cookie based session management.

I need to propagate a remote session id that comes as a cookie on the
HTTP Headers of the response of the login request.

I can access this session id by using the following code:

MimeHeaders headers = stub._getCall().getResponseMessage().getMimeHeaders();
String remoteSessionId = headers.getHeader("set-cookie")[0];

I don't like it but it works, the problem is I haven't found a way to
add this HTTP header to the next request.

I've tried:

MimeHeaders headers = ((Stub) 
port)._getCall().getMessageContext().getRequestMessage().getMimeHeaders();
headers.setHeader("set-cookie", account.getRemoteSessionId());

But the stub creates and invokes the _call object and I can't add
headers to it without modifying the stub. I tried changing _getCall for
_createCall but this doesn't work.

Any help would be appreciated.

Thanks and best regards,
Marcos


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





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

XFire Web Service and Axis Client

[Marcos]

Hello,

I'm trying to implement a client with Axis for a web service implemented
with XFire. I generate service stubs with any problem and I can login
and call most of the web services but I'm having problems with those
that use XFire cookie based session management.

I need to propagate a remote session id that comes as a cookie on the
HTTP Headers of the response of the login request.

I can access this session id by using the following code:

MimeHeaders headers = stub._getCall().getResponseMessage().getMimeHeaders();
String remoteSessionId = headers.getHeader("set-cookie")[0];

I don't like it but it works, the problem is I haven't found a way to
add this HTTP header to the next request.

I've tried:

MimeHeaders headers = ((Stub) 
port)._getCall().getMessageContext().getRequestMessage().getMimeHeaders();
headers.setHeader("set-cookie", account.getRemoteSessionId());

But the stub creates and invokes the _call object and I can't add
headers to it without modifying the stub. I tried changing _getCall for
_createCall but this doesn't work.

Any help would be appreciated.

Thanks and best regards,
Marcos


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

Re: [Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a subelement that doesn't conform to the WSDL

[Davanum Srinivas]

Shahar,

we deferred AXIS2-1606 and hence will defer this as well. Solution for
now is to please use WSDL2Java and use ADB generated code (or any
other data binding). We will deal with this issue immediately after
1.1 release.

thanks,
dims

On 11/9/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:





Hi,



Will this issue be resolved soon? If I can't change the WSDL and change
elements' names then I cannot provide a robust API through my web services.



Thanks and regards,

Shahar Kedar





--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

problems generating wsdl

[Philipp Perner]

How do you generate wsdl file?

I have a service class, which has some methods. For example a 
datahandler should be returned and a beanclass i designed.
When i generate wsdl file with java2wsdl from command line the generated 
wsdl file is invalid and cannot be transformed to service classes by 
WSDL2Java.bat:


Command to generate WSDL from Java Code:
java -cp {required libs} org.apache.ws.java2wsdl.Java2WSDL -tn 
http://Pseudonymisierung.pseudo.service.axis.healthgate -tp ns -stn 
http://Pseudonymisierung.pseudo.service.axis.healthgate/types -stp types 
-o ../ -l "http://localhost:8081/axis2/services/"; -sn 
"Pseudonymisierung" -cn healthgate.axis.service.pseudo.Pseudonymisierung 
-of pseudo.wsdl


--> No error

Command to generate Java Code from WSDL:
D:\Development\eclipse3.2\WebService\WEB-INF>D:\downloads\axis2-1.1-SNAPSHOT\bin\WSDL2Java.bat 
-uri pseudo.wsdl -ss -sd -d xmlbeans -o \generated -p 
healthgate.axis.service.pseudo.Pseudonymisierung


Using AXIS2_HOME:   D:\downloads\axis2-std-1.0-bin
Using JAVA_HOME:D:\Java\j2sdk1.4.2_12
Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94)

   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: Schema for namespace 
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory; 
nested exception is:
   java.lang.RuntimeException: Schema for namespace 
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
   at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243)
   at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87)

   ... 2 more
Caused by: java.lang.RuntimeException: Schema for namespace 
'http://net.java/xsd' already contains type 'URLStreamHandlerFactory
   at 
org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:244)
   at 
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:110)
   at 
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:250)
   at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuilder.java:959)
   at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisServiceBuilder.java:1067)
   at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:221)

   ... 3 more


any clues to fix this problem?
Please help, because I'm stuck in there since monday...

regards, philipp


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

[Axis2] How to forward results?

[Michele Mazzucco]

Hi all,

I'm not able to forward a result to an EPR different from where the
original message comes from. I'll try to explain better:
I've node A (client) which sends a message to node B (in-only with
addressing informations), which in turn sends a different message to a
node C.
When the result is ready, node C sends it to node B, which (I'm
simplifying) should send the result to node A.
Now, until now I've been using a RawXMLINOutMessageReceiver message
receiver, while the method signature was

void result(OMElement)

and it used to work by using

options.setRelationships + the A's EPR. But now I get an AxisFault
saying an operation with the signature OMElement result(OMElement) does
not exist.
I've tried to change the message receiver to in-only, but if I do this
the forward operation is ignored (see also the
RawXMLInOnlyMessageReceiver java doc).


This issue has been discussed several times (i.e. [1, 2]) on this
mailing list and the result was that it's actually possible.


Any clue?


Michele



[1] http://www.mail-archive.com/axis-user@ws.apache.org/msg13338.html
[2] http://www.mail-archive.com/axis-user@ws.apache.org/msg12733.html

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

org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected

[AS-IT-3-9-20 Loesche, Mathias]

Hello,

I've a strange problem using wss4j 1.5.0 with axis 1.4.

During the parsing of the ready encoded soap xml Document the following 
exception occured


2006-11-09 12:03:16,029 DEBUG [http-8080-Processor25] 
org.apache.axis.enterprise: Mapping Exception to AxisFault
org.xml.sax.SAXException: SimpleDeserializer encountered a child 
element, which is NOT expected, in something it was trying to deserialize.
   at 
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)


The soap request is (from the SOAP Mointor)


xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

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

 
   Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>

   http://www.w3.org/2000/09/xmldsig#";>
 
   EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"; 
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";>MIIDljCCAv+gAwIBAgIJALveiiZKbS80MA0GCSqGSIb3DQEBBAUAMIGPMQswCQYDVQQGEwJERTEPMA0GA1UECBMGQmVybGluMQ8wDQYDVQQHEwZCZXJsaW4xCzAJBgNVBAoTAkFBMQ4wDAYDVQQLEwVBQS1DQTEYMBYGA1UEAxMPTWF0aGlhcyBMb2VzY2hlMScwJQYJKoZIhvcNAQkBFhhtYXRoaWFzLmxvZXNjaGVAZGlwbG8uZGUwHhcNMDYxMTAxMDkwMjU1WhcNMDcxMTAxMDkwMjU1WjBkMQswCQYDVQQGEwJERTEPMA0GA1UECBMGQmVybGluMQswCQYDVQQKEwJBQTEdMBsGA1UECxMUQUEgQVMtSVQgRGV2ZWxvcG1lbnQxGDAWBgNVBAMTD01hdGhpYXMgTG9lc2NoZTCBnjANBgkqhkiG9w0BAQEFAAOBjAAwgYgCgYBkBJYNGPfNdcLlhZALTLJ6SfEIH2j/FRtJb4HiCvkVHUXnsTgAbvjkGSa80Ceq+dUNh7xDVMXxs79qhyQauFvpNa9y4Wf1dbeh2bbMGIaBOn/QC4IxehLHsuUYvuSkrofaG4CQqO89Hq+ydyk31hZ0ccl6X5zLj35MEGx6aXtLywIDAQABo4IBIzCCAR8wCQYDVR0TBAIwADAsBglghkgBhvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFJ90VDPPawdT7zDOGPabbR/3TpcNMIHEBgNVHSMEgbwwgbmAFACdWHMtlFU5XPAzfuWj/WNZ+uUsoYGVpIGSMIGPMQswCQYDVQQGEwJERTEPMA0GA1UECBMGQmVybGluMQ8wDQYDVQQHEwZCZXJsaW4xCzAJBgNVBAoTAkFBMQ4wDAYDVQQLEwVBQS1DQTEYMBYGA1UEAxMPTWF0aGlhcyBMb2VzY2hlMScwJQYJKoZIhvcNAQkBFhhtYXRoaWFzLmxvZXNjaGVAZGlwbG8uZGWCCQC73oomSm0vMjANBgkqhkiG9w0BAQQFAAOBgQAKOoiNCh/5nfky1xCnEqiduC22+UyT+/vwzKodxVmARgML2lfQ5x3i8GVVSu2CqDgA8bavUVGJpEHK9qpW/5D58UR6v37V8rFObwzskSY2IO02HjBJG/IilTgMaS5H5gEpvyB1K4uW2RSN5GR6R/mmE3Vrf0CUzGMCE/H3UchlAA==

 
   
   
 
Y0iN+MlvPFgUm8IWx8qThEkReBOEENXAbuNvQv5OVZ4ejm5VQasFaRxk3ZJXAF0uJqdm1ZKKPJlMZU2MiUnxpg50b04nolTHLM24gzZlXrY8ttoSG8wblxnnzkv4mvC7+LNoafJM6rJBckx7As60xr3dLF6cOunzSOK61GG6DMs=

   
   
 
   
 
   
 
 
   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="http://aa";>

 blablabla
   
 



generated with the following Client:

import org.apache.xml.utils.*;

import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.encoding.XMLType;
import org.apache.axis.utils.Options;

import javax.xml.namespace.QName;
import javax.xml.rpc.ParameterMode;

public class cl_HelloWorld
{
  public static void main(String [] args) {
  try {

  Options options = new Options(args);

  String endpointURL =
   "http://127.0.0.1:8080/axis/services/HelloWorldXmlEnc";;

  String textToSend;

   args = options.getRemainingArgs();
   if ((args == null) || (args.length < 1)) {
   textToSend = "";
   } else {
   textToSend = args[0];
   }

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

   call.setTargetEndpointAddress( new java.net.URL(endpointURL) );
   call.setOperationName( new QName("http://aa";, "hallo") );
   call.addParameter( "name", 
org.apache.axis.Constants.XSD_STRING, ParameterMode.IN);

   call.setReturnType(org.apache.axis.Constants.XSD_STRING);

   String ret = (String) call.invoke( new Object[] { textToSend 
} );



  System.out.println( ret );
  } catch (Exception e) {
  System.err.println(e.toString());
  }
  }
}


The encryption and decryption works fine as I can see in the log. The I 
can find the encrypted and later the decrypted soapbody.


When I call a plain service, the generated soap request is:


xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

 
   soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="http://aa";>

 test
   
 


All works fine. I use the same client, except the URL of the service of 
cause.


Here the last messages before the exception occured
8080-Processor25] org.apache.axis.providers.java.RPCProvider: body is 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="http://aa"; 

Re: axis to spring

[robert lazarski]

Do you have this spring bean wired in your serviceContect.xml file?    class="
org.apache.axis2.extensions.spring.receivers.ApplicationContextHolder" />HTH,Robert On 11/9/06, Matthew Hannay <
[EMAIL PROTECTED]> wrote:I am wiring up my aar to be spring aware
and I am asuming that the only partof the doc athttp://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/spring.html
to follow is the part headed "Spring Inside AAR"I follow this and drop my aar in to the axis warand start up the server the app deploys andall the debug suggests that the spring wiring is ok.
However when I run the unit test the server spits it!!444589 [http-8080-Processor25] DEBUGorg.apache.axis2.transport.http.AxisServlet  - org.apache.axis2.AxisFault: Axis2 Can't findSpring's ApplicationContext; ne
sted exception is:java.lang.Exception: Axis2 Can't find Spring'sApplicationContextStructure of aarMyservice.aar-serviceContect.xmllib/axis2spring.jarlib/other spring 
2.0 jarsMETA-INF/services.xmlMETA-INF/service.wsdl/au/.../*.classIn the aar and the axis2/web-inf/lib Ihave removed thespring 1-2-8 jars and replaced them with spring 2.0
I am using the snapshot for 08/11/2006Any clues?MattSend instant messages to your online friends http://au.messenger.yahoo.com-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2]: where to put ? Can't call an ejb from inside a service!

[Andreas Bohnert]

thank you martin for your thoughts.
I have to try this one. looks interresting. I would not ever hit on that!

andreas


Martin Gainty schrieb:
> Hello Andreas-
> described inside the xsd (in Axis 1.x used to be wsdl / and is now 
> -Axis2.xml as in this example
> 
>   targetNamespace="http://java.sun.com/xml/ns/j2ee";
>  xmlns:j2ee="http://java.sun.com/xml/ns/j2ee";
> 
>  you can construct complexTypes based on underlying j2ee referenced objects 
> as in this example
> 
> 
> 
>   
> 
>   
> 
>   
> 
> Later on we can define our own individual elements based on previously 
> described j2ee:descriptionType as in this example..
> 
> type="j2ee:descriptionType"
>  minOccurs="0"
>  maxOccurs="unbounded"/>
> 
> Anyone else?
> M-
> This e-mail communication and any attachments may contain confidential and 
> privileged information for the use of the 
> designated recipients named above. If you are not the intended recipient, you 
> are hereby notified that you have received
> this communication in error and that any review, disclosure, dissemination, 
> distribution or copying of it or its 
> contents
> - Original Message - 
> From: "Andreas Bohnert" <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, November 08, 2006 10:39 AM
> Subject: [Axis2]: where to put ? Can't call an ejb from inside 
> a service!
> 
> 
>> hi,
>>
>> I'm using axis2 0.95 (with geronimo) and I try to call a local ejb from
>> inside my service.
>>
>> to resolve the ejb reference I normally put a  or
>>  to the web.xml if I call from a webapplication or to the
>> ejb-jar.xml, if I call from another ejb.
>>
>> but now I have an aar file with no deployment descriptor! service.xml
>> seems to be not the right place ...
>> well, I could put it to the axis2.war, but I don't want to mess it up
>> with service specific stuff.
>>
>> Is there a nice way todo it?
>>
>> thanks for your help,
>> andreas
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>


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

Re: [Axis2] NullPointerException in org.apache.axis2.transport.http.AxisServlet

[Michele Mazzucco]

jira AXIS2-1655 created.

Michele

Davanum Srinivas wrote:
> Could u please log a bug anyway (with the bad xml). We should not be
> throwing NPE's.
> 
> thanks,
> -- dims
> 
> On 11/8/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> Hi again,
>>
>> I've found out a problem was due to a mis configured services.xml (the
>> message receiver must be declared inside each operation, it is not legal
>> to declare all used message receivers this way:
>>
>> 
>> http://www.w3.org/2004/08/wsdl/in-only";
>>
>> class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
>> http://www.w3.org/2004/08/wsdl/in-out";
>>
>> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>> 
>>
>> and this was the cause of:
>> 2006-11-08 15:18:20,954 [org.apache.axis2.transport.http.AxisServlet] -
>> org.apache.axis2.AxisFault: ServiceClass does not implement required
>> method of the form OMElement addService(OMElement e)
>>
>> but I still have this:
>>
>> DEBUG Phase:invoke - Invoking Handler 'AddressingBasedDispatcher' in
>> Phase 'Dispatch'
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingserviceforepr)
>> DEBUG AddressingBasedDispatcher:findService - Checking for Service using
>> toEPRs address : {0}
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingserviceforepr)
>> DEBUG AddressingBasedDispatcher:findService - Checking for Service using
>> toEPRs address : {0}
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(servicefound)
>> DEBUG AbstractDispatcher:invoke - Found AxisService : RoutingService
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingoperation)
>> DEBUG AddressingBasedDispatcher:findOperation - Checking for Operation
>> using WSAAction : urn:addNode
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(operationfound)
>> DEBUG AbstractDispatcher:invoke - Found AxisOperation : addNode
>> DEBUG Phase:invoke - Invoking Handler 'SOAPMessageBodyBasedDispatcher'
>> in Phase 'Dispatch'
>> DEBUG Phase:invoke - Invoking Handler 'InstanceDispatcher' in Phase
>> 'Dispatch'
>> DEBUG Phase:invoke - Invoking Handler 'AddressingWSDLValidationHandler'
>> in Phase 'Dispatch'
>> DEBUG Phase:invoke - Checking post-conditions for phase "Dispatch"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "OperationInPhase"
>> DEBUG Phase:invoke - Invoking phase "OperationInPhase"
>> DEBUG Phase:invoke - Checking post-conditions for phase
>> "OperationInPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "soapmonitorPhase"
>> DEBUG Phase:invoke - Invoking phase "soapmonitorPhase"
>> DEBUG Phase:invoke - Checking post-conditions for phase
>> "soapmonitorPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase
>> "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Invoking phase "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Invoking Handler 'InFlowManagerHandler' in Phase
>> 'ManagerInterceptorPhase'
>> DEBUG Phase:invoke - Checking post-conditions for phase
>> "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "Transport"
>> DEBUG Phase:invoke - Invoking phase "Transport"
>> DEBUG Phase:invoke - Invoking Handler 'SOAPActionBasedDispatcher' in
>> Phase 'Transport'
>> DEBUG SOAPActionBasedDispatcher:findService - Checking for Service using
>> SOAPAction is a TODO item
>> DEBUG Phase:invoke - Checking post-conditions for phase "Transport"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "Security"
>> DEBUG Phase:invoke - Invoking phase "Security"
>> DEBUG Phase:invoke - Checking post-conditions for phase "Security"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "PreDispatch"
>> DEBUG Phase:invoke - Invoking phase "PreDispatch"
>> DEBUG Phase:invoke - Invoking Handler 'AddressingFinalInHandler' in
>> Phase 'PreDispatch'
>> DEBUG AddressingInHandler:invoke - Starting WS-Addressing Final IN
>> handler ...
>> DEBUG AddressingInHandler:invoke - No Headers present corresponding to
>> WS-Addressing Final
>> DEBUG Phase:invoke - Invoking Handler 'AddressingSubmissionInHandler' in
>> Phase 'PreDispatch'
>> DEBUG AddressingInHandler:invoke - Starting WS-Addressing Submission IN
>> handler ...
>> DEBUG AddressingInHandler:invoke - No Headers present corresponding to
>> WS-Addressing Submission
>> DEBUG Phase:invoke - Checking post-conditions for phase "PreDispatch"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "Dispatch"
>> DEBUG Phase:invoke - Invoking phase "Dispatch"
>> DEBUG Phase:invoke - Invoking Handler 'AddressingBasedDispatcher' in
>> Phase 'Dispatch'
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingserviceforepr)
>> DEBUG AddressingBasedDispatcher:findService - Checking for Service using
>> toEPRs 

RE: FW: Schema question

[Kedar, Shahar]

Thanks!

-Original Message-
From: Bhatra, Junaid [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 16, 2006 8:07 PM
To: axis-user@ws.apache.org
Subject: RE: FW: Schema question

Yes, like Jeff said, you reference an element using "ref" attribute and
you reference a type (simple/complex) using "type" attribute, so there
is no ambiguity as far as schema parsers are concerned.

You can define global elements, types (simple/complex), attributes and
groups in a schema. Each one of these categories is in its own domain
(or namespace, for lack of a better terminology). So you can use the
same name for an element, type, attribute or group. Simple & Complex
types share the same domain, so you cannot simultaneously use the same
name for a simpleType and complexType.

- Junaid

-Original Message-
From: Jeff Greif [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 16, 2006 9:46 AM
To: axis-user@ws.apache.org
Subject: Re: FW: Schema question

A complex type is referenced in schemas using type="ns:my-type-name" 
where ns is a prefix bound to the namespace in which the type is 
designed.  A type and an element may have the same name.  It is not 
possible, I think, for an ambiguity to arise within the XML Schema 
system itself, or in many of the specs which use it, such as WSDL.  You 
can also have attributes and elements with the same name.

However, if you invent an arbitrary attribute that can hold any 
qualified name, such as

   global-attribute-element-or-type-name="ns:some-name"

you'll need some other attribute or element to hold information 
resolving the ambiguity.  The schema parser is not involved in handling 
this, however.  The application must deal with this ambiguity.

Jeff

Kedar, Shahar wrote:
> Ann,
>
> To add to my questions below, how can a schema parser distinguish
> between a reference to an {element} and to a {complexType} if they
have
> the same name? 
>
> Thanks,
> Shahar
>
> -Original Message-
> From: Kedar, Shahar [mailto:[EMAIL PROTECTED] 
> Sent: Monday, October 16, 2006 2:30 PM
> To: axis-user@ws.apache.org
> Subject: RE: Schema question
>
> Hi Ann,
>
> Thanks for the quick answer. Another question:
> The {ref} attribute is used only to refer to a global {element}? Can
it
> be used to refer to a {complexType}? If so, then is it possible to
> define an {element} and a {complexType} with the same name?
>
> Thanks,
> Shahar.
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
> Sent: Monday, October 16, 2006 1:25 PM
> To: axis-user@ws.apache.org
> Subject: Re: Schema question
>
> You may define a particular element only once in a schema, so if the
> element is used in multiple places, you must define it as a global and
> reference it from the various types that use it. (Only global elements
> can be referenced.) Or perhaps you want to allow the element to be
> used both as a root element and as a child element in another element.
>
> Here's an example:
>
> 
> 
> 
>
>
>
>
> 
>
> Anne
>
>
> On 10/15/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote:
>   
>>
>>
>> Hi,
>>
>>
>>
>> Can someone explain to me when and where the {ref} attribute should
be
>> 
> used
>   
>> inside an XML schema? Also, is it valid for an {element} to refer to
a
>> different {element} and not a {type}?
>>
>>
>>
>> Thanks,
>>
>> Shahar.
>> 


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


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


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

[Axis2] JIRA AXIS2-1580 -RPCMessageReceiver returns a subelement that doesn't conform to the WSDL

[Kedar, Shahar]

Hi,

 

Will
this issue be resolved soon? If I can't change the WSDL and change elements'
names then I cannot provide a robust API through my web services.

 

Thanks
and regards,

Shahar
Kedar

 

RE: FW: [Axis2] Incoming message input stream is null when usingRPCInOnlyMessageReceiver

[Kedar, Shahar]

Hi Sanka,

The problem was not completely resolved. I've updated the JIRA.

Shahar.

-Original Message-
From: Sanka Samaranayke [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 07, 2006 7:51 AM
To: axis-user@ws.apache.org
Subject: Re: FW: [Axis2] Incoming message input stream is null when
usingRPCInOnlyMessageReceiver

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Kedar, Shahar wrote:
> Hi,
>
> I've noticed that no one is assigned to this JIRA. I see it as a
> rather big bug. I've uploaded all the information needed for
> reproduction of the bug. Could someone please take a look?

There was a minor error in the services.xml (Please see the comments
on this issue).

Sanka
>
> Thanks, Shahar.
>
> -Original Message- From: Kedar, Shahar
> [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02,
> 2006 12:28 PM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED]
> Subject: RE: [Axis2] Incoming message input stream is null when
> using RPCInOnlyMessageReceiver
>
> Opened a JIRA - AXIS2-1574.
>
> -Original Message- From: Deepal Jayasinghe
> [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 6:26
> AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Incoming
> message input stream is null when using RPCInOnlyMessageReceiver
>
> Hi Kedar; Can you please send me your service aar file or provide
> way to re-generate the issue. Its better if you can create a JIRA
> attaching the service aar file.
>
> Thanks Deepal
>
>> I'm using the RPCInOnlyMessageReceiver for one of my web methods,
>> and I keep getting the following exception:
>>
>> org.apache.axis2.AxisFault: Incoming message input stream is null
>>
>>
>> at
>>
>
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
> ls.java:64)
>> at
>>
>
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
> ation.java:367)
>> at
>>
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
> peration.java:281)
>> at
>>
>
org.apache.ws.axis2.ServiceManagerStub.cancelConnection(ServiceManagerSt
> ub.java:745)
>> at
>>
>
org.apache.ws.axis2.ServiceManagerTest.testcancelConnection(ServiceManag
> erTest.java:143)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>>
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>> at
>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:324)
>>
>> at junit.framework.TestCase.runTest(TestCase.java:154)
>>
>> at junit.framework.TestCase.runBare(TestCase.java:127)
>>
>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>>
>> at junit.framework.TestResult.runProtected(TestResult.java:124)
>>
>> at junit.framework.TestResult.run(TestResult.java:109)
>>
>> at junit.framework.TestCase.run(TestCase.java:118)
>>
>> at junit.framework.TestSuite.runTest(TestSuite.java:208)
>>
>> at junit.framework.TestSuite.run(TestSuite.java:203)
>>
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUn
> it3TestReference.java:128)
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
> va:38)
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
> stRunner.java:460)
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
> stRunner.java:673)
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun
> ner.java:386)
>> at
>>
>
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu
> nner.java:196
>> The Axis2 version is 1.1 RC1. I cannot use the nightly build
>> because of other problems I'm having there. However, if this is a
>> know problem that was solved I will try to move to a newer
>> version.
>>
>> BTW - Is there a date for the next Axis2 release?
>>
>> Thanks,
>>
>> Shahar Kedar
>>
>


- --
Sanka Samaranayake
WSO2 Inc.
T:+94-77-3506382 F:+94-11-2424304

http://sankas.blogspot.com/
http://www.wso2.net/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFFUB68/Hd0ETKdgNIRAuhYAJ9vOW/K3XO+zFDcvFNM/mmXP9rqnwCgk93w
Jl/JiD1mNmIm0gclrecnlrY=
=uBtZ
-END PGP SIGNATURE-


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


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

Re: [Axis2] NullPointerException in org.apache.axis2.transport.http.AxisServlet

[Michele Mazzucco]

Deepal,

as I said in a my previous post, this way I get

2006-11-08 15:18:20,954 [org.apache.axis2.transport.http.AxisServlet] -
org.apache.axis2.AxisFault: ServiceClass does not implement required
method of the form OMElement addService(OMElement e)

where the addService operation has a in-only MEP and the two declared
message receivers were RawXMLINOnlyMessageReceiver and
RawXMLINOutMessageReceiver



Michele

Deepal Jayasinghe wrote:
> Hi Michele;
> 
> You need to add message receivers as follows;
> 
>  
> http://www.w3.org/2004/08/wsdl/in-only";
> 
> class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
> http://www.w3.org/2004/08/wsdl/in-out";
> 
> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> 
> 
> And it is working correctly , pls have a look at the service life cycle
> sample.  And you do not need to specify message receivers at each
> operation level.
> 
> Thanks
> Deepal
> 
> 
>> Hi again,
>>
>> I've found out a problem was due to a mis configured services.xml (the
>> message receiver must be declared inside each operation, it is not legal
>> to declare all used message receivers this way:
>>
>> 
>>http://www.w3.org/2004/08/wsdl/in-only";
>>
>> class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
>>http://www.w3.org/2004/08/wsdl/in-out";
>>
>> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>>
>>
>> and this was the cause of:
>> 2006-11-08 15:18:20,954 [org.apache.axis2.transport.http.AxisServlet] -
>> org.apache.axis2.AxisFault: ServiceClass does not implement required
>> method of the form OMElement addService(OMElement e)
>>
>> but I still have this:
>>
>> DEBUG Phase:invoke - Invoking Handler 'AddressingBasedDispatcher' in
>> Phase 'Dispatch'
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingserviceforepr)
>> DEBUG AddressingBasedDispatcher:findService - Checking for Service using
>> toEPRs address : {0}
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingserviceforepr)
>> DEBUG AddressingBasedDispatcher:findService - Checking for Service using
>> toEPRs address : {0}
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(servicefound)
>> DEBUG AbstractDispatcher:invoke - Found AxisService : RoutingService
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(checkingoperation)
>> DEBUG AddressingBasedDispatcher:findOperation - Checking for Operation
>> using WSAAction : urn:addNode
>> DEBUG ProjectResourceBundle:handleGetObject -
>> org.apache.axis2.i18n.resource::handleGetObject(operationfound)
>> DEBUG AbstractDispatcher:invoke - Found AxisOperation : addNode
>> DEBUG Phase:invoke - Invoking Handler 'SOAPMessageBodyBasedDispatcher'
>> in Phase 'Dispatch'
>> DEBUG Phase:invoke - Invoking Handler 'InstanceDispatcher' in Phase
>> 'Dispatch'
>> DEBUG Phase:invoke - Invoking Handler 'AddressingWSDLValidationHandler'
>> in Phase 'Dispatch'
>> DEBUG Phase:invoke - Checking post-conditions for phase "Dispatch"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "OperationInPhase"
>> DEBUG Phase:invoke - Invoking phase "OperationInPhase"
>> DEBUG Phase:invoke - Checking post-conditions for phase "OperationInPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "soapmonitorPhase"
>> DEBUG Phase:invoke - Invoking phase "soapmonitorPhase"
>> DEBUG Phase:invoke - Checking post-conditions for phase "soapmonitorPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase
>> "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Invoking phase "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Invoking Handler 'InFlowManagerHandler' in Phase
>> 'ManagerInterceptorPhase'
>> DEBUG Phase:invoke - Checking post-conditions for phase
>> "ManagerInterceptorPhase"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "Transport"
>> DEBUG Phase:invoke - Invoking phase "Transport"
>> DEBUG Phase:invoke - Invoking Handler 'SOAPActionBasedDispatcher' in
>> Phase 'Transport'
>> DEBUG SOAPActionBasedDispatcher:findService - Checking for Service using
>> SOAPAction is a TODO item
>> DEBUG Phase:invoke - Checking post-conditions for phase "Transport"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "Security"
>> DEBUG Phase:invoke - Invoking phase "Security"
>> DEBUG Phase:invoke - Checking post-conditions for phase "Security"
>> DEBUG Phase:invoke - Checking pre-condition for Phase "PreDispatch"
>> DEBUG Phase:invoke - Invoking phase "PreDispatch"
>> DEBUG Phase:invoke - Invoking Handler 'AddressingFinalInHandler' in
>> Phase 'PreDispatch'
>> DEBUG AddressingInHandler:invoke - Starting WS-Addressing Final IN
>> handler ...
>> DEBUG AddressingInHandler:invoke - No Headers present corresponding to
>> WS-Addressing Final
>> DEBUG Phase:invoke - Inv

axis to spring

[Matthew Hannay]

I am wiring up my aar to be spring aware
and I am asuming that the only part
of the doc at
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/spring.html
to follow is the part headed "Spring Inside AAR"

I follow this and drop my aar in to the axis war
and start up the server the app deploys and
all the debug suggests that the spring wiring is ok.

However when I run the unit test the server spits it!!
444589 [http-8080-Processor25] DEBUG
org.apache.axis2.transport.http.AxisServlet
  - org.apache.axis2.AxisFault: Axis2 Can't find
Spring's ApplicationContext; ne
sted exception is:
java.lang.Exception: Axis2 Can't find Spring's
ApplicationContext

Structure of aar
Myservice.aar
-
serviceContect.xml
lib/axis2spring.jar
lib/other spring 2.0 jars
META-INF/services.xml
META-INF/service.wsdl
/au/.../*.class
 

In the aar and the axis2/web-inf/lib Ihave removed the

spring 1-2-8 jars and replaced them with spring 2.0

I am using the snapshot for 08/11/2006

Any clues?

Matt





Send instant messages to your online friends http://au.messenger.yahoo.com 

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

Re: Fault after deploying

[Babette Wagner]

It is still failing, I re-compiled and copied to the directory listed below:

[EMAIL PROTECTED] apache-tomcat-5.5.20]$ ls webapps/axis/WEB-INF/classes/ws/
deploy.wsdd  IQueryHandlerService.class
QueryHandlerSoapBindingImpl.class IQueryHandlerServiceLocator.class 
QueryHandlerSoapBindingSkeleton.class ...

In the server-config.wsdd my service is mentioned as follows:

 
 
  
  
  
  
  
  
  
  
  
 

after deploying everything looks good but still I receive the 
- Exception:
java.lang.ClassNotFoundException: ws.QueryHandlerSoapBindingSkeleton


Regards,
Babette

---
Martin wrote:

server-config.wsdd makes the call on the location of the classname(s) via the
className parameter
of your service declaration in server-config.wsdd
re-compile all (including QueryHandlerSoapBindingSkeleton.java) of the
generated java files
and copy to $CATALINA_HOME/webapps/axis/WEB-INF/classes/ws

Viel Gluck,
M-
This e-mail communication and any attachments may contain confidential and
privileged information
for the use of the 
designated recipients named above. If you are not the intended recipient, you
are hereby notified
that you have received
this communication in error and that any review, disclosure, dissemination,
distribution or
copying of it or its 
contents
- Original Message - 
From: "Babette Wagner" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, November 08, 2006 4:25 PM
Subject: Fault after deploying


> I'm using Axis-1_4 with apache-tomcat-5.5.20 and JDK 1.5.0_08 on Mandrake 
> Linux
> 
> Like described in the user guide I generated a wsdl-file out of my interface
> and went on with WSDL2Java. When deploying my service with the AdminClient I
> receive a "Done processing".
> 
> But list via http://localhost:8080/axis/servlet/AxisServlet gives me the
> following message:
> 
> And now... Some Services
> AXIS error
> 
> Sorry, something seems to have gone wrong... here are the details:
> 
> Fault - Could not find class for the service named:
> ws.QueryHandlerSoapBindingSkeleton
> Hint: you may need to copy your class files/tree into the right location
> (which depends on the servlet system you are using).; nested exception is: 
>java.lang.ClassNotFoundException: ws.QueryHandlerSoapBindingSkeleton
> 
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> faultSubcode: 
> faultString: Could not find class for the service named:
> ws.QueryHandlerSoapBindingSkeleton
> Hint: you may need to copy your class files/tree into the right location
> (which depends on the servlet system you are using).; nested exception is: 
>java.lang.ClassNotFoundException: ws.QueryHandlerSoapBindingSkeleton
> faultActor: 
> faultNode: 
> faultDetail: 
>{http://xml.apache.org/axis/}hostname:cengiz
> 
> ---
> My packages are copied to 
> $CATALINA_HOME/webapps/axis/WEB-INF/classes/ 
> and the class QueryHandlerSoapBindingSkeleton exists in package ws.
> 
> All Path variables are set properly.
> 
> Any ideas?
> 
> regards,
> Babette
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

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