Re: Creating Axis2 SOAP Header

[Samisa Abeysinghe]

Eran Chinthaka wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Samisa Abeysinghe wrote:
  

Amila Suriarachchi wrote:


I am not sure about your problem.
but add this code to specifically set the soap12 for service client.

clientOptions = new Options();
clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
);
  

Why not simplify the API to something like:
clientOptions.setSoap12();



Look at the number of properties inside Options. So are you suggesting
to have one setter and a getter method of all of those params? 
Not exactly! Just make the common case simple. As an example, setting 
SOAP version, enabling MTOM, REST are more common. Leave all other more 
complex stuff to params.


Samisa...

--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services 
Developers' Portal)


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

Re: [Axis2] Creating Axis2 SOAP Header

[Eran Chinthaka]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ok, the first advice is *never* use impl classes inside Axiom. Always
use the factories. The reason is we have multiple implementations of them.

To correct your problem, the easiest way is to create an OMElement
rather than a SOAPHeaderBlock and call serviceClient.addHeader(OMElement).

The second option is to use the created SOAP12Factory to create
SOAPHeaderBlock.
use soapFactory.createSOAPHeaderBlock(...)

HTH.
Chinthaka

Daniel Herbison wrote:
> I'm trying to add the SOAP header, described in comment in code below, to a
> RPC call to a service.  First of all I really do not know if the code to
> create the header is correct, i think it is in the ball park(?)  But I get a
> run time error of:
> 
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.axiom.om.impl.OMNamespaceImpl
> at
> org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.(SOAPHeaderBlockImpl.java:54)
> at
> org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.(SOAP12HeaderBlockImpl.java:45)
> at rpcAxSys.main(Unknown Source)
> 
> the line causing the run time error is marked below, why is this doing this? 
> Also, is the header creation correct?
> 
> code--
> RPCServiceClient serviceClient = new RPCServiceClient();
> Options options = serviceClient.getOptions();
> EndpointReference targetEPR = new
> EndpointReference("https://xyz/Authorize/Service.asmx";);
> options.setTo(targetEPR);
> 
> /* header build
>  
>   
>string1
>string2  
>   
>  
>  */
> OMFactory fac = OMAbstractFactory.getOMFactory();
> OMNamespace omNs = fac.createOMNamespace("beta", "xmlns"); 
> 
> SOAPFactory soapFactory = new SOAP12Factory(); 
> SOAPHeaderBlock soapHeaderBlock = new
> SOAP12HeaderBlockImpl("Security",omNs,soapFactory); 
> soapHeaderBlock.setMustUnderstand(true); 
> 
> OMElement basicCredentials = fac.createOMElement("BasicCredentials", omNs); 
> 
> OMElement serviceId = fac.createOMElement("serviceId", omNs); 
> OMText serviceIdText = fac.createOMText(serviceId, agentID);
> serviceId.addChild(serviceIdText); 
> 
> OMElement serviceKey = fac.createOMElement("serviceKey", omNs); 
> OMText serviceKeyText = fac.createOMText(serviceKey, agentToken);
> serviceKey.addChild(serviceKeyText); 
> 
> basicCredentials.addChild(serviceId); 
> basicCredentials.addChild(serviceKey); 
> 
> soapHeaderBlock.addChild(basicCredentials); 
> 
> serviceClient.addHeader(soapHeaderBlock); 
> // end header build
> 
> QName opSetClaim = new QName("beta", "GetClaim" );
> 
> Object[] opSetParams = new Object[] { agentID, agentToken, requestor };
> Class[] returnTypes = new Class[] { Object.class };
> 
> Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
> returnTypes);
> 

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

iD8DBQFGQ/jSjON2uBzUhh8RAqVZAKC0exk4tKs9zIALPgI65NYyo+AbxQCePUqQ
xt15TCLceO7fDJe517267k8=
=duG+
-END PGP SIGNATURE-

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

Re: Creating Axis2 SOAP Header

[Eran Chinthaka]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Samisa Abeysinghe wrote:
> Amila Suriarachchi wrote:
>> I am not sure about your problem.
>> but add this code to specifically set the soap12 for service client.
>>
>> clientOptions = new Options();
>> clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
>> );
> Why not simplify the API to something like:
> clientOptions.setSoap12();

Look at the number of properties inside Options. So are you suggesting
to have one setter and a getter method of all of those params? And what
about API changes whenever we add a new property.

Hmm, the best option we thought was to use properties like this so that
there are no problems to API and you won't see hundreds of methods
inside options.

Thanks,
Chinthaka

> 
> Samisa...
>> serviceClient.setOptions(clientOptions);
>>
> 

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

iD8DBQFGQ/eCjON2uBzUhh8RAn6DAJ9P1rsJPsuo9IX0XmCuYDWDc5ZytQCfRQ6H
z0cOZBaE9B85sKHfqQQB9RY=
=+Ma2
-END PGP SIGNATURE-

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

Re: Creating Axis2 SOAP Header

[Samisa Abeysinghe]

Amila Suriarachchi wrote:

I am not sure about your problem.
but add this code to specifically set the soap12 for service client.

clientOptions = new Options();
clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI 
);

Why not simplify the API to something like:
clientOptions.setSoap12();

Samisa...

serviceClient.setOptions(clientOptions);



--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


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

Re: Release notes don't mention change in class name for generated stubs

[Dennis Sosnoski]

Hi John,

I agree completely - the Axis2 releases have been careless about 
breaking backward compatibility without even mentioning the breaks in 
the documentation. It looks like there's going to be a new set of API 
changes going into the 1.3 build, so I'll try to monitor what's changed 
in the release candidates and add a Jira for documenting anything that 
effects normal users.


On this particular point, you may find it convenient to just strip out 
the SOAP 1.2  in the WSDL. If there's only one binding present 
WSDL2Java will use the same names as before.


 - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



John G. Norman wrote:

Amila,

All I'm asking for is that the release notes should describe things
that break dependencies.

Even a link to an archived e-mail in the user or developer list would 
help.


Anything: Just a toehold.

:-)

John

On 5/10/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
I really sorry for your inconvenience. Anyway we discussed this in 
user and

developer lists.
 Earlier Axis2 generated the code only for one port. But now it 
generates

the code for all the ports
So if you want to generate the code only for one binding please 
specify them

with the
-sn  -pn  attributes.



On 5/9/07, John G. Norman <[EMAIL PROTECTED]> wrote:
>
> I notice that codegen'd client stubs in 1.2 now have names like
>
> UserServiceUserServiceSOAP12Port_httpStub
>
> rather than
>
> UserServiceStub
>
> I suppose I can live with the name change, though it did, er, break my
> build script -- but the fact that this change is not mentioned in the
> release notes is inexcusable.
>
> If the changes are buried in JIRA, you might provide a link in the
> release notes that would pull up the changes for the particular
> packages or tools.
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



--
Amila Suriarachchi,
WSO2 Inc.


-
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] ADB unwrapping broken in 1.2?

[Dennis Sosnoski]

Is anyone getting unwrapping to work with ADB in the 1.2 release? I 
tried my example project from 
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/example/adb-client 
(which worked fine in 1.1.1) and found that I'm now getting the wrapped 
style everywhere in the generated code even though this passes the '-uw' 
parameter for WSDL2Java. The JiBX unwrapped example still works without 
a problem, as does the (wrapped) XMLBeans example.


 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117


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

Re: problem trying to call a service using separate listener

[Jim Alateras]

Martin,

The addressing  module is enabled in the axis2.xml file. Do I also need 
to set the -Daxis2.repo property?


cheers

Martin Gainty wrote:

can you check this module entry in %AXIS2_HOME%\conf\axis2.xml
   

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - From: "Jim Alateras" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, May 10, 2007 8:05 PM
Subject: problem trying to call a service using separate listener


I have written a web service client to call the getVersion operation 
of the Version service that is part of the axis2 distribution.


The following code works fine


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);



now I want to test being able to receive the response on a different 
connection to the request. I have a couple of lines to the code to 
engage the addressing module and to use a separate listener.


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));
client.engageModule(new QName(Constants.MODULE_ADDRESSING));
options.setUseSeparateListener(true);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);


When I execute the code I get the following exception

Exception in thread "main" org.apache.axis2.AxisFault: Unable to 
engage module : addressing
at 
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:298) 


at com.comware.axis2.examples.VersionClient.main(VersionClient.java:29)


Can anyone provide some assistance in moving this forward. I have 
tried setting the -Daxsi2.xml= property on the 
command line but then I get the following error


Caused by: org.apache.axis2.deployment.DeploymentException: Invalid 
Handler phase rule has not been specified
at 
org.apache.axis2.deployment.DescriptionBuilder.processHandler(DescriptionBuilder.java:295) 

at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfigBuilder.java:261) 

at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisConfigBuilder.java:292) 

at 
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:107) 

at 
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:690) 

at 
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:109) 

at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61) 

at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory 


.java:180)
at 
org.apache.axis2.client.ServiceClient.initializeTransports(ServiceClient.java:189) 

at 
org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:118) 

at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:114)
at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:207)
at 
com.comware.axis2.examples.VersionClient.main(VersionClient.java:27)


cheers


-
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: problem trying to call a service using separate listener

[Martin Gainty]

can you check this module entry in %AXIS2_HOME%\conf\axis2.xml
   

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: "Jim Alateras" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, May 10, 2007 8:05 PM
Subject: problem trying to call a service using separate listener


I have written a web service client to call the getVersion operation of the 
Version service that is part of the axis2 distribution.


The following code works fine


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);



now I want to test being able to receive the response on a different 
connection to the request. I have a couple of lines to the code to engage 
the addressing module and to use a separate listener.


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));
client.engageModule(new QName(Constants.MODULE_ADDRESSING));
options.setUseSeparateListener(true);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);


When I execute the code I get the following exception

Exception in thread "main" org.apache.axis2.AxisFault: Unable to engage 
module : addressing
at 
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:298)

at com.comware.axis2.examples.VersionClient.main(VersionClient.java:29)


Can anyone provide some assistance in moving this forward. I have tried 
setting the -Daxsi2.xml= property on the command 
line but then I get the following error


Caused by: org.apache.axis2.deployment.DeploymentException: Invalid 
Handler phase rule has not been specified
at 
org.apache.axis2.deployment.DescriptionBuilder.processHandler(DescriptionBuilder.java:295)
at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfigBuilder.java:261)
at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisConfigBuilder.java:292)
at 
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:107)
at 
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:690)
at 
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:109)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory

.java:180)
at 
org.apache.axis2.client.ServiceClient.initializeTransports(ServiceClient.java:189)
at 
org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:118)
at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:114)
at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:207)
at 
com.comware.axis2.examples.VersionClient.main(VersionClient.java:27)


cheers


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

problem trying to call a service using separate listener

[Jim Alateras]

I have written a web service client to call the getVersion operation of 
the Version service that is part of the axis2 distribution.


The following code works fine


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);



now I want to test being able to receive the response on a different 
connection to the request. I have a couple of lines to the code to 
engage the addressing module and to use a separate listener.


ServiceClient client = new ServiceClient();
client.setTargetEPR(new
EndpointReference("http://localhost:5050/axis2/services/Version?wsdl";));
client.engageModule(new QName(Constants.MODULE_ADDRESSING));
options.setUseSeparateListener(true);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

// set the options
Options options = client.getOptions();
options.setAction("urn:getVersion");

// build the request
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace tns1 = fac.createOMNamespace("http://axisversion.sample";, 
"tns1");

OMElement getVersion = fac.createOMElement("getVersion", tns1);
OMElement response = client.sendReceive(getVersion);


When I execute the code I get the following exception

Exception in thread "main" org.apache.axis2.AxisFault: Unable to engage 
module : addressing
	at 
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:298)

at com.comware.axis2.examples.VersionClient.main(VersionClient.java:29)


Can anyone provide some assistance in moving this forward. I have tried 
setting the -Daxsi2.xml= property on the command 
line but then I get the following error


Caused by: org.apache.axis2.deployment.DeploymentException: Invalid 
Handler phase rule has not been specified
at 
org.apache.axis2.deployment.DescriptionBuilder.processHandler(DescriptionBuilder.java:295)
at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfigBuilder.java:261)
at 
org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisConfigBuilder.java:292)
at 
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:107)
at 
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:690)
at 
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:109)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory

.java:180)
at 
org.apache.axis2.client.ServiceClient.initializeTransports(ServiceClient.java:189)
at 
org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:118)
at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:114)
at 
org.apache.axis2.client.ServiceClient.(ServiceClient.java:207)
at 
com.comware.axis2.examples.VersionClient.main(VersionClient.java:27)


cheers


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

Re: [Axis2] Web service with no implementation

[Daniel Feist]

Yes, I was planning to do this programmatically rather than using aar.  It
looks like i'll need to implement my own dispatcher and receiver.

My concern was that the axis2 API would not let me create axis
engine/services without serviceClass.  Although you are right i can use a
dummy service implementation.  Looking at synapse I think will give me some
clues about how I can do this.

thanks

On 5/10/07, Shantanu Sen <[EMAIL PROTECTED]> wrote:


I do not think you can get away without having a serviceClass element in
the services.xml if you want to use an aar for creating the service.

What you want is possible programmatically, but when axis tries to read
the service info from an aar file it looks for the serviceClass I believe.

You can set it up with a 'dummy' service class that never gets invoked
since you can overeride RawXMLInoutMessageReceiver and do whatever you want
with the raw message.

Shantanu

- Original Message 
From: Daniel Feist <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Tuesday, May 8, 2007 7:19:21 AM
Subject: Re: [Axis2] Web service with no implementation

I don't mind the sales pitch, just i was ideally looking for a lightweight
solution using axis2 as a transport for esb with the option of using and
passing on raw xml rather than binding and invoking.

I am planning to use mule, but i don't quite see what axis2/synapse/mule
would give me over and above axis2/mule apart from more config files and
more dependencies, yet neither have i looked into synapse much.

If there any doc or information or wiki page on using axis2/synapse/mule?
Is the book on using Synapse and Mule available yet?

I saw the RawXMLInOutMessageReceiver receiver, I can try this out.. i was
just wondering before going down that path it is was possible to configure
and start up an axis engine with null service implementation? In other web
services stacks the definition of service implementation is integral and not
optional which would be a problem for the approach i want to take.


thanks



On 5/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Sorry I wasn't very clear!!!
>
> > Take a look at the RawXMLInOutMessageReceiver.
>
> This is an Axis2 MessageReceiver that can give you the body of the
> message as an XML.
>
> Paul
>
> >
> > But even if you are looking at using another ESB, it might still be
> > useful to use Synapse.
> >
> > Here's my sales pitch:
> >
> > 1) Its really not that big. Its a 20Mb download but the core Synapse
> > code is about 300k over and above Axis2.
> > 2) You might end up using some of the features later.
> > 3) We have tested our code a lot, so we're pretty sure that its going
> > to work well in your case.
> > 4) One of our committers is writing a book on using Synapse and Mule.
> > So you wouldn't be alone in using Synapse as a way of adding really
> > top rate XML and WS handling to your existing ESBs.
> >
> > Paul
> >
> > On 5/8/07, Daniel Feist <[EMAIL PROTECTED]> wrote:
> > > I will have a look at synapse...
> > >
> > > If i was starting from scratch it seems that would be the best
> option but as
> > > I am planning to integrate with an esb solution I am already use
> that
> > > provide message routing, transformation etc. I think the best option
> would
> > > be to extend axis to achieve what I need rather than using synapse
> which has
> > > functionality that i already have in my esb.
> > >
> > > I need to use axis as a SOAP stack that receives SOAP messages,
> processes
> > > them using phases/pipelines and then spits out the xml message
> payload
> > > rather than binding to java objects and invoking a service that has
> been
> > > configured.
> > >
> > > How would I go about doing this with axis2, using axis
> programaticaly if
> > > needed?
> > >
> > > - What the implementation of a custom Reciever allow me to output
> xml rather
> > > than bind and invoke?
> > > - Is it possible to configure axis engine that works without
> configuring a
> > > server implementation?
> > > - Can i specifiy wsdl instead of generating from service
> interface/class (i
> > > wouldn't have a service interface/class)
> > > - Any others things I should take into account?
> > >
> > > thanks,
> > > Dan
> > >
> > >
> > >  On 5/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Dan
> > > >
> > > > As Chathura also said, Synapse basically does what you want -
> > > > out-of-the-box. We already have built and tested samples where we
> do:
> > > >
> > > > XML/JMS->SOAP mapping
> > > > and SOAP/WSRM->XML/JMS
> > > >
> > > > We have also done plain-text/JMS -> XML/SOAP.
> > > >
> > > > Synapse is simply configured using an XML config file. If you send
> me
> > > > an example message or two I can help you create the config to test
> it.
> > > >
> > > > Paul
> > > >
> > > > On 5/8/07, Daniel Feist < [EMAIL PROTECTED]> wrote:
> > > > > Hi,
> > > > >
> > > > > I am attempting to implement a web-services using a web service
> stack
> > > such
> > > > > as axis in order to export

Re: Debug using SimpleHTTPServer

[Pablo Bendersky]

Dennis,
Thanks, I'll try debugging directly in Tomcat.

On 5/10/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:

Hi Pablo,

I generally stay with Tomcat for testing, hooking in for remote
debugging from my IDE. To do this, you first have to start Tomcat with
the debug transport enabled (using "catalina.sh jpda start" on
Linux/Unix/Mac). You can then connect to the running server code from
your IDE. Using Eclipse, you do this from your server code project by
going to Run/Debug... Remote Java Application/New. This creates a debug
configuration that matches the default for Tomcat running locally
(localhost, port 8000). You just need to run this configuration and set
a breakpoint in your server code in order to debug.

On Windows it's a little more complex to configure Tomcat for Eclipse. I
don't use Windows myself, but from looking at the slides I use in my
training classes the default is for Tomcat to use a dt_shmem connector
and address when run with catalina.bat. To change this, you need to set
variables JPDA_TRANSPORT=dt_socket and JPDA_ADDRESS=8000. Some people
were able do just add these lines directly to the start of their
catalina.bat file, but for others that didn't seem to work (even though
everyone was using the same Tomcat version, 4.1.32 as I remember) and
they had to instead set these as environmental variables before running
catalina.bat.

