Re: Required Fields

[Todd Orr]

I got it. So WSDL first is a better approach. Thanks for your input.>> when something is missing in an open source project perhaps that thing is your>> contribution. :)I'm thinking about it. It's no small change and would require JDK5, etc. But, I think it would help.
On 11/23/05, Ron Reynolds <[EMAIL PROTECTED]> wrote:
i've found (the hard way) that putting your objects before your XML whenwriting web services makes for more problems than it solves (and tends toproduce very inefficient XML, especially if you go with a non-encoded
(literal) approach).  i found it much easier and more efficient in general tothink about the API operations, then the XML to the API, write the WSDL, letAxis generate the objects, then write code to map those objects into any other
object model(s) i might have on the client and/or server sides.  much simpler(and possibly more efficient) than trying to write customserializers/deserializers to map pre-existing objects into XML (especially if
that XML is substantially different from the original object).just my $0.02 worth...when something is missing in an open source project perhaps that thing is yourcontribution. :)> I don't know how. I imagine a world where I can put a little @required
> annotation next to a property in my pojo. The java2wsdl would recognize this> and produce the correct schema. Forgive me, I'm still getting a handle on> SOAP. Maybe I've got pie in the sky hopes. I've gotten used to working with
> (what I've found to be) highly productive frameworks like ejb3, spring, and> tapestry. I feel like something is missing here. I will hand code this stuff> if I have to, but this solution has improvement written all over it. I've
> looked around a little bit (http://ws.apache.org/axis/java/releases.html,> for example) and I don't see any roadmap for these type of conveniences.
> Are there any plans to ease our burdens?>> On 11/22/05, Ron Reynolds <[EMAIL PROTECTED]> wrote: AH!  that's backwards from the way i build my services.  sorry, dunno
>> that one - how WOULD Java2WSDL be able to tell that a field is required>> vs optional?  it seems to use primitives for required fields,>> object-wrappers for optional.  but i'm not sure if it works in reverse.
>> good luck.>> Todd Orr wrote: > I'm trying to produce wsdl's from my service pojos. How do I specify>> > which properties are mandatory so that when the java2wsdl runs the
>> > schema will be correct?>> >

Re: Required Fields

[Ron Reynolds]

i've found (the hard way) that putting your objects before your XML when
writing web services makes for more problems than it solves (and tends to
produce very inefficient XML, especially if you go with a non-encoded
(literal) approach).  i found it much easier and more efficient in general to
think about the API operations, then the XML to the API, write the WSDL, let
Axis generate the objects, then write code to map those objects into any other
object model(s) i might have on the client and/or server sides.  much simpler
(and possibly more efficient) than trying to write custom
serializers/deserializers to map pre-existing objects into XML (especially if
that XML is substantially different from the original object).

just my $0.02 worth...

when something is missing in an open source project perhaps that thing is your
contribution. :)

> I don't know how. I imagine a world where I can put a little @required
> annotation next to a property in my pojo. The java2wsdl would recognize this
> and produce the correct schema. Forgive me, I'm still getting a handle on
> SOAP. Maybe I've got pie in the sky hopes. I've gotten used to working with
> (what I've found to be) highly productive frameworks like ejb3, spring, and
> tapestry. I feel like something is missing here. I will hand code this stuff
> if I have to, but this solution has improvement written all over it. I've
> looked around a little bit (http://ws.apache.org/axis/java/releases.html,
> for example) and I don't see any roadmap for these type of conveniences.
> Are there any plans to ease our burdens?
>
> On 11/22/05, Ron Reynolds <[EMAIL PROTECTED]> wrote:
>>
>> AH!  that's backwards from the way i build my services.  sorry, dunno
>> that one - how WOULD Java2WSDL be able to tell that a field is required
>> vs optional?  it seems to use primitives for required fields,
>> object-wrappers for optional.  but i'm not sure if it works in reverse.
>> good luck.
>> Todd Orr wrote:
>>
>> > I'm trying to produce wsdl's from my service pojos. How do I specify
>> > which properties are mandatory so that when the java2wsdl runs the
>> > schema will be correct?
>> >

Re: Required Fields

[Todd Orr]

I don't know how. I imagine a world where I can put a little @required annotation next to a property in my pojo. The java2wsdl would recognize this and produce the correct schema. Forgive me, I'm still getting a handle on SOAP. Maybe I've got pie in the sky hopes. I've gotten used to working with (what I've found to be) highly productive frameworks like ejb3, spring, and tapestry. I feel like something is missing here. I will hand code this stuff if I have to, but this solution has improvement written all over it. I've looked around a little bit (
http://ws.apache.org/axis/java/releases.html, for example) and I don't see any roadmap for these type of conveniences.  Are there any plans to ease our burdens?
On 11/22/05, Ron Reynolds <[EMAIL PROTECTED]> wrote:
AH!  that's backwards from the way i build my services.  sorry, dunnothat one - how WOULD Java2WSDL be able to tell that a field is requiredvs optional?  it seems to use primitives for required fields,object-wrappers for optional.  but i'm not sure if it works in reverse.
good luck.Todd Orr wrote:> I'm trying to produce wsdl's from my service pojos. How do I specify> which properties are mandatory so that when the java2wsdl runs the> schema will be correct?
>> On 11/22/05, * Ron Reynolds* <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:>> when did pojo's come into the picture?
> i was referring to the client-side api classes generated by> WSDL2Java -> the  section of the WSDL is XML Schema, which has all the rules> for "required", "optional", and so forth.  WSDL2Java consumes the XSD
> and produces Java code (in the form of the client api data> classes) that> enforce those rules.  it sounded like you wanted to change those rules> post-WSDL2Java.  but now it sounds like you're not using WSDL2Java at
> all?  i guess i'm not sure how you generated your service or your> client> - is the client-side hand-written (thus pojo) or generated?  or> are you> talking straight XML to your service?  sorry, it's getting late - i'm
> rambling...> ...ron.> Todd Orr wrote:>> > Really, how? Do I annotate the methods or something? How does the> > Java2WSDL generate a WSDL that reflects the constraints on my pojo?
> >> > On 11/22/05, *Ron Reynolds * <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> > [EMAIL PROTECTED] [EMAIL PROTECTED]>>> wrote:> >> > that sort of info is normally contained in the XSD and embedded
> > into the code> > via WSDL2Java...  you're trying to change a WSDD so that the> > generated WSDL's> > XSD has requirements that aren't mirrored in the original WSDL
> > from which the> > WSDD was generated? :-?  from what i've seen the client-side> > validation is> > embedded into the client-side stub code and that also is
> extracted> > from the> > WSDL/XSD from which it was generated.> >> > > Pardon my noobiness, but I've googled the hell out of this> to no
> > avail. Is> > > there a way to specify required properties in the wsdd file so> > that the> > > schema gets generated accordingly? All I want to do is
> specify> > required> > > elements so that the validation can occur at XML> validation time> > before> > > hitting the code.
> > >> > > Thanks,> > > T> > >> >> >> >>>

Re: Required Fields

[Ron Reynolds]

AH!  that's backwards from the way i build my services.  sorry, dunno 
that one - how WOULD Java2WSDL be able to tell that a field is required 
vs optional?  it seems to use primitives for required fields, 
object-wrappers for optional.  but i'm not sure if it works in reverse.  
good luck.

Todd Orr wrote:

I'm trying to produce wsdl's from my service pojos. How do I specify 
which properties are mandatory so that when the java2wsdl runs the 
schema will be correct?


On 11/22/05, * Ron Reynolds* <[EMAIL PROTECTED] 
> wrote:


when did pojo's come into the picture?
i was referring to the client-side api classes generated by
WSDL2Java -
the  section of the WSDL is XML Schema, which has all the rules
for "required", "optional", and so forth.  WSDL2Java consumes the XSD
and produces Java code (in the form of the client api data
classes) that
enforce those rules.  it sounded like you wanted to change those rules
post-WSDL2Java.  but now it sounds like you're not using WSDL2Java at
all?  i guess i'm not sure how you generated your service or your
client
- is the client-side hand-written (thus pojo) or generated?  or
are you
talking straight XML to your service?  sorry, it's getting late - i'm
rambling...
...ron.
Todd Orr wrote:

> Really, how? Do I annotate the methods or something? How does the
> Java2WSDL generate a WSDL that reflects the constraints on my pojo?
>
> On 11/22/05, *Ron Reynolds * <[EMAIL PROTECTED]

> >> wrote:
>
> that sort of info is normally contained in the XSD and embedded
> into the code
> via WSDL2Java...  you're trying to change a WSDD so that the
> generated WSDL's
> XSD has requirements that aren't mirrored in the original WSDL
> from which the
> WSDD was generated? :-?  from what i've seen the client-side
> validation is
> embedded into the client-side stub code and that also is
extracted
> from the
> WSDL/XSD from which it was generated.
>
> > Pardon my noobiness, but I've googled the hell out of this
to no
> avail. Is
> > there a way to specify required properties in the wsdd file so
> that the
> > schema gets generated accordingly? All I want to do is
specify
> required
> > elements so that the validation can occur at XML
validation time
> before
> > hitting the code.
> >
> > Thanks,
> > T
> >
>
>
>

Re: Required Fields

[Todd Orr]

I'm trying to produce wsdl's from my service pojos. How do I specify which properties are mandatory so that when the java2wsdl runs the schema will be correct?On 11/22/05, 
Ron Reynolds <[EMAIL PROTECTED]> wrote:
when did pojo's come into the picture?i was referring to the client-side api classes generated by WSDL2Java -the  section of the WSDL is XML Schema, which has all the rulesfor "required", "optional", and so forth.  WSDL2Java consumes the XSD
and produces Java code (in the form of the client api data classes) thatenforce those rules.  it sounded like you wanted to change those rulespost-WSDL2Java.  but now it sounds like you're not using WSDL2Java at
all?  i guess i'm not sure how you generated your service or your client- is the client-side hand-written (thus pojo) or generated?  or are youtalking straight XML to your service?  sorry, it's getting late - i'm
rambling..ron.Todd Orr wrote:> Really, how? Do I annotate the methods or something? How does the> Java2WSDL generate a WSDL that reflects the constraints on my pojo?>
> On 11/22/05, *Ron Reynolds * <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:>> that sort of info is normally contained in the XSD and embedded
> into the code> via WSDL2Java...  you're trying to change a WSDD so that the> generated WSDL's> XSD has requirements that aren't mirrored in the original WSDL> from which the
> WSDD was generated? :-?  from what i've seen the client-side> validation is> embedded into the client-side stub code and that also is extracted> from the> WSDL/XSD from which it was generated.
>> > Pardon my noobiness, but I've googled the hell out of this to no> avail. Is> > there a way to specify required properties in the wsdd file so> that the> > schema gets generated accordingly? All I want to do is specify
> required> > elements so that the validation can occur at XML validation time> before> > hitting the code.> >> > Thanks,> > T
> 

Re: Required Fields

[Ron Reynolds]

when did pojo's come into the picture? 
i was referring to the client-side api classes generated by WSDL2Java - 
the  section of the WSDL is XML Schema, which has all the rules 
for "required", "optional", and so forth.  WSDL2Java consumes the XSD 
and produces Java code (in the form of the client api data classes) that 
enforce those rules.  it sounded like you wanted to change those rules 
post-WSDL2Java.  but now it sounds like you're not using WSDL2Java at 
all?  i guess i'm not sure how you generated your service or your client 
- is the client-side hand-written (thus pojo) or generated?  or are you 
talking straight XML to your service?  sorry, it's getting late - i'm 
rambling...

...ron.
Todd Orr wrote:

Really, how? Do I annotate the methods or something? How does the 
Java2WSDL generate a WSDL that reflects the constraints on my pojo?


On 11/22/05, *Ron Reynolds * <[EMAIL PROTECTED] 
> wrote:


that sort of info is normally contained in the XSD and embedded
into the code
via WSDL2Java...  you're trying to change a WSDD so that the
generated WSDL's
XSD has requirements that aren't mirrored in the original WSDL
from which the
WSDD was generated? :-?  from what i've seen the client-side
validation is
embedded into the client-side stub code and that also is extracted
from the
WSDL/XSD from which it was generated.

> Pardon my noobiness, but I've googled the hell out of this to no
avail. Is
> there a way to specify required properties in the wsdd file so
that the
> schema gets generated accordingly? All I want to do is specify
required
> elements so that the validation can occur at XML validation time
before
> hitting the code.
>
> Thanks,
> T
>

Re: Required Fields

[Todd Orr]

Really, how? Do I annotate the methods or something? How does the Java2WSDL generate a WSDL that reflects the constraints on my pojo?On 11/22/05, Ron Reynolds
 <[EMAIL PROTECTED]> wrote:that sort of info is normally contained in the XSD and embedded into the code
via WSDL2Java...  you're trying to change a WSDD so that the generated WSDL'sXSD has requirements that aren't mirrored in the original WSDL from which theWSDD was generated? :-?  from what i've seen the client-side validation is
embedded into the client-side stub code and that also is extracted from theWSDL/XSD from which it was generated.> Pardon my noobiness, but I've googled the hell out of this to no avail. Is> there a way to specify required properties in the wsdd file so that the
> schema gets generated accordingly? All I want to do is specify required> elements so that the validation can occur at XML validation time before> hitting the code.>> Thanks,> T
>

Re: Required Fields

[Ron Reynolds]

that sort of info is normally contained in the XSD and embedded into the code
via WSDL2Java...  you're trying to change a WSDD so that the generated WSDL's
XSD has requirements that aren't mirrored in the original WSDL from which the
WSDD was generated? :-?  from what i've seen the client-side validation is
embedded into the client-side stub code and that also is extracted from the
WSDL/XSD from which it was generated.

> Pardon my noobiness, but I've googled the hell out of this to no avail. Is
> there a way to specify required properties in the wsdd file so that the
> schema gets generated accordingly? All I want to do is specify required
> elements so that the validation can occur at XML validation time before
> hitting the code.
>
> Thanks,
> T
>