Re: Error merging include schema

[Anne Thomas Manes]

Muralidaran,

Please ask these types of questions on the axis-user list rather than
the axis-dev list.

I suspect your problem is caused by the fact that you have a number of
schemas that do not specify targetNamespaces, and that you import
these schemas without specifying a namespace. I believe that the
namespace attribute is required on an import.

You could try adding namespace="" to the import declaration, or change
the import to include.

My guess is that the testing tools you use can't handle this situation.

Anne

On Thu, May 29, 2008 at 1:58 PM, cmurali <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
> Our Axis2 1.3 based web service is in IVV (independent Validation and
> verification) and hence would appreciate your quick help.
>
> When I query my web service wsdl using SOAPUI, it queries fine and generates
> a sample request fine. But when I used another client tool called soapSonar,
> I received the subject error and it is shown in the attached word document.
> I also attached all my schemas and wsdl.
>
> Another issue is that when IVV ran the WS-I compliance check by downloading
> the web service interoperability tool from
> http://www.ws-i.org/deliverables/, it failed in many aspects, they reported.
> I am yet to receive the report from them.
>
> Any quick help will be much appreciated.
>
> Thanks,
> Muralidaran Chakravarthy
>
> http://www.nabble.com/file/p17542178/AllXSDandWsdl.zip AllXSDandWsdl.zip
> http://www.nabble.com/file/p17542178/soapsonarUI.doc soapsonarUI.doc
>
> --
> View this message in context: 
> http://www.nabble.com/Error-merging-include-schema-tp17542178p17542178.html
> Sent from the Axis - Dev mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: FW: Why this wsdl is not valid Wsdl

[Anne Thomas Manes]

Change:

  

to:

  

Anne

On Tue, Apr 1, 2008 at 10:16 AM, Dayalan, Ravikumar <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>  -Original Message-
> From:   Dayalan, Ravikumar
> Sent:   Tuesday, April 01, 2008 7:45 PM
> To: 'axis-dev@ws.apache.org'
> Subject:Why this wsdl is not valid Wsdl
>
>
> When I try this wsdl and try to validate (I Use eclipse) it always gives
> this error.
> IWAB0380E Errors were encountered while validating XML schemas. XSD: The
> target namespace 'http://MedicalMitchel/interfaces/IMedMitPOC' of the
> resolved schema conflicts with '' XSD: Element reference '#MMFILE' is
> unresolved
>
> Can you please help me in understanding where iam wrong in this WSDL
>
> Whereis the otherwsdl is working fine.. <>
>
> Here I have  has 
> Will this be the reason.. Since this wsdl is given by some other team I
> don't have much control over changing it.
> Any help will be highly appreciated.
>
> Thanks
> Ravi.
>  <> <>
> =
> The information in this transmission is intended for official use only and
> may contain information from NJM Insurance Group that is privileged,
> confidential and exempt from disclosure under applicable law. It is intended
> for the exclusive use of the persons or entities to which it is addressed.
> If you are not an intended recipient or the employee or agent responsible
> for delivering this transmission to an intended recipient, be aware that any
> disclosure, dissemination, distribution or copying of this communication, or
> the use of its contents, is strictly prohibited. If you received this
> transmission in error, please notify the sender by return e-mail and delete
> the material from any computer.
> =
> -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>

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

Re: MTOM Communication with .NET

[Anne Thomas Manes]

All web services created using .NET have an associated WSDL. You can
obtain the WSDL from the .NET service by appending "?wsdl" to the
service endpoint URL. e.g., if the endpoint URL is
"http://www.example.org/service.asmx";, you can get the WSDL from
"http://www.example.org/service.asmx?wsdl";.

Anne

On Thu, Mar 6, 2008 at 1:30 PM, WJ Krpelan <[EMAIL PROTECTED]> wrote:
> Hi,
>  in .net the corresponding program is wsdl.exe
>  I'm very interested whether MTOM-communications is
>  interoperable so pls tell us your experiences.
>  Cheers,
>  Wolfgang
>
>
>
>
>  --- Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
>
>  > Hi,
>  > > > Now, I'm trying to create an application to talk
>  > to a .NET web service and
>  > > since .NET doesn't use WSDL, i cannot generate the
>  > required files necessary
>  > > to do the bindings.
>  > Are you sure??... AFAIK .net use WSDL... According
>  > to following (which
>  > I found just now) .net even supports contract first
>  > development..
>  >
>  http://msdn2.microsoft.com/en-us/magazine/cc163800.aspx
>  >
>  > Wat exactly is your use case.. ??
>  >
>  > thanks,
>  > Thilina
>  > > >
>  > > > Does anyone know how to talk to a .NET
>  > application with MTOM using Java ?
>  > > >
>  > > > Thanks,
>  > > >
>  > > >
>  > >
>  > >
>  >
>  >
>  >
>  > --
>  > Thilina Gunarathne  - http://thilinag.blogspot.com
>  >
>  >
>  -
>  > To unsubscribe, e-mail:
>  > [EMAIL PROTECTED]
>  > For additional commands, e-mail:
>  > [EMAIL PROTECTED]
>  >
>  >
>
>
>
>
>   
> 
>  Looking for last minute shopping deals?
>  Find them fast with Yahoo! Search.  
> http://tools.search.yahoo.com/newsearch/category.php?category=shopping
>
>
>
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: Interopertability issues with Axis2 ADB and .NET client

[Anne Thomas Manes]

You'll also get better results if you adopt a WSDL-first development model.

Anne

On Feb 6, 2008 7:30 PM, keith chapman <[EMAIL PROTECTED]> wrote:
> AFAIK some fixes went in after 1.3 (Mainly on security related stuff).
> So its advisable to use the SNAPSHOT build.
>
> Thanks,
> Keith.
>
>
> On Feb 6, 2008 8:13 PM, Charitha Kankanamge <[EMAIL PROTECTED]> wrote:
> > Hi Rick,
> >
> > AFAIK there wouldn't be any issues with .NET interoperability. A few
> > months ago we did interop tests against .NET stack and most of the
> > scenarios were successful. If you use Axis2-1.3 or the latest SNAPSHOT,
> > .NET client/server should interoperate properly.
> >
> > regards
> > Charitha
> >
> >
> > ricko xavier wrote:
> >
> > > Hello,
> > >
> > > I have Axis2 WS Stack run on JBOSS server using axis2 default binding
> > > ADB. The client is .NET. Will there be any interoperatibilty issues???
> > >
> > > Also, vice-versa if my client uses Axis2 ADB and .NET WS stack will
> > > there be any issues ?? Any replies are appreicated ???
> > >
> > > Rick
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> Keith Chapman
> Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: [Axis2] Soap Encoding support with ADB

[Anne Thomas Manes]

Amila,

SOAP encoding is much more likely to be used in a code-first scenario,
but you must make sure that it also works in a WSDL-first scenario.

Regarding one of your questions, you would never see an element
defined as follows:


> 
> 
> 
> 
> 
> 
> 

First off, you would define a named complexType rather than an
element. And second, you never define an element simply as
soapenc:Array. The ComplexType would look something like this:

  
 
  
  
 
  


   
  
 
  
   


Or even more likely, you wouldn't define the "TestSoapType2" type --
you would simply reference the child types in the WSDL message
description:


   
   


You might find this article helpful:
http://www.developer.com/services/article.php/10928_1602051_3

You also might spend a little time playing with Axis generating some
RPC/encoded services to get a better sense of how the environment
works.

Anne

On Jan 3, 2008 1:51 AM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
> hi tom,
>
> I went through the Axis user guide[1] and as I understood Axis 1.x has used
> soap encoding in the
> code first approach to support Arrays. I think this is where both you and
> glen has misunderstood.
>
> in that case if I have a class like this
>
> public class Test {
>  private int[] testArray;
> public void setTestArray(int[] param){
>  testArray = param;
> }
>
> public int[] getTestArray(){
> return testArray;
> }
>
> }
>
> in this case as Axis 1.x has done users must be given the chance to deal
> with the standard types and it is
> almost useless to ask to deal with a new type. Further as I guess it uses
> org.apache.axis.providers.java.RPCProvider as in Axis2 RPCMessageReceiver.
> BTW one question. Why Axis 1.x use soap encoding for this? why it simply
> generate something
> like this
> 
> it is always better to use POX rather than encoding types isn't it?
>
> So we won't be able to use the Axis 1.x code for this.
>
> But In the contract first approach people always have to deal with the
> generated classes. So I believe in this
> case I don't think it is a problem. Here the main idea is to access a
> service already deployed with soap:encoding.
>
> So it would only be used at client side.
>
> [1]
> http://ws.apache.org/axis/java/user-guide.html#ConsumingWebServicesWithAxis
>
> thanks,
> Amila.
>
>
>
> On Jan 3, 2008 10:53 AM, Amila Suriarachchi <[EMAIL PROTECTED]>
> wrote:
> > hi tom,
> > thanks you your reply. if you have already working with axis 1.x could you
> please help on answering these
> > questions?
> >
> >
> >
> > On Jan 3, 2008 4:06 AM, Tom Jordahl < [EMAIL PROTECTED]> wrote:
> >
> > > +1 on Glen's -1 of using a whole new set of types to support SOAP
> > > encoding.  A String must map to a soapenc:string and a Array[] must map
> > > to a SOAP encoded array.
> >
> >
> > In axis 1.x is it use in code first or contract first (i.e. wsdl2java)
> approach? Here what I am trying to do is to
> > use it with the wsdl2java tool. i.e with the contract first approach.
> >
> > So the main question is what is the generated method signature for
> >
> > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> >
> > this type of element. what is the type of param2 in Axis 1.x? Here in code
> generation
> > time I do not know the type of the array. That is why I set it as a new
> type letting users to define it.
> >
> >
> >
> > >
> > >
> > > I would also argue for "full" multiref support, as servers will be
> > > sending this back to Axis2 clients, right?
> >
> >
> > I agree. I'll add this feature as I have describe earlier.
> >
> >
> > >
> > >
> > > Amila, please feel free to use the Axis 1.x code base as a reference for
> > > how to do any of this.  Please also feel free to NOT to duplicate the
> > > Array serialization/deserialization bugs. :-)
> >
> >
> > For the moment in Axis 2 ADB is also in a very stable state.  so using
> already existing ADB logic
> > won't give any serializing de serializing issues.
> >
> > Thanks,
> > Amila.
> >
> >
> >
> >
> > >
> > >
> > > --
> > > Tom Jordahl
> > > Axis 1.x guy
> > >
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Glen Daniels [mailto:[EMAIL PROTECTED] ]
> > > Sent: Friday, December 28, 2007 1:49 AM
> > > To: axis-dev@ws.apache.org
> > > Subject: Re: [Axis2] Soap Encoding support with ADB
> > >
> > > Hey Amila:
> > >
> > > > won't need them.  But for SOAP 1.1, the situation is different.
> > > The
> > > > encoding spec says you MUST encode all complex object types as
> > > top-level
> > > > members of the serialization.  Therefore ALL conforming SOAP 1.1
> > > > encoding implementations will be putting out stuff that looks like
> > > this:
> > > >
> > > > 
> > > >   
> > > > 
> > > >   
> > > >   
> > > > the real argument
> > > > blue
> > >

Re: [Axis2] Release plan and road map for Axis2 1.4 release

[Anne Thomas Manes]

There are no standard tests for a product, only for the WSDLs and SOAP
messages generated by the product. Axis2 frequently generates
non-compliant WSDLs -- e.g., a service with multiple operations with
non-unique signatures, where the signature is defined as the qname of
the child element of the SOAP Body. If we properly supported wrapped
document/literal, then it's very likely that would resolve the WS-I
non-compliance issues.

It would be useful to have a switch that requests WS-I compliance,
which would then automatically generate wrapped style.

Anne

On Dec 24, 2007 1:21 AM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 22, 2007 7:49 PM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > I'd like to see a WS-I BP 1.1 compliance option added.
>
> Axis2 do have most of the Basic profile  features.  Do we have to run any
> standard test suite to claim the
> compliance? I mean for  JAXWS we have to pass the SUNs' TCK.
>
> Amila.
>
>
> >
> >
> > Anne
> >
> >
> >
> >
> > On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> > > Hi Devs and Users,
> > >
> > > I saw a number of users asking about the next release of Axis2 , so I
> > > think its good time to think about that. We did our last release on
> > > August , looking at the mailing list and JIRA I can assume that the
> > > release is very stable release.  However in the meantime we have few
> > > items that we need to implement that we discussed over the mailing list
> > > for the next release. And there are a few bug fixes and new features
> > > that users have ask about , so taking all those into account how about
> > > doing a release on end of February ?
> > >
> > > So in the release I would like to see following list of items
> > >  - Support for RPC-Encoded
> > >  - Full support for JAX-WS
> > >  - Enhance NIO transport support
> > > -  Discuss and implement dynamic phase rule support
> > >  - Fix the issues we found at MS PlugFest
> > >  - Anything else .   ??
> > >
> > > In addition to that we need to identify the issues that we are going to
> > > fix in next release , for that I would like ask Axis2 users to go and
> > > create a JIRA or change the priority of JIRA if they want some issues or
> > > features (s)he like to see in next release. In the meantime if someone
> > > think to fix some particular issue for next release then please go and
> > > mark the issue as blocker. But please do not just mark issue as blocker
> > > provide some useful information specifying what do you think its is
> > > important.
> > >
> > > So let's target Axis2 1.4 on end of February , and here is my +1 for the
> > > release.
> > >
> > > -Deepal
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.

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

Re: [Axis2] Release plan and road map for Axis2 1.4 release

[Anne Thomas Manes]

I'd like to see a WS-I BP 1.1 compliance option added.

Anne

On Dec 19, 2007 12:02 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Devs and Users,
>
> I saw a number of users asking about the next release of Axis2 , so I
> think its good time to think about that. We did our last release on
> August , looking at the mailing list and JIRA I can assume that the
> release is very stable release.  However in the meantime we have few
> items that we need to implement that we discussed over the mailing list
> for the next release. And there are a few bug fixes and new features
> that users have ask about , so taking all those into account how about
> doing a release on end of February ?
>
> So in the release I would like to see following list of items
>  - Support for RPC-Encoded
>  - Full support for JAX-WS
>  - Enhance NIO transport support
> -  Discuss and implement dynamic phase rule support
>  - Fix the issues we found at MS PlugFest
>  - Anything else .   ??
>
> In addition to that we need to identify the issues that we are going to
> fix in next release , for that I would like ask Axis2 users to go and
> create a JIRA or change the priority of JIRA if they want some issues or
> features (s)he like to see in next release. In the meantime if someone
> think to fix some particular issue for next release then please go and
> mark the issue as blocker. But please do not just mark issue as blocker
> provide some useful information specifying what do you think its is
> important.
>
> So let's target Axis2 1.4 on end of February , and here is my +1 for the
> release.
>
> -Deepal
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: Namespace problem of Array element.

[Anne Thomas Manes]

As I said, I think it must be something wrong in your implementation.
Please start from a clean slate by generating code from your WSDL
file.

Anne

On Nov 27, 2007 9:28 AM, Terry Zhou <[EMAIL PROTECTED]> wrote:
> Thanks Anne for your reply!
>
>  I have two question about you answer:
> 1.The same WSDL why axis2 behavior differs with Axis 1.4?
> 2.If it's qualified why not use " http://math.samples"; as its namespace
> instead of empty?
>
> Regards,
> Terry
>
>
>
> On Nov 27, 2007 10:23 PM, Anne Thomas Manes <[EMAIL PROTECTED] > wrote:
> >
> >
> >
> > You schema definition specifies elementFormDefault="qualified"
> > therefore Axis should qualify the "item" elements. Axis normally
> > handles this just fine, so I assume there's a problem in the way you
> > implemented your service. I suggest you start over by running
> > wsdl2java.
> >
> > Anne
> >
> >
> >
> >
> > On Nov 27, 2007 9:10 AM, Terry Zhou <[EMAIL PROTECTED]> wrote:
> > > Sorry, Anne, I just think this maybe an issue of Axis 1.4, developer may
> > > know more about it.
> > >
> > > Thanks,
> > > Terry
> > >
> > >
> > >
> > > On Nov 27, 2007 10:02 PM, Anne Thomas Manes < [EMAIL PROTECTED] > wrote:
> > > >
> > > >
> > > >
> > > > Please send questions related to using Axis and Axis2 to the axis-user
> > > > list. The axis-dev list is for issues related to developing the Axis
> > > > and Axis2 frameworks themselves.
> > > >
> > > > Anne
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 5:31 AM, Terry Zhou < [EMAIL PROTECTED]> wrote:
> > > > > Hi, all
> > > > >
> > > > > Is there any configuration to prevent the empty namespace
> generatation
> > > of
> > > > > array element for Axis1.4 when use basic type array with
> > > document/literal
> > > > > style? For example,
> > > > > The client soap request message is:
> > > > >
> > > > >  > > xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/ ">
> > > > >
> > > > >   http://quickstart.samples/xsd";>
> > > > >  1
> > > > >  2
> > > > >  5
> > > > >  8
> > > > >  99
> > > > >   
> > > > >
> > > > > 
> > > > >
> > > > >
> > > > > and axis serve side response:
> > > > >
> > > > > http://schemas.xmlsoap.org/soap/envelope/";
> > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema "
> > > > > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";>
> > > > >
> > > > >   http://math.samples";>
> > > > >  1
> > > > >  2
> > > > >  5
> > > > >  8
> > > > >  99
> > > > >   
> > > > >
> > > > > 
> > > > >
> > > > > This won't interop with some web service client for the element
> 
> > > has a
> > > > > empty namespace instead of the default one(" http://math.samples ").
> I
> > > have
> > > > > also tested with Axis2-1.3, it responses OK with the following
> message:
> > > > >
> > > > > http://schemas.xmlsoap.org/soap/envelope/";>
> > > > >
> > > > >   http://quickstart.samples/xsd
> > > ">
> > > > >   1
> > > > >  2
> > > > >  5
> > > > >  8
> > > > >  99
> > > > >   
> > > > >
> > > > > 
> > > > >
> > > > > So for Axis 1.4, is there any configuration to make the namespace of
> > > element
> > > > >  right? Thanks a lot!
> > > > >
> > > > > Terry
> > > > >
> > > > >
> > > > > FYI, WSDL file for the web service.
> > > > > 
> > > > >  > > > >  targetNamespace="http://math.samples/"; xmlns:apachesoap="
> > &g

Re: Namespace problem of Array element.

[Anne Thomas Manes]

You schema definition specifies elementFormDefault="qualified"
therefore Axis should qualify the "item" elements. Axis normally
handles this just fine, so I assume there's a problem in the way you
implemented your service. I suggest you start over by running
wsdl2java.

Anne

