Re: [Axis2] Thread
The threading model is controlled by the platform that axis2 is deployed on. In most cases, it is the Servlet container. Either thread per connection or thread per request may be implemented. HTH, Dong On Wed, Mar 12, 2008 at 6:22 PM, Arlindo Luis Marcon Junior <[EMAIL PROTECTED]> wrote: > Hi All... > > Doubt: > Is possible to have a "new Thread" inside one service deployed in Axis2? > Example: I have a Web Service which attend many clientes,,, with > scope="request"... > In other words,,, many instances of the same service,,, one instance for > each cliente... > And I need "one" ( only one ) Thread ( or something like this ) to > perform some tasks for me ( like monitoring my environment )... > > Question: > Is possible do it? > If Yes, where/how I could start, and stop, this Thread? > Or has other "elegant" manner to do it? > > Any cue is welcome... > Thanks all... > > -- > Arlindo Luis Marcon Junior > E-mail: [EMAIL PROTECTED] > Internet Web Page: http://lattes.cnpq.br/6483462042489662 > ICQ: 138864173 > Curitiba - Paraná - Brasil > > > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Dong Liu http://blogs.usask.ca/dong_notes/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] What does "Unable to generate EPR for the transport tcp" mean?
Hi, folks,I found the servlet container informs that "Unable to generate EPR for the transport tcp" when I clicked on the links of the services deployed on Axis2 .95. What does that mean? Cheers, Dong
Re: [Axis2] How to specifiy operation name
You may need to use the tcp monitor or other tools to see the HTTP message. Cheers,DongOn 3/14/06, Michael Robinson <
[EMAIL PROTECTED]> wrote:
Thanks!!
One question though:
options.setSoapAction("actionName");
options.setAction("actionName");
both fixed the problem. Is there a
difference?
Thanks again for both replies.
Michael
Re: [Axis2] A question about asynchronous services and message queue
I agree that Axis2 should be simple and lightweight, and just for soap processing. WS-RM does cover some of my requirements. However, I have a question in my mind about asynchronous "service" and "client" for a long time. As I know, the current implementation of async dual client in axis2 is to listen to a specific port, 6060 by default. That makes problem when running several async dual clients on the same machine at the same time. What I expect is to remove the difference between client and server so that all services can be accessed through the same port for a certain transportation, the http or tcp or JMS transportation components are always there listening, and the correlated service will be triggered based on ws-addressing. Cheers,DonOn 3/14/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: On Tue, 2006-03-14 at 10:59 -0600, Dong Liu wrote:> Maybe I should clarify my point here:>> 1. A service can support asynchronous communication with a> message queue stands before it, no matter whether or not this > service is able to support asynchronous messaging by nature.> 2. It is hard for an asynchronous service to handle long-run> service requests without the support of a message queue and > more important a persistence layer.> I am not sure if they are correct. Any comments?It seems to me that you're looking for WS-Reliable Messaging likefeatures. Have you looked at Sandesha2? That will give behavior you're looking for.I think the core Axis2 platform should continue to have a simple,lightweight async model based purely on threads to cover simplepatterns. If you really need reliable, long running async behavior then its time to use WS-RM.Sanjiva.
Re: [Axis2] A question about asynchronous services and message queue
Maybe I should clarify my point here: A service can support asynchronous communication with a message queue stands before it, no matter whether or not this service is able to support asynchronous messaging by nature. It is hard for an asynchronous service to handle long-run service requests without the support of a message queue and more important a persistence layer. I am not sure if they are correct. Any comments? Cheers,DonOn 3/12/06, Dong Liu <[EMAIL PROTECTED]> wrote: Hi, folks,When trying to deploy some async services to compare their performance to the sync ones, I realize that the async services make no sense with the support of a message queue. What is your idea? Cheers, Don
[Axis2] A question about asynchronous services and message queue
Hi, folks,When trying to deploy some async services to compare their performance to the sync ones, I realize that the async services make no sense with the support of a message queue. What is your idea? Cheers, Don
Re: Async Service with callback for BPEL process (any hints?)
Where did you put it? I would like to look at it as well. Cheers,DonOn 3/10/06, Deepal Jayasinghe < [EMAIL PROTECTED]> wrote:I just created a test case to demonstrate how Axis2 server side async work if you can have a look at that.org.apache.axis2.async.AsyncServiceTest
Re: WebServices very slow after some requests
Try Eclipse TPTP to profile your Tomcat and services for free. On 2/22/06, Erik Daughtrey <[EMAIL PROTECTED] > wrote:Hello,For this sort of problem, I've found analysis of jvm thread dumps very effective.If you're using unix, then "kill -QUIT pid" is usually sufficient to get acurrent thread dump. In this case, pid would be the process id of therunning Tomcat process.If you're using Windows, then the easiest way to get a thread dump is by running the target process in the foreground and using CTRL+BREAK. Theoutput will usually go to stderr or stdout so, using output redirection onthe process at startup is recommended.Where the output goes depends on the jdk in use. It may wind up in the stderr/stdout, or files like javadump may appear in the current directoryof the process being dumped.Analyzing a threaddump can be tricky, but I suspect that in this case it mayjump from the output. Personally, I'd look for some number of threads having the same or very similar top of stack. This will indicate the first level ofdebug. I suspect that the threads are waiting on some external resource --at least that's been my experience in cases like these. Good luck. On Wednesday 22 February 2006 12:54, Franz Coriand wrote:> Hi all,>> we have the problem, that our webservices become very slow after some> requests.> For the first request we need about 10s. > For the 100th request we need about 2mins - its the same request like> the first one, with the same result.>> We use Tomcat 5.5.12 and Axis 1.3.>> We have no clue what's the problem. > Do you have any ideas?>> Thanks, Franz--Regards,Erik
Re: could someone help me in java client to invoke webservices?
Please try after adding this line into your clientcall.setSOAPActionURI("Operation");Cheers,DonOn 2/1/06, mm jj <
[EMAIL PROTECTED]> wrote: thanks for reply. could you please look into the following code, error and WSDL.
here is the code, error, and wsdl(this wsdl is created in TIBCO). I used AXIS 1.3 to write and compile java code. import org.apache.axis.client.*;import javax.xml.rpc.ParameterMode
;import org.apache.axis.encoding.XMLType;import org.apache.axis.utils.Options; public class FibClient { public static void main(String[] args) throws Exception { String endpoint = "
http://DUSU41009X1:80/Processes/SOAPServer"; //String endpoint = "
http://DUSU41009X1:8080/Processes_sp_Definition"; String Sub = "SUBJECT"; String Data = ""> Service service = n
ew
Service(); Call call = (Call) service.createCall(); call.setTargetEndpointAddress(endpoint); call.setOperationName("Operation"); call.setProperty(Call.OPERATION_STYLE_PROPERTY, "wrapped");
call.addParameter("op1", XMLType.XSD_STRING, ParameterMode.IN); call.addParameter("op2", XMLType.XSD_STRING, ParameterMode.IN); call.setReturnType(XMLType.XSD_STRING); call.setReturnType
(XMLType.XSD_STRING); String ret = (String) call.invoke(new Object[]{Sub, Data}); System.out.println("Got result : " + ret); }}--
init:deps-jar:compile-single:run-single:- Unable to find required classes (javax.activation.DataHandler an
d
javax.mail.internet.MimeMultipart). Attachment support is disabled.AxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: No handler for body element faultActor: faultNode: faultDetail: {}detail:
http://DUSU41009X1:80/Processes/SOAPServer""Operation No handler for body element at org.apache.axis.message.SOAPFaultBuilder.createFault
(SOAPFaultBuilder.java:222) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129) at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712) at org.apache.crimson.parser.Parser2.content
(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement
(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java
:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke
(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) 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 FibClient.main(FibClient.java:24)Exception in thread "main" Java Result: 1BUILD SUCCESSFUL (total time: 1 second) --
www.examples.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="
http://xmlns.example.com/1138294660453/OperationImpl" xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/" name="Untitled" targetNamespace="
http://xmlns.example.com/1138294660453/OperationImpl">
www.examples.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="
www.examples.com">
Generic web service request
insert the reply XML here
Generic web service request
insert the request XML
here
http://schemas.xmlsoap.org/soap/http"/>
Re: could someone help me in java client to invoke webservices?
Please post the details of your questions here, otherwise no one could give you an answer. A good start point is always the code samples coming with the release. CheersDon On 2/1/06, mm jj <[EMAIL PROTECTED]> wrote: could someone help me in java client to invoke webservices? Do you Yahoo!? With a free 1 GB, there's more in store with Yahoo! Mail.
Re: Problem changing operation name
Hi, Alan,I guess a way to make your client work is to add the following line in your clientoptions.setSoapAction("estandar");before the line then your client sends out the message.
Cheers,DonOn 1/17/06, Alan Aguia <[EMAIL PROTECTED]> wrote:
Hi Im using Axis 0.94. I dindnt have problems deploying EchoNonBlockingClient everything worked fine. After that I modify some parameters, so I change the name of the method in the class MyService from echo to estandar. I also change the operation name in
services.xml from echo to estandar. After that I redeploy de aar it doesn´t work I dont get it. java.lang.Exception: org.apache.axis2.AxisFault: Operation Not found EPR is
http://localhost:8080/axis2/services/MyService and WSA Action =""> Help please Alan.
Yahoo! Photos
Got holiday prints?
See all the ways to get quality prints in your hands ASAP.
Re: [Axis2-0.94] Weird wsdl2java behaviour
I agree. However, in my cases, I have both axis 1 and axis2 installed. AXIS_HOME is already defined for axis 1, and I had to change the tool .bat files when I wanted to use them. Cheers,Don On 1/13/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi Dong,all My guess is users would find a bat/sh script very useful if they want to get into business directly. take the tomcat example. There's nothing to do other than dbl clicking the bat file (or the sh equivalent) to start the tomcat server (which I, as a user, find very useful and convenient) We need to provide similar experience to Axis2 users as well.On 1/13/06, Dong Liu < [EMAIL PROTECTED]> wrote: The same idea is appliable to testing all the samples instead supply the .bat and .sh scripts. DonOn 1/13/06, Dong Liu < [EMAIL PROTECTED]> wrote:I still think it is better to supply a document to suggest the user to create proper classpath definitions in their systems. And run the utils by calling the class directly. What do you think? Cheers,Don On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote: hmm, we should switch to "%*" instead of listing "%1 %2..."Ruben can u please try editing the bat file and do that?thanks,-- dimsOn 1/13/06, Ajith Ranabahu < [EMAIL PROTECTED]> wrote:> Hi,> This is not really a bug in the codegen but in the script. If you have a> look at the shell script you'll see that it takes only the first 9 arguments > and not the rest! Same issue is with the bat file.>>> On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote:> > Rubén,> >> > Please log a jira issue and upload your wsdl. > >> > thanks,> > dims> >> > On 1/13/06, Rubén Naranjo Izquierdo < [EMAIL PROTECTED]> wrote:> > > Hi all, > > >> > > I've been using Axis2-0.94 wsdl2java this last two days and I've> realized that "-p" and "-pn" options have no efect when compiling my wsdl. I> mean, they have no effect. > > >> > > But the real weird thing comes when I change the order of the> parameters in wsdl2java call. With the following call:> > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -ss -sd -t -d > xmlbeans -o $HOME/project/ -p org.objectweb.service -sn MyService -pn> MySecondPortType> > >> > > I get the code generated (in default package) and this output:> > > > > > Warning - Multiple endpoints found - picking the first endpoint!> > >> > >> > > But with the following call (note that is the same call, but with the> parameters's order canged): > > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -o $HOME/project/ -p> org.objectweb.service -t -ss -sd -d xmlbeans -sn MyService -pn> MySecondPortType> > > > > > I get the following exception with no code generated:> > >> > > Exception in thread "main"> org.apache.axis2.wsdl.codegen.CodeGenerationException:> java.lang.RuntimeException :> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118) > > > at org.apache.axis2.wsdl.WSDL2Code.main> (WSDL2Code.java:31)> > > at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > > Caused by: java.lang.RuntimeException:> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:152)> > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)> > > ... 2 more> > > Caused by: java.lang.IllegalArgumentException: Local> part not allowed to be null > > > at javax.xml.namespace.QName.(QName.java:85)> > > at javax.xml.namespace.QName.( QName.java:70)> > > at> org.apache.ws.commons.schema.XmlSchemaType.getQName (XmlSchemaType.java:91)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1496)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleSequence (SchemaBuilder.java:979)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContentExtension(SchemaBuilder.java:895)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContent > (SchemaBuilder.java:684)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:592)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement (SchemaBuilder.java> :1501)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:107)> > > at> org.apache.ws.commons.schema.XmlSchemaCollection.read (XmlSchemaCollection.java:233)> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:86)> > > ... 3 more> > >> > > >> > --> > Davanum Srinivas : http://wso2.com/blogs/> >>> >> --> Ajith Ranabahu--Davanum Srinivas : http://wso2.com/blogs/ -- Ajith Ranabahu
Re: [Axis2-0.94] Weird wsdl2java behaviour
The same idea is appliable to testing all the samples instead supply the .bat and .sh scripts. DonOn 1/13/06, Dong Liu < [EMAIL PROTECTED]> wrote:I still think it is better to supply a document to suggest the user to create proper classpath definitions in their systems. And run the utils by calling the class directly. What do you think? Cheers,Don On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote: hmm, we should switch to "%*" instead of listing "%1 %2..."Ruben can u please try editing the bat file and do that?thanks,-- dimsOn 1/13/06, Ajith Ranabahu < [EMAIL PROTECTED]> wrote:> Hi,> This is not really a bug in the codegen but in the script. If you have a> look at the shell script you'll see that it takes only the first 9 arguments > and not the rest! Same issue is with the bat file.>>> On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote:> > Rubén,> >> > Please log a jira issue and upload your wsdl. > >> > thanks,> > dims> >> > On 1/13/06, Rubén Naranjo Izquierdo < [EMAIL PROTECTED]> wrote:> > > Hi all, > > >> > > I've been using Axis2-0.94 wsdl2java this last two days and I've> realized that "-p" and "-pn" options have no efect when compiling my wsdl. I> mean, they have no effect. > > >> > > But the real weird thing comes when I change the order of the> parameters in wsdl2java call. With the following call:> > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -ss -sd -t -d > xmlbeans -o $HOME/project/ -p org.objectweb.service -sn MyService -pn> MySecondPortType> > >> > > I get the code generated (in default package) and this output:> > > > > > Warning - Multiple endpoints found - picking the first endpoint!> > >> > >> > > But with the following call (note that is the same call, but with the> parameters's order canged): > > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -o $HOME/project/ -p> org.objectweb.service -t -ss -sd -d xmlbeans -sn MyService -pn> MySecondPortType> > > > > > I get the following exception with no code generated:> > >> > > Exception in thread "main"> org.apache.axis2.wsdl.codegen.CodeGenerationException:> java.lang.RuntimeException :> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118) > > > at org.apache.axis2.wsdl.WSDL2Code.main> (WSDL2Code.java:31)> > > at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > > Caused by: java.lang.RuntimeException:> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:152)> > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)> > > ... 2 more> > > Caused by: java.lang.IllegalArgumentException: Local> part not allowed to be null > > > at javax.xml.namespace.QName.(QName.java:85)> > > at javax.xml.namespace.QName.( QName.java:70)> > > at> org.apache.ws.commons.schema.XmlSchemaType.getQName (XmlSchemaType.java:91)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1496)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleSequence (SchemaBuilder.java:979)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContentExtension(SchemaBuilder.java:895)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContent > (SchemaBuilder.java:684)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:592)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement (SchemaBuilder.java> :1501)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:107)> > > at> org.apache.ws.commons.schema.XmlSchemaCollection.read (XmlSchemaCollection.java:233)> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:86)> > > ... 3 more> > >> > > >> > --> > Davanum Srinivas : http://wso2.com/blogs/> >>> >> --> Ajith Ranabahu--Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2-0.94] Weird wsdl2java behaviour
I still think it is better to supply a document to suggest the user to create proper classpath definitions in their systems. And run the utils by calling the class directly. What do you think? Cheers,Don On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: hmm, we should switch to "%*" instead of listing "%1 %2..."Ruben can u please try editing the bat file and do that?thanks,-- dimsOn 1/13/06, Ajith Ranabahu < [EMAIL PROTECTED]> wrote:> Hi,> This is not really a bug in the codegen but in the script. If you have a> look at the shell script you'll see that it takes only the first 9 arguments > and not the rest! Same issue is with the bat file.>>> On 1/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:> > Rubén,> >> > Please log a jira issue and upload your wsdl. > >> > thanks,> > dims> >> > On 1/13/06, Rubén Naranjo Izquierdo < [EMAIL PROTECTED]> wrote:> > > Hi all, > > >> > > I've been using Axis2-0.94 wsdl2java this last two days and I've> realized that "-p" and "-pn" options have no efect when compiling my wsdl. I> mean, they have no effect. > > >> > > But the real weird thing comes when I change the order of the> parameters in wsdl2java call. With the following call:> > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -ss -sd -t -d > xmlbeans -o $HOME/project/ -p org.objectweb.service -sn MyService -pn> MySecondPortType> > >> > > I get the code generated (in default package) and this output:> > > > > > Warning - Multiple endpoints found - picking the first endpoint!> > >> > >> > > But with the following call (note that is the same call, but with the> parameters's order canged): > > >> > > ./WSDL2Java.sh -uri $HOME/project/wsdl/mywsdl.wsdl -o $HOME/project/ -p> org.objectweb.service -t -ss -sd -d xmlbeans -sn MyService -pn> MySecondPortType> > > > > > I get the following exception with no code generated:> > >> > > Exception in thread "main"> org.apache.axis2.wsdl.codegen.CodeGenerationException:> java.lang.RuntimeException :> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:118)> > > at org.apache.axis2.wsdl.WSDL2Code.main> (WSDL2Code.java:31)> > > at> org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)> > > Caused by: java.lang.RuntimeException:> java.lang.IllegalArgumentException: Local part not allowed> to be null> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:152)> > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:80)> > > ... 2 more> > > Caused by: java.lang.IllegalArgumentException: Local> part not allowed to be null > > > at javax.xml.namespace.QName.(QName.java:85)> > > at javax.xml.namespace.QName.( QName.java:70)> > > at> org.apache.ws.commons.schema.XmlSchemaType.getQName (XmlSchemaType.java:91)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement(SchemaBuilder.java:1496)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleSequence (SchemaBuilder.java:979)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContentExtension(SchemaBuilder.java:895)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexContent > (SchemaBuilder.java:684)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleComplexType(SchemaBuilder.java:592)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleElement (SchemaBuilder.java> :1501)> > > at> org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:107)> > > at> org.apache.ws.commons.schema.XmlSchemaCollection.read (XmlSchemaCollection.java:233)> > > at> org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:86)> > > ... 3 more> > >> > > >> > --> > Davanum Srinivas : http://wso2.com/blogs/> > --> Ajith Ranabahu--Davanum Srinivas : http://wso2.com/blogs/
Re: axis2 0.94 api doc
Please check the released Documents Distribution http://gulus.usherbrooke.ca/pub/appl/apache/ws/axis2/0_94/axis2-0.94-docs.zip don On 1/11/06, steven reinisch <[EMAIL PROTECTED]> wrote: > hi, > > is there an api documentation for axis2 0.94? it is not contained in > the actual release. > in how far can the doc of the 0.93 version be used? > > thanks, > steven >
Re: [Axis2] how does the SOAPAction be identified on the service provider?
Thank you, Chinthaka,
I figure out options.setSoapAction(operationName) is exactly what I want.
Don
On 1/5/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Dong,
>
> When you give the operationName to the invoke method, that parameter
> is only for the client side of Axis2 engine, and this will not be
> passed in to the SOAP message you send out. This basically will be
> used to engage modules in the client side Axis2 engine. (In our new
> ServiceClient implemenation, which is still in the SVN, this method
> name has become optional)
>
> We have couple of methods to pass the operationName, that you invoke,
> to the server side. So that name will be used for dispatching your
> message to the correct service and operation.
>
> 1. You can append that to the URL. I think thats what you did and
>its not a hack.
> 2. You can say options.setAction(operationName)
> 3. You can say options.setSoapAction(operationName)
> 4. or you can use the RPC based dispatching by putting the QName of
>the operation as the first child of the body.
>
> HTH,
>
> - -- Chinthaka
>
> Dong Liu wrote:
>
> > Hi, folks,
> >
> > I found something strange about the mechanism how axis2 service
> > identifies the operation corresponding to a request message.
> >
> > When I used the following code to invoke a service: ... OMElement
> > result = call.invokeBlocking("operationName", payload); ...
> >
> > If the SOAP body is *not* something like
> > http://www.example.org/ns";> ...
> > I would get the fault message
> > like
> >
> > Operation Not found EPR is http://the targetEPR and
> > WSA Action =
> >
> > However, if I hardcode the SOAPAction part and send it to the
> > targetEPR, the service works fine.
> >
> > I checked the HTTP content of the requests in all the cases, and
> > found that the SOAPAction part in the HTTP head is always *empty*.
> >
> > I am not sure if this behavior is by design. And I would like to
> > know how to specify the SOAPAction part when I use Call client.
> >
> > Thanks,
> >
> > Don
> >
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.2 (MingW32)
>
> iD8DBQFDvegwjON2uBzUhh8RAjDSAJ90CB5v5Q7TxYxzHoNf0vVG7U90pgCeOZWO
> q415kSphpfyyNb/NxlG3dFs=
> =P7kL
> -END PGP SIGNATURE-
>
>
[Axis2] how does the SOAPAction be identified on the service provider?
Hi, folks,
I found something strange about the mechanism how axis2 service
identifies the operation corresponding to a request message.
When I used the following code to invoke a service:
...
OMElement result = call.invokeBlocking("operationName", payload);
...
If the SOAP body is *not* something like
http://www.example.org/ns";>
...
I would get the fault message like
Operation Not found EPR is http://the targetEPR and WSA
Action =
However, if I hardcode the SOAPAction part and send it to the
targetEPR, the service works fine.
I checked the HTTP content of the requests in all the cases, and found
that the SOAPAction part in the HTTP head is always *empty*.
I am not sure if this behavior is by design. And I would like to know
how to specify the SOAPAction part when I use Call client.
Thanks,
Don
Re: [Axis2] how to generate java code without xmlbean things using wsdl2java in axis2 .93
OK, it is the switch "-d none". I could not find it in the pdf version of code generator document. Maybe the documents of axis2 need to be updated. On 1/3/06, Dong Liu <[EMAIL PROTECTED]> wrote: > hi, folks, > > I want to figure out how to generate java code using the wsdl2java > tool without those xmlbean stuff just like the axis2 .92 eclipse > plug-in does. > > Thanks, > > Don >
[Axis2] how to generate java code without xmlbean things using wsdl2java in axis2 .93
hi, folks, I want to figure out how to generate java code using the wsdl2java tool without those xmlbean stuff just like the axis2 .92 eclipse plug-in does. Thanks, Don
Re: problem in getting WSDL
Please refer to http://marc.theaimsgroup.com/?l=axis-dev&m=113323679508571 I think it will help. On 12/15/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > Hi, > According to what I know (Correct me if I'm wrong), Axis2 still does not > support WSDL generation. > Inorder to get the wsdl in http://.../myservice?wsdl you have to provide > your own wsdl inside the aar file... > If you have the WSDL file corresponding to the Web service, rename it to > service.wsdl and put that into the META-INF directory. (It is not necessary > to have a wsdl file in Axis2.) > > The following article might help you... > http://www.developer.com/open/print.php/10930_3557741_2 > > HTH, > ~Thilina > > > > On 12/15/05, thilina madu <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > 1. I don't know how to take the WSDL from the myself written service. > > > > 2. I deployed my .. .aar file in the services folder.That service is > working nicley > > with java client.But now I want access that from .NET client to do that I > want to take > > wsdl. > > when I (brows by using thius http:// localhost:8080/axis2 > )go serrvice link that show all > > the method my services.but once I go to the link corresponding to the > service then > > it giev XML document telling WSDL is not available. > > Why like that. > > > > If you know any method to take WSDL onceafter deploying the service in > axis2 .please send me . > > Any kind of response is higly appreciated > > > > 3.How can I make a java or .Net proxy to achve interopoerability. > > > > madushan thilina > > > > > > > > > > > > > > > > > > > > > Yahoo! Shopping > > Find Great Deals on Holiday Gifts at Yahoo! Shopping > > > > > > > > > > > > -- > "May the SourcE be with u" > http://webservices.apache.org/~thilina/ > http://thilinag.blogspot.com/ > http://www.bloglines.com/blog/Thilina
Re: issues with have 2 axis's on tomcat?
I found it's fine to find 2 versions of axis on the same tomcat, say axis 1.x and axis2 0.9x. The only thing to take care is the different classpath for axis 1 and 2. And some .bat or .sh tool code delivered in axis2 may not work properly because of the setup of 'axishome'. On 12/15/05, Frank <[EMAIL PROTECTED]> wrote: > Was wondering is there any know issues (other then setting up classpaths > correctly and all and pointing to the correct url/endpoint), with having > 2 different versions (or the same for that matter, just under another > directory) of axis on a tomcat install? axis is just an application > from a tomcat perspective isn't it? It does not care that there might > be similar apps. But does axis have any issues I should be made aware of? > > > Thanks, > > Frank > > >
[axis2]Looking for code examples for manipulating OM objects using XPath
Hi, folks, I am learning to manipulate XML in SOAP message by using the OM objects and XPath. Please drop a line if you know where to find such examples. Cheers, Don
Re: java.net.ConnectException: Connection refused: connect
I guess that is because the endpoint http://nagoya.apache.org:5049/axis/services/echo does not work now. Just try other examples if you want to test your configuration. Cheers, Don On 7/18/05, Tongjie Li <[EMAIL PROTECTED]> wrote: > I have the same problem! > > On 7/18/05, jim wang <[EMAIL PROTECTED]> wrote: > > Hi: > > > > I am the new user to axis, after installing axis on my PC(XP) machine > > successfully, i try to run some services to apache server in > > %AXIS_HOME% > > like: > > > > samples.userguide.example1.TestClient > > Sent 'Hello!', got 'Hello!' > > > > and got following error: > > > > java.net.ConnectException: Connection refused: connect > > > > any experter, please. > > > > Thanks. > > > > -Jim > > > > > > > > Start your day with Yahoo! - make it your home page > > > > >
Re: Problems with enabling the SOAPMonitor and TCPMonitor!
As I know, TCPMonitor does not need to be enabled. The SOAPMonitor needs to be compiled locally, and the corresponding service needs to be deployed to enable the function. I run them on Java SE 5 without problems. What is your Java version? Cheers, Don On 7/18/05, Tongjie Li <[EMAIL PROTECTED]> wrote: > Hi all! >Currently I work with the Axis.I want to enable the SOAPMonitor > and TCPMonitor.But When I run it, it appears following error: > java.lang.NullPointerException >at javax.swing.border.EmptyBorder.(Unknown Source) >at com.sun.java.swing.plaf.windows.WindowsTableHeaderUI$XPDefaultRe= > ndere > r.getTableCellRendererComponent(Unknown Source) >at javax.swing.plaf.basic.BasicTableHeaderUI.getHeaderRenderer(Unkn= > own S > ource) >at javax.swing.plaf.basic.BasicTableHeaderUI.getHeaderHeight(Unknow= > n Sou > rce) >at javax.swing.plaf.basic.BasicTableHeaderUI.createHeaderSize(Unkno= > wn So > urce) >at javax.swing.plaf.basic.BasicTableHeaderUI.getPreferredSize(Unkno= > wn So > urce) >at javax.swing.JComponent.getPreferredSize(Unknown Source) >at javax.swing.ViewportLayout.preferredLayoutSize(Unknown Source) >at java.awt.Container.preferredSize(Unknown Source) >at java.awt.Container.getPreferredSize(Unknown Source) >at javax.swing.JComponent.getPreferredSize(Unknown Source) >at javax.swing.ScrollPaneLayout.layoutContainer(Unknown Source) >at java.awt.Container.layout(Unknown Source) >at java.awt.Container.doLayout(Unknown Source) >at java.awt.Container.validateTree(Unknown Source) >at java.awt.Container.validateTree(Unknown Source) >at java.awt.Container.validateTree(Unknown Source) >... > > Could someone help me!=20 > Thanks a lot! >
Re: Unsubscribe me please
Try emailto: axis-user-unsubscribe- patricia.zuno = gmail.com @ws.apache.org Cheers, Don On 7/14/05, patricia zuno <[EMAIL PROTECTED]> wrote: > >
Re: [axis 2]Questions on the development process using Axis 2.0
Thank you all for the replies.
I think WSDL is still the easy way to connect service-side development
to consumer-side development. Reading the machine-generated long WSDL
file always remind me a question whether we can have another way to
let both the service-side and consumer-side developers understand each
other easily. service.xml, in this sense, is a good option, or a point
to start.
Cheers,
Don
On 7/12/05, Chathura Herath <[EMAIL PROTECTED]> wrote:
>
> Don,
> If you are asking how to get the client codegened using the service.xml and
> service impl classes; the answer is there is no way to do it directly. One
> of the options is to hand write the client side SOAPEnvelop creation part
> and use the call api to send the message.
> The other option I would say is to use the java2wsdl tool to get the wsdl
> from the service implementation and then use the wsdl2java tool to generate
> the clientside.
>
> One thing to note is that if you use the wsdl2java tool databinding is
> engaged automatically.
>
> Cheers
> Chathura
>
>
> > -Original Message-
> > From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, July 13, 2005 9:48 AM
> > To: axis-user@ws.apache.org; Dong Liu
> > Subject: Re: [axis 2]Questions on the development process using Axis 2.0
> >
> > hi Don;
> >
> > you can write a client to consume a web service where web service only
> > contains service.xml (no wsdl file is present) , in that case you have to
> > create the SOAPMessge by hand , use one of the MEPClient to send the
> > request
> > . And all these has to handle in the your client code since you do not
> > have
> > stubs. In fact in M2 we have don that.and I think following code will help
> > you to do so , and which invoke the version service.
> >
> >
> > private String value;
> > private QName operationName = new QName("getVersion");
> > private OMElement createEnvelope() {
> > OMFactory fac = OMAbstractFactory.getOMFactory();
> > OMNamespace omNs = fac.createOMNamespace("http://localhost/my";,
> > "my");
> > OMElement method = fac.createOMElement("Version", omNs);
> > OMElement value = fac.createOMElement("myValue", omNs);
> > method.addChild(value);
> > return method;
> > }
> >
> > public boolean inVokeTheService() {
> > try {
> > OMElement payload = createEnvelope();
> > Call call = new Call();
> > call.setTo(targetEPR);
> > call.setTransportInfo(Constants.TRANSPORT_HTTP,
> > Constants.TRANSPORT_HTTP, false);
> >
> > OMElement result =
> > (OMElement)
> > call.invokeBlocking(operationName.getLocalPart(), payload);
> > StringWriter writer = new StringWriter();
> > result.serializeWithCache(new
> > OMOutput(XMLOutputFactory.newInstance().createXMLStreamWriter(writer)));
> > writer.flush();
> > value = writer.toString();
> > return true;
> > } catch (AxisFault axisFault) {
> > value = axisFault.getMessage();
> > return false;
> > } catch (XMLStreamException e) {
> > value = e.getMessage();
> > return false;
> > }
> > }
> >
> >
> > Deepal
> >
> >
> > - Original Message -
> > From: "Dong Liu" <[EMAIL PROTECTED]>
> > To: ; <[EMAIL PROTECTED]>
> > Sent: Tuesday, July 12, 2005 10:26 PM
> > Subject: Re: [axis 2]Questions on the development process using Axis 2.0
> >
> >
> > Hi, Chathura,
> >
> > Thank you for your reply to my questions. Now I understand the
> > purposes of the different parts in the user guide of axis 2.
> >
> > I like the approach that using the java classes and the service.xml to
> > deploy web services. But I am still thinking how to develop clients to
> > consume such services, if no wsdls are present. Is it possible to
> > develop a client just based on the service.xml?
> >
> > Cheers,
> >
> > Don
> >
> > On 7/12/05, Chathura Herath <[EMAIL PROTECTED]> wrote:
> > > Hi Don,
> > >
> > > If the documentation is blurred we need to fix it, but see my comments
> > > below
> > > for each of your queries.
> > >
> > > > -Original Message-
> > > > From: Dong Liu [mailto:[EMAIL PROTECTED]
> >
Re: [axis 2]Questions on the development process using Axis 2.0
Hi, Chathura, Thank you for your reply to my questions. Now I understand the purposes of the different parts in the user guide of axis 2. I like the approach that using the java classes and the service.xml to deploy web services. But I am still thinking how to develop clients to consume such services, if no wsdls are present. Is it possible to develop a client just based on the service.xml? Cheers, Don On 7/12/05, Chathura Herath <[EMAIL PROTECTED]> wrote: > Hi Don, > > If the documentation is blurred we need to fix it, but see my comments below > for each of your queries. > > > -Original Message- > > From: Dong Liu [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 11, 2005 10:17 PM > > To: axis-user@ws.apache.org; axis-dev@ws.apache.org > > Subject: [axis 2]Questions on the development process using Axis 2.0 > > > > Hi, > > > > I am confused about the development process when using Axis 2.0. As > > described in the user guide, the process will be > > > > 1. write the class interfaces using Java; > > 2. write the service.xml; > > 3. create the .aar achieve and deploy it; > > 4. generate the skeleton code based on the *WSDL* file; > > 5. implement the logic of services; > > 6. create *another achieve* again and deploy it; > > 7. write the client code in either a dynamic or a static fashion. > > > > My questions are > > > > 1. what is purpose of the first deployment using the achieve have only > > class interfaces and service.xml? > > This is an sample with no data binding(Note it echo's the OMElement. This > was the sample we had for M2 where we didn't have databinding support) So if > the user want to be smart and do everyting manually that's the way to do it. > This example will tell you what are the must have's if you are to make it > work. > > > > 2. where does the WSDL come from? It is hard for the developer to code > > it by hand. > > You of course can write it by hand, the sample is based on the fact that you > start with the contract, which is the wsdl. But.. we have a tool that does > the java2wsdl part. Actually we use the Axis1 java2wsdl tool and I belive we > have a eclipse pluigin for that too. Am I right Ajith??? > > > > 3. what is the relationship between the first aar and the second one? > > No relationship.. The second one is a databound (a more comprehensive and > practical I would say) example that emphasize the axis2 data binding > support. > > > In a nut shell we are not trying to invent a new development process. (But > we have our own deployment model, programming model too I would say..) > > > Thanks > Chathura > > >
Re: How to configure and deploy JAX-RPC handler in Axis?
Axis has its own Handler interface. No idea about the difference between axis handler and javax handler. Anyway, you can first try to deploy the handler like axis handler, and then see if it work, and what is the error. Cheers, Don On 7/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi all > I have wrote a handler class implement the javax.xml.rpc.handler.Handler > interface.But I don't know how to > configure and deploy it at the server side in Axis.I know the Axis is > compliant with JAX-RPC specification and should be surport it. > > Thanks in advance:) > > > Best Regards, > > Robert Zhang > Email:[EMAIL PROTECTED] > Tel:86-010-62014411-2437 > >
[axis 2]Questions on the development process using Axis 2.0
Hi, I am confused about the development process when using Axis 2.0. As described in the user guide, the process will be 1. write the class interfaces using Java; 2. write the service.xml; 3. create the .aar achieve and deploy it; 4. generate the skeleton code based on the *WSDL* file; 5. implement the logic of services; 6. create *another achieve* again and deploy it; 7. write the client code in either a dynamic or a static fashion. My questions are 1. what is purpose of the first deployment using the achieve have only class interfaces and service.xml? 2. where does the WSDL come from? It is hard for the developer to code it by hand. 3. what is the relationship between the first aar and the second one? Hope my questions are clear enough. Cheers, Don
Re: Cannot find the log file generated by a log handler?
I found the file MyService.log in the windows system32 folder. So how to set up the path for such log files. Cheers, Don On 7/10/05, Dong Liu <[EMAIL PROTECTED]> wrote: > Hi, all > > I am testing the example 4 in the user guide about the use of a log > handler. As described in the WSDD file > > > > > > > The handler is supposed to write some logs to the file named > "MyService.log", to my understanding. However, I cannot locate the log > file, and have no idea about what happens with the handler when > running the Client and get a response from the service. > > I guess I missed some configuration of axis. > > I am running axis 1.2.1 on Tomcat 5.5 and Java SE 5. > > Cheers, > > Don >
Cannot find the log file generated by a log handler?
Hi, all I am testing the example 4 in the user guide about the use of a log handler. As described in the WSDD file The handler is supposed to write some logs to the file named "MyService.log", to my understanding. However, I cannot locate the log file, and have no idea about what happens with the handler when running the Client and get a response from the service. I guess I missed some configuration of axis. I am running axis 1.2.1 on Tomcat 5.5 and Java SE 5. Cheers, Don
How to get the WSDL file when using Axis 2.0
Hi, I am reading the documents of Axis 2.0, and try the examples in the user guide. It is straightforward to write a service.xml file based on the java file. But where does the wsdl file come from? I guess it should not be written by our keyboards. So it is generated by something like Java2WSDL? It is not mentioned in the user guide. Cheers, Don
