Without knowing complete details of what the "differences" are, this
is a very hard question to answer.
If your beans "look" like the jaxb beans, but with additional business
logic methods added, it's fairly straight forward. You can pretty
much copy the JAXB annotations over to your beans and just use your
beans. With jaxb, you can even add extra methods that are called
after the data is read to finish any extra wiring you need done.
If you get it so your objects are usable with JAXB, you can use jaxb
customizations at code generation time to tell it to map the schema
types into your objects instead of code generating new objects. You
can actually do this piece meal. Map the objects you have working
and code generate the rest.
Dan
On Jun 26, 2008, at 2:21 AM, Kuga wrote:
Hi,
We have several existing Java POJO classes in client side.
Now we are planning to use the WSDL, as such we have defined the WSDL
definition, based on server side schema, and then generated Java
objects. I
would not be able to just use these generated classes in the client
side
instead of my POJO, as some of the POJO has some business logic also
involved in them.
As such can I use my POJO instead of the WSDL generated Java
objects. Where
do we need to add these mappings in the WSDL file.
Any help is appreciated.
Thanks & Regards
Kuga
--
View this message in context:
http://www.nabble.com/Using-existing-Java-objects-as-against-the-WSDL-generated-java-objects%21-tp18127291p18127291.html
Sent from the cxf-user mailing list archive at Nabble.com.
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
