Well, here's some more info. I actually had a message from a TME (GLUE) person, expressing interest in my project, so we'll see about pursuing that.
I've also read once through the Sun DSMLv2 provider docs. Tantalizing. Everything is there for a client to a "DSMLv2 server", but I'm trying to BE the DSMLv2 server, and the reverse operations (i.e., generate a DOM doc with WSDL schema from JNDI objects like Context) don't seem to be there. No replies from the Sun shepherds of the JNDI-INTEREST list.
I also just finished reading the very long & informative thread on axis-user on document vs RPC styles. Whew!
So the current working hypothesis is to use the Sun providers to generate a String version of a DSML response (a BatchResponse element) and give that to Axis, somehow generating a doc/literal SOAP body that refers to the DSML schema. Still need to get the incoming BatchRequest document deserialized into a BatchRequest object. I don't suppose WSDL2Java will do that for me? What do you think of this approach? (Is this that "mentoring" phenomenon somebody postulated?)
And another thing . . . Some of these directory search responses will be pretty long. Is Axis somehow going to figure out how to do stream parsing (SAX?) on them? That would seem to be magic.
Next steps: actually try using some of the Axis and Sun tools.
Martin
Anne Thomas Manes wrote:
I think I mentioned that I didn't think that WASP supported DSML. WASP will fully generate all the mappings between XML and Java objects for you, though, whether you are using rpc or document. (and if you like to use an IDE, you might try WASP Developer (for NetBeans, Eclipse, and JBuilder). I believe that GLUE does document style XML/Java mapping equally well.But as I said before ... if the Sun provider does it for you, go with it. Anne
