Re: WS-RM does not work?
Hi, I change the Axis2 to version 1.3. And the result is correct. But in the server side console, I always got the warning: /- [WARN] A message has been waiting for a MakeConnection call. The message will co ntinue to wait, but there may be a problem with the client configuration. Sandes ha message type 7. --/ Could anybody tell me why and how can I remove this annoying warning? BTW, I add a serviceClient.cleanup() call at the end to shutdown the simple http server (or the jvm will not exit), is that the cause of this warning? Best Regards, Yang Sun 2008/6/17 Sun Yang <[EMAIL PROTECTED]>: > Hi, > > I am new to axis2 and currently I met a problem with WS-RM using Axis2-1.4 > + Sandesha-1.3. Pls give me some help. > > Problem senario: > Server-side > 1. download the production packages from apache and extract all the > contents in the right place. > 2. set AXIS2_HOME to point to the right location. > 3. copy the RMSampleService.aar in the sandesha2-1.3-bin package to > AXIS2_HOME/repository/services > 4. copy sandesha2-1.3.mar to AXIS2_HOME/repository/modules > 5. start the server with AXIS2_HOME/bin/axis2server.bat. > Client-side > 1. Make a seperate client repo as the Sandesha user guide said. > 2. Start AnonEchoClient.java. > > Problem I met: > Sometimes, the client will complain the following error messages. > org.apache.axis2.AxisFault: A message was added that is not valid. > However, the operation context was complete. > at > org.apache.axis2.description.OutInAxisOperation.addMessageContext(OutInAxisOperation.java:77) > at > org.apache.axis2.context.OperationContext.addMessageContext(OperationContext.java:218) > at > org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:123) > at > org.apache.axis2.engine.AxisEngine.resumeReceive(AxisEngine.java:341) > at > org.apache.sandesha2.workers.InvokerWorker.run(InvokerWorker.java:100) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) > at java.lang.Thread.run(Unknown Source) > At the same time, the server will show some warnings like this: > [WARN] A message has been waiting for a MakeConnection call. The > message will co > ntinue to wait, but there may be a problem with the client > configuration. Sandes > ha message type 7. > > The confusion point is that sometimes 1/3 calls get the correct response, > sometimes 2/3 calls get the responses. And sometimes all the calls failed > with the above error messages. Why I get different results in the runs? > I am not sure whether I missed anything in the configuration. Could anyone > give me a hand? If you need more information, pls tell me. > > Best Regards, > Yang Sun >
Decoding < & > symbols
Hi. I am getting a SOAP request from client in encoded format. *<* being encoded to *"<'"* & *>* being encoded to "*>'" *I would like to know how can I decode it in my SOAP Server?? *-- Thanks & Regards Sandeep Kumar K Sr. Software Engineer Geneva Software Technologies Limited, # 82, Research Center II, I floor, EPIPA Nallurhalli, Whitefield, Bangalore - 560066 Mob : +91-9880193454*
Re: Problems with WSDL references on Axis2 1.3
Hi Amila, Actually, I manually create the .AAR file from my code (using zip compression feature of JDK). It was successfully deployed to the Axis2 server, the WSDL is recognized. and the schema has been validated successfully. When I try to use wsdl2java the generate client stub, (eg: http://localhost:8080/axis2/services/TMCreateApplication?wsdl), some schema imported by WSDL can not be accessed. The example of WSDL is attached with this email. Regards, Sukma On Mon, Jun 16, 2008 at 5:20 PM, Amila Suriarachchi < [EMAIL PROTECTED]> wrote: > How you generate the .aar file. did you use the wsdl2java tool? Can you > send your wsdl? > > thanks > Amila. > > > On Fri, Jun 13, 2008 at 8:22 AM, Sukma Agung Verdianto <[EMAIL PROTECTED]> > wrote: > >> Hi, >> Can anybody help me out of this? >> I can see from the internet there is some problem with nested import of >> schema? >> >> I can;t attach the sample AAR file, I think this mailing list does not >> allow binary attachment? >> >> Regards, >> Sukma >> >> On Wed, Jun 11, 2008 at 12:08 PM, Sukma Agung Verdianto < >> [EMAIL PROTECTED]> wrote: >> >>> Hi All, >>> I have a question regarding WSDL published by a service packaged in AAR. >>> I have a service class, WSDL and all it references (imported WSDL's and >>> schema's) structured like this inside an aar: >>> >>> java >>> -- package >>> ServiceClass.class >>> META-INF >>> -- services.xml >>> -- ExampleService.wsdl >>> -- _ >>> schema1.xsd (this import schema2, >> namespace="namespace" schemaLocation="schema2.xsd"/>) >>> schema2.xsd (let say this schema import schema3 using >> namespace="namespace" schemaLocation="_/schema3.xsd"/>) >>> _ >>> -- schema3.xsd (this import schema 4) >>> -- _ >>> schema4.xsd >>> >>> I can get ExampleService deployed successfully, and it is exposing the >>> right WSDL (using originalWsdl set to true). >>> However, when I try to access the WSDL and get all references, it failed >>> because it cannot find some references... >>> >>> I've digging more, and found out that Axis2 using replacing some relative >>> URL to be something like this format - [ServiceName]?xsd=path/to/xsd >>> This is fine for the XSD that directly imported by WSDL, but not for the >>> XSD imported by ther XSD. >>> Axis2 does not change import definition to >> namespace="namespace" schemaLocation="ServiceName?xsd=_/_/schema3.xsd"/> to >>> import schema3. >>> >>> Is this the right behavior of Axis2? Does't it support nested import? >>> Please give me some insight. >>> >>> Regards, >>> Sukma >>> >> >> > > > -- > Amila Suriarachchi, > WSO2 Inc. http://schemas.xmlsoap.org/wsdl/"; xmlns:bs="urn:xml-gov-au:draft:sig:BusinessSignal:0.1" xmlns:bt="urn:xeda-org:draft:bt:CreateApplicationCommercialTransaction:2.0.0" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"; xmlns:sbd="urn:xml-gov-au:draft:data:messagingAggregates:1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tm="urn:xml-gov-au:draft:tm:TransactionModule:0.1" xmlns:tns="urn:xeda-org:draft:tm:CreateApplicationCommercialTransaction:2.0.0" xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; name="TMCreateApplication" targetNamespace="urn:xeda-org:draft:tm:CreateApplicationCommercialTransaction:2.0.0"> bt:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier bt:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier bt:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier tm:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier tm:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier bs:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier bs:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier bs:StandardBusinessMessageHeader/sbd:BusinessScope/sbd:InstanceIdentifier
WS-RM does not work?
Hi, I am new to axis2 and currently I met a problem with WS-RM using Axis2-1.4 + Sandesha-1.3. Pls give me some help. Problem senario: Server-side 1. download the production packages from apache and extract all the contents in the right place. 2. set AXIS2_HOME to point to the right location. 3. copy the RMSampleService.aar in the sandesha2-1.3-bin package to AXIS2_HOME/repository/services 4. copy sandesha2-1.3.mar to AXIS2_HOME/repository/modules 5. start the server with AXIS2_HOME/bin/axis2server.bat. Client-side 1. Make a seperate client repo as the Sandesha user guide said. 2. Start AnonEchoClient.java. Problem I met: Sometimes, the client will complain the following error messages. org.apache.axis2.AxisFault: A message was added that is not valid. However, the operation context was complete. at org.apache.axis2.description.OutInAxisOperation.addMessageContext(OutInAxisOperation.java:77) at org.apache.axis2.context.OperationContext.addMessageContext(OperationContext.java:218) at org.apache.axis2.util.CallbackReceiver.receive(CallbackReceiver.java:123) at org.apache.axis2.engine.AxisEngine.resumeReceive(AxisEngine.java:341) at org.apache.sandesha2.workers.InvokerWorker.run(InvokerWorker.java:100) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source) At the same time, the server will show some warnings like this: [WARN] A message has been waiting for a MakeConnection call. The message will co ntinue to wait, but there may be a problem with the client configuration. Sandes ha message type 7. The confusion point is that sometimes 1/3 calls get the correct response, sometimes 2/3 calls get the responses. And sometimes all the calls failed with the above error messages. Why I get different results in the runs? I am not sure whether I missed anything in the configuration. Could anyone give me a hand? If you need more information, pls tell me. Best Regards, Yang Sun
Axis2(1.4) + Rampart 1.4 throws exception
I was trying to use Axis2 (1.4) + Rampart 1.4, with a policy file, and I got the following exception: Exception in thread "main" org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'Security' while deploying handler 'PolicyBasedSecurityInHandler'. at org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:75) at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToFlow(PhaseResolver.java:68) at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:104) at org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:110) at org.apache.axis2.description.AxisOperation.onEngage(AxisOperation.java:158) at org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:490) at org.apache.axis2.description.AxisService.onEngage(AxisService.java:785) at org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:490) at org.apache.axis2.description.AxisServiceGroup.onEngage(AxisServiceGroup.java:134) at org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:490) at org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:453) at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:323) at org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:293) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:175) at org.apache.axis2.client.ServiceClient.(ServiceClient.java:143) at ws.landslide.security.Axis2ClientWssePolicy.main(Axis2ClientWssePolicy.java:29) at these lines of code on my client side: String args1 = "C:/java/eclipse/workspace/Axis2Client"; ConfigurationContext ctx = ConfigurationContextFactory.createConfigurationContextFromFileSystem(args1, null); ServiceClient client = new ServiceClient(ctx, null); It seems that the second parameter of "ConfigurationContextFactory.createConfigurationContextFromFileSystem(args1, null);" cannot be set null as it is shown here. The exception is thrown long before the code reaches the following 2 lines: String args2 = "policy.xml"; options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, loadPolicy(args2)); Please advise how to resolve this error. Thanks! -- View this message in context: http://www.nabble.com/Axis2%281.4%29-%2B-Rampart-1.4-throws-exception-tp17877253p17877253.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: More SOAP Attachment Questions
I have an XML appliance that works only with SOAP with Attachments, AND it is expecting a WSDL that uses mime multipart/related definitions. I was wondering if there was a way to tweak the Axis2 sample of SWA to use this kind of WSDL? Can anyone provide such a WSDL for my testing. I appreciate this very much. __ Marc Lefebvre, Principle Software Engineer Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 Phone: (808)442-7168, Email: [EMAIL PROTECTED] echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc <>- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: getClass().getResource() in .aar?
It turns out that the problem was not with getResource() but with embedded
spaces in the returned resource string being converted to %20. The
following code resolved it:
File propfile;
try {
propfile = new File(propUrl.toURI());
}
catch (URISyntaxException e) {
propfile = new File(propUrl.getPath());
}
An interesting and useful additional point emerged, which I will mention
just in case anyone ever runs into this sort of problem. Because Axis2 is
running the class, the syntax:
propUrl = this.getClass().getResource("/myservice.properties");
looks in /webapps/axis2/WEB-INF/classes, not in the root of the
.aar. Knowing this can be handy, as it allows a service aar to be updated
without resetting custom properties. Not knowing it can be frustrating, for
obvious reasons.
_
Stephen Kilburn, GeoPraxis Inc.
-Original Message-
From: Stephen Kilburn [mailto:[EMAIL PROTECTED]
Sent: June 9, 2008 22:15
To: axis-user@ws.apache.org
Subject: getClass().getResource() in .aar?
Hi,
I am attempting to embed a resource file in an Axis2 .aar, but haven't been
able to make this work.
I have been using the syntax:
URL propUrl = this.getClass().getResource("/myResource.properties");
This returns null. I've tried putting the resource file in various places
in the .aar, but so far no joy.
I'm running this as a Spring application, BTW. Not sure if that makes a
difference.
Am I missing something, or is there some special syntax I need to use to
make this work? (I would be happy placing the properties outside the .aar
if that is easier.)
Thanks in advance for any replies.
_
Stephen Kilburn, GeoPraxis Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Send direct XML rather than using Java classes
Use the SAAJ API. See http://users.skynet.be/pascalbotte/rcx-ws-doc/saajpost.htm for samples. Anne On Mon, Jun 16, 2008 at 11:04 AM, Jacky Rymasz-Maillot <[EMAIL PROTECTED]> wrote: > I am using actually Axis 1.4. > Is it still possible? If so, where can I find an example? > Thank you for all your answer ;) > > Jack > > -Message d'origine- > De : Paul Fremantle [mailto:[EMAIL PROTECTED] > Envoyé : lundi 16 juin 2008 16:36 > À : axis-user@ws.apache.org > Objet : Re: Send direct XML rather than using Java classes > > Jacky > > Sure. If you use Axis2 it was designed this way. The Java classes > model is actually just a separate layer on top of the core XML > messaging layer. > > You just need to look at the ServiceClient API. The XML is represented > in Axis2 as an OMElement. > > Paul > > 2008/6/16 Jacky Rymasz-Maillot <[EMAIL PROTECTED]>: >> Hello, >> >> >> >> I would like to know if it is possible to send a WSDL request directly >> without using Java classes to create the request. >> >> Let's say I want to create a WSDL request (XML format) into a text editor >> and send the resulting String to my server without using the generated Java >> classes from Axis. >> >> >> >> What I want looks like that but for SOAP: >> >> http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm >> >> >> >> Is it possible? >> >> >> >> Thx >> >> >> >> Jack >> >> >> >> >> >> No virus found in this outgoing message. >> Checked by AVG. >> Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 >> 17:52 >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 > 17:52 > > > No virus found in this outgoing message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 > 17:52 > > > - > 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]
SSL Error
Hi,
I am seeing intermittent SSL Exception "Unrecognized SSL message,
plaintext connection?" in my application
has anybody seen this any pointers on how to resolve this.
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: javax.net.ssl.SSLException: Unrecognized SSL message,
plaintext connection?
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLException:
Unrecognized SSL message, plaintext connection?
at
com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord
.java:501)
at
com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:343)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java
:720)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
cketImpl.java:1025)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
java:1038)
at
org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactor
y.java:186)
at
org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at
org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:
404)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.wellsfargo.eai_schemas.provider.aps.fundsTransfer.FundsTransferSoapB
indingStub.transferFunds200609(FundsTransferSoapBindingStub.java:8647)
at
wellsfargo.ops.transferscheduling.aps.transferfunds.TransferFundsService
Invoker.invokeTransferFundsService(TransferFundsServiceInvoker.java:49)
at
wellsfargo.ops.transferscheduling.performtransfer.PerformFundTransfer.tr
ansferFunds(PerformFundTransfer.java:74)
at
wellsfargo.ops.transferscheduling.service.PerformTransferServiceImpl.pro
cessTransfer(PerformTransferServiceImpl.java:69)
at sun.reflect.GeneratedMethodAccessor1628.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
wellsfargo.bm.common.sql.demarcation.TransactionContainer.invoke(Transac
tionContainer.java:88)
at $Proxy44.processTransfer(Unknown Source)
at
wellsfargo.ops.transferscheduling.ejb.TransferMessageBean.onMessage(Tran
sferMessageBean.java:91)
at
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
at
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDList
ener.java:332)
at
weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288
)
at
com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:292
1)
at
com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
at java.lang.Thread.run(Thread.java:595)
{http://xml.apache.org/axis/}hostname:mn1-bellagio-isb-op.wellsfargo.com
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
connection?
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
Thanks
Shashank
Re: firewall issue
Add support for WS-MakeConnection [1] - its designed for this. [1] http://docs.oasis-open.org/ws-rx/wsmc/200702 thanks -Doug __ STSM | Web Services Architect | IBM Software Group (919) 254-6905 | IBM T/L 444-6905 | [EMAIL PROTECTED] "samanth marisetty" <[EMAIL PROTECTED]> 06/16/2008 10:56 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject firewall issue Hi, I have an issue with the firewall on my workstation. I cannot access a web service from my local machine, however I have to deploy the ear on the test server to test any changes. I was thinking of opening a tunnel to bypass the firewall. Could somebody please tell me, what is the information I need for opening a tunnel. I also wanted to know if there is any other(better) way of bypassing the firewall to test the application on my local machine. Thanks, Samanth Marisetty.
Re: How call axis from tomcat
Yes, i think this is the best solution, and wirte a little client (RPCServiceClent) is not very complicated. Moreover, you can write a configurator to manage ip and port of your axis2 standalone. You can also add SSL with certificate if you want to give access only to your tomcat's webapp... 2008/6/16 Paul Fremantle <[EMAIL PROTECTED]>: > Lars > > What I mean is that you write a standard Axis2 client that is > expecting to communicate via SOAP/HTTP, using the URL > http://localhost:8595/.. then call it from within Tomcat. > > That's all! > > Paul > > On Mon, Jun 16, 2008 at 2:55 PM, Lars Ericsson <[EMAIL PROTECTED]> > wrote: > > Paul! > > > > > > > > I forget to say, that i have axis-plug-in in tomcat too!!? > > > > and i want to call axis-server from tomcat-axis-plug-in. > > > > > > > > :) > > > > > > > > R. > > > > Lars > > > > - Original Message > > From: Paul Fremantle <[EMAIL PROTECTED]> > > To: axis-user@ws.apache.org > > Sent: Monday, June 16, 2008 3:50:36 PM > > Subject: Re: How call axis from tomcat > > > > If you have 2 JVMs you can *NOT* use the local option - you should use > > the standard network model. It will still be very fast because you are > > calling on localhost. > > > > Paul > > > > On Mon, Jun 16, 2008 at 2:31 PM, Lars Ericsson <[EMAIL PROTECTED]> > > wrote: > >> Thanks Paul! > >> > >> I'm more intersting on the secound option, could you explaine moer. > >> and i have two jwm > >> R > >> Lars > >> - Original Message > >> From: Paul Fremantle <[EMAIL PROTECTED]> > >> To: axis-user@ws.apache.org > >> Sent: Monday, June 16, 2008 3:26:06 PM > >> Subject: Re: How call axis from tomcat > >> > >> Lars > >> > >> You have two options. > >> > >> 1) You can just create a standard client for Axis2 and call that from > >> your Tomcat servlet. The servlet will open a socket to 8595 and call > >> Axis2. > >> > >> 2) Are the two systems running in the same process/JVM? If so there is > >> a local transport you can use to call directly without going through > >> the network. > >> > >> Paul > >> > >> On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> > >> wrote: > >>> Hi! > >>> > >>> My axis2, stand-alone, running on port 8595 and my tomcat is runinng on > >>> port > >>> 8080. > >>> > >>> For some resones i want to call myserver on axis-on port 8595 from > tomcat > >>> 8080. > >>> > >>> How is it possible? is there any documentation about this or? > >>> > >>> Thanks > >>> Lars > >>> > >> > >> > >> > >> -- > >> Paul Fremantle > >> Co-Founder and CTO, WSO2 > >> Apache Synapse PMC Chair > >> OASIS WS-RX TC Co-chair > >> > >> blog: http://pzf.fremantle.org > >> [EMAIL PROTECTED] > >> > >> "Oxygenating the Web Service Platform", www.wso2.com > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > > > > -- > > Paul Fremantle > > Co-Founder and CTO, WSO2 > > Apache Synapse PMC Chair > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: How call axis from tomcat
Lars What I mean is that you write a standard Axis2 client that is expecting to communicate via SOAP/HTTP, using the URL http://localhost:8595/.. then call it from within Tomcat. That's all! Paul On Mon, Jun 16, 2008 at 2:55 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Paul! > > > > I forget to say, that i have axis-plug-in in tomcat too!!? > > and i want to call axis-server from tomcat-axis-plug-in. > > > > :) > > > > R. > > Lars > > - Original Message > From: Paul Fremantle <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Monday, June 16, 2008 3:50:36 PM > Subject: Re: How call axis from tomcat > > If you have 2 JVMs you can *NOT* use the local option - you should use > the standard network model. It will still be very fast because you are > calling on localhost. > > Paul > > On Mon, Jun 16, 2008 at 2:31 PM, Lars Ericsson <[EMAIL PROTECTED]> > wrote: >> Thanks Paul! >> >> I'm more intersting on the secound option, could you explaine moer. >> and i have two jwm >> R >> Lars >> - Original Message >> From: Paul Fremantle <[EMAIL PROTECTED]> >> To: axis-user@ws.apache.org >> Sent: Monday, June 16, 2008 3:26:06 PM >> Subject: Re: How call axis from tomcat >> >> Lars >> >> You have two options. >> >> 1) You can just create a standard client for Axis2 and call that from >> your Tomcat servlet. The servlet will open a socket to 8595 and call >> Axis2. >> >> 2) Are the two systems running in the same process/JVM? If so there is >> a local transport you can use to call directly without going through >> the network. >> >> Paul >> >> On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> >> wrote: >>> Hi! >>> >>> My axis2, stand-alone, running on port 8595 and my tomcat is runinng on >>> port >>> 8080. >>> >>> For some resones i want to call myserver on axis-on port 8595 from tomcat >>> 8080. >>> >>> How is it possible? is there any documentation about this or? >>> >>> Thanks >>> Lars >>> >> >> >> >> -- >> Paul Fremantle >> Co-Founder and CTO, WSO2 >> Apache Synapse PMC Chair >> OASIS WS-RX TC Co-chair >> >> blog: http://pzf.fremantle.org >> [EMAIL PROTECTED] >> >> "Oxygenating the Web Service Platform", www.wso2.com >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Send direct XML rather than using Java classes
I am using actually Axis 1.4. Is it still possible? If so, where can I find an example? Thank you for all your answer ;) Jack -Message d'origine- De : Paul Fremantle [mailto:[EMAIL PROTECTED] Envoyé : lundi 16 juin 2008 16:36 À : axis-user@ws.apache.org Objet : Re: Send direct XML rather than using Java classes Jacky Sure. If you use Axis2 it was designed this way. The Java classes model is actually just a separate layer on top of the core XML messaging layer. You just need to look at the ServiceClient API. The XML is represented in Axis2 as an OMElement. Paul 2008/6/16 Jacky Rymasz-Maillot <[EMAIL PROTECTED]>: > Hello, > > > > I would like to know if it is possible to send a WSDL request directly > without using Java classes to create the request. > > Let's say I want to create a WSDL request (XML format) into a text editor > and send the resulting String to my server without using the generated Java > classes from Axis. > > > > What I want looks like that but for SOAP: > > http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm > > > > Is it possible? > > > > Thx > > > > Jack > > > > > > No virus found in this outgoing message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 > 17:52 > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 17:52 No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 17:52 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
firewall issue
Hi, I have an issue with the firewall on my workstation. I cannot access a web service from my local machine, however I have to deploy the ear on the test server to test any changes. I was thinking of opening a tunnel to bypass the firewall. Could somebody please tell me, what is the information I need for opening a tunnel. I also wanted to know if there is any other(better) way of bypassing the firewall to test the application on my local machine. Thanks, Samanth Marisetty.
Re: Send direct XML rather than using Java classes
Jack, It is possible. Instead of the "string" add your "xml" and it will work. Nevertheless the xml should be escaped eg.. *<*item*>*description of the item*<*/item*>* becomes: *<*item>description of the item*<*/item*>* Jose Ferreiro On 6/16/08, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > Jacky > > Sure. If you use Axis2 it was designed this way. The Java classes > model is actually just a separate layer on top of the core XML > messaging layer. > > You just need to look at the ServiceClient API. The XML is represented > in Axis2 as an OMElement. > > Paul > > 2008/6/16 Jacky Rymasz-Maillot <[EMAIL PROTECTED]>: > > Hello, > > > > > > > > I would like to know if it is possible to send a WSDL request directly > > without using Java classes to create the request. > > > > Let's say I want to create a WSDL request (XML format) into a text editor > > and send the resulting String to my server without using the generated > Java > > classes from Axis. > > > > > > > > What I want looks like that but for SOAP: > > > > http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm > > > > > > > > Is it possible? > > > > > > > > Thx > > > > > > > > Jack > > > > > > > > > > > > No virus found in this outgoing message. > > Checked by AVG. > > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: > 15/06/2008 > > 17:52 > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- José Ferreiro EPFL Communication Systems engineer ing.sys.com.dipl.EPFL "Think little goals and expect little achievements. Think big goals and win big success." David Joseph Schwartz
Re: Send direct XML rather than using Java classes
Jacky Sure. If you use Axis2 it was designed this way. The Java classes model is actually just a separate layer on top of the core XML messaging layer. You just need to look at the ServiceClient API. The XML is represented in Axis2 as an OMElement. Paul 2008/6/16 Jacky Rymasz-Maillot <[EMAIL PROTECTED]>: > Hello, > > > > I would like to know if it is possible to send a WSDL request directly > without using Java classes to create the request. > > Let's say I want to create a WSDL request (XML format) into a text editor > and send the resulting String to my server without using the generated Java > classes from Axis. > > > > What I want looks like that but for SOAP: > > http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm > > > > Is it possible? > > > > Thx > > > > Jack > > > > > > No virus found in this outgoing message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 > 17:52 > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Send direct XML rather than using Java classes
Hello, I don't know if that is possible, but I have a few suggestions: - If your final purpose is testing a service, I would use soapui since it lets you write the request as xml. - I would consider using xmlbeans binding in order to read/parse the xml from a file or string. This would create a RequestDocument that can be used by the generated classes. I do not know if the other bindings supported by axis2 can achieve this, I haven't used them that much. Hope it helps, On Monday 16 June 2008 09:51:45 am Jacky Rymasz-Maillot wrote: > Hello, > > > > I would like to know if it is possible to send a WSDL request directly > without using Java classes to create the request. > > Let’s say I want to create a WSDL request (XML format) into a text editor > and send the resulting String to my server without using the generated Java > classes from Axis. > > > > What I want looks like that but for SOAP: > > HYPERLINK > "http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm"http://users.sky >net.be/pascalbotte/rcx-ws-doc/xmlpost.htm > > > > Is it possible? > > > > Thx > > > > Jack > > > > > > > No virus found in this outgoing message. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 > 17:52 -- Ing. David Ojeda Integra Consultores +58 416 6262898 Caracas, Venezuela - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Send direct XML rather than using Java classes
Hello, I would like to know if it is possible to send a WSDL request directly without using Java classes to create the request. Let’s say I want to create a WSDL request (XML format) into a text editor and send the resulting String to my server without using the generated Java classes from Axis. What I want looks like that but for SOAP: HYPERLINK "http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm"http://users.skynet.be/pascalbotte/rcx-ws-doc/xmlpost.htm Is it possible? Thx Jack No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.3.0/1504 - Release Date: 15/06/2008 17:52
Re: How call axis from tomcat
Paul! I forget to say, that i have axis-plug-in in tomcat too!!? and i want to call axis-server from tomcat-axis-plug-in. :) R. Lars - Original Message From: Paul Fremantle <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Monday, June 16, 2008 3:50:36 PM Subject: Re: How call axis from tomcat If you have 2 JVMs you can *NOT* use the local option - you should use the standard network model. It will still be very fast because you are calling on localhost. Paul On Mon, Jun 16, 2008 at 2:31 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Thanks Paul! > > I'm more intersting on the secound option, could you explaine moer. > and i have two jwm > R > Lars > - Original Message > From: Paul Fremantle <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Monday, June 16, 2008 3:26:06 PM > Subject: Re: How call axis from tomcat > > Lars > > You have two options. > > 1) You can just create a standard client for Axis2 and call that from > your Tomcat servlet. The servlet will open a socket to 8595 and call > Axis2. > > 2) Are the two systems running in the same process/JVM? If so there is > a local transport you can use to call directly without going through > the network. > > Paul > > On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> > wrote: >> Hi! >> >> My axis2, stand-alone, running on port 8595 and my tomcat is runinng on >> port >> 8080. >> >> For some resones i want to call myserver on axis-on port 8595 from tomcat >> 8080. >> >> How is it possible? is there any documentation about this or? >> >> Thanks >> Lars >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How call axis from tomcat
Ok paul! But i didn't get your point "to use standard network model"! What do you mean with it? Thanks Lars - Original Message From: Paul Fremantle <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Monday, June 16, 2008 3:50:36 PM Subject: Re: How call axis from tomcat If you have 2 JVMs you can *NOT* use the local option - you should use the standard network model. It will still be very fast because you are calling on localhost. Paul On Mon, Jun 16, 2008 at 2:31 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Thanks Paul! > > I'm more intersting on the secound option, could you explaine moer. > and i have two jwm > R > Lars > - Original Message > From: Paul Fremantle <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Monday, June 16, 2008 3:26:06 PM > Subject: Re: How call axis from tomcat > > Lars > > You have two options. > > 1) You can just create a standard client for Axis2 and call that from > your Tomcat servlet. The servlet will open a socket to 8595 and call > Axis2. > > 2) Are the two systems running in the same process/JVM? If so there is > a local transport you can use to call directly without going through > the network. > > Paul > > On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> > wrote: >> Hi! >> >> My axis2, stand-alone, running on port 8595 and my tomcat is runinng on >> port >> 8080. >> >> For some resones i want to call myserver on axis-on port 8595 from tomcat >> 8080. >> >> How is it possible? is there any documentation about this or? >> >> Thanks >> Lars >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How call axis from tomcat
If you have 2 JVMs you can *NOT* use the local option - you should use the standard network model. It will still be very fast because you are calling on localhost. Paul On Mon, Jun 16, 2008 at 2:31 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Thanks Paul! > > I'm more intersting on the secound option, could you explaine moer. > and i have two jwm > R > Lars > - Original Message > From: Paul Fremantle <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Monday, June 16, 2008 3:26:06 PM > Subject: Re: How call axis from tomcat > > Lars > > You have two options. > > 1) You can just create a standard client for Axis2 and call that from > your Tomcat servlet. The servlet will open a socket to 8595 and call > Axis2. > > 2) Are the two systems running in the same process/JVM? If so there is > a local transport you can use to call directly without going through > the network. > > Paul > > On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> > wrote: >> Hi! >> >> My axis2, stand-alone, running on port 8595 and my tomcat is runinng on >> port >> 8080. >> >> For some resones i want to call myserver on axis-on port 8595 from tomcat >> 8080. >> >> How is it possible? is there any documentation about this or? >> >> Thanks >> Lars >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How call axis from tomcat
Thanks Paul! I'm more intersting on the secound option, could you explaine moer. and i have two jwm R Lars - Original Message From: Paul Fremantle <[EMAIL PROTECTED]> To: axis-user@ws.apache.org Sent: Monday, June 16, 2008 3:26:06 PM Subject: Re: How call axis from tomcat Lars You have two options. 1) You can just create a standard client for Axis2 and call that from your Tomcat servlet. The servlet will open a socket to 8595 and call Axis2. 2) Are the two systems running in the same process/JVM? If so there is a local transport you can use to call directly without going through the network. Paul On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Hi! > > My axis2, stand-alone, running on port 8595 and my tomcat is runinng on port > 8080. > > For some resones i want to call myserver on axis-on port 8595 from tomcat > 8080. > > How is it possible? is there any documentation about this or? > > Thanks > Lars > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How call axis from tomcat
Lars You have two options. 1) You can just create a standard client for Axis2 and call that from your Tomcat servlet. The servlet will open a socket to 8595 and call Axis2. 2) Are the two systems running in the same process/JVM? If so there is a local transport you can use to call directly without going through the network. Paul On Mon, Jun 16, 2008 at 2:20 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: > Hi! > > My axis2, stand-alone, running on port 8595 and my tomcat is runinng on port > 8080. > > For some resones i want to call myserver on axis-on port 8595 from tomcat > 8080. > > How is it possible? is there any documentation about this or? > > Thanks > Lars > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How call axis from tomcat
Hi! My axis2, stand-alone, running on port 8595 and my tomcat is runinng on port 8080. For some resones i want to call myserver on axis-on port 8595 from tomcat 8080. How is it possible? is there any documentation about this or? Thanks Lars
Re: Trouble with a .NET client.
Zaq, I assume that your .net client will not only authenticate in the java web service. It looks like you are not able to perform the first operation i.e " logon". Therefore if you would like that your .net client also performs other operations, I will suggest you to follow the contract-first approach (also known as WSDL first) because you will have other troubles with the other function IMHO... Hope this helps. Jose FERREIRO On 6/16/08, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > There no option for asking the tools to generate attributes rather > than elements. For the most part, it's considered a bad practice. Bear > in mind that attributes must be simple types. > > Anne > > On Mon, Jun 16, 2008 at 8:08 AM, Zaq Rizer <[EMAIL PROTECTED]> wrote: > > On Mon, Jun 16, 2008 at 6:54 AM, keith chapman <[EMAIL PROTECTED]> > > wrote: > >>> > >>> I'd suggest to switch to the contract-first approach: you'll have to > >>> learn WSDL, of course, but you have much more control over > interoperability > >>> and you'll get to use Axis2 (the latest version, at least) with > success. > >> > >> Thanks, > >> Keith > >> > >> Alternatively you can use a tool such a java2wsdl to generate the WSDL > for > >> you and then tune it accor ding to your needs (remove minoccurs and > >> nillable). > >> > >> Thanks, > >> Keith. > > > > Thanks for the input everyone. I will go with Keith's recommendation of > > modifying the produced WSDL. Does anyone know of a way to automatically > > change the format of the WSDL instead of modifying it by hand? (e.g. > > somehow modifying an underlying axis2 config file or perhaps even source > > file?). > > > > I'll see how this solution works for us. > > > > Regards, > > Zaq > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Trouble with a .NET client.
On Mon, Jun 16, 2008 at 8:13 AM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > There no option for asking the tools to generate attributes rather > than elements. For the most part, it's considered a bad practice. Bear > in mind that attributes must be simple types. > > Anne > > > Okay, thanks Anne. Zaq
Re: Re : Re : Axis2 / Maven 2
Hi Julien, many thanks for your replay about this... > Did you read this document: > http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing > > In substance Maven 2.0.x is not very clear about running both unit and > integration testing. Choose the way you prefere but if you can keep only > one module I suggest you do because multi-modules still don't play well > with reporting plugins. I'm trying to get two ways working. Via Maven2 (differnt modules and inline..) but currently I'm struggling with particular problems in relationship with axis2 and services...cause i have to deploy axis2.war first (which is working via cargo and maven) but the next step to deploy the aar file this is currently not working And you are right about the clearness of Maven and it's integration-test phase...there are no good examples for this...i've read the example in the book...but... I will seeI'm working on this Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with a .NET client.
There no option for asking the tools to generate attributes rather than elements. For the most part, it's considered a bad practice. Bear in mind that attributes must be simple types. Anne On Mon, Jun 16, 2008 at 8:08 AM, Zaq Rizer <[EMAIL PROTECTED]> wrote: > On Mon, Jun 16, 2008 at 6:54 AM, keith chapman <[EMAIL PROTECTED]> > wrote: >>> >>> I'd suggest to switch to the contract-first approach: you'll have to >>> learn WSDL, of course, but you have much more control over interoperability >>> and you'll get to use Axis2 (the latest version, at least) with success. >> >> Thanks, >> Keith >> >> Alternatively you can use a tool such a java2wsdl to generate the WSDL for >> you and then tune it accor ding to your needs (remove minoccurs and >> nillable). >> >> Thanks, >> Keith. > > Thanks for the input everyone. I will go with Keith's recommendation of > modifying the produced WSDL. Does anyone know of a way to automatically > change the format of the WSDL instead of modifying it by hand? (e.g. > somehow modifying an underlying axis2 config file or perhaps even source > file?). > > I'll see how this solution works for us. > > Regards, > Zaq > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty arg0 in Request
Hi, many thanks for the information and the hints how to get around this... > Yes I now understand your problem. Actually that is one of the issue in > RPCServiceClient , when it come to bean serialization. Even I wrote an > article about this , but I can not find the link. > > Well , let's try to fix the issue for the next release. Till that , > since you have the WSDL try to generate the client code for that and > invoke the service. Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with a .NET client.
On Mon, Jun 16, 2008 at 6:54 AM, keith chapman <[EMAIL PROTECTED]> wrote: > I'd suggest to switch to the contract-first approach: you'll have to learn >> WSDL, of course, but you have much more control over interoperability and >> you'll get to use Axis2 (the latest version, at least) with success. > > > Thanks, > Keith > > Alternatively you can use a tool such a java2wsdl to generate the WSDL for > you and then tune it accor ding to your needs (remove minoccurs and > nillable). > > Thanks, > Keith. > Thanks for the input everyone. I will go with Keith's recommendation of modifying the produced WSDL. Does anyone know of a way to automatically change the format of the WSDL instead of modifying it by hand? (e.g. somehow modifying an underlying axis2 config file or perhaps even source file?). I'll see how this solution works for us. Regards, Zaq
Re: client port
The server is fine, as the client can connect with the server if the client is outside its firewall. The client can not connect if it is behind client's firewall. >Can you ping to your Server machine? >if you use a DNS address try using the direct ip address of the server >machine. > >thanks, >Amila. -- View this message in context: http://www.nabble.com/client-port-tp17829239p17862802.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trouble with a .NET client.
> > I'd suggest to switch to the contract-first approach: you'll have to learn > WSDL, of course, but you have much more control over interoperability and > you'll get to use Axis2 (the latest version, at least) with success. Thanks, Keith Alternatively you can use a tool such a java2wsdl to generate the WSDL for you and then tune it accor ding to your needs (remove minoccurs and nillable). Thanks, Keith. > > > -- > Mauro Molinari > Software Developer > [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: WSDL2Java for JMS Endpoint.
Hi Goutham, have you got any solution for this... I too facing the same problem. I think we can achieve this usng axis 2. but need to dig further more. Gautham.Kasinath wrote: > > Hello all, > > I have been looking around in the list for some hint to explain/resolve my > problem, in vain. So here I am posting my issue. > I have been using Axis 1.4 final, to WSDL2Java a SOAP based Web Service > that requires the JMS Transport. The Service itself runs within the TIBCO > EMS environment and the WSDL is generated by the TIBCO EMS engine. > Whilst WSDL2Java is successful in most part of the WSDL parsing, it fails > over with the following stack trace: > > java.io.IOException: Emitter failure. Cannot find endpoint address in > port Domain in service MatchContactServiceagentLocator > at > org.apache.axis.wsdl.toJava.JavaServiceImplWriter.writeFileBody(JavaServiceImplWriter.java:189) > at > org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127) > at > org.apache.axis.wsdl.toJava.JavaServiceWriter.generate(JavaServiceWriter.java:112) > at > org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421) > at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:476) > at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45) > at > org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362) > at java.lang.Thread.run(Thread.java:570) > > > I suspect this happens when parsing the following port bindings in the > WSDL: > > > > > > type="java.lang.String">tibjmsnaming://d2esbprm.dev.hbf.com.au:7222 > type="java.lang.String">com.tibco.tibjms.naming.TibjmsInitialContextFactory > > QueueConnectionFactory > destination="queue">hbf.dev2.web.contact.match.src > > > location="http://d2esbprm.dev.hbf.com.au:8991/Services/MatchContact/Web"/> > > > > However, could one of you explain what I could be missing that makes the > WSDL2Java fail over? Further, is there a way to WSDL2Java a Service WSDL > for JMS transport using JMS? > > Please advise. > > Thanks > > Cheers > Gautham Kasinath > > Gautham KASINATH > > HBF/Ajilon > William Street > Perth > Phone: +61 8 9214 6754 > > Go Red for Women and fight heart disease - the number one killer of > Australian women. > Wear red on Friday 13 June and purchase fundraising merchandise from any > HBF Service Centre. > === > HBF Health Funds Inc ARBN 126 884 786 incorporated in Western Australia > is a Private Health Insurer under the Private Health Insurance Act 2007. > The liability of its constitutional members is limited; HBF Insurance > Pty Ltd ABN 11 009 268 277; HBF Financial Services Pty Ltd > ABN 18 009 123 675. The information contained in this email and any > attachment is intended solely for the named recipients. It may contain > material or information that is confidential and/or legally privileged > material. It is also subject to copyright. If you are not the intended > recipient please advise us immediately by return email or contact a > Member Service Advisor on 133 423 and delete the email and any > attachments. Any use or disclosure of the contents of either is > unauthorised and may be unlawful. Any personal information in this email > must be handled in accordance with the Privacy Act 1988 (Cth). The views > expressed in this email are those of the author and do not represent > those of HBF unless clearly indicated. > === > > -- View this message in context: http://www.nabble.com/WSDL2Java-for-JMS-Endpoint.-tp17747599p17862090.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with WSDL references on Axis2 1.3
How you generate the .aar file. did you use the wsdl2java tool? Can you send your wsdl? thanks Amila. On Fri, Jun 13, 2008 at 8:22 AM, Sukma Agung Verdianto <[EMAIL PROTECTED]> wrote: > Hi, > Can anybody help me out of this? > I can see from the internet there is some problem with nested import of > schema? > > I can;t attach the sample AAR file, I think this mailing list does not > allow binary attachment? > > Regards, > Sukma > > On Wed, Jun 11, 2008 at 12:08 PM, Sukma Agung Verdianto <[EMAIL PROTECTED]> > wrote: > >> Hi All, >> I have a question regarding WSDL published by a service packaged in AAR. >> I have a service class, WSDL and all it references (imported WSDL's and >> schema's) structured like this inside an aar: >> >> java >> -- package >> ServiceClass.class >> META-INF >> -- services.xml >> -- ExampleService.wsdl >> -- _ >> schema1.xsd (this import schema2, > namespace="namespace" schemaLocation="schema2.xsd"/>) >> schema2.xsd (let say this schema import schema3 using > namespace="namespace" schemaLocation="_/schema3.xsd"/>) >> _ >> -- schema3.xsd (this import schema 4) >> -- _ >> schema4.xsd >> >> I can get ExampleService deployed successfully, and it is exposing the >> right WSDL (using originalWsdl set to true). >> However, when I try to access the WSDL and get all references, it failed >> because it cannot find some references... >> >> I've digging more, and found out that Axis2 using replacing some relative >> URL to be something like this format - [ServiceName]?xsd=path/to/xsd >> This is fine for the XSD that directly imported by WSDL, but not for the >> XSD imported by ther XSD. >> Axis2 does not change import definition to > namespace="namespace" schemaLocation="ServiceName?xsd=_/_/schema3.xsd"/> to >> import schema3. >> >> Is this the right behavior of Axis2? Does't it support nested import? >> Please give me some insight. >> >> Regards, >> Sukma >> > > -- Amila Suriarachchi, WSO2 Inc.
Re: client port
On Sat, Jun 14, 2008 at 1:21 AM, danclemson <[EMAIL PROTECTED]> wrote: > > Hi, > > The client can connect to the service if it's outside its firewall. The > problem is when it is behind its firewall. > So, I do not think there is issue with firewall/port of the service side. Can you ping to your Server machine? if you use a DNS address try using the direct ip address of the server machine. thanks, Amila. > > > > Vinh Nguyen (vinguye2) wrote: > > > > Hi, > > Normally, a server would have port 80 or 8080 as the default for HTTP > > connections. So first, you need to check if your server/firewall allows > > incoming HTTP at all. If it doesn't, then your web service can't be > > accessed. > > > > But if it does, then you need to check what port number is assigned for > > HTTP. Your client would then send requests to the server using that > > port. > > > > Note that some firewalls have separate configurations for outgoing and > > incoming, so you have to check both, too. > > -Vinh > > > > > > -Original Message- > > From: danclemson [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 13, 2008 11:08 AM > > To: axis-user@ws.apache.org > > Subject: client port > > > > > > Hi, > > > > I am new to web services and axis2. > > i host a web service, and my client is behind a firewall(no proxy). > > > > The client can connect with my service if it's outside it firewall, but > > could not communicate with service if behind its firewall. what might be > > the problem? > > > > When the client send request to server, which port is used or is there > > any default port? If the firewall lets the request out, will it blocks > > the response send in by the service server as the port is not opened at > > firewall? > > > > thanks for help. > > -- > > View this message in context: > > http://www.nabble.com/client-port-tp17829239p17829239.html > > Sent from the Axis - User mailing list archive at Nabble.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] > > > > > > > > -- > View this message in context: > http://www.nabble.com/client-port-tp17829239p17830818.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc.
Re: Trouble with a .NET client.
From a .NET point of view I learnt by experience that: - if you specify an input element as optional (minOccurs="0"), .NET will generate client stubs with two parameters for each WSDL input parameter, the second one being a boolean that specifies if that parameter has been actually specified or not - if you specify an element as nillable (nillable="true"), .NET will generate client stubs with just an input parameter for each WSDL input parameter and that parameter "might" accept null values. I used "might", because some types in .NET 1.1 cannot be null (this has changed in .NET 2.0). So, if you want to specify a null for some kind of parameters (integers, for instance, or datetime...) you have to specify it as optional rather than nillable, otherwise .NET 1.1 clients won't be able to properly invoke your webservices. Another problem is that Axis2 code-first tools always generate WSDLs with nillable="true" for every parameter (even if they are specified in Java using primitive type, so they shouldn't be optional or nullable at all!!) and there's no way at the moment to tune this in the generation process. I'd suggest to switch to the contract-first approach: you'll have to learn WSDL, of course, but you have much more control over interoperability and you'll get to use Axis2 (the latest version, at least) with success. -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: .NET Integration
Ben Paulsen ha scritto: The company I work for is in the process of doing an axis web service integration a with a client using the .NET framework 1.1 and Visual Studio 2003. Recently the client reported the following exception when making a request: If you are writing your webservices with top-down approach (i.e.: starting from the WSDL), which I highly recommend, define your numeric field as optional (minOccurs="0"), rather than nillable (nillable="true") in the WSDL. In this way, your Java code can still return null values, while .NET will generate client stubs with code that will be able to process your responses by checking against a boolean value that states whether the numeric value has been actually specified (i.e.: it's not-null) or not (i.e.: it's null). -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
