Yeah, if you could point me in the right direction, I'm interested. Let me know what I could do to help.
On 12/3/05, Chathura Herath <[EMAIL PROTECTED]> wrote: > If we are talking about data binding using jaxb, it can be done > without much of a hassel and we had this idea in mind when we did the > xml-beans databinding. So the WSDL2Java code generation engine is more > than extensible for this. > > Chathura > > On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Ron, > > > > This is definitely possible in Axis2. Willing to help? there is some > > code in the scratch area which we can polish up and update. > > > > thanks, > > dims > > > > On 12/2/05, Ron Mexico <[EMAIL PROTECTED]> wrote: > > > I believe that could do the trick. How, then, would my marshalling take > > > place? > > > I'd basically have to pull apart the whole incoming soap payload only to > > > begin my marshalling. > > > Or is there something I'm missing? > > > The reason I'm asking, and even considering introducing axis into our > > > current architecture is for testing purposes. It's laborous to test our > > > application in it's current state. We've hacked together some jsps > > > that'll > > > allow for form completion, then assembling the XML and finally submitting > > > it. > > > it's quite lame, for lack of a better term. > > > > > > On 12/2/05, Guy Rixon <[EMAIL PROTECTED]> wrote: > > > > Suppose you write your own WSDL instead of letting axis generate it. You > > > can > > > > then include your XSDs in the types section of the WSDL. If you use > > > absolute > > > > URLs in the schemaLocation attributes of the import statements for teh > > > XSDs, > > > > then anybody who sees you WSDL can also find the XSDs. Does this suit > > > > your > > > > purpose? > > > > > > > > On Fri, 2 Dec 2005, Ron Mexico wrote: > > > > > > > > > let me elaborate. right now our process is very elementary. > > > > > "consumers" need to have copies of our XSDs. they format their xml > > > > > accordingly, then submit that xml essentially as a string to a > > > > > servlet. then our servlet marshals that string which it receives > > > > > basically as a request parameter. > > > > > i'm looking to make this process a little more mature, so i was hoping > > > > > that Axis would be able to broadcast our XSDs - much like it does for > > > > > a WSDL. is that possible? > > > > > > > > > > >I'd just send the String as a parameter to the web service and > > > > > >marshal > > > that. > > > > > >jaxb by its nature automatically validates against the xsd. Perhaps I > > > > > >misunderstand the question. All you need is the jarred classes from > > > > > >the > > > xsd > > > > > >on the web service side. > > > > > > > > > > > >An important point is that Axis2 uses XMLBeans heavily - sort of an > > > open > > > > > >source alternative to jaxb. From what I gather sun's implementation > > > > > >of > > > JWSDP > > > > > >2.0 will be based off of jaxb. > > > > > > > > > > > >HTH, > > > > > >iksrazal > > > > > > > > > > > > > > > > > > > > > we've got an application where clients send us xml formatted to > > > > > > match > > > > > > the XSD's that we use internally to create our generated objects. > > > > > > we simply marshall/unmarshall that xml internally. > > > > > > > > > > > > i'd like to make this more of a web-service. is it possible to have > > > > > > axis broadcast the XSDs as the wsdl for each service? > > > > > > > > > > > > furthermore, is it possible to have axis integrate with jaxb so the > > > > > > incoming xml would simply be converted right to the generated > > > > > > objects? > > > > > > > > > > > > thanks > > > > > > > > > > > > > Guy Rixon > > > [EMAIL PROTECTED] > > > > Institute of Astronomy Tel: > > > +44-1223-337542 > > > > Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523 > > > > > > > > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > > > > -- > Chathura Herath > http://www.bloglines.com/blog/chathurah >