On Nov 27, 2007 9:10 AM, Terry Zhou <[EMAIL PROTECTED]> wrote:
> Sorry, Anne, I just think this maybe an issue of Axis 1.4, developer may
> know more about it.
>
> Thanks,
> Terry
>
>
>
> On Nov 27, 2007 10:02 PM, Anne Thomas Manes < [EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Please send questions related to using Axis and Axis2 to the axis-user
> > list. The axis-dev list is for issues related to developing the Axis
> > and Axis2 frameworks themselves.
> >
> > Anne
> >
> >
> >
> >
> > On Nov 27, 2007 5:31 AM, Terry Zhou < [EMAIL PROTECTED]> wrote:
> > > Hi, all
> > >
> > > Is there any configuration to prevent the empty namespace generatation
> of
> > > array element for Axis1.4 when use basic type array with
> document/literal
> > > style? For example,
> > > The client soap request message is:
> > >
> > >  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ ">
> > >
> > >   http://quickstart.samples/xsd";>
> > >  1
> > >  2
> > >  5
> > >  8
> > >  99
> > >   
> > >
> > > 
> > >
> > >
> > > and axis serve side response:
> > >
> > > http://schemas.xmlsoap.org/soap/envelope/";
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema "
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > >
> > >   http://math.samples";>
> > >  1
> > >  2
> > >  5
> > >  8
> > >  99
> > >   
> > >
> > > 
> > >
> > > This won't interop with some web service client for the element 
> has a
> > > empty namespace instead of the default one(" http://math.samples "). I
> have
> > > also tested with Axis2-1.3, it responses OK with the following message:
> > >
> > > http://schemas.xmlsoap.org/soap/envelope/";>
> > >
> > >   http://quickstart.samples/xsd
> ">
> > >   1
> > >  2
> > >  5
> > >  8
> > >  99
> > >   
> > >
> > > 
> > >
> > > So for Axis 1.4, is there any configuration to make the namespace of
> element
> > >  right? Thanks a lot!
> > >
> > > Terry
> > >
> > >
> > > FYI, WSDL file for the web service.
> > > 
> > >  > >  targetNamespace="http://math.samples/"; xmlns:apachesoap="
> > > http://xml.apache.org/xml-soap " xmlns:impl="http://math.samples/";
> > > xmlns:intf="http://math.samples/"; xmlns:tns1="
> > > http://math.samples"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd=
> > > "http://www.w3.org/2001/XMLSchema ">
> > > 
> > >
> > >  
> > >   > > targetNamespace="http://math.samples"; xmlns=
> > > "http://www.w3.org/2001/XMLSchema";>
> > >   > > "a">
> > >  
> > >  
> > >   > > ="unbounded" minOccurs="0" name=
> > > "item" type="xsd:int"/>
> > >  
> > >
> > >
> > >  
> > >  
> > >  
> > >   > >  elementFormDefault="qualified" targetNamespace="
> > > http://math.samples/"; xmlns="http://www.w3.org/2001/XMLSchema";>
> > >  <
> > > element name="echoIntArrayReturn">
> > >  
> > >  <
> > > sequence>
> > >   > > minOccurs="0" name="item" type=
> > > "xsd:int"/>
> > >  
> > >
> > >  
> > >   > > element>
> > >  
> > >  
> > >
> > >   > > "echoIntArrayResponse">
> > >
> > >   > > name="echoIntArrayReturn"/>
> > >
> > >  
> > >
> > >
> > >  
> > >
> > >  <
> > > wsdl:part element="tns1:a" name="a"
> > > />
> > >
> > >  
> > >
> > >   > > >
> > >
> > >   > > ="a">
> > >
> > >   > > name="echoIntArrayRequest"/>
> > >
> > >  <
> > > wsdl:output message="impl:echoIntArrayResponse"
> name="echoIntArrayResponse"
> > > />
> > >
> > >  
> > >
> > >  
> > >
> > >   > >  name="MathSoapBinding" type="impl:Math">
> > >
> > >
> > >   > > " http://schemas.xmlsoap.org/soap/http"/>
> > >
> > >   > >  name="echoIntArray">
> > >
> > >   > > ""/>
> > >
> > >   > > >
> > >
> > >  
> > >
> > >
> > >  
> > >
> > >   > > >
> > >
> > >  
> > >
> > >
> > >  
> > >
> > >  
> > >
> > >  
> > >
> > >  <
> > > wsdl:service name="MathService">
> > >
> > >   > >  binding="impl:MathSoapBinding" name="Math">
> > >
> > >  <
> > > wsdlsoap:address location="http://localhost:8080/axis/services/Math "
> > > />
> > >
> > >  
> > >
> > >  
> > >
> > > 
> > >
> > >
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>

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

Re: Namespace problem of Array element.

[Anne Thomas Manes]

Please send questions related to using Axis and Axis2 to the axis-user
list. The axis-dev list is for issues related to developing the Axis
and Axis2 frameworks themselves.

Anne

On Nov 27, 2007 5:31 AM, Terry Zhou <[EMAIL PROTECTED]> wrote:
> Hi, all
>
> Is there any configuration to prevent the empty namespace generatation of
> array element for Axis1.4 when use basic type array with document/literal
> style? For example,
> The client soap request message is:
>
> http://schemas.xmlsoap.org/soap/envelope/";>
>
>   http://quickstart.samples/xsd";>
>  1
>  2
>  5
>  8
>  99
>   
>
> 
>
>
> and axis serve side response:
>
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>   http://math.samples";>
>  1
>  2
>  5
>  8
>  99
>   
>
> 
>
> This won't interop with some web service client for the element  has a
> empty namespace instead of the default one(" http://math.samples";). I have
> also tested with Axis2-1.3, it responses OK with the following message:
>
> http://schemas.xmlsoap.org/soap/envelope/";>
>
>   http://quickstart.samples/xsd";>
>   1
>  2
>  5
>  8
>  99
>   
>
> 
>
> So for Axis 1.4, is there any configuration to make the namespace of element
>  right? Thanks a lot!
>
> Terry
>
>
> FYI, WSDL file for the web service.
> 
>   targetNamespace="http://math.samples/"; xmlns:apachesoap="
> http://xml.apache.org/xml-soap"; xmlns:impl="http://math.samples/";
> xmlns:intf="http://math.samples/"; xmlns:tns1="
> http://math.samples"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd=
> "http://www.w3.org/2001/XMLSchema";>
> 
>
>  
>   targetNamespace="http://math.samples"; xmlns=
> "http://www.w3.org/2001/XMLSchema";>
>   "a">
>  
>  
>   ="unbounded" minOccurs="0" name=
> "item" type="xsd:int"/>
>  
>
>
>  
>  
>  
>elementFormDefault="qualified" targetNamespace="
> http://math.samples/"; xmlns="http://www.w3.org/2001/XMLSchema";>
>  <
> element name="echoIntArrayReturn">
>  
>  <
> sequence>
>   minOccurs="0" name="item" type=
> "xsd:int"/>
>  
>
>  
>   element>
>  
>  
>
>   "echoIntArrayResponse">
>
>   name="echoIntArrayReturn"/>
>
>  
>
>
>  
>
>  <
> wsdl:part element="tns1:a" name="a"
> />
>
>  
>
>   >
>
>   ="a">
>
>   name="echoIntArrayRequest"/>
>
>  <
> wsdl:output message="impl:echoIntArrayResponse" name="echoIntArrayResponse"
> />
>
>  
>
>  
>
>name="MathSoapBinding" type="impl:Math">
>
>
>   "http://schemas.xmlsoap.org/soap/http"/>
>
>name="echoIntArray">
>
>   ""/>
>
>   >
>
>  
>
>
>  
>
>   >
>
>  
>
>
>  
>
>  
>
>  
>
>  <
> wsdl:service name="MathService">
>
>binding="impl:MathSoapBinding" name="Math">
>
>  <
> wsdlsoap:address location="http://localhost:8080/axis/services/Math";
> />
>
>  
>
>  
>
> 
>
>
>
>

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

Re: axis 1.4 and Basic Profile

[Anne Thomas Manes]

Kumar,

You can implement WS-I BP 1.1 compliant service endpoints using Axis
1.4. Axis 1.4 processes SOAP messages in accordance with the profile.

Anne

On Nov 16, 2007 2:27 AM, Iyengar, Kumar <[EMAIL PROTECTED]> wrote:
> Hi Lawrence,
>
> I do mean WS-I Basic Profile. If I understand correctly Basic Profile
> 1.1 has WSDL and SOAP compliance. I understand and agree with you on the
> WSDL compliance part. However, for SOAP we entirely depend on Axis and
> so the compliance for SOAP part of Basic Profile 1.1 has to come from
> Axis 1.x. I wanted to find out if Axis 1.4 is WS-I Basic Profile 1.1
> compliant.
>
> We are currently using Axis 1.2 and that is not BP 1.1 compliant (but it
> is BP 1.0 compliant).
>
> Axis2 is considered BP 1.1 compliant but I am having problems
> integrating with that.
>
> Thanks,
>
> --kumar
>
> -Original Message-
> From: Lawrence Mandel [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 15, 2007 7:53 PM
> To: axis-dev@ws.apache.org
>
> Subject: Re: axis 1.4 and Basic Profile
>
> Hi Kumar,
>
> By basic profile I'm assuming you mean the WS-I basic profile. I don't
> think you can label a runtime as WS-I compliant as there are many things
>
> that you can do with Web services that are not recommended by the WS-I -
>
> that's why there is a WS-I - such as rpc encoded services and importing
> schemas in a WSDL document with the wsdl:import element. The real
> question
> when it comes to WS-I compliance is "is service X WS-I compliant"? If
> the
> service description and implementation follows the WS-I recommendations
> than it is compliant. Note that even if service X is compliant, service
> Y,
> which is deployed to the same runtime (Axis or otherwise), can be
> non-compliant.
>
> Lawrence
>
>
>
>
> "Iyengar, Kumar" <[EMAIL PROTECTED]>
> 11/15/2007 08:45 PM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> 
> cc
>
> Subject
> axis 1.4 and Basic Profile
>
>
>
>
>
>
> Hi all,
>
> Does anyone know if Axis1.4 is Basic Profile 1.1 compliant?
>
> Thanks,
>
> --kumar
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: Simple suggestion for namespaces

[Anne Thomas Manes]

Would it be possible to allow the organization to configure a default
namespace format?
I recommend using URNs for namespaces and giving the RDDL a resolvable URL.

Anne

On Nov 8, 2007 7:33 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> When we create default namespaces, why don't we have an option to create
> them based on actual URIs hosted by the server
>
> For example, the schema namespaces could point to the ?xsd we publish, and
> the service namespaces could point to the ?wsdl. That way our namespaces
> would be meaningful and dereferenceable.
>
> Another approach would be to define a standard NS for each service and use
> if for both schema and service, and then autogen an RDDL at that URI that
> points to both the schema and WSDL.
>
> I guess one problem will be that they will be based on IP addresses and
> therefore change - but we could at least make this an option.
>
> Thoughts?
>
> Paul
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
>  [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com

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

Re: [Axis2] WS-policy client support

[Anne Thomas Manes]

That's a proprietary policy assertion language. It's supported only by
BEA products. Talk to BEA and convince them to add support for the
standard OASIS WS-SecurityPolicy.

Anne

On 10/31/07, Feng Lu <[EMAIL PROTECTED]> wrote:
>
> Hello friends,
>
> I am wondering whether Axis2 support WS-policy client? My WSDL server is
> Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2
> will be able to handle WS-policy in such case. If it does, could anybody let
> me know how to implement the client side support for this? Any special
> handling in the stub genration?
>
>
>
> - 
>
>
> -  xmlns:wssp="http://www.bea.com/wls90/security/policy";>
>
>
> - 
>
>
> -  TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken";>
>
>
>Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
> />
>   
>   
>   
>   
>
> Thanks a lot for your help!
>
> Frank
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com

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

Re: rpc encoding in Axis2

[Anne Thomas Manes]

Axis2 does not support SOAP encoding. Use Axis 1.4 instead.

Anne

On 10/26/07, Iyengar, Kumar <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi all,
>
>
>
> We have a program that consumes external web services using Axis. I am
> currently upgrading the program to use Axis2. Our program works with Web
> Services that are of RPC Encoded Style as well ( besides doc/literal). I
> followed the examples and the java documentation but I am not clear how this
> works with RPC encoded styles. Most examples require me to change the WSDL
> from rpc/encoded to doc/literal. But since we are consuming external web
> services, we cannot do that.
>
>
>
> I looked at the Axis 2 API and it is unclear whether I can use ServiceClient
> for this. There is also another object RPCServiceClient. Does anyone know if
> this can be used for RPC Encoded Styles? The doc indicates that I pass in
> arg[] – if I have an OMElement then how do I use RPCServiceClient?
>
>
>
> Thanks,
>
>
>
> --ki

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

Re: axis2 access .net web service

[Anne Thomas Manes]

Please send this type of user request to axis-user, not axis-dev.

Anne

On 9/23/07, zhrb <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
>  I am now using axis2 accessing .net web service following samples of
> "EchoNonBlockingDualClient".The userguide just mentions the condition of
> both web service and client are based on axis2.But if my web service is .net
> web service,how should I use Axis2 client
>  to access in the "EchoNonBlockingDualClient" way?How should I change this
> line below:
>
>  options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
>  Waiting for your answer!Thanks!
>
>
>  -Zhang
>
>
>
>
> 
> 使用新一代 Hotmail，更强大、更安全、更多存储空间！ 立刻体验！

Re: Axis2 access .net web service

[Anne Thomas Manes]

I believe you are not creating your payload properly.

I'm not an expert on AXIOM, but I think it should look like this:

public static OMElement getContentOMElement() {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace("http://tempuri.org/";, "");
OMElement method = fac.createOMElement("HelloWorld", omNs);
OMElement value = fac.createOMElement("name", omNs);
value.addChild(fac.createText("zhangsan"));
method.addChild(value);
return method;

Anne

On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote:
>
> Wsdl document is in the attachment.Waiting for your help.
>
>
>
>  
>  > Date: Sat, 22 Sep 2007 08:29:59 -0400
> > From: [EMAIL PROTECTED]
> > To: axis-dev@ws.apache.org
> > Subject: Re: Axis2 access .net web service
> >
> > Please provide the WSDL.
> >
> > Anne
> >
> > On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello,
> > >
> > > I am now trying to using axis2 as client to access .net web service.
> > >
> > > .net web service as follows:
> > >
> > > public string HelloWorld(string name)
> > > {
> > > return "Hello World"+name;
> > > }
> > >
> > > Axis2 client code is in the attachment.When I run the client code,I get
> the
> > > following information:
> > >
> > > - Discarding unexpected response: HTTP/1.1 100 ContinueHello
> > > World
> > >
> > > Could you tell me what's the problem?Axis2 can access .net web service?I
> am
> > > waiting for your he lp.Thank you!
> > >
> > >
> > >
> > > -Zha ng
> > > 
> > > 用 Windows Live Spaces 展示个性自我，与好友分享生活！ 了解更多信息！
> > >
> -
> > > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
>
> 
> Windows Live Writer 让您告别龟速网络，轻松写日志！ 立即使用！
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Axis2 access .net web service

[Anne Thomas Manes]

Also -- please ask these questions on the axis-user list rather than
the axis-dev list.

Anne

On 9/22/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> Please provide the WSDL.
>
> Anne
>
> On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> >  I am now trying to using axis2 as client to access .net web service.
> >
> > .net web service as follows:
> >
> > public string HelloWorld(string name)
> >   {
> >return "Hello World"+name;
> >   }
> >
> > Axis2 client code is in the attachment.When I run the client code,I get the
> > following information:
> >
> > - Discarding unexpected response: HTTP/1.1 100 ContinueHello
> >  World
> >
> > Could you tell me what's the problem?Axis2 can access .net web service?I am
> > waiting for your help.Thank you!
> >
> >
> >
> > -Zha ng
> > 
> > 用 Windows Live Spaces 展示个性自我，与好友分享生活！ 了解更多信息！
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

Re: Axis2 access .net web service

[Anne Thomas Manes]

Please provide the WSDL.

Anne

On 9/22/07, zhrb <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
>  I am now trying to using axis2 as client to access .net web service.
>
> .net web service as follows:
>
> public string HelloWorld(string name)
>   {
>return "Hello World"+name;
>   }
>
> Axis2 client code is in the attachment.When I run the client code,I get the
> following information:
>
> - Discarding unexpected response: HTTP/1.1 100 ContinueHello
>  World
>
> Could you tell me what's the problem?Axis2 can access .net web service?I am
> waiting for your help.Thank you!
>
>
>
> -Zha ng
> 
> 用 Windows Live Spaces 展示个性自我，与好友分享生活！ 了解更多信息！
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Fwd: Re: Java2WSDL output for no parameters or void return type?]

[Anne Thomas Manes]

Deepal,

Per the wrapped convention, if you have the following interface:

  public String foo();

java2wsdl should generate an input element called "foo":


  


And "foo" must be defined as:


  


See the JAX-WS spec for the specific requirements of the wrapped
convention, or my blog for a quick overview:

http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html

Anne



On 9/13/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>
>
> Simon Laws wrote:
> > Hi Deepal
> >
> > Some more comments/questions below.
> >
> > Thanks
> >
> > Simon
> >
> > On 9/13/07, *Deepal jayasinghe* <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> > > I'm not quite sure whether this in answering the question about
> > >   public String foo();
> > This does not take any method parameters , so user can send SOAP
> > message
> > with empty body .
> >
> >
> > But in this case Axis at the server has to pull the operation name
> > from the SOAPAction header.
> yes . And Axis2 generate SOAP action for that , so it can find the
> operation from the generated SOAP action (if user sends that)
> >
> > So when generating the Schema we do not need to
> > generate Schema element for the input.
> >
> >
> > So in this case axis is happy that the operation name arrives at the
> > server in the SOAPAction header rather than in the first child element
> > of the ?
> It won't try to look for the body first child , so there wont be big
> difference whether you send that or not. But sometime if you send the
> body first child without sending SOAP action, that Axis2 will use its
> local name to dispatch the operation.
> >
> > To put it another way. If you have parameters on you operationjava2WSL
> > generates wrapped style WSDL. However it doesn't generate wrapped
> > style WSDL if you don't have parameters on your operation (I'm using
> > the definition of wrapped WSDL from JAX-WS in this case).
> Hmm , well need WSDL advice here , but as I know the WSDL we are
> generating is correct according to the WSDL validators I have used.
> >
> > Sounds strange to me but I'm just trying to get confirmation that this
> > behaviour is by design. There may be a good reason that I'm just not
> > thinking of.
> >
> > But we are generating message
> > element for both input and output. So we are generating in-out mep for
> > the above operation.
> > >
> > > or the other question about
> > >   public void foo(String param);
> > In this case we have method which take method parameter , so in this
> > case we generate two schema elements one for input and one for output.
> > And we generate two message elements as well. So in effect we generate
> > in-out mep.
> >
> >
> > When I runjava2WSDL on an interface with the method signature
> >
> > public void foo(String param);
> >
> > I see
> >
> > a single message
> > a single input part in this message
> > a single XSD element
> That is correct , since you have in only operation.
> >
> > (see the WSDL I posted earlier in this thread)
> >
> > So it seems axis is generating an in only mep. How do I tell it to
> > produce what you are saying here, i.e. an in-out mep
> >
> > >
> > > I think it's answering the former.  If I have understood this
> > correctly,
> > > then I'm not clear about what is the intention of Axis2 for the
> > latter.
> > > This case does seem to generate an in-only MEP at the moment.
> > If the method is in only you need to have method with void as it
> > return
> > type.
> >
> > public void update(String id){
> > }
> >
> >
> > Are you saying here that any message with a void return type is
> > assumed to be in-only? Or am I reading too much into this. To put it
> > another way how do I tell java2WSDL to choose between the generation
> > of in-only or in-out meps in this case.
> There is no way , it pick the MEP looking at the java method , if it is
> void then it assume that as in-only , if the method is void and has a
> exception then it will generate robust-in else it will generate in-out.
>
> Thanks
> Deepal
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: axis[1.3] Change in Rest Support

[Anne Thomas Manes]

Do you mean Axis2 1.3? Axis 1.3 doesn't support REST.

In the future, please send these requests to the axis-user group
rather than the axis-dev list.

Anne

On 9/13/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am using axis 1.3 and i am trying to execute a simple web service using
> REST.
> I was surpriced when i got:
>
> [ERROR] Allocate exception for servlet AxisRESTServlet
> java.lang.ClassNotFoundException:
> org.apache.axis2.transport.http.AxisRESTServlet
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java
> :1359)
> at
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1068)
> at
> org.apache.catalina.core.StandardWrapper.allocate
> (StandardWrapper.java:791)
> ...
> ...
>
> Is there some change in the REST support in axis 1.3?
> I checked out the web.xml, expecting to find a servlet and a mapping for
> the REST Servlet:
>
>
>
> 
>
> AxisRESTServlet
>
> Apache-Axis Servlet (REST)
>
> 
>
> org.apache.axis2.transport.http.AxisRESTServlet
>
> 
>
> 
>
>
>
> There is no such declaration in the web.xml of axis 1.3.
>
> There is no org.apache.axis2.transport.http.AxisRESTServlet
> class in the 1.3 release.
>
> How do you handle REST requests?
>
>
>
> Thanks,
>
> Nencho
>
>

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

Re: AXIS2 Skeleton and Stub Generation

[Anne Thomas Manes]

Axis2 support of RPC/literal is sketchy at best, considering that you
must edit the WSDL to tell Axis2 how to handle it.

See http://ws.apache.org/axis2/1_3/Axis2-rpc-support.html

Anne

On 8/20/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
>
>
> On 8/19/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > Use of types in a message part (rather than an element) indicates that
> > you are using an RPC style service. You should be using document style
> > with Axis2.
>
> Axis2 supports RPC style. but only literal. so if you wsdl is rpc/literal
> then you can use Axis2.
> but  Axis2 does not support rpc/encoded.
>
> >
> > Anne
> >
> > On 8/19/07, Karuppusamy, Thamayanthi (Consultant)
> > <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Hi,
> > >
> > >   How the stub and skeleton class are generated in AXIS2?. because It is
> > > totally different from AXIS 1.3 . For Example
> > > 
> > >
> > >
> > > 
> > >
> > > 
> > > above is created as one class Execute and ExecuteResponse etc., why it
> is
> > > creating like, but previous version is not creating like this.
> > >
> > > What is use of ExtensionMapper and * MessageReceiverInOut.java file, I
> have
> > > searched the *MessageReceiverInOut no where used this file in skeleton
> or
> > > other files
> > >
> > > Can anyone please help me?
> > >
> > >
> > > Thanks & Regards
> > > Thamayanthi Karuppusamy
> > >
> > >
> > >
> > > 
> > >
> > >
> > >
> > >
> > >  This email may contain confidential and privileged material for the
> sole
> > > use of the intended recipient(s). Any review, use, retention,
> distribution
> > > or disclosure by others is strictly prohibited. If you are not the
> intended
> > > recipient (or authorized to receive for the recipient), please contact
> the
> > > sender by reply email and delete all copies of this message. Also, email
> is
> > > susceptible to data corruption, interception, tampering, unauthorized
> > > amendment and viruses. We only send and receive emails on the basis that
> we
> > > are not liable for any such corruption, interception, tampering,
> amendment
> > > or viruses or any consequence thereof.
> >
> >
> -
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.

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

Re: AXIS2 Skeleton and Stub Generation

[Anne Thomas Manes]

Use of types in a message part (rather than an element) indicates that
you are using an RPC style service. You should be using document style
with Axis2.

Anne

