Re: [Axis2-0.94] wsdl2java generates in-out receiver for in-only operations

[Ajith Ranabahu]

This bug has been identified and already fixed!

On 2/8/06, Rubén Naranjo Izquierdo <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I downloaded the latest codebase, tried the last code generator and
> realised that in generated stubs (with "-g" option); in-only operations are
> declared as "org.apache.axis2.description.OutOnlyAxisOperation". Is this
> behaviour normal or we are dealing with a new bug?
>
>Thanks!
>
> Rubén Naranjo
>
> On Tuesday 07 February 2006 15:26, Ajith Ranabahu wrote:
> > Hi Andreas,
> > Yes this bug was realised recently and fixed in the latest codebase.
> > Now the codegenerator generates correct message receivers based on the
> > operation
> >
> > On 2/7/06, Andreas Bobek <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I have a very small WSDL file with only one in-only operation.
> > > When running wsdl2java it generates a services.xml file with
> > > mep="http://www.w3.org/2004/08/wsdl/in-out";
> > > and a MessageReceiver class inheriting from
> > > AbstractInOutSyncMessageReceiver.
> > > As expected, when invoking the service with ClientAPI it sends back a
> > > fault. At service side RawXMLINOnlyMessageReceiver is used instead of
> > > the generated MessageReceiver class.
> > >
> > > Is this bug already known? I couldn't find another post.
> > > Thanks, Andreas Bobek.
> >
> > --
> > Ajith Ranabahu
>


--
Ajith Ranabahu

whats the expected release date for axis 1.4 (java)

[mshankar]

Hi,
 
Whats the expected 
release date for Axis 1.4 (java). I tested our implementation with the latest 
nightly build(08-feb-2006) and a critical bug which was blocking us from moving 
to Axis 1.3 for java has been fixed in Axis 1.4. 
 
It would be very 
helpful if the release date is known so that we can decide on whether to move to 
1.4 or not.
 
thanks
Manohar
 

Help! - WebSphere 5.1.1 issue with attachments

[Pradeep Reddy]

Hi all,I am having trouble accessing the Response Message on WebSphere 5.1.1.I am trying to send an attachment from server to the client. I add it to the response message using this familiar code snippet.
MessageContext msgContext = MessageContext.getCurrentContext();Message msg = msgContext.getResponseMessage();
msg.getAttachmentsImpl().setSendType(Attachments.SEND_TYPE_MIME);                AttachmentPart part = new AttachmentPart(new DataHandler(new ArtifactDataSource(
ais.getInfo().getName(),ais.getInputStream(),ais.getContentType().toString(;//ArtifactDataSource is a custom implementation of datasourcepart.setContentId
(ais.getInfo().getName());msg.addAttachmentPart(part);msg.saveChanges();
this code returns an attachment on weblogic 8.1. On WebSphere 5.1.1, i am getting back a response with no xml message in it. I just get back these headers with no xml message or the attachment.
HTTP/1.1 200 OKDate: Wed, 08 Feb 2006 20:48:43 GMTServer: IBM_HTTP_SERVER/1.3.28.1  Apache/1.3.28 (Unix)Connection: closeContent-Type: multipart/related; type="text/xml"; start=""; boundary=
1446154572.1139431723394.JavaMail.test.blutoTo debug, I retained only these calls:
MessageContext msgContext = MessageContext.getCurrentContext();
Message msg = msgContext.getResponseMessage();This returned an empty soap message.HTTP/1.1 200 OKDate: Wed, 08 Feb 2006 22:00:48 GMTServer: IBM_HTTP_SERVER/1.3.28.1  Apache/1.3.28 (Unix)
Connection: closeContent-Type: text/xml; charset=utf-8http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So when i call getResponseMessage(), its going through a seperate path and giving me a brand new response. I am using axis 1.2 RC2.Any help on what i can do to work around this problem would be greatly appreciated. 
Thanks,Pradeep

Arbitrary Authenitcation Types (based on SOAP Headers)

[Scott McCoy]

Hello All,    I have a specification that demands I use a SOAP Header element for credential verification, and from a technical perspective it needs to be highly reusable, with a technical requirement that it preceeds and stops processing of the SOAP Body.  I've found what seems to be just the ticket, which is simply adding a component via the  element in WSDL or WSDD...But the problem I'm having is that I'm having difficulty finding documentation on doing this.
    Essentially, I have the following (mock) request envelope:            
                    
            Nevermind the details of the SOAP Body, handlers for this are easily generatable by WSDL2Java, but how do I deal with the SOAP Header in a respectible and logical fasion (Axis 
1.3) ?    Thanks,    Scott S. McCoy

Re: Digest Authentication in Axis 1.3?

[Davanum Srinivas]

Axis1.3 supports CommonsHTTPSender (check the wiki) which uses Commons
HTTPClient. AFAIK, that supports Digests
(http://jakarta.apache.org/commons/httpclient/authentication.html#Alternate%20authentication)

ergo, it should be possible to set up
Axis1.3/CommonsHTTPSender/HTTPClient to use Digest.

-- dims

On 2/8/06, Anthony Bargnesi <[EMAIL PROTECTED]> wrote:
> Will,
>
> I am also interested in using Digest authentication over Basic
> authentication.  I am using Axis 1.3 and have found no information on how to
> use Digest Authentication.  If you do find out some information please let
> me know.  I will do the same for you.
>
> Thanks,
>
> Anthony Bargnesi
>
> On 2/8/06, Will Blanchard <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> >
> > Correction: Digest Auth is NOT implemented in Axis 1.2.1, but there's a
> little helper class called SimpleHTTPSender which a colleague got from some
> Microsoft sample code.  If this class is in the classpath, Axis 1.2.1 will
> use Digest authentication.
> >
> >
> >
> > The presence of this class is not enough to get Axis 1.3 to use Digest
> Authentication, so I'm trying to figure out if there is some way to
> configure Axis 1.3 to use it.
> >
> >
> >
> > Thanks.
> >
> >
> >
> > -Will
> >
> >
> >
> > 
>
> >
> > From: Will Blanchard
> > Sent: Wednesday, February 08, 2006 2:05 PM
> > To: axis-user@ws.apache.org
> > Subject: Digest Authentication in Axis 1.3?
> >
> >
> >
> >
> > I am working on a java application that makes calls into a web service
> implemented with .Net.  The service requires Digest authentication on its
> requests.
> >
> >
> >
> > It was working fine with Axis 1.2.1, but when I upgraded to Axis 1.3, all
> my requests started using Basic authentication instead of Digest
> authentication.
> >
> >
> >
> > Is there some way to enable Digest authentication on requests made using
> Axis 1.3?  Does anyone disagree that Digest authentication was working for
> requests made using Axis 1.2.1?
> >
> >
> >
> > As far as I can tell, all I had to do to get Digest Authentication for my
> Axis 1.2.1 requests was set credentials by calling
> (org.apache.axis.client.Stub).setUsername() and
> (org.apache.axis.client.Stub).setPassword().
> >
> >
> >
> > Thanks.
> >
> > -Will
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

Re: Digest Authentication in Axis 1.3?

[Anthony Bargnesi]

Will,I am also interested in using Digest authentication over Basic authentication.  I am using Axis 1.3 and have found no information on how to use Digest Authentication.  If you do find out some information please let me know.  I will do the same for you.
Thanks,Anthony BargnesiOn 2/8/06, Will Blanchard <[EMAIL PROTECTED]> wrote:














 

Correction: Digest Auth is NOT implemented
in Axis 1.2.1, but there's a little helper class called SimpleHTTPSender
which a colleague got from some Microsoft sample code.  If this class is
in the classpath, Axis 1.2.1 will use Digest authentication.

 

The presence of this class is not enough
to get Axis 1.3 to use Digest Authentication, so I'm trying to figure out
if there is some way to configure Axis 1.3 to use it.

 

Thanks.

 

-Will

 









From: Will Blanchard 

Sent: Wednesday, February 08, 2006
2:05 PM
To: axis-user@ws.apache.org
Subject: Digest Authentication in
Axis 1.3?



 

I am working on a java application that makes calls into a
web service implemented with .Net.  The service requires Digest
authentication on its requests.

 

It was working fine with Axis 1.2.1, but when I upgraded to
Axis 1.3, all my requests started using Basic authentication instead of Digest
authentication.

 

Is there some way to enable Digest authentication on
requests made using Axis 1.3?  Does anyone disagree that Digest
authentication was working for requests made using Axis 1.2.1?

 

As far as I can tell, all I had to do to get Digest
Authentication for my Axis 1.2.1 requests was set credentials by calling
(org.apache.axis.client.Stub).setUsername() and
(org.apache.axis.client.Stub).setPassword().

 

Thanks.

-Will

RE: Digest Authentication in Axis 1.3?

[Will Blanchard]

 

Correction: Digest Auth is NOT implemented
in Axis 1.2.1, but there’s a little helper class called SimpleHTTPSender
which a colleague got from some Microsoft sample code.  If this class is
in the classpath, Axis 1.2.1 will use Digest authentication.

 

The presence of this class is not enough
to get Axis 1.3 to use Digest Authentication, so I’m trying to figure out
if there is some way to configure Axis 1.3 to use it.

 

Thanks.

 

-Will

 









From: Will Blanchard 
Sent: Wednesday, February 08, 2006
2:05 PM
To: axis-user@ws.apache.org
Subject: Digest Authentication in
Axis 1.3?



 

I am working on a java application that makes calls into a
web service implemented with .Net.  The service requires Digest
authentication on its requests.

 

It was working fine with Axis 1.2.1, but when I upgraded to
Axis 1.3, all my requests started using Basic authentication instead of Digest
authentication.

 

Is there some way to enable Digest authentication on
requests made using Axis 1.3?  Does anyone disagree that Digest
authentication was working for requests made using Axis 1.2.1?

 

As far as I can tell, all I had to do to get Digest
Authentication for my Axis 1.2.1 requests was set credentials by calling
(org.apache.axis.client.Stub).setUsername() and
(org.apache.axis.client.Stub).setPassword().

 

Thanks.

-Will

Digest Authentication in Axis 1.3?

[Will Blanchard]

I am working on a java application that makes calls into a web
service implemented with .Net.  The service requires Digest authentication
on its requests.

 

It was working fine with Axis 1.2.1, but when I upgraded to
Axis 1.3, all my requests started using Basic authentication instead of Digest
authentication.

 

Is there some way to enable Digest authentication on
requests made using Axis 1.3?  Does anyone disagree that Digest
authentication was working for requests made using Axis 1.2.1?

 

As far as I can tell, all I had to do to get Digest
Authentication for my Axis 1.2.1 requests was set credentials by calling (org.apache.axis.client.Stub).setUsername()
and (org.apache.axis.client.Stub).setPassword().

 

Thanks.

-Will

RE: NPE in SoapBindingStub for valid Soap elements

[Mike Whittaker]

Oh and here is the WSDL, I expect that helps!

Thanks,
Mike W


http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:impl="http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";
xmlns:intf="http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";
xmlns:tns1="http://dmu.ac.uk/csci3420/2006/02/BankTypes";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

 
  http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";
xmlns="http://www.w3.org/2001/XMLSchema";>
   http://dmu.ac.uk/csci3420/2006/02/BankTypes"/>
   

 
  
  
  
 

   
   

 
 
 
 

   
   

 
 
 

   
   

 
  
 

   
  
  http://dmu.ac.uk/csci3420/2006/02/BankTypes";
xmlns="http://www.w3.org/2001/XMLSchema";>
   http://dmu.ac.uk/csci3420/2006/02/BACSPayroll"/>
   

 
 
 
 

   
   

 
 
 
 

   
  
 

   

  

   

   

  

   

   

  

 

 

  

   

   

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

  

 

 



 

 



 

  

   

   

  

 http://localhost:9090/p02233990ws/services/BACSPayroll"/>

  

   

Attachments and Re: newbie questions on "style" attribute

[GEORGE MCKINNEY]

Anne ( or anyone else who can answer ), 

In another entry of the blog Anne references, I read:


Unfortunatly, because Microsoft refuses to support SwA, the Attachments Profile 
doesn't really enable interoperability. I can understand Microsoft position on 
SwA, though -- SwA is a remarkably insecure mechanism for passing attachments. 
In the future (probably 2006), most SOAP platforms will adopt MTOM as the 
standard mechanism to pass attachments, and Microsoft is implementing support 
for MTOM in Indigo. (I'll be posting more on attachment mechanisms in a future 
blog entry.)


I'm not sure what the implications of this are, but the design we have been 
beginning to think about has a single kind of message, with an xml attachment 
that follows a schema that would be implied by the contents of one of the bits 
of the SOAPBody. This would not be open to the world, but only to partners with 
whom we have a vpn connection. Because the attachments are of widely varying 
sizes, and the set of schemas (ae?) they follow are expected to change fairly 
frequently (and each partner would use only a subset of that ), our intent was 
to have a fairly stable base on which we "layer" the attachments. I had 
imagined that the WSDL would simply specify an xml attachment. Is that where 
the Microsoft tools break?

I have played with (oops, make that " done some exploratory prototyping with " 
) both Axis 1.3 and Weblogic 8.1 webservice tools, and using their Handler 
facilities, been able to add / remove attachments without having any reference 
to them in the WSDL. Can anyone tell me whether that be a viable tactic to use 
with partners that are Microsoft shops? 

BTW, Anne, I didn't see the " ... future blog entry." Does it exist yet? 
Please? I've found your postings here to be some of the clearest SOAP / 
webservices information around.

Thanks (and especially to Anne )
George McKinney

- Original Message -
From: Anne Thomas Manes <[EMAIL PROTECTED]>
Date: Wednesday, February 8, 2006 7:41 am
Subject: Re: newbie questions on "style" attribute

> The style attribute in WSDL is different from the style attribute 
> in WSDD.
> 
> The WSDL style has two possible options: RPC and Document. (If 
> neither is
> specified, it defaults to "document".) This attribute refers to 
> the SOAP
> message style -- whether the SOAP Body contains a document defined 
> by a
> schema or whether the Body is constructed dynamically based on the 
> methodname and a set of parameter types. WSDL has another 
> attribute, "use", which
> indicates whether the message structure is defined by a schema
> (use="literal") or generated using the SOAP encoding data model
> (use="encoded"). Valid combinations of these two attributes include
> document/literal, rpc/literal, and rpc/encoded.
> 
> The WSDD style has four options: RPC, WRAPPED, DOCUMENT, MESSAGE. 
> If no
> style is specified, it defaults to "RPC".) This style attribute 
> encompassesboth message style and programming style. There are 
> three types of
> programming style:
> - a parameterized invocation API (XML parameters are mapped to 
> individualJava classes):
> return method(arg1, arg2)
> - an object-based invocation API (XML parameters are collectively 
> mapped to
> a bean):
> return method (object)
> - a messaging API (XML messages are mapped to DOM):
> Document method(Document)
> 
> RPC produces rpc/encoded with a parameterized API (you can use the 
> "use"attribute to specify that you want rpc/literal)
> WRAPPED produces document/literal with a parameterized API
> DOCUMENT produces document/literal with an object-based API
> MESSAGE produces document/literal with a messaging API
> 
> For more information on the WRAPPED style, see my blog:
> http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-
> convention.html
> Anne
> 
> On 2/8/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > Anyone can help me to understand the "style" element better. 
> (well, or
> > pointing me to some good articles on it?)
> >
> > Here's what's puzzling me:
> >
> > In Axis1.x user guide, it says the "service" element can have a 
> "style"> attribute.  I also see under the "wsdl:binding" element, 
> both "soap:binding"
> > and "soap:operation" elements can have a "style" attribute as 
> well.   I've
> > got a few questions:
> >
> > - do they have the same meaning and one will overide the other?
> >
> > - when do I select "rpc" and "document" for my WSDL?  It seems 
> "document"> is suggested for Axis 1.x, is it still a better choice 
> for Axis2?
> >
> >
> > thanks,
> >
> > -Hui
> >
> 

NPE in SoapBindingStub for valid Soap elements

[Mike Whittaker]

I get the exception below as a Soap Fault and Http500 error
I'm invoking a service generated by wsdl2java
but the request never gets to calling my code the generated
BACSPayrollSoapBindingStub throws the exception,
but the soap payload contains valid elements as defined in wsdl.

Can any one give me a direction to resolving this?

TIA
Mike W

java.lang.NullPointerException

AxisFault faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode: faultString: java.lang.NullPointerException faultActor:
faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:persephonejava.lang.NullPointerExcepti
on at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
22) at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
9) at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
ntext.java:1087) at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at
javax.xml.parsers.SAXParser.parse(SAXParser.java:375) 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(MustUnderstandChe
cker.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
dmu.p02233990.wswp.service.payroll.BACSPayrollSoapBindingStub.paySalaries(BA
CSPayrollSoapBindingStub.java:199) at
dmu.p02233990.wswp.service.payroll.BACSPayrollServiceTest.testPaySalaries(BA
CSPayrollServiceTest.java:119)

Thrown in this code (BACSPayrollSoapBindingStub.java:199):

public dmu.p02233990.wswp.service.banktypes.Trailer
paySalaries(dmu.p02233990.wswp.service.payroll.Header header,
dmu.p02233990.wswp.service.payroll.Salary[] salaries,
dmu.p02233990.wswp.service.banktypes.Trailer trailer) throws
java.rmi.RemoteException {
if (super.cachedEndpoint == null) {
throw new org.apache.axis.NoEndPointException();
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[0]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI("");
_call.setEncodingStyle(null);
_call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
Boolean.FALSE);
_call.setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
Boolean.FALSE);

_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new
javax.xml.namespace.QName("http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";,
"paySalaries"));

setRequestHeaders(_call);
setAttachments(_call);
 try {java.lang.Object _resp = _call.invoke(new java.lang.Object[]
{header, salaries, trailer}); // **LINE 199**

if (_resp instanceof java.rmi.RemoteException) {
throw (java.rmi.RemoteException)_resp;
}


The Soap sent is:

POST /p02233990ws/services/BACSPayroll HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.3
Host: localhost:9090
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 1661


   http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
 http://dmu.ac.uk/csci3420/2006/02/BACSPayroll";>

   identifier
   2006-02-08
   De Montfort University
   
  http://dmu.ac.uk/csci3420/2006/02/BankTypes";>natwest
  http://dmu.ac.uk/csci3420/2006/02/BankTypes";>30-96-18
  http://dmu.ac.uk/csci3420/2006/02/BankTypes";>12345
  http://dmu.ac.uk/csci3420/2006/02/BankTypes";>Mike
Whittaker
   


   
  1
  
 http://dmu.ac.uk/csci3420/2006/02/BankTypes";>bobwest
 http://dmu.ac.uk/csci3420/2006/02/BankTypes";>30-96-21
 http://dmu.

wsdl2java DuplicateFileException

[Palakovich, Jim]

Hi,

 

I’m seeing some strange behavior with WSDL2Java that I
cannot explain (which is probably not surprising, since I’m fairly new to
web services).  When attempting to generate stub classes, I’m
getting the following exception:

 

org.apache.axis.wsdl.toJava.DuplicateFileException:
Duplicate file name: com\acme\api\obj\Int_valref.java.

Hint: you may have mapped two namespaces with elements of
the same name to the same package name.

    at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:110)

    at org.apache.axis.wsdl.toJava.JavaBeanWriter.generate(JavaBeanWriter.java:1406)

    at org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.java:113)

    at
