This sounds like a good idea that you've spent some
quality time thinking about. I know (almost) nothing
about SOAP, but look forward to watching the
discussion and code evolve.
I know you mention it, but I would like to reiterate
that JSR 160 (even though I haven't seen it yet)
should definitely be kept in mind while designing
--- Alireza Taherkordi <taherkordy@...>
> Dear Friends,
> I'm a new committer to MX4J,
> I really hope to deserve this honour.
> I've spoke with Simon,
> I want to implement a SOAP Adaptor for MX4J,
> but certainly with your help,
> in this email I just want to start the discussion,
> we should discuss more about the solution,
> the tasks and anything,
> please help me with contributing in this
> new task.
> Just begin the discussion:
> We want to implement a SOAP adaptor for MX4J
> to enable soap connectivity to our MX4J
> based management framework,
> we know that web services are evolving so fast
> and we should consider the changes.
> The only available Soap Adaptors as I know are
> AdventNet JMX Studio and JBoss.NET project.
> Both of them are using Axis as their soap engine and
> Jetty/Tomact as their servlet containers,
> but neither of them can be used out of the box,
> this is the thing that we can provide by MX4J.
> so please let me know your ideas about the
> - We need a soap engine, I'm considering Apache Axis
> because of its so much flexible architecture,
> any idea?
> - We need a Http transport listener, Axis has a
> SimpleAxisServer but it is not a production ready
> as Axis team says, so What I'm considering is Jetty,
> It's so easy to integrate and use,
> Any idea?
> - About Soap Adaptor implementation:
> we need to expose our MBeanServer functionally to
> the public via SOAP, but with SOAP we are restricted
> to some extent,
> we can't provide remote notification mechanaism.
> - If we're considering Axis then We need to
> an MBean Provider that is our Axis pivot handler to
> the invocations to the MBeanServer
> - We need to implement multiple JAX-RPC
> - javax.management.ObjectName
> - javax.management.Attribute
> - javax.management.MBeanInfo
> - javax.management.MBeanAttributeInfo
> - javax.management.MBeanConstructorInfo
> - javax.management.MBeanFeatureInfo
> - javax.management.MBeanNotificationInfo
> - javax.management.MBeanOperationInfo
> - javax.management.MBeanParameterInfo
> - ....
> - We should consider JSR 160
> - I'm not sure but since we need to integrate
> with our adaptor, so it may be better to provide
> soap adaptor
> as a separate download, This is just a proposal.
> Best Regards,
> Alireza Taherkordi
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day