On 8/19/07, Karuppusamy, Thamayanthi (Consultant)
<[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
>   How the stub and skeleton class are generated in AXIS2?. because It is
> totally different from AXIS 1.3 . For Example
> 
>
>
> 
>
> 
> above is created as one class Execute and ExecuteResponse etc., why it is
> creating like, but previous version is not creating like this.
>
> What is use of ExtensionMapper and *MessageReceiverInOut.java file, I have
> searched the *MessageReceiverInOut no where used this file in skeleton or
> other files
>
> Can anyone please help me?
>
>
> Thanks & Regards
> Thamayanthi Karuppusamy
>
>
>
> 
>
>
>
>
>  This email may contain confidential and privileged material for the sole
> use of the intended recipient(s). Any review, use, retention, distribution
> or disclosure by others is strictly prohibited. If you are not the intended
> recipient (or authorized to receive for the recipient), please contact the
> sender by reply email and delete all copies of this message. Also, email is
> susceptible to data corruption, interception, tampering, unauthorized
> amendment and viruses. We only send and receive emails on the basis that we
> are not liable for any such corruption, interception, tampering, amendment
> or viruses or any consequence thereof.

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

Re: Bug? SimpleType enumeration output is incorrect.

[Anne Thomas Manes]

That's an inappropriate restriction. XML has no such "reserved words"
constraints. If Axis2 has a problem dealing with a valid local name,
it's a bug.

Anne

On 8/16/07, WJ Krpelan <[EMAIL PROTECTED]> wrote:
> Hi
> Methinks you shouldn't use "type" as element name, and
> neither "element" nor "attribute" etc. as these are
> kind of "reserved words". Use "type1" or something and
> it should work imho.
> Cheers
> Wolfgang Krpelan
>
>
> --- Amila Suriarachchi <[EMAIL PROTECTED]>
> wrote:
>
> > Can you please test this for Axis2 1.3 release.
> >
> > And run this sample code which gives me the correct
> > out put
> >
> > public class TestClass extends TestCase {
> >
> > public void testGetResponse(){
> > GetResponse getResponse = new GetResponse();
> > getResponse.setOut("Test out");
> > getResponse.setType(Type_T.a);
> >
> > try {
> > OMElement omElement =
> > getResponse.getOMElement(
> > GetResponse.MY_QNAME,
> > OMAbstractFactory.getOMFactory());
> > System.out.println("OM Element ==> " +
> > omElement.toStringWithConsume());
> > } catch (ADBException e) {
> > e.printStackTrace();  //To change body
> > of catch statement use
> > File | Settings | File Templates.
> > } catch (XMLStreamException e) {
> > e.printStackTrace();  //To change body
> > of catch statement use
> > File | Settings | File Templates.
> > }
> > }
> > }
> >
> >  > xmlns:ns1="http://localhost:8080/wsdlfile/";>
> > Test out
> > a
> > 
> >
> > Amila.
> >
> >
> > On 8/10/07, Kevin TierOne <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > 1 - If I run the wsdl through the code generator,
> > I get the file
> > > WsdlfileSkeleton.java.
> > >
> > > 2 - I implement this method:
> > >   public localhost.wsdlfile.GetResponse
> > Get(localhost.wsdlfile.Get get0)
> > >   {
> > > localhost.wsdlfile.GetResponse resp=new
> > localhost.wsdlfile.GetResponse
> > > ();
> > > resp.setOut(get0.getIn());
> > > resp.setType(get0.getType());
> > > return resp;
> > >   }
> > >
> > > 3 - After deploying the webservice, I send the
> > request as shown in the
> > > original post.
> > >
> > > 4 - In the TCP monitor, I see the response shown
> > the original post.  I
> > > expect that the response should echo the same
> > values and structure as
> > > in the request.  However, in the response, the
> > Element  is
> > > incorrect.  The name of the element should be
> > .
> > >
> > > Let me know if you need any other info.
> > >
> > > Kevin
> > >
> > > On 8/10/07, Amila Suriarachchi
> > <[EMAIL PROTECTED]> wrote:
> > > > Can you please describe your qestion bit?
> > > >
> > > > in other words How can I regenerate your issue?
> > > >
> > > > Amila.
> > > >
> > > >
> > > > On 8/9/07, Kevin TierOne <
> > [EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Sorry, I forgot to mention that I'm using
> > Axis2 1.2.
> > > > >
> > > > > Kevin
> > > > >
> > > > > On 8/9/07, Kevin TierOne
> > <[EMAIL PROTECTED]> wrote:
> > > > > > The XML tags in the response messsage of an
> > enumerated element uses
> > > > > > the simpleType name.  It should use the
> > element name.  For example,
> > > > > > using the wsdl below I get the following
> > request and response.
> > > > > >
> > > > > > Look at the output
> > "c", this element should
> > > > > > be c
> > > > > >
> > > > > > REQUEST:
> > > > > >  > > > > >
> > > >
> >
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > > > > > xmlns:q0=" http://localhost:8080/wsdlfile/";
> > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > > > > > xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance";>
> > > > > > 
> > > > > > 
> > > > > > www
> > > > > > c
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >
> > > > > > RESPONSE:
> > > > > >  > > >
> >
> encoding="http://schemas.xmlsoap.org/soap/envelope/";?>
> > > > > >  > > >
> >
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> > > > > > 
> > > > > > http://localhost:8080/wsdlfile/";>
> > > > > >  > xmlns="http://localhost:8080/wsdlfile/";>www
> > > > > > c
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > 
> > > > > >  > > >
> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > > > > >
> > xmlns:tns="http://localhost:8080/wsdlfile/ "
> > > > > >
> > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > > > > >
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema "
> > > > > >
> > > >
> >
> xmlns:wsaw="http://www.w3.org/2006/02/addressing/wsdl";
> > > > name="wsdlfile"
> > > > > > targetNamespace="
> > http://localhost:8080/wsdlfile/";>
> > > > > > 
> > > > > >  > attributeFormDefault="qualified"
> > > > > > elementFormDefault="qualified"
> > > > > > targetNamespace="
> > http://localhost:8080/wsdlfile/";>
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >  > name="in" type="xsd:string" />
> > > > > >

Re: Fwd: [AXIOM] Undeclare default namespace

[Anne Thomas Manes]

By "undeclare" I believe Xinjun means that he wants to declare the
default namespace as no value, e.g., xmlns="".

Anne

On 7/23/07, Xinjun Chen <[EMAIL PROTECTED]> wrote:

Hi Chinthaka,

I have an element

   bValue
.
I have another element  which is created by another OMStaxBuilder.  is
unqualified. Now I need to add  to  as a child of  but I want to
remove the namespace in  and make  unqualified.

I tried the AXIOM API to undeclare the default namespace of  but failed.
I can only change the default namespace to another value but not empty
string, i.e., I cannot undeclare it.


Regards,
Xinjun


On 7/23/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> What did u mean by undeclare? If you point me what you want with some
> code, perhaps I can answer better.
>
> Thanks,
> Chinthaka
>
> Xinjun Chen wrote:
> > Hi Axis2 Developers,
> >
> > Is it possible to undeclare a default namespace from an OMElement in
AXIOM?
> > I tried several ways but failed to undeclare a default namespace. Could
> > anyone point me a way out?
> > Thanks.
> >
> > Regards,
> > Xinjun
> >
> > -- Forwarded message --
> > From: *Xinjun Chen* <[EMAIL PROTECTED] >
> > Date: Jul 19, 2007 12:54 PM
> > Subject: [AXIOM] Undeclare default namespace
> > To: [EMAIL PROTECTED] 
> >
> >
> > Hi,
> >
> > I have some problem undeclaring the default namespace in an OMElement.
> > I have tried the following three ways but all failed. The default
> > namespace is still in the OMElement.
> >
> > #1:
> > OMElement reqElement = ;
> > reqElement.declareDefaultNamespace ("");
> >
> > #2:
> > OMElement reqElement = ;
> > reqElement.declareNamespace("", "");
> >
> > #3:
> > OMElement reqElement = ;
> > OMFactory omFactory = reqElement.getOMFactory();
> > OMNamespace ns = omFactory.createOMNamespace("", "");
> > reqElement.declareNamespace(ns);
> >
> > Could anyone point me out what I can do to undeclare the default
> > namespace in AXIOM? Thanks for your help in advance.
> >
> > Regards,
> > Xinjun
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
>
iD8DBQFGo5JvjON2uBzUhh8RAlM6AJoDKg+9UJTRdIVIDgwMgrtIkcvyZQCgmVss
> gisWSWkZr/pLyS9lRjOPGjY=
> =zx5V
> -END PGP SIGNATURE-
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




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

Re: problem with SOAPFault custom error tags.

[Anne Thomas Manes]

Is this the verbatim error you receive from .NET? I ask because it is
not a valid SOAP Fault. The , , and 
elements must be unqualified. Also, the namespace prefix for the
 element has not been declared.

These errors are the reason why Axis cannot properly interpret the fault.

Anne

On 7/16/07, Rupesh Kumar Kansara <[EMAIL PROTECTED]> wrote:





Hi All,



I am facing a strange problem.

I have a web-service which is developed in .Net. and accessing the same with
client generated with axis2.



In case of any Exception web-service returns SOAP-FAULT message with a
custom tag error and code as attribute as follows:





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



  

  soapenv:Server.Application

  Application
Error

  No CPS's have been
selectedNo
CPS's have been selected   at
AML.Server.Interface.MethodHandler.takeOnClientImp(BaseIDDef
EntityType, EntityIdentifierDef EntityIdentifier, BaseIDDef
OwnerJurisdiction, RelationshipDef EntityRelationship, BaseIDDef[]
AMLProduct, ActivitySimpleDef Activity, KYCFICAExemptionSimpleDef[]
KYCFICAExemption, SecurityContextDef SecurityContext) in
Z:\Investec\AML\Server\src\Interface\MHInterface.cs:line 60

   at
Codegen.amlint.WSAMLInterfaceBase.takeOnClient(takeOnClientRequest
request) in
Z:\Investec\AML\common\src\gen\wsi_AMLInterface.cs:line
40





But at client side it's absence in AxisObject, If I walkthrough the
AxisFault object I just got the text part in the soap:detail element no
 element.





Please suggest where the problem is ?



Thanks & Regards

Rupesh Kansara
















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

Re: Jxta bridge

[Anne Thomas Manes]

Check out http://soap.jxta.org/.

Anne

On 3/22/07, Скворцов Никита <[EMAIL PROTECTED]> wrote:

Good time of day, mighty All!


 I am looking for a project called Jxta Bridge.
 It's aim was to create combination of Axis WebService framework and Jxta
P2P technologies. It was announced at 2002 by Kevin A. Burton - and since
then wasn't mentioned a lot.

The only link I've found
(http://relativity.yi.org/jxta-bridge/) points to a dead
server :(

Can anyone help me with any info related to this project? Links, developer
contacts... - anything.

Thank you!

Nikita Skvortsov

Re: Problem with the namespace prefix in Axis

[Anne Thomas Manes]

You must process the signature before Axis deserializes the message.
You can do it in a JAX-RPC handler -- that's what WSS4J does, or you
must use the messaging API.

Anne

On 3/10/07, anup bansal <[EMAIL PROTECTED]> wrote:

Dear Anne,

I am not using WSSJ. We use a common service within our institution for
signing and verification of messages. I am using the SAAJ APIs to extract
the element tags from the SOAP message I receive.
However when extracting the elements, the message is serialized by AXIS and
it is during this process that the origiinal prefix values are ignored.

Can using WSS4J solve my problem?

You have mentioned the following:
If the application needs to maintain the contents of the original SOAP
message in its pure form, then you must use the Messaging API and
process the raw XML.

So does that mean the only way to overcome the problem is: I need to write
my own HTTPSender class. The entire message I response I receive in the
bytes, will have to be converted to an XML and then the data extracted
without the interferrence of AXIS?

Thanks  regards,
Anup

Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Prefixes are significant when the XML message or a portion thereof is
being signed.

Anup -- you have to make sure you process the signature before Axis
begins to process it. Are you using WSS4J to process the signature?

If the application needs to maintain the contents of the original SOAP
message in its pure form, then you must use the Messaging API and
process the raw XML.

Anne

On 3/8/07, Tom Jordahl wrote:
>
>
>
>
> No, namespace prefixes are not significant in SOAP messages. They are just
> a shorthand.
>
> Axis doesn't preserve them in any way (nor do most other toolkits that I
am
> aware of).
>
>
>
>
> --
>
> Tom Jordahl
>
> Adobe ColdFusion Team
>
> 
>
>
> From: anup bansal [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 03, 2007 3:39 AM
> To: axis-dev@ws.apache.org
> Subject: Re: Problem with the namespace prefix in Axis
>
>
>
>
>
> Hi All,
>
>
>
>
>
> Has anyone never faced this problem before?
>
>
> I debugged the Axis 1.4 code and found that during serialization of the
> input
>
>
> received, (Client respone handler), the URIs are mapped to default
namespace
> prefix values and the original prefixes received with the mesages are
> ignored.
>
>
> Is there a way to get around this and make Axis use the same prefixes as
> recevied? Can I set some prameter in my client-config.wsdd to disable
this?
>
>
> I have already tried the
> "enableNamespacePrefixOptimization" property but it too
> does not work?
>
>
>
>
>
> Please help me.. Its really very urgent.
>
>
>
>
>
> Thanks & regards,
>
>
> Anup
>
> Anne Thomas Manes wrote:
>
>
> As long as the prefix maps to the correct namespace URI, the messages
> are semantically identical. Your handler should be to handle any
> prefix string.
>
> Anne
>
> On 2/27/07, anup bansal wrote:
> > Hi All,
> >
> > I am using Axis 1.4 for accessing a third party weservice. I am able to
> > connect to the service and receive the response.
> >
> > The prefixes in the response I receive is not the same as the the one
> sent
> > by the service. The difference lies in the name space prefix values.
> > As a result the response header is not being validated.
> >
> > Axis is replacing the namespace prefixes with its own prefix values.
> > For e.g. the prefix value sent for the SOAP Body is soap12, where as
Axis
> > converts it into soapenv.
> >
> > Is this a bug in Axis or is there a way to get around this problem? Can
> you
> > please help?
> >
> > Regards,
> > Anup
> >
> > 
> > Here's a new way to find what you're looking for - Yahoo! Answers
> >
> >
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> 
>
>
> Here's a new way to find what you're looking for - Yahoo! Answers

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




 
 Here's a new way to find what you're looking for - Yahoo! Answers




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

Re: Problem with the namespace prefix in Axis

[Anne Thomas Manes]

Prefixes are significant when the XML message or a portion thereof is
being signed.

Anup -- you have to make sure you process the signature before Axis
begins to process it. Are you using WSS4J to process the signature?

If the application needs to maintain the contents of the original SOAP
message in its pure form, then you must use the Messaging API and
process the raw XML.

Anne

On 3/8/07, Tom Jordahl <[EMAIL PROTECTED]> wrote:





No, namespace prefixes are not significant in SOAP messages.  They are just
a shorthand.

Axis doesn't preserve them in any way (nor do most other toolkits that I am
aware of).




--

Tom Jordahl

Adobe ColdFusion Team

 


From: anup bansal [mailto:[EMAIL PROTECTED]
 Sent: Saturday, March 03, 2007 3:39 AM
 To: axis-dev@ws.apache.org
 Subject: Re: Problem with the namespace prefix in Axis





Hi All,





Has anyone never faced this problem before?


I debugged the Axis 1.4 code and found that during serialization of the
input


received, (Client respone handler), the URIs are mapped to default namespace
prefix values and the original prefixes received with the mesages are
ignored.


Is there a way to get around this and make Axis use the same prefixes as
recevied? Can I set some prameter in my client-config.wsdd to disable this?


I have already tried the
"enableNamespacePrefixOptimization" property but it too
does not work?





Please help me.. Its really very urgent.





Thanks & regards,


Anup

 Anne Thomas Manes <[EMAIL PROTECTED]> wrote:


As long as the prefix maps to the correct namespace URI, the messages
 are semantically identical. Your handler should be to handle any
 prefix string.

 Anne

 On 2/27/07, anup bansal wrote:
 > Hi All,
 >
 > I am using Axis 1.4 for accessing a third party weservice. I am able to
 > connect to the service and receive the response.
 >
 > The prefixes in the response I receive is not the same as the the one
sent
 > by the service. The difference lies in the name space prefix values.
 > As a result the response header is not being validated.
 >
 > Axis is replacing the namespace prefixes with its own prefix values.
 > For e.g. the prefix value sent for the SOAP Body is soap12, where as Axis
 > converts it into soapenv.
 >
 > Is this a bug in Axis or is there a way to get around this problem? Can
you
 > please help?
 >
 > Regards,
 > Anup
 >
 > 
 > Here's a new way to find what you're looking for - Yahoo! Answers
 >
 >

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




 


Here's a new way to find what you're looking for - Yahoo! Answers


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

Re: Possible Axis 1.4 Bug

[Anne Thomas Manes]

Yes. If you modify the generated WSDL, you must run WSDL2Java.
That should fix your namespace errors.

On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:


 All the neccesary information is attatched to those mails (WSDL, WSDD,
JARs,...).

I changed the WSDL provided by Axis so as to work with Netbeans, but after
that, I didn´t change the Axis related part at all!

So, I take note, in conclusion, in your opinion, I should regenerate the
Java Object (Sumador) from which Axis generates the Web service.

Am I right?

 --
*De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
*Enviado el:* miércoles, 07 de marzo de 2007 15:49
*Para:* axis-dev@ws.apache.org
*Asunto:* Re: Possible Axis 1.4 Bug

btw -- after you did this:

> As you can see in the project I send some days before, I took this
> WSDL and removed the Schema to paste it in the Operacion.xsd file
> under the "
http://serv.wsutils.batz.com";
> <http://serv.wsutils.batz.com/> namespace . Then, I imported this XML
> Schema to the WSDL under the
> _"__http://stiperez:7070/axis/services/Sumador"; namespace._ What's

> wrong with this??
>
> Consider that the In-Line validator of WSDL schemas doesn´t work
> properly!!

Did you then regen the service skeleton using wsdl2java?

Anne

On 3/7/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>
> The last 6 mails don't provide enough information.
> Please summarize the problem. Include appropriate WSDLs, WSDDs, etc.
>
> Thanks,
> Anne
>
> On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:
> >
> >  Please, read the last 6 mails (from 2007-03-02 on), they sumarize the
> > key subject!
> >
> > P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read
> > client as partner!
> >
> > Thank you!
> >
> >  --
> > *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> > *Enviado el:* miércoles, 07 de marzo de 2007 15:29
> > *Para:* axis-dev@ws.apache.org
> > *Asunto:* Re: Possible Axis 1.4 Bug
> >
> >  Please summarize the problem for us.
> >
> > On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >Hello,
> > >
> > > first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.
> > >
> > > We've found an issue wih the namespaces in the SOAP message returned
> > > by Axis.
> > >
> > > In order to follow this issue from the begining to the analysis of
> > > the problem, please, follow this thread at NetBeans Enterprise Pack 
Mailing
> > > list:
> > >
> > > 
http://www.netbeans.org/servlets/BrowseList?list=nbentpack&by=thread&from=772248
> > >
> > >
> > > Thank you!
> > >
> > >
> > >   [image: BATZ S.COOP]
> > >
> > > Ibai Perez Arbulu
> > > [EMAIL PROTECTED]
> > >
> > > *BATZ S. COOP
> > > *Torrea Auzoa,32
> > > 48140 IGORRE, (Bizkaia) - Spain
> > > Tfn: +34 946305000
> > > Fax +34 946305020
> > >
> > > *http://www.batz.com
> > > *
> > >
> > >  *P*
> > > *"Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera
> > > doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da."
> > > *
> > > *"No imprima este mensaje o sus documentos adjuntos, a no ser que
> > > sea verdaderamente necesario. Colaborar a respetar el medio ambiente es 
cosa
> > > nuestra"*
> > >
> > >  La información contenida en este mensaje y/o archivo(s) adjunto(s)
> > > es confidencial/privilegiada y esta destinada a ser leída solo por la(s)
> > > persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el
> > > destinatario señalado, el empleado o el agente responsable de entregar el
> > > mensaje al destinatario, o ha recibido esta comunicación por error, le
> > > informamos que esta totalmente prohibida, y puede ser ilegal, cualquier
> > > divulgación, distribución o reproducción de esta comunicación, y le 
rogamos
> > > que nos lo notifique inmediatamente y nos devuelva el mensaje original a 
la
> > > dirección arriba mencionada. Gracias.
> > >
> > >
> >
>

Re: Possible Axis 1.4 Bug

[Anne Thomas Manes]

btw -- after you did this:


As you can see in the project I send some days before, I took this
WSDL and removed the Schema to paste it in the Operacion.xsd file
under the "http://serv.wsutils.batz.com";
<http://serv.wsutils.batz.com/> namespace . Then, I imported this XML
Schema to the WSDL under the
_"__http://stiperez:7070/axis/services/Sumador"; namespace._ What's
wrong with this??

Consider that the In-Line validator of WSDL schemas doesn´t work
properly!!


Did you then regen the service skeleton using wsdl2java?

Anne

On 3/7/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:


The last 6 mails don't provide enough information.
Please summarize the problem. Include appropriate WSDLs, WSDDs, etc.

Thanks,
Anne

On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:
>
>  Please, read the last 6 mails (from 2007-03-02 on), they sumarize the
> key subject!
>
> P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client
> as partner!
>
> Thank you!
>
>  --
> *De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> *Enviado el:* miércoles, 07 de marzo de 2007 15:29
> *Para:* axis-dev@ws.apache.org
> *Asunto:* Re: Possible Axis 1.4 Bug
>
> Please summarize the problem for us.
>
> On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:
> >
> >
> >Hello,
> >
> > first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.
> >
> > We've found an issue wih the namespaces in the SOAP message returned
> > by Axis.
> >
> > In order to follow this issue from the begining to the analysis of the
> > problem, please, follow this thread at NetBeans Enterprise Pack Mailing
> > list:
> >
> > 
http://www.netbeans.org/servlets/BrowseList?list=nbentpack&by=thread&from=772248
> >
> >
> > Thank you!
> >
> >
> >   [image: BATZ S.COOP]
> >
> > Ibai Perez Arbulu
> > [EMAIL PROTECTED]
> >
> > *BATZ S. COOP
> > *Torrea Auzoa,32
> > 48140 IGORRE, (Bizkaia) - Spain
> > Tfn: +34 946305000
> > Fax +34 946305020
> >
> > * http://www.batz.com
> > *
> >
> >  *P*
> > * "Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera
> > doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da."*
> > *"No imprima este mensaje o sus documentos adjuntos, a no ser que sea
> > verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa
> > nuestra"*
> >
> >  La información contenida en este mensaje y/o archivo(s) adjunto(s) es
> > confidencial/privilegiada y esta destinada a ser leída solo por la(s)
> > persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el
> > destinatario señalado, el empleado o el agente responsable de entregar el
> > mensaje al destinatario, o ha recibido esta comunicación por error, le
> > informamos que esta totalmente prohibida, y puede ser ilegal, cualquier
> > divulgación, distribución o reproducción de esta comunicación, y le rogamos
> > que nos lo notifique inmediatamente y nos devuelva el mensaje original a la
> > dirección arriba mencionada. Gracias.
> >
> >
>

Re: Possible Axis 1.4 Bug

[Anne Thomas Manes]

The last 6 mails don't provide enough information.
Please summarize the problem. Include appropriate WSDLs, WSDDs, etc.

Thanks,
Anne

On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:


 Please, read the last 6 mails (from 2007-03-02 on), they sumarize the key
subject!

P.D: In the mail forom Kiran ( the one posted in 2007-03-02) read client
as partner!

Thank you!

 --
*De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
*Enviado el:* miércoles, 07 de marzo de 2007 15:29
*Para:* axis-dev@ws.apache.org
*Asunto:* Re: Possible Axis 1.4 Bug

Please summarize the problem for us.

On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:
>
>
>Hello,
>
> first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.
>
> We've found an issue wih the namespaces in the SOAP message returned by
> Axis.
>
> In order to follow this issue from the begining to the analysis of the
> problem, please, follow this thread at NetBeans Enterprise Pack Mailing
> list:
>
> 
http://www.netbeans.org/servlets/BrowseList?list=nbentpack&by=thread&from=772248
>
>
> Thank you!
>
>
>   [image: BATZ S.COOP]
>
> Ibai Perez Arbulu
> [EMAIL PROTECTED]
>
> *BATZ S. COOP
> *Torrea Auzoa,32
> 48140 IGORRE, (Bizkaia) - Spain
> Tfn: +34 946305000
> Fax +34 946305020
>
> *http://www.batz.com
> *
>
>  *P*
> *"Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera
> doazkizun dokumentuak. Lagundu ingurumena zaintzen, denon ardura da."*
> *"No imprima este mensaje o sus documentos adjuntos, a no ser que sea
> verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa
> nuestra"*
>
>  La información contenida en este mensaje y/o archivo(s) adjunto(s) es
> confidencial/privilegiada y esta destinada a ser leída solo por la(s)
> persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el
> destinatario señalado, el empleado o el agente responsable de entregar el
> mensaje al destinatario, o ha recibido esta comunicación por error, le
> informamos que esta totalmente prohibida, y puede ser ilegal, cualquier
> divulgación, distribución o reproducción de esta comunicación, y le rogamos
> que nos lo notifique inmediatamente y nos devuelva el mensaje original a la
> dirección arriba mencionada. Gracias.
>
>

Re: Possible Axis 1.4 Bug

[Anne Thomas Manes]

Please summarize the problem for us.

On 3/7/07, Ibai Perez Arbulu <[EMAIL PROTECTED]> wrote:



   Hello,

first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.

We've found an issue wih the namespaces in the SOAP message returned by
Axis.

In order to follow this issue from the begining to the analysis of the
problem, please, follow this thread at NetBeans Enterprise Pack Mailing
list:


http://www.netbeans.org/servlets/BrowseList?list=nbentpack&by=thread&from=772248

Thank you!


  [image: BATZ S.COOP]

Ibai Perez Arbulu
[EMAIL PROTECTED]

*BATZ S. COOP
*Torrea Auzoa,32
48140 IGORRE, (Bizkaia) - Spain
Tfn: +34 946305000
Fax +34 946305020

*http://www.batz.com
*

  *P*
*"Ezinbestekoa ez bada, ez imprimitu mezu hau edo honekin batera doazkizun
dokumentuak. Lagundu ingurumena zaintzen, denon ardura da."*
*"No imprima este mensaje o sus documentos adjuntos, a no ser que sea
verdaderamente necesario. Colaborar a respetar el medio ambiente es cosa
nuestra"*

   La información contenida en este mensaje y/o archivo(s) adjunto(s) es
confidencial/privilegiada y esta destinada a ser leída solo por la(s)
persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el
destinatario señalado, el empleado o el agente responsable de entregar el
mensaje al destinatario, o ha recibido esta comunicación por error, le
informamos que esta totalmente prohibida, y puede ser ilegal, cualquier
divulgación, distribución o reproducción de esta comunicación, y le rogamos
que nos lo notifique inmediatamente y nos devuelva el mensaje original a la
dirección arriba mencionada. Gracias.

Re: [axis2] How to Configure/Enable Axis2 for REST

[Anne Thomas Manes]

I haven't said anything about this before, but it's really starting to
bother me. There's a real problem with the idea of specifying an
"operation" with a service that supposed to be RESTful.

Keep in mind that REST is an architectural style. Rule number one when
following REST architectural principles. The ONLY operations involved
are those defined by a uniform interface: in the case of HTTP, that
uniform interface supports the following operations: GET, PUT, POST,
DELETE. You perform these operations on "resources" by exchanging
"representations" of those resources (hence the name Representational
State Transfer).

The reason why the getVersion service works as a RESTful service is
that it only supports the GET operation. If you really want to support
REST then you need to put constraints on the types of resources and
the available methods that can be exposed via a REST interface.

If you're tunneling an operation name via the interface, then it isn't
REST. It's POX.

(Ignore me if you want, but I just had to say it.)

Anne

On 3/6/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

What is shown in the web interface is the EPR only. You need to append
the operation name also to that.

Anyway this has more things to think about, in addition to solving the
problem that you have mentioned.

1. Seems the error message could have been improved
2. Do we wanna use some sort of defaulting where, if the service has
just one operation then even if the request doesn't contain the
operation, we can return the proper reply. I think version service has
just one operation.

Any thoughts on this?

- -- Chinthaka

rjain wrote:
> Thanx, whew, how could I miss that one!!
>
>
> Manoj Khangaonkar wrote:
>> Rajest,
>>
>> The url you need to enter in the browser is I think
>>
>> http://localhost:8080/axis2/rest/Version/getVersion
>>
>> Mj
>>
>>
>> On 3/5/07, rjain <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> Let me explain what are the steps I do and what is the result I get
>>>
>>> 1. I have downloaded the axis-2.1.1 distribution, and created a axis2.war
>>> file.
>>> 2. I have Tomcat 5.5.15, and drop the war file in the webapps folder
>>> 3. I start Tomcat, and access the following URL
>>> http://localhost:8080/axis2/services/listServices
>>>
>>> It shows me the Version Service with the following URL's
>>>
>>> Service EPR : http://localhost:8080/axis2/services/Version
>>> Service REST epr : http://localhost:8080/axis2/rest/Version
>>>
>>> If I try to access the first URL
>>> (http://localhost:8080/axis2/services/Version) I get the following
>>> message
>>>
>>> Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml
>>>
>>> If I try to access the second URL (
>>> http://localhost:8080/axis2/rest/Version)
>>> I get the following error message
>>> 
>>> 
>>> −
>>>
>>> I can not find a service for this request to be serviced. Check the WSDL
>>> and
>>> the request URI
>>> 
>>> 
>>> 
>>>
>>> Next, I go the axis2.xml and  in the webapps/axis/WEB-INF\conf folder and
>>> change the following settings
>>>services
>>>rest
>>>>> locked="true">true
>>>
>>> The rest all parameters are default, I don't change anything else.
>>>
>>> I stop and start tomcat, access the List services, it shows me the same
>>> URL.
>>> I try to access the first URL,
>>> http://localhost:8080/axis2/services/Version,
>>> I get the error message
>>> 
>>> 
>>> −
>>>
>>> I can not find a service for this request to be serviced. Check the WSDL
>>> and
>>> the request URI
>>> 
>>> 
>>> 
>>>
>>> I try to access the second URL, http://localhost:8080/axis2/rest/Version,
>>> I
>>> get the error message
>>> soapenv:Fault>
>>> 
>>> −
>>>
>>> I can not find a service for this request to be serviced. Check the WSDL
>>> and
>>> the request URI
>>> 
>>> 
>>> 
>>>
>>> I check the WSDL at http://localhost:8080/axis2/services/Version?wsdl,
>>> and
>>> it is available.
>>>
>>> I have tried with the Nightly builds, where the configuration parameters
>>> are
>>> simpler, I have not
>>> been successful. I would like to know what is the step I am missing or
>>> going
>>> wrong.
>>>
>>> Thanx once again for all the help!!
>>>
>>> regards
>>> Rajesh
>>>
>>>
>>> Manoj Khangaonkar wrote:
 Rajesh,

 REST is enabled by default.

 What is not working ? What error are u getting ?

 In the email below - the wrong URL is used to get the Version. The
 documentation has the right URL

 Mj


 On 3/3/07, rjain <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to configure the axis2.xml and web.xml for REST. What are
>>> the
> parameters I need to set? I have tried all combinations of parameters
>>> and
> it
> doesn't seem to work. Out of box axis2.war, doesn't work (the Version
> REST
> Service doesn't work) Is this broken and do I have to do anything.
>>> Please
> help!!!
>
> Below is the conversation

Re: qn about binding in document/literal message mode

[Anne Thomas Manes]

Please file a JIRA.

On 3/4/07, Prasad Sarma <[EMAIL PROTECTED]> wrote:

Hi All,
  When I am creating wsdl from my source code , Binding is
"document/literal" messaging mode ( I am not sure how to chose the mode
explicitly using the code generation wizard in axis2) I could see  namespace
attribute in  element in  element
here is the part of my wsdl.

Can somebody tell me why "namespace" appears for soap:body element.

 I get a warning that "A document/literal binding in a description MUST NOT
have the name space attribute specified on contained soap:body"
Is there any way to avoid this besides manually deleting it?


http://schemas.xmlsoap.org/soap/http";
style="document" />



http://ws.marketlink.nationwide.com"; />


http://ws.marketlink.nationwide.com"; />


http://ws.marketlink.nationwide.com"; />




Thanks in advance,
Prasad

Eran Chinthaka <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

If you can give some more insights in to your problem, perhaps we can
help you a bit.

Do remember that REST and SOAP endpoints are different, by default. And
if you wanna change that in to one, or disable one, then only you need
to touch the config files. Other than that things should work fine.

- -- Chinthaka

rjain wrote:
> Hi,
>
> I am trying to configure the axis2.xml and web.xml for REST. What are the
> parameters I need to set? I have tried all combinations of parameters and
it
> doesn't seem to work. Out of box axis2.war, doesn't work (the Version REST
> Service doesn't work) Is this broken and do I have to do anything. Please
> help!!!
>
> Below is the conversation from the axis-user mailing list, and I haven't
got
> any useful information
>
> regards
> Rajesh
>
>
>
>> Hi Glen
>>
>> Thanx for the article. But this didn't help.
>>
>> If I set both the parameters as described in the document i.e.
>> >> locked="true">true
>>
>> >> locked="true">true
>>
>> Both the Service URL are same
>> Service EPR :
http://localhost:8080/axis2/services/Version
>> Service REST epr :
http://localhost:8080/axis2/services/Version
>>
>> I get the following error
>>
>>
>>
>> −
>>
>> I can not find a service for this request to be serviced. Check the WSDL
>> and
>> the request URI
>>
>>
>>
>>
>>
>> I hope this feature is not broken in the latest version. Any other
>> pointers
>> what I should be doing?
>>
>
> Sorry, I have not done this before. You may wish to google the
> parameter properties "enableRESTInAxis2MainServlet" and
> "disableSeparateEndpointForREST" separately. Hopefully
that will lead
> you to a working configuration.
>
> Glen
>
>
>
>
>> ===
>>
>>
>>
>> GlenMazza wrote:
>>> Am Freitag, den 02.03.2007, 17:05 -0800 schrieb rjain:
 Hi

 I am using Axis2 1.1.1 , and I am trying to configure the "Version"
 Service
 to be RESTFul.
>>> ...
>>>
 Can someone guide me to the documentation of how to Enable AXIS2 for
 REST,what are the configuration parameters I need to set to make this
 successful.

>>> Search on this page[1] for the two articles (under External FAQs) with
>>> the word "REST". Let us know if they help you.
>>>
>>> Glen
>>>
>>> [1] http://wiki.apache.org/ws/FrontPage/Axis2/
>>>
>>>
 Thanx!
 Rajesh
>

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

iD8DBQFF60UBjON2uBzUhh8RAvlIAKCGUZD18pzNsw8ezmyGtVzL8K7/4gCfcQ+F
Vm3G3SuJIcmEYfufAZQKVlc=
=rV2F
-END PGP SIGNATURE-

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






 
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.




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

Re: WSDL2Java Code will not compile

[Anne Thomas Manes]

Robert,

Both your WSDL and imported schema have errors.

The WSDL does not define its faults properly. The names specified in
the binding must correspond to the names specified in the portType:

The portType is defined as:

   
   
   
   
   

But the binding is defined as:

   
   
   

The  name should be "SDD2ErrorFault".
Also, you must remove the namespace attribute from the  definition.

As for the schema, it repeatedly defines a set of elements with the
same name, e.g., AppId, RequestId, SourceService, DestService,
ProcessingStatus, etc. In a schema that's defined as
elementFormDefault="qualified", every element must have a unique name.
If you want to use the same element in multiple types, then you must
define the element as a global element (defined as a direct child of
the  element), and use "ref=" to refer to the element from
within a type definition.

Regards,
Anne

On 3/2/07, Robert Chilvers <[EMAIL PROTECTED]> wrote:

Hi There;

I have a WSDL that I am trying to generate code for in Axis1.4.  The
WSDL generates code, but the code will not compile.  The WSDL was
supplied to me by a third party.

The error is the fact that the code generator is creating a class
called SDD2Error_Element, but my implantation class is looking for a
file called SDD2Error which it throws as a exception.  The code
generator does not create a SDD2Error class at all.  My theory is
that the SDD2Error_Element is supposed to be SDD2Error, but some when
wrong in the generation.  So I will assume there is something wrong
with the WSDL, but I can not figure out what is wrong.  I have
included my WSDL for you, and I am hoping someone will give me some
help here.


Rob

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




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

Re: Problem with the namespace prefix in Axis

[Anne Thomas Manes]

As long as the prefix maps to the correct namespace URI, the messages
are semantically identical. Your handler should be to handle any
prefix string.

Anne

On 2/27/07, anup bansal <[EMAIL PROTECTED]> wrote:

Hi All,

I am using Axis 1.4 for accessing a third party weservice.  I am able to
connect to the service and receive the response.

The prefixes in the response I receive is not the same as the the one sent
by the service. The difference lies in the name space prefix values.
As a result the response header is not being validated.

Axis is replacing the namespace prefixes with its own prefix values.
For e.g. the prefix value sent for the SOAP Body is soap12, where as Axis
converts it into soapenv.

Is this a bug in Axis or is there a way to get around this problem? Can you
please help?

Regards,
Anup

 
 Here's a new way to find what you're looking for - Yahoo! Answers




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

Re: Issue with rpc/literal wsdl processing

[Anne Thomas Manes]

Small correction:

On 2/26/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:

hi.
please see the issue
https://issues.apache.org/jira/browse/AXIS2-2246

For rpc/literal messages, we have to generate the wrapper elements. i.e we
have to generate an outer element with local part equals to operation name
and namespace equals to operation target name space.


*** The namespace must be equal to the value specified in the
*** namespace attribute in the  definition in the binding.
***
*** e.g., 
***
*** (that's why this attribute is not supposed to be used when style="document")
***


But the part accesser
element should not be namespace qualified.

When generating the code first we generate the Element in normal way.
Lets say we have an message as follows and we generated an element like this






   








After that
1. if there is no schema then create new schema and put the element.
 In this case, we can set the
'elementFormDefault="unqualified"' and put both part1 and
part2 to no namespace.
2. if there is an schema with the same target name space then add the
element to the existing schema.
 in this case, we have to add the generated element to existing
schema and  if the existing schema has elementFormDefault="qualified" then
the both part1 and part2 automatically assigned to the same target name as
the 'echo' element. (But this is totally wrong)

Can someone please sudjest a solution for this? How can we make
part1 and part2 unqualified in latter case?


*** Add a form attribute to the element definitions:
***
*** form="unqualified"
***
*** You should do this in either case.

Anne




--
Amila Suriarachchi,
WSO2 Inc.


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

Re: problems axis newbie!!! - The method fromOM

[Anne Thomas Manes]

I've raised this issue before, but it never seems to get resolved.
Note that the generated WSDL is document style, but the 
definitions include a namespace attribute. This should not be the
case. The namespace attribute should be generated only for RPC style.

Meanwhile -- John -- can you tell us how you invoke wsdl2java?

Anne

On 2/14/07, John McCosker <[EMAIL PROTECTED]> wrote:

Hi I have an ant script which generates a wsdl from a class I created,
thw wsdl is generated fine.

I then generate web service skeletons from the wsdl,
of which I get this message,

[wsdl2java] (Location of error
unknown)org.apache.xml.utils.URI$MalformedURIException: Cannot
initialize URI with empty parameters
[wsdl2java] (Location of error
unknown)org.apache.xml.utils.URI$MalformedURIException: Cannot
initialize URI with empty parameters

when I pull my generated classes into my ide I get these errors,
Severity and DescriptionPathResourceLocation
Creation Time   Id
The method fromOM(OMElement, Class, Map) is undefined for the
type EnterShowroomMessageReceiverInOut  
Axis_ant_generated/src/com/cloverjcoverage/main 
EnterShowroomMessageReceiverInOut.java  line
68  1171471798672   5859

The method fromOM(OMElement, Class, Map) is undefined for
the type EnterShowroomMessageReceiverInOut  
Axis_ant_generated/src/com/cloverjcoverage/main 
EnterShowroomMessageReceiverInOut.java  line
47  1171471798672   5857

The method toEnvelope(SOAPFactory, BuyCarResponse, boolean) is
undefined for the type
EnterShowroomMessageReceiverInOut   
Axis_ant_generated/src/com/cloverjcoverage/main 
EnterShowroomMessageReceiverInOut.java  line
76  1171471798672   5860

The method toEnvelope(SOAPFactory, GetInvoiceResponse, boolean) is
undefined for the type
EnterShowroomMessageReceiverInOut   
Axis_ant_generated/src/com/cloverjcoverage/main 
EnterShowroomMessageReceiverInOut.java  line
55  1171471798672   5858


I have included the class i generated the wsdl from, and the wsdl itself,
I don't have any xsd's should I? if so can I generate them, I'm a bit
confused here.

package com.cloverjcoverage.main;

import com.cloverjcoverage.customer.Customer;
import com.cloverjcoverage.dto.DTO;
import com.cloverjcoverage.dto.DTOGolfGtiDetails;
import com.cloverjcoverage.dto.DTOGolfPlusDetails;
import com.cloverjcoverage.dto.DTOPassatDetails;
import com.cloverjcoverage.dto.DTOPoloDetails;
import com.cloverjcoverage.orders.Invoice;
import com.cloverjcoverage.orders.MyInvoice;
import com.cloverjcoverage.orders.MyOrder;
import com.cloverjcoverage.orders.Order;
import com.cloverjcoverage.specs.CustomSpec;
import com.cloverjcoverage.specs.GolfGtiCustomSpec;
import com.cloverjcoverage.specs.GolfPlusCustomSpec;
import com.cloverjcoverage.specs.PassatCustomSpec;
import com.cloverjcoverage.specs.PoloCustomSpec;

public class EnterShowroom {

private String showroom;

public EnterShowroom(){

}

public EnterShowroom(String showroom){
this.showroom=showroom;
}

private DTO selectCar(String car, boolean withCustomSpec){
DTO dto = null;
if(car.equals("Passat")){
if(withCustomSpec){
dto = new 
DTOPassatDetails(createCustomSpec("Passat"));
}else{
dto = new DTOPassatDetails();
}
}else if(car.equals("Golf Plus")){
if(withCustomSpec){
dto = new DTOGolfPlusDetails(createCustomSpec("Golf 
Plus"));
}else{
dto = new DTOGolfPlusDetails();
}
}else if(car.equals("Golf gti")){
if(withCustomSpec){
dto = new DTOGolfGtiDetails(createCustomSpec("Golf 
gti"));
}else{
dto = new DTOGolfGtiDetails();
}
}else{
if(withCustomSpec){
dto = new 
DTOPoloDetails(createCustomSpec("Polo"));
}else{
dto = new DTOPoloDetails();
}
}
return dto;
}

private CustomSpec createCustomSpec(String car){

if(car.equals("Passat")){
PassatCustomSpec spec = new PassatCustomSpec();

return spec;
}else if(car.equals("Golf Plus")){
GolfPlusCustomSpec spec = new GolfPlusCustomSpec();

return spec;

}else if(car.equals("Golf gti")){
GolfGtiCustomSpec spec = new GolfGtiCustomSpec();

return spec;

}else if(car.equals("Polo")){
  

Re: Generating wsdl for url

[Anne Thomas Manes]

Either deploy the service using the RPC message receiver, or write
your own WSDL and add it to the META-INF directory.

Anne

On 2/13/07, John McCosker <[EMAIL PROTECTED]> wrote:

Hi I'm using Axis2 and I have deployed a web service.
I am now trying to generate client stubs but I am getting the
following error when doing ?wsdl in the browser address bar,

Unable to generate WSDL for this
serviceIf you wish Axis2 to automatically
generate the WSDL, then please use one of the RPC message receivers
for the service(s)/operation(s) in services.xml. If you have added a
custom WSDL in the META-INF directory, then please make sure that the
name of the service in services.xml (/serviceGroup/service/@name) is
the same as in the custom wsdl's service name
(/wsdl:definitions/wsdl:service/@name). 

What is the work around for this?

Kind Regards,

JP.

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




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

Re: Latest Axis2 performance benchmarking.... this time against XFire!

[Anne Thomas Manes]

It should be "with maybe the exception of trading floors", which means
that Axis2 should deliver sufficient perfromance to support most
application, except perhaps for trading applications, i.e.,
applications with exceptionally high performance and scalability
requirements.

On 1/31/07, robert lazarski <[EMAIL PROTECTED]> wrote:

Very good news indeed!

There is one sentence in the presentation that is not clear:

"with may be the exception of trading floors"  . As a native english
speaker I can't parse that ;-) . Otherwise all the points made were
clear and concise to this reader - good going !

Robert

On 1/30/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> FYI
>
> http://wso2.org/library/588
>
> The good news: Axis2/ADB is at least 40% faster than XFire/JAXB.
> The other news: we need to tune our own JAXB its very slow on
> large messages.
>
> Paul
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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




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

Re: [axis2] simplecontent that refers itself - is that valid?

[Anne Thomas Manes]

Not valid.

On 1/31/07, Eric Deshayes <[EMAIL PROTECTED]> wrote:

Hi,
I am not sure of the validity of that xsd type.



  

  

  

Thanks for answering me...
Eric





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

Re: not able to retrieve attribute (elements work fine)

[Anne Thomas Manes]

Danny,

You don't just need the namespace declaration, you also must use the
prefix with the attribute. e.g.:

   http://jxdm.ws.doc.state.sc.us";>
 Rebecca
 Mace
 Smith
   

Are you certain that XMLBeans returns the correct XML?

Anne

On 1/22/07, Danny Lin <[EMAIL PROTECTED]> wrote:

Thank you Anne and Dennis for looking into this problem. However, I
wonder if it is a problem with Axis2, not XMLBenas because I added the
logger and on the server side the  XML generated
contains the namespace for the "personNameCommentText" attribute in the
 element. But, by the time the client receives the
document, it doesn't have namespace any more. The client and the server
both were generated from the same WSDL at the same time. Any suggestions
as what else I can try out?

Thanks again.

Danny


-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 20, 2007 6:29 PM
To: axis-dev@ws.apache.org
Subject: Re: not able to retrieve attribute (elements work fine)

Duh! Of course, my bad. This has caught me before, I'm sad to say - it
just somehow seems unnatural for attributes to be put into a namespace
without anything special being done to cause it.

  - Dennis

Anne Thomas Manes wrote:
> attributeFormDefault only applies to local attributes (those defined
> within a complexType). But this attribute is defined as a global
> attribute (a direct child of the ). All entities (elements,
> attributes, and types) that are defined as global belong to the
> targetNamespace.
>
> Anne
>
> On 1/20/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
>> Here's the start of jxdm.xsd:
>>
>> http://www.w3.org/2001/XMLSchema";
>> targetNamespace="http://jxdm.ws.doc.state.sc.us";
>> xmlns="http://jxdm.ws.doc.state.sc.us";
>> elementFormDefault="qualified">
>>
>> This does not specify attributeFormDefault="qualified", so why are
>> you saying the attribute needs to be namespace qualified?
>>
>>   - Dennis
>>
>> Anne Thomas Manes wrote:
>> > The attribute is defined as a global attribute in the jxdm.xsd,
>> > therefore it must be namespace qualified. The error is in the
>> > message generated by the server.
>> >
>> > Anne
>> >
>> > On 1/20/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
>> >> I think this is the wrong way around, Anne. It looks to me like
>> >> the attribute is not namespace qualified in the schema (it's
>> >> defined in jxdm.xsd, not in the WSDL schema which has
>> >> attributeFormDefault="qualified"), so the response being sent from
>> the
>> >> server is good and the error is apparently in the client-side
>> generated
>> >> code.
>> >>
>> >> Either way, it looks like a problem with the XMLBeans code
>> >> generation for Axis2. That's assuming you're using the same exact
>> >> WSDL and
>> schema
>> >> for both client and server code generation - you might want to
>> >> double-check that to be sure. Then can you try this out using the
>> Axis2
>> >> 1.1.1 release? There were a number of bug fixes in that, and it's
>> >> possible this problem has been corrected.
>> >>
>> >>   - Dennis
>> >>
>> >> Dennis M. Sosnoski
>> >> SOA and Web Services in Java
>> >> Training and Consulting
>> >> http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA
>> >> +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>> >>
>> >>
>> >>
>> >> Anne Thomas Manes wrote:
>> >> > Danny,
>> >> >
>> >> > According to your schema, the attribute should be namespace
>> qualified.
>> >> > Hence the message you get back from the service should look like
>> this:
>> >> >
>> >> > > >> > xmlns:ns1="http://jxdm.ws.doc.state.sc.us";
>> >> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>> >> >  Rebecca
>> >> >  Mace
>> >> >  Smith
>> >> > 
>> >> >
>> >> > The reason why your request for the comment text returns null is

>> >> > because it's looking for an attribute called
>> >> > ns1:personNameCommentText. Since that attribute doesn't exist,
>> >> > it returns null.
>> >> >
>> >> > If you implemented the service using Axis2 and XMLBeans, then I

Re: not able to retrieve attribute (elements work fine)

[Anne Thomas Manes]

attributeFormDefault only applies to local attributes (those defined
within a complexType). But this attribute is defined as a global
attribute (a direct child of the ). All entities (elements,
attributes, and types) that are defined as global belong to the
targetNamespace.

Anne

On 1/20/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:

Here's the start of jxdm.xsd:

http://www.w3.org/2001/XMLSchema";
targetNamespace="http://jxdm.ws.doc.state.sc.us";
xmlns="http://jxdm.ws.doc.state.sc.us";
elementFormDefault="qualified">

This does not specify attributeFormDefault="qualified", so why are you
saying the attribute needs to be namespace qualified?

  - Dennis

Anne Thomas Manes wrote:
> The attribute is defined as a global attribute in the jxdm.xsd,
> therefore it must be namespace qualified. The error is in the message
> generated by the server.
>
> Anne
>
> On 1/20/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
>> I think this is the wrong way around, Anne. It looks to me like the
>> attribute is not namespace qualified in the schema (it's defined in
>> jxdm.xsd, not in the WSDL schema which has
>> attributeFormDefault="qualified"), so the response being sent from the
>> server is good and the error is apparently in the client-side generated
>> code.
>>
>> Either way, it looks like a problem with the XMLBeans code generation
>> for Axis2. That's assuming you're using the same exact WSDL and schema
>> for both client and server code generation - you might want to
>> double-check that to be sure. Then can you try this out using the Axis2
>> 1.1.1 release? There were a number of bug fixes in that, and it's
>> possible this problem has been corrected.
>>
>>   - Dennis
>>
>> Dennis M. Sosnoski
>> SOA and Web Services in Java
>> Training and Consulting
>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>>
>> Anne Thomas Manes wrote:
>> > Danny,
>> >
>> > According to your schema, the attribute should be namespace qualified.
>> > Hence the message you get back from the service should look like this:
>> >
>> > > > xmlns:ns1="http://jxdm.ws.doc.state.sc.us";
>> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>> >  Rebecca
>> >  Mace
>> >  Smith
>> > 
>> >
>> > The reason why your request for the comment text returns null is
>> > because it's looking for an attribute called
>> > ns1:personNameCommentText. Since that attribute doesn't exist, it
>> > returns null.
>> >
>> > If you implemented the service using Axis2 and XMLBeans, then I think
>> > this is a bug in XMLBeans.
>> >
>> > Anne
>> >
>> > On 1/19/07, Danny Lin <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> I added more logging on the web service server end just to see what's
>> >> going
>> >> on. The document that was prepared contains the namespace in the
>> >> attribute.
>> >> However, at the point where the client received, the namespace in the
>> >> attribute is gone. Can someone please help? I feel that has something
>> >> to do
>> >> with the WSDL which I do not have very good understanding.
>> >>
>> >> Thanks.
>> >>
>> >> Danny
>> >>
>> >>
>> >>  
>> >>  From: Danny Lin
>> >> Sent: Friday, January 19, 2007 6:24 PM
>> >> To: axis-dev@ws.apache.org; axis-user@ws.apache.org
>> >> Subject: not able to retrieve attribute (elements work fine)
>> >>
>> >>
>> >>
>> >>
>> >> I am attaching my WSDL and my schema to this message. Hopefully
>> >> someone with
>> >> good knowledge can spot where I did wrong here. I am using XMLBeans
>> >> binding
>> >> (version 2.2). My Axis2 version 1.1.
>> >>
>> >> Basically I am having problem in getting the "personNameCommentText"
>> >> attribute in the "PersonAlternateName" element.
>> >>
>> >> After my webservice is called, the server returns:
>> >> ...
>> >> > >> xmlns:ns1="http://jxdm.ws.doc.state.sc.us";>
>> >>   Rebecca
>> >>   Mace
>> >>   Smith
>> >

Re: not able to retrieve attribute (elements work fine)

[Anne Thomas Manes]

The attribute is defined as a global attribute in the jxdm.xsd,
therefore it must be namespace qualified. The error is in the message
generated by the server.

Anne

On 1/20/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:

I think this is the wrong way around, Anne. It looks to me like the
attribute is not namespace qualified in the schema (it's defined in
jxdm.xsd, not in the WSDL schema which has
attributeFormDefault="qualified"), so the response being sent from the
server is good and the error is apparently in the client-side generated
code.

Either way, it looks like a problem with the XMLBeans code generation
for Axis2. That's assuming you're using the same exact WSDL and schema
for both client and server code generation - you might want to
double-check that to be sure. Then can you try this out using the Axis2
1.1.1 release? There were a number of bug fixes in that, and it's
possible this problem has been corrected.

  - Dennis

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



Anne Thomas Manes wrote:
> Danny,
>
> According to your schema, the attribute should be namespace qualified.
> Hence the message you get back from the service should look like this:
>
>  xmlns:ns1="http://jxdm.ws.doc.state.sc.us";
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>  Rebecca
>  Mace
>  Smith
> 
>
> The reason why your request for the comment text returns null is
> because it's looking for an attribute called
> ns1:personNameCommentText. Since that attribute doesn't exist, it
> returns null.
>
> If you implemented the service using Axis2 and XMLBeans, then I think
> this is a bug in XMLBeans.
>
> Anne
>
> On 1/19/07, Danny Lin <[EMAIL PROTECTED]> wrote:
>>
>>
>> I added more logging on the web service server end just to see what's
>> going
>> on. The document that was prepared contains the namespace in the
>> attribute.
>> However, at the point where the client received, the namespace in the
>> attribute is gone. Can someone please help? I feel that has something
>> to do
>> with the WSDL which I do not have very good understanding.
>>
>> Thanks.
>>
>> Danny
>>
>>
>>  
>>  From: Danny Lin
>> Sent: Friday, January 19, 2007 6:24 PM
>> To: axis-dev@ws.apache.org; axis-user@ws.apache.org
>> Subject: not able to retrieve attribute (elements work fine)
>>
>>
>>
>>
>> I am attaching my WSDL and my schema to this message. Hopefully
>> someone with
>> good knowledge can spot where I did wrong here. I am using XMLBeans
>> binding
>> (version 2.2). My Axis2 version 1.1.
>>
>> Basically I am having problem in getting the "personNameCommentText"
>> attribute in the "PersonAlternateName" element.
>>
>> After my webservice is called, the server returns:
>> ...
>> > xmlns:ns1="http://jxdm.ws.doc.state.sc.us";>
>>   Rebecca
>>   Mace
>>   Smith
>> 
>> ...
>>
>> In my client side, I have code that looks like this:
>> ...
>> String commentText = al.getPersonNameCommentText();
>> log.debug("XML: "+al);
>> ...
>>
>> The output is:
>> > xmlns:ns1="http://jxdm.ws.doc.state.sc.us";
>> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>>   Rebecca
>>   Mace
>>   Smith
>> 
>>
>> BUT, the commentText is null, not the "A" that I am expecting!!
>>
>> Then, I just want to see what the client is expecting for the XML to
>> look
>> like, I added the code:
>> ...
>> al.setPersonNameCommentText("R");
>> log.debug("XML after change:\n"+al);
>> ...
>>
>> Now the output added a namespace to the personNameCommentText.
>> > xmlns:ns1="http://jxdm.ws.doc.state.sc.us";
>> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>>   Rebecca
>>   Mace
>>   Smith
>> 
>>
>> And, if I call getPersonNameCommentText(), I am getting "R".
>>
>> Any help is greatly appreciated.
>>
>> Danny
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

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




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

Re: not able to retrieve attribute (elements work fine)

[Anne Thomas Manes]

Danny,

According to your schema, the attribute should be namespace qualified.
Hence the message you get back from the service should look like this:

http://jxdm.ws.doc.state.sc.us";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
 Rebecca
 Mace
 Smith


The reason why your request for the comment text returns null is
because it's looking for an attribute called
ns1:personNameCommentText. Since that attribute doesn't exist, it
returns null.

If you implemented the service using Axis2 and XMLBeans, then I think
this is a bug in XMLBeans.

Anne

On 1/19/07, Danny Lin <[EMAIL PROTECTED]> wrote:



I added more logging on the web service server end just to see what's going
on. The document that was prepared contains the namespace in the attribute.
However, at the point where the client received, the namespace in the
attribute is gone. Can someone please help? I feel that has something to do
with the WSDL which I do not have very good understanding.

Thanks.

Danny


 
 From: Danny Lin
Sent: Friday, January 19, 2007 6:24 PM
To: axis-dev@ws.apache.org; axis-user@ws.apache.org
Subject: not able to retrieve attribute (elements work fine)




I am attaching my WSDL and my schema to this message. Hopefully someone with
good knowledge can spot where I did wrong here. I am using XMLBeans binding
(version 2.2). My Axis2 version 1.1.

Basically I am having problem in getting the "personNameCommentText"
attribute in the "PersonAlternateName" element.

After my webservice is called, the server returns:
...
http://jxdm.ws.doc.state.sc.us";>
  Rebecca
  Mace
  Smith

...

In my client side, I have code that looks like this:
...
String commentText = al.getPersonNameCommentText();
log.debug("XML: "+al);
...

The output is:
http://jxdm.ws.doc.state.sc.us";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
  Rebecca
  Mace
  Smith


BUT, the commentText is null, not the "A" that I am expecting!!

Then, I just want to see what the client is expecting for the XML to look
like, I added the code:
...
al.setPersonNameCommentText("R");
log.debug("XML after change:\n"+al);
...

Now the output added a namespace to the personNameCommentText.
http://jxdm.ws.doc.state.sc.us";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
  Rebecca
  Mace
  Smith


And, if I call getPersonNameCommentText(), I am getting "R".

Any help is greatly appreciated.

Danny



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

Re: FW: Needs help in writing WSDL

[Anne Thomas Manes]

.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/3.0.3/proxy/nibrs_misc/1.0.1] and systemId
[jxdm/3.0.3/proxy/nibrs_misc/1.0.1/nibrs_misc.xsd]
[wsdl2java] Dec 27, 2006 12:03:26 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/3.0.3/proxy/xsd/1.0] and systemId
[jxdm/3.0.3/proxy/xsd/1.0/xsd.xsd]
[wsdl2java] Dec 27, 2006 12:03:26 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/3.0.3/proxy/ncic_2000/1.0.2] and systemId
[jxdm/3.0.3/proxy/ncic_2000/1.0.2/ncic_2000.xsd]
[wsdl2java] Dec 27, 2006 12:03:26 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/3.0.3/proxy/census/1.0] and systemId
[jxdm/3.0.3/proxy/census/1.0/census.xsd]
[wsdl2java] Dec 27, 2006 12:03:26 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/nibrs_misc/1.0.1] and systemId
[jxdm/nibrs_misc/1.0.1/nibrs_misc.xsd]
[wsdl2java] Dec 27, 2006 12:03:26 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/3.0.3] and systemId [jxdm/3.0.3/jxdm.xsd]
[wsdl2java] Dec 27, 2006 12:03:27 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/ncic_2000/1.0.2] and systemId
[jxdm/ncic_2000/1.0.2/ncic_2000.xsd]
[wsdl2java] Dec 27, 2006 12:03:27 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
[wsdl2java] INFO: Resolving schema with publicId
[http://www.it.ojp.gov/jxdm/census/1.0] and systemId
[jxdm/census/1.0/census.xsd]

BUILD FAILED
C:\workspace\scdc-ws\build.xml:40:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException



-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 27, 2006 9:14 AM
To: axis-user@ws.apache.org
Subject: Re: Needs help in writing WSDL

Danny,

Can you provide the schema for ? My assumption (based on this
document snipet) is that  is defined as an element rather than
a type. You need to look into the schema to find out what type you
should be returning. e.g.:



But given that you have the schema already defined, I recommend that you
use the schema elements and types rather than trying to define new ones,
e.g.:














 
 






Anne

On 12/26/06, Danny Lin <[EMAIL PROTECTED]> wrote:
>
>
> I have a schema that will validate something like this:
> 
> 
> John
> Middle
> Doe
> 
> 
>
> I want to be able to give a last name and receive a list of people
> with the same last name. Please see the part of WSDL below in defining

> the operations. Can I reference the  type in my WSDL this way?

> How do I allow a list of  to be returned? Am I heading the
right direction?
> Thanks.
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
>
>

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


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


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




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

Re: Questions about "Unsupported content Simple Type Union"

[Anne Thomas Manes]

It sounds like the schema defines the type more than once.

On 11/2/06, Jose Manuel Valladares Pernas <[EMAIL PROTECTED]> wrote:

When I use xmlbeans I get an exception because of
"Duplicate global type":

Duplicate global type:
[EMAIL PROTECTED]://www.opentravel.org/OTA/2003/05
(Original global type found in file:
xsd/FS_OTA_HotelAvailRS.xsd)


Here it is the whole exception stacktrace:

[EMAIL PROTECTED]:~/src/MiraiOTA/axis_2/OTA_HotelAvail>
/usr/local/axis2-1.1-SNAPSHOT/bin/wsdl2java.sh -uri
/home/jmanuel/src/MiraiOTA/axis_2/OTA_HotelAvail/OTA_HotelAvail.wsdl
-o
/home/jmanuel/src/MiraiOTA/axis_2/OTA_HotelAvail/axis2/
-d xmlbeans
 Using AXIS2_HOME:   /usr/local/axis2-1.1-SNAPSHOT
 Using JAVA_HOME:   /usr/local/jdk1.5.0_06
Retrieving schema at 'xsd/FS_OTA_HotelAvailRQ.xsd',
relative to
'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_HotelAvail/'.
Retrieving schema at 'xsd/FS_OTA_HotelAvailRS.xsd',
relative to
'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_HotelAvail/'.
Nov 2, 2006 12:19:39 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
INFO: Resolving schema with publicId
[http://www.opentravel.org/OTA/2003/05] and systemId
[xsd/FS_OTA_HotelAvailRS.xsd]
Nov 2, 2006 12:19:39 PM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
INFO: Resolving schema with publicId
[http://www.opentravel.org/OTA/2003/05] and systemId
[xsd/FS_OTA_HotelAvailRQ.xsd]
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82)
... 3 more
Caused by: java.lang.RuntimeException:
org.apache.xmlbeans.XmlException:
/usr/local/axis2-1.1-SNAPSHOT/xsd/FS_OTA_HotelAvailRQ.xsd:89:1:
error: sch-props-correct.2: Duplicate global type:
[EMAIL PROTECTED]://www.opentravel.org/OTA/2003/05
(Original global type found in file:
xsd/FS_OTA_HotelAvailRS.xsd)
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:248)
... 8 more
Caused by: org.apache.xmlbeans.XmlException:
/usr/local/axis2-1.1-SNAPSHOT/xsd/FS_OTA_HotelAvailRQ.xsd:89:1:
error: sch-props-correct.2: Duplicate global type:
[EMAIL PROTECTED]://www.opentravel.org/OTA/2003/05
(Original global type found in file:
xsd/FS_OTA_HotelAvailRS.xsd)
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:166)
... 8 more


Any ideas?
   Manuel Valladares


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


> Can you use xmlbeans databinding?
>
> -- dims
>
> On 10/31/06, Jose Manuel Valladares Pernas
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> > I am using axis 2 snapshot from today (October
> 11th
> > 2006) to generate the java classes from a wsdl
> file
> > that references several schema classes.
> >
> > I am using the OTA specification for hotel
> > communicaions.
> >
> > I got the known issue of Unsupported content
> Simple
> > Type Union in one of the schemas.
> >
> > I am using the adb data binding.
> >
> > I would like to know if this bug is going to be
> fixed
> > soon, and also if there is any recommendation
> about
> > changing the Union for another construct.
> >
> > This wsdl and schemas work fine in axis 1. The
> classes
> > are produced and
> >
> > If you want I can send you the files that I am
> using.
> >
> > Thank you very much for your help,
> >Manuel Valladares
> >
> > 

Re: axis2 1.1

[Anne Thomas Manes]

RC1 was released on Oct 9:

Download locations :
* binary and source distributions -
http://people.apache.org/~thilina/axis2/1.1-RC1/

* jars
http://people.apache.org/~thilina/maven/org.apache.axis2/jars/

* mars (addressing and SOAP monitor)
http://people.apache.org/~thilina/maven/org.apache.axis2/mars/

* Tools
http://people.apache.org/~thilina/axis2/1.1-RC1/eclipse_codegen_plugin_1.1-RC1http://people.apache.org/~thilina/axis2/1.1-RC1/idea_codegen_plugin_1.1-RC1/

On 10/20/06, Tony Dean <[EMAIL PROTECTED]> wrote:

Hi,

I thought there were plans to do a release candidate for 1.1... RC1, RC2?

Is such a candidate available?

Thanks.

Tony Dean
SAS Institute Inc.
919.531.6704
[EMAIL PROTECTED]

SAS... The Power to Know
http://www.sas.com


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




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

Re: Bean Serialization

[Anne Thomas Manes]

Willem,

You should send this type of user question to the axis-user list
rather than to the axis-dev list.

As a starting point, I recommend you read these documents:
http://ws.apache.org/axis/java/client-side-axis.html
http://ws.apache.org/axis/java/user-guide.html

You should also find these articles helpful:
http://users.skynet.be/pascalbotte/rcx-ws-doc/seiadvanced.htm
http://info.borland.com/techpubs/jbuilder/jbuilder2005/websvcs/wsdl/wsdl-employee-tutorial.html

You're easiest option is to generate a client stub from the service's
WSDL using the WSDL2Java utility.

Anne

On 10/20/06, Willem Liu <[EMAIL PROTECTED]> wrote:



Hi,

I'm new to Axis Soap. I have made a Soap webservice with axis and a Soap
client which can communicate. But now I need to create a client which can
send serialized objects. But after a long search on the web I still haven't
found anything which can help me further.
The following code is the Soap client one I have now.

Integer i1 = new Integer(1);
Integer i2 = new Integer(2);
call.setTargetEndpointAddress(url);
call.setOperationName(new QName("add", "add"));
call.addParameter("num1", XMLType.XSD_INT, ParameterMode.IN);

call.addParameter("num2", XMLType.XSD_INT, ParameterMode.IN);
call.setReturnType(XMLType.XSD_INT);

Integer ret = null;
try {
  //Call the SOAP Service with i1 and i2 as arguments.
  ret = (Integer) call.invoke(new Object[] {i1, i2});
}
catch (RemoteException ex2) {
  //If connection to SOAP Service failes.
  System.out.println("Remote Exception");
  ex2.printStackTrace();
}

What I would like to try is to have a Bean which stores the Integers and
then I want to serialize this object and send it to the Soap Webservice.
Could anyone help me out on modifying the code so that it can do that or
give me pointers on how to do it?

Regards,

Willem Liu



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

Re: issue-clarification 'incorrect local element definition with elementFormDefault=qualified' or not ?

[Anne Thomas Manes]

There are a great many bugs in Axis 1.2RC.

On 10/19/06, Andreas Schöller <[EMAIL PROTECTED]> wrote:


Am 19.10.2006 um 18:51 schrieb Anne Thomas Manes:

> Please try it with Axis 1.4.

Hello Anne Thomas Manes,

thanks for your advice, and i'd really like to do so, but i simply
can't. I could suggest your advice to the people at uni-leipzig which
run the service. My prognosis on what their reaction might be, is
smth. like : 'Hello, is there an issue with the axis release we use
in our production system and who's affected by this (Java-, .NET- /
PHP- / Python-clients in that order) ? Ahh, so it's unclear if
there's a real issue - surely we won't touch/upgrade under these
circumstances.'. Here is the crucial point where i need clarification
from your side. Right now my position to ask them for a upgrade is
obviously not too solid - as currently nobody is about to say if
somethings is really broken here, except J. Boverhof, who did a clear
statement. Things would be much easier as soon as one of your team
would confirm that the release-candidate 1.2 has/had some issue and
for sure that things will be great for all current users of the
Wortschatz-Service as soon as they upgrade their site with axis-
release 1.4. ?
Maybe i have been not clear enough - i don't use axis-libs directly -
i'm trying to use axis-generated WSDL and SOAP-responses from python
- so i guess i'm somehow in between the sheets ;-)
Would it be possible that you pls. check your bug-tracker for issues
which might be connected to what was found, keeping in mind that you
won't find any complaints from axis-clients as these are definitely
not affected - proven by the fact, that the Java-client-Apps provided
by uni-leipzip perform well. The complaining side might rather be
PHP-, Perl-, Python-, younameit-clients.

thx & best regards, A. Schoeller





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




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

Re: issue-clarification 'incorrect local element definition with elementFormDefault=qualified' or not ?

[Anne Thomas Manes]

Please try it with Axis 1.4.

On 10/18/06, Andreas Schöller <[EMAIL PROTECTED]> wrote:

Hello axis developers,

while trying to access a axis-driven webservice using the ZSI-modul
from python i ran into some problems. I reported back to the python-
developing team as i believed the cause of trouble to be somewhere
inside the python code that processes/deserializes the SOAP-answer.
Joshua Boverhof reviewed my bug-report and explained to me that the
generated SOAP-answer is incorrect according to the SOAP-specs. He
suggested to file another bug-report to you. Before i'll do so, i
follow the advice from the your website and ask here if this issue is
already fixed in the current axis-release. The axis-engine on the
server-side was/is this :

taken from the WSDL-description.
I put in here the relevant parts and leave out some lines python-code.
The full bug-report is here [ https://sourceforge.net/tracker/?
func=detail&atid=387667&aid=1564784&group_id=26590 ]. The team that
developed the Wortschatz-Service at the uni-leipzig provides a java-
client-app which can handle the SOAP-answers without any problem. The
request/response-xml grabbed with tcpdump is included.

Thanks for reviewing and pls cc to my address 'cos i'd like to
unsubscribe from the list soon and i've not yet found a html-
interface for it.

Greets, A. Schoeller



> Comment By: Joshua Boverhof (boverhof)
>
Date: 2006-10-18 18:16

Message:
Logged In: YES
user_id=711996

I hate pointing out that it's a bug in Axis but here goes:

I get the same exception, ZSI appears to correctly generate this code:

 class DataMatrix_Def(ZSI.TCcompound.ComplexType, TypeDefinition):
 schema = "urn:Baseform"
 type = (schema, "DataMatrix")
 def __init__(self, pname, ofwhat=(), attributes=None,
extend=False,
restrict=False, **kw):
 ns = ns0.DataMatrix_Def.schema
 TClist = [GTD("http://
datatypes.webservice.wortschatz.uni_leipzig.de","DataVector",lazy=False)
(pname=(ns,"dataVectors"), aname="_dataVectors", minOccurs=1,
maxOccurs="unbounded", nillable=False, typed=False, encoded=kw.get
("encoded"))]

However Axis is putting the local element declaration "DataVector" in
the
namespace that the type is defined, which is incorrect.

So ZSI is doing the "correct" thing.

Axis is just sloppy about how it handles instance namespacing for local
element declarations when "elementFormDefault" is true.

I'd really appreciate if you'd file a bug report for Axis, you could
just copy and
paste bug report.

Here is a reference, I checked to make sure:
"Definitive XML Schema", Priscilla Walmsley pg. 445-447



--



Summary: ZSI latest fails on parsing SOAP Response

Service-Name : Baseform
wdsl-used : http://wortschatz.uni-leipzig.de/axis/services/Baseform?wsdl
overview here : http://wortschatz.uni-leipzig.de/axis/servlet/
ServiceOverviewServlet
hmtl-frontend : http://wortschatz.uni-leipzig.de/


import sys

from ZSI import TC
from BaseformService_services import *
from BaseformService_services_types import *

loc = BaseformServiceLocator()
kw = { 'tracefile' : sys.stdout, "auth" : ( 1 , "anonymous" ,
"anonymous" ) }
portType = loc.getBaseform(**kw)

class Holder:pass

# // Version A
#
dataRow = ns1.DataVector_Def( "DataVector").pyclass()
dataRow._dataRow = ["Wort","rannte"]

matrix = ns0.DataMatrix_Def("DataMatrix").pyclass()
matrix._dataVectors = []
matrix._dataVectors.append( dataRow )

oRP = ns0.RequestParameter_Def("RequestParameter").pyclass()

oRP._corpus = "de"
oRP._parameters = matrix
req = executeRequest()
req._objRequestParameters = oRP
#
# // end of Version A

response = portType.execute( req )
print response
sys.exit('not dead ?')



...

de


Wort
rannte



...






http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>



0.012 s


rennen
V


0
2102808448
-100







The problem seems to be around the 'result' section :

EvaluateException: Element "_dataVectors" missing from complexType
[Element trace: /soapenv:Envelope/soapenv:Body/executeResponse/
executeReturn/result]
WARNING: Failure executing file: <../../../leibzig2.py>











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




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

Re: WS-callback support in axis

[Anne Thomas Manes]

WS-Callback has not been accepted by the industry. (Only BEA
implements it.) It has been superceded by WS-Addressing.

Anne

On 10/15/06, Rodrigue Butaye <[EMAIL PROTECTED]> wrote:

Hello,

Is there in Axis a support for the ws-callback protocol as defined by
BEA(http://dev2dev.bea.com/webservices/WS-CallBack-0_9.html) ?
I've read the documentation but there is no mention of callback, I've
only found a post of 2005-11-15 on the dev list with the same topic but
it was for Axis C and it's old. (Axis C didn't support callback).

Thanks by advance,
Rodrigue

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




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

Re: Error occurred while testing the CodeGen Tool

[Anne Thomas Manes]

See http://ws.apache.org/axis2/1_0/jibx/jibx-codegen-integration.html
and http://jibx.sourceforge.net/tutorial/binding-tutorial.html.
The binding file specifies how to map Java object to XML.

Anne

On 9/26/06, Evanthika Amarasiri <[EMAIL PROTECTED]> wrote:


 Hi,
 I was testing the Code Generator tool with and gave the command
"WSDL2Java.bat -uri
C:\WSO2-Projects\Axis2\Nightly_builds\axis2-std-SNAPSHOT-src\modules\samples\wsdl\Axis2SampleDocLit.wsdl
-o C:\WSDLJavaTool\output -d jibx" and I got the following exception.

 Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: jibx binding option requires -bindingfile {file
path} parameter
 at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
 at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: java.lang.RuntimeException: jibx binding option requires
-bindingfile {file path} parameter
 at
org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:52)
 at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
 ... 2 more

 Seems that the command requests the parameter -bindingfile along with jibx.
Can some one please tell me what this refers to?

 Thanks,
 Evanthika



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

Re: Axis2 1.0 beta?

[Anne Thomas Manes]

It's not a "beta" release, but it also isn't a stable,
production-quality release. Given the number of bugs, it should not
have been released as a 1.0 version.

You should wait for 1.1.

Anne

On 9/22/06, Donald Miller <[EMAIL PROTECTED]> wrote:

Thank you for replying so fast!

I appreciate it greatly...


On 9/22/06, Thilina Gunarathne <[EMAIL PROTECTED] > wrote:
> No .. It's not a beta..
>
> Thilina
>
> On 9/22/06, Donald Miller < [EMAIL PROTECTED]> wrote:
> >
> >
> > Quick question I hope you can address real fast.  I just want to be 100%
> > sure that Axis2 1.0 is not a beta release.
> >
> > Hope you can help me.
> >
> >
> >
> > Thanks!
>
>
> --
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>




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

Re: Can I expose services of a new technology as web services?

[Anne Thomas Manes]

What's the nature of your "particular technology"? If you can invoke
the technology using Java, then you should be able to use Axis to
enable it as a web service.

Anne

On 9/12/06, Domenico Caputi <[EMAIL PROTECTED]> wrote:

WJ Krpelan wrote:
> Axis is open source, just do it!
> Cheers
> Wolfgang Krpelan
>
> --- Domenico Caputi <[EMAIL PROTECTED]> wrote:
>
>
>> Hi,
>> I have a new technology that I want expose with web
>> services, using
>> Axis. Web Services that I want expose is not a java
>> class but is a
>> particular technology that executes some process. Is
>> it possible to
>> extend Axis in this sense?
>> Thanks,
>> Domenico
>>
>>
>>
> -
>
>> To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> For additional commands, e-mail:
>> [EMAIL PROTECTED]
>>
>>
>>
>
>
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
I know that Axis is open source but I haven't found documentation for my
problem.
What is the way for resolve it?
Thanks,
Domenico

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




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

Re: maxOccurs Interop Problem

[Anne Thomas Manes]

This is a bug in Axis -- please file a bug report in JIRA.

On 9/7/06, Amol Ambekar <[EMAIL PROTECTED]> wrote:





am using axis 1.4



I have a complex type element called ArrayOfString



WSDL Snippet



   

  

   







The client is C++



When the client is accessing the service it's expected soap  packet is

TestSpec



But when AXIS sends a soap Response it creates a following response



TestSpec



Can anybody Help Me .Thanks in advance.





Regards,

Amol Ambekar

Skandsoft Technologies

KnowNow!

www.skandsoft.com

+91 92235 11526






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

Re: [VOTE] Axis2 next release (Axis2 1.1)

[Anne Thomas Manes]

If you call it 1.5, then you need to be absolutely certain that it is
a solid, reliable, robust release. It doesn't matter how much new
stuff has been added -- the major issue with 1.0 was quality. I
recommend calling it 1.1. You have to prove yourselves before
agrandizing yourselves.

Anne

On 9/5/06, Chuck Williams <[EMAIL PROTECTED]> wrote:


 +1

 Chuck

 robert lazarski wrote on 09/04/2006 11:45 PM:
+1 to either 1.1 or 1.5

 Robert

 On 9/4/06, Chamil Thanthrimudalige <[EMAIL PROTECTED]> wrote:

+1

 Best Regards,
 Chamil Thanthrimudalige


 On Sep 4, 2006, at 5:50 PM, Afkham Azeez wrote:

 > +1 for Axis2 1.5
 >
 > On 9/4/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: +1 for the
 > next release. No objections for 1.5 nor for 1.1.
 >
 > Thanks,
 > ~Thilina
 >
 > On 9/4/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
 > > I have no objection of calling its as 1.5 ,
 > >
 > > btw if we do so that give us a wrong signal next Axis2 version
 > will be
 > > Axis2 2.0  ;-)
 > >
 > > Thanks
 > > Deepal
 > >
 > > Davanum Srinivas wrote:
 > >
 > > > +1 from me. Can we make it 1.5 instead of 1.1? There are just
 > too many
 > > > changes :)
 > > >
 > > > -- dims
 > > >
 > > > On 9/4/06, Deepal Jayasinghe <[EMAIL PROTECTED] > wrote:
 > > >
 > > >> Hi all;
 > > >>
 > > >> Axis2 1.0 release on 05/05/2006 and it took about four month
 > after that
 > > >> release and I think this is the good time for next release
 > (well we
 > > >> discuss this sometimes ago in the list :) ).
 > > >>
 > > >> Well we have few blockers to fix and I am sure that we can fix
 > them
 > > >> soon :)
 > > >>
 > > >> As you know there are a number of SNAPSHOT dependencies for
 > various
 > > >> projects , the problem is how to get stable release for those,
 > we can
 > > >> not release Axis2 1.1 with any SNAPSHOT dependences.
 > > >>  - Axiom
 > > >>  - jibx
 > > >>  - neethi
 > > >>  - woden
 > > >>  - XmlSchema
 > > >>
 > > >> I think we will be able to get release for axiom , neethi and
 > xmlScheam
 > > >> before Axis2 release , but not sure about other two.
 > > >>
 > > >> Any way I am +1 on releasing Axis2 1.1 on week starting form 18th
 > > >> Septembers.
 > > >>
 > > >> Any suggestions ..
 > > >>
 > > >> Thanks
 > > >> Deepal
 > > >>
 > > >>
 > > >>
 >
-
 > > >> To unsubscribe, e-mail:
[EMAIL PROTECTED]
 > > >> For additional commands, e-mail: [EMAIL PROTECTED]
 > > >>
 > > >>
 > > >
 > > >
 > >
 > > --
 > > Thanks,
 > > Deepal
 > >

 > > ~Future is Open~
 > >
 > >
 > >
 > >
 >
-
 > > To unsubscribe, e-mail:
[EMAIL PROTECTED]
 > > For additional commands, e-mail: [EMAIL PROTECTED]
 > >
 > >
 >
 >
 > --
 > "May the SourcE be with u"
 > http://webservices.apache.org/~thilina/
 > http://thilinag.blogspot.com/
 > http://www.bloglines.com/blog/Thilina
 >
 >
-
 > To unsubscribe, e-mail:
[EMAIL PROTECTED]
 > For additional commands, e-mail: [EMAIL PROTECTED]
 >
 >
 >
 >
 > --
 > Thanks
 > Afkham Azeez


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



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



--

 Chuck Williams
 Manawiz
 Principal
 V: (808)885-8688
 C: (415)846-9018
 [EMAIL PROTECTED]
 Skype: manawiz
 AIM: hawimanawiz
 Yahoo: jcwxx
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

Re: No deserializer error

[Anne Thomas Manes]

You must define a deserializer for your User type.

Anne

On 8/29/06, Rodrigo Faria <[EMAIL PROTECTED]> wrote:

I am facing a "No deserializer" error coming from Apache Axis code.

This is the installed version:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.1_01-b01 (Sun Microsystems Inc.)
Name: org/apache/axis
Implementation-Title: Apache Axis
Implementation-Version: 1.1 1021 June 13 2003
Implementation-Vendor: Apache Web Services

This was the log error:
2006-08-27 18:06:56,941 DEBUG [Servlet.Engine.Transports : 9] 
builder.AxisDIIWebServiceBuilder (AxisDIIWebServiceBuilder.java:333) - Loop: 
getUserByLogin getUserByLogin
2006-08-27 18:06:56,941 DEBUG [Servlet.Engine.Transports : 9] 
builder.AxisDIIWebServiceBuilder (AxisDIIWebServiceBuilder.java:336) - Found 
operation
2006-08-27 18:06:56,942 DEBUG [Servlet.Engine.Transports : 9] 
builder.AxisDIIWebServiceBuilder (AxisDIIWebServiceBuilder.java:338) - 
Parameters
returnParam = (QName: {http://user.dvo.core.sac.abc.com}User
name:  null
isReferenced?  true
Class: org.apache.axis.wsdl.symbolTable.DefinedType
Base?: false
Undefined?:false
isSimpleType?  false
Node:  [complexType: null]
Dims:
RefType:   null
, getUserByLoginReturn, OUT)
faults = {SACFault=Fault: name=SACFault
Message: name={http://service.ws.sac.abc.com}SACFault
Part: name=fault
typeName={http://fault.ws.sac.abc.com}SACFault}
signature = null
(inputs, inouts, outputs) = (2, 0, 1)
list = [(QName: {http://www.w3.org/2001/XMLSchema}string
name:  null
isReferenced?  true
Class: org.apache.axis.wsdl.symbolTable.BaseType
Base?: true
Undefined?:false
isSimpleType?  false
Node:  null
Dims:
RefType:   null
, clientId, IN), (QName: {http://www.w3.org/2001/XMLSchema}string
name:  null
isReferenced?  true
Class: org.apache.axis.wsdl.symbolTable.BaseType
Base?: true
Undefined?:false
isSimpleType?  false
Node:  null
Dims:
RefType:   null
, isiUserId, IN)]


2006-08-27 18:06:56,982 ERROR [Servlet.Engine.Transports : 9] 
adapter.AxisDIIWebServiceAdapter (AxisDIIWebServiceAdapter.java:137) - 
com.adp.windward.fmwk.adapter.AxisDIIWebServiceAdapter.invoke(): Remote 
Exception is an Axis Fault.; nested exception is:
 org.xml.sax.SAXException: No deserializer for 
{http://www.w3.org/2001/XMLSchema}string
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: No deserializer for 
{http://www.w3.org/2001/XMLSchema}string
faultActor:
faultNode:
faultDetail:
 {http://xml.apache.org/axis/}stackTrace: org.xml.sax.SAXException: No 
deserializer for {http://www.w3.org/2001/XMLSchema}string
 at 
org.apache.axis.encoding.DeserializerImpl.onStartElement(DeserializerImpl.java(Compiled
 Code))
 at 
org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl.java(Compiled
 Code))
 at 
org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java(Compiled
 Code))
 at 
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java(Compiled
 Code))
 at 
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java(Inlined
 Compiled Code))
 at 
org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl.java(Compiled
 Code))
 at 
org.apache.axis.encoding.ser.BeanDeserializer.startElement(BeanDeserializer.java(Compiled
 Code))
 at 
org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java(Compiled
 Code))
 at 
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java(Compiled
 Code))
 at 
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:722)
 at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
 at org.apache.axis.client.Call.invoke(Call.java:2272)
 at org.apache.axis.client.Call.invoke(Call.java:2171)
 at org.apache.axis.client.Call.invoke(Call.java:1691)


Does somebody faced this problem before? Any clues to debug this issue?

Thanks,
Rodrigo Faria


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




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

Re: [Axis2] Learning Axis & Hair Los

[Anne Thomas Manes]

Here's a tutorial on AXIOM: http://ws.apache.org/axis2/1_0/OMTutorial.html

(The developers are busy fixing bugs -- unfortunately, the
documentation will come later. But please continue to provide
constructive criticism. Perhaps you could compile a list of things you
found unintelligible and create a JIRA requesting they by improved.)

Anne

On 8/22/06, M. Goodell <[EMAIL PROTECTED]> wrote:



First of all let me preface what I am about to say by stating clearly:

I really appreciate the work that goes into open source projects like Axis.
I know this is a "labor of love" in many respects and people choose to do
this with no direct monetary compensation whatsoever. To all of you
dedicated passionate developers on Axis2 & other open source projects I'm
sure I speak for thousands when I say Thank You!!

With that said, over the past years as I have worked with various open
source projects and have found one common problem with most of them:

The problem: Documentation and reference material.

I have found Axis2 be the same way. Please allow a couple of examples:

1. In the users guide that demonstrates how to build a web service using the
Axis2s primary APIs there is the sample code

public void ping(OMElement element){} //IN-ONLY operation, just accepts the
OMElement and do some processing.
public OMElement echo(OMElement element){}//IN-OUT operation, accepts an
OMElement and // sends back the same again

The questions that popped up in my mind after reading this were:

1. What's an OMElement?
2. What's an IN-ONLY operation?
3. What's an IN-OUT operation?
etc . . .

Then below the code example is this statement:

"As you can see, the two operations are very simple and need no explanations
on what they do"

Yes, the operations in and of themselves are not complex at all but there is
some very foundational information missing here. i.e. items 1,2 & 3

It seems, to me anyway, much of the documentation assumes familiarity with
concepts and technologies used. In this case AXIOM.

2. The services.xml file example as demonstrated in the users guide is
another item I would like to point out. I have looked for the reference to
what each element is such as a DTD description etc. But no such luck. Very
frustrating! Where does one go to get this information??

Much of the documentation is assembled in this fashion. Moreover, I have
seen posts in the newsgroups about the Axis documentation being difficult to
follow and find information.

In summary, what I, and perhaps others, are asking for is a more clearly
defined, logical, orderly & complete path to learning, in this case AXIS2. I
am not afraid to read anything, I just need to know what and when. I believe
good technical documentation should supply that opportunity and road map.

Am I asking something from the open source community that simply does not,
and never will exist?

Will I need to await a text book on subject *hoping* it' not just a rehash
of material already on the web?

Do we need to spend the money on a commercial application and forget open
source? The documentation is in many cases better, hence a faster ascent up
the learning curve.

Finally, does anyone else share my frustration or do I simply need to end my
20+ career as a programmer and go work in a pet grooming shop for the rest
of my days?

(Don't answer that!)

It just seems a shame and waste to see such useful technology not used
perhaps due in large part to proper explanation and systematic exposure on
the part of those responsible for bringing it to the marketplace.

I welcome and invite others thoughts and opinions on this topic.

Respectfully,


M Goodell


 
Get your email and more, right on the new Yahoo.com




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

Re: WSDL2Java works for an invalid WSDL

[Anne Thomas Manes]

Please note that the first WSDL was not valid. You MUST NOT specify
the namespace attribute in the  elements when using
document style.

Anne

On 8/8/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:

Keith,

Can you please file a JIRA with this.

Thanks,
Chinthaka

keith chapman wrote:
> Hi,
>
> I tried using the WSDL2Java tool of axis 2 using the following WSDL's.
>
> Using the following valid WSDL it generates the java classes
>
> 
> http://org.apache.axis2/xsd";
> xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soap="
> http://schemas.xmlsoap.org/wsdl/soap/
> "
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="
> http://org.apache.axis2/"; targetNamespace=" http://org.apache.axis2/";>
>   
> http://www.w3.org/2001/XMLSchema"; xmlns:ns1="
> http://org.apache.axis2/xsd"; targetNamespace="
> http://org.apache.axis2/xsd"; elementFormDefault="qualified"
> attributeFormDefault="unqualified">
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> http://schemas.xmlsoap.org/soap/http
> " style="document"/>
> 
>   
>   
> http://www.org.apache.axis2
> "/>
>   
>   
> http://www.org.apache.axis2
> "/>
>   
> 
>   
>   
> 
>   http://127.0.0.1:8080/axis2/services/EchoService
> "/>
> 
>   
> 
>
>
>
>
> Then I deleted the message element corresponding to helloRequestMessage.
> Still it generates the classes for the following WSDL (with the
> helloRequestMessage element deleted)
>
>
>
>
> 
> http://org.apache.axis2/xsd"; xmlns:xs="
> http://www.w3.org/2001/XMLSchema"; xmlns:soap="
> http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="
> http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://org.apache.axis2/";
> targetNamespace=" http://org.apache.axis2/";>
>   
> http://www.w3.org/2001/XMLSchema"; xmlns:ns1="
> http://org.apache.axis2/xsd "
> targetNamespace="http://org.apache.axis2/xsd";
> elementFormDefault="qualified" attributeFormDefault="unqualified">
>   
> 
>   
> 
>   
> 
>   
>   
> 
>   
> 
>   
> 
>   
> 
>   
>
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> http://schemas.xmlsoap.org/soap/http";
> style="document"/>
> 
>   
>   
> http://www.org.apache.axis2
> "/>
>   
>   
> http://www.org.apache.axis2
> "/>
>   
> 
>   
>   
> 
>location="http://127.0.0.1:8080/axis2/services/EchoService
> "/>
> 
>   
> 
>
>
> Shouldn't this report an error instead of generating the java classes?
>
> Thx,
> Keith







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

Re: [Axis2]Fwd: Question regarding wsdl level imports in Axis 2 ...

[Anne Thomas Manes]

I believe your problem is caused by the  section and the
 in the service WSDL. A WSDL can have only one 
section.

Anne

On 8/7/06, Srinath Perera <[EMAIL PROTECTED]> wrote:

-- Forwarded message --
From: Vishal Deshpande <[EMAIL PROTECTED]>
Date: Aug 7, 2006 3:27 PM
Subject: Question regarding wsdl level imports in Axis 2 ...
To: [EMAIL PROTECTED]



Hello Axis team,

I am a new user of Axis 2 and would like to ask you a few questions
about it as you seem to have great understanding on the subject.

We have a scenario where we have multiple services that are to be
exposed as web-services over Tomcat server. We are trying to use Axis
for our wsdl grunt-work, but would like to have a modular wsdl design
structure.

Ideally, I would like to have the schema elements separated into a say
ServiceType.wsdl and import these in the individual service wsdls like
ServiceA.wsdl, ServiceB.wsdl and so on where I have the service
bindings defined.

So far so good. I have the wsdls coded that way and I have Axis 2
generating the correct code. However, w.r.t creating jars, I was
trying to implement a similar logic, i.e have the schema elements and
its corresponding xsb bindings in a ServiceTypes.jar and have the
services in their own respective jars. This would have reduced the
need for having the schema elements in every single service jar, as I
could have the schema element jar in a shared location. That, for some
reason, when deployed, makes tomcat to go in an infinite loop on
import.

Now we do have the services deployed on the Tomcat as application
archive, instead of exploded jars. Can we use exploded jars with Axis2
as I feel that Tomcat would be better off importing things from a
flat-file architecture rather than through a jar. However, I may be
wrong. It may just be my wsdls are incorrectly formed. ANy help in
this matter is highly appreciated.

To summarise, I guess my questions are
   1. Are the attached wsdls incorrectly formed? Syntax error or design error?
   2. Can we split wsdls in a hierarchical fashion when using Axis 2
as in the attachments?
   3. Can we have a clean separation between reusable schema elements
and service bindings in seaprate jars or do we have to package things
together in a single jar?
   4. Does Axis 2 support having more than one wsdl in a single jar?

I have attached the shcema wsdl and service wsdl for you. I would be
glad if I can get some guidance on this matter.

Thanking you for your help,
-- Vishal Deshpande

This is what the tomcat shows in its log when trying to view the service.

org.apache.axis2.description.WSDL2AxisServiceBuilder.processImports(WSDL2AxisServiceBuilder.java
:895) at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.processImports(WSDL2AxisServiceBuilder.java:895)
at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.processImports(WSDL2AxisServiceBuilder.java:895)
at 
org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:217)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(ArchiveReader.java:192)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:261)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:604)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:195)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:207)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:155)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:91)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:142)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:42)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:213)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:182)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4197)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1112)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at 
org.apache.catalina.util.LifecycleSupport.f