org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421)

    at org.apache.axis.wsdl.gen.Parser.generateTypes(Parser.java:547)

    at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:432)

    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:595)

 

The snippet in question from my schema is:

 

    

    

   


   


   


   


    

    

 

    

    

   


   


    

    

    

 

    

    

   


   


   


    

    

 

Also, in the Int_valref.java file that gets generated, the Int_valref
class attempts to extend itself.

 

If I change all the above references of ‘simpleContent’
to ‘complexContent’, the stub generation completes successfully,
but class Int_valref still tries to extend itself.

 

Note that this same WSDL/Schema combination works just fine
with both the .NET and Sun JWSDP wsdl compilers.

 

Any suggestions on what might be going on here would be
graciously appreciated.

 

I’ve attached the full wsdl and schema files, if
necessary.

 

 

Thanks,

Jim

 








error.xsd
Description: error.xsd


error.wsdl
Description: error.wsdl

Re: Confused about more advanced WSDD usage

[Anne Thomas Manes]

It sounds to me like you didn't define the  definition properly. If you can post your WSDL, I'd be happy to look at it for you.AnneOn 2/7/06, 
Scott McCoy <[EMAIL PROTECTED]> wrote:This is quite close to what I am after, I want a properly marked up XML Document fragement to be my message.
Imagine your example, except with a few attributes :)  The:   1
   2approach to XML I find painful.We already have documents defined, and I am trying to model our services around them.For instance, we have an invoice document, with an xsd of:
            
    
            
                
                    

                    I would like to return this from my webservice call.  It will accept a different document type to define the order:
            
                        
            I would like to map these, attributes, etc, to service calls in the cleanest fasion possible with the most behind the scenes action from Axis available.
However, your example seems to not agree with wsdl2java so I'm having difficulty seeing how it really works.  After the changes made (Which I stumbled upon myself but noticed someone had already posted about) that are required to make it a valid XML document, it seems to still not be a valid WSDL document:
java.io.IOException: Emitter failure.  Invalid endpoint address in port addSoapPort in service AddServiceLocator:  ...    at org.apache.axis.wsdl.toJava.JavaServiceImplWriter.writeFileBody(JavaServiceImplWriter.java

:242)    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:595)On 2/7/06, Anne Thomas Manes
 <[EMAIL PROTECTED]
> wrote:I don't understand what you mean. The messaging API (i.e., provider="java:MSG") is a low-level API in which the application programmatically constructs and processes XML messages using DOM. If you don't want to work with DOM, then you shouldn't use the messaging API. 
To produce a method like this:public invoice handler (Calendar date, int id, int accountid, Item[] lineItems, float balance) {}you need to use the RPC API (
i.e., provider="java:RPC"). The RPC API does automagic mapping of Java objects to XML types. (Note that per the JAX-RPC spec, you should use Calendar instead of Date)Perhaps what you want is to use document style messages as opposed to rpc/encoded? Well -- you still use the RPC API. (Don't you hate these overloaded terms?) The RPC API supports four message styles: rpc/encoded, rpc/literal, wrapped doc/literal, and unwrapped doc/literal. I suspect you want wrapped doc/literal. If you are generating the WSDL then specify style="WRAPPED" in the WSDD. If you are generating code from WSDL, then you have to follow the wrapped convention in your WSDL. See my blog entry for instructions:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
Anne
On 2/7/06, Scott McCoy <[EMAIL PROTECTED]> wrote:


Hello All,    I am trying to implement a message-style API (as opposed to the automagical RPC stuff I've seen).  I'd like, however, to write my java service handlers in a more traditional fasion rather than accepting document fragments and handling them with a bunch of DOM code.  So I was doing some reading about WSDD/WSDL and Schema, and this should be possible.  But I'm not quite sure how it works, and the more I read and look at examples the more I spin my wheels.
Basically, I have a document fragment like this:            
                
            
        
    
        I would like to both return and accept this.It seems it should be possible, through some magic I don't quite yet understand, to map a service call to it with the following form:
public  handler (Date date, int id, int accountid, Item[] lineItems, float balance) {}Also, there should be some way to return this from a webservice handler as well.Can someone clear up how this works, exactly?  Simply defining this complexType as mapping to a specific method, as above, and being able to return such a thing.
My next question, is how can I stuff a handler in my request flow that will read the header and determine weither or not the main service handler is allowed to be called?  I would like to use this for a custom form of authentication, in which I check the soap envelopes Header before allowing the soap body elements to get mapped to method calls.

Re: java2wsdl interface question

[Anne Thomas Manes]

Nope. Create the bean.On 2/7/06, Nishant Deshpande <[EMAIL PROTECTED]> wrote:
i have been reading various threads asking this question on thenet but not really got any definitive answers so i will try here.so if i use java2wsdl to convert some api which either takes/returnsan interface, i get the following errors:
"""- The class com.[protected].ReportRequestObject does not contain adefault constructor, which is a requirement for a bean class.  Theclass cannot be converted into an xml schema type.  An xml schema
anyType will be used to define this class in the wsdl file.- The class com.[protected].ReportObject does not contain a defaultconstructor, which is a requirement for a bean class.  The classcannot be converted into an xml schema type.  An xml schema anyType
will be used to define this class in the wsdl file."""the only way i can think of to get around this is to create an'interface' bean (essentially an implementation of this interface with
a default constructor) and use this to create the wsdl and then editthe wsdl and i guess it will work.any better ways?

Re: method missing for WSDL containing simpleType use. A BIT URGENT!

[Anne Thomas Manes]

Actually, there is a problem in the WSDL, although that isn't what's causing your problem. As Ajith says, you're trying to use a feature that isn't yet supported. But meanwhile, for completeness sake...When using style="rpc", your message parts must reference types, not elements. You can fix the WSDL either by changing the style to "document" and removing the @namespace attributes from the  definitions (the easy alternative), or by changing the message part definitions to:
  
            
  And change the anonymous complexType definition in your Item element definition to a named type called "Item".AnneOn 2/8/06, 
Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hi Hui,There's nothing wrong with your WSDL but it's an Axis2- ADBlimitation for the time. We do not handle simple typerestrictions/enumerations - the schema parser just ignores thesimpletype's restriction and picks up OMElement for that!
If you need to use enums I would say you need to move to XMLBeansAjithOn 2/8/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:> Yeah, I had hoped so. So I changed the names of form "Property" to
> "ItemProperty". It still doesn't work, same exception complaining: The> method convertToPropertyType(String) is undefined for the type ConverterUtil> in the Property.java.>> Can you guys take a brief look at it and see whether I've messed up
> anything, Thanks!>> Here's the Types.xsd:> ==>> > 
http://www.w3.org/2001/XMLSchema"> targetNamespace="http://internal.aaa.com/fims/Types "> xmlns:tns="
http://internal.aaa.com/fims/Types">>> >> >   
> > > > 
>   > >> >   >  
> > > 
>> >> >> >   
>   > maxOccurs="unbounded"/>> >   
> >> >>> And the WSDL:> ===>> > >   targetNamespace="http://internal.aaa.com/fims">   xmlns="http://schemas.xmlsoap.org/wsdl/ "
>   xmlns:xs="http://www.w3.org/2001/XMLSchema">   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/
 ">   xmlns:tns="http://internal.aaa.com/fims">   xmlns:xsd="http://internal.aaa.com/fims/Types
">>>   http://internal.aaa.com/fims/Types"> location="Types.xsd"/>>>   
> >   >   > 
>   >>   > >   
>   > >   >>   
> http://schemas.xmlsoap.org/soap/http"/>> 
>   >   >  http://internal.aaa.com/fims
" use="literal"/>>   >   > http://internal.aaa.com/fims" use="literal"/>
>   > >   >   > > binding="tns:fimsServiceBinding">
>   > location="http://yjin-2.desktop.aaa.com:8080/axis2/services/fims> "/>> 
>   > >> On 2/7/06, Jim Azeltine <[EMAIL PROTECTED]
> wrote:>> Because I figured that since you said that you were using Eclipse, and> you were working with web services, that you were using the WTP plugin.> I would guess that you are picking up the Property class from the wrong
> package in your classpath.>> Jim>> Yu-Hui Jin <[EMAIL PROTECTED]> wrote:>> Hi, Jim,>> Not sure how you figure out i'm using WTP. But I don't see how it
> has to do with this generation problem. Besides, I'm not using Axis plugin> at all, I simply use the command-line WSDL2Java in Axis2 0.94.>>> -Hui>>> On 2/7/06, Jim Azeltine <
[EMAIL PROTECTED]> wrote:>> You need to find out if the Eclipse WTP plugin even supports> Axis 2 yet.>> Jim
>>> Yu-Hui Jin < [EMAIL PROTECTED]> wrote:>>> Hi, there,>> I defined the following type in my WSDL.
>> >   > 
> > > 
>   > >> The used in in an element:>> 
>   > >   >   > minOccurs="0" maxOccurs="unbounded"/>> >   > 
>> The code generates without any problem. But Eclipse reports> compilation error: The method convertToPropertyType(String) is undefined for> the type ConverterUtil in the Property.java
.>> I displayed the line which uses the method in bold here:>> if> ("Type".equals(reader.getLocalName())) {> String content =
> reader.getElementText();> object.setType> (org.apache.axis2.databinding.utils.ConverterUtil.convertToPropertyType> (> content));
>  count++;> }>> Is this a bug or am I missing anything?>>> regards,
>> -Hui>>>--Ajith Ranabahu

Axis2C deployment and clients

[Benjamin Bender]

Hi,

I'm got the latest version of Axis2C
running under Fedora Core 4 and I'm using it as standalone version
(i.e. I'm not running it in a Tomcat).
Now, I've got a C program and I want to deploy it as a web service.
Since, I'm new in Axis I have no idea
how to deploy this program and how to create a client for it. I tried
the Java version also and got some services
deployed and clients built. 

Can somebody tell me how to deploy services
and create clients with Axis2C, I did not find any 
documentation on it.

Thanks,
Ben

Re: [Axis2-0.94] wsdl2java generates in-out receiver for in-only operations

[Rubén Naranjo Izquierdo]

   Hi,

   I downloaded the latest codebase, tried the last code generator and 
realised that in generated stubs (with "-g" option); in-only operations are 
declared as "org.apache.axis2.description.OutOnlyAxisOperation". Is this 
behaviour normal or we are dealing with a new bug? 

   Thanks!

Rubén Naranjo

On Tuesday 07 February 2006 15:26, Ajith Ranabahu wrote:
> Hi Andreas,
> Yes this bug was realised recently and fixed in the latest codebase.
> Now the codegenerator generates correct message receivers based on the
> operation
>
> On 2/7/06, Andreas Bobek <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have a very small WSDL file with only one in-only operation.
> > When running wsdl2java it generates a services.xml file with
> > mep="http://www.w3.org/2004/08/wsdl/in-out";
> > and a MessageReceiver class inheriting from
> > AbstractInOutSyncMessageReceiver.
> > As expected, when invoking the service with ClientAPI it sends back a
> > fault. At service side RawXMLINOnlyMessageReceiver is used instead of
> > the generated MessageReceiver class.
> >
> > Is this bug already known? I couldn't find another post.
> > Thanks, Andreas Bobek.
>
> --
> Ajith Ranabahu

Re: Removed xalan specific tags from xsl's (Re: [Axis2] application scope)

[donnerdrummel2000-mailing]

oh yes... thats my fault! After 'maven clean' the
build was successful :-)))