I've also used local transport in the past for some of my own
development, since that allows you to have both client and server code
in the same project. For most purposes I find the remote debugging on
Tomcat works best, though. Note that this can also be used with your
production system (so that if something breaks in production you can
hook in directly to try to find the problem). If you want to do this you
should naturally make sure that access to port 8000 (or whatever number
you choose to use) is restricted.

  - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117


Pablo Bendersky wrote:
> Hi,
> I'm trying to setup a development environment with Axis2 where it's
> easy for me to debug my services, but at the same time easy to deploy
> them on a production server.
> After looking around, I thought a good idea was to use Tomcat to
> deploy and the embedded SimpleHTTPServer to debug.
> So, I created a folder structure like this:
> /src/
> /server/
> /server/conf/axis2.xml
> /server/services/
> /server/services/MyService
> /server/services/MyService/META-INF
>
> Then I configured eclipse to output the class files into
> /server/services/MyService, and then wrote a starter class like this:
> public static void main(String[] args) {
>try {
> ConfigurationContext context = ConfigurationContextFactory.
> createConfigurationContextFromFileSystem("server",
> "server/conf/axis2.xml");
> SimpleHTTPServer server = new SimpleHTTPServer(context,
> 8080);
> server.start();
> } catch (AxisFault e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> The server starts ok, and I can get the WSDL file just fine. However,
> when I try to run any webservice, it doesn't get to the skeleton file
> (I'm using xmlbeans, BTW). If I zip the whole MyService folder and
> deploy it on Tomcat as an aar file, the service works as expected.
>
> I'm wondering if this is some classloader related issue, or anything.
> Does anyone has any hint? Any better idea on how to accomplish an app
> that is both easy to debug and easy to deploy at the same time?
>
> Thanks in advance.
>
> -
> 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: Debug using SimpleHTTPServer

[Dennis Sosnoski]

Hi Pablo,

I generally stay with Tomcat for testing, hooking in for remote 
debugging from my IDE. To do this, you first have to start Tomcat with 
the debug transport enabled (using "catalina.sh jpda start" on 
Linux/Unix/Mac). You can then connect to the running server code from 
your IDE. Using Eclipse, you do this from your server code project by 
going to Run/Debug... Remote Java Application/New. This creates a debug 
configuration that matches the default for Tomcat running locally 
(localhost, port 8000). You just need to run this configuration and set 
a breakpoint in your server code in order to debug.


On Windows it's a little more complex to configure Tomcat for Eclipse. I 
don't use Windows myself, but from looking at the slides I use in my 
training classes the default is for Tomcat to use a dt_shmem connector 
and address when run with catalina.bat. To change this, you need to set 
variables JPDA_TRANSPORT=dt_socket and JPDA_ADDRESS=8000. Some people 
were able do just add these lines directly to the start of their 
catalina.bat file, but for others that didn't seem to work (even though 
everyone was using the same Tomcat version, 4.1.32 as I remember) and 
they had to instead set these as environmental variables before running 
catalina.bat.


I've also used local transport in the past for some of my own 
development, since that allows you to have both client and server code 
in the same project. For most purposes I find the remote debugging on 
Tomcat works best, though. Note that this can also be used with your 
production system (so that if something breaks in production you can 
hook in directly to try to find the problem). If you want to do this you 
should naturally make sure that access to port 8000 (or whatever number 
you choose to use) is restricted.


 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117


Pablo Bendersky wrote:

Hi,
I'm trying to setup a development environment with Axis2 where it's
easy for me to debug my services, but at the same time easy to deploy
them on a production server.
After looking around, I thought a good idea was to use Tomcat to
deploy and the embedded SimpleHTTPServer to debug.
So, I created a folder structure like this:
/src/
/server/
/server/conf/axis2.xml
/server/services/
/server/services/MyService
/server/services/MyService/META-INF

Then I configured eclipse to output the class files into
/server/services/MyService, and then wrote a starter class like this:
public static void main(String[] args) {
   try {
ConfigurationContext context = ConfigurationContextFactory.
createConfigurationContextFromFileSystem("server", 
"server/conf/axis2.xml");
SimpleHTTPServer server = new SimpleHTTPServer(context, 
8080);

server.start();
} catch (AxisFault e) {
// TODO Auto-generated catch block
e.printStackTrace();
}

The server starts ok, and I can get the WSDL file just fine. However,
when I try to run any webservice, it doesn't get to the skeleton file
(I'm using xmlbeans, BTW). If I zip the whole MyService folder and
deploy it on Tomcat as an aar file, the service works as expected.

I'm wondering if this is some classloader related issue, or anything.
Does anyone has any hint? Any better idea on how to accomplish an app
that is both easy to debug and easy to deploy at the same time?

Thanks in advance.

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

[Paul Fremantle]

A hint. The generated ANT tasks that get created when you use XMLBeans
usually do everything necessary.

ADB is getting closer and closer to supporting as much Schema as is
feasible. One approach is to identify any schema issues that ADB has
with your WSDL and raise JIRAs - you might end up pretty close.

The other option is JAXB 2.0 Reference Implementation. That's also a
pretty good DB option.

Paul

On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote:

That's not much of a work-around if a person is using Maven to build
with.  You can't just pause the build in the middle, fix things, and
then let it continue ... maybe I can fix it with an ant task in
process-sources ...

Hey, thanks for helping me find that!  I was having no luck!

So, which data binding do folks use if they have moderate to complex
schema-mapping requirements.  My understanding is that ADB isn't the
best choice in that case (seems to work _great_ and _easy_ for simple
requirements though!), and I'm not sure I want to buy the complexity
that I hear comes with JIBX.

Thanks again for your help Robert!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com



From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 2:13 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] XMLBeans Implementation


Seems like you've run into a common problem:

http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html#invoking



"An important detail is that an XMLBean class file is also generated by
WSDL2Java, TypeSystemHolder.class. That file is placed into
build/classes by the above ant task and will be needed to compile the
generated sources. A frequent problem is users get an error such as:

ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load
class with name
schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeS
ystemHolder. Make sure the generated binary files are on the classpath.

The TypeSystemHolder.class generated by WSDL2Java must be placed in your
classpath in order to avoid this error."

wsdl2java created the class somewhere on your system - placing it in
your classpath should fix the issue.


HTH,
Robert


On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote:

That package isn't anywhere -- static or generated.  Is the
package name
being incorrectly generated, or am I missing something here?  Is
it
possible this is my error and not one of the Axis2 components?

Anyone successfully using Axis2 1.2 + XMLBeans?  With or without
the
wsdl2code and/or aar plugin?  Anyone doing this with Maven2?

Any feedback would be very appreciated!

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

-Original Message-
From: Edward Bush [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 12:29 PM
To: axis-user@ws.apache.org
Subject: [Axis2] XMLBeans Implementation

All,

I'm having some problems running a simple client.  As indicated,
I chose
an XMLBeans implementation.  Everything goes great -- I can
deploy it
fine, and the stand-alone Axis2 server starts up fine.  I can
check the
deployed services and that looks good.  I'm having a problem
actually
running my client though.  It's acting like it can't find a
class, which
I find odd.

I tracked-down the root package, and was traversing the package
structure.  When I got to the "system" level, I was lost --
there is not
a package named s672D183626EBCBAE4E84BBAC56FF9CA9.  Any
suggestions?

Here's the stack trace:

Exception in thread "main" java.lang.ExceptionInInitializerError
at

com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E
choTextRequestDocument.java :92)
at

com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient
Test.java:19)

Caused by: java.lang.RuntimeException: Cannot load
SchemaTypeSystem.
Unable to load class with name

schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS

ystemHolder. Make sure the generated binary files are on the
classpath.
at

org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at

com.crlcorp.ws.math.domain.EchoTextRequestDocument.(EchoTextRequ

estDocument.java:20)
... 2 more

Caused by: java.lang.ClassNotFoundException:

schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java :200)
at java.security.AccessController.doPrivileged(Native Method) at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClass

SOAP 1.1 Messages with Axis 1.4

[Nathan Wells]

I have built a web service client in Java using Axis 1.4.  When I call
the web service, the server responds with an HTTP 415 error because the
content type of the message is 'application/soap+xml; charset=UTF-8'
instead of 'text/xml; charset=utf-8'.  The developer responsible for the
server suggested using SOAP 1.1 instead of SOAP 1.2.

Does anyone know how to specify that the SOAP messages Axis 1.4 creates
conform to SOAP 1.1 instead of 1.2?  I didn't see any obvious way of
doing it, however, I did see there is a class named SOAP11Constants in
org.apache.axis.soap.

BTW - we are locked into using Axis 1.4, so we just can't switch to an
earlier version of the Axis library.

Any ideas, suggestions, or general direction would be appreciated.

Thanks,

Nate

--
Nathan Wells

-
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.

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

RE: [Axis2] XMLBeans Implementation

[Edward Bush]

That's not much of a work-around if a person is using Maven to build
with.  You can't just pause the build in the middle, fix things, and
then let it continue ... maybe I can fix it with an ant task in
process-sources ...
 
Hey, thanks for helping me find that!  I was having no luck!
 
So, which data binding do folks use if they have moderate to complex
schema-mapping requirements.  My understanding is that ADB isn't the
best choice in that case (seems to work _great_ and _easy_ for simple
requirements though!), and I'm not sure I want to buy the complexity
that I hear comes with JIBX.
 
Thanks again for your help Robert!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com



From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 2:13 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] XMLBeans Implementation


Seems like you've run into a common problem: 

http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html#invoking



"An important detail is that an XMLBean class file is also generated by
WSDL2Java, TypeSystemHolder.class. That file is placed into
build/classes by the above ant task and will be needed to compile the
generated sources. A frequent problem is users get an error such as:

ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load
class with name
schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeS
ystemHolder. Make sure the generated binary files are on the classpath.

The TypeSystemHolder.class generated by WSDL2Java must be placed in your
classpath in order to avoid this error."

wsdl2java created the class somewhere on your system - placing it in
your classpath should fix the issue. 


HTH,
Robert 


On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote: 

That package isn't anywhere -- static or generated.  Is the
package name
being incorrectly generated, or am I missing something here?  Is
it
possible this is my error and not one of the Axis2 components?

Anyone successfully using Axis2 1.2 + XMLBeans?  With or without
the
wsdl2code and/or aar plugin?  Anyone doing this with Maven2?

Any feedback would be very appreciated!

Thanks!

Eddie Bush
Software Analyst 
Clinical Reference Laboratory
bushe at crlcorp dot com

-Original Message-
From: Edward Bush [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 12:29 PM 
To: axis-user@ws.apache.org
Subject: [Axis2] XMLBeans Implementation

All,

I'm having some problems running a simple client.  As indicated,
I chose
an XMLBeans implementation.  Everything goes great -- I can
deploy it 
fine, and the stand-alone Axis2 server starts up fine.  I can
check the
deployed services and that looks good.  I'm having a problem
actually
running my client though.  It's acting like it can't find a
class, which 
I find odd.

I tracked-down the root package, and was traversing the package
structure.  When I got to the "system" level, I was lost --
there is not
a package named s672D183626EBCBAE4E84BBAC56FF9CA9.  Any
suggestions? 

Here's the stack trace:

Exception in thread "main" java.lang.ExceptionInInitializerError
at

com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E
choTextRequestDocument.java :92)
at

com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient
Test.java:19)

Caused by: java.lang.RuntimeException: Cannot load
SchemaTypeSystem.
Unable to load class with name

schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS

ystemHolder. Make sure the generated binary files are on the
classpath.
at

org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at

com.crlcorp.ws.math.domain.EchoTextRequestDocument.(EchoTextRequ

estDocument.java:20)
... 2 more

Caused by: java.lang.ClassNotFoundException:

schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java :200)
at java.security.AccessController.doPrivileged(Native Method) at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass
(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at

org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 3 more

I'm building against Axis2 using the wsdl2code plugin and the
aar plugi

Debug using SimpleHTTPServer

[Pablo Bendersky]

Hi,
I'm trying to setup a development environment with Axis2 where it's
easy for me to debug my services, but at the same time easy to deploy
them on a production server.
After looking around, I thought a good idea was to use Tomcat to
deploy and the embedded SimpleHTTPServer to debug.
So, I created a folder structure like this:
/src/
/server/
/server/conf/axis2.xml
/server/services/
/server/services/MyService
/server/services/MyService/META-INF

Then I configured eclipse to output the class files into
/server/services/MyService, and then wrote a starter class like this:
public static void main(String[] args) {
   try {
ConfigurationContext context = 
ConfigurationContextFactory.
createConfigurationContextFromFileSystem("server", 
"server/conf/axis2.xml");
SimpleHTTPServer server = new SimpleHTTPServer(context, 
8080);
server.start();
} catch (AxisFault e) {
// TODO Auto-generated catch block
e.printStackTrace();
}

The server starts ok, and I can get the WSDL file just fine. However,
when I try to run any webservice, it doesn't get to the skeleton file
(I'm using xmlbeans, BTW). If I zip the whole MyService folder and
deploy it on Tomcat as an aar file, the service works as expected.

I'm wondering if this is some classloader related issue, or anything.
Does anyone has any hint? Any better idea on how to accomplish an app
that is both easy to debug and easy to deploy at the same time?

Thanks in advance.

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

Re: [Axis2] XMLBeans Implementation

[robert lazarski]

Seems like you've run into a common problem:

http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html#invoking

"An important detail is that an XMLBean class file is also generated by
WSDL2Java, TypeSystemHolder.class. That file is placed into build/classes by
the above ant task and will be needed to compile the generated sources. A
frequent problem is users get an error such as:

*ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load class
with name
schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeSystemHolder.
Make sure the generated binary files are on the classpath.*

The TypeSystemHolder.class generated by WSDL2Java must be placed in your
classpath in order to avoid this error."

wsdl2java created the class somewhere on your system - placing it in your
classpath should fix the issue.
HTH,
Robert

On 5/10/07, Edward Bush <[EMAIL PROTECTED]> wrote:


That package isn't anywhere -- static or generated.  Is the package name
being incorrectly generated, or am I missing something here?  Is it
possible this is my error and not one of the Axis2 components?

Anyone successfully using Axis2 1.2 + XMLBeans?  With or without the
wsdl2code and/or aar plugin?  Anyone doing this with Maven2?

Any feedback would be very appreciated!

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

-Original Message-
From: Edward Bush [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 12:29 PM
To: axis-user@ws.apache.org
Subject: [Axis2] XMLBeans Implementation

All,

I'm having some problems running a simple client.  As indicated, I chose
an XMLBeans implementation.  Everything goes great -- I can deploy it
fine, and the stand-alone Axis2 server starts up fine.  I can check the
deployed services and that looks good.  I'm having a problem actually
running my client though.  It's acting like it can't find a class, which
I find odd.

I tracked-down the root package, and was traversing the package
structure.  When I got to the "system" level, I was lost -- there is not
a package named s672D183626EBCBAE4E84BBAC56FF9CA9.  Any suggestions?

Here's the stack trace:

Exception in thread "main" java.lang.ExceptionInInitializerError
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E
choTextRequestDocument.java:92)
at
com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient
Test.java:19)

Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem.
Unable to load class with name
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder. Make sure the generated binary files are on the classpath.
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument.(EchoTextRequ
estDocument.java:20)
... 2 more

Caused by: java.lang.ClassNotFoundException:
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method) at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 3 more

I'm building against Axis2 using the wsdl2code plugin and the aar plugin
--- version 1.2 on all counts.  My build system is Maven2.

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

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


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

RE: [Axis2] XMLBeans Implementation

[Edward Bush]

That package isn't anywhere -- static or generated.  Is the package name
being incorrectly generated, or am I missing something here?  Is it
possible this is my error and not one of the Axis2 components?

Anyone successfully using Axis2 1.2 + XMLBeans?  With or without the
wsdl2code and/or aar plugin?  Anyone doing this with Maven2?

Any feedback would be very appreciated!

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

-Original Message-
From: Edward Bush [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 12:29 PM
To: axis-user@ws.apache.org
Subject: [Axis2] XMLBeans Implementation

All,

I'm having some problems running a simple client.  As indicated, I chose
an XMLBeans implementation.  Everything goes great -- I can deploy it
fine, and the stand-alone Axis2 server starts up fine.  I can check the
deployed services and that looks good.  I'm having a problem actually
running my client though.  It's acting like it can't find a class, which
I find odd.

I tracked-down the root package, and was traversing the package
structure.  When I got to the "system" level, I was lost -- there is not
a package named s672D183626EBCBAE4E84BBAC56FF9CA9.  Any suggestions?

Here's the stack trace:
 
Exception in thread "main" java.lang.ExceptionInInitializerError
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E
choTextRequestDocument.java:92)
at
com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient
Test.java:19)

Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem.
Unable to load class with name
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder. Make sure the generated binary files are on the classpath.
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument.(EchoTextRequ
estDocument.java:20)
... 2 more