Re: SwA Axis2 implementation swaRef document literal

[Anne Thomas Manes]

Dims suggests you have a look at this:

http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/latest/mtom-guide.html


On 7/31/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:

Thanks Anne,

Now, I think I have the WSDL in the correct way:








  

  








Also I have the axis2.xml with MTOM activated:
true

And I guess I´m using the generated Stub in the correct way:
image.setMetaInfo( "foo");
EnqueueImage.ImageAttachment imageAttachment =
EnqueueImage.ImageAttachment.Factory.newInstance();
imageAttachment.setByteArrayValue( data );
image.setImageAttachment( imageAttachment );
imageDoc.setEnqueueImage( image );
stub.enqueue_image( imageDoc );

But with the SOAPMonitor, I see the next message being transmitted:


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



foo

//zU8Guvrtr7aXm14hR7GyI42QkWK+KgyEQRY0yI9wyI9rBgt4URERERER
ERHyutByKM1IzUrqgEECBdCyBxqAg4ROyGeTHUtw2U5Yk+9PQ5QY/LGGHevw3/t6Jjv7f+303kGA
P/IMdb0ryY//9vSfQ/8sZb9v/17ehf0v9vT5BrCX+xomjsjhwTy4ICKeXVlwlkcUj6ulePiCQi44
i96blvCEq5lQZ0zPZnuHpqIiIiIiIiP//5bqp097om4egwyku2vbXt8Em0qsNLhtLtpdtLTa9tLt
hLsQuyMf0../k4krqa//0g==





