If you've defined the schema separately, you can import the schema:
<wsdl:types>
<xsd:schema>
<xsd:import namespace="[your schema namespace]"
schemaLocation="[relative path to your schema file]"/>
</xsd:schema>
</wsdl:types>
Otherwise, you can just define the schema inline.
If you run java2wsdl specifying wrapped style and literal use, it will
generate the schema for you. As long as your interface doesn't use
Collections, it should work pretty well, but you need to upgrade to
Axis 1.4. Arrays and nulls can sometimes cause a few stumbling blocks,
but you should be able to make it work.
Anne
On 10/16/07, Dimitris Mouchritsas <[EMAIL PROTECTED]> wrote:
> Walker, Jeff wrote:
> > Anne means Document Literal Wrapped style.
> > Go here to see a good definition of the 4 major styles:
> > http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/
> > The style we are advocating means you need to write XML Schema and
> > place it into your wsdl file. Then you run your wsdl file through
> > WSDL2Java to generate a bunch of serializer and deserializer classes.
> > The command is something like:
> > %>java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy
> > true <web_service_name>.wsdl
> > Regards,
> > -jeff
> >
> >
> > ------------------------------------------------------------------------
> > *From:* M N [mailto:[EMAIL PROTECTED]
> > *Sent:* Tuesday, October 16, 2007 8:56 AM
> > *To:* [email protected]
> > *Subject:* Re: Axis 1.4 and .NET interop
> >
> > Thanks Anne.
> >
> > when you say Java specific types I assume you talking about
> > something like Collections,arraylists etc. So far I dont have
> > anything like that.
> >
> >
> >
> > */Anne Thomas Manes <[EMAIL PROTECTED]>/* wrote:
> >
> > Wrapped style is the way to go. But you still might encounter
> > problems
> > if your service is exposing Java-specific types.
> >
> > Anne
> >
> > On 10/16/07, M N wrote:
> > > We have been using AXIS 1.1 ( yeah I know its old) for past
> > few years with
> > > Jboss and everythings looks fine.We have removed the
> > jbossws.sar directory
> > > completely.
> > >
> > > Anyway so we have this new requirement where we have to
> > provide webservices
> > > to a .NET client. No matter what we provide .NET client
> > keeps getting
> > > exceptions. We found yesterday that .NET does not support
> > RPC transport from
> > > java webservices. So we decided to use DOCUMENT/LITERAL
> > style in WSDL (
> > > created using ANT JAVA2WSDL tool) . But then even when I
> > test the WS from
> > > Java side it keeps giving me NOT A ARGUMENT(or something
> > like that) error. I
> > > read later on that AXIS 1.1 doesnt support the
> > DOCUMENT/LITERAL style well.
> > > So we decided to upgrade to 1.4.
> > >
> > > I still kept getting the NOT A ERROR except when I
> > > mention in ANT JAVA2WSDL utility that I need WRAPPED/LITERAL
> > style. Any
> > > other style doesnt seem to work. So now with WRAPPED/LITERAL
> > style my Java
> > > client stubs can successfully work with Java WSs. We will be
> > testing it with
> > > .NET tomorrow. I am wondering if it will work and there wont
> > be any
> > > exceptions.
> > >
> > > Thanks
> > >
> > >
> > > ________________________________
> > > Moody friends. Drama queens. Your life? Nope! - their life,
> > your story.
> > > Play Sims Stories at Yahoo! Games.
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ------------------------------------------------------------------------
> > Pinpoint customers
> >
> > <http://us.rd.yahoo.com/evt=48250/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v9.php?o=US2226&cmp=Yahoo&ctv=AprNI&s=Y&s2=EM&b=50>who
> > are looking for what you sell.
> >
> Mmm, how exactly do you put your schema in your wsdl file? And is there
> a way to validate the xml comming in and out (with RawXMLInOutReceiver)
> in Java 1.4;
>
> ---------------------------------------------------------------------
> 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]
