I found it! It was too close to be easy to discover. What I was looking
for is the method writeSchema() contained in every Serializer
implementataion.
Speaking of, I have another question:
How do I specify the type in <element>-Tags correctly in this method?
Something like setAttribute("type","xsd:dateTime") is fine but what if
the namespace of XML Schema is mapped onto another prefix? As far as I
understood namespaces and prefixes is that the prefix can change while
referring to the same namespace. But where can the actual prefix for the
namespace be found?
Thanks in advance,
Werner Jansen
> -----Original Message-----
> From: Jansen Werner [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 30, 2006 10:13 AM
> To: [email protected]
> Subject: RE: Howto add schema definition of type to wsdl?
>
> Hallo there,
>
> thanks for you response :)
>
> ScheduleMetaData is not defined as a JavaBean, it's mapped using a
> <typemapping> in the axis configuration and using our own Serializers
> and Deserializers.
>
> I did not run java2wsdl, but I'll try that right away :)
> The wsdl file I examined is the one generated by axis on the fly by
> specifying ?wsdl at the end of the URL.
>
> This is how the service is defined in server-config.wsdd:
>
> <service name="ScheduleNotifyService" provider="java:RPC"
> [... namespace definitions ...]
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> <parameter name="className"
>
> value="de.eonis.prs.romeo.comm.ve.schedule.soap.ws.WsScheduleN
> otifyServi
> ce" />
>
> <parameter name="allowedMethods" value="*" />
>
> <namespace>http://www.eon-is.com/namespaces/prs/1.0/schedule/v
> e</namespa
> ce>
>
>
> <typeMapping ... [ some other typemappings following the same rules as
> ScheduleMetaData, schedule:Result for example ] />
>
> <typeMapping qname="schedule:ScheduleMetaData"
> languageSpecificType="java:de.eonis.[...].ScheduleMetaData"
> serializer="de.eonis.[..].axis.VEScheduleMetaDataSerFactory"
> deserializer="de.eonis.[...].axis.VEScheduleMetaDataDeserFactory"
> />
>
> <operation name="scheduleNotify"
> qname="schedule:scheduleNotify">
>
> <parameter name="scheduleMetaData"
> qname="schedule:scheduleMetaData"
> type="schedule:ScheduleMetaData"
> mode="IN" />
>
> <parameter qname="schedule:result" name="result"
> type="schedule:Result" mode="OUT" />
> </operation>
>
> </service>
>
>
> And yes, we're using Axis1 1.3
>
> Thanks for any help!
> ________________________________
>
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 29, 2006 5:32 PM
> To: [email protected]
> Subject: Re: Howto add schema definition of type to wsdl?
>
>
> Is ScheduleMetaData defined as a JavaBean?
> Did you run java2wsdl?
>
> Or did you perhaps try to deploy the service using the .jws
> option?
> If you are using complex types, then you can't use the .jws
> option.
>
> (I'm assuming that you're using Axis 1.)
>
> Anne
>
>
> On 6/29/06, Jansen Werner <[EMAIL PROTECTED] > wrote:
>
> Hallo everybody,
>
> I have a web service called ScheduleNotifyService. It
> has a single
> operation called "scheduleNotify". This operation needs
> a parameter of
> java type ScheduleMetaData. So I wrote a
> Serializer/Deserializer pair
> with their corresponding factories. This works.
>
> But: When I call my wsdl using
> ScheduleNotifyService?wsdl, it defines a
> part
>
> <wsdl:part name="scheduleMetaData"
> type="tns1:ScheduleMetaData"/>
>
> without defining ScheduleMetaData in the document. Is it
> possible to
> automatically include the definition for my java types
> somehow? Axis
> could - i suppose - extract the definition from the
> serializer. Do I
> need to manually include the definition?
>
> I hope I made myself clear. :) If not, don't hesitate to
> ask for further
> information ... :)
>
> Greetings from Munich,
>
> Werner Jansen
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> <mailto:[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]
