Hi Daniel;

Thanks very much for the  answer! please find the comments in line.

I'm not totally clear on what you want to do. I looked at your project
page and user guide, and it seems you have created a system for exposing
command line apps via SOAP using a custom service descriptor; your toolkit
that creates a WSDL and mapping layer that can be deployed as a web
service. Is that right?

Yes, it creates services remotely. There is a factory service that
create services in remote hosts. We use Grid to access to remote
machines/data transfers and exposed applications are Weather
simulation applications. (It is part project called LEAD
http://www.itsc.uah.edu/lead/index.html)

We end up creating hundreds of services and we are trying to use WSDM
to manage and monitor those services and back end Grid infrastructure.
Those services are created and used by a work flow system, and each
service may run for hours.  Right now we use in house soap stack but
we might move to Axis2 soon. (I myself a Axis2 developer).

However due to dynamic nature of system we need to avoid code
generation and need close access to the  SOAP stack. Also we prefer to
have our deployment model and integrate Axis2/Muse into that model.
Even we used Axis2, we would with jetty and closely integrated to our
deployment.

I understand if we use internal API they might change in the future.
But I hope they will reasonably stay fixed. Hopefully I can understand
Muse internals to keep the things going.

Let me ask a one more question, Is there a way to use Muse with Axis2
without code generation? Is it possible to make Muse a Axis2 module?
My Gut feeling is it is possible, but may be there is something I
missed.

Thanks very much again for you comments!
Thanks
Srinath


--
============================
Srinath Perera:
  Indiana University, Bloomington
  http://www.cs.indiana.edu/~hperera/
  http://www.bloglines.com/blog/hemapani

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to