Thanks a lot
Ted

--- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:

> did u run "maven clean"?
> 
> 
> On 2/8/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > Sorry, after update from svn and 'maven war' the
> build
> > faild with exactly the same failure (details see
> > attachment). There is maybe stil a bug in one of
> the
> > scripts...
> >
> > Thanks a lot
> > Ted
> > --- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:
> >
> > > Checked in fixes to the xsl's. Please try now.
> > >
> > > thanks,
> > > dims
> > >
> > > On 2/8/06, [EMAIL PROTECTED]
> > > <[EMAIL PROTECTED]> wrote:
> > > > ... so please have a look to this failure as
> well
> > > (see
> > > > attachement for details), this appears after
> > > excluding
> > > > the perf tests and running 'maven war' (maven
> > > 1.02,
> > > > jdk1.5)
> > > >
> > > > Thanks Ted
> > > > --- Davanum Srinivas <[EMAIL PROTECTED]>
> schrieb:
> > > >
> > > > > Guys!! i'll fix this today. Patience please
> :)
> > > > >
> > > > > -- dims
> > > > >
> > > > > On 2/8/06, Ajith Ranabahu
> > > <[EMAIL PROTECTED]>
> > > > > wrote:
> > > > > > ps - You seem to use JDK 1.5 !, We've
> been
> > > > > told about this problem
> > > > > > in JDK 1.5 and still trying to find a
> > > solution.
> > > > > > For the build, exclude the perf tests in
> the
> > > > > integration module.
> > > > > > (look for the project.xml inside the
> > > integration
> > > > > folder and edit the
> > > > > > excludes under build/unittests/excludes)
> > > > > >
> > > > > > On 2/8/06,
> [EMAIL PROTECTED]
> > > > > > <[EMAIL PROTECTED]>
> wrote:
> > > > > > > Hi Deepal,
> > > > > > >
> > > > > > > sorry to say that, but the build failed
> even
> > > > > today
> > > > > > > (using maven war). For more detail see
> > > > > attachement,
> > > > > > > maybe this will help you to fix an other
> bug
> > > or
> > > > > giving
> > > > > > > me a hint what i did wrong.
> > > > > > >
> > > > > > > Thank you,
> > > > > > > Ted
> > > > > > > --- Deepal Jayasinghe
> <[EMAIL PROTECTED]>
> > > > > schrieb:
> > > > > > >
> > > > > > > > Hi Ted;
> > > > > > > >
> > > > > > > > I dont think maven war goal will fail
> now
> > > ,
> > > > > there
> > > > > > > > was a bug and we have
> > > > > > > > fixed that , try and see :)
> > > > > > > >
> > > > > > > > [EMAIL PROTECTED]
> wrote:
> > > > > > > >
> > > > > > > > >Wow, Deepal this was realy one of the
> > > > > quickest
> > > > > > > > replys
> > > > > > > > >I got! So I'll try to build the
> source
> > > but
> > > > > since
> > > > > > > > some
> > > > > > > > >days I've problems to do this
> > > successfuly.
> > > > > Can you
> > > > > > > > >please give me a hint to build the
> *.war
> > > > > without
> > > > > > > > >running into an build failure.
> > > > > > > > >
> > > > > > > > >Thanks a lot
> > > > > > > > >Ted
> > > > > > > > >--- Deepal Jayasinghe
> > > <[EMAIL PROTECTED]>
> > > > > > > > schrieb:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >>I understood the problem , and I
> just
> > > fixed
> > > > > that
> > > > > > > > :)
> > > > > > > > >>
> > > > > > > > >>if you can get Axis2 source update ,
> > > then
> > > > > you will
> > > > > > > > >>be able to get the
> > > > > > > > >>correct behavior , and you do not
> need
> > > to
> > > > > send the
> > > > > > > > >>service group id , if
> > > > > > > > >>you deploy the service in
> application
> > > scope.
> > > > > > > > >>
> > > > > > > > >>[EMAIL PROTECTED]
> > > wrote:
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>Hi Deepal,
> > > > > > > > >>>
> > > > > > > > >>>first at all, thanks for your
> reply.
> > > Okay,
> > > > > I'll
> > > > > > > > try
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>to
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>clarify the 'it does not work'. To
> test
> > > > > this
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>scoping
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>feature for the 0.94 release I used
> a
> > > > > simple
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>Service
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>which increases an integer value at
> > > every
> > > > > call
> > > > > > > > and
> > > > > > > > >>>returns this value. After
> deployment
> > > under
> > > > > the
> > > > > > > > >>> scope="application">-setting
> > > it
> > > > > does not
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>work
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>wich means it returns for every
> request
> > > a
> > > > > '1' but
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>it
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>>should be for 3 request
> '1','2','3'...
> > > > > > > > >>>The only way to get this behavior
> is to
> > > > > deploy
> > > > > > > > the
> > > > > > > > >>>service with the scope="transport"
> 
=== message tru

Re: newbie questions on "style" attribute

[Davanum Srinivas]

Thanks as always Anne :) Added a new FAQ

http://wiki.apache.org/ws/FrontPage/Axis/StyleInWSDDAndWSDL


On 2/8/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> The style attribute in WSDL is different from the style attribute in WSDD.
>
> The WSDL style has two possible options: RPC and Document. (If neither is
> specified, it defaults to "document".) This attribute refers to the SOAP
> message style -- whether the SOAP Body contains a document defined by a
> schema or whether the Body is constructed dynamically based on the method
> name and a set of parameter types. WSDL has another attribute, "use", which
> indicates whether the message structure is defined by a schema
> (use="literal") or generated using the SOAP encoding data model
> (use="encoded"). Valid combinations of these two attributes include
> document/literal, rpc/literal, and rpc/encoded.
>
> The WSDD style has four options: RPC, WRAPPED, DOCUMENT, MESSAGE. If no
> style is specified, it defaults to "RPC".) This style attribute encompasses
> both message style and programming style. There are three types of
> programming style:
> - a parameterized invocation API (XML parameters are mapped to individual
> Java classes):
> return method(arg1, arg2)
> - an object-based invocation API (XML parameters are collectively mapped to
> a bean):
> return method (object)
> - a messaging API (XML messages are mapped to DOM):
> Document method(Document)
>
> RPC produces rpc/encoded with a parameterized API (you can use the "use"
> attribute to specify that you want rpc/literal)
> WRAPPED produces document/literal with a parameterized API
> DOCUMENT produces document/literal with an object-based API
> MESSAGE produces document/literal with a messaging API
>
> For more information on the WRAPPED style, see my blog:
> http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
>
> Anne
>
> On 2/8/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Anyone can help me to understand the "style" element better. (well, or
> pointing me to some good articles on it?)
> >
> > Here's what's puzzling me:
> >
> > In Axis1.x user guide, it says the "service" element can have a "style"
> attribute.  I also see under the "wsdl:binding" element, both "soap:binding"
> and "soap:operation" elements can have a "style" attribute as well.   I've
> got a few questions:
> >
> > - do they have the same meaning and one will overide the other?
> >
> > - when do I select "rpc" and "document" for my WSDL?  It seems "document"
> is suggested for Axis 1.x, is it still a better choice for Axis2?
> >
> >
> > thanks,
> >
> > -Hui
> >
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

Re: Removed xalan specific tags from xsl's (Re: [Axis2] application scope)

[Davanum Srinivas]

did u run "maven clean"?