Caused by: java.lang.ClassNotFoundException:
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method) at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 3 more

I'm building against Axis2 using the wsdl2code plugin and the aar plugin
--- version 1.2 on all counts.  My build system is Maven2.

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

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


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

RE: How to set transport out?

[Chau, Hoang]

Hi Martin,

The version of axis2 is 1.2
The version of common http client is 3.0.1


Hoang

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 11:19 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


Chau-

I dont see 5.1 for for either Axis or commons-httpclient?

Axis latest release is 2.1.2??

latest commons-httpclient is 3.0.1 ??

Please confirm..

Thx
Martin
This email message and any files transmitted with it contain
confidential information intended only for the person(s) to whom this
email message is addressed.  If you have received this email message in
error, please notify the sender immediately by telephone or email and
destroy the original message without making a copy.  Thank you.

- Original Message - 
From: "Chau, Hoang" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Thursday, May 10, 2007 2:01 PM
Subject: RE: How to set transport out?


Will do it.

Thanks,


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


This is extremely weird!! could you please create a JIRA with your test
case and scripts?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> Yes, Davanum.  I have all 51 jars file in my classpath.
>
>
> Thank you.
>
>
> Hoang
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 10, 2007 9:58 AM
> To: axis-user@ws.apache.org
> Subject: Re: How to set transport out?
>
>
> Hoang,
>
> do you have the commons http client jar in the classpath?
>
> -- dims
>
> On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > How to set the transport out explicitly?  I understand that axis2
> > will
>
> > take the default one in axis2.xml but it appears that it doesn't set

> > the transport correctly?  I search on the web and check the jars in
> > lib to make sure every jars file is there.  Nothing is abnormal.  
> > Here
>
> > is the
> > error:
> >
> > Exception in thread "main" org.apache.axis2.AxisFault: Transport out

> > has not been set
> > at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
> > at
> > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxis
> > Op
> > er
> > ation.java:330)
> > at
> >
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxi
> sO
> > peration.java:294)
> > at
> >
> gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetService
> Fs
> > etServiceSoapStub.java:843)
> >
> > By the way, I am using axis2_1.2 version.
> >
> >
> > Hoang
> > -
> > This message and any attachments are intended only for the use of
> > the addressee and may contain information that is privileged and 
> > confidential. If the reader of the message is not the intended 
> > recipient or an authorized representative of the intended recipient,

> > you are hereby notified that any dissemination of this communication

> > is strictly prohibited. If you have received this communication in
> > error, notify the sender immediately by return email and delete the 
> > message and any attachments from your system.
> >
> >
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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


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



-
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: OMElement response message problem

[Martin Gainty]

Reneta
I would go with Thilina's suggestion of implementing with MTOM since encoding 
your data is base64Binary and works with the provided sample
e.g.
 
- http://ws.apache.org/axis2/mtomsample/";>
  http://www.w3.org/2005/05/xmlmime"; 
schemaLocation="MTOMSample?xsd=xsd0" /> 
- 
- 
   
   
  
  
   
   
  
  
- 
   
  

On the other hand SWA seems to be attachment oriented but not necessarily 
geared to encoding Binary64 e.g.
- 
- 
- 
   
   
  
  
  
- 
- 
- 
   
  
  
  
  
  
- 
   
  

Once all MTOM aspects are operational then work on the response..

Bon Chance/
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Reneta Säll (HF/EBC) 
  To: axis-user@ws.apache.org 
  Sent: Thursday, May 10, 2007 9:51 AM
  Subject: Axis2: OMElement response message problem


  Hi everybody,

  I'm having a problem with Axis2 web service that uploads txt file. The 
downloading works fine. 
  The file content is binary 64 type and is transfered as xml element in the 
Soap message.(not as attachment!!!)
  The size of my txt file is 3 KB. When I minimized the file size to1 KB then 
the problem does't exist.  

  The web service works fine with Axis 1.4. but not in Axis2?

  Is the max size of the OMElement in the response limited: firstChild, 
LastChild in some way?

  When I ran the client  it occured a wrong: java.lang.NullPointerException, 
then I debuged, it shows that: com.sun.jdi.InvocationException - exception held 
inside the result.


  I am using autogenerated wsdl2java Stub:

  public org.apache.axiom.om.OMElement View( org.apache.axiom.om.OMElement 
param18) throws java.rmi.RemoteException


  {

  try

  {

  org.apache.axis2.client.OperationClient _operationClient = 
_serviceClient.

  createClient(_operations[0].getName());

  _operationClient.getOptions().setAction("urn:#View");

  _operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);


  // create SOAP envelope with that payload

  org.apache.axiom.soap.SOAPEnvelope env = null;


  //Style is Doc.


  env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),param18,optimizeContent(new
 javax.xml.namespace.QName("","View")));


  //adding SOAP headers

  _serviceClient.addHeadersToEnvelope(env);

  // create message context with that soap envelope

  org.apache.axis2.context.MessageContext _messageContext = new 
org.apache.axis2.context.MessageContext();

 _messageContext.setEnvelope(env);


  // add the message contxt to the operation client

  _operationClient.addMessageContext(_messageContext);


  //execute the operation client

  _operationClient.execute(true);


  org.apache.axis2.context.MessageContext _returnMessageContext = 
_operationClient.getMessageContext 
(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);

  org.apache.axiom.soap.SOAPEnvelope _returnEnv = 
_returnMessageContext.getEnvelope();


  org.apache.axiom.om.OMElement omElement = 
_returnEnv.getBody().getFirstElement();



  java.lang.Object object = fromOM( 
_returnEnv.getBody().getFirstElement(), org.apache.axiom.om.OMElement.class, 
getEnvelopeNamespaces(_returnEnv));

  
_messageContext.getTransportOut().getSender().cleanup(_messageContext);

  return (org.apache.axiom.om.OMElement) object;


  }

  When I debug this (autogenerated) piece of code with a breakpoint on the 
return statement, the debugger says "com.sun.jdi.InvocationException occurred 
invoking method" and I get cin the client  java.lang.NullPointerException.

  I hope this is enough information. Please help me out with this.


  Best regards, Reneta

   

Re: [Axis2] Web service with no implementation

[Shantanu Sen]

I do not think you can get away without having a serviceClass element in the 
services.xml if you want to use an aar for creating the service. 

What you want is possible programmatically, but when axis tries to read the 
service info from an aar file it looks for the serviceClass I believe. 

You can set it up with a 'dummy' service class that never gets invoked since 
you can overeride RawXMLInoutMessageReceiver and do whatever you want with the 
raw message.

Shantanu

- Original Message 
From: Daniel Feist <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Tuesday, May 8, 2007 7:19:21 AM
Subject: Re: [Axis2] Web service with no implementation

I don't mind the sales pitch, just i was ideally looking for a lightweight 
solution using axis2 as a transport for esb with the option of using and 
passing on raw xml rather than binding and invoking.

I am planning to use mule, but i don't quite see what axis2/synapse/mule would 
give me over and above axis2/mule apart from more config files and more 
dependencies, yet neither have i looked into synapse much.


If there any doc or information or wiki page on using axis2/synapse/mule?  Is 
the book on using Synapse and Mule available yet?


I saw the RawXMLInOutMessageReceiver receiver, I can try this out.. i was just 
wondering before going down that path it is was possible to configure and start 
up an axis engine with null service implementation? In other web services 
stacks the definition of service implementation is integral and not optional 
which would be a problem for the approach i want to take.



thanks



On 5/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Sorry I wasn't very clear!!!

> Take a look at the RawXMLInOutMessageReceiver.

This is an Axis2 MessageReceiver that can give you the body of the
message as an XML.

Paul

>
> But even if you are looking at using another ESB, it might still be

> useful to use Synapse.
>
> Here's my sales pitch:
>
> 1) Its really not that big. Its a 20Mb download but the core Synapse
> code is about 300k over and above Axis2.
> 2) You might end up using some of the features later.

> 3) We have tested our code a lot, so we're pretty sure that its going
> to work well in your case.
> 4) One of our committers is writing a book on using Synapse and Mule.
> So you wouldn't be alone in using Synapse as a way of adding really

> top rate XML and WS handling to your existing ESBs.
>
> Paul
>
> On 5/8/07, Daniel Feist <[EMAIL PROTECTED]> wrote:
> > I will have a look at synapse...

> >
> > If i was starting from scratch it seems that would be the best option but as
> > I am planning to integrate with an esb solution I am already use that
> > provide message routing, transformation etc. I think the best option would

> > be to extend axis to achieve what I need rather than using synapse which has
> > functionality that i already have in my esb.
> >
> > I need to use axis as a SOAP stack that receives SOAP messages, processes

> > them using phases/pipelines and then spits out the xml message payload
> > rather than binding to java objects and invoking a service that has been
> > configured.
> >
> > How would I go about doing this with axis2, using axis programaticaly if

> > needed?
> >
> > - What the implementation of a custom Reciever allow me to output xml rather
> > than bind and invoke?
> > - Is it possible to configure axis engine that works without configuring a

> > server implementation?
> > - Can i specifiy wsdl instead of generating from service interface/class (i
> > wouldn't have a service interface/class)
> > - Any others things I should take into account?

> >
> > thanks,
> > Dan
> >
> >
> >  On 5/8/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> > >
> > > Dan

> > >
> > > As Chathura also said, Synapse basically does what you want -
> > > out-of-the-box. We already have built and tested samples where we do:
> > >
> > > XML/JMS->SOAP mapping

> > > and SOAP/WSRM->XML/JMS
> > >
> > > We have also done plain-text/JMS -> XML/SOAP.
> > >
> > > Synapse is simply configured using an XML config file. If you send me

> > > an example message or two I can help you create the config to test it.
> > >
> > > Paul
> > >
> > > On 5/8/07, Daniel Feist < 
[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > I am attempting to implement a web-services using a web service stack
> > such
> > > > as axis in order to export functionality through a web service defined

> > by
> > > > wsdl but with a twist...I want to integrate this into a message based
> > esb
> > > > type architecture.
> > > >
> > > > What i want to do is the following:

> > > > 1) WSDL first development
> > > > 2) Http transport
> > > > 3) Phase/handlers as normal
> > > > 4) BUT receiver does not invoke a service but rather forwards message

> > (SOAP
> > > > payload, as defined in WSDL) to a message broker ( e.g. JMS queue) where
> > it
> > > > will be routed to the service implementation.
> > > >

> > > > I don't want to attempt to do this with

Re: Release notes don't mention change in class name for generated stubs

[John G. Norman]

Amila,

All I'm asking for is that the release notes should describe things
that break dependencies.

Even a link to an archived e-mail in the user or developer list would help.

Anything: Just a toehold.

:-)

John

On 5/10/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:

I really sorry for your inconvenience. Anyway we discussed this in user and
developer lists.
 Earlier Axis2 generated the code only for one port. But now it generates
the code for all the ports
So if you want to generate the code only for one binding please specify them
with the
-sn  -pn  attributes.



On 5/9/07, John G. Norman <[EMAIL PROTECTED]> wrote:
>
> I notice that codegen'd client stubs in 1.2 now have names like
>
> UserServiceUserServiceSOAP12Port_httpStub
>
> rather than
>
> UserServiceStub
>
> I suppose I can live with the name change, though it did, er, break my
> build script -- but the fact that this change is not mentioned in the
> release notes is inexcusable.
>
> If the changes are buried in JIRA, you might provide a link in the
> release notes that would pull up the changes for the particular
> packages or tools.
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



--
Amila Suriarachchi,
WSO2 Inc.


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

Re: How to set transport out?

[Martin Gainty]

Chau-

I dont see 5.1 for for either Axis or commons-httpclient?

Axis latest release is 2.1.2??

latest commons-httpclient is 3.0.1 ??

Please confirm..

Thx
Martin
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: "Chau, Hoang" <[EMAIL PROTECTED]>

To: ; <[EMAIL PROTECTED]>
Sent: Thursday, May 10, 2007 2:01 PM
Subject: RE: How to set transport out?


Will do it.

Thanks,


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 10:27 AM

To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


This is extremely weird!! could you please create a JIRA with your test
case and scripts?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:

Yes, Davanum.  I have all 51 jars file in my classpath.


Thank you.


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 9:58 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


Hoang,

do you have the commons http client jar in the classpath?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> How to set the transport out explicitly?  I understand that axis2 
> will


> take the default one in axis2.xml but it appears that it doesn't set


> the transport correctly?  I search on the web and check the jars in 
> lib to make sure every jars file is there.  Nothing is abnormal.  
> Here


> is the
> error:
>
> Exception in thread "main" org.apache.axis2.AxisFault: Transport out



> has not been set
> at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
> at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxis

> Op
> er
> ation.java:330)
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxi
sO
> peration.java:294)
> at
>
gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetService
Fs
> etServiceSoapStub.java:843)
>
> By the way, I am using axis2_1.2 version.
>
>
> Hoang
> -
> This message and any attachments are intended only for the use of 
> the addressee and may contain information that is privileged and 
> confidential. If the reader of the message is not the intended 
> recipient or an authorized representative of the intended recipient,



> you are hereby notified that any dissemination of this communication


> is strictly prohibited. If you have received this communication in 
> error, notify the sender immediately by return email and delete the 
> message and any attachments from your system.

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


--
Davanum Srinivas :: http://davanum.wordpress.com

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


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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


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



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

RE: How to set transport out?

[Chau, Hoang]

Will do it.

Thanks,


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


This is extremely weird!! could you please create a JIRA with your test
case and scripts?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> Yes, Davanum.  I have all 51 jars file in my classpath.
>
>
> Thank you.
>
>
> Hoang
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 10, 2007 9:58 AM
> To: axis-user@ws.apache.org
> Subject: Re: How to set transport out?
>
>
> Hoang,
>
> do you have the commons http client jar in the classpath?
>
> -- dims
>
> On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > How to set the transport out explicitly?  I understand that axis2 
> > will
>
> > take the default one in axis2.xml but it appears that it doesn't set

> > the transport correctly?  I search on the web and check the jars in 
> > lib to make sure every jars file is there.  Nothing is abnormal.  
> > Here
>
> > is the
> > error:
> >
> > Exception in thread "main" org.apache.axis2.AxisFault: Transport out

> > has not been set
> > at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
> > at 
> > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxis
> > Op
> > er
> > ation.java:330)
> > at
> >
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxi
> sO
> > peration.java:294)
> > at
> >
> gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetService
> Fs
> > etServiceSoapStub.java:843)
> >
> > By the way, I am using axis2_1.2 version.
> >
> >
> > Hoang
> > -
> > This message and any attachments are intended only for the use of 
> > the addressee and may contain information that is privileged and 
> > confidential. If the reader of the message is not the intended 
> > recipient or an authorized representative of the intended recipient,

