Deepak Sharma wrote:
Hi Folks,
I have very basic question to you guys.
Followinvg are the questions for which need clarifications:
a) From end to end prospective implementation of the MUSE on web based
application, following is my understanding:
i) Device which we are managing like Printer should install MUSE (on App
server/Web server) for catering to the requests coming from Web service
installed on some server.
Could be installed on printer or on some other webserver which can speak
to the printer to get its information.
ii) Device MUSE installation should be parsing the SOAP request (sent by
the Web service) for various operation like changing/retrieving the state of
the device.
Muse is recieving the request from Axis..Axis parses the incoming
messages and hands-off to our Provider....
iii) Also as Device would be acting as Publisher, it would be intimating
all the subscribers ( i.e. different Web services i.e. subscribers) for any
events triggered.
If the service throws events, then it would need to send events as
things occur...
b) Also do we have any utility existing in the MUSE which generates the
client code which help us in integrating MUSE application with any web
application.
No, there is no client-generation code in the distribution. There is a
client subproject however...
My knowledge to MUSE is pretty limited which obviously you can make out from
the questions which I have asked. And unless I get clarification on the
above questions, I would be stuck to nowhere. So, please let me know your
thoughts.
Regards,
Deepak
See inlined....