On 2/8/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Sorry, after update from svn and 'maven war' the build
> faild with exactly the same failure (details see
> attachment). There is maybe stil a bug in one of the
> scripts...
>
> Thanks a lot
> Ted
> --- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:
>
> > Checked in fixes to the xsl's. Please try now.
> >
> > thanks,
> > dims
> >
> > On 2/8/06, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> wrote:
> > > ... so please have a look to this failure as well
> > (see
> > > attachement for details), this appears after
> > excluding
> > > the perf tests and running 'maven war' (maven
> > 1.02,
> > > jdk1.5)
> > >
> > > Thanks Ted
> > > --- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:
> > >
> > > > Guys!! i'll fix this today. Patience please :)
> > > >
> > > > -- dims
> > > >
> > > > On 2/8/06, Ajith Ranabahu
> > <[EMAIL PROTECTED]>
> > > > wrote:
> > > > > ps - You seem to use JDK 1.5 !, We've been
> > > > told about this problem
> > > > > in JDK 1.5 and still trying to find a
> > solution.
> > > > > For the build, exclude the perf tests in the
> > > > integration module.
> > > > > (look for the project.xml inside the
> > integration
> > > > folder and edit the
> > > > > excludes under build/unittests/excludes)
> > > > >
> > > > > On 2/8/06, [EMAIL PROTECTED]
> > > > > <[EMAIL PROTECTED]> wrote:
> > > > > > Hi Deepal,
> > > > > >
> > > > > > sorry to say that, but the build failed even
> > > > today
> > > > > > (using maven war). For more detail see
> > > > attachement,
> > > > > > maybe this will help you to fix an other bug
> > or
> > > > giving
> > > > > > me a hint what i did wrong.
> > > > > >
> > > > > > Thank you,
> > > > > > Ted
> > > > > > --- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > > schrieb:
> > > > > >
> > > > > > > Hi Ted;
> > > > > > >
> > > > > > > I dont think maven war goal will fail now
> > ,
> > > > there
> > > > > > > was a bug and we have
> > > > > > > fixed that , try and see :)
> > > > > > >
> > > > > > > [EMAIL PROTECTED] wrote:
> > > > > > >
> > > > > > > >Wow, Deepal this was realy one of the
> > > > quickest
> > > > > > > replys
> > > > > > > >I got! So I'll try to build the source
> > but
> > > > since
> > > > > > > some
> > > > > > > >days I've problems to do this
> > successfuly.
> > > > Can you
> > > > > > > >please give me a hint to build the *.war
> > > > without
> > > > > > > >running into an build failure.
> > > > > > > >
> > > > > > > >Thanks a lot
> > > > > > > >Ted
> > > > > > > >--- Deepal Jayasinghe
> > <[EMAIL PROTECTED]>
> > > > > > > schrieb:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >>I understood the problem , and I just
> > fixed
> > > > that
> > > > > > > :)
> > > > > > > >>
> > > > > > > >>if you can get Axis2 source update ,
> > then
> > > > you will
> > > > > > > >>be able to get the
> > > > > > > >>correct behavior , and you do not need
> > to
> > > > send the
> > > > > > > >>service group id , if
> > > > > > > >>you deploy the service in application
> > scope.
> > > > > > > >>
> > > > > > > >>[EMAIL PROTECTED]
> > wrote:
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>Hi Deepal,
> > > > > > > >>>
> > > > > > > >>>first at all, thanks for your reply.
> > Okay,
> > > > I'll
> > > > > > > try
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>to
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>clarify the 'it does not work'. To test
> > > > this
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>scoping
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>feature for the 0.94 release I used a
> > > > simple
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>Service
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>which increases an integer value at
> > every
> > > > call
> > > > > > > and
> > > > > > > >>>returns this value. After deployment
> > under
> > > > the
> > > > > > > >>>-setting
> > it
> > > > does not
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>work
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>wich means it returns for every request
> > a
> > > > '1' but
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>it
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>should be for 3 request '1','2','3'...
> > > > > > > >>>The only way to get this behavior is to
> > > > deploy
> > > > > > > the
> > > > > > > >>>service with the scope="transport"
> > setting.
> > > > > > > >>>
> > > > > > > >>>You said that there is a usage of a
> > service
> > > > group
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>ID
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>for the intern handling of some of this
> > > > scope
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>types.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>>Does this mean, that I've to deploy my
> > > > single
> > > > > > > >>>Countservice as a service group to get
> > all
> > > > the
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>scoping
> > > > > > > >>

Re: newbie questions on "style" attribute

[Anne Thomas Manes]

The style attribute in WSDL is different from the style attribute in WSDD.The WSDL style has two possible options: RPC and Document. (If neither is specified, it defaults to "document".) This attribute refers to the SOAP message style -- whether the SOAP Body contains a document defined by a schema or whether the Body is constructed dynamically based on the method name and a set of parameter types. WSDL has another attribute, "use", which indicates whether the message structure is defined by a schema (use="literal") or generated using the SOAP encoding data model (use="encoded"). Valid combinations of these two attributes include document/literal, rpc/literal, and rpc/encoded.
The WSDD style has four options: RPC, WRAPPED, DOCUMENT, MESSAGE. If no style is specified, it defaults to "RPC".) This style attribute encompasses both message style and programming style. There are three types of programming style: 
- a parameterized invocation API (XML parameters are mapped to individual Java classes):return method(arg1, arg2)- an object-based invocation API (XML parameters are collectively mapped to a bean):
return method (object)- a messaging API (XML messages are mapped to DOM):Document method(Document)RPC produces rpc/encoded with a parameterized API (you can use the "use" attribute to specify that you want rpc/literal)
WRAPPED produces document/literal with a parameterized APIDOCUMENT produces document/literal with an object-based APIMESSAGE produces document/literal with a messaging APIFor more information on the WRAPPED style, see my blog:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.htmlAnneOn 2/8/06, 
Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
Hi, Anyone can help me to understand the "style" element better. (well, or pointing me to some good articles on it?)Here's what's puzzling me: In Axis1.x user guide, it says the "service" element can have a "style" attribute.  I also see under the "wsdl:binding" element, both "soap:binding" and "soap:operation" elements can have a "style" attribute as well.   I've got a few questions: 
- do they have the same meaning and one will overide the other? - when do I select "rpc" and "document" for my WSDL?  It seems "document" is suggested for Axis 1.x, is it still a better choice for Axis2? 
thanks,-Hui 

RE: Generating code with wsdl2code

[Ricardo Blanes]

Thanks Ajith

I have changed the command to invoke the wsdl2code by this:

Wsdl2code -uri /afolder/ip.wsdl -o /outputfolder/ip -ss -d xmlbeans -sd

And I have the same result. I thing that all paremeters are being used, because 
the service.xml has been created (and is the last parameter)

I have been making proves. If I use the ip.wsdl (that imports the schema using 
the tag wsdl:import ) it Works, but I can't use this because it is supplied by 
a third party.

I attach the new version of ip.wsdl.

Ricardo Blanes


-Mensaje original-
De: Ajith Ranabahu [mailto:[EMAIL PROTECTED] 
Enviado el: miércoles, 08 de febrero de 2006 14:18
Para: axis-user@ws.apache.org
Asunto: Re: Generating code with wsdl2code

Hi,
I see a number of simpletype restrictions in your schema. ADB does not
support these schema constructions and that may well be the problem
here. Even though you explicitly mentioned  -d xmlbeans, there is a
problem with the script (both the bat and the sh) that caused it not
to pick some of the parameters. (I am inclined to think that since the
xmlbeans argument is last, that can be the case)

Please check whether you see any XMLBeans stuff generated.


On 2/8/06, Ricardo Blanes <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi all
>
>
>
> When I generate code using axis2-0.94 wsdl2code applied to a
> wsdl that imports an schema (both of them attached in this mail), the
> receiver class compiles with errors, and the methods in the skeleton class
> has a parameter of type OMElement, instead of the appropriate type based on
> schema and wsdl.
>
>
>
> This is the command I execute:
>
>
>
> Wsdl2code -uri /afolder/ip.wsdl -o /outputfolder/ip -p
> com.tissat.guide.ip -ss -d xmlbeans
>
>
>
> Is this a bug? or have I done anything wrong?
>
>
>
> Thanks, Ricardo Blanes
>
>  
>  Nota Legal: Este correo electronico puede contener informacion
> estrictamente confidencial y es de uso exclusivo del destinatario, quedando
> prohibida a cualquier otra persona su revelacion, copia, distribucion, o el
> ejercicio de cualquier accion relativa a su contenido. Si ha recibido este
> correo electronico por error, por favor, conteste al remitente, y
> posteriormente proceda a borrarlo de su sistema. Gracias por su
> colaboracion.
>
> Confidentiality notice: This e-mail message may contain confidential and/or
> legally privileged information and is solely for the attention and use of
> the intended recipient. Any disclosure, copying, distribution or the taking
> of any action with relation to  the contents of this e-mail by any other
> person is strictly prohibited. If you believe that this e-mail has been
> mistakenly sent  to you,
> please reply to the sender from whom you received the message in error and
> then delete the original e-mail from your system. Thank you for your
> co-operation. 
>
>
>
>
>
>
>
>
>
>


--
Ajith Ranabahu




Nota Legal: Este correo electrónico puede contener información estrictamente 
confidencial y es de uso exclusivo del destinatario, quedando prohibida a 
cualquier otra persona su revelación, copia, distribución, o el ejercicio de 
cualquier acción relativa a su contenido. Si ha recibido este correo 
electrónico por error, por favor, conteste al remitente, y posteriormente 
proceda a borrarlo de su sistema. Gracias por su colaboración.

Confidentiality notice: This e-mail message may contain confidential and/or 
legally privileged information and is solely for the attention and use of the 
intended recipient. Any disclosure, copying, distribution or the taking of any 
action with relation to  the contents of this e-mail by any other person is 
strictly prohibited. If you believe that this e-mail has been mistakenly sent  
to you, please reply to the sender from whom you received the message in error 
and then delete the original e-mail from your system. Thank you for your 
co-operation.




guide_trial.xsd
Description: guide_trial.xsd


ip2.wsdl
Description: ip2.wsdl

RE: Removed xalan specific tags from xsl's (Re: [Axis2] application scope)

[donnerdrummel2000-mailing]

Sorry, after update from svn and 'maven war' the build
faild with exactly the same failure (details see
attachment). There is maybe stil a bug in one of the
scripts...

Thanks a lot
Ted
--- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:

> Checked in fixes to the xsl's. Please try now.
> 
> thanks,
> dims
> 
> On 2/8/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > ... so please have a look to this failure as well
> (see
> > attachement for details), this appears after
> excluding
> > the perf tests and running 'maven war' (maven
> 1.02,
> > jdk1.5)
> >
> > Thanks Ted
> > --- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:
> >
> > > Guys!! i'll fix this today. Patience please :)
> > >
> > > -- dims
> > >
> > > On 2/8/06, Ajith Ranabahu
> <[EMAIL PROTECTED]>
> > > wrote:
> > > > ps - You seem to use JDK 1.5 !, We've been
> > > told about this problem
> > > > in JDK 1.5 and still trying to find a
> solution.
> > > > For the build, exclude the perf tests in the
> > > integration module.
> > > > (look for the project.xml inside the
> integration
> > > folder and edit the
> > > > excludes under build/unittests/excludes)
> > > >
> > > > On 2/8/06, [EMAIL PROTECTED]
> > > > <[EMAIL PROTECTED]> wrote:
> > > > > Hi Deepal,
> > > > >
> > > > > sorry to say that, but the build failed even
> > > today
> > > > > (using maven war). For more detail see
> > > attachement,
> > > > > maybe this will help you to fix an other bug
> or
> > > giving
> > > > > me a hint what i did wrong.
> > > > >
> > > > > Thank you,
> > > > > Ted
> > > > > --- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > schrieb:
> > > > >
> > > > > > Hi Ted;
> > > > > >
> > > > > > I dont think maven war goal will fail now
> ,
> > > there
> > > > > > was a bug and we have
> > > > > > fixed that , try and see :)
> > > > > >
> > > > > > [EMAIL PROTECTED] wrote:
> > > > > >
> > > > > > >Wow, Deepal this was realy one of the
> > > quickest
> > > > > > replys
> > > > > > >I got! So I'll try to build the source
> but
> > > since
> > > > > > some
> > > > > > >days I've problems to do this
> successfuly.
> > > Can you
> > > > > > >please give me a hint to build the *.war
> > > without
> > > > > > >running into an build failure.
> > > > > > >
> > > > > > >Thanks a lot
> > > > > > >Ted
> > > > > > >--- Deepal Jayasinghe
> <[EMAIL PROTECTED]>
> > > > > > schrieb:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>I understood the problem , and I just
> fixed
> > > that
> > > > > > :)
> > > > > > >>
> > > > > > >>if you can get Axis2 source update ,
> then
> > > you will
> > > > > > >>be able to get the
> > > > > > >>correct behavior , and you do not need
> to
> > > send the
> > > > > > >>service group id , if
> > > > > > >>you deploy the service in application
> scope.
> > > > > > >>
> > > > > > >>[EMAIL PROTECTED]
> wrote:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>>Hi Deepal,
> > > > > > >>>
> > > > > > >>>first at all, thanks for your reply.
> Okay,
> > > I'll
> > > > > > try
> > > > > > >>>
> > > > > > >>>
> > > > > > >>to
> > > > > > >>
> > > > > > >>
> > > > > > >>>clarify the 'it does not work'. To test
> > > this
> > > > > > >>>
> > > > > > >>>
> > > > > > >>scoping
> > > > > > >>
> > > > > > >>
> > > > > > >>>feature for the 0.94 release I used a
> > > simple
> > > > > > >>>
> > > > > > >>>
> > > > > > >>Service
> > > > > > >>
> > > > > > >>
> > > > > > >>>which increases an integer value at
> every
> > > call
> > > > > > and
> > > > > > >>>returns this value. After deployment
> under
> > > the
> > > > > > >>>-setting
> it
> > > does not
> > > > > > >>>
> > > > > > >>>
> > > > > > >>work
> > > > > > >>
> > > > > > >>
> > > > > > >>>wich means it returns for every request
> a
> > > '1' but
> > > > > > >>>
> > > > > > >>>
> > > > > > >>it
> > > > > > >>
> > > > > > >>
> > > > > > >>>should be for 3 request '1','2','3'...
> > > > > > >>>The only way to get this behavior is to
> > > deploy
> > > > > > the
> > > > > > >>>service with the scope="transport"
> setting.
> > > > > > >>>
> > > > > > >>>You said that there is a usage of a
> service
> > > group
> > > > > > >>>
> > > > > > >>>
> > > > > > >>ID
> > > > > > >>
> > > > > > >>
> > > > > > >>>for the intern handling of some of this
> > > scope
> > > > > > >>>
> > > > > > >>>
> > > > > > >>types.
> > > > > > >>
> > > > > > >>
> > > > > > >>>Does this mean, that I've to deploy my
> > > single
> > > > > > >>>Countservice as a service group to get
> all
> > > the
> > > > > > >>>
> > > > > > >>>
> > > > > > >>scoping
> > > > > > >>
> > > > > > >>
> > > > > > >>>features to work?
> > > > > > >>>
> > > > > > >>>Thanks Ted
> > > > > > >>>
> > > > > > >>>--- Deepal Jayasinghe
> > > <[EMAIL PROTECTED]>
> > > > > > wrote:
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>Hi Ted;
> > > > > > >>>
> > > > > > >>>what do u mean by that does not work ?
> , I
> 
=== message truncated ===