> > you are hereby notified that any dissemination of this communication

> > is strictly prohibited. If you have received this communication in 
> > error, notify the sender immediately by return email and delete the 
> > message and any attachments from your system.
> >
> >
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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


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

[Axis2] XMLBeans Implementation

[Edward Bush]

All,

I'm having some problems running a simple client.  As indicated, I chose
an XMLBeans implementation.  Everything goes great -- I can deploy it
fine, and the stand-alone Axis2 server starts up fine.  I can check the
deployed services and that looks good.  I'm having a problem actually
running my client though.  It's acting like it can't find a class, which
I find odd.

I tracked-down the root package, and was traversing the package
structure.  When I got to the "system" level, I was lost -- there is not
a package named s672D183626EBCBAE4E84BBAC56FF9CA9.  Any suggestions?

Here's the stack trace:
 
Exception in thread "main" java.lang.ExceptionInInitializerError
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument$Factory.newInstance(E
choTextRequestDocument.java:92)
at
com.crlcorp.ws.math.service.TestServiceClientTest.main(TestServiceClient
Test.java:19)

Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem.
Unable to load class with name
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder. Make sure the generated binary files are on the classpath.
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at
com.crlcorp.ws.math.domain.EchoTextRequestDocument.(EchoTextRequ
estDocument.java:20)
... 2 more

Caused by: java.lang.ClassNotFoundException:
schemaorg_apache_xmlbeans.system.s672D183626EBCBAE4E84BBAC56FF9CA9.TypeS
ystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 3 more

I'm building against Axis2 using the wsdl2code plugin and the aar plugin
--- version 1.2 on all counts.  My build system is Maven2.

Thanks!

Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com

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

Re: How to set transport out?

[Davanum Srinivas]

This is extremely weird!! could you please create a JIRA with your
test case and scripts?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:

Yes, Davanum.  I have all 51 jars file in my classpath.


Thank you.


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 9:58 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


Hoang,

do you have the commons http client jar in the classpath?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> How to set the transport out explicitly?  I understand that axis2 will

> take the default one in axis2.xml but it appears that it doesn't set
> the transport correctly?  I search on the web and check the jars in
> lib to make sure every jars file is there.  Nothing is abnormal.  Here

> is the
> error:
>
> Exception in thread "main" org.apache.axis2.AxisFault: Transport out
> has not been set
> at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOp
> er
> ation.java:330)
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
> peration.java:294)
> at
>
gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetServiceFs
> etServiceSoapStub.java:843)
>
> By the way, I am using axis2_1.2 version.
>
>
> Hoang
> -
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and
> confidential. If the reader of the message is not the intended
> recipient or an authorized representative of the intended recipient,
> you are hereby notified that any dissemination of this communication
> is strictly prohibited. If you have received this communication in
> error, notify the sender immediately by return email and delete the
> message and any attachments from your system.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Davanum Srinivas :: http://davanum.wordpress.com

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


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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

RE: How to set transport out?

[Chau, Hoang]

Yes, Davanum.  I have all 51 jars file in my classpath.


Thank you.


Hoang

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 9:58 AM
To: axis-user@ws.apache.org
Subject: Re: How to set transport out?


Hoang,

do you have the commons http client jar in the classpath?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> How to set the transport out explicitly?  I understand that axis2 will

> take the default one in axis2.xml but it appears that it doesn't set 
> the transport correctly?  I search on the web and check the jars in 
> lib to make sure every jars file is there.  Nothing is abnormal.  Here

> is the
> error:
>
> Exception in thread "main" org.apache.axis2.AxisFault: Transport out 
> has not been set
> at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
> at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOp
> er
> ation.java:330)
> at
>
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
> peration.java:294)
> at
>
gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetServiceFs
> etServiceSoapStub.java:843)
>
> By the way, I am using axis2_1.2 version.
>
>
> Hoang
> -
> This message and any attachments are intended only for the use of the 
> addressee and may contain information that is privileged and 
> confidential. If the reader of the message is not the intended 
> recipient or an authorized representative of the intended recipient, 
> you are hereby notified that any dissemination of this communication 
> is strictly prohibited. If you have received this communication in 
> error, notify the sender immediately by return email and delete the 
> message and any attachments from your system.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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


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

Re: How to set transport out?

[Davanum Srinivas]

Hoang,

do you have the commons http client jar in the classpath?

-- dims

On 5/10/07, Chau, Hoang <[EMAIL PROTECTED]> wrote:

Hi,

How to set the transport out explicitly?  I understand that axis2 will
take the default one in axis2.xml but it appears that it doesn't set the
transport correctly?  I search on the web and check the jars in lib to
make sure every jars file is there.  Nothing is abnormal.  Here is the
error:

Exception in thread "main" org.apache.axis2.AxisFault: Transport out has
not been set
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:294)
at
gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetServiceFs
etServiceSoapStub.java:843)

By the way, I am using axis2_1.2 version.


Hoang
-
This message and any attachments are intended only for the use of
the addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended
recipient or an authorized representative of the intended
recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this
communication in error, notify the sender immediately by return
email and delete the message and any attachments from your system.


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





--
Davanum Srinivas :: http://davanum.wordpress.com

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

How to set transport out?

[Chau, Hoang]

Hi,

How to set the transport out explicitly?  I understand that axis2 will
take the default one in axis2.xml but it appears that it doesn't set the
transport correctly?  I search on the web and check the jars in lib to
make sure every jars file is there.  Nothing is abnormal.  Here is the
error:

Exception in thread "main" org.apache.axis2.AxisFault: Transport out has
not been set
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:439)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:294)
at
gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetServiceFs
etServiceSoapStub.java:843)

By the way, I am using axis2_1.2 version.


Hoang
-
This message and any attachments are intended only for the use of
the addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended
recipient or an authorized representative of the intended
recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this
communication in error, notify the sender immediately by return
email and delete the message and any attachments from your system.


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

WSS4J signature authentication, doesn't appear to cross reference ca root authority

[Karen Loughran]

Hi all,

I'm using apache axis 1.x and have set up WS Security Axis handlers and
wss4j (v1.5) for the authentication of signed messages at the
requestFlow of my service and client.

Having carried out some tests, I realise that wss4j security (at least
action signature) just enables mutual authentication based on user certs
with no cross reference check to the ca root authority chained in the
keystores. 

Is there a way to configure wss4j to cross reference the chained ca root
in the request against the servers the caroot in the servers keystore
and/or the java system wide ca certs ?

Thanks

Karen



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

RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning

[Ted Jones]

That's good to know. Thanks Paul. 

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 10:00 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning

Ted

FYI The latest Sandesha builds (and the upcoming 1.2 release) support RM
1.0 without a separate listener. There has been a lot of work to support
this.

Paul



On 5/10/07, Ted Jones <[EMAIL PROTECTED]> wrote:
>
>
> Thanks Amila. I appreciate the input. I am using Dual channel since it

> appeared to be required per this thread:
> http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%
> [EMAIL PROTECTED]
> Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1.
>
> I have verified your points outlined below. Everything appears
correct.
>
> Martin - I will put together a reproducible test case and post ASAP.
>
> Thanks for your assistance.
> Ted
>
>
>  
>
> From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 10, 2007 12:25 AM
> To: axis-user@ws.apache.org; Martin Gainty
>
> Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning
>
>
> Are you using the Dual chanel mode or single chanel?
>
> if you set the setUseSeparateListener your request comes in a 
> different http chanel than you send the request. Otherwise it comes in
the same chanel.
>
> In the dual chanel model, What happens is your client starts a simple 
> http server on your machine and set the ReplyTo addressing header to 
> point to the stated server.
>
> So you have to make sure these things.
> 1. you must have engage the Addressing. (otherwise server won't be 
> able to find the reply location) 2. client uses the port and the host 
> name you have specified in the axis2.xml to start its simple http 
> server and set this address to replyTo filed. So you have to use two 
> seperate axis2.xml files for client and the server with different port

> numbers if you run them both in one machine.
>
> 3. if your server is in out side your firewall, the host name you 
> specify in the client axis2.xml should be able to access from the out 
> side the firewall.
>
>
>
> On 5/10/07, Martin Gainty <[EMAIL PROTECTED]> wrote:
> > Good Evening
> >
> > if you publish your wsdl we can run the client code
> >
> > Thanks
> > Martin--
> > This email message and any files transmitted with it contain 
> > confidential information intended only for the person(s) to whom 
> > this email message is addressed.  If you have received this email 
> > message in error, please
> notify
> > the sender immediately by telephone or email and destroy the 
> > original message without making a copy.  Thank you.
> >
> > - Original Message -
> > From: "Ted Jones" <[EMAIL PROTECTED]>
> > To: 
> > Sent: Wednesday, May 09, 2007 7:10 PM
> > Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
> >
> >
> > So, I'm guessing that the message is never reaching the server. 
> > Which may explain why there is no logging? I can see in debug where 
> > the
> > Sandesha2 logic is hit and the message is sent but I never see any 
> > sequences or other message traffic and my client is left polling 
> > forever waiting for the callback to complete.
> >
> > Any other thoughts on what might be happening here or where else I 
> > can look?
> >
> > Thanks,
> > Ted
> >
> > -Original Message-
> > From: Ted Jones [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, May 09, 2007 10:27 AM
> > To: axis-user@ws.apache.org
> > Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
> >
> > Thanks for all the responses. This is a great mailing list.
> >
> > I am not seeing any messages in TCPMON or in the logs. :-(
> >
> > Question: How can you configure TCPMON to capture messages sent to 
> > SimpleHTTPServer? I get a port bind exception.
> >
> > Also, I cannot seems to get logging working with Sandesha2. If 
> > anyone has it working, I would really appreciate a peek at their 
> > log4j.properties.
> >
> > Thanks!
> > Ted
> >
> > -Original Message-
> > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, May 08, 2007 11:12 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning
> >
> > Ted Jones wrote:
> >
> > > I am using Sandesha2 with an asynch Axis2 client. Using the 
> > > example that comes with Sandesha2 (the asynch echo client), the 
> > > onComplete() method of my callback is never hit. It appears the 
> > > response is not returning.
> > >
> > > Any ideas?
> >
> > Did you try capturing message sequences with TCPMON and chek the 
> > message sequence?
> >
> > Also, have a look into the server and client logs.
> >
> > Samisa...
> >
> >
> >
> -
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> 

Re: Keystore in Axis2 war

[sridhar vudutha]

Amila,
   Thanks for the response. I tried with different paths but couldn't get
it working.

I have placed the TestKeyStore in conf/props folder and mentioned the below
paths.

org.apache.ws.security.crypto.merlin.file=C:\jboss-
4.0.5.GA\server\default\conf\props\TestKeyStore
org.apache.ws.security.crypto.merlin.file=C:\\jboss-
4.0.5.GA\\server\\default\\conf\\props\\TestKeyStore
org.apache.ws.security.crypto.merlin.file=C:/jboss-
4.0.5.GA/server/default/conf/props/TestKeyStore
org.apache.ws.security.crypto
.merlin.file=%JBOSS_HOME%\\server\\default\\conf\\props\\TestKeyStore
org.apache.ws.security.crypto
.merlin.file=%JBOSS_HOME%/server/default/conf/props/TestKeyStore

Next I have placed the TestKeyStore in different directories
C:\jboss-4.0.5.GA\server\default\conf\props\TestKeyStore
C:\jboss-4.0.5.GA\server\default\TestKeyStore
C:\jboss-4.0.5.GA\bin\TestKeyStore

Tried with the below paths

org.apache.ws.security.crypto.merlin.file=./TestKeyStore
org.apache.ws.security.crypto.merlin.file=/TestKeyStore

None of the above tests worked. I have the test.properties in C:\jboss-
4.0.5.GA\server\default\conf\props\test.properties.

Am I missing anything? Any help would be greatly apperciated.

Thanks,
Sridhar.




On 5/10/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:


I think you can give the full path to file here
e.g.
org.apache.ws.security.crypto .merlin.file=/home/test/TestKeyStore

or a relative path from the jboss bin folder



On 5/9/07, sridhar vudutha <[EMAIL PROTECTED]> wrote:
>
> Martin,
>  Putting the test.properties file in  
$JBOSS_HOME/server/default/conf/props,
> worked fine. How can I take the KeyStore out of the war file? I tried
> putting it in the same directory ( $JBOSS_HOME/server/default/conf/props) but 
didn't work. Any suggestions?
>
> Thanks,
> Sridhar.
>
>
>
> On 5/8/07, Martin Gainty <[EMAIL PROTECTED] > wrote:
> >
> >  Sridhar--
> > did you try
> > $JBOSS_HOME/server/default/conf/props
> > ?
> > M--
> > This email message and any files transmitted with it contain
> > confidential
> > information intended only for the person(s) to whom this email message
> > is
> > addressed.  If you have received this email message in error, please
> > notify
> > the sender immediately by telephone or email and destroy the original
> > message without making a copy.  Thank you.
> >
> >
> > - Original Message -
> > *From:* sridhar vudutha <[EMAIL PROTECTED]>
> > *To:* axis-user@ws.apache.org
> > *Sent:* Tuesday, May 08, 2007 1:08 PM
> > *Subject:* Keystore in Axis2 war
> >
> >
> > Hello,
> > I'm having trouble taking out the KeyStore or the properties file
> > from the Axis2 war file. As long as they are in the 
Axis2.war/WEB-INF/classes
> > directory, everything works fine. I'm using JBoss 4.0.5 and would like
> > to put KeyStore or the properties file outside the Axis2.war file. I
> > tried putting it in Jboss/server/default/lib ; Jboss/server/conf and also
> > manually updated the JBoss CLASSPATH in the run.bat file but doesn't
> > work.
> >
> > The properties  file (test.properties) in Axis2.war/WEB-INF/classes
> > folder has the following contents.
> >
> >
> > 
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
> > org.apache.ws.security.components.crypto.Merlin
> > org.apache.ws.security.crypto.merlin.keystore.type=jks
> > org.apache.ws.security.crypto.merlin.keystore.password=password
> > org.apache.ws.security.crypto.merlin.keystore.alias=uattest
> > org.apache.ws.security.crypto.merlin.alias.password=password
> > org.apache.ws.security.crypto.merlin.file=TestKeyStore
> >
> > If I keep both the TestKeyStore and test.properties files in the
> > Axis2.war/WEB-INF/classes folder, it works fine.
> >
> > Can someone please suggest me how to put make the properties file or
> > the KeyStore file available to Axis2.war after it is deployed?
> >
> > I'm putting Axis2.war in an ear which contains some jars and 2 other
> > war files.
> >
> > Any help would be greatly appreciated.
> >
> > Thanks,
> > Sridhar.
> >
> >
>


--
Amila Suriarachchi,
WSO2 Inc.

Re: Creating Axis2 SOAP Header

[Michele Mazzucco]

What about env.serialize(System.out)?, where env is a SOAPEnvelope
object?

Michele

On Thu, 2007-05-10 at 07:55 -0700, Daniel Herbison wrote:
> I changed this:
> 
> SOAPFactory factory = (SOAPFactory) OMAbstractFactory.getSOAP12Factory();
> 
> and got rid of the error but it is failing on the call with:
> 
> Exception in thread "main" org.apache.axiom.soap.SOAPProcessingException:
> Expecting an implementation of SOAP Envelope as the parent. But received
> some other implementation
> at
> org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkParent(SOAPHeaderImpl.java:369)
> at
> org.apache.axiom.soap.impl.llom.SOAPElement.setParent(SOAPElement.java:75)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:236)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:192)
> at
> org.apache.axis2.client.ServiceClient.addHeadersToEnvelope(ServiceClient.java:647)
> at
> org.apache.axis2.client.ServiceClient.fillSOAPEnvelope(ServiceClient.java:633)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:517)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
> at
> org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:97)
> at rpcAxSys.main(rpcAxSys.java:51)
> 
> Is there a way to print the soap message out before calling invokeBlocking?
> 
> Code excluding header code, same as before.
> 
> rpcAxSys rpc = new rpcAxSys(args[0],args[1],args[2]);
> EndpointReference targetEPR = new
> EndpointReference("https://pcary571.corp.nortel.com/Authorize/Service.asmx";);
> RPCServiceClient serviceClient = new RPCServiceClient();
> Options options = serviceClient.getOptions();
> options.setTo(targetEPR);
> serviceClient.addHeader(rpc.header2());  // header2 has header generation
> code below
> QName opSetClaim = new QName("beta", "GetClaim" );
> Object[] opSetParams = new Object[] { rpc.agentID, rpc.agentToken,
> rpc.requestor };
> Class[] returnTypes = new Class[] { Object.class };
> Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
> returnTypes); FAILING HERE 
> 
> 
> 
> 
> Michele Mazzucco-2 wrote:
> > 
> > Daniel,
> > 
> > could you please enable the debug  of javac (it is enabled by default,
> > remove the -g:none option) and tell us which line causes the problem?
> > 
> > Michele
> > 
> > On Thu, 2007-05-10 at 05:28 -0700, Daniel Herbison wrote:
> >> Thank you for your replies!
> >> I tried the code below and still get a runtime casting error.
> >> 
> >> Exception in thread "main" java.lang.ClassCastException:
> >> org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
> >> at rpcAxSys.header2(Unknown Source)
> >> at rpcAxSys.main(Unknown Source)
> >> 
> >> SOAP12Factory factory = (SOAP12Factory)
> >> OMAbstractFactory.getSOAP12Factory();
> >> OMNamespace omNs = factory.createOMNamespace("beta.va.nortel.com",
> >> "xmlns"); 
> >> 
> >> SOAPHeader header = factory.createSOAPHeader();
> >> 
> >> SOAPHeaderBlock block = factory.createSOAPHeaderBlock("BasicCredentials",
> >> omNs);
> >> 
> >> OMElement serviceId = factory.createOMElement("serviceId", omNs); 
> >> OMText serviceIdText = factory.createOMText(serviceId, agentID);
> >> serviceId.addChild(serviceIdText); 
> >> 
> >> OMElement serviceKey = factory.createOMElement("serviceKey", omNs); 
> >> OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
> >> serviceKey.addChild(serviceKeyText); 
> >> 
> >> block.addChild(serviceId);
> >> block.addChild(serviceKey);
> >> 
> >> header.addChild(block);
> >> 
> >> 
> >> Amila Suriarachchi wrote:
> >> > 
> >> > I am not sure about your problem.
> >> > but add this code to specifically set the soap12 for service client.
> >> > 
> >> > clientOptions = new Options();
> >> >
> >> clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
> >> > );
> >> > serviceClient.setOptions(clientOptions);
> >> > 
> >> > On 5/10/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >> Daniel,
> >> >>
> >> >> I think the way you create the SOAPHeaderBlock is not correct. Can
> >> >> you try this way please?
> >> >>
> >> >> SOAP12Factory factory = (SOAP12Factory)
> >> >> OMAbstractFactory.getSOAP12Factory();
> >> >> OMNamespace omNs = factory.createOMNamespace(
> >> >> "http://...";,
> >> >> "..."
> >> >> );
> >> >>
> >> >> SOAPEnvelope env = factory.createSOAPEnvelope();
> >> >> SOAPHeader header = factory.createSOAPHeader();
> >> >> SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
> >> >> SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
> >> >> OMElement type = factory.createOMElement(
> >> >> SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);
> >> >>
> >> >> type.setText(MessageType.UPLOAD.value());
> >> >> block.addChild(type);
> >> >> header.addChild(block);
> >> >>
> >> >