So I guess I am not using MTOM in the correct way because the image is being
sent base64 encoded and I guess that should be sent in mime type!!!

Any suggestion???

Thanks in advanced

-Mensaje original-----
De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 28 de julio de 2006 18:59
Para: axis-dev@ws.apache.org
Asunto: Re: SwA Axis2 implementation swaRef document literal

When using MTOM, you define your binary content as xsd:base64binary
within your message element. At serialization time, MTOM automatically
extracts the binary data and attaches it in a separate MIME part. If
you want to predefine the type of binary content, then you can use the
xmime types defined in the "Assigning Media Types to Binary Data in
XML" specification [1]. Here's the example from the spec:


http://www.w3.org/2001/XMLSchema";
   xmlns:tns="http://example.com/ct-required";
   xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
   targetNamespace="http://example.com/ct-required";>

http://www.w3.org/2005/05/xmlmime";
schemaLocation="http://www.w3.org/2005/05/xmlmime"/>



  

  

  

  




[1] http://www.w3.org/TR/xml-media-types/

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:
> Excuse me Anne, but I have tried to use MTOM with document literal but I
> didn´t know how. I don´t know how is the WSDL for support this.
>
> When I have tried to use MTOM, the WSDL2Java have generated methods that
> receive OMElement object as parameters. But I NEED that the stub has
methods
> that receive DataBinding objects (for example EnqueueImage see WSDL below)
> as parameters.
>
> Any suggestion? Thanks
>
> Regards
>
> -Mensaje original-
> De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Enviado el: viernes, 28 de julio de 2006 16:27
> Para: axis-dev@ws.apache.org
> Asunto: Re: SwA Axis2 implementation swaRef document literal
>
> As long as you're using Axis2, I suggest using MTOM rather than SwA.
>
> Anne
>
> On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]>
wrote:
> >
> >
> >
> >
> > Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have
> the
> > addAttachment method, so I don´t know how to send the image and I cannot
> use
> > the DataHandler.
> >
> >
> >
> > Thanks again. Regards
> >
> >
> >
> >  
> >
> >
> > De: Rudolf Pailer [mailto:[EMAIL PROTECTED]
> >  Enviado el: viernes, 28 de julio de 2006 13:32
> >  Para: axis-dev@ws.apache.org
> >  Asunto: AW: SwA Axis2 implementation swaRef document literal
> >
> >
> >
> >
> > Hello Francisco!
> >
> >
> >
> > have a look at
> >
> > http://www.mail-archive.com/axis-user@xml.apache.org/msg08732.html
> >
> >
> >
> > regards
> >
> > Rudolf
> >
> >
> >
> >  
> >
> >
> > Von: Francisco Fernandez Velasco [mailto:[EMAIL PROTECTED]
> >  Gesendet: Freitag, 28. Juli 2006 13:07
> >  An: axis-dev@ws.apache.org
> >  Betreff: SwA Axis2 implementation sw

Fwd: SwA Axis2 implementation swaRef document literal

[Anne Thomas Manes]

Is there any documentation or tutorials that explains how to use MTOM
with Axis2?

-- Forwarded message --
From: Francisco Fernandez Velasco <[EMAIL PROTECTED]>
Date: Jul 31, 2006 1:14 PM
Subject: RE: SwA Axis2 implementation swaRef document literal
To: axis-dev@ws.apache.org


Thanks Anne,

Now, I think I have the WSDL in the correct way:



   
   
   
   
   
 
   
 
   
   
   
   




Also I have the axis2.xml with MTOM activated:
true

And I guess I´m using the generated Stub in the correct way:
image.setMetaInfo( "foo");
EnqueueImage.ImageAttachment imageAttachment =
EnqueueImage.ImageAttachment.Factory.newInstance();
imageAttachment.setByteArrayValue( data );
image.setImageAttachment( imageAttachment );
imageDoc.setEnqueueImage( image );
stub.enqueue_image( imageDoc );

But with the SOAPMonitor, I see the next message being transmitted:


http://schemas.xmlsoap.org/soap/envelope/";>
   
   
   
   foo

//zU8Guvrtr7aXm14hR7GyI42QkWK+KgyEQRY0yI9wyI9rBgt4URERERER
ERHyutByKM1IzUrqgEECBdCyBxqAg4ROyGeTHUtw2U5Yk+9PQ5QY/LGGHevw3/t6Jjv7f+303kGA
P/IMdb0ryY//9vSfQ/8sZb9v/17ehf0v9vT5BrCX+xomjsjhwTy4ICKeXVlwlkcUj6ulePiCQi44
i96blvCEq5lQZ0zPZnuHpqIiIiIiIiP//5bqp097om4egwyku2vbXt8Em0qsNLhtLtpdtLTa9tLt
hLsQuyMf0../k4krqa//0g==
   
   



So I guess I am not using MTOM in the correct way because the image is being
sent base64 encoded and I guess that should be sent in mime type!!!

Any suggestion???

Thanks in advanced

-Mensaje original-----
De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 28 de julio de 2006 18:59
Para: axis-dev@ws.apache.org
Asunto: Re: SwA Axis2 implementation swaRef document literal

When using MTOM, you define your binary content as xsd:base64binary
within your message element. At serialization time, MTOM automatically
extracts the binary data and attaches it in a separate MIME part. If
you want to predefine the type of binary content, then you can use the
xmime types defined in the "Assigning Media Types to Binary Data in
XML" specification [1]. Here's the example from the spec:


http://www.w3.org/2001/XMLSchema";
  xmlns:tns="http://example.com/ct-required";
  xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
  targetNamespace="http://example.com/ct-required";>

   http://www.w3.org/2005/05/xmlmime";
   schemaLocation="http://www.w3.org/2005/05/xmlmime"/>

   
   
 
   
 
   
 
   
 
   



[1] http://www.w3.org/TR/xml-media-types/

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:

Excuse me Anne, but I have tried to use MTOM with document literal but I
didn´t know how. I don´t know how is the WSDL for support this.

When I have tried to use MTOM, the WSDL2Java have generated methods that
receive OMElement object as parameters. But I NEED that the stub has

methods

that receive DataBinding objects (for example EnqueueImage see WSDL below)
as parameters.

Any suggestion? Thanks

Regards

-Mensaje original-
De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 28 de julio de 2006 16:27
Para: axis-dev@ws.apache.org
Asunto: Re: SwA Axis2 implementation swaRef document literal

As long as you're using Axis2, I suggest using MTOM rather than SwA.

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]>

wrote:

>
>
>
>
> Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have
the
> addAttachment method, so I don´t know how to send the image and I cannot
use
> the DataHandler.
>
>
>
> Thanks again. Regards
>
>
>
>  
>
>
> De: Rudolf Pailer [mailto:[EMAIL PROTECTED]
>  Enviado el: viernes, 28 de julio de 2006 13:32
>  Para: axis-dev@ws.apache.org
>  Asunto: AW: SwA Axis2 implementation swaRef document literal
>
>
>
>
> Hello Francisco!
>
>
>
> have a look at
>
> http://www.mail-archive.com/axis-user@xml.apache.org/msg08732.html
>
>
>
> regards
>
> Rudolf
>
>
>
>  
>
>
> Von: Francisco Fernandez Velasco [mailto:[EMAIL PROTECTED]
>  Gesendet: Freitag, 28. Juli 2006 13:07
>  An: axis-dev@ws.apache.org
>  Betreff: SwA Axis2 implementation swaRef document literal
>
>   I need send an image to a webservice (document/literal) using SwA and
> not base64 enconding because of performance problems.
>
> I have defined the next WSDL following the WS-I Profile:
>
> 
> http://schemas.xmlsoap.org/wsdl/";
> xmlns

Re: SwA Axis2 implementation swaRef document literal

[Anne Thomas Manes]

When using MTOM, you define your binary content as xsd:base64binary
within your message element. At serialization time, MTOM automatically
extracts the binary data and attaches it in a separate MIME part. If
you want to predefine the type of binary content, then you can use the
xmime types defined in the "Assigning Media Types to Binary Data in
XML" specification [1]. Here's the example from the spec:


http://www.w3.org/2001/XMLSchema";
  xmlns:tns="http://example.com/ct-required";
  xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
  targetNamespace="http://example.com/ct-required";>

   http://www.w3.org/2005/05/xmlmime";
   schemaLocation="http://www.w3.org/2005/05/xmlmime"/>

   
   
 
   
 
   
 
   
 
   



[1] http://www.w3.org/TR/xml-media-types/

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:

Excuse me Anne, but I have tried to use MTOM with document literal but I
didn´t know how. I don´t know how is the WSDL for support this.

When I have tried to use MTOM, the WSDL2Java have generated methods that
receive OMElement object as parameters. But I NEED that the stub has methods
that receive DataBinding objects (for example EnqueueImage see WSDL below)
as parameters.

Any suggestion? Thanks

Regards

-Mensaje original-
De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 28 de julio de 2006 16:27
Para: axis-dev@ws.apache.org
Asunto: Re: SwA Axis2 implementation swaRef document literal

As long as you're using Axis2, I suggest using MTOM rather than SwA.

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have
the
> addAttachment method, so I don´t know how to send the image and I cannot
use
> the DataHandler.
>
>
>
> Thanks again. Regards
>
>
>
>  
>
>
> De: Rudolf Pailer [mailto:[EMAIL PROTECTED]
>  Enviado el: viernes, 28 de julio de 2006 13:32
>  Para: axis-dev@ws.apache.org
>  Asunto: AW: SwA Axis2 implementation swaRef document literal
>
>
>
>
> Hello Francisco!
>
>
>
> have a look at
>
> http://www.mail-archive.com/axis-user@xml.apache.org/msg08732.html
>
>
>
> regards
>
> Rudolf
>
>
>
>  
>
>
> Von: Francisco Fernandez Velasco [mailto:[EMAIL PROTECTED]
>  Gesendet: Freitag, 28. Juli 2006 13:07
>  An: axis-dev@ws.apache.org
>  Betreff: SwA Axis2 implementation swaRef document literal
>
>   I need send an image to a webservice (document/literal) using SwA and
> not base64 enconding because of performance problems.
>
> I have defined the next WSDL following the WS-I Profile:
>
> 
> http://schemas.xmlsoap.org/wsdl/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";>
> 
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd";
> elementFormDefault="qualified">
>   namespace="http://ws-i.org/profiles/basic/1.1/xsd";
> schemaLocation="http://ws-i.org/profiles/basic/1.1/xsd"/>
> 
> 
> 
> 
> 
> 
>  type="xsd:string"/>
>  type="wsi:swaRef"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  message="tns:enqueueImageRequest"/>
> 
> 
> 
> 
>  transport="http://schemas.xmlsoap.org/soap/http"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> http://"/>
> 
> 
> 
>
> When I run WSDL2Java (xmlbeans data binding) it's generated a
> EnqueueImage object with a method waiting for a SwaRef object and I don´t
> know
> what to do with it:
>
> void
> xsetImageAttachment(org.ws_i.profiles.basic._1_1.xsd.SwaRef
> imageAttachment)
>
> I don´t know where to add the image that I want to send to the
> WebService.
>
> Thanks and Regards.
> Fran.
>
>
>
>  --
>  email scanned by Ikarus ContentWall
>  filename: mailbody -->

Re: SwA Axis2 implementation swaRef document literal

[Anne Thomas Manes]

As long as you're using Axis2, I suggest using MTOM rather than SwA.

Anne

On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:





Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have the
addAttachment method, so I don´t know how to send the image and I cannot use
the DataHandler.



Thanks again. Regards



 


De: Rudolf Pailer [mailto:[EMAIL PROTECTED]
 Enviado el: viernes, 28 de julio de 2006 13:32
 Para: axis-dev@ws.apache.org
 Asunto: AW: SwA Axis2 implementation swaRef document literal




Hello Francisco!



have a look at

http://www.mail-archive.com/axis-user@xml.apache.org/msg08732.html



regards

Rudolf



 


Von: Francisco Fernandez Velasco [mailto:[EMAIL PROTECTED]
 Gesendet: Freitag, 28. Juli 2006 13:07
 An: axis-dev@ws.apache.org
 Betreff: SwA Axis2 implementation swaRef document literal

  I need send an image to a webservice (document/literal) using SwA and
not base64 enconding because of performance problems.

I have defined the next WSDL following the WS-I Profile:


http://schemas.xmlsoap.org/wsdl/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";>

http://www.w3.org/2001/XMLSchema";
xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd";
elementFormDefault="qualified">
 http://ws-i.org/profiles/basic/1.1/xsd";
schemaLocation="http://ws-i.org/profiles/basic/1.1/xsd"/>
























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












http://"/>




When I run WSDL2Java (xmlbeans data binding) it's generated a
EnqueueImage object with a method waiting for a SwaRef object and I don´t
know
what to do with it:

void
xsetImageAttachment(org.ws_i.profiles.basic._1_1.xsd.SwaRef
imageAttachment)

I don´t know where to add the image that I want to send to the
WebService.

Thanks and Regards.
Fran.



 --
 email scanned by Ikarus ContentWall
 filename: mailbody --> clean
 filename: mailbody(html) --> clean
 SCANMODULE: Ikarus vdb: 27.07.2006(67671) version: 0.2.65.0
 --



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

Re: axis-mailing-list

[Anne Thomas Manes]

See http://ws.apache.org/axis/mail.html.

Send a mail to [EMAIL PROTECTED] from the email
account that you originally subscribed with. You must then confirm
your unsubscription request by replying to the confirmation mail you
get.

Anne

On 7/26/06, Christian Sell <[EMAIL PROTECTED]> wrote:





Hey,



can you tell me how I can unsubscribe from the mailing list?



Chris


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

Re: AXIS2::Serialization of conplex type throws NPE

[Anne Thomas Manes]

One more note: I think you need to use a later build.

When using Document style, the  definition in the WSDL
binding must not specify a namespace attribute. I believe this problem
is fixed in the latest build.

Anne



On 7/12/06, Pradeepta Bhattacharya <[EMAIL PROTECTED]> wrote:

Do you mean that to use the Receiver class that is generated. But it will be
internally making call to the ShoppingServiceSkeleton interface resulting in
an NotSupportedException. Could you please explain a bit in brief the
procedure what you meant in the solution. Thanks a lot.

Pradeepta

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 11:41 AM
To: axis-dev@ws.apache.org
Subject: Re: AXIS2::Serialization of conplex type throws NPE

Hi Pradeepta;
Since you have the wsdl why dont you code generate rather than using
RPCMessage receiver , I think that is the best way.
Any way can you pls send me the service impl class as well (if possible)

Pradeepta Bhattacharya wrote:

>When trying to invoke a RPC based service, Axis throws an exception when
>
>trying to serialize a response of hierarchic bean structure to response
SOAP
>
>request. I have attached the service jar deployed on JBoss 4.0.4 and I have

>
>tested the simple response sayHello but when it comes to complex structure
>
>axis throws NPE. Any help on what might be wrong is highly appreciated.
>
>Thanks a lot.
>
>
>
>/
>
>// REQUEST  /
>
>/
>
>
>
>
>
>http://schemas.xmlsoap.org/soap/envelope/";>
>
>   
>
>   
>
>   
>xmlns="http://ShoppingEngine.shoppingengine.airtrade.project.bsil.com/types
">
>
>  
>
>

>xmlns="http://air.airtrade.project.bsil.com/xsd";>
>
>
2006-08-
>
>28T00:22:08.968+05:30
>
>
MIA
>
>
CDG
>
>

>
> 
>xmlns="http://air.airtrade.project.bsil.com/xsd";>1
>
>  
>
>   
>
>   
>
>
>
>
>
>
>
>/
>
>// RESPONSE /
>
>/
>
>
>
>
>
>http://schemas.xmlsoap.org/soap/envelope/";>
>
>   
>
>   
>
>   
>
>
soapenv:Client
>
>
>
>   java.lang.NullPointerException
>
>  
>
>
org.apache.axis2.AxisFault:
>
>java.lang.NullPointerException; nested exception is:
>
>   org.apache.axiom.om.OMException:
java.lang.NullPointerException
>
>   at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
>
>   at
>
>org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic
>
>(RPCMessageReceiver.java:150)
>
>   at
>
>org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive
>
>(AbstractInOutSyncMessageReceiver.java:37)
>
>   at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:504)
>
>
>
>   at
>
>org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest
>
>(HTTPTransportUtils.java:284)
>
>   at org.apache.axis2.transport.http.AxisServlet.doPost
>
>(AxisServlet.java:144)
>
>   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>   at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
>
>   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
>
>(ApplicationFilterChain.java:252)
>
>   at org.apache.catalina.core.ApplicationFilterChain.doFilter
>
>(ApplicationFilterChain.java:173)
>
>   at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter
>
>(ReplyHeaderFilter.java:96)
>
>   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
>
>(ApplicationFilterChain.java:202)
>
>   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.jboss.web.tomcat.security.SecurityAssociationValve.invoke
>
>(SecurityAssociationValve.java:175)
>
>   at org.jboss.web.tomcat.security.JaccContextValve.invoke
>
>(JaccContextValve.java:74)
>
>   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

Re: Null Pointer Exception: BijectiveNSMap.java

[Anne Thomas Manes]

I suggest you submit this question to the folks that supplied you with
this package:

 com.ctc.wstx.util.BijectiveNsMap.findPrefixByUri

Anne

On 7/2/06, Giridhar Manepalli <[EMAIL PROTECTED]> wrote:

Hello,
I am facing the same problem as this one

http://mail-archives.apache.org/mod_mbox/ws-axis-user/200605.mbox/[EMAIL 
PROTECTED]

Is there anyone who is facing the same problem as me? I am using axis2
v1.0 and all the packaged jars with this particular distribution.

I would appreciate if one of you could throw some light on this issue.

FYI
databinding is using xmlbeans
wsdl is doc/literal wrapped


Regards,
Giridhar

My particular error dump is

org.apache.axis2.AxisFault: Transport error 500 . Error Message is
Apache Tomcat/5.5.9 - Error
report HTTP Status 500 - type Exception
reportmessage description The
server encountered an internal error () that prevented it from
fulfilling this request.exception
java.lang.NullPointerException
com.ctc.wstx.util.BijectiveNsMap.findPrefixByUri(BijectiveNsMap.java:132)

com.ctc.wstx.sw.SimpleOutputElement.getPrefix(SimpleOutputElement.java:453)

org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeAttributes(StreamingOMSerializer.java:214)

org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:147)

org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:73)

org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:56)

org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:315)

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:786)

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:780)