___ 
Telef

axis2axis2

[Alejandro Ariel de Lio]

Hi all there. I just wanted to ask about how true is it that your programs
in axis will work in axis2, considering that the zipped size of the axis
source code is about 17mb while the axis2 one barely rounds the 2mb

Removed xalan specific tags from xsl's (Re: [Axis2] application scope)

[Davanum Srinivas]

Checked in fixes to the xsl's. Please try now.

thanks,
dims

On 2/8/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> ... so please have a look to this failure as well (see
> attachement for details), this appears after excluding
> the perf tests and running 'maven war' (maven 1.02,
> jdk1.5)
>
> Thanks Ted
> --- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:
>
> > Guys!! i'll fix this today. Patience please :)
> >
> > -- dims
> >
> > On 2/8/06, Ajith Ranabahu <[EMAIL PROTECTED]>
> > wrote:
> > > ps - You seem to use JDK 1.5 !, We've been
> > told about this problem
> > > in JDK 1.5 and still trying to find a solution.
> > > For the build, exclude the perf tests in the
> > integration module.
> > > (look for the project.xml inside the integration
> > folder and edit the
> > > excludes under build/unittests/excludes)
> > >
> > > On 2/8/06, [EMAIL PROTECTED]
> > > <[EMAIL PROTECTED]> wrote:
> > > > Hi Deepal,
> > > >
> > > > sorry to say that, but the build failed even
> > today
> > > > (using maven war). For more detail see
> > attachement,
> > > > maybe this will help you to fix an other bug or
> > giving
> > > > me a hint what i did wrong.
> > > >
> > > > Thank you,
> > > > Ted
> > > > --- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > schrieb:
> > > >
> > > > > Hi Ted;
> > > > >
> > > > > I dont think maven war goal will fail now ,
> > there
> > > > > was a bug and we have
> > > > > fixed that , try and see :)
> > > > >
> > > > > [EMAIL PROTECTED] wrote:
> > > > >
> > > > > >Wow, Deepal this was realy one of the
> > quickest
> > > > > replys
> > > > > >I got! So I'll try to build the source but
> > since
> > > > > some
> > > > > >days I've problems to do this successfuly.
> > Can you
> > > > > >please give me a hint to build the *.war
> > without
> > > > > >running into an build failure.
> > > > > >
> > > > > >Thanks a lot
> > > > > >Ted
> > > > > >--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > > > schrieb:
> > > > > >
> > > > > >
> > > > > >
> > > > > >>I understood the problem , and I just fixed
> > that
> > > > > :)
> > > > > >>
> > > > > >>if you can get Axis2 source update , then
> > you will
> > > > > >>be able to get the
> > > > > >>correct behavior , and you do not need to
> > send the
> > > > > >>service group id , if
> > > > > >>you deploy the service in application scope.
> > > > > >>
> > > > > >>[EMAIL PROTECTED] wrote:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>>Hi Deepal,
> > > > > >>>
> > > > > >>>first at all, thanks for your reply. Okay,
> > I'll
> > > > > try
> > > > > >>>
> > > > > >>>
> > > > > >>to
> > > > > >>
> > > > > >>
> > > > > >>>clarify the 'it does not work'. To test
> > this
> > > > > >>>
> > > > > >>>
> > > > > >>scoping
> > > > > >>
> > > > > >>
> > > > > >>>feature for the 0.94 release I used a
> > simple
> > > > > >>>
> > > > > >>>
> > > > > >>Service
> > > > > >>
> > > > > >>
> > > > > >>>which increases an integer value at every
> > call
> > > > > and
> > > > > >>>returns this value. After deployment under
> > the
> > > > > >>>-setting it
> > does not
> > > > > >>>
> > > > > >>>
> > > > > >>work
> > > > > >>
> > > > > >>
> > > > > >>>wich means it returns for every request a
> > '1' but
> > > > > >>>
> > > > > >>>
> > > > > >>it
> > > > > >>
> > > > > >>
> > > > > >>>should be for 3 request '1','2','3'...
> > > > > >>>The only way to get this behavior is to
> > deploy
> > > > > the
> > > > > >>>service with the scope="transport" setting.
> > > > > >>>
> > > > > >>>You said that there is a usage of a service
> > group
> > > > > >>>
> > > > > >>>
> > > > > >>ID
> > > > > >>
> > > > > >>
> > > > > >>>for the intern handling of some of this
> > scope
> > > > > >>>
> > > > > >>>
> > > > > >>types.
> > > > > >>
> > > > > >>
> > > > > >>>Does this mean, that I've to deploy my
> > single
> > > > > >>>Countservice as a service group to get all
> > the
> > > > > >>>
> > > > > >>>
> > > > > >>scoping
> > > > > >>
> > > > > >>
> > > > > >>>features to work?
> > > > > >>>
> > > > > >>>Thanks Ted
> > > > > >>>
> > > > > >>>--- Deepal Jayasinghe
> > <[EMAIL PROTECTED]>
> > > > > wrote:
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>Hi Ted;
> > > > > >>>
> > > > > >>>what do u mean by that does not work ? , I
> > > > > >>>
> > > > > >>>
> > > > > >>recently
> > > > > >>
> > > > > >>
> > > > > >>>changed scope
> > > > > >>>handling , and I hope that should work.
> > > > > >>>
> > > > > >>>and that work as follows ,
> > > > > >>>  1. If you deploy a service under the
> > scope
> > > > > >>>"request" , then there
> > > > > >>>wont be any sessions management even if you
> > send
> > > > > >>>
> > > > > >>>
> > > > > >>the
> > > > > >>
> > > > > >>
> > > > > >>>service group ID
> > > > > >>>back (we mange session using ServiceGroup
> > ID)
> > > > > >>>  2. If you deploy a service in the
> > transport
> > > > > >>>session scope , then the
> > > > > >>>there will be session management using
> > transport
> > > > > >>>cookies and there
> > > > > >>>will be only one instance

Re: [Axis2] application scope

[donnerdrummel2000-mailing]

... so please have a look to this failure as well (see
attachement for details), this appears after excluding
the perf tests and running 'maven war' (maven 1.02,
jdk1.5)

Thanks Ted
--- Davanum Srinivas <[EMAIL PROTECTED]> schrieb:

> Guys!! i'll fix this today. Patience please :)
> 
> -- dims
> 
> On 2/8/06, Ajith Ranabahu <[EMAIL PROTECTED]>
> wrote:
> > ps - You seem to use JDK 1.5 !, We've been
> told about this problem
> > in JDK 1.5 and still trying to find a solution.
> > For the build, exclude the perf tests in the 
> integration module.
> > (look for the project.xml inside the integration
> folder and edit the
> > excludes under build/unittests/excludes)
> >
> > On 2/8/06, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> wrote:
> > > Hi Deepal,
> > >
> > > sorry to say that, but the build failed even
> today
> > > (using maven war). For more detail see
> attachement,
> > > maybe this will help you to fix an other bug or
> giving
> > > me a hint what i did wrong.
> > >
> > > Thank you,
> > > Ted
> > > --- Deepal Jayasinghe <[EMAIL PROTECTED]>
> schrieb:
> > >
> > > > Hi Ted;
> > > >
> > > > I dont think maven war goal will fail now ,
> there
> > > > was a bug and we have
> > > > fixed that , try and see :)
> > > >
> > > > [EMAIL PROTECTED] wrote:
> > > >
> > > > >Wow, Deepal this was realy one of the
> quickest
> > > > replys
> > > > >I got! So I'll try to build the source but
> since
> > > > some
> > > > >days I've problems to do this successfuly.
> Can you
> > > > >please give me a hint to build the *.war
> without
> > > > >running into an build failure.
> > > > >
> > > > >Thanks a lot
> > > > >Ted
> > > > >--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > > schrieb:
> > > > >
> > > > >
> > > > >
> > > > >>I understood the problem , and I just fixed
> that
> > > > :)
> > > > >>
> > > > >>if you can get Axis2 source update , then
> you will
> > > > >>be able to get the
> > > > >>correct behavior , and you do not need to
> send the
> > > > >>service group id , if
> > > > >>you deploy the service in application scope.
> > > > >>
> > > > >>[EMAIL PROTECTED] wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >>>Hi Deepal,
> > > > >>>
> > > > >>>first at all, thanks for your reply. Okay,
> I'll
> > > > try
> > > > >>>
> > > > >>>
> > > > >>to
> > > > >>
> > > > >>
> > > > >>>clarify the 'it does not work'. To test
> this
> > > > >>>
> > > > >>>
> > > > >>scoping
> > > > >>
> > > > >>
> > > > >>>feature for the 0.94 release I used a
> simple
> > > > >>>
> > > > >>>
> > > > >>Service
> > > > >>
> > > > >>
> > > > >>>which increases an integer value at every
> call
> > > > and
> > > > >>>returns this value. After deployment under
> the
> > > > >>>-setting it
> does not
> > > > >>>
> > > > >>>
> > > > >>work
> > > > >>
> > > > >>
> > > > >>>wich means it returns for every request a
> '1' but
> > > > >>>
> > > > >>>
> > > > >>it
> > > > >>
> > > > >>
> > > > >>>should be for 3 request '1','2','3'...
> > > > >>>The only way to get this behavior is to
> deploy
> > > > the
> > > > >>>service with the scope="transport" setting.
> > > > >>>
> > > > >>>You said that there is a usage of a service
> group
> > > > >>>
> > > > >>>
> > > > >>ID
> > > > >>
> > > > >>
> > > > >>>for the intern handling of some of this
> scope
> > > > >>>
> > > > >>>
> > > > >>types.
> > > > >>
> > > > >>
> > > > >>>Does this mean, that I've to deploy my
> single
> > > > >>>Countservice as a service group to get all
> the
> > > > >>>
> > > > >>>
> > > > >>scoping
> > > > >>
> > > > >>
> > > > >>>features to work?
> > > > >>>
> > > > >>>Thanks Ted
> > > > >>>
> > > > >>>--- Deepal Jayasinghe
> <[EMAIL PROTECTED]>
> > > > wrote:
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>Hi Ted;
> > > > >>>
> > > > >>>what do u mean by that does not work ? , I
> > > > >>>
> > > > >>>
> > > > >>recently
> > > > >>
> > > > >>
> > > > >>>changed scope
> > > > >>>handling , and I hope that should work.
> > > > >>>
> > > > >>>and that work as follows ,
> > > > >>>  1. If you deploy a service under the
> scope
> > > > >>>"request" , then there
> > > > >>>wont be any sessions management even if you
> send
> > > > >>>
> > > > >>>
> > > > >>the
> > > > >>
> > > > >>
> > > > >>>service group ID
> > > > >>>back (we mange session using ServiceGroup
> ID)
> > > > >>>  2. If you deploy a service in the
> transport
> > > > >>>session scope , then the
> > > > >>>there will be session management using
> transport
> > > > >>>cookies and there
> > > > >>>will be only one instance of service impl
> class
> > > > >>>
> > > > >>>
> > > > >>for
> > > > >>
> > > > >>
> > > > >>>that transport
> > > > >>>session.
> > > > >>> 3. If you deploy a service in scope of
> SOAP
> > > > >>>
> 
=== message truncated ===






___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.deBUILD FAILED
File.. C:\Dokumente und Einstellungen\ted\.maven\cache\maven-multiproje
ct-plugin-1.3.1\plug

Different handlers per operations in same port

[Jean-Noel Colin]

Title: Different handlers per operations in same port



Hi  

I have a webservice with 2 methods, hence 2 operations in the same porttype.
I would like to have different handlers apply to each method. Is it possible with Axis 1.3? 

Regards

Jean-Noel Colin

Re: Generating code with wsdl2code

[Ajith Ranabahu]

Hi,
I see a number of simpletype restrictions in your schema. ADB does not
support these schema constructions and that may well be the problem
here. Even though you explicitly mentioned  -d xmlbeans, there is a
problem with the script (both the bat and the sh) that caused it not
to pick some of the parameters. (I am inclined to think that since the
xmlbeans argument is last, that can be the case)

Please check whether you see any XMLBeans stuff generated.