Re: [Axis2 1.2] Java2WSDL with support of SwA and/or MTOM

[Thilina Gunarathne]

Axis2 supports Java2WSDL only for MTOM...

String uploadFile(String userID, String fileName) {}

Try changing the method as follows,
String uploadFile(String userID, DataHandler file) {}


My second question is:
What will be the differences between MTOM and SwA in terms of Web Service
implementation class (the signature) and the WSDL?

It's not trivial to capture the SwA details in the WSDL... Axis2 does
not support it either..
On the other hand specifying a MTOM compatible WSDL is trivial.. You
just need to specify a element with the type base64Binary...


Another question about attachment is about interoperability.
From Axis2 user guide, MTOM is much better than SwA. However, MTOM is not
WS-I Basic Profile 1.0 or 1.1 compliant.

I don't think MTOM was there when they are doing the basic profile ;)...


Will there be any issue if my web
service uses MTOM and the client uses .NET or other non-Axis2 SOAP toolkit?

Most of the newer stacks including WCF (.net) supports MTOM..If you
are looking for a futuristic approach then MTOM is the choice..If you
are looking for support from the older stacks, then SwA is the choice.

Thanks,
Thilina


--
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

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

Re: working in .NET, but "Unexpected subelement return" when I try to run as axis2 client

[Amila Suriarachchi]

can you try
either putting return to

parameterOrder='arg0 arg1' ie parameterOrder='arg0 arg1 return'

or removing parameterOrder='arg0 arg1'


And can you find the Response and send it to us?


On 5/9/07, Rick Reumann <[EMAIL PROTECTED]> wrote:


I'm trying to figure out why I'm getting this "Unexpected subelement
return" Runtime Exception when I try to use an axis2 client that I
created by using wsdl2java pointing to a wsdl that describes a
webservice running on Jboss4.0.5 (with jax-ws2.0 applied).

I can easily create the webservice from the same wsdl using visual
studio 2005. I can also connect fine if I build my client on a remote
jboss server using the wsconsume tool to generate my client stub.

The client code that I'm trying to use looks like this in a TestClient
class:

CalculatorBeanServiceStub stub = new
CalculatorBeanServiceStub();
CalculatorBeanServiceStub.Add addClass = new
CalculatorBeanServiceStub.Add();
addClass.setArg0(5);
addClass.setArg1(1);
AddResponse addResponse = stub.add(addClass);
System.out.println( addResponse.localResult );

The wsdl I pasted here http://pastehere.com/?lidoec

and also is listed below (at the end I also list the annotated ejbs
that are deployed). Thanks for any help with this. It's sort of
driving me nuts that I can get this to work from a .NET client but not
Axis2.




  
  


  



  


  
  


  

   
   
  
  
   
   
  



  
  
   
   

   
   

   

  
  
   
   

   
   

   

  


  
   
  





@Stateless
@WebService(endpointInterface="
org.jboss.tutorial.webservice.bean.Calculator")
public class CalculatorBean
{
   public int add(int x, int y)
   {
  return x + y;
   }

   public int subtract(int x, int y)
   {
  return x - y;
   }
}

---

@WebService
@SOAPBinding(style=Style.RPC)
public interface Calculator extends Remote
{
   @WebMethod int add(int x, int y);

   @WebMethod int subtract(int x, int y);
}

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





--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Amila Suriarachchi]

Any way this is a bug and I fixed it for the trunk.

On 5/10/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:


have you put elementFormDefault="qualified" in your schma?

On 5/10/07, Stephane Roy <[EMAIL PROTECTED] > wrote:
>
> Hi,
>
> The XSD schema used by my WSDL defines the following types:
>
> ...
>
>  
>
>
>  
>
>  
>  
>
>  
>
>
>  
>
> ...
>
> In short, typeA uses typeB, typeB being defined within typeA.
>
>
> I generated the code for the server in adb mode with the command
>
> $AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
> /tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd
>
> Then in /tmp/my/dir/server/src, I have a java file for typeB, for which
> the package name is not set ('package ;'). As a result, the java code
> cannot be compiled.
>
> I have this problem with Axis2.1.1.1 and with the latest release
> (Axis2.1.2).
>
>
> However, if I change my XSD schema, to have something like this:
>
> ...
>
>  
>
>
>  
>
>
>
>  
>
>
>  
>
> ...
>
> In short, typeB is now defined at the top-level in the XSD schema and
> typeA defines elementB which uses a reference to typeB.
>
> Now, the code generation in adb mode works fine and the java files
> compile.
>
>
> I would like to know if someone had this kind of problem before.
> Is this behavior a known issue or a limitation of Axis2.1.x ?
>
> Thanks in advance.
>
> Stephane Roy
> Alcatel-Lucent
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Amila Suriarachchi,
WSO2 Inc.





--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning

[Paul Fremantle]

Ted

FYI The latest Sandesha builds (and the upcoming 1.2 release) support
RM 1.0 without a separate listener. There has been a lot of work to
support this.

Paul



On 5/10/07, Ted Jones <[EMAIL PROTECTED]> wrote:



Thanks Amila. I appreciate the input. I am using Dual channel since it
appeared to be required per this thread:
http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/[EMAIL 
PROTECTED]
Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1.

I have verified your points outlined below. Everything appears correct.

Martin - I will put together a reproducible test case and post ASAP.

Thanks for your assistance.
Ted


 

From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 12:25 AM
To: axis-user@ws.apache.org; Martin Gainty

Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning


Are you using the Dual chanel mode or single chanel?

if you set the setUseSeparateListener your request comes in a different http
chanel than you send the request. Otherwise it comes in the same chanel.

In the dual chanel model, What happens is your client starts a simple http
server on your machine and set the ReplyTo addressing header to point to the
stated server.

So you have to make sure these things.
1. you must have engage the Addressing. (otherwise server won't be able to
find the reply location)
2. client uses the port and the host name you have specified in the
axis2.xml to start its simple http server and set this address to replyTo
filed. So you have to use two seperate axis2.xml files for client and the
server with different port numbers if you run them both in one machine.

3. if your server is in out side your firewall, the host name you specify in
the client axis2.xml should be able to access from the out side the
firewall.



On 5/10/07, Martin Gainty <[EMAIL PROTECTED]> wrote:
> Good Evening
>
> if you publish your wsdl we can run the client code
>
> Thanks
> Martin--
> This email message and any files transmitted with it contain confidential
> information intended only for the person(s) to whom this email message is
> addressed.  If you have received this email message in error, please
notify
> the sender immediately by telephone or email and destroy the original
> message without making a copy.  Thank you.
>
> - Original Message -
> From: "Ted Jones" <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, May 09, 2007 7:10 PM
> Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
>
>
> So, I'm guessing that the message is never reaching the server. Which
> may explain why there is no logging? I can see in debug where the
> Sandesha2 logic is hit and the message is sent but I never see any
> sequences or other message traffic and my client is left polling forever
> waiting for the callback to complete.
>
> Any other thoughts on what might be happening here or where else I can
> look?
>
> Thanks,
> Ted
>
> -Original Message-
> From: Ted Jones [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 09, 2007 10:27 AM
> To: axis-user@ws.apache.org
> Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning
>
> Thanks for all the responses. This is a great mailing list.
>
> I am not seeing any messages in TCPMON or in the logs. :-(
>
> Question: How can you configure TCPMON to capture messages sent to
> SimpleHTTPServer? I get a port bind exception.
>
> Also, I cannot seems to get logging working with Sandesha2. If anyone
> has it working, I would really appreciate a peek at their
> log4j.properties.
>
> Thanks!
> Ted
>
> -Original Message-
> From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 11:12 PM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning
>
> Ted Jones wrote:
>
> > I am using Sandesha2 with an asynch Axis2 client. Using the example
> > that comes with Sandesha2 (the asynch echo client), the onComplete()
> > method of my callback is never hit. It appears the response is not
> > returning.
> >
> > Any ideas?
>
> Did you try capturing message sequences with TCPMON and chek the message
> sequence?
>
> Also, have a look into the server and client logs.
>
> Samisa...
>
>
>
-
> 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]
>
>



--
Amila Suriarachchi,
WSO2 Inc.



--
Paul Fremantle
V

RE: Axis2: OMElement response message problem

[HF/EBC]

Hi Martin,
 
thank you for your answer.
 
The reason is time and that I would like to reuse my Axis 1 .xsd, wsdl and 
server side code since it is an working application.
But if it is not possible to upload xml element with 3 Kb size in Axis2 
(strange thing is that when debuging and looking on the reterned response 
envelope then is working fine - timing?) I need to know, then I have to look at 
SWA or MTOM.
 
Best regards, Reneta
 


From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: den 10 maj 2007 16:42
To: axis-user@ws.apache.org
Subject: Re: Axis2: OMElement response message problem


Any reason why you are cannot xmit the entity with Attachment as in 
/sample/soapwithattachments/client/SWAClient.java example?

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.


- Original Message - 
From: Reneta Säll (HF/EBC)   
To: axis-user@ws.apache.org 
Sent: Thursday, May 10, 2007 9:51 AM
Subject: Axis2: OMElement response message problem

Hi everybody,
 
I'm having a problem with Axis2 web service that uploads txt file. The 
downloading works fine. 
The file content is binary 64 type and is transfered as xml element in 
the Soap message.(not as attachment!!!)
The size of my txt file is 3 KB. When I minimized the file size to1 KB 
then the problem does't exist.  
 
The web service works fine with Axis 1.4. but not in Axis2?
 
Is the max size of the OMElement in the response limited: firstChild, 
LastChild in some way?
 
When I ran the client  it occured a wrong: 
java.lang.NullPointerException, then I debuged, it shows that: 
com.sun.jdi.InvocationException - exception held inside the result.

 
I am using autogenerated wsdl2java Stub:
 
public org.apache.axiom.om.OMElement View( 
org.apache.axiom.om.OMElement param18) throws java.rmi.RemoteException



{

try

{

org.apache.axis2.client.OperationClient _operationClient = 
_serviceClient.

createClient(_operations[0].getName());

_operationClient.getOptions().setAction("urn:#View");


_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);



// create SOAP envelope with that payload

org.apache.axiom.soap.SOAPEnvelope env = null;



//Style is Doc.



env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),param18,optimizeContent(new
 javax.xml.namespace.QName("","View")));



//adding SOAP headers

_serviceClient.addHeadersToEnvelope(env);

// create message context with that soap envelope

org.apache.axis2.context.MessageContext _messageContext = new 
org.apache.axis2.context.MessageContext();

   _messageContext.setEnvelope(env);



// add the message contxt to the operation client

_operationClient.addMessageContext(_messageContext);



//execute the operation client

_operationClient.execute(true);



org.apache.axis2.context.MessageContext _returnMessageContext = 
_operationClient.getMessageContext 
(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);

org.apache.axiom.soap.SOAPEnvelope _returnEnv = 
_returnMessageContext.getEnvelope();



org.apache.axiom.om.OMElement omElement = 
_returnEnv.getBody().getFirstElement();





java.lang.Object object = fromOM( 
_returnEnv.getBody().getFirstElement(), org.apache.axiom.om.OMElement.class, 
getEnvelopeNamespaces(_returnEnv));


_messageContext.getTransportOut().getSender().cleanup(_messageContext);

return (org.apache.axiom.om.OMElement) object;



}

When I debug this (autogenerated) piece of code with a breakpoint on 
the return statement, the debugger says "com.sun.jdi.InvocationException 
occurred invoking method" and I get cin the client  
java.lang.NullPointerException.

I hope this is enough information. Please help me out with this.
 
 
Best regards, Reneta

 

Re: Creating Axis2 SOAP Header

[Daniel Herbison]

I changed this:

SOAPFactory factory = (SOAPFactory) OMAbstractFactory.getSOAP12Factory();

and got rid of the error but it is failing on the call with:

Exception in thread "main" org.apache.axiom.soap.SOAPProcessingException:
Expecting an implementation of SOAP Envelope as the parent. But received
some other implementation
at
org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkParent(SOAPHeaderImpl.java:369)
at
org.apache.axiom.soap.impl.llom.SOAPElement.setParent(SOAPElement.java:75)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:236)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:192)
at
org.apache.axis2.client.ServiceClient.addHeadersToEnvelope(ServiceClient.java:647)
at
org.apache.axis2.client.ServiceClient.fillSOAPEnvelope(ServiceClient.java:633)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:517)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
at
org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:97)
at rpcAxSys.main(rpcAxSys.java:51)

Is there a way to print the soap message out before calling invokeBlocking?

Code excluding header code, same as before.

rpcAxSys rpc = new rpcAxSys(args[0],args[1],args[2]);
EndpointReference targetEPR = new
EndpointReference("https://pcary571.corp.nortel.com/Authorize/Service.asmx";);
RPCServiceClient serviceClient = new RPCServiceClient();
Options options = serviceClient.getOptions();
options.setTo(targetEPR);
serviceClient.addHeader(rpc.header2());  // header2 has header generation
code below
QName opSetClaim = new QName("beta", "GetClaim" );
Object[] opSetParams = new Object[] { rpc.agentID, rpc.agentToken,
rpc.requestor };
Class[] returnTypes = new Class[] { Object.class };
Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
returnTypes); FAILING HERE 