org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:171)

org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)

org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:381)

org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:256)

org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:210)
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)

org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:43)
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)

org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is
available in the Apache Tomcat/5.5.9 logs.Apache Tomcat/5.5.9

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




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

Re: Client using Axis2

[Anne Thomas Manes]

Rebuild the service using document/literal. Then you can use Axis2 as an asynchronous client. Given the simplicity of the interface, there's no reason to use rpc/encoded.AnneOn 6/29/06, 
Marta García Rueda <[EMAIL PROTECTED]> wrote:
Thank you very much for your response.I thought use Axis2 because I want to make an asynchronous client for thisweb service. I´m not interested in the web service response but I don´t findthe solution with Axis. Can someone tell me if I can do a simple client
where the client application immediately gets the control back with Axis?-Mensaje original-De: Ajith Ranabahu [mailto:[EMAIL PROTECTED]]Enviado el: jueves, 29 de junio de 2006 11:27
Para: axis-dev@ws.apache.orgAsunto: Re: Client using Axis2Hi,Seems this is an rpc/encoded WSDL which is not supported yet in Axis2.AjithOn 6/29/06, Marta García Rueda <
[EMAIL PROTECTED]> wrote:> Hello,>> I´m trying to make a Client using Axis2 based on> samples\userguide\src\userguide\clients for a simply web
> service in Sun One 7.1 with wsdl: >  http://schemas.xmlsoap.org/wsdl/
" xmlns:tns="> http://ServicioNotificacion.ws/wsdl/ServicioPrueba"> xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:soap="> http://schemas.xmlsoap.org/wsdl/soap/" name="ServicioPrueba"> targetNamespace="
http://ServicioNotificacion.ws/wsdl/ServicioPrueba">>>
>  >>
>  >>>
message="tns:ServicioPruebaIF_getDatosPruebaResponse"/>e>>>  
>>  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/> " use="encoded"
> namespace="http://ServicioNotificacion.ws/wsdl/ServicioPrueba"/>>>  > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"> namespace=" 
http://ServicioNotificacion.ws/wsdl/ServicioPrueba"/>>>  
http://schemas.xmlsoap.org/soap/http"> style="rpc"/>>>  > binding="tns:ServicioPruebaIFBinding">
>http://schemas.xmlsoap.org/wsdl/"> location="> http://cabana:8701/ServicioPrueba/ws
"/> but I have the next exception in the Sun One´s console unexpected encoding style:> expected=
http://schemas.xmlsoap.org/soap/encoding/, actual=>  atcom.sun.xml.rpc.encoding.SOAPDeserializationContext.verifyEncodingStyle> (SOAPDeserializationContext.java
:142)>  at>com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:148)>  at>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(Referenceab
leSerializerImpl.java> :115)>  at>ws.ServicioPruebaIF_Tie.deserialize_getDatosPrueba(ServicioPruebaIF_Tie.java:88)>  at> ws.ServicioPruebaIF_Tie.readFirstBodyElement(ServicioPruebaIF_Tie.java:74)
>  at com.sun.xml.rpc.server.StreamingHandler.handle> (StreamingHandler.java:164)>  at>com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:280)>  at
com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)>  at javax.servlet.http.HttpServlet.service (HttpServlet.java:760)>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>  at>org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)>  at org.apache.catalina.core.StandardWrapperValve.access$000> (StandardWrapperValve.java
:118)>  at>org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)>  at java.security.AccessController.doPrivileged(Native Method)>  at org.apache.catalina.core.StandardWrapperValve.invoke
> (StandardWrapperValve.java:274)>  at>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)>  at>org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:212)>  at org.apache.catalina.core.StandardPipeline.invoke> (StandardPipeline.java:505)>  at>org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)>  at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)>  at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process> (NSAPIProcessor.java:158)>  at com.iplanet.ias.web.WebContainer.service
(WebContainer.java:856) Could you tell me how can I define the encoding style? Thank you very much.>> Marta García.>>
--Ajith Ranabahu-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]-To unsubscribe, e-mail: 
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Unwrapping support - how to maintain the part name reference ?

[Anne Thomas Manes]

You would need to use the message name as the namespaceURI to ensure uniqueness. (Notice that your example uses "part1" for both input and output messages for the same operation.)Anne
On 6/28/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hi all,Dennis has been a bit silent on the mailing list these days so Idecided to move on with the mentioned plan in the last mail. It seemsthat there is no alternative to the problem of finding how to populate
the method signatures other than a schema walker that figures out thepart names and their type during the code generation.While doing that I came across a small issue. Our type mapper (whichis basically a wrapped  hash table) is global. As soon as you try to
populate it with types that relate to parts (with the part name as thekey) a problem occurs. The part names are *not* supposed to be uniqueacross messages and part names are not namespace qualified forrpc/lit!
Here is a snippet from one of the test WSDL's
How can I maintain a reference to part1 of the first message uniquelyin the type mapper ? I don't want to change the structure of the type
mapper (the fact that it is a simple key-value pair) partly becausethe users are allowed to pass in an external mapping file and also Ifear things might get messy if I add more methods to it..What I thought was to have our own convention inside the codegen where
we generate a QName for the part with part name as the localpart andthe operation name as the namespaceURI. It is totally a privateconvention but the databinding extensions have to follow thatcovention and populate the type map accordingly.
Any thoughts ?--Ajith Ranabahu-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration Axis 1 to Axis 2