On 2/8/06, Ricardo Blanes <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi all
>
>
>
> When I generate code using axis2-0.94 wsdl2code applied to a
> wsdl that imports an schema (both of them attached in this mail), the
> receiver class compiles with errors, and the methods in the skeleton class
> has a parameter of type OMElement, instead of the appropriate type based on
> schema and wsdl.
>
>
>
> This is the command I execute:
>
>
>
> Wsdl2code –uri /afolder/ip.wsdl –o /outputfolder/ip –p
> com.tissat.guide.ip –ss –d xmlbeans
>
>
>
> Is this a bug? or have I done anything wrong?
>
>
>
> Thanks, Ricardo Blanes
>
>  
>  Nota Legal: Este correo electronico puede contener informacion
> estrictamente confidencial y es de uso exclusivo del destinatario, quedando
> prohibida a cualquier otra persona su revelacion, copia, distribucion, o el
> ejercicio de cualquier accion relativa a su contenido. Si ha recibido este
> correo electronico por error, por favor, conteste al remitente, y
> posteriormente proceda a borrarlo de su sistema. Gracias por su
> colaboracion.
>
> Confidentiality notice: This e-mail message may contain confidential and/or
> legally privileged information and is solely for the attention and use of
> the intended recipient. Any disclosure, copying, distribution or the taking
> of any action with relation to  the contents of this e-mail by any other
> person is strictly prohibited. If you believe that this e-mail has been
> mistakenly sent  to you,
> please reply to the sender from whom you received the message in error and
> then delete the original e-mail from your system. Thank you for your
> co-operation. 
>
>
>
>
>
>
>
>
>
>


--
Ajith Ranabahu

Re: [Axis2] application scope

[Davanum Srinivas]

Guys!! i'll fix this today. Patience please :)

-- dims

On 2/8/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> ps - You seem to use JDK 1.5 !, We've been told about this problem
> in JDK 1.5 and still trying to find a solution.
> For the build, exclude the perf tests in the  integration module.
> (look for the project.xml inside the integration folder and edit the
> excludes under build/unittests/excludes)
>
> On 2/8/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > Hi Deepal,
> >
> > sorry to say that, but the build failed even today
> > (using maven war). For more detail see attachement,
> > maybe this will help you to fix an other bug or giving
> > me a hint what i did wrong.
> >
> > Thank you,
> > Ted
> > --- Deepal Jayasinghe <[EMAIL PROTECTED]> schrieb:
> >
> > > Hi Ted;
> > >
> > > I dont think maven war goal will fail now , there
> > > was a bug and we have
> > > fixed that , try and see :)
> > >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > >Wow, Deepal this was realy one of the quickest
> > > replys
> > > >I got! So I'll try to build the source but since
> > > some
> > > >days I've problems to do this successfuly. Can you
> > > >please give me a hint to build the *.war without
> > > >running into an build failure.
> > > >
> > > >Thanks a lot
> > > >Ted
> > > >--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > schrieb:
> > > >
> > > >
> > > >
> > > >>I understood the problem , and I just fixed that
> > > :)
> > > >>
> > > >>if you can get Axis2 source update , then you will
> > > >>be able to get the
> > > >>correct behavior , and you do not need to send the
> > > >>service group id , if
> > > >>you deploy the service in application scope.
> > > >>
> > > >>[EMAIL PROTECTED] wrote:
> > > >>
> > > >>
> > > >>
> > > >>>Hi Deepal,
> > > >>>
> > > >>>first at all, thanks for your reply. Okay, I'll
> > > try
> > > >>>
> > > >>>
> > > >>to
> > > >>
> > > >>
> > > >>>clarify the 'it does not work'. To test this
> > > >>>
> > > >>>
> > > >>scoping
> > > >>
> > > >>
> > > >>>feature for the 0.94 release I used a simple
> > > >>>
> > > >>>
> > > >>Service
> > > >>
> > > >>
> > > >>>which increases an integer value at every call
> > > and
> > > >>>returns this value. After deployment under the
> > > >>>-setting it does not
> > > >>>
> > > >>>
> > > >>work
> > > >>
> > > >>
> > > >>>wich means it returns for every request a '1' but
> > > >>>
> > > >>>
> > > >>it
> > > >>
> > > >>
> > > >>>should be for 3 request '1','2','3'...
> > > >>>The only way to get this behavior is to deploy
> > > the
> > > >>>service with the scope="transport" setting.
> > > >>>
> > > >>>You said that there is a usage of a service group
> > > >>>
> > > >>>
> > > >>ID
> > > >>
> > > >>
> > > >>>for the intern handling of some of this scope
> > > >>>
> > > >>>
> > > >>types.
> > > >>
> > > >>
> > > >>>Does this mean, that I've to deploy my single
> > > >>>Countservice as a service group to get all the
> > > >>>
> > > >>>
> > > >>scoping
> > > >>
> > > >>
> > > >>>features to work?
> > > >>>
> > > >>>Thanks Ted
> > > >>>
> > > >>>--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > > wrote:
> > > >>>
> > > >>>
> > > >>>
> > > >>>Hi Ted;
> > > >>>
> > > >>>what do u mean by that does not work ? , I
> > > >>>
> > > >>>
> > > >>recently
> > > >>
> > > >>
> > > >>>changed scope
> > > >>>handling , and I hope that should work.
> > > >>>
> > > >>>and that work as follows ,
> > > >>>  1. If you deploy a service under the scope
> > > >>>"request" , then there
> > > >>>wont be any sessions management even if you send
> > > >>>
> > > >>>
> > > >>the
> > > >>
> > > >>
> > > >>>service group ID
> > > >>>back (we mange session using ServiceGroup ID)
> > > >>>  2. If you deploy a service in the transport
> > > >>>session scope , then the
> > > >>>there will be session management using transport
> > > >>>cookies and there
> > > >>>will be only one instance of service impl class
> > > >>>
> > > >>>
> > > >>for
> > > >>
> > > >>
> > > >>>that transport
> > > >>>session.
> > > >>> 3. If you deploy a service in scope of SOAP
> > > >>>
> > > >>>
> > > >>session
> > > >>
> > > >>
> > > >>>then you can
> > > >>>manage session using ServiceGroupID , but that
> > > >>>session will be removed
> > > >>>from the system if you did not touch the session
> > > >>>
> > > >>>
> > > >>for
> > > >>
> > > >>
> > > >>>about 30s. (there
> > > >>>will be only one instance of the service impl for
> > > >>>that session)
> > > >>>4. If you deploy service in application scope
> > > then
> > > >>>one can manage a
> > > >>>session using servicegroupID throughout the life
> > > >>>time of the
> > > >>>system.(there will be only one instance of the
> > > >>>service impl for that
> > > >>>session)
> > > >>>
> > > >>>and can you pls clarify what do you mean by it
> > > >>>
> > > >>>
> > > >>does
> > > >>
> > > >>
> > > >>>not work , so that
> > > >>>I can fix that
> > > >>>
> > > >>>[EMAIL PROTECTED] wrote:
> > > >>>
> > > >>>
> > > >>>
> > > Hello,
> > > 
> > > 
> > > try

Generating code with wsdl2code

[Ricardo Blanes]

Hi all

 

    When
I generate code using axis2-0.94 wsdl2code applied to a wsdl that imports an
schema (both of them attached in this mail), the receiver class compiles with
errors, and the methods in the skeleton class has a parameter of type OMElement,
instead of the appropriate type based on schema and wsdl. 

 

    This
is the command I execute:

 

    Wsdl2code
–uri /afolder/ip.wsdl –o /outputfolder/ip –p com.tissat.guide.ip
–ss –d xmlbeans

 

    Is
this a bug? or have I done anything wrong?

 

Thanks, Ricardo Blanes








Nota Legal: Este correo electronico puede contener informacion estrictamente confidencial y es de uso exclusivo del destinatario, quedando prohibida a cualquier otra persona su revelacion, copia, distribucion, o el ejercicio de cualquier accion relativa a su contenido. Si ha recibido este correo electronico por error, por favor, conteste al remitente, y posteriormente proceda a borrarlo de su sistema. Gracias por su colaboracion.
Confidentiality notice: This e-mail message may contain confidential and/or legally privileged information and is solely for the attention and use of the intended recipient. Any disclosure, copying, distribution or the taking of any action with relation to  the contents of this e-mail by any other person is strictly prohibited. If you believe that this e-mail has been mistakenly sent  to you,please reply to the sender from whom you received the message in error and then delete the original e-mail from your system. Thank you for your co-operation. 







ip.wsdl
Description: ip.wsdl


guide_trial.xsd
Description: guide_trial.xsd

Re: Web service receiving a binary file

[fabricio]

Hello Simone, 

I tested the sample too without problems. I created my own web service that
receives the attachment file and calls a program passing it. I created my
client based on the client of the example. But I think that's no problem to
create one by WSDL2Java.

Cheers,

Fabricio.


Citando Simone Bonazzoli <[EMAIL PROTECTED]>:

> i try the attachments sample and it works... now i'm trying do customize the
> sample... but i have a question: anyone has created a wsdl and then use
> wsdl2java to generate the skeleton sources???
> 
> thanks
> Simone
> 
> 2006/2/6, Simone Bonazzoli <[EMAIL PROTECTED]>:
> >
> > when i find a solution i will send an email to the mailing list ok?
> >
> > SImone
> >
> > 2006/2/6, [EMAIL PROTECTED] < [EMAIL PROTECTED]>:
> > >
> > > H,
> > >
> > > I'll take a look in this... I didn't know about this in AXIS.
> > >
> > > Thanks a lot!!
> > >
> > > Simone, would you mind in we share our experiences on it?
> > >
> > > Thanks
> > >
> > >
> > > Citando Simone Bonazzoli <[EMAIL PROTECTED]>:
> > >
> > > > ok, thank you for information i will try it as soon as possible.
> > > >
> > > > Simone
> > > >
> > > > 2006/2/6, German Sakaryan <[EMAIL PROTECTED]>:
> > > > >
> > > > >
> > > > > java, wsdd are there.
> > > > >
> > > > > wsdl ist automatically generated by AXIS.
> > > > >
> > > > > Simone Bonazzoli schrieb:
> > > > > > ok, thanks for informations :)
> > > > > > but the attachments sample is complete of source code, wsdd,wsdl,
> > > xsd ?
> > > > > >
> > > > > > Simone
> > > > > >
> > > > > > 2006/2/6, German Sakaryan < [EMAIL PROTECTED]
> > > > > > >:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > you can transfer not only single files but also directories,
> > > and the
> > > > > > size of the file is less important.
> > > > > >
> > > > > > German Sakaryan
> > > > > >
> > > > > > Simone Bonazzoli schrieb:
> > > > > >  > i will look ... but why is better to use attachments
> > > instead of
> > > > > swa?
> > > > > >  >
> > > > > >  > Simone
> > > > > >  >
> > > > > >  > 2006/2/6, German Sakaryan < [EMAIL PROTECTED]
> > >
> > > > > > 
> > > > > >  >  > > > > > >>:
> > > > > >  >
> > > > > >  > Hi,
> > > > > >  > It is better to use attachments.
> > > > > >  > An example you can find in your axis installation
> > > > > >  >
> > > > > >  > \axis\samples\attachments
> > > > > >  > --
> > > > > >  > German Sakaryan
> > > > > >  >
> > > > > >  >
> > > > > >  >
> > > > > >  >
> > > > > >  > Fabrício schrieb:
> > > > > >  >  > Is it possible to create a web service that receives
> > > a
> > > > > > binary file? I
> > > > > >  >  > want to create a wrapper web service for a program
> > > and
> > > > > > this program
> > > > > >  >  > receives a binary input file. Is it possible to
> > > receive
> > > > > > this file
> > > > > >  > by the
> > > > > >  >  > soap message?
> > > > > >  >  >
> > > > > >  >  >
> > > > > >  >  >
> > > > > >  >  > If it possible… Does anyone have a sample from this
> > > case?
> > > > > >  >  >
> > > > > >  >  >
> > > > > >  >  >
> > > > > >  >  > Cheers.
> > > > > >  >  >
> > > > > >  >
> > > > > >  >
> > > > > >  >
> > > > > >  >
> > > > > >  >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Dr.-Ing. German Sakaryan
> > > > >
> > > > > Computer Science Dept.
> > > > > University of Rostock
> > > > > Tel:  +49 381 498-7585
> > > > > Fax:  +49 381 498-7642
> > > > > E-mail: [EMAIL PROTECTED]
> > > > > Home: http://www.informatik.uni-rostock.de/~gs137
> > > 
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > 
> > > This message was sent using IMP, the Internet Messaging Program.
> > >
> >
> >
> 





This message was sent using IMP, the Internet Messaging Program.

Re: Web service receiving a binary file

[Simone Bonazzoli]