Michele Mazzucco-2 wrote:
> 
> Daniel,
> 
> could you please enable the debug  of javac (it is enabled by default,
> remove the -g:none option) and tell us which line causes the problem?
> 
> Michele
> 
> On Thu, 2007-05-10 at 05:28 -0700, Daniel Herbison wrote:
>> Thank you for your replies!
>> I tried the code below and still get a runtime casting error.
>> 
>> Exception in thread "main" java.lang.ClassCastException:
>> org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
>> at rpcAxSys.header2(Unknown Source)
>> at rpcAxSys.main(Unknown Source)
>> 
>> SOAP12Factory factory = (SOAP12Factory)
>> OMAbstractFactory.getSOAP12Factory();
>> OMNamespace omNs = factory.createOMNamespace("beta.va.nortel.com",
>> "xmlns"); 
>> 
>> SOAPHeader header = factory.createSOAPHeader();
>> 
>> SOAPHeaderBlock block = factory.createSOAPHeaderBlock("BasicCredentials",
>> omNs);
>> 
>> OMElement serviceId = factory.createOMElement("serviceId", omNs); 
>> OMText serviceIdText = factory.createOMText(serviceId, agentID);
>> serviceId.addChild(serviceIdText); 
>> 
>> OMElement serviceKey = factory.createOMElement("serviceKey", omNs); 
>> OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
>> serviceKey.addChild(serviceKeyText); 
>> 
>> block.addChild(serviceId);
>> block.addChild(serviceKey);
>> 
>> header.addChild(block);
>> 
>> 
>> Amila Suriarachchi wrote:
>> > 
>> > I am not sure about your problem.
>> > but add this code to specifically set the soap12 for service client.
>> > 
>> > clientOptions = new Options();
>> >
>> clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
>> > );
>> > serviceClient.setOptions(clientOptions);
>> > 
>> > On 5/10/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Daniel,
>> >>
>> >> I think the way you create the SOAPHeaderBlock is not correct. Can
>> >> you try this way please?
>> >>
>> >> SOAP12Factory factory = (SOAP12Factory)
>> >> OMAbstractFactory.getSOAP12Factory();
>> >> OMNamespace omNs = factory.createOMNamespace(
>> >> "http://...";,
>> >> "..."
>> >> );
>> >>
>> >> SOAPEnvelope env = factory.createSOAPEnvelope();
>> >> SOAPHeader header = factory.createSOAPHeader();
>> >> SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
>> >> SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
>> >> OMElement type = factory.createOMElement(
>> >> SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);
>> >>
>> >> type.setText(MessageType.UPLOAD.value());
>> >> block.addChild(type);
>> >> header.addChild(block);
>> >>
>> >> SOAPBody body = factory.createSOAPBody();
>> >> OMElement method = factory.createOMElement(SOAPUtils.UPLOAD_SERVICE,
>> >> omNs);
>> >>
>> >> OMElement name = factory.createOMElement(
>> >> SOAPUtils.UPLOAD_SERVICE_FILE_NAME, omNs);
>> >> name.setText(this.fileName);
>> >>
>> >> method.addChild(name);
>> >> body.addChild(method);
>> >> env.addChild(header);
>> >> env.addChild(body);
>> >>

Re: Axis2: OMElement response message problem

[Martin Gainty]

Any reason why you are cannot xmit the entity with Attachment as in 
/sample/soapwithattachments/client/SWAClient.java example?

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Reneta Säll (HF/EBC) 
  To: axis-user@ws.apache.org 
  Sent: Thursday, May 10, 2007 9:51 AM
  Subject: Axis2: OMElement response message problem


  Hi everybody,

  I'm having a problem with Axis2 web service that uploads txt file. The 
downloading works fine. 
  The file content is binary 64 type and is transfered as xml element in the 
Soap message.(not as attachment!!!)
  The size of my txt file is 3 KB. When I minimized the file size to1 KB then 
the problem does't exist.  

  The web service works fine with Axis 1.4. but not in Axis2?

  Is the max size of the OMElement in the response limited: firstChild, 
LastChild in some way?

  When I ran the client  it occured a wrong: java.lang.NullPointerException, 
then I debuged, it shows that: com.sun.jdi.InvocationException - exception held 
inside the result.


  I am using autogenerated wsdl2java Stub:

  public org.apache.axiom.om.OMElement View( org.apache.axiom.om.OMElement 
param18) throws java.rmi.RemoteException


  {

  try

  {

  org.apache.axis2.client.OperationClient _operationClient = 
_serviceClient.

  createClient(_operations[0].getName());

  _operationClient.getOptions().setAction("urn:#View");

  _operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);


  // create SOAP envelope with that payload

  org.apache.axiom.soap.SOAPEnvelope env = null;


  //Style is Doc.


  env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),param18,optimizeContent(new
 javax.xml.namespace.QName("","View")));


  //adding SOAP headers

  _serviceClient.addHeadersToEnvelope(env);

  // create message context with that soap envelope

  org.apache.axis2.context.MessageContext _messageContext = new 
org.apache.axis2.context.MessageContext();

 _messageContext.setEnvelope(env);


  // add the message contxt to the operation client

  _operationClient.addMessageContext(_messageContext);


  //execute the operation client

  _operationClient.execute(true);


  org.apache.axis2.context.MessageContext _returnMessageContext = 
_operationClient.getMessageContext 
(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);

  org.apache.axiom.soap.SOAPEnvelope _returnEnv = 
_returnMessageContext.getEnvelope();


  org.apache.axiom.om.OMElement omElement = 
_returnEnv.getBody().getFirstElement();



  java.lang.Object object = fromOM( 
_returnEnv.getBody().getFirstElement(), org.apache.axiom.om.OMElement.class, 
getEnvelopeNamespaces(_returnEnv));

  
_messageContext.getTransportOut().getSender().cleanup(_messageContext);

  return (org.apache.axiom.om.OMElement) object;


  }

  When I debug this (autogenerated) piece of code with a breakpoint on the 
return statement, the debugger says "com.sun.jdi.InvocationException occurred 
invoking method" and I get cin the client  java.lang.NullPointerException.

  I hope this is enough information. Please help me out with this.


  Best regards, Reneta

   

Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Amila Suriarachchi]

have you put elementFormDefault="qualified" in your schma?

On 5/10/07, Stephane Roy <[EMAIL PROTECTED]> wrote:


Hi,

The XSD schema used by my WSDL defines the following types:

...
   
 

   
 
   
 
 
   
 
   

 
   
...

In short, typeA uses typeB, typeB being defined within typeA.


I generated the code for the server in adb mode with the command

$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd

Then in /tmp/my/dir/server/src, I have a java file for typeB, for which
the package name is not set ('package ;'). As a result, the java code
cannot be compiled.

I have this problem with Axis2.1.1.1 and with the latest release
(Axis2.1.2).


However, if I change my XSD schema, to have something like this:

...
   
 
   
   
 
   

   
 
   
   
 
   
...

In short, typeB is now defined at the top-level in the XSD schema and
typeA defines elementB which uses a reference to typeB.

Now, the code generation in adb mode works fine and the java files
compile.


I would like to know if someone had this kind of problem before.
Is this behavior a known issue or a limitation of Axis2.1.x ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent


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





--
Amila Suriarachchi,
WSO2 Inc.

RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning

[Ted Jones]

Thanks Amila. I appreciate the input. I am using Dual channel since it
appeared to be required per this thread:
http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/%3C
[EMAIL PROTECTED] Is this
the case? I am using Sandesha2 1.1 with Axis2 1.1.1.
 
I have verified your points outlined below. Everything appears correct.
 
Martin - I will put together a reproducible test case and post ASAP.
 
Thanks for your assistance.
Ted
 
 


From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 10, 2007 12:25 AM
To: axis-user@ws.apache.org; Martin Gainty
Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning


Are you using the Dual chanel mode or single chanel?

if you set the setUseSeparateListener your request comes in a different
http chanel than you send the request. Otherwise it comes in the same
chanel.

In the dual chanel model, What happens is your client starts a simple
http server on your machine and set the ReplyTo addressing header to
point to the stated server. 

So you have to make sure these things.
1. you must have engage the Addressing. (otherwise server won't be able
to find the reply location)
2. client uses the port and the host name you have specified in the
axis2.xml to start its simple http server and set this address to
replyTo filed. So you have to use two seperate axis2.xml files for
client and the server with different port numbers if you run them both
in one machine.

3. if your server is in out side your firewall, the host name you
specify in the client axis2.xml should be able to access from the out
side the firewall.



On 5/10/07, Martin Gainty <[EMAIL PROTECTED]> wrote: 

Good Evening

if you publish your wsdl we can run the client code

Thanks
Martin--
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this email
message is 
addressed.  If you have received this email message in error,
please notify
the sender immediately by telephone or email and destroy the
original
message without making a copy.  Thank you.

- Original Message - 
From: "Ted Jones" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, May 09, 2007 7:10 PM 
Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning


So, I'm guessing that the message is never reaching the server.
Which
may explain why there is no logging? I can see in debug where
the 
Sandesha2 logic is hit and the message is sent but I never see
any
sequences or other message traffic and my client is left polling
forever
waiting for the callback to complete.

Any other thoughts on what might be happening here or where else
I can 
look?

Thanks,
Ted

-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning

Thanks for all the responses. This is a great mailing list.

I am not seeing any messages in TCPMON or in the logs. :-( 

Question: How can you configure TCPMON to capture messages sent
to
SimpleHTTPServer? I get a port bind exception.

Also, I cannot seems to get logging working with Sandesha2. If
anyone
has it working, I would really appreciate a peek at their 
log4j.properties.

Thanks!
Ted

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 11:12 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning

Ted Jones wrote:

> I am using Sandesha2 with an asynch Axis2 client. Using the
example
> that comes with Sandesha2 (the asynch echo client), the
onComplete() 
> method of my callback is never hit. It appears the response is
not
> returning.
>
> Any ideas?

Did you try capturing message sequences with TCPMON and chek the
message
sequence?

Also, have a look into the server and client logs.

Samisa...



-
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] Service Versioning support ?

[Samaya Althuru]

Any ideas please

My question is...
Suppose if we need to update schema as per new clients requirements which is 
already published to existing clients. How to support existing customers 
without effecting them from new changes immediately?

Thanks,
Samaya

Samaya Althuru <[EMAIL PROTECTED]> wrote: Hi Team,

Is Axis2 supports service version in the recent releases? If yes, how?
If not, how to achieve it?
Any recommendations would be great.


Thanks in advance,
Samaya


 

-
Ahhh...imagining that irresistible "new car" smell?
 Check out new cars at Yahoo! Autos. 

   
-
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.

maven2 wsdl2code plugin

[Ecker Severin]

Hi,

I've just updated my repository to use the newest axis2 snapshot which
fixed a few bugs that concerned me, but now the wsdl2code mojo doesn't
work anymore at all:

[ERROR] BUILD ERROR
[INFO]

[INFO] Internal error in the plugin manager executing goal
'org.apache.axis2:axis2-wsdl2code-maven-plugin:SNAPSHOT:wsdl2
code': Unable to find the mojo
'org.apache.axis2:axis2-wsdl2code-maven-plugin:SNAPSHOT:wsdl2code' in
the plugin 'org.apa
che.axis2:axis2-wsdl2code-maven-plugin'
org/apache/axis2/wsdl/codegen/CodeGenerationException

this is the output I get when I try to run it.
Any ideas anyone??? (it did work before of course)

My thanks in advance, cheers,
Severin


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

Axis2: OMElement response message problem

[HF/EBC]

Hi everybody,
 
I'm having a problem with Axis2 web service that uploads txt file. The 
downloading works fine. 
The file content is binary 64 type and is transfered as xml element in the Soap 
message.(not as attachment!!!)
The size of my txt file is 3 KB. When I minimized the file size to1 KB then the 
problem does't exist.  
 
The web service works fine with Axis 1.4. but not in Axis2?
 
Is the max size of the OMElement in the response limited: firstChild, LastChild 
in some way?
 
When I ran the client  it occured a wrong: java.lang.NullPointerException, then 
I debuged, it shows that: com.sun.jdi.InvocationException - exception held 
inside the result.

 
I am using autogenerated wsdl2java Stub:
 
public org.apache.axiom.om.OMElement View( org.apache.axiom.om.OMElement 
param18) throws java.rmi.RemoteException

{

try

{

org.apache.axis2.client.OperationClient _operationClient = 
_serviceClient.

createClient(_operations[0].getName());

_operationClient.getOptions().setAction("urn:#View");

_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);

// create SOAP envelope with that payload

org.apache.axiom.soap.SOAPEnvelope env = null;

//Style is Doc.

env = 
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),param18,optimizeContent(new
 javax.xml.namespace.QName("","View")));

//adding SOAP headers

_serviceClient.addHeadersToEnvelope(env);

// create message context with that soap envelope

org.apache.axis2.context.MessageContext _messageContext = new 
org.apache.axis2.context.MessageContext();

   _messageContext.setEnvelope(env);

// add the message contxt to the operation client

_operationClient.addMessageContext(_messageContext);

//execute the operation client

_operationClient.execute(true);

org.apache.axis2.context.MessageContext _returnMessageContext = 
_operationClient.getMessageContext 
(org.apache.axis2.wsdl.WSDLConstants.MESSAGE_LABEL_IN_VALUE);

org.apache.axiom.soap.SOAPEnvelope _returnEnv = 
_returnMessageContext.getEnvelope();

org.apache.axiom.om.OMElement omElement = 
_returnEnv.getBody().getFirstElement();

java.lang.Object object = fromOM( 
_returnEnv.getBody().getFirstElement(), org.apache.axiom.om.OMElement.class, 
getEnvelopeNamespaces(_returnEnv));

_messageContext.getTransportOut().getSender().cleanup(_messageContext);

return (org.apache.axiom.om.OMElement) object;

}

When I debug this (autogenerated) piece of code with a breakpoint on the return 
statement, the debugger says "com.sun.jdi.InvocationException occurred invoking 
method" and I get cin the client  java.lang.NullPointerException.

I hope this is enough information. Please help me out with this.
 
 
Best regards, Reneta

 

Re: Creating Axis2 SOAP Header

[Michele Mazzucco]

Daniel,

could you please enable the debug  of javac (it is enabled by default,
remove the -g:none option) and tell us which line causes the problem?

Michele