[Anne Thomas Manes]

Sorry -- was not complete in my last answer. If you change it to rpc style, then you must also add namespace attributes to the  definitions, e.g.,:http://www.fabiorosolino.com/Servizio.xsd1"/>AnneOn 6/27/06, 
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Anne,I modified Servizio.wsdl as you suggested but the question is,1) why it work fine (style document) with axis 1.2?2) after the change in rpc style i'm still not able to do a service that work!!! :(I use Tomcat 
5.5 as container either with axis 1.2 or with axis 2 on windows.There will be something wrong in this configuration?mmm, I just made performace analysis with Jmeter on this services developed in axis 1.2, I wish to develop same service in axis 
2.0 to compare performance with axis 2.Someone help me :( :)Thanks-- Initial Header ---From  : "Anne Thomas Manes" [EMAIL PROTECTED]
To  : axis-dev@ws.apache.orgCc  :Date  : Tue, 27 Jun 2006 08:59:50 -0400Subject : Re: Migration Axis 1 to Axis 2
> Fabio,>> There are errors in your WSDL. You must fix them before you can get Axis2 to> work.>> You've defined the service as document style, but your message parts> reference types rather than elements. (A document style service MUST
> reference elements; and RPC style service MUST reference types.) Either> convert the style to RPC or define the "res" and "n" parts as elements in> your schema and reference them rather than the types.
>> I suggest you follow the "wrapped" document style convention. See> http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.htmlfor
> guidance.>> Anne>> On 6/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:> >> > I have a wsdl genereted by SOA Editor.
> > I'm able to develop a service in Axis 1.2 from this WSDL, but i'm not able> > to develop a service with Axis 2 v1.0.> > Someome can send me send me a service developed using my WSDL in Axis 2.
> > In attachment the Servizio.wsdl (Servizio means Service in italian ;))> > Thanks Fabio> >> >> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >> >>-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration Axis 1 to Axis 2

[Anne Thomas Manes]

Fabio,There are errors in your WSDL. You must fix them before you can get Axis2 to work.You've defined the service as document style, but your message parts reference types rather than elements. (A document style service MUST reference elements; and RPC style service MUST reference types.) Either convert the style to RPC or define the "res" and "n" parts as elements in your schema and reference them rather than the types. 
I suggest you follow the "wrapped" document style convention. See http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
 for guidance.AnneOn 6/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:I have a wsdl genereted by SOA Editor.I'm able to develop a service in Axis 
1.2 from this WSDL, but i'm not able to develop a service with Axis 2 v1.0.Someome can send me send me a service developed using my WSDL in Axis 2.In attachment the Servizio.wsdl (Servizio means Service in italian ;))
Thanks Fabio-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [Axis2] Implementing unwrapped (was Re: [Axis2] Planning for Axis2 next rev - 1.1 (?))

[Anne Thomas Manes]

Dennis,The terminology is confusing. When using Document style, the message body on the wire must always contain at most one element. When using "non-wrapped" document style, the databinding maps that body element to a value object. When using "wrapped" style, that body element (which has the same name as the operation) is a wrapper around a set of parameter elements. "Unwrapping" refers to the process in which the databinding system automatically unwraps the body element and maps the parameter elements to individual classes. Support for "wrapped" style (which includes the ability to automatically "unwrap" the body wrapper element) is what Ajith is currently implementing.  
AnneOn 6/24/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Sanjiva Weerawarana wrote:> On Fri, 2006-06-23 at 22:03 +1200, Dennis Sosnoski wrote:>> ...>>> One of the points of unwrapping is supposed to be to reduce the number>> of class generated. Besides, in many cases those unwrapped parts are
>> going to be primitives. How do you plan to handle these? Reduce the # of classes? Unwrapping *increases* the number of classes ..> each arg becomes a separate class. I must be missing something.
>I think that's the crux of where my approach differs from what Ajith isimplementing. You're thinking in terms of a unique class per elementname, which leads to an even worse proliferations of unnecessary classes
than what we've got now. The reason I want to handle the entire call tothe service method within the data binding-specific code is so that Ican work with primitives and classes that have a defined structure
binding (the equivalent of a complexType definition) but may be reusedin different places with different names. That way you're working onlywith the actual data classes, without the wrapper classes.Here's a snippet from the Axis(1) users guide, describing the Axis(1)
handling of wrapped vs. unwrapped:For a *document* style service, this would map to a method like this:public void method(PurchaseOrder po)In other words, the ENTIRE  element would be handed to
your method as a single bean with three fields inside it. On the otherhand, for a *wrapped* style service, it would map to a method like this:public void purchaseOrder(String item, int quantity, String description)
Note that in the "wrapped" case, the  element is a"wrapper" (hence the name) which only serves to indicate the correctoperation. The arguments to our method are what we find when we "unwrap"
the outer element and take each of the inner ones as a parameter.This is what users expect from unwrapped support, not to have to dealwith a whole new layer of classes wrapping the simple bean values.
  - Dennis-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [axis2] - wsdl2java - exception

[Anne Thomas Manes]

Please post the WSDL. On 6/23/06, Gmail <[EMAIL PROTECTED]> wrote:
I'm new to axis2. I have wsdl from which in axis 1.* I have succesfullygenerated java code, but in axis2 I got following exception:Exception in thread "main"org.apache.axis2.wsdl.codegen.CodeGenerationException
:org.apache.axis2.wsdl.codegen.CodeGenerationException:java.lang.NullPointerException   atorg.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185)   at org.apache.axis2.wsdl.WSDL2Code.main
(WSDL2Code.java:32)   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:java.lang.NullPointerException   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub
(AxisServiceBasedMultiLanguageEmitter.java:171)   atorg.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:176)   ... 2 moreCaused by: java.lang.NullPointerException
   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1511)   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.getFaultElement
(AxisServiceBasedMultiLanguageEmitter.java:1449)   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1199)   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.createDOMDocumentForCallbackHandler
(AxisServiceBasedMultiLanguageEmitter.java:572)   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.writeCallBackHandlers(AxisServiceBasedMultiLanguageEmitter.java:551)   at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStubFromService(AxisServiceBasedMultiLanguageEmitter.java:266)   atorg.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEmitter.emitStub
(AxisServiceBasedMultiLanguageEmitter.java:169)   ... 3 morelinux: i686java: sun-jdk1.5.0_06axis:  2I typed command :sh WSDL2Java.sh -uri xxx.wsdl -ss -sd -d xmlbeans -o xxx
Is there any problem with wsdl types, namespaces in axis2 or somethingelse please help me.best regardsBorowski Filip-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: AXIS1x bug: 2+ operations with same input/output

[Anne Thomas Manes]

Method overloading should not be exposed through your WSDL interface. You should define a unique operation name and a unique input message for each operation. If your service implementation uses method overloading, that's fine -- but you need to provide an abstraction layer between your WSDL interface and the service implementation. 
The SOAP specification requires that each operation has a unique signature.(well, technically, it's not required by SOAP 1.1, but it is required by WS-I Basic Profile and SOAP 1.2. In any case, most SOAP implementations don't support it.)
AnneOn 6/5/06, Julio César Pérez Arques <[EMAIL PROTECTED]> wrote:
Thanks for your response.>>It's not a bug. Each operation must have a unique signature (defined as the>qname of the child element of the  element).I think this is a strong limitation.
Then, how can i get methods overloading?Why is not soapaction used?Is it the same for Axis2?Greetings.Julio César.>From: "Anne Thomas Manes" <
[EMAIL PROTECTED]>>Reply-To: axis-dev@ws.apache.org>To: axis-dev@ws.apache.org>Subject: Re: AXIS1x bug: 2+ operations with same input/output
>Date: Sun, 4 Jun 2006 17:36:43 -0400>>It's not a bug. Each operation must have a unique signature (defined as the>qname of the child element of the  element).>>Anne
>>On 6/3/06, Julio César Pérez Arques <[EMAIL PROTECTED]> wrote:>>>>Hello boyz.>>>>I am developing a axis ws that has 2 operations with same input/output. I
>>use axis 1.4 and wsdl2java.>>But always 1st operation is executed, never the 2nd one.>>>>I have read in axis mailing lists it is a bug. Is this correct?>>I always have read a possible solution in by a user. It dates from March
>>2006.>>>>Is this bug going to fix?>>>>Thanks in advance.>>Julio César.>>>>>>>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>>-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis Error - Server

[Anne Thomas Manes]

Please post the WSDL.On 6/2/06, Nicolas Guaneme <[EMAIL PROTECTED]> wrote:
Hello all,I have a bug with a web service I have 3 method for show I have
a problem with a method excatly I run the client an the tcp-mon showthe message that send the client and response the server. this isthe messages:User-Agent: NuSOAP/0.6.3Host: 
127.0.0.1:Content-Type: text/xml; charset=ISO-8859-1Content-Length: 936SOAPAction: ""   xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/
"xmlns:si="http://soapinterop.org/xsd">   xmlns="
http://co.com.www.avisortech/MPPWebServices/">   10017   9875   100201
   Pagos en Linea PSE. No. de Matricula   45000   0
   0   Prueba   Prueba   Prueba
   0   locahost:   1009
  this is the response:HTTP/1.1 500 Error Interno del ServidorContent-Type: text/xml;charset=iso-8859-1
Date: Fri, 02 Jun 2006 17:27:46 GMTServer: Apache-Coyote/1.1Connection: close   xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">   soapenv:Server.userException
java.lang.reflect.InvocationTargetException   xmlns:ns1="http://xml.apache.org/axis/">avisortech02
  but I consuming the web service in PHP I can see the debug of the clientand the response also... this is teh debug for the response
soapclient: got response, length: 524soapclient: Entering parseResponse(), about to create soap_parser instancesoapclient: soap_parser: Entering soap_parser()soap_parser: found root struct Fault, pos 2
soap_parser: adding data for scalar value faultcode of value soapenv:Server.userExceptionsoap_parser: adding data for scalar value faultstring of value java.lang.reflect.InvocationTargetExceptionsoap_parser: adding data for scalar value hostname of value avisortech02
soap_parser: inside buildVal() for detail(pos 5) of typesoap_parser: inside buildVal() for Fault(pos 2) of type structsoap_parser: parsed successfully, found root struct: 2 of name Faultsoapclient: sent message successfully and got a(n) array back
soapclient: got faultsoapclient: faultcode = soapenv:Server.userExceptionsoapclient: faultstring = java.lang.reflect.InvocationTargetExceptionsoapclient: detail = Array
when I try to do the debug in my project I can't run step to step beacause the service start tocall any jar that hope find... if I attach the jar in run time no work it but with the othersmethod no do it...
I config the classpath of jdk,axis_home...etc with the jar external that I need.. but nothink..Hel me please.Nicolás G. Rico-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: AXIS1x bug: 2+ operations with same input/output

[Anne Thomas Manes]

It's not a bug. Each operation must have a unique signature (defined as the qname of the child element of the  element).AnneOn 6/3/06, 
Julio César Pérez Arques <[EMAIL PROTECTED]> wrote:
Hello boyz.I am developing a axis ws that has 2 operations with same input/output. Iuse axis 1.4 and wsdl2java.But always 1st operation is executed, never the 2nd one.I have read in axis mailing lists it is a bug. Is this correct?
I always have read a possible solution in by a user. It dates from March2006.Is this bug going to fix?Thanks in advance.Julio César.-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error Axis

[Anne Thomas Manes]

Please supply the WSDL and the input message.AnneOn 5/23/06, Nicolas Guaneme <[EMAIL PROTECTED]
> wrote:Hello , I hava a WS and show me this exception in the TCP-Mon   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd="
http://www.w3.org/2001/XMLSchema"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">   
soapenv:Server.userExceptionorg.xml.sax.SAXException: Invalid element inavisortech.www.com.co.MPPWebServices._createTransactionPayment_request
 -EntityCode   xmlns:ns1="http://xml.apache.org/axis/">avisortech02
  The client send the xml ok, but I don't lnow why axis return this XML.-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Help Me!!

[Anne Thomas Manes]

What do you mean you can't create a client stub? Whay happens when you try?And what do you mean you never return the soap headers? You have no headers defined in your messages?I did notice that you have what appears to be a typo in the name of the return element -- it's called "tns:getBabkListResponse", but I would have expected it to be called "tns:getBankListResponse".
But if you fix the name in the message definition, you will also have to fix it in the schema:      type="tns:ArrayOfGetBankList">
   You also have two extraneous complex types defined. (This doesn't hurt anything, but might be causing some confusion):   
            
         
      AnneOn 5/19/06, Nicolas Guaneme <
[EMAIL PROTECTED]> wrote:Hello All,I have this WSDL service
http://schemas.xmlsoap.org/wsdl/soap/"xmlns:tns="
http://co.com.www.avisortech/MPPWebServices/"xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="MPPWebServices"targetNamespace="
http://co.com.www.avisortech/MPPWebServices/">targetNamespace="http://co.com.www.avisortech/MPPWebServices/
">minOccurs="0" maxOccurs="1">
type="xsd:string" minOccurs="0" maxOccurs="1">type="xsd:string" minOccurs="0" maxOccurs="1">
type="tns:ArrayOfGetBankList">
ref="tns:getBabkListResponse">


type="tns:createTransactionPaymentResponseType">

type="tns:createTransactionPaymentRequestType">
name="createTransactionPaymentRequestType">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">minOccurs="0" maxOccurs="1">minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">minOccurs="0" maxOccurs="1">
name="createTransactionPaymentResponseType">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">

type="tns:getTransactionInformationResponseType">

type="tns:getTransactionInformationRequestType">
name="getTransactionInformationRequestType">
minOccurs="0" maxOccurs="1">
minOccurs="0" maxOccurs="1">
name="getTransactionInformationResponseType">type="xsd:string" minOccurs="0" maxOccurs="1"> 

Re: ServiceMix

[Anne Thomas Manes]

ServiceMix is a CodeHaus project, not an Apache project. You need to ask them what their plans are. See http://servicemix.org/. AnneOn 5/10/06, 
Arjuna Chala <[EMAIL PROTECTED]> wrote:
Is there a plan to build Axis2 support into Apache ServiceMix?

Re: FW: [Axis 1.3] wsdl with import vs. without import

[Anne Thomas Manes]

You need to define a targetNamespace for your schema.AnneOn 4/7/06, Dovholuk, Clint <[EMAIL PROTECTED]
> wrote:




Can anybody point me at my problem with ""?  I added 
this to my server-config.wsdd... 


but it 
didn't 'help' any..


From: Dovholuk, Clint 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, April 06, 
2006 7:46 AMTo: axis-user@ws.apache.orgSubject: [Axis 1.3] 
wsdl with import vs. without import

Hello 
all,
 
I think this post 
might be related to my last post titled: 
  [Axis 1.3] 
Namespace issues, element with "" namespace
 
I've been trying to 
include a schema to a wsdl document, generate code for axis and use the 
generated classes as a web service but when I include the schema doc, I find 
that (I think) because of the "" namespace being applied to an element higher up 
the doc multiple namespaces are being injected into the response (ns2 through 
ns15+) all of which have the exact same namespace (including the 'wrapper' 
element).
 
I attached a .zip 
file (rename to .zip from _zip) with the two wsdls, the schemas, and the 
TCPMonitor capture of each...
 
Any thoughts? 
I 
appreciate anyone taking the time to look at this...
 
-cwd

Re: [Axis2] Schema with no targetNamespace rejected

[Anne Thomas Manes]

Here's the email thread:http://marc.theaimsgroup.com/?l=axis-user&m=114348410608730&w=2And here's the standard OTA schema which has no targetNamespace:
http://www.opentravel.org/2005B/OTA_SimpleTypes.xsd(You'd think a standards group would have the sense to define a namespace!)Anne
On 3/29/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Sanjiva Weerawarana wrote:>On Wed, 2006-03-29 at 09:01 +1200, Dennis Sosnoski wrote:>Does WSDL 1.1 define QNames somewhere to require prefixes? This>>certainly isn't standard usage of the schema QName type. Schema
>>considers QNames with no prefix to be using the default namespace for>>the context.>>No, WSDL doesn't define that IIRC. However, when it uses the default>namespace then its still a qualified name. So if the schema is
>targetnamespace-less then it still can't be referred to.>>Am I missing something?>>As long as there's no default namespace declared in the WSDL unqualifiedvalues are in the nonamespace namespace, the same as schema definitions
with no targetNamespace. So references from the WSDL into the schemadefinitions are not a problem.  - Dennis

Re: [Axis2] Schema with no targetNamespace rejected

[Anne Thomas Manes]

I recently responded to a question from someone using the OTA schema which does not declare a targetNamespace (bad form on their part, but such is the case).AnneOn 3/28/06, 
Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Sanjiva Weerawarana wrote:>On Tue, 2006-03-28 at 19:33 +1200, Dennis Sosnoski wrote:>+1, which leads me to a quick comment.  Currently, the error reporting>>>in Axis2 is... less than adequate, to say the least.  We're building a
>>>toolkit/engine which is supposed to make it easy for developers to>>>expose and consume arbitrary Web Services in a variety of ways.  And>>>because there are so many moving parts and extensions, it is EXTRA
>>>important for us to provide detailed and useful information when>>>things go wrong.  We can discuss this more on another thread, but I>>>think this needs some serious attention if we want good uptake.
Are you willing to go along on this, Sanjiva? If so, I'll change the>>code to print a warning message to the console when a schema with no>>targetNamespace is used.
>>It doesn't work for direct reference from WSDL even for WSDL 1.1>original: part/@type and part/@element both require QNames. The only use>is for a schema defining one of those to refer to stuff in a schema with
>no namespace.>>Does WSDL 1.1 define QNames somewhere to require prefixes? Thiscertainly isn't standard usage of the schema QName type. Schemaconsiders QNames with no prefix to be using the default namespace for
the context.>Do you know of *any* usecases of this? Can you point me to the WSDL? I'd>like to understand it a bit before saying just print a warning.>>I did a quick search earlier in this thread to see if I could find any
discussion of the topic for .NET or other frameworks, but didn't findanything. But I don't see any justification for considering it an error,either.  - Dennis

Re: [Axis2] Schema with no targetNamespace rejected

[Anne Thomas Manes]

I agree with Dennis on this. WSDL 1.1 doesn't *require* that a schema have a targetNamespace. The BP does, but that's a best practice, not a spec requirement. WSDL 2.0 requires that schemas have a targetNamespace, but that doesn't change WSDL 
1.1.The better solution is to throw a warning if the targetNamespace isn't there --let XMLBeans throw the error.AnneOn 3/27/06, Dennis Sosnoski
 <[EMAIL PROTECTED]> wrote:That just BP - which everybody likes, but AFAIK Axis2 is not enforcing.
  - DennisDavanum Srinivas wrote:>Sanjiva,>>Is it this one?>>http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16552904
>>-- dims>>On 3/26/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:Sanjiva Weerawarana wrote:
>On Mon, 2006-03-27 at 14:59 +1200, Dennis Sosnoski wrote:The resolution of 
http://issues.apache.org/jira/browse/AXIS2-67 wastoadd a check that the schema definition within a WSDL defines atargetNamespace. What is the justification for this? AFAIK it's
>>>The justification is that its required by WSDL. WSDL 1.1 wasn't clear>>>but it has since been clarified.>>>
>>>So the requirement was added after WSDL 1.1 - is it spelled out>>somewhere, or just an informal interpretation? I'm happy enough to>>accept it either way, as long as other frameworks such as .NET require
>>schema namespaces, but it'd be nice to have something to point to by way>>of justification.The current code throws an NPE if a schema doesn't have a>>targetNamespace rather than reporting anything useful - that's what led
>>me into this. I'll fix that.  - Dennis>>>-->Davanum Srinivas : http://wso2.com/blogs/
>>>

Re: java file generated using WSDL2JAVA fail to compile with 'too many parameters' error

[Anne Thomas Manes]

The Opportunity complex type has too many child elements to map to a Java object. You'll have to figure out a way to break it into multiple types, or you need to use the messaging API and map it to a DOM.Anne
On 3/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:Hi,I have generated java files using WSDL2Java utility using following option.
java -Dlog4j.configuration=file:/c:/dontknow/wsdl/log4j.properties-classpathC:\axis-1_3\lib\axis.jar;C:\axis-1_3\lib\commons-logging-1.0.4.jar;C:\axis-1_3\lib\log4j-1.2.8.jar;C:\axis-1_3\lib\commons-discovery-0.2.jar
;C:\axis-1_3\lib\jaxrpc.jar;C:\axis-1_3\lib\saaj.jar;C:\axis-1_3\lib\wsdl4j-1.5.1.jar org.apache.axis.wsdl.WSDL2Java enterprise.wsdlAll java files successfully created. But when I am trying to compile those
java files then Iam getting following exception.Opportunity.java:588: too many parameters.I have seen code of Opportunity.java & its constructor is having 286parameters which is against java specification. Java limits the number of
method parameters to 255 or 254 or less ifparameters are of type long for double.My environment is ..WIndows XP, Java(TM) 2 Runtime Environment, StandardEdition (build 1.4.2_04-b05), AXIS1.3Attached is WSDL.
(See attached file: enterprise.wsdl)Thanks for you help.RegardsRakeshThis email is confidential and should not be used by anyone who is not
the original intended recipient. Prudential cannot accept liabilityfor statements made which are clearly the sender's own and not madeon behalf of the Prudential. In addition no statement should beconstrued as giving investment advice within or outside the United
Kingdom.Prudential plc, Laurence Pountney Hill, London, EC4R 0HH.Incorporated and registered in England and Wales.  RegisteredOffice as above. Registered number 1397169.  Prudential plc is aholding company, subsidiaries of which are authorised and regulated
by the Financial Services Authority (FSA)."Prudential" is a trading name of The Prudential Assurance CompanyLimited, which is registered in England and Wales.  This name isalso used by other companies within the Prudential Group, which
between them provide a range of financial products including lifeassurance, pensions, savings and investment products. RegisteredOffice at Laurence Pountney Hill, London, EC4R 0HH. Registerednumber 15454.  Authorised and regulated by the Financial Services
Authority.An e-mail reply to this address may be subject to interception ormonitoring for operational reasons or for lawful business practices.

Re: Accessing attachment in message-style or document/literal servic e

[Anne Thomas Manes]

Naeem,Please ask user questions on the user discussion list. The dev list is for the folks developing the Axis code base. I don't believe that you can access attachments using the messaging API. I suggest that you switch to the RPC provider. (It supports document/literal.)
AnneOn 2/27/06, Naeem Malik (Ext. 797) <[EMAIL PROTECTED]> wrote:
Hi allFrom long time I am not able to access the attachment. could any one pleasehelp me regarding the following problemI am using message-style service method (not RPC mode), now at client side I
can attach any attachment (i.e. binary file or in my case xml file) and cansend our the wire by using the HTTP protocol  but now the server side I cantaccess the only attachment because there are only 4 methods (see axis user
guide for reference) allowed in messaging-style service. which are1>>public Element [] method(Element [] bodies);2>>public SOAPBodyElement [] method (SOAPBodyElement [] bodies);3>>public Document method(Document body);
4>>public void method(SOAPEnvelope req, SOAPEnvelope resp);now I am using the 4th one after trying the 3rd one, now I can get thesoapEnvelope but not able to get the soapMessage actually which contain
attachments and soapEnvelope etc.Now the each method doesn't allow to access the soapMessage object( kind ofcontainer for AttachementPart & SOAPPart), or there might be another way toaccess the SOAPmessage object because if I get the soapMessage object then I
will use the following method and can retrieve any number of attachments.SOAPMessage.getAttachments();Now do any one know how to access the attachment by using above 4 methodsignatures. here is my client application code where I am attaching the file
 SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance(); SOAPConnection sc = scf.createConnection(); MessageFactory msgFactory = MessageFactory.newInstance(); SOAPMessage message = msgFactory.createMessage
(new MimeHeaders(), new ByteArrayInputStream(getXMLMessage).getBytes())); SOAPPart soapPart = message.getSOAPPart(); AttachmentPart attpart = message.createAttachmentPart();//there i am attaching the XML document
   attpart.setContent(getXMLAttachment(),"text/plain");   message.addAttachmentPart(attpart);   URLEndpoint urlEndPoint = new URLEndpoint("
http://localhost:/axis/services/claimmsgservice");   //System.out.println("before call service "+message.getAttachments());  SOAPMessage response = sc.call(message, urlEndPoint);
 but on server side I am not able to access the SOAPMessage object because of the limitation of 4 types of methodI would really appreciate if some one could help me in this matter.Thanks & regards
Naeem MalikNaeem MalikTechnical Consultancy Team___FINEOS CorporationPembroke House8 - 10 Lower Pembroke StDublin 2Email:  
[EMAIL PROTECTED]Ph: +353 1 6399797(Direct)Fax:+353 1 6399701Why don't you visit our website at http://www.FINEOS.comENTERPRISE SOLUTIONS FOR BANKING AND INSURANCE
**The information contained in this e-mail is confidential, may beprivileged and is intended only for the user of the recipient named above.
If you are not the intended recipient or a representative of the intendedrecipient, you have received this e-mail in error and must not copy, useor disclose the contents of this e-mail to anybody else.  If you have
received this e-mail in error, please notify the sender immediatelyby return e-mail and permanently delete the copy you received.This e-mail has been swept for computer viruses.  However, you shouldcarry out your own virus checks.
Registered in Ireland, No. 205721.  http://www.FINEOS.com**

Re: rpc/encoded support?

[Anne Thomas Manes]

Axis 2 does not yet support rpc/encoded.On 2/3/06, local-underground <[EMAIL PROTECTED]> wrote:
Does Axis2 0.94 support rpc/encoded WSDL2Java code generation?  Also, are there known
issues calling a rpc/encoded Web Service?The Web Service I am calling below is rpc/encoded.--- local-underground <[EMAIL PROTECTED]
> wrote:> Maybe my problem is my approach of calling a web service that takes no parameters?> Here> is my ClientUtil function:>> public static OMElement getCountriesAndStates()
> {> OMFactory fac = OMAbstractFactory.getOMFactory();> OMNamespace omNs = fac.createOMNamespace(>
"http://tempuri.org/SoapTixs/message/", "");> OMElement method =>fac.createOMElement("GetCountriesAndStates", omNs);
>> return method;> }>> Is that the appropriate way of calling a non-parameter function?> Other than that, I have no idea what it could be.>> --- Deepal Jayasinghe <
[EMAIL PROTECTED]> wrote:>> > pls recheck the request, I think ur request OMElment has some problem , but> > not sure , pls try again and if you still have the problem pls create a JIRA
> >> > Thanks,> >  Deepal> > > > ~Future is Open~> >> > - Original Message -
> > From: "local-underground" <[EMAIL PROTECTED]>> > To: 
> > Sent: Friday, February 03, 2006 4:26 AM> > Subject: [Axis2] Server:XML Parser failed> >> >> > > Hi all,> > > I tried digging through the archives but cannot find the answer to what
> > > must be a simple> > > fix.  I am getting the following error on my simple WebService client when> > > I try to call> > > any web service?> > >> > >
> > >> > > org.apache.axis2.AxisFault: Server:XML Parser failed at linenumber 1,> > > lineposition 0,> > > reason is: Unspecified error> > >> > > at
> > >> >>org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295)> > > at> > > org.apache.axis2.client.ServiceClient.sendReceive
(ServiceClient.java:393)> > > at> > > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)> > > at> > >> >> com.vegas.warehouse.external.titan.EchoBlockingClient.main
(EchoBlockingClient.java:53)> > >> > >> > >> > > Please help.  I have no idea what is causing this.> > >> > > thanks> > >> > >
> > > chris> > >> > > __> > > Do You Yahoo!?> > > Tired of spam?  Yahoo! Mail has the best spam protection around
> > > http://mail.yahoo.com> > >> >> >>  __> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around> http://mail.yahoo.com>__Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com

