question modifying WSDL2C generated stubs
Hello, this should be easy but I failed.
I want to skip deserialisation of one element in a WSDL2C-generated
stub. I comment out the block that does the deserialisation, but in the
next block I lose current_node:
current_node = axiom_node_get_next_sibling(current_node, env);
current_node is null but I know there is another node. Get_next_sibling
returns null because the following case is true in
axiom_stax_builder_next_with_token()
if (om_builder-done)
{
AXIS2_ERROR_SET(env-error,
AXIS2_ERROR_BUILDER_DONE_CANNOT_PULL,
AXIS2_FAILURE);
return -1;
}
I have been reading the code to try to understand where the builder is
generated, when it is set to done, etc. I don't understand how the
block I commented out affects this. The builder only seems generated
once, and the done property is affected when the payload is read using
build_all(). But I know if this block wasn't commented out, the
current_node would not be null!
Anyone have an idea what to do?
To recap:
XML contains
A
B
C
D
Elements.
In deserialize() it says
Building A
Building B
Building C
Building D
I want to do this
Building A
Building B
//Building C
Building D
And still have current_node point to D correctly
Carl LEFRANÇOIS
Analyste Programmeur - Études et développement
AXA Canada Tech
2020, rue University - Bureau 600, Montréal (Québec), H3A 2A5
carl.lefranc...@axa-canada.com
Tél. :éc514-282-6817, poste 4548
Téléc. :514-282-6017
www.axa.com
_
Ce message est confidentiel, à l'usage exclusif du destinataire
ci-dessus et son contenu ne représente en aucun cas un engagement de la
part de AXA, sauf en cas de stipulation expresse et par écrit de la part
de AXA. Toute publication, utilisation ou diffusion, même partielle,
doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
message, merci d'en avertir immédiatement l'expéditeur.
This e-mail message is confidential, for the exclusive use of the
addressee and its contents shall not constitute a commitment by AXA,
except as otherwise specifically provided in writing by AXA. Any
unauthorized disclosure, use or dissemination, either whole or partial,
is prohibited. If you are not the intended recipient of the message,
please notify the sender immediately.
Class cast Exception, trying to create a own Token issuer
Hi all,
I'm trying to make my own little SAML issuer, that implements the
TokenIssuer class of rampart-trust. But when I call the service I get this
error
java.lang.ClassCastException:
no.uib.bccs.esysbio.services.sts.EsysbioSAMLIssuer cannot be cast to
org.apache.rahas.TokenIssuer
even though my class implements TokenIssuer
public class EsysbioSAMLIssuer implements TokenIssuer {
@Override
public String getResponseAction(RahasData arg0) throws TrustException {
// TODO Auto-generated method stub
return null;
}
@Override
public SOAPEnvelope issue(RahasData arg0) throws TrustException {
System.out.println(Key size + arg0.getKeysize());
return null;
}
@Override
public void setConfigurationElement(OMElement arg0) {
// TODO Auto-generated method stub
}
@Override
public void setConfigurationFile(String arg0) {
// TODO Auto-generated method stub
}
@Override
public void setConfigurationParamName(String arg0) {
// TODO Auto-generated method stub
}
}
My configuration of the issuer in service.xml looks like this
parameter name=token-dispatcher-configuration
token-dispatcher-configuration
!-- Issuers. You may have many issuers. --
issuer
class=no.uib.bccs.esysbio.services.sts.EsysbioSAMLIssuer
default=true
tokenType
http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1
/tokenType
/issuer
/token-dispatcher-configuration
/parameter
I looked at the rampart page for this and to me it looks the same, but I
guess there must be an error somewhere.
One possible reason for the error could be that, I need to have
rampart-trust.jar file in both tomcat/lib and axis2/WEB-INF/lib in my tomcat
web server. If I don't have this I get error about not finding certain
classes.
Does anyone have a good tip for me??
cheers, Håkon
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
Re: deploy both client and server in tomcat
Hi By looking into the axis2 source code, I have a solution like this ConfigurationContext ctx= ListenerManager.defaultConfigurationContext; sc = new ServiceClient(ctx, null); sc.engageModule(rampart); However, I have an exception:Unable to engage module : rampart Any help on configuring axis2 client in server is really appreciated. thanks -jason jason zhang wrote: Hi, All I am using axis2-1.4. I had the service deployed to tomcat and it is tested. I also developed client using the AXIOM. The client is initialized like this ConfigurationContext ctx = ConfigurationContextFactory.createConfigurationContextFromFileSystem(TestConfig.repo_dir, null); sc = new ServiceClient(ctx, null); sc.engageModule(rampart); Right now, I need to move the client code to tomcat and use it as a library. How can I obtain a ConfigurationContext in server? I know the axis2 definitely creates configurationContext for its services. I just do not know how to obtain the configuration for my client. Help is appreciated. thanks -jason
Using xmlbeans binding and axiom in same service
Hi A possible stupid question, but I need ask it, when making a service that can handle mtom. Can one generate the service from WSDL using any databinding(xmlbeans,adb) etc? Just as long as one enables it in the service.xml? and does the same stand for the client side generation of code? cheers, Håkon -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company)
Re: Axis2 Jboss and SSL issue
You can see the tutorials here to enable SSL on JBoss.
http://www.theserverside.com/discussions/thread.tss?thread_id=22243
http://roneiv.wordpress.com/2008/01/03/jboss-tutorial-how-to-enable-ssl-https-on-jboss-as-well-as-other-nice-to-know-configurations/
Thanks,
Sudhir
On Thu, Apr 16, 2009 at 3:47 PM, Darshana ® srdarsh...@gmail.com wrote:
Hi,
I'm trying to configure SSL for axis2 on jboss. Problem is I dont know
where to put the .jks file. I tried putting the jks file to following
locations.
WEB-INF directory of the web archive.
META-INF directory of the web archive
jboss home directory
{jboss home}/server/default directory
{jboss home}/server/default/deploy directory
{jboss home}/bin directory
Also I tried with the absolute path of the .jks (localhost.jks in my case)
file.
Following are my Keystore and Truststore parameters in
transportReceiver and transportSender beans included in the axis2.xml
parameter name=keystore locked=false
KeyStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
KeyPassword123456/KeyPassword
/KeyStore
/parameter
parameter name=truststore locked=false
TrustStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
/TrustStore
/parameter
When I'm starting the jboss server, everytime it gives an error like this.
java.lang.NullPointerException
at
org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener.getSSLContext(HttpCoreNIOSSLListener.java:96)
at
org.apache.axis2.transport.nhttp.HttpCoreNIOListener.init(HttpCoreNIOListener.java:151)
at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4069)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4373)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5310)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
But when I commented out above mentioned parameters from axis2.xml
file, server starts sucessfully without any errors.
Please give me idea, where should I put the localhost.jks file
Re: Axis2 Jboss and SSL issue
Hi Sudhir,
Thanks a lot for your quick reply, but I have already enabled ssl for
jboss sucessfully. What Im currently trying to do is enabling the ssl
for axis2. Thats where I have stuck now. Any idea??
Thanks..
On Thu, Apr 16, 2009 at 3:52 PM, Sudhir Mongia sudhir.mon...@gmail.com wrote:
You can see the tutorials here to enable SSL on JBoss.
http://www.theserverside.com/discussions/thread.tss?thread_id=22243
http://roneiv.wordpress.com/2008/01/03/jboss-tutorial-how-to-enable-ssl-https-on-jboss-as-well-as-other-nice-to-know-configurations/
Thanks,
Sudhir
On Thu, Apr 16, 2009 at 3:47 PM, Darshana ® srdarsh...@gmail.com wrote:
Hi,
I'm trying to configure SSL for axis2 on jboss. Problem is I dont know
where to put the .jks file. I tried putting the jks file to following
locations.
WEB-INF directory of the web archive.
META-INF directory of the web archive
jboss home directory
{jboss home}/server/default directory
{jboss home}/server/default/deploy directory
{jboss home}/bin directory
Also I tried with the absolute path of the .jks (localhost.jks in my case)
file.
Following are my Keystore and Truststore parameters in
transportReceiver and transportSender beans included in the axis2.xml
parameter name=keystore locked=false
KeyStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
KeyPassword123456/KeyPassword
/KeyStore
/parameter
parameter name=truststore locked=false
TrustStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
/TrustStore
/parameter
When I'm starting the jboss server, everytime it gives an error like this.
java.lang.NullPointerException
at
org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener.getSSLContext(HttpCoreNIOSSLListener.java:96)
at
org.apache.axis2.transport.nhttp.HttpCoreNIOListener.init(HttpCoreNIOListener.java:151)
at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4069)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4373)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5310)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
But when I commented out above mentioned parameters from axis2.xml
file, server starts sucessfully without any errors.
Please give me idea, where should I put the localhost.jks file
Axis2 Jboss and SSL issue
Hi,
I'm trying to configure SSL for axis2 on jboss. Problem is I dont know
where to put the .jks file. I tried putting the jks file to following
locations.
WEB-INF directory of the web archive.
META-INF directory of the web archive
jboss home directory
{jboss home}/server/default directory
{jboss home}/server/default/deploy directory
{jboss home}/bin directory
Also I tried with the absolute path of the .jks (localhost.jks in my case) file.
Following are my Keystore and Truststore parameters in
transportReceiver and transportSender beans included in the axis2.xml
parameter name=keystore locked=false
KeyStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
KeyPassword123456/KeyPassword
/KeyStore
/parameter
parameter name=truststore locked=false
TrustStore
Locationlocalhost.jks/Location
TypeJKS/Type
Password123456/Password
/TrustStore
/parameter
When I'm starting the jboss server, everytime it gives an error like this.
java.lang.NullPointerException
at
org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener.getSSLContext(HttpCoreNIOSSLListener.java:96)
at
org.apache.axis2.transport.nhttp.HttpCoreNIOListener.init(HttpCoreNIOListener.java:151)
at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4069)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4373)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5310)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
But when I commented out above mentioned parameters from axis2.xml
file, server starts sucessfully without any errors.
Please give me idea, where should I put the localhost.jks file
RE: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing
Good Morning Glenn/Andreas
noting the version of Version.java from the distro located t
http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5/
package sample.axisversion;
public class Version {
public String getVersion() throws Exception {
return Hi - the Axis2 version is +
org.apache.axis2.Version.getVersionText();
}
}
i see this error in /modules/codegen/target/surefire-reports/
TEST-org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.xml
testcase time=0.11
classname=org.apache.axis2.wsdl.codegen.XML2JavaMappingTest
name=testVersion
error message=sample.axisversion.xsd.Version
type=java.lang.ClassNotFoundExceptionjava.lang.ClassNotFoundException:
sample.axisversion.xsd.Version
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:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.testVersion(XML2JavaMappingTest.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
/error
/testcase
seems like the package sample.axisversion.xsd.Version
is not the actual java class version located at
sample.axisversion.Version
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de
déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then
we ask politely to report. Each unauthorized forwarding or manufacturing of a
copy is inadmissible. This message serves only for the exchange of information
and has no legal binding effect. Due to the easy manipulation of emails we
cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Wed, 15 Apr 2009 12:32:32 -0400
To: axis-...@ws.apache.org; axis-user@ws.apache.org
Subject: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing
From: g...@thoughtcraft.com
Hi all!
After a failed set of attempts to use the Maven release
RE: Dodging the spam filter Axis admin won't start
This may be ClassLoader conflict. Look at this thread: http://www.nabble.com/Axis2-Service-Deployment-Question-td19390975s134.html#a19513947 From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Wednesday, April 15, 2009 7:42 PM To: axis-user@ws.apache.org Subject: RE: Dodging the spam filter Axis admin won't start check commons-fileupload-1.2.jar in located on your %CLASSPATH% my commons-fileupload-1.2.jar is located on \axis2-1.5\stagingRepo\axis2-1.5\lib\commons-fileupload-1.2.jar HTH Martin __ Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: ckn...@onebox.com To: axis-user@ws.apache.org Subject: Dodging the spam filter Axis admin won't start Date: Wed, 15 Apr 2009 19:13:44 -0400 Log entries appear in: C:\geronimo\geronimo-tomcat6-javaee5-2.1.4\var\log\geronimo.log The relevant section starts with: 2009-04-15 18:25:42,609 ERROR [[AxisAdminServlet]] Allocate exception for servlet AxisAdminServlet java.lang.ClassNotFoundException: org.apache.commons.fileupload.FileUploadException in classloader org.apache.geronimo.configs/axis2/2.1.4/car At face value, it looks like a class that should have been included in the download doesn't seem to have been there. What do you suggest? -- Charles Knell ckn...@onebox.com - email Rediscover Hotmail®: Now available on your iPhone or BlackBerry Check it out.http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Mobile1_042009 STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at g...@whisolutions.com, and destroy all copies of this message and any attachments.
Rampart symetric encryption.
Anybody could explain me how does encryptionSymAlgorithm and encryptionKeyTransportAlgorithm work. i need to implement a kind of symetric session key to encryt my data, signing with my assymetric key. I need to know if configuring this params it solves my problem. As we say, dont reivent the wheel. Thanks, JP.
Re: Axis2 commons-httpclient 3.1 dependencies
Guillaume, I think it's a great idea to upgrade to a recent version of httpclient. One of the prerequisite would be to solve AXIS2-3933 so that axis2-kernel no longer depends on commons-httpclient. Since Axis2 1.5 is going to be released soon, we can again do larger changes to the trunk. Also, there is a patch available for AXIS2-3933, so we could solve that issue quite quickly. This will also tell us if there is any code in Axis2 that has a hidden dependency on commons-httpclient. For CommonsHTTPTransportSender, I think we should avoid creating a new transport sender. I would suggest that you do your changes on a well defined version of the transport so that we can later commit these changes to the codebase. Did you already start to analyze the amount of changes that are required to upgrade CommonsHTTPTransportSender to commons-httpclient 4.0? Andreas On Wed, Apr 15, 2009 at 15:57, Jeudy, Guillaume gje...@teksystems.com wrote: Hi, I'm considering upgrading axis2 to use the new httpclient 4.0 in conjunction with jcifs library in order to support HTTP NTLMv2 connections. I need feedback from axis2 contributors/developers. Please confirm what steps I should take to achieve that. 1. Implement a new TransportSender using httpclient 4.0. I'm hoping I can base my code on the existing CommonsHTTPTransportSender and port it to use httpclient 4.0. 2. Modify axis2.xml to use my new TransportSender. Can anyone tell me if there are any hidden runtime dependencies I should be aware of? Based on the axis2 source code analysis I made; it seems like httpclient 3.1 is only used in CommonsHTTPTransportSender class and that class can be completely ignored at runtime if axis2.xml is not configured to use it, please correct me if i'm wrong. Thank you! -Guillaume Jeudy This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
RE: Axis2 commons-httpclient 3.1 dependencies
Andreas, I have looked at AXIS2-3933 and I'm not sure the patch is complete. I was thinking to create a new transport as to avoid recompiling axis2 with httpclient 4.0 and hopefully save some time. Additionnally I was planning to hard-code NTLMv2 support into that transport using JCIFS library as outlined here: http://hc.apache.org/httpcomponents-client/ntlm.html. I don't think such support should be committed in axis2 trunk because there are legal implications: JCIFS is licensed under the Lesser General Public License (LGPL). This license is not compatible with the Apache Licenses under which all Apache Software is released. Lawyers of the Apache Software Foundation are currently investigating under which conditions Apache software is allowed to make use of LGPL software. Hardcoding axis2 to use httpclient 4.0 is the best long term solution for the trunk as long as nothing outside the CommonsHTTPTransportSender and it's apparatus are directly dependent of httpclient library. I guess I could find a way to upgrade CommonsHTTPTransportSender to httpclient 4.0 without any NTLM support (that is a step backwards considering httpclient 3.1 has limited NTLMv1 support). Additionnally you will have to advise me; find some kind of pluggable mechanism that allows a user through configuration to add NTLM support (with jcifs library). I haven't looked into more details for the changes required to upgrade CommonsHTTPTransportSender yet. Thanks, -Guillaume From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Thu 4/16/2009 10:44 AM To: axis-user@ws.apache.org Subject: Re: Axis2 commons-httpclient 3.1 dependencies Guillaume, I think it's a great idea to upgrade to a recent version of httpclient. One of the prerequisite would be to solve AXIS2-3933 so that axis2-kernel no longer depends on commons-httpclient. Since Axis2 1.5 is going to be released soon, we can again do larger changes to the trunk. Also, there is a patch available for AXIS2-3933, so we could solve that issue quite quickly. This will also tell us if there is any code in Axis2 that has a hidden dependency on commons-httpclient. For CommonsHTTPTransportSender, I think we should avoid creating a new transport sender. I would suggest that you do your changes on a well defined version of the transport so that we can later commit these changes to the codebase. Did you already start to analyze the amount of changes that are required to upgrade CommonsHTTPTransportSender to commons-httpclient 4.0? Andreas On Wed, Apr 15, 2009 at 15:57, Jeudy, Guillaume gje...@teksystems.com wrote: Hi, I'm considering upgrading axis2 to use the new httpclient 4.0 in conjunction with jcifs library in order to support HTTP NTLMv2 connections. I need feedback from axis2 contributors/developers. Please confirm what steps I should take to achieve that. 1. Implement a new TransportSender using httpclient 4.0. I'm hoping I can base my code on the existing CommonsHTTPTransportSender and port it to use httpclient 4.0. 2. Modify axis2.xml to use my new TransportSender. Can anyone tell me if there are any hidden runtime dependencies I should be aware of? Based on the axis2 source code analysis I made; it seems like httpclient 3.1 is only used in CommonsHTTPTransportSender class and that class can be completely ignored at runtime if axis2.xml is not configured to use it, please correct me if i'm wrong. Thank you! -Guillaume Jeudy This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. winmail.dat
service specific folder configuration
Hi all, you know how we deploy all services in /WEB-INF/services/ folder -- But my requirement is to have service specific folder mapping. Therefore I thought if I create folder in services directory as myservice1 and myservice2 and deploy them as follows: 1) /WEB-INF/services/myservice1/myService1 2) /WEB-INF/services/myservice2/myService2 The goal is that if the user says http://localhost:/axis2/services/myservice1/myService1?wsdl -- then he/she should be able to get the wsdl same if she does http://localhost:/axis2/services/myservice2/myService2?wsdl -- then he/she should be able to get the wsdl I am testing this in Tomcat 6.0.18 and have axis2.1.4.1 Please let me know how can I achieve this - thanks a lot. regards, rishi
Re: service specific folder configuration
I remember that sometime ago there has been a discussion on this list about exactly this requirement, but I don't remember the conclusions. I think the discussion was also about versioning. Maybe that will help you to find the relevant posts in the mailing list archives. Andreas On Thu, Apr 16, 2009 at 18:22, rishi kapur@gmail.com wrote: Hi all, you know how we deploy all services in /WEB-INF/services/ folder -- But my requirement is to have service specific folder mapping. Therefore I thought if I create folder in services directory as myservice1 and myservice2 and deploy them as follows: 1) /WEB-INF/services/myservice1/myService1 2) /WEB-INF/services/myservice2/myService2 The goal is that if the user says http://localhost:/axis2/services/myservice1/myService1?wsdl -- then he/she should be able to get the wsdl same if she does http://localhost:/axis2/services/myservice2/myService2?wsdl -- then he/she should be able to get the wsdl I am testing this in Tomcat 6.0.18 and have axis2.1.4.1 Please let me know how can I achieve this - thanks a lot. regards, rishi
Axis2 Serialization/De-serialization issue
I have attempted to search online for documentation on the subject, but
I have not found sufficient information, but I am open to other links
people may provide.
We have a java webservice which utilizes inheritance. So say that we
have the following classes:
Public abstract class AbstractClass{
// some code here
}
Public class AbstractClassImp extends AbstractClass {
// some other suff here
}
And this is the service method:
Public SomeClass doService(AbstractClass someClass) {
// logic goes here
}
Now when I send a soap message from the client I see that the xsi:type
flag does indeed point ot the AbstractClassImp. However, the class that
gets created during serialization is the AbstractClass (which results in
an error) since it is the object type from the webservice's argument.=20
I believe that the client is correctly serializing the object, but the
server is not handling the de-serialization/serialization correctly.
So here is the question
How do I tell axis2 which class should be created from the xsi:type?
Or is there something else I should be doing?
Thank you.
Securing Axis2 REST Style Services
HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay
Re: Re: service specific folder configuration
Thank you so much for the reply. But the closest that I found was http://wso2.org/library/90 -- but it tells me somewhat the same thing as before - I still can't have service specific URL configuration. I tried searching with all the keywords that I could think but wasn't able to find the exact discuss in mailing list archive. kind regards, rishi On Apr 16, 2009 12:32pm, Andreas Veithen andreas.veit...@gmail.com wrote: I remember that sometime ago there has been a discussion on this list about exactly this requirement, but I don't remember the conclusions. I think the discussion was also about versioning. Maybe that will help you to find the relevant posts in the mailing list archives. Andreas On Thu, Apr 16, 2009 at 18:22, rishi kapur@gmail.com wrote: Hi all, you know how we deploy all services in /WEB-INF/services/ folder -- But my requirement is to have service specific folder mapping. Therefore I thought if I create folder in services directory as myservice1 and myservice2 and deploy them as follows: 1) /WEB-INF/services/myservice1/myService1 2) /WEB-INF/services/myservice2/myService2 The goal is that if the user says http://localhost:/axis2/services/myservice1/myService1?wsdl -- then he/she should be able to get the wsdl same if she does http://localhost:/axis2/services/myservice2/myService2?wsdl -- then he/she should be able to get the wsdl I am testing this in Tomcat 6.0.18 and have axis2.1.4.1 Please let me know how can I achieve this - thanks a lot. regards, rishi
Re: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing
The code for the Version class in the codegen module is generated by
an invocation of the maven-antrun-plugin plugin during the
generate-test-sources phase. Please have a look at the pom.xml file.
Note that this class has nothing to do with the version service that
is part of the distribution.
Andreas
On Thu, Apr 16, 2009 at 13:39, Martin Gainty mgai...@hotmail.com wrote:
Good Morning Glenn/Andreas
noting the version of Version.java from the distro located t
http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5/
package sample.axisversion;
public class Version {
public String getVersion() throws Exception {
return Hi - the Axis2 version is +
org.apache.axis2.Version.getVersionText();
}
}
i see this error in /modules/codegen/target/surefire-reports/
TEST-org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.xml
testcase time=0.11
classname=org.apache.axis2.wsdl.codegen.XML2JavaMappingTest
name=testVersion
error message=sample.axisversion.xsd.Version
type=java.lang.ClassNotFoundExceptionjava.lang.ClassNotFoundException:
sample.axisversion.xsd.Version
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:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.testVersion(XML2JavaMappingTest.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
/error
/testcase
seems like the package sample.axisversion.xsd.Version
is not the actual java class version located at
sample.axisversion.Version
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note
de déni et de confidentialité
This message is confidential. If you should not be the intended receiver,
then we ask politely to report. Each unauthorized forwarding or
manufacturing of a copy is inadmissible. This message serves only for the
exchange of information and has no legal binding effect. Due to the easy
manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
de ceci est interdite. Ce message sert à l'information seulement et n'aura
pas n'importe quel effet
Re: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing
Thanks, Andreas. Martin, the test you refer to doesn't fail for me when I
build... are you seeing this error when doing a mvn clean install?
Incidentally, I'm in the midst of fixing the poms to include NOTICE and
LICENSE files in all the jars (thanks to Dan Kulp for pointing this out on
IM). Keith just let me know this morning that the WSO2 folks found an issue
they'd like to fix as well, so pending those changes I'll roll out another RC
hopefully by EOD tomorrow, then maybe get a VOTE started early next week.
Thanks,
--Glen
Andreas Veithen wrote:
The code for the Version class in the codegen module is generated by
an invocation of the maven-antrun-plugin plugin during the
generate-test-sources phase. Please have a look at the pom.xml file.
Note that this class has nothing to do with the version service that
is part of the distribution.
Andreas
On Thu, Apr 16, 2009 at 13:39, Martin Gainty mgai...@hotmail.com wrote:
Good Morning Glenn/Andreas
noting the version of Version.java from the distro located t
http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5/
package sample.axisversion;
public class Version {
public String getVersion() throws Exception {
return Hi - the Axis2 version is +
org.apache.axis2.Version.getVersionText();
}
}
i see this error in /modules/codegen/target/surefire-reports/
TEST-org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.xml
testcase time=0.11
classname=org.apache.axis2.wsdl.codegen.XML2JavaMappingTest
name=testVersion
error message=sample.axisversion.xsd.Version
type=java.lang.ClassNotFoundExceptionjava.lang.ClassNotFoundException:
sample.axisversion.xsd.Version
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:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.axis2.wsdl.codegen.XML2JavaMappingTest.testVersion(XML2JavaMappingTest.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
/error
/testcase
seems like the package sample.axisversion.xsd.Version
is not the actual java class version located at
sample.axisversion.Version
Martin
__
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung / Note
de déni et de confidentialité
This message is confidential. If you should not be the intended receiver,
then we ask politely to report. Each unauthorized forwarding or
manufacturing of a copy is inadmissible. This message serves only for the
exchange of information and has no legal binding effect. Due to the easy
manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie
Re: Securing Axis2 REST Style Services
Hi, For the REST style calls you can use HTTPS + Basic Auth Have a look at this [1] handler from WSO2 WSAS. This will simply add the UsernameToken into the SOAP representation of the incoming REST request, which will be processed by Rampart (which you have already configured). Thanks, Ruchith On Thu, Apr 16, 2009 at 3:04 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay -- http://blog.ruchith.org
hot to add Basic Authentication to my service
Hey there, I'd like to deploy a service and require clients to use basic authentication. I found an email [1] from Paul saying that axis2 does not have native support for it, that ws-security is the way to go. But in my case it would be overkilled. His answer is dated from 2006 so I'd like to know if it is still not possible ? Thanks in advance for your answers, good luck to axis2 dev team for the impending release. Alexis [1] http://markmail.org/thread/w2anpwbxbum4x3fb
RE: Securing Axis2 REST Style Services
Hi Ruchith, Thanks for the quick reply. Could you please point me to the link that talks about this solutions. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 4:31 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi, For the REST style calls you can use HTTPS + Basic Auth Have a look at this [1] handler from WSO2 WSAS. This will simply add the UsernameToken into the SOAP representation of the incoming REST request, which will be processed by Rampart (which you have already configured). Thanks, Ruchith On Thu, Apr 16, 2009 at 3:04 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay -- http://blog.ruchith.org
Re: Securing Axis2 REST Style Services
Oops :-) Here you go : https://wso2.org/repos/wso2/branches/wsas/java/2.2/wsas/java/modules/core/src/org/wso2/wsas/security/pox/POXSecurityHandler.java On Thu, Apr 16, 2009 at 8:36 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Ruchith, Thanks for the quick reply. Could you please point me to the link that talks about this solutions. Thanks Sanjay -Original Message- From: Ruchith Fernando [mailto:ruchith.ferna...@gmail.com] Sent: Thursday, April 16, 2009 4:31 PM To: axis-user@ws.apache.org Subject: Re: Securing Axis2 REST Style Services Hi, For the REST style calls you can use HTTPS + Basic Auth Have a look at this [1] handler from WSO2 WSAS. This will simply add the UsernameToken into the SOAP representation of the incoming REST request, which will be processed by Rampart (which you have already configured). Thanks, Ruchith On Thu, Apr 16, 2009 at 3:04 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: HI, I have a POJO based services deployed in axis2 and it's working well. I have implememted the basic user/password security using rampart and it's working fine for SOAP calls. I generated the client using wsdl2java.My question is how do I secure the REST style calls. Do I need to do anything special. I need to deploy these services into production soon and any help or pointers would be greatly appreciated. Thanks Sanjay -- http://blog.ruchith.org -- http://blog.ruchith.org
Re: How to monitor SOAP messages in the Client without changing the server?
Hi Robert, Logging Module is also a server side solution; I need a solution in the client without any change or installing anything in the server. Thanks. Joe. On Wed, Apr 15, 2009 at 8:47 AM, robert lazarski robertlazar...@gmail.comwrote: On Wed, Apr 15, 2009 at 9:44 AM, robert lazarski robertlazar...@gmail.com wrote: On Tue, Apr 14, 2009 at 11:25 PM, Joe Smithian joe.smith...@gmail.com wrote: Hi all, Can any one please let me know how can I display SOAP request and response messages in a SOAP AXIS2 Client GUI application? Umm, the soap monitor perhaps? http://ws.apache.org/axis2/1_4_1/soapmonitor-module.html There's also tcpmon: https://tcpmon.dev.java.net/ - R Oops, I'm just waking up and I just noticed you can't use either of those. Maybe try the Logging Module and get the info you need from there. http://ws.apache.org/axis2/1_4/modules.html - R