On Thu, 2007-05-10 at 05:28 -0700, Daniel Herbison wrote:
> Thank you for your replies!
> I tried the code below and still get a runtime casting error.
> 
> Exception in thread "main" java.lang.ClassCastException:
> org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
> at rpcAxSys.header2(Unknown Source)
> at rpcAxSys.main(Unknown Source)
> 
> SOAP12Factory factory = (SOAP12Factory)
> OMAbstractFactory.getSOAP12Factory();
> OMNamespace omNs = factory.createOMNamespace("beta.va.nortel.com", "xmlns"); 
> 
> SOAPHeader header = factory.createSOAPHeader();
> 
> SOAPHeaderBlock block = factory.createSOAPHeaderBlock("BasicCredentials",
> omNs);
> 
> OMElement serviceId = factory.createOMElement("serviceId", omNs); 
> OMText serviceIdText = factory.createOMText(serviceId, agentID);
> serviceId.addChild(serviceIdText); 
> 
> OMElement serviceKey = factory.createOMElement("serviceKey", omNs); 
> OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
> serviceKey.addChild(serviceKeyText); 
> 
> block.addChild(serviceId);
> block.addChild(serviceKey);
> 
> header.addChild(block);
> 
> 
> Amila Suriarachchi wrote:
> > 
> > I am not sure about your problem.
> > but add this code to specifically set the soap12 for service client.
> > 
> > clientOptions = new Options();
> > clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
> > );
> > serviceClient.setOptions(clientOptions);
> > 
> > On 5/10/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> >>
> >> Daniel,
> >>
> >> I think the way you create the SOAPHeaderBlock is not correct. Can
> >> you try this way please?
> >>
> >> SOAP12Factory factory = (SOAP12Factory)
> >> OMAbstractFactory.getSOAP12Factory();
> >> OMNamespace omNs = factory.createOMNamespace(
> >> "http://...";,
> >> "..."
> >> );
> >>
> >> SOAPEnvelope env = factory.createSOAPEnvelope();
> >> SOAPHeader header = factory.createSOAPHeader();
> >> SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
> >> SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
> >> OMElement type = factory.createOMElement(
> >> SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);
> >>
> >> type.setText(MessageType.UPLOAD.value());
> >> block.addChild(type);
> >> header.addChild(block);
> >>
> >> SOAPBody body = factory.createSOAPBody();
> >> OMElement method = factory.createOMElement(SOAPUtils.UPLOAD_SERVICE,
> >> omNs);
> >>
> >> OMElement name = factory.createOMElement(
> >> SOAPUtils.UPLOAD_SERVICE_FILE_NAME, omNs);
> >> name.setText(this.fileName);
> >>
> >> method.addChild(name);
> >> body.addChild(method);
> >> env.addChild(header);
> >> env.addChild(body);
> >>
> >>
> >> Michele
> >>
> >>
> >>
> >>
> >> On 9 May 2007, at 22:26, Daniel Herbison wrote:
> >>
> >> >
> >> > I'm trying to add the SOAP header, described in comment in code
> >> > below, to a
> >> > RPC call to a service.  First of all I really do not know if the
> >> > code to
> >> > create the header is correct, i think it is in the ball park(?)
> >> > But I get a
> >> > run time error of:
> >> >
> >> > Exception in thread "main" java.lang.ClassCastException:
> >> > org.apache.axiom.om.impl.OMNamespaceImpl
> >> > at
> >> > org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.
> >> > (SOAPHeaderBlockImpl.java:54)
> >> > at
> >> > org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.
> >> > (SOAP12HeaderBlockImpl.java:45)
> >> > at rpcAxSys.main(Unknown Source)
> >> >
> >> > the line causing the run time error is marked below, why is this
> >> > doing this?
> >> > Also, is the header creation correct?
> >> >
> >> > code--
> >> > RPCServiceClient serviceClient = new RPCServiceClient();
> >> > Options options = serviceClient.getOptions();
> >> > EndpointReference targetEPR = new
> >> > EndpointReference("https://xyz/Authorize/Service.asmx";);
> >> > options.setTo(targetEPR);
> >> >
> >> > /* header build
> >> >  
> >> >   
> >> >string1
> >> >string2
> >> >   
> >> >  
> >> >  */
> >> > OMFactory fac = OMAbstractFactory.getOMFactory();
> >> > OMNamespace omNs = fac.createOMNamespace("beta", "xmlns");
> >> >
> >> > SOAPFactory soapFactory = new SOAP12Factory();
> >> > SOAPHeaderBlock soapHeaderBlock = new
> >> > SOAP12HeaderBlockImpl("Security",omNs,soapFactory);
> >> > soapHeaderBlock.setMustUnderstand(true);
> >> >
> >> > OMElement basicCredentials = fac.createOMElement
> >> > ("BasicCredentials", omNs);
> >> >
> >> > OMElement serviceId = fac.createOMElement("serviceId", omNs);
> >> > OMText serviceIdText = fac.createOMText(serviceId, agentID);
> >> > serviceId.addChild(serviceIdText);
> >> >
> >> > OMElement serviceKey = fac.createOMElement("serviceKey", omNs);
> >> > OMText serviceKeyText = fac.createOMText(service

Re: Unexpected subelement, encryption problem

[Jon Horsman]

see my comment on this issue.
http://issues.apache.org/jira/browse/RAMPART-29
Can you find the decripted message and send us?


"you can put an System.out at the message Receiver and see the message"

I'll see if i can figure out exactly where to put the system.out but I
haven't done any axis coding so i'm not very familiar with axis in
general, i was just tasked to make things secure.  Hopefully the
message receiver class is obvious, if not, i'll post back asking  you
to be more specific if possible.


It looks a little bit strange, ... maybe it is an axis2 bug and not a rampart 
bug. But please
take a look. I'm not so deep inside the axis stuff!


Is there a known workaround for this issue?  Our web service is
supposed to be going to a client with a very large contract soon and
they won't accept it if its not sending secure messages.  As mentioned
i'm not very familiar with what axis has to offer, if there is no
known workaround for this is there another technology/way to get axis
to send its info encrypted?

Thanks,

Jon.

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

[Axis2] Incomplete code generation with wsdl2java, in adb mode

[Stephane Roy]

Hi,

The XSD schema used by my WSDL defines the following types:

...
  


  

  


  

  


  
...

In short, typeA uses typeB, typeB being defined within typeA.


I generated the code for the server in adb mode with the command

$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o 
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd


Then in /tmp/my/dir/server/src, I have a java file for typeB, for which 
the package name is not set ('package ;'). As a result, the java code 
cannot be compiled.


I have this problem with Axis2.1.1.1 and with the latest release 
(Axis2.1.2).



However, if I change my XSD schema, to have something like this:

...
  

  
  

  

  

  
  

  
...

In short, typeB is now defined at the top-level in the XSD schema and 
typeA defines elementB which uses a reference to typeB.


Now, the code generation in adb mode works fine and the java files compile.


I would like to know if someone had this kind of problem before.
Is this behavior a known issue or a limitation of Axis2.1.x ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent


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

Re: Creating Axis2 SOAP Header

[Daniel Herbison]

Thank you for your replies!
I tried the code below and still get a runtime casting error.

Exception in thread "main" java.lang.ClassCastException:
org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
at rpcAxSys.header2(Unknown Source)
at rpcAxSys.main(Unknown Source)

SOAP12Factory factory = (SOAP12Factory)
OMAbstractFactory.getSOAP12Factory();
OMNamespace omNs = factory.createOMNamespace("beta.va.nortel.com", "xmlns"); 

SOAPHeader header = factory.createSOAPHeader();

SOAPHeaderBlock block = factory.createSOAPHeaderBlock("BasicCredentials",
omNs);

OMElement serviceId = factory.createOMElement("serviceId", omNs); 
OMText serviceIdText = factory.createOMText(serviceId, agentID);
serviceId.addChild(serviceIdText); 

OMElement serviceKey = factory.createOMElement("serviceKey", omNs); 
OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
serviceKey.addChild(serviceKeyText); 

block.addChild(serviceId);
block.addChild(serviceKey);

header.addChild(block);


Amila Suriarachchi wrote:
> 
> I am not sure about your problem.
> but add this code to specifically set the soap12 for service client.
> 
> clientOptions = new Options();
> clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
> );
> serviceClient.setOptions(clientOptions);
> 
> On 5/10/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>>
>> Daniel,
>>
>> I think the way you create the SOAPHeaderBlock is not correct. Can
>> you try this way please?
>>
>> SOAP12Factory factory = (SOAP12Factory)
>> OMAbstractFactory.getSOAP12Factory();
>> OMNamespace omNs = factory.createOMNamespace(
>> "http://...";,
>> "..."
>> );
>>
>> SOAPEnvelope env = factory.createSOAPEnvelope();
>> SOAPHeader header = factory.createSOAPHeader();
>> SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
>> SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
>> OMElement type = factory.createOMElement(
>> SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);
>>
>> type.setText(MessageType.UPLOAD.value());
>> block.addChild(type);
>> header.addChild(block);
>>
>> SOAPBody body = factory.createSOAPBody();
>> OMElement method = factory.createOMElement(SOAPUtils.UPLOAD_SERVICE,
>> omNs);
>>
>> OMElement name = factory.createOMElement(
>> SOAPUtils.UPLOAD_SERVICE_FILE_NAME, omNs);
>> name.setText(this.fileName);
>>
>> method.addChild(name);
>> body.addChild(method);
>> env.addChild(header);
>> env.addChild(body);
>>
>>
>> Michele
>>
>>
>>
>>
>> On 9 May 2007, at 22:26, Daniel Herbison wrote:
>>
>> >
>> > I'm trying to add the SOAP header, described in comment in code
>> > below, to a
>> > RPC call to a service.  First of all I really do not know if the
>> > code to
>> > create the header is correct, i think it is in the ball park(?)
>> > But I get a
>> > run time error of:
>> >
>> > Exception in thread "main" java.lang.ClassCastException:
>> > org.apache.axiom.om.impl.OMNamespaceImpl
>> > at
>> > org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.
>> > (SOAPHeaderBlockImpl.java:54)
>> > at
>> > org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.
>> > (SOAP12HeaderBlockImpl.java:45)
>> > at rpcAxSys.main(Unknown Source)
>> >
>> > the line causing the run time error is marked below, why is this
>> > doing this?
>> > Also, is the header creation correct?
>> >
>> > code--
>> > RPCServiceClient serviceClient = new RPCServiceClient();
>> > Options options = serviceClient.getOptions();
>> > EndpointReference targetEPR = new
>> > EndpointReference("https://xyz/Authorize/Service.asmx";);
>> > options.setTo(targetEPR);
>> >
>> > /* header build
>> >  
>> >   
>> >string1
>> >string2
>> >   
>> >  
>> >  */
>> > OMFactory fac = OMAbstractFactory.getOMFactory();
>> > OMNamespace omNs = fac.createOMNamespace("beta", "xmlns");
>> >
>> > SOAPFactory soapFactory = new SOAP12Factory();
>> > SOAPHeaderBlock soapHeaderBlock = new
>> > SOAP12HeaderBlockImpl("Security",omNs,soapFactory);
>> > soapHeaderBlock.setMustUnderstand(true);
>> >
>> > OMElement basicCredentials = fac.createOMElement
>> > ("BasicCredentials", omNs);
>> >
>> > OMElement serviceId = fac.createOMElement("serviceId", omNs);
>> > OMText serviceIdText = fac.createOMText(serviceId, agentID);
>> > serviceId.addChild(serviceIdText);
>> >
>> > OMElement serviceKey = fac.createOMElement("serviceKey", omNs);
>> > OMText serviceKeyText = fac.createOMText(serviceKey, agentToken);
>> > serviceKey.addChild(serviceKeyText);
>> >
>> > basicCredentials.addChild(serviceId);
>> > basicCredentials.addChild(serviceKey);
>> >
>> > soapHeaderBlock.addChild(basicCredentials);
>> >
>> > serviceClient.addHeader(soapHeaderBlock);
>> > // end header build
>> >
>> > QName opSetClaim = new QName("beta", "GetClaim" );
>> >
>> > Object[] opSetParams = new Object[] { agentID, agentToken,
>> > requestor };
>> > Class[] returnTypes = new Class[] { Object.class };
>> >
>> > Obj

Re: Performances of Axis2 over Axis 1.1

[Amila Suriarachchi]

I think the problem is with the xmlbeans. xml beans is a slow databinding
framewrok.
Try to use ADB or jibx which are much faster data binding frame works.



On 5/4/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:


Jack

I'm still not sure what you are describing. WSDL is a description
language that typically isn't used at runtime. The actual message
exchanges are made using SOAP.

Axis2 can typically serve around 110req/s of SOAP messages when using
a large and complex payload (100k in/100k out of complex object-mapped
XML) on a modern machine, so I'm wondering whats going on with your
case.

Is it possible you can post your WSDL, a sample SOAP message, or even
better your code?

Paul

On 5/4/07, Jacky Rymasz-Maillot <[EMAIL PROTECTED]> wrote:
> Hello Paul,
>
> My server application is receiving WSDL requests and my server perform
functional work then returns a WSDL response using.
>
> When I run my test class, I got the response from my server about 2-3
seconds after sending the request. The functional part takes only 600ms.
> Both server and test class are on my dev computer.
> The message sent to the client is rather large.
> But my questioning is more about the performance difference between AXIS
1.1 and AXIS2 which is almost identical.
>
> Paul, tell me if you need more info to understand my problem.
>
> And thank you very much for your help
>
> Jack
>
> -Message d'origine-
> De: Paul Fremantle [mailto:[EMAIL PROTECTED]
> Envoyé: vendredi 4 mai 2007 12:13
> À: axis-user@ws.apache.org
> Objet: Re: Performances of Axis2 over Axis 1.1
>
> Jacky
>
> I'm not clear what you mean by "generate some WSDL responses".
>
> Can you explain exactly what you want to run faster? Its very unusual
> too see response times of 2-3 seconds. On small messages I see
> response times of 2-3milliseconds!
>
> Paul
>
> On 5/4/07, Jacky Rymasz-Maillot <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Hello,
> >
> >
> >
> > We have a server which is using Axis1.1 for WSDL request/response.
> >
> > We have noticed that Axis 1.1 was taking too long time to generate
some WSDL
> > responses (the functional part is taking about 600ms but the
transformation
> > to WSDL is taking about 2000-2500ms).
> >
> > Response speed is quite an important factor for us.
> >
> >
> >
> > We heard that Axis2 was about 10 times faster than old version of
Axis, so I
> > did a test and adapted Axis2 onto the server, but we don't see any
time
> > response improvement!
> >
> >
> >
> > I generated my java classes from a wsdl file.
> >
> > I am using xmlbeans binding with AXIS2 1.2RC
> >
> > Is there a way to monitor were the time is used into Axis?
> >
> >
> >
> > What did I do wrong?
> >
> > Thx ;)
> >
> >
> >
> > Jack
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

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





--
Amila Suriarachchi,
WSO2 Inc.

Re: Sequence of choices, or "no serializer for AnyType"

[Amila Suriarachchi]

try to generate the code with ADB binding (i.e the defult) and using -b (for
backwork compatibility) option



On 5/7/07, Axel Bock <[EMAIL PROTECTED]> wrote:


Hi Paul,

thanks for that. I just learned that our decision for Axis1 had other
reasons, I just assumed it was compatibility with 1.4. One of those things
you "think" you know ... :-) .

still, switching to Axis2 is not a good option, cause the complete project
works with 1.4 right now, and that would mean a major rewrite in the final
development phase. Not good, no time for that. Unless Axis2 guarantees that
the stubs are identical to the ones from Axis1, which I don't actually
believe.

Can I - somehow - define a custom mapping of these data types, or the
wrapping element? I could parse that manually via DOM for example ... but I
don't know how ...


Thanks & greetings,
Axel.