Re: [Axis2] Re: Compliance with Java Web Services APIs

[Anne Thomas Manes]

Axis2 supports WS-Addressing.
Axis1 supports WS-Addressing via See http://ws.apache.org/addressing/.

AnneOn 2/2/06, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
Hi,
 
I am wondering what sort of compliance we have wrt to the Java Web Services API's described in 
http://java.sun.com/webservices/index.jsp
 
From what I understand we have JAXB - JAX-RPC and SAAJ, but I am not aware of the other modules like WS-Addressing.
 
Can somebody please explain the compliance level for current Axis2
 
Thanks,
 
Rajith.

Re: WSDL 2.0 is a non-goal for Axis2 1.0?

[Anne Thomas Manes]

According to the WSDL 2.0 Working Group, they don't expect to produce a
Proposed Recommendation until the second half of 2006. We'll be lucky
to see WSDL 2.0 finalized before the end of the year. 

I agree with Dims. WSDL 2.0 should be a non-goal for Axis 2 1.0.

AnneOn 1/10/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Ahum...
Are you serious Dims ? I mean about getting rid of WOM ? For me it
seems getting rid of WOM is not that easy (codegenerator completely
depends on it) and the WSDL 2.0 is taking shape and will be finalized
soon (which means we should be supporting it anyway)

On 1/10/06, Davanum Srinivas <[EMAIL PROTECTED]
> wrote:
Team,Let's get rid of of WOM and declare that we will use only wsdl4j whichimplies hence WSDL 2.0 is a non-goal for Axis2 1.0. IF we get arelease from woden that includes parsing WSDL1.1 THEN we willreconsider.
sounds like a plan?thanks,dims--Davanum Srinivas : http://wso2.com/blogs/
-- Ajith Ranabahu

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

[Anne Thomas Manes]

Your problems are with schema and namespaces, not with WSDL. In addition to the wsdl spec, you should study these documents:

- WS-I Basic Profile: http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html
- XML Namespaces: http://www.w3.org/TR/REC-xml-names/
- XML Schema Tutorial: http://www.w3schools.com/schema/default.asp
- XML Schema Primer: http://www.w3.org/TR/xmlschema-0/

I think you should work on the assumption that it isn't a bug, but a
problem with the way you're importing/including schemas and referencing
elements. XML Schema is really complicated, but you're fortunate in
that
you don't really need to define your elements and types. You just need
to import and include the files properly, and reference your elements
and types properly.

Going back to your first question -- that was caused by the fact that
the StyledLayerDescription element references elements (Name,
Description, etc) that are defined in the common.xsd schema rather than
in the sld.xsd schema, and the sld.xsd schema doesn't 
common.xsd schema. (They are both in the sld namespace, therefore you
must  the common.xsd schema rather than 

As I said to you before, I recommend that you consolidate all the
schemas that have the same targetNamespace. That should resolve the
problems you're experiencing.

AnneOn 12/14/05, Ales St <[EMAIL PROTECTED]> wrote:







Ok,I try to solve it by myself, but problem is , 
that I  trying to solve it for one week and still can't find resolution. So 
I try to ask you, where can I find some  good book or web pages 
about wsdl i know only this http://www.w3.org/TR/wsdl and it is 
hard for me to find resolution of my problem there. Or do you knew some source 
where where is my problem solved?
Please help
        
    Ales

  - Original Message - 
  
From: 
  Anne Thomas 
  Manes 
  To: 
axis-dev@ws.apache.org 
  Sent: Wednesday, December 14, 2005 6:54 
  PM
  Subject: Re: Is it a bug? Multi-nested 
  includes. Server.generalException - makeTypeElement() was told to create a 
  type ...
  Sorry, I'm not going to do your homework for 
  you.
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote:
  
Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix 
them, please help. 
Thank you
        
Ales

  - 
  Original Message - 
  
From: 
  Anne Thomas Manes 
  To: 
  axis-dev@ws.apache.org 
  
  Sent: 
  Wednesday, December 14, 2005 6:27 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  You have a bunch of namespace errors in these files. 
  Fix them and try again.I strongly recommend that you use a 
  WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml
 . The 
  validate function is very handy.Anne
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote: 
  
Here is that files.

  - 
  Original Message - 
  
From: 
  Anne Thomas Manes 
  
  To: 
  axis-dev@ws.apache.org 
  
  Sent: 
  Wednesday, December 14, 2005 5:18 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  Please post the updated wsdl and schema files.
  On 12/14/05, Ales St <[EMAIL PROTECTED]
> 
  wrote: 
  
Hi, I did It, but still the same Server 
exception. I write this wsdl to create the simpler similar situation 
as with  StyledLayerDescription.xsd,what I solve. So it is my wsdl 
correct?
        
    Ales


  - 
      Original Message - 
  
From: 
  Anne Thomas 
  Manes 
  To: 
  axis-dev@ws.apache.org 
  Sent: 
  Wednesday, December 14, 2005 4:36 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  You must use  to bring 
  in a schema with the same namespace and  to 
  bring in a schema with a different namespace. So you must change 
  this:
  
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/ows"> 
  
  
  
    <xsd:import 
  namespace="http://www.opengis.net/ows 
  "   
   
  schemaLocation="./wms_schemas.xsd" 
  />xsd:schema&

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

[Anne Thomas Manes]

Sorry, I'm not going to do your homework for you.On 12/14/05, Ales St <[EMAIL PROTECTED]> wrote:







Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix 
them, please help. 
Thank you
        
Ales

  - Original Message ----- 
  
From: 
  Anne Thomas 
  Manes 
  To: 
axis-dev@ws.apache.org 
  Sent: Wednesday, December 14, 2005 6:27 
  PM
  Subject: Re: Is it a bug? Multi-nested 
  includes. Server.generalException - makeTypeElement() was told to create a 
  type ...
  You have a bunch of namespace errors in these files. Fix 
  them and try again.I strongly recommend that you use a WSDL editor 
  such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml
. 
  The validate function is very handy.Anne
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote:
  
Here is that files.

  - 
  Original Message - 
  
From: 
  Anne Thomas Manes 
  To: 
  axis-dev@ws.apache.org 
  
  Sent: 
  Wednesday, December 14, 2005 5:18 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  Please post the updated wsdl and schema files.
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote: 
  
Hi, I did It, but still the same Server 
exception. I write this wsdl to create the simpler similar situation as 
with  StyledLayerDescription.xsd,what I solve. So it is my wsdl 
correct?
        
    Ales


  - 
  Original Message ----- 
      
From: 
  Anne Thomas Manes 
  
  To: 
  axis-dev@ws.apache.org 
  Sent: 
  Wednesday, December 14, 2005 4:36 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  You must use  to bring in a 
  schema with the same namespace and  to bring in a 
  schema with a different namespace. So you must change this:
  
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/ows"> 
  
  
  
    <xsd:import 
  namespace="http://www.opengis.net/ows 
  "    
  schemaLocation="./wms_schemas.xsd" 
  />xsd:schema>
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/bla"> 
  
  
  
    
  <xsd:import 
  namespace=" 
  http://www.opengis.net/bla 
  " schemaLocation="./wms-pok2.xsd" 
  /> 
    
  xsd:schema>to 
  this:
  
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/ows"> 
  
  
  
    
  <xsd:include 
  schemaLocation=" 
  ./wms_schemas.xsd" /> 
  
    
  xsd:schema>
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/bla"> 
  
  
  
    
  <xsd:include 
  schemaLocation=" 
  ./wms-pok2.xsd" /> 
  
    
  xsd:schema>Anne
  On 12/14/05, Ales St <[EMAIL PROTECTED]
> 
  wrote: 
  
Hi
I have a problem with multi-nested 
includes, and I thing that it is a bug. I use java Axis 
1.3.
I try in my wsdl file to import two 
difrent namespaces from two difrent xsd files. And then I generate 
classes using WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a 
--server-side  --skeletonDeploy true --NStoPkg urn:Wms=wms 
wms.wsdl ) Then I copy files to server and when I wanted to see 
server generated wsdl Axis error is generated:
 
AXIS error
Sorry, something seems to have gone wrong... here are the 
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}>zzbb", with no 
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException 
faultSubcode: faultString: makeTypeElement() was told to 
create a type "{http://www.opengis.net/bla}>zzbb", with no 
containing elementfaultActor: faultNode: faultDetail: 
{http://xml.apache.org/axis/}hostname:pocitac 
So my question is it is possible 
to import in wsdl two difrent schemas?Or not and it is a bug. I 
 

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

[Anne Thomas Manes]

You have a bunch of namespace errors in these files. 
Fix them and try again.

I strongly recommend that you use a WSDL editor such as Cape Clear SOA
Editor. (It's free.) See http://www.capescience.com/soa/index.shtml. 

The validate function is very handy.

AnneOn 12/14/05, Ales St <[EMAIL PROTECTED]> wrote:







Here is that files.

  - Original Message - 
  
From: 
  Anne Thomas 
  Manes 
  To: 
axis-dev@ws.apache.org 
  Sent: Wednesday, December 14, 2005 5:18 
  PM
  Subject: Re: Is it a bug? Multi-nested 
  includes. Server.generalException - makeTypeElement() was told to create a 
  type ...
  Please post the updated wsdl and schema files.
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote:
  
Hi, I did It, but still the same Server 
exception. I write this wsdl to create the simpler similar situation as 
with  StyledLayerDescription.xsd,what I solve. So it is my wsdl 
correct?
        
    Ales


  - 
  Original Message - 
      
From: 
  Anne Thomas Manes 
  To: 
  axis-dev@ws.apache.org 
  Sent: 
  Wednesday, December 14, 2005 4:36 PM
  Subject: 
  Re: Is it a bug? Multi-nested includes. Server.generalException - 
  makeTypeElement() was told to create a type ...
  You must use  to bring in a 
  schema with the same namespace and  to bring in a schema 
  with a different namespace. So you must change this:
  
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/ows"> 
  
  
    <xsd:import 
  namespace="http://www.opengis.net/ows 
  "    
  schemaLocation="./wms_schemas.xsd" 
  />xsd:schema>
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/bla"> 
  
  
    
  <xsd:import 
  namespace=" 
  http://www.opengis.net/bla 
  " schemaLocation="./wms-pok2.xsd" 
  /> 
    
  xsd:schema>to 
  this:
  
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/ows"> 
  
  
    
  <xsd:include 
  schemaLocation=" 
  ./wms_schemas.xsd" /> 
  
    
  xsd:schema>
  
  <xsd:schema 
  targetNamespace=" 
  http://www.opengis.net/bla"> 
  
  
    
  <xsd:include 
  schemaLocation=" 
  ./wms-pok2.xsd" /> 
    
  xsd:schema>Anne
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote: 
  
Hi
I have a problem with multi-nested 
includes, and I thing that it is a bug. I use java Axis 
1.3.
I try in my wsdl file to import two difrent 
namespaces from two difrent xsd files. And then I generate classes using 
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side  
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files 
to server and when I wanted to see server generated wsdl Axis error is 
generated:
 
AXIS error
Sorry, something seems to have gone wrong... here are the 
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}>zzbb", with no 
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException 
faultSubcode: faultString: makeTypeElement() was told to 
create a type "{http://www.opengis.net/bla}>zzbb", with no 
containing elementfaultActor: faultNode: faultDetail: 
{http://xml.apache.org/axis/}hostname:pocitac 
So my question is it is possible to 
import in wsdl two difrent schemas?Or not and it is a bug. I enclose 
some files which demonstrate this problem. I hope, that they are good 
writed because I beginner in soap. If it is not bug, please write to me, 
how to solve this problem, because it is wery important.
Thank you
        
        Ales

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

[Anne Thomas Manes]

Please post the updated wsdl and schema files.On 12/14/05, Ales St <[EMAIL PROTECTED]> wrote:







Hi, I did It, but still the same Server exception. 
I write this wsdl to create the simpler similar situation as with  StyledLayerDescription.xsd,what I solve. So it is 
my wsdl correct?
        
    Ales

  - Original Message - 
  
From: 
  Anne Thomas 
  Manes 
  To: 
axis-dev@ws.apache.org 
  Sent: Wednesday, December 14, 2005 4:36 
  PM
  Subject: Re: Is it a bug? Multi-nested 
  includes. Server.generalException - makeTypeElement() was told to create a 
  type ...
  You must use  to bring in a schema 
  with the same namespace and  to bring in a schema with a 
  different namespace. So you must change this:
  
  
  <xsd:schema 
  targetNamespace=" http://www.opengis.net/ows">

  
  
    <xsd:import namespace="http://www.opengis.net/ows
 "    
  schemaLocation="./wms_schemas.xsd" />xsd:schema>
  
  <xsd:schema 
  targetNamespace=" http://www.opengis.net/bla">

  
  
    
  <xsd:import namespace=" http://www.opengis.net/bla
" schemaLocation="./wms-pok2.xsd" 
  /> 
    xsd:schema>to this:
  
  
  <xsd:schema 
  targetNamespace=" http://www.opengis.net/ows">

  
  
    
  <xsd:include schemaLocation=" 
  ./wms_schemas.xsd" 
  /> 
    xsd:schema>
  
  <xsd:schema 
  targetNamespace=" http://www.opengis.net/bla">

  
  
    
  <xsd:include schemaLocation=" 
  ./wms-pok2.xsd" /> 
  
    xsd:schema>Anne
  On 12/14/05, Ales 
  St <[EMAIL PROTECTED]> 
  wrote:
  
Hi
I have a problem with multi-nested includes, 
and I thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent 
namespaces from two difrent xsd files. And then I generate classes using 
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side  
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to 
server and when I wanted to see server generated wsdl Axis error is 
generated:
 
AXIS error
Sorry, something seems to have gone wrong... here are the 
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}>zzbb", with no containing 
elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: 
faultString: makeTypeElement() was told to create a type "{http://www.opengis.net/bla}>zzbb", with no containing 
elementfaultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to import in wsdl two 
difrent schemas?Or not and it is a bug. I enclose some files which 
demonstrate this problem. I hope, that they are good writed because I 
beginner in soap. If it is not bug, please write to me, how to solve this 
problem, because it is wery important.
Thank you
        
        Ales

Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...

[Anne Thomas Manes]

You must use  to bring in a schema with the same
namespace and  to bring in a schema with a different
namespace. So you must change this:






  
xsd:schema>







   
  xsd:schema>


to this:






   
  xsd:schema>





   
  xsd:schema>


Anne
On 12/14/05, Ales St <[EMAIL PROTECTED]> wrote:







Hi
I have a problem with multi-nested includes, and I 
thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent 
namespaces from two difrent xsd files. And then I generate classes using 
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side  
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to 
server and when I wanted to see server generated wsdl Axis error is 
generated:
 
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - makeTypeElement() was told to create a type 
"{http://www.opengis.net/bla}>zzbb", with no containing 
elementAxisFaultfaultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: 
faultString: makeTypeElement() was told to create a type 
"{http://www.opengis.net/bla}>zzbb", with no containing 
elementfaultActor: faultNode: faultDetail: 
{http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two difrent schemas?Or 
not and it is a bug. I enclose some files which demonstrate this problem. I 
hope, that they are good writed because I beginner in soap. If it is not bug, 
please write to me, how to solve this problem, because it is wery 
important.
Thank you
        
        Ales

Re: Question concerning criteria of wsdl document for "wrapped" styl e

[Anne Thomas Manes]

Dies,

You might find my bog entry on the wrapped convention helpful:
http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html
(Check the comments for a couple of corrections to the example WSDL.)

Note: If your message definition also contains header parts, Axis 1.2
will not recognize it as "wrapped" style, even though it should.

AnneOn 11/30/05, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:








Dies,


Thanks for the reply.  I was looking in the
wrong place for "docs" concerning this.  I'm using Axis1.2. 
Actually I was checking the wsdd generated and "wrapped" is placed in
the type.  (I didn't type this in manually; WSDL2Java did):


At any rate I'm temporarily removing the operations
in my portType and binding sections to uncover the non-compliant
operations, and have isolated 2 of my operations which are okay, and
two which are not.  

BTW,  a co-worker suggested I debug the wsdl
this way(removing/commenting out the operations and re-adding them) for
my scenario, and although simple, it greatly helped to narrow the areas
down for me..  Since I'm personally always looking for debugging
tips, this might be a good one, speaking generally...Obviously, it may
not work for everyone...

Once again; thanks!!
Cheers!
Peter



-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, November 29, 2005 7:13 PM
To: axis-dev@ws.apache.org
Subject: Re: Question concerning criteria of wsdl document for "wrapped" styl e



Hello Peter,


Document style operations can use the regular mapping
or the "wrapper" style. See section 6.4.1 of the JAX-RPC 1.1
specification (and the example in 6.4.3) for details.

Even if you generate a WSDL with "wrapped" style
operations, the WSDL file will still say "document". IIRC, the WSDD
does say whether Axis identified an operation as being wrapped or not.

Please check whether your WSDL follows the criteria
listed in the spec. If you think it does post your WSDL, maybe someone
can pinpoint the problem.

Regards,
Dies


[EMAIL PROTECTED] wrote:
> Hi,
>  
> Based on the source I viewed, the criteria for considering a wsdl 
> file(s) to be "wrapped" is "
>   + *    Special case of DOCLIT where there is only one parameter
>   + *    and it has the same qname as the operation.  In
>   + *    such cases, there is no actual type with the name...the
>   + *    elements are treated as parameters to the operation
> "
>  
> I'm trying to get wsdl2Java to generate "wrapped" and keep getting 
> "document".  I'm wondering if there are any other criteria I should 
> look
> for(correct) in my wsdl,
> in order to produce this type. I'm coding the type="document" in the main
> .wsdl file, and unfortunately the resulting .java files and .wsdd are not
> converting to "wrapped".  Or is there a place in the source where I can
> determine this information without being completely abstracted;-)
>  
> Thanks for your time!
> Peter A
> 

Re: [axis2] WSDL2Code throws NPE on complex type

[Anne Thomas Manes]

I agree that the NPE isn't particularly informative, but you do have a
number of errors in your WSDL. I suggest you get a WSDL editor with a
validation function. 
The Cape Clear SOA Editor is free and works pretty well.

First error:
You have two elements defined in your schema named "elementReturnWeb_Base"

Second set of errors:
You need to be more careful with your namespace qualifications. In your
message parts, you don't qualify the referenced elements, so it
defaults to the wsdl namespace. e.g., 

This:
  

should be this:
  

And finally:
When using document style, a message must contain at most one body
part. You have two body parts in your login request. You must create a
wrapper element (preferably with the same name as the operation) and
use that as your input element. e.g., 

 
  
   
 
 
    
   
 

 
  
 

Anne
On 11/23/05, iksrazal <[EMAIL PROTECTED]> wrote:
Hi all,I'm trying to convert a simple wsdl from rpc encoded to doc lit and wsdl 2.0.Please excuse if I'm making a simple error here. However, the wsdl is validxml. I'm getting:./WSDL2Java.sh -uri wout/axis-
jira-doclit.wsdl -o wout/...Exception in thread "main" java.lang.NullPointerException  atorg.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.generateWrapperSchema(WSDLPump.java:633)  atorg.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.populateDefinition
(WSDLPump.java:153)  atorg.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.pump(WSDLPump.java:100)  atorg.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build(WSDL1ToWOMBuilder.java:126)  atorg.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build
(WSDL1ToWOMBuilder.java:95)  atorg.apache.axis2.wsdl.codegen.CodeGenerationEngine.getWOM(CodeGenerationEngine.java:117)  atorg.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java
:47)  at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:30)  at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)The line throwing is:if (XMLSCHEMA_NAMESPACE_URI.equals(schemaTypeName.getNamespaceURI
())){Here's my wsdl, once again please excuse if there is an error, but even stillperhaps the the error should'nt be NPE.targetNamespace="http://com/callcentreweb"xmlns:tns="http://com/callcentreweb" xmlns="
http://schemas.xmlsoap.org/wsdl/"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/
"xmlns:ns2="http://com/callcentreweb/types">   http://com/callcentreweb/types
"xmlns:tns="http://com/callcentreweb/types"xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/
"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
"xmlns="http://www.w3.org/2001/XMLSchema">  http://schemas.xmlsoap.org/soap/encoding/"/
>

  
  
 
      
  
    type="tns:CallCentreWebEndpoint">  
http://schemas.xmlsoap.org/soap/http"style="document"/>
      binding="tns:CallCentreWebEndpointBinding">  location="http://127.0.0.1"/>
--Faster, better, cheaper - choose two of the above.   - Old engineering proverbIt's easier to ask for forgiveness than permission.   - Another oldengineering proverb

Re: [Axis2] SOAPMessageContext

[Anne Thomas Manes]

+1 to separating the programming model from the implementation model.

AnneOn 11/13/05, Paul Fremantle <[EMAIL PROTECTED]> wrote:
So I think the approach will work, but we are introducing a performance overhead straight away. I know its just a method call. I
would like to try the approach proposed, and if it breaks lets fix it.
Of course if the Axis2 community -1s it then we can say its broken.
I personally still think that the SMC concept has value in the
world of Axis2, and I think we've never done enough in Axis1 or 2 to
separate out the customer's programming model from the implementation
model. That's what the SMC is doing as I see it.
PaulOn 11/13/05, Sanjiva Weerawarana <
[EMAIL PROTECTED]> wrote:

On Sun, 2005-11-13 at 11:51 +0600, Ajith Ranabahu wrote:> Ok, I don't want to look like the mad scientist who comes up with the> craziest theory always but I humbly think I'm talking about the same> issue of allowing the SOAPMsgCtx to co-exist without corrupting (or
> rather effecting) the Axis2 system. However I also feel that I lack> knowledge of some discussions which were in the mailing lists (Silly> me) so I won't push the msgCtxtFactory theory anymore.

Ajith, the problem with the context factory approach is that Synapserequires something that'll allow Axis2 to continue to work. We can ofcourse introduce a factory, but in order for whatever that's produces to

enable Axis2 to work, it needs to extend the current Axis2 messagecontext (right?).That's precisely the problem: there's too much stuff in there forSynapse users to care/worry about.> BTW is this SOAPMC needed to be implemented as part of Axis2 ? The
> original mail seems to imply that the SOAP specific methods were> specifically for Synapse, in which case the particular 'Ctxt' needs to> be part of Synapse and not Axis2!> Am I deeply mislead or missing a crucial piece of logic here ?
I much prefer Ant's suggestion in reply to your mail - create a new typeand embed Axis2's MC inside it.Ant, you seem to imply that that approach was suggested earlier andrejected .. what I was arguing against earlier was creating an
*alternate* MC; you are not suggesting an alternate but rather embeddingthe Axis2 MC and use delegation to expose what Synapse finds useful. Ilike that approach.Sanjiva.

Re: Body elements get copied into Headers !

[Anne Thomas Manes]

Code?
WSDL?
WSDD?
On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
We are getting pretty strange problem when trying to generate or publish a soap 
message. All the paremeters which should have been part of the SOPA BODY element are copying into the SOAP headers.The actually body tag is empty  Anyone if has faced a similar issue or problem please share the info, we would 
be very thankful. Using WASIE 5.1.7 , with axis 1.2.1 , We are trying to build a client which resides in non-websphere server.http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
http://peoplesoft.com/WG_CHARTFIELD3">V-04


Check Out the new free AIM(R) Mail -- 2 GB of storage and industry-leading spam and email virus protection.

Re: [Axis2] Road Map for next release

[Anne Thomas Manes]

I caution you regarding the "XMethods core services". As far as I'm
aware, XMethods hasn't vetted any of the services listed on the site,
and many contain invalid WSDL. I recommend that you stick with
commercial WSDLs (Google, Amazon, Yahoo, EBay, Salesforce.com, UDDI,
etc.) as well as whatever interop endpoints you can find.

AnneOn 11/6/05, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Ajith / Folks1) Please can we do a release ASAP? The core
changes (like renaming to AxisService) mean that it would be good to
have a stable build with these in, plus the latest ADB.2) The obvious list of services to support are:
All of Google, Amazon, Yahoo, XMethods core services
(stockquote, currency, etc). I would like to see some from strikeiron.
Any WSDL interop tests. Axis1 samples???That would be a good starter set. Paul
On 11/6/05, Ajith Ranabahu <
[EMAIL PROTECTED]> wrote:
Hi All,
It's partly my fault that ADB did not get tested with Amazon or Google
or any other widely used WSDLs. However ADB does not understand SOAP
encoding (!) and the Google service cannot be directly codegned. One
other limitation of ADB is that it does not support imports (yet) which
I intend to fix before the end of this indigo plugfest (with the hope
of  using ADB for Indigo interoperability as well)
In the mean time anyone is welcome to write test cases for testing the
ADB stuff. I've already written some reflection based tests (these
tests have to be reflection based since the code generates during the
build!) and are in the org.apache.axis2.databinding.schema.populate
package in the test folder of the codegen module.
te:On Thu, 2005-11-03 at 13:34 -0500, Tom Jordahl wrote
> What I would hope is that ADB can be used with a typical WSDL found in> the wild – UDDI, Amazon.com

, Google, etc, etc.  If it doesn't work> with the WSDL users are likely to want to consume, then they will just
> walk away.  Or maybe they will figure out how to use XMLBeans.  Maybe.Oh absolutely- if ADB doesn't work with Google, Amazon, Salesforce,Yahoo etc. then its no use at all. Can you help identify a set of
"widely used" services like that that need to be test cases? I've askedfor that repeatedly but there haven't been many responses. If we have aset of WSDLs that'll help identify what features need to work and which
are not needed for "normal use".Sanjiva.-- Ajith Ranabahu

Re: .net java InvalidCastException

[Anne Thomas Manes]

We need more information ...
Either provide the entire WSDL, or provide all pertinent parts that
apply to the operation (all types and messages plus the portType and
binding)

AnneOn 10/26/05, Kuldeep Malhotra <[EMAIL PROTECTED]> wrote:













Hi i am using apache axis to write web services but when
.net calls my service it gives the following error.

System.InvalidCastException: Cannot assign object of type
SystemWebService.d31504.organisationdetails to an object of type SystemWebService.d31504.organisationdetails[].

 

here is the part of my wsdl

 

 

   

 

   
 

   


   
  

   


 

   

 

   


   


   


   


   


 

i am not sure is this the right place to ask my question ,
any one help.