Not to disuade you from using Axis, but you might consider using either GLUE or WASP, both of which provide better support for doc/literal than Axis does. You wouldn't need to worry about building a custom serializer. Given a full schema, they will generate all the serializer code you need. Both of these products are available for free, and both run in Tomcat.
I know that WASP includes a SOAP JNDI provider, although I doubt if it supports DSML. (I think it only supports a JNDI lookup function.) It's part of the EJB integration tool. You might find it helpful in your efforts. See http://www.systinet.com/doc/wasp_jserver/applicationIntegration/j2eeIntegrat ion.html#j2eeIntegration.overview I would hope that Sun's DSML provider would do most of what you need, though. Good luck. > -----Original Message----- > From: Martin Smith [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 01, 2003 11:29 PM > To: [EMAIL PROTECTED] > Subject: Re: DSML activity? > > > Anne-- > > I just did the download. It's not big. Not a lot of explanatory text > that I've found yet, however; and the current (on-line) JNDI tutorial > doesn't seem to cover DSML either. > > Here's a bit fuller statement of what I'm doing. My immediate interest > is to provide a web-services entry point to an LDAP directory > (specifically, directory.gov) , which is already accessible via browser > (http) and LDAP. > > I thought first in terms of exposing methods (via SOAP) for all the > common LDAP functions (starting with search) ; then I thought about how > to represent the searchresults (java namingeumerations etc) in XML. Then > I said "d'oh! that's probably been done!" So I checked up on DSML, > which, in v2, does seem to do all that. I'm on Tomcat, so I checked on > Axix for the SOAP engine. From what I've seen, I need my Java to provide > Axis with a javabean or a simple type or array. A DSML BatchRequest or > BatchResponse is not any of those, so I'm looking for the most painless > way to serialize and deserialize between the DSML-defined structures and > the corresponding Java JNDI objects (initialdircontext; searchresult, > basicattributes, etc.) I'd prefer not to have to attempt an Axis custom > serializer class (I'm not that skilled, and the docs are still "to > come.") . I don't intend to write a W-S client at all (well, maybe as a > demo): I'm just trying to add a WS port to provide a new way for > whoever's interested to access the data in directory.gov. > > BTW, I have a post into jndi-interest list at Sun to see if the Sun > engineers or others there will identify a "no-brainer" way to combine > their stuff with axis. I probably will avoid doing any actual hard > thinking until I hear (or don't hear) from them. > > Thanks again for the info & suggestions, > > Martin > > > Anne Thomas Manes wrote: > > >Martin, > > > >Do you have a link to some documentation, or do I have to > download it to see > >the contents of the package? > > > >I just looked through the DSMLv2 spec. It defines a SOAP binding, but it > >doesn't provide a WSDL portType or binding description (too bad). But it > >does provide XML Schemas for all the messages. It's not too hard > to create > >the WSDL from that. Once you have a WSDL file, you ought to be > able to just > >generate your client proxy. > > > >DSML requires that you use document/literal mode. > > > >Anne > > > >