On 5/7/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Axel
>
> Axis2 is 1.4 compatible.
>
> Paul
>
>
> On 5/7/07, Axel Bock < [EMAIL PROTECTED]> wrote:
> >
> > Hi Anne,
> >
> > I am sorry. I forgot to mention that Axis2 is not an option for this
> > project, becasue we need Java 1.4 compatibility.
> >
> > Do you have any other ideas, maybe? :-)
> >
> >
> > Greetings & thanks,
> > Axel.
> >
> >
> >
> >
> > On 5/6/07, Anne Thomas Manes <[EMAIL PROTECTED] > wrote:
> > > Try using Axis2 with the XMLBeans databinding.
> > >
> > > On 5/4/07, Axel Bock < [EMAIL PROTECTED]> wrote:
> > > > Hi list,
> > > >
> > > > Using Axis 1.4 I ran into a very annoying problem, based on this
> thing
> > in my
> > > > web service schema:
> > > >
> > > >  
> > > >   
> > > >
> > > > 
> > > > 
> > > >  
> > > >   
> > > >
> > > >
> > > >   
> > > >  
> > > > 
> > > >
> > > >   
> > > >  
> > > >
> > > > Now every time axis tries to parse the answer with more than one
> element
> > in
> > > > the DocumentList type I get the following error:
> > > >
> > > > No deserializer for
> > > >
> > 
{http://www.w3.org/2001/XMLSchema}anyType
> >org.xml.sax.SAXException
> > :
> > > > No deserializer for {
> > > > 
http://www.w3.org/2001/XMLSchema}anyType
> > > > I found a post concerning that topic back from 2002, which
> basically
> > said
> > > > "bad luck, axis does not do this". (see here:
> > > >
> > http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200204.mbox/[EMAIL 
PROTECTED]
>
> > > > ).
> > > >
> > > > I tried to change the choise(0..n) thing to a
> sequence(0..n)-->choice
> > thing,
> > > > or a sequence(1)-->choice(0..n) thing, but both did not help. I
> had a
> > look
> > > > into the stubs and they always look the same - they only seem to
> expect
> > ONE
> > > > sub-element under DocumentList.
> > > >
> > > >
> > > > This is ... well, kind of mission-critical for us here, so I would
> be
> > > > thankful for every suggestion.
> > > >
> > > >
> > > > cheers & thanks in advance,
> > > > Axel.
> > >
> > >
> > -
> > > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2 1.2] Migrated from Axis2-1.1.1 to Axis2-1.2 and ...

[Amila Suriarachchi]

can you send your wsdl and options you used in wsdl2java?

On 5/8/07, Rudolph, Troy <[EMAIL PROTECTED]> wrote:


 Hello Samaya,

When I installed Axis2-1.2, I regenerated the code using WSDL2Java, and
then rebuilt the project.  I did not change anything other than to add the
implementation code in XXXSkeleton.java.  Interestingly, there is no
method like the one Axis2 seems to be looking for in the generated skeleton
class.  So, I wonder where it was supposed to be implemented.

Thanks
Troy

 --
*From:* Samaya Althuru [mailto:[EMAIL PROTECTED]
*Sent:* Monday, May 07, 2007 3:15 PM
*To:* axis-user@ws.apache.org
*Subject:* Re: [Axis2 1.2] Migrated from Axis2-1.1.1 to Axis2-1.2 and ...

Hi Troy,

Recently, I too got the same problem because i have used new AxisFault
constructor provided by Axis2 1.2, which takes Message Context. I have
resolved it by passing proper message context.

In Axis2 1.2, AxisFault class has been improved to have
FaultMessageContext. Did you change AxisFault creation at server side?
Could you send the client code?

Regards,
Samaya



*"Rudolph, Troy" <[EMAIL PROTECTED]>* wrote:

Hi All,
After migrating from Axis2-1.1.1 to Axis2-1.2, my application fails.  The
client code receives the exception below.  This all worked great before.  Is
1.2 ot compatible with 1.1.1?
org.apache.axis2.AxisFault: ServiceClass does not implement required
method of the form OMElement getContent(OMElement e)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(*
Utils.java:434*)
at org.apache.axis2.description.OutInAxisOperationClient.send(*
OutInAxisOperation.java:373*)
at org.apache.axis2.description.OutInAxisOperationClient.execute(*
OutInAxisOperation.java:294*)
at com.ca.contentupdate.cus.CUSStub.getContent(*CUSStub.java:141*)
at com.ca.contentupdate.cus.CUSClient.getContent(*CUSClient.java
:61*)
at com.ca.contentupdate.cus.CUSTester.main(*CUSTester.java:36*)
Exception in thread "main"* java.lang.NullPointerException*
at com.ca.contentupdate.cus.CUSTester.main(*CUSTester.java:37*)

Thanks very much!
Troy Rudolph
Computer Associates
Senior Software Engineer
tel: +1 512 401-2273
fax: +1 512 401-2205
[EMAIL PROTECTED]


 --
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! 
Travelto
 find your fit.





--
Amila Suriarachchi,
WSO2 Inc.

Re: Unexpected subelement, encryption problem

[Jochen Zink]

Hi,

I have captured the messages and have done some tests. You can see the very 
strange results an the issue. http://issues.apache.org/jira/browse/RAMPART-29

It looks a little bit strange, ... maybe it is an axis2 bug and not a rampart 
bug. But please take a look. I'm not so deep inside the axis stuff!

thanks


> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 10.05.07 09:00:24
> An: axis-user@ws.apache.org
> Betreff: Re: Unexpected subelement, encryption problem

see my comment on this issue. http://issues.apache.org/jira/browse/RAMPART-29
> Can you find the decripted message and send us?
> 
> 
> 
> On 5/10/07, Jochen Zink <[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I have not a solution for your problem, because I have the same one :)
> 
> Please take a look at this bug http://issues.apache.org/jira/browse/RAMPART-29
> 
> 
> Maybe it hits your problem, to.
> 
> regards
> Jochen
> 
> 
> 
> > -Ursprüngliche Nachricht-
> > Von: axis-user@ws.apache.org
> > Gesendet: 09.05.07 20:24:16
> > An: axis-user@ws.apache.org
> > Betreff: Unexpected subelement, encryption problem
> 
> 
> >
> > Hello,
> >
> > I'm trying to get encryption working with axis using rampart.  I was
> 
> > having a hard time getting everything working but think i have worked
> > through all the encryption related setup issues (i'm not getting
> > random exceptions anymore).
> >
> > I currently have the following in my axis2.xml file
> >
> > 
> > 
> > 
> > Encrypt
> > jontest
> 
> > com.mitel.me.soap.ssserver.TestCallBack
> > client.properties
> > 
> > 
> 
> > 
> > 
> > Encrypt
> > client.properties
> > 
> com.mitel.me.soap.ssserver.TestCallBack
> > 
> > 
> >
> > client.properties looks like
> >
> > org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
> 
> > org.apache.ws.security.crypto.merlin.keystore.type=jks
> > org.apache.ws.security.crypto.merlin.file=testkeystore
> > org.apache.ws.security.crypto.merlin.keystore.password=default
> >
> > I created the key using
> 
> >
> > keytool -genkey -keyalg rsa -alias ME -keypass default -keystore
> > testkeystore -storepass default
> >
> > When i start up tomcat i immediately get an error message.
> >
> > "java.lang.RuntimeException
> : Unexpected subelement Result"
> >
> > This is being thrown from an auto generated 'parse' method in one of
> > the stub files as seen below.
> >
> > public static LoginResponse parse(javax.xml.stream.XMLStreamReader
> 
> > reader) throws java.lang.Exception
> >
> > 
> > if (reader.isStartElement() && new
> > javax.xml.namespace.QName("","return").equals(reader.getName
> ())){
> >  
> > object.set_return(com.mitel.www.mixml.ss.CmdResponse.Factory.parse(reader));
> >  reader.next();
> > }  // End of if for expected property start element
> > else{
> > // A start element we are not expecting indicates an invalid parameter
> 
> > was passed
> > throw new java.lang.RuntimeException("Unexpected subelement " +
> > reader.getLocalName());
> > }
> >
> > If i comment out the encryption stuff in the axis2.xml file that i
> 
> > mentioned above our web service functions as expected.  I'm pretty
> > much at a loss as to what the problem could be.  I've tried attaching
> > the debugger and stepping through the auto generated code and nothing
> 
> > is jumping out at me as being 'wrong'.
> >
> > Anyone have any advice?
> >
> > Thanks,
> >
> > Jon H.
> >
> > -
> 
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> >
> >
> 
> 
> ___
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
> 
> 
> -
> To unsubscribe, e-mail: 
> [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> -- 
> Amila Suriarachchi,
> 
> WSO2 Inc.
> 


___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192


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

Re: Keystore in Axis2 war

[Amila Suriarachchi]

I think you can give the full path to file here
e.g.
org.apache.ws.security.crypto.merlin.file=/home/test/TestKeyStore

or a relative path from the jboss bin folder


On 5/9/07, sridhar vudutha <[EMAIL PROTECTED]> wrote:


Martin,
 Putting the test.properties file in  $JBOSS_HOME/server/default/conf/props,
worked fine. How can I take the KeyStore out of the war file? I tried
putting it in the same directory (  $JBOSS_HOME/server/default/conf/props)
but didn't work. Any suggestions?

Thanks,
Sridhar.



On 5/8/07, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
>  Sridhar--
> did you try
> $JBOSS_HOME/server/default/conf/props
> ?
> M--
> This email message and any files transmitted with it contain
> confidential
> information intended only for the person(s) to whom this email message
> is
> addressed.  If you have received this email message in error, please
> notify
> the sender immediately by telephone or email and destroy the original
> message without making a copy.  Thank you.
>
>
> - Original Message -
> *From:* sridhar vudutha <[EMAIL PROTECTED]>
> *To:* axis-user@ws.apache.org
> *Sent:* Tuesday, May 08, 2007 1:08 PM
> *Subject:* Keystore in Axis2 war
>
>
> Hello,
> I'm having trouble taking out the KeyStore or the properties file
> from the Axis2 war file. As long as they are in the Axis2.war/WEB-INF/classes
> directory, everything works fine. I'm using JBoss 4.0.5 and would like
> to put KeyStore or the properties file outside the Axis2.war file. I
> tried putting it in Jboss/server/default/lib ; Jboss/server/conf and also
> manually updated the JBoss CLASSPATH in the run.bat file but doesn't
> work.
>
> The properties  file (test.properties) in Axis2.war/WEB-INF/classes
> folder has the following contents.
>
>
> 
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
> org.apache.ws.security.components.crypto.Merlin
> org.apache.ws.security.crypto.merlin.keystore.type=jks
> org.apache.ws.security.crypto.merlin.keystore.password=password
> org.apache.ws.security.crypto.merlin.keystore.alias=uattest
> org.apache.ws.security.crypto.merlin.alias.password=password
> org.apache.ws.security.crypto.merlin.file=TestKeyStore
>
> If I keep both the TestKeyStore and test.properties files in the
> Axis2.war/WEB-INF/classes folder, it works fine.
>
> Can someone please suggest me how to put make the properties file or the
> KeyStore file available to Axis2.war after it is deployed?
>
> I'm putting Axis2.war in an ear which contains some jars and 2 other war
> files.
>
> Any help would be greatly appreciated.
>
> Thanks,
> Sridhar.
>
>




--
Amila Suriarachchi,
WSO2 Inc.

Re: [AXIS2] Module not avaible exception

[Amila Suriarachchi]

try to create the service client like this

ConfigurationContext configurationContext =

ConfigurationContextFactory.createConfigurationContextFromFileSystem(AXIS2_REPOSITORY,
AXIS2_CONF);
   ServiceClient sender = new ServiceClient(configurationContext,
null);

By giving a valid axis2.xml file and a repository

On 5/9/07, Lorenzo <[EMAIL PROTECTED]> wrote:


Hi all,

i have this problem:

1)receive a message context from epr1
2)save and edit it
3)send to epr2
4)collect epr2's response, save, edit and send it to epr1

now with 1.2 release is easy to save and restore message context, but i
have problems to send them to other epr...

i tried this:

-
-

ServiceClient sender = new ServiceClient();

OperationClient opClient =
sender.createClient(ServiceClient.ANON_OUT_IN_OP);

MessageContext outMsgCtx = new MessageContext();

Options opts = outMsgCtx.getOptions();

opts.setTo(new EndpointReference(epr2));

opts.setTransportInProtocol(Constants.TRANSPORT_HTTP);

opClient.addMessageContext(outMsgCtx);

opClient.execute(true);

-
-

but i get this error:

org.apache.axis2.deployment.DeploymentException: The system is
attempting to engage a module that is not available: addressing
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(
DeploymentEngine.java:156)
at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(
FileSystemConfigurator.java:116)
at

org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext
(ConfigurationContextFactory.java:60)
at

org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem
(ConfigurationContextFactory.java:174)
at
org.apache.axis2.client.ServiceClient.initializeTransports(
ServiceClient.java:211)
at
org.apache.axis2.client.ServiceClient.configureServiceClient(
ServiceClient.java:138)
at
org.apache.axis2.client.ServiceClient.(ServiceClient.java:133)
at
org.apache.axis2.client.ServiceClient.(ServiceClient.java:229)
at
org.openspcoop.OpenSPCoopMessage.fire(OpenSPCoopMessage.java:118)
at
org.openspcoop.OpenSPCoopMessageReceiver.receive(
OpenSPCoopMessageReceiver.java:47)
at
org.openspcoop.OpenSPCoopDispatcher.findOperation(
OpenSPCoopDispatcher.java:66)
at
org.apache.axis2.engine.AbstractDispatcher.invoke(AbstractDispatcher.java
:100)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
HTTPTransportUtils.java:279)
at
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:216)
at
org.apache.axis2.transport.http.server.AxisHttpService.doService(
AxisHttpService.java:275)
at
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(
AxisHttpService.java:184)
at
org.apache.axis2.transport.http.server.HttpServiceProcessor.run(
HttpServiceProcessor.java:74)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.AxisFault: The system is attempting to
engage a module that is not available: addressing
at
org.apache.axis2.engine.AxisConfiguration.engageModule(
AxisConfiguration.java:396)
at
org.apache.axis2.deployment.DeploymentEngine.engageModules(
DeploymentEngine.java:614)
at
org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(
DeploymentEngine.java:152)
... 22 more


addressing module is present...

any suggestion?



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





--
Amila Suriarachchi,
WSO2 Inc.

[Axis 1.4] setReturnType is guessing the wrong type

[etoom etoom]

Hi,

I have this code:
..
QName returnTypeName = new QName("http://www.w3.org/2001/XMLSchema";, "string");
call.setReturnType(returnTypeName);
..

When I call invoke I get the following exception:
caught exception while handling request: deserialization error:
unexpected element type:
expected={http://www.w3.org/2001/XMLSchema}string,
actual={http://schemas.xmlsoap.org/soap/encoding/}string

Why did Axis change the type from XMLSchema:string to
SOAPEnccoding:string is this a bug?

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

Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning

[Paul Fremantle]

Ted

I'm with Martin! I think the easiest thing would be if you could send
us a simple test case that shows what's happening.

Paul

On 5/10/07, Ted Jones <[EMAIL PROTECTED]> wrote:

So, I'm guessing that the message is never reaching the server. Which
may explain why there is no logging? I can see in debug where the
Sandesha2 logic is hit and the message is sent but I never see any
sequences or other message traffic and my client is left polling forever
waiting for the callback to complete.

Any other thoughts on what might be happening here or where else I can
look?

Thanks,
Ted

-Original Message-
From: Ted Jones [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 10:27 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning

Thanks for all the responses. This is a great mailing list.

I am not seeing any messages in TCPMON or in the logs. :-(

Question: How can you configure TCPMON to capture messages sent to
SimpleHTTPServer? I get a port bind exception.

Also, I cannot seems to get logging working with Sandesha2. If anyone
has it working, I would really appreciate a peek at their
log4j.properties.

Thanks!
Ted

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 11:12 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning

Ted Jones wrote:

> I am using Sandesha2 with an asynch Axis2 client. Using the example
> that comes with Sandesha2 (the asynch echo client), the onComplete()
> method of my callback is never hit. It appears the response is not
> returning.
>
> Any ideas?

Did you try capturing message sequences with TCPMON and chek the message
sequence?

Also, have a look into the server and client logs.

Samisa...


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





--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

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

Re: Release notes don't mention change in class name for generated stubs

[Amila Suriarachchi]

I really sorry for your inconvenience. Anyway we discussed this in user and
developer lists.
Earlier Axis2 generated the code only for one port. But now it generates the
code for all the ports
So if you want to generate the code only for one binding please specify them
with the
-sn  -pn  attributes.


On 5/9/07, John G. Norman <[EMAIL PROTECTED]> wrote:


I notice that codegen'd client stubs in 1.2 now have names like

UserServiceUserServiceSOAP12Port_httpStub

rather than

UserServiceStub

I suppose I can live with the name change, though it did, er, break my
build script -- but the fact that this change is not mentioned in the
release notes is inexcusable.

If the changes are buried in JIRA, you might provide a link in the
release notes that would pull up the changes for the particular
packages or tools.

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





--
Amila Suriarachchi,
WSO2 Inc.

Re: Unexpected subelement, encryption problem

[Amila Suriarachchi]

see my comment on this issue.
http://issues.apache.org/jira/browse/RAMPART-29
Can you find the decripted message and send us?


On 5/10/07, Jochen Zink <[EMAIL PROTECTED]> wrote:


Hello,

I have not a solution for your problem, because I have the same one :)

Please take a look at this bug
http://issues.apache.org/jira/browse/RAMPART-29

Maybe it hits your problem, to.

regards
Jochen



> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 09.05.07 20:24:16
> An: axis-user@ws.apache.org
> Betreff: Unexpected subelement, encryption problem


>
> Hello,
>
> I'm trying to get encryption working with axis using rampart.  I was
> having a hard time getting everything working but think i have worked
> through all the encryption related setup issues (i'm not getting
> random exceptions anymore).
>
> I currently have the following in my axis2.xml file
>
> 
> 
> 
> Encrypt
> jontest
> com.mitel.me.soap.ssserver.TestCallBack

> client.properties
> 
> 
> 
> 
> Encrypt
> client.properties
> com.mitel.me.soap.ssserver.TestCallBack

> 
> 
>
> client.properties looks like
>
>
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
> org.apache.ws.security.crypto.merlin.keystore.type=jks
> org.apache.ws.security.crypto.merlin.file=testkeystore
> org.apache.ws.security.crypto.merlin.keystore.password=default
>
> I created the key using
>
> keytool -genkey -keyalg rsa -alias ME -keypass default -keystore
> testkeystore -storepass default
>
> When i start up tomcat i immediately get an error message.
>
> "java.lang.RuntimeException: Unexpected subelement Result"
>
> This is being thrown from an auto generated 'parse' method in one of
> the stub files as seen below.
>
> public static LoginResponse parse(javax.xml.stream.XMLStreamReader
> reader) throws java.lang.Exception
>
> 
> if (reader.isStartElement() && new
> javax.xml.namespace.QName("","return").equals(reader.getName())){
>  object.set_return(com.mitel.www.mixml.ss.CmdResponse.Factory.parse
(reader));
>  reader.next();
> }  // End of if for expected property start element
> else{
> // A start element we are not expecting indicates an invalid parameter
> was passed
> throw new java.lang.RuntimeException("Unexpected subelement " +
> reader.getLocalName());
> }
>
> If i comment out the encryption stuff in the axis2.xml file that i
> mentioned above our web service functions as expected.  I'm pretty
> much at a loss as to what the problem could be.  I've tried attaching
> the debugger and stepping through the auto generated code and nothing
> is jumping out at me as being 'wrong'.
>
> Anyone have any advice?
>
> Thanks,
>
> Jon H.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192


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





--
Amila Suriarachchi,
WSO2 Inc.