i try the attachments sample and it works... now i'm trying do customize the sample... but i have a question: anyone has created a wsdl and then use wsdl2java to generate the skeleton sources???thanksSimone
2006/2/6, Simone Bonazzoli <[EMAIL PROTECTED]>:
when i find a solution i will send an email to the mailing list ok?SImone2006/2/6, 
[EMAIL PROTECTED] <
[EMAIL PROTECTED]>:
H,I'll take a look in this... I didn't know about this in AXIS.
Thanks a lot!!Simone, would you mind in we share our experiences on it?ThanksCitando Simone Bonazzoli <
[EMAIL PROTECTED]>:> ok, thank you for information i will try it as soon as possible.
>> Simone>> 2006/2/6, German Sakaryan <[EMAIL PROTECTED]
>:> >> >> > java, wsdd are there.
> >> > wsdl ist automatically generated by AXIS.> >> > Simone Bonazzoli schrieb:> > > ok, thanks for informations :)> > > but the attachments sample is complete of source code, wsdd,wsdl, xsd ?
> > >> > > Simone> > >> > > 2006/2/6, German Sakaryan < 
[EMAIL PROTECTED]> > > [EMAIL PROTECTED]>>:> > >> > > Hi,> > >
> > > you can transfer not only single files but also directories, and the
> > > size of the file is less important.> > >> > > German Sakaryan> > >> > > Simone Bonazzoli schrieb:> > >  > i will look ... but why is better to use attachments instead of
> > swa?> > >  >> > >  > Simone> > >  >> > >  > 2006/2/6, German Sakaryan < 
[EMAIL PROTECTED]
> > > [EMAIL PROTECTED]>> > >  > [EMAIL PROTECTED]
> > > [EMAIL PROTECTED]>>>:> > >  >
> > >  > Hi,> > >  > It is better to use attachments.
> > >  > An example you can find in your axis installation> > >  >> > >  > \axis\samples\attachments> > >  > --> > >  > German Sakaryan
> > >  >> > >  >> > >  >> > >  >> > >  > Fabrício schrieb:> > >  >  > Is it possible to create a web service that receives a
> > > binary file? I> > >  >  > want to create a wrapper web service for a program and> > > this program> > >  >  > receives a binary input file. Is it possible to receive
> > > this file> > >  > by the> > >  >  > soap message?> > >  >  >> > >  >  >> > >  >  >
> > >  >  > If it possible… Does anyone have a sample from this case?> > >  >  >> > >  >  >> > >  >  >> > >  >  > Cheers.
> > >  >  >> > >  >> > >  >> > >  >> > >  >> > >  >> > >> > >> > >
> > >> >> >> > --> > Dr.-Ing. German Sakaryan> >> > Computer Science Dept.> > University of Rostock> > Tel:  +49 381 498-7585

> > Fax:  +49 381 498-7642> > E-mail: [EMAIL PROTECTED]> > Home: 
http://www.informatik.uni-rostock.de/~gs137
> >> >> >> >>This message was sent using IMP, the Internet Messaging Program.

Re: [Axis2] application scope

[Ajith Ranabahu]

ps - You seem to use JDK 1.5 !, We've been told about this problem
in JDK 1.5 and still trying to find a solution.
For the build, exclude the perf tests in the  integration module.
(look for the project.xml inside the integration folder and edit the
excludes under build/unittests/excludes)

On 2/8/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Hi Deepal,
>
> sorry to say that, but the build failed even today
> (using maven war). For more detail see attachement,
> maybe this will help you to fix an other bug or giving
> me a hint what i did wrong.
>
> Thank you,
> Ted
> --- Deepal Jayasinghe <[EMAIL PROTECTED]> schrieb:
>
> > Hi Ted;
> >
> > I dont think maven war goal will fail now , there
> > was a bug and we have
> > fixed that , try and see :)
> >
> > [EMAIL PROTECTED] wrote:
> >
> > >Wow, Deepal this was realy one of the quickest
> > replys
> > >I got! So I'll try to build the source but since
> > some
> > >days I've problems to do this successfuly. Can you
> > >please give me a hint to build the *.war without
> > >running into an build failure.
> > >
> > >Thanks a lot
> > >Ted
> > >--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > schrieb:
> > >
> > >
> > >
> > >>I understood the problem , and I just fixed that
> > :)
> > >>
> > >>if you can get Axis2 source update , then you will
> > >>be able to get the
> > >>correct behavior , and you do not need to send the
> > >>service group id , if
> > >>you deploy the service in application scope.
> > >>
> > >>[EMAIL PROTECTED] wrote:
> > >>
> > >>
> > >>
> > >>>Hi Deepal,
> > >>>
> > >>>first at all, thanks for your reply. Okay, I'll
> > try
> > >>>
> > >>>
> > >>to
> > >>
> > >>
> > >>>clarify the 'it does not work'. To test this
> > >>>
> > >>>
> > >>scoping
> > >>
> > >>
> > >>>feature for the 0.94 release I used a simple
> > >>>
> > >>>
> > >>Service
> > >>
> > >>
> > >>>which increases an integer value at every call
> > and
> > >>>returns this value. After deployment under the
> > >>>-setting it does not
> > >>>
> > >>>
> > >>work
> > >>
> > >>
> > >>>wich means it returns for every request a '1' but
> > >>>
> > >>>
> > >>it
> > >>
> > >>
> > >>>should be for 3 request '1','2','3'...
> > >>>The only way to get this behavior is to deploy
> > the
> > >>>service with the scope="transport" setting.
> > >>>
> > >>>You said that there is a usage of a service group
> > >>>
> > >>>
> > >>ID
> > >>
> > >>
> > >>>for the intern handling of some of this scope
> > >>>
> > >>>
> > >>types.
> > >>
> > >>
> > >>>Does this mean, that I've to deploy my single
> > >>>Countservice as a service group to get all the
> > >>>
> > >>>
> > >>scoping
> > >>
> > >>
> > >>>features to work?
> > >>>
> > >>>Thanks Ted
> > >>>
> > >>>--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> > wrote:
> > >>>
> > >>>
> > >>>
> > >>>Hi Ted;
> > >>>
> > >>>what do u mean by that does not work ? , I
> > >>>
> > >>>
> > >>recently
> > >>
> > >>
> > >>>changed scope
> > >>>handling , and I hope that should work.
> > >>>
> > >>>and that work as follows ,
> > >>>  1. If you deploy a service under the scope
> > >>>"request" , then there
> > >>>wont be any sessions management even if you send
> > >>>
> > >>>
> > >>the
> > >>
> > >>
> > >>>service group ID
> > >>>back (we mange session using ServiceGroup ID)
> > >>>  2. If you deploy a service in the transport
> > >>>session scope , then the
> > >>>there will be session management using transport
> > >>>cookies and there
> > >>>will be only one instance of service impl class
> > >>>
> > >>>
> > >>for
> > >>
> > >>
> > >>>that transport
> > >>>session.
> > >>> 3. If you deploy a service in scope of SOAP
> > >>>
> > >>>
> > >>session
> > >>
> > >>
> > >>>then you can
> > >>>manage session using ServiceGroupID , but that
> > >>>session will be removed
> > >>>from the system if you did not touch the session
> > >>>
> > >>>
> > >>for
> > >>
> > >>
> > >>>about 30s. (there
> > >>>will be only one instance of the service impl for
> > >>>that session)
> > >>>4. If you deploy service in application scope
> > then
> > >>>one can manage a
> > >>>session using servicegroupID throughout the life
> > >>>time of the
> > >>>system.(there will be only one instance of the
> > >>>service impl for that
> > >>>session)
> > >>>
> > >>>and can you pls clarify what do you mean by it
> > >>>
> > >>>
> > >>does
> > >>
> > >>
> > >>>not work , so that
> > >>>I can fix that
> > >>>
> > >>>[EMAIL PROTECTED] wrote:
> > >>>
> > >>>
> > >>>
> > Hello,
> > 
> > 
> > trying to deploy some services under the use of
> > 
> > 
> > >>the
> > >>
> > >>
> > attribute scope="application" at the
> > 
> > 
> > >>-tag
> > >>
> > >>
> > >>>in
> > >>>
> > >>>
> > >>>
> > services.xml, I noticed that this setting of the
> > 
> > 
> >
> === message truncated ===
>
>
>
>
>
>
> ___
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
> BUILD FAILED
> File.. C:\Dokumente und 
>

Re: [Axis2] application scope

[donnerdrummel2000-mailing]

Hi Deepal,

sorry to say that, but the build failed even today
(using maven war). For more detail see attachement,
maybe this will help you to fix an other bug or giving
me a hint what i did wrong.

Thank you,
Ted
--- Deepal Jayasinghe <[EMAIL PROTECTED]> schrieb:

> Hi Ted;
> 
> I dont think maven war goal will fail now , there
> was a bug and we have
> fixed that , try and see :)
> 
> [EMAIL PROTECTED] wrote:
> 
> >Wow, Deepal this was realy one of the quickest
> replys
> >I got! So I'll try to build the source but since
> some
> >days I've problems to do this successfuly. Can you
> >please give me a hint to build the *.war without
> >running into an build failure.
> >
> >Thanks a lot
> >Ted
> >--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> schrieb:
> >
> >  
> >
> >>I understood the problem , and I just fixed that
> :)
> >>
> >>if you can get Axis2 source update , then you will
> >>be able to get the
> >>correct behavior , and you do not need to send the
> >>service group id , if
> >>you deploy the service in application scope.
> >>
> >>[EMAIL PROTECTED] wrote:
> >>
> >>
> >>
> >>>Hi Deepal,
> >>>
> >>>first at all, thanks for your reply. Okay, I'll
> try
> >>>  
> >>>
> >>to
> >>
> >>
> >>>clarify the 'it does not work'. To test this
> >>>  
> >>>
> >>scoping
> >>
> >>
> >>>feature for the 0.94 release I used a simple
> >>>  
> >>>
> >>Service
> >>
> >>
> >>>which increases an integer value at every call
> and
> >>>returns this value. After deployment under the
> >>>-setting it does not
> >>>  
> >>>
> >>work
> >>
> >>
> >>>wich means it returns for every request a '1' but
> >>>  
> >>>
> >>it
> >>
> >>
> >>>should be for 3 request '1','2','3'...
> >>>The only way to get this behavior is to deploy
> the
> >>>service with the scope="transport" setting.
> >>>
> >>>You said that there is a usage of a service group
> >>>  
> >>>
> >>ID
> >>
> >>
> >>>for the intern handling of some of this scope
> >>>  
> >>>
> >>types.
> >>
> >>
> >>>Does this mean, that I've to deploy my single
> >>>Countservice as a service group to get all the
> >>>  
> >>>
> >>scoping
> >>
> >>
> >>>features to work?
> >>>
> >>>Thanks Ted
> >>>
> >>>--- Deepal Jayasinghe <[EMAIL PROTECTED]>
> wrote:
> >>>
> >>>  
> >>>
> >>>Hi Ted;
> >>>
> >>>what do u mean by that does not work ? , I
> >>>  
> >>>
> >>recently
> >>
> >>
> >>>changed scope
> >>>handling , and I hope that should work.
> >>>
> >>>and that work as follows ,
> >>>  1. If you deploy a service under the scope
> >>>"request" , then there
> >>>wont be any sessions management even if you send
> >>>  
> >>>
> >>the
> >>
> >>
> >>>service group ID
> >>>back (we mange session using ServiceGroup ID)
> >>>  2. If you deploy a service in the transport
> >>>session scope , then the
> >>>there will be session management using transport
> >>>cookies and there
> >>>will be only one instance of service impl class
> >>>  
> >>>
> >>for
> >>
> >>
> >>>that transport
> >>>session.
> >>> 3. If you deploy a service in scope of SOAP
> >>>  
> >>>
> >>session
> >>
> >>
> >>>then you can
> >>>manage session using ServiceGroupID , but that
> >>>session will be removed
> >>>from the system if you did not touch the session
> >>>  
> >>>
> >>for
> >>
> >>
> >>>about 30s. (there
> >>>will be only one instance of the service impl for
> >>>that session)
> >>>4. If you deploy service in application scope
> then
> >>>one can manage a
> >>>session using servicegroupID throughout the life
> >>>time of the
> >>>system.(there will be only one instance of the
> >>>service impl for that
> >>>session)
> >>>
> >>>and can you pls clarify what do you mean by it
> >>>  
> >>>
> >>does
> >>
> >>
> >>>not work , so that
> >>>I can fix that
> >>>
> >>>[EMAIL PROTECTED] wrote:
> >>>
> >>>  
> >>>
> Hello,
> 
> 
> trying to deploy some services under the use of
> 
> 
> >>the
> >>
> >>
> attribute scope="application" at the
> 
> 
> >>-tag
> >>
> >>
> >>>in
> >>>
> >>>  
> >>>
> services.xml, I noticed that this setting of the
> 
> 
> 
=== message truncated ===






___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.deBUILD FAILED
File.. C:\Dokumente und Einstellungen\t.israel\.maven\cache\maven-multiproje
ct-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [multiproject:install-callback] -- C:\axis2_nightly\module
s\integration\maven.xml:40:38:  Unexpected attribute "xmlns:xalan"
Total time: 12 minutes 10 seconds
Finished at: Wed Feb 08 11:35:24 CET 2006

Re: [Axis2] application scope

[Deepal Jayasinghe]

Hi Ted;

I dont think maven war goal will fail now , there was a bug and we have
fixed that , try and see :)

[EMAIL PROTECTED] wrote:

>Wow, Deepal this was realy one of the quickest replys
>I got! So I'll try to build the source but since some
>days I've problems to do this successfuly. Can you
>please give me a hint to build the *.war without
>running into an build failure.
>
>Thanks a lot
>Ted
>--- Deepal Jayasinghe <[EMAIL PROTECTED]> schrieb:
>
>  
>
>>I understood the problem , and I just fixed that :)
>>
>>if you can get Axis2 source update , then you will
>>be able to get the
>>correct behavior , and you do not need to send the
>>service group id , if
>>you deploy the service in application scope.
>>
>>[EMAIL PROTECTED] wrote:
>>
>>
>>
>>>Hi Deepal,
>>>
>>>first at all, thanks for your reply. Okay, I'll try
>>>  
>>>
>>to
>>
>>
>>>clarify the 'it does not work'. To test this
>>>  
>>>
>>scoping
>>
>>
>>>feature for the 0.94 release I used a simple
>>>  
>>>
>>Service
>>
>>
>>>which increases an integer value at every call and
>>>returns this value. After deployment under the
>>>-setting it does not
>>>  
>>>
>>work
>>
>>
>>>wich means it returns for every request a '1' but
>>>  
>>>
>>it
>>
>>
>>>should be for 3 request '1','2','3'...
>>>The only way to get this behavior is to deploy the
>>>service with the scope="transport" setting.
>>>
>>>You said that there is a usage of a service group
>>>  
>>>
>>ID
>>
>>
>>>for the intern handling of some of this scope
>>>  
>>>
>>types.
>>
>>
>>>Does this mean, that I've to deploy my single
>>>Countservice as a service group to get all the
>>>  
>>>
>>scoping
>>
>>
>>>features to work?
>>>
>>>Thanks Ted
>>>
>>>--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>>>
>>>  
>>>
>>>Hi Ted;
>>>
>>>what do u mean by that does not work ? , I
>>>  
>>>
>>recently
>>
>>
>>>changed scope
>>>handling , and I hope that should work.
>>>
>>>and that work as follows ,
>>>  1. If you deploy a service under the scope
>>>"request" , then there
>>>wont be any sessions management even if you send
>>>  
>>>
>>the
>>
>>
>>>service group ID
>>>back (we mange session using ServiceGroup ID)
>>>  2. If you deploy a service in the transport
>>>session scope , then the
>>>there will be session management using transport
>>>cookies and there
>>>will be only one instance of service impl class
>>>  
>>>
>>for
>>
>>
>>>that transport
>>>session.
>>> 3. If you deploy a service in scope of SOAP
>>>  
>>>
>>session
>>
>>
>>>then you can
>>>manage session using ServiceGroupID , but that
>>>session will be removed
>>>from the system if you did not touch the session
>>>  
>>>
>>for
>>
>>
>>>about 30s. (there
>>>will be only one instance of the service impl for
>>>that session)
>>>4. If you deploy service in application scope then
>>>one can manage a
>>>session using servicegroupID throughout the life
>>>time of the
>>>system.(there will be only one instance of the
>>>service impl for that
>>>session)
>>>
>>>and can you pls clarify what do you mean by it
>>>  
>>>
>>does
>>
>>
>>>not work , so that
>>>I can fix that
>>>
>>>[EMAIL PROTECTED] wrote:
>>>
>>>  
>>>
Hello,


trying to deploy some services under the use of


>>the
>>
>>
attribute scope="application" at the


>>-tag
>>
>>
>>>in
>>>
>>>  
>>>
services.xml, I noticed that this setting of the


>>>scope
>>>
>>>  
>>>
doesn't work in Axis2 0.94. The only correct


>>>working
>>>
>>>  
>>>
scope is the scope="transport". Are there any


>>knows
>>
>>
bugs? I thought that this application scope


>>setting
>>
>>
worked well, using release 0.93...


Thanks Ted


>>>
>>>
>>>
>>>
>>>
>>>  
>>>
>___
>  
>
Telefonate ohne weitere Kosten vom PC zum PC:


>>>http://messenger.yahoo.de
>>>
>>>
>>>--
>>>Thanks,
>>>Deepal
>>>
>>>
>>>  
>>>
>>
>>
>>
>>>~Future is Open~
>>>  
>>>
>>
>>___
>>
>>
>>>Telefonate ohne weitere Kosten vom PC zum PC:
>>>  
>>>
>>http://messenger.yahoo.de
>>
>>
>>
>>-- 
>>Thanks,
>>Deepal
>>
>>
>>
>
>  
>
>>~Future is Open~
>>
>>
>>
>>
>>
>
>
>
>   
>
>   
>   
>___ 
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
>  
>

-- 
Thanks,
Deepal

~Future is Open~ 

Re: [Axis2] application scope

[donnerdrummel2000-mailing]

Wow, Deepal this was realy one of the quickest replys
I got! So I'll try to build the source but since some
days I've problems to do this successfuly. Can you
please give me a hint to build the *.war without
running into an build failure.

Thanks a lot
Ted
--- Deepal Jayasinghe <[EMAIL PROTECTED]> schrieb:

> 
> I understood the problem , and I just fixed that :)
> 
> if you can get Axis2 source update , then you will
> be able to get the
> correct behavior , and you do not need to send the
> service group id , if
> you deploy the service in application scope.
> 
> [EMAIL PROTECTED] wrote:
> 
> >Hi Deepal,
> >
> >first at all, thanks for your reply. Okay, I'll try
> to
> >clarify the 'it does not work'. To test this
> scoping
> >feature for the 0.94 release I used a simple
> Service
> >which increases an integer value at every call and
> >returns this value. After deployment under the
> >-setting it does not
> work
> >wich means it returns for every request a '1' but
> it
> >should be for 3 request '1','2','3'...
> >The only way to get this behavior is to deploy the
> >service with the scope="transport" setting.
> >
> >You said that there is a usage of a service group
> ID
> >for the intern handling of some of this scope
> types.
> >Does this mean, that I've to deploy my single
> >Countservice as a service group to get all the
> scoping
> >features to work?
> >
> >Thanks Ted
> >
> >--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> >
> 
> > Hi Ted;
> >
> > what do u mean by that does not work ? , I
> recently
> > changed scope
> > handling , and I hope that should work.
> >
> > and that work as follows ,
> >   1. If you deploy a service under the scope
> > "request" , then there
> > wont be any sessions management even if you send
> the
> > service group ID
> > back (we mange session using ServiceGroup ID)
> >   2. If you deploy a service in the transport
> > session scope , then the
> > there will be session management using transport
> > cookies and there
> > will be only one instance of service impl class
> for
> > that transport
> > session.
> >  3. If you deploy a service in scope of SOAP
> session
> > then you can
> > manage session using ServiceGroupID , but that
> > session will be removed
> > from the system if you did not touch the session
> for
> > about 30s. (there
> > will be only one instance of the service impl for
> > that session)
> > 4. If you deploy service in application scope then
> > one can manage a
> > session using servicegroupID throughout the life
> > time of the
> > system.(there will be only one instance of the
> > service impl for that
> > session)
> >
> > and can you pls clarify what do you mean by it
> does
> > not work , so that
> > I can fix that
> >
> > [EMAIL PROTECTED] wrote:
> >
> > >Hello,
> >
> > >trying to deploy some services under the use of
> the
> > >attribute scope="application" at the
> -tag
> >
> > in
> >
> > >services.xml, I noticed that this setting of the
> >
> > scope
> >
> > >doesn't work in Axis2 0.94. The only correct
> >
> > working
> >
> > >scope is the scope="transport". Are there any
> knows
> > >bugs? I thought that this application scope
> setting
> > >worked well, using release 0.93...
> >
> > >Thanks Ted
> >
> >
> >
> >
> >
> >
> >
>
___
> >
> > >Telefonate ohne weitere Kosten vom PC zum PC:
> >
> > http://messenger.yahoo.de
> >
> >
> > --
> > Thanks,
> > Deepal
> >
> >
>
>
> >
> > ~Future is Open~
> 
> 
>
>___
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
> 
> 
> 
> -- 
> Thanks,
> Deepal
>

> ~Future is Open~
> 
> 
> 







___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

Re: [Axis2] application scope

[Deepal Jayasinghe]

I understood the problem , and I just fixed that :)

if you can get Axis2 source update , then you will be able to get the
correct behavior , and you do not need to send the service group id , if
you deploy the service in application scope.

[EMAIL PROTECTED] wrote:

>Hi Deepal,
>
>first at all, thanks for your reply. Okay, I'll try to
>clarify the 'it does not work'. To test this scoping
>feature for the 0.94 release I used a simple Service
>which increases an integer value at every call and
>returns this value. After deployment under the
>-setting it does not work
>wich means it returns for every request a '1' but it
>should be for 3 request '1','2','3'...
>The only way to get this behavior is to deploy the
>service with the scope="transport" setting.
>
>You said that there is a usage of a service group ID
>for the intern handling of some of this scope types.
>Does this mean, that I've to deploy my single
>Countservice as a service group to get all the scoping
>features to work?
>
>Thanks Ted
>
>--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>

> Hi Ted;
>
> what do u mean by that does not work ? , I recently
> changed scope
> handling , and I hope that should work.
>
> and that work as follows ,
>   1. If you deploy a service under the scope
> "request" , then there
> wont be any sessions management even if you send the
> service group ID
> back (we mange session using ServiceGroup ID)
>   2. If you deploy a service in the transport
> session scope , then the
> there will be session management using transport
> cookies and there
> will be only one instance of service impl class for
> that transport
> session.
>  3. If you deploy a service in scope of SOAP session
> then you can
> manage session using ServiceGroupID , but that
> session will be removed
> from the system if you did not touch the session for
> about 30s. (there
> will be only one instance of the service impl for
> that session)
> 4. If you deploy service in application scope then
> one can manage a
> session using servicegroupID throughout the life
> time of the
> system.(there will be only one instance of the
> service impl for that
> session)
>
> and can you pls clarify what do you mean by it does
> not work , so that
> I can fix that
>
> [EMAIL PROTECTED] wrote:
>
> >Hello,
>
> >trying to deploy some services under the use of the
> >attribute scope="application" at the -tag
>
> in
>
> >services.xml, I noticed that this setting of the
>
> scope
>
> >doesn't work in Axis2 0.94. The only correct
>
> working
>
> >scope is the scope="transport". Are there any knows
> >bugs? I thought that this application scope setting
> >worked well, using release 0.93...
>
> >Thanks Ted
>
>
>
>
>
>
> ___
>
> >Telefonate ohne weitere Kosten vom PC zum PC:
>
> http://messenger.yahoo.de
>
>
> --
> Thanks,
> Deepal
>
> >
>
> ~Future is Open~


>___
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de



-- 
Thanks,
Deepal

~Future is Open~

nullpointerexception: org.apache.axis.SOAPPart.writeTo(SOAPPart.java:324)

[Henrik Troeng]

Hello, I get a NullPointerException sometimes, when I print my soap messages to log file.I use a class that extends the BasicHandler, and just writes the data to a file on the filesystem. The OutputStream is synchronized, and the traffic to the log-writer is quite heavy (writing approx 50 mb logfiles each day).The files are rotated when they grow to 3 mb.  Here are the wsdd-parameters:            Here is the exception:java.lang.NullPointerException at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:324) at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269) at org.apache.axis.Message.writeTo(Message.java:519) at com.abc.ss.AxisLogHandler.invoke(AxisLogHandler.java:40) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:249) at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Unknown Source) Does anyone have a clue what could cause this? Thanks in advanceHenrik

Re: [Axis2] application scope

[donnerdrummel2000-mailing]

Hi Deepal,

first at all, thanks for your reply. Okay, I'll try to
clarify the 'it does not work'. To test this scoping
feature for the 0.94 release I used a simple Service
which increases an integer value at every call and
returns this value. After deployment under the
-setting it does not work
wich means it returns for every request a '1' but it
should be for 3 request '1','2','3'...
The only way to get this behavior is to deploy the
service with the scope="transport" setting.

You said that there is a usage of a service group ID
for the intern handling of some of this scope types.
Does this mean, that I've to deploy my single
Countservice as a service group to get all the scoping
features to work?

Thanks Ted

--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>  
> Hi Ted;
> 
> what do u mean by that does not work ? , I recently
> changed scope
> handling , and I hope that should work.
> 
> and that work as follows ,
>   1. If you deploy a service under the scope
> "request" , then there
> wont be any sessions management even if you send the
> service group ID
> back (we mange session using ServiceGroup ID)
>   2. If you deploy a service in the transport
> session scope , then the
> there will be session management using transport
> cookies and there
> will be only one instance of service impl class for
> that transport
> session.
>  3. If you deploy a service in scope of SOAP session
> then you can
> manage session using ServiceGroupID , but that
> session will be removed
> from the system if you did not touch the session for
> about 30s. (there
> will be only one instance of the service impl for
> that session)
> 4. If you deploy service in application scope then
> one can manage a
> session using servicegroupID throughout the life
> time of the
> system.(there will be only one instance of the
> service impl for that
> session)
> 
> and can you pls clarify what do you mean by it does
> not work , so that
> I can fix that
> 
> [EMAIL PROTECTED] wrote:
> 
> >Hello,
> >
> >trying to deploy some services under the use of the
> >attribute scope="application" at the -tag
> in
> >services.xml, I noticed that this setting of the
> scope
> >doesn't work in Axis2 0.94. The only correct
> working
> >scope is the scope="transport". Are there any knows
> >bugs? I thought that this application scope setting
> >worked well, using release 0.93...
> >
> >Thanks Ted
> >
> >
> >
> >
> >
> >
>
>___
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
> >
> >
> 
> - --
> Thanks,
> Deepal
>

> ~Future is Open~
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird -
> http://enigmail.mozdev.org
>  
>
iD8DBQFD6Z/ajOGcXNDx0CARAnxlAJ9QWwpSlj7guWeZnwvpCrCjulPJDQCfTC6c
> T47YjD9rTeMWqwUQrT/IhG8=
> =XjMa
> -END PGP SIGNATURE-
> 
> 
> 







___ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de