axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Neward <>
Subject RE: AXIS and JMX Architecture.
Date Thu, 05 Sep 2002 19:34:10 GMT
As the counterargument, though, what are you giving up in exchange for this
careful ignorance? If there are performance, functional or scalability
improvements that tying yourself to a given provider offers, you have to
carefully consider how portable you really need to be. Frequently, once
we've chosen a particular "vendor" (in this case Axis), we stick with that
vendor come hell or high water, particularly in the space of open source,
where typical reasons for abandoning a vendor (licensing disagreements,
cost, inability to influence product direction, etc) aren't as relevant.

I'm not necessarily suggesting everybody and everything needs to be tied to
their particular vendor--I'm suggesting everybody should take a good, hard
look at why they need to be portable, if at all.

I've got this same rant (on EJB, not web services) going right now up on my
weblog at OReilly, if anybody cares to comment there, too. :-)

Ted Neward
Architect, UCDavis Account & Financial Services

-----Original Message-----
From: Adam Kurland []
Sent: Thursday, September 05, 2002 12:14
To: ''
Subject: RE: AXIS and JMX Architecture.

I recently found myself in the same position- wanting to know a lot about
the specific parameters of the servlet request in a web service call. 
You must ask yourself a question- why would you need such details in a
normal application?  AXIS is supposed to shield the developer from knowing
the details of the servlet request- in fact why should you care if it is a
servlet handling the request at all? Suppose the implementation of AXIS (or
any other web service hosting thing) changes so that different kinds of
requests are handled by different servlets in the future- you want to
service to continue working gracefully.

One thing that I have learned after using AXIS for while is that its best to
"know" as little as possible about the web services container implmentation.
In fact, if you stick with service implmentation classes (the ones that we
write) that only import the jax-rpc libraries and dont import the axis ones,
you're better off.

Kind of like using PreparedStatement instead of OraclePreparedStatement in a
JDBC program- sure you can do more but look- you have wedded yourself to an
implementation detail when its usually not necessary.  And thats one of the
larger points of using web services- that you dont wed yourself to closely
to these implementation details.

Sorry for the rant.

-----Original Message-----
From: Jung, Eric (Contractor) []
Sent: Thursday, September 05, 2002 11:35 AM
To: ''
Subject: RE: AXIS and JMX Architecture.

How about this?

MessageContext msgc = MessageContext.getCurrentContext();
String methodName = msgc.getOperation().getName();

I don't know what you mean about parameter objects. Do you want the objects
themselves, or their names as specified in the WSDL?


-----Original Message-----
From: Lachezar Dobrev []
Sent: Thursday, September 05, 2002 12:04 PM
Subject: Re: AXIS and JMX Architecture.


  Thanks. It helped.

  Now what about the requested method and parameter objects? Any help there
too ? :)))


> >how to get the name of the service?
> This one was answered yesterday by Ramon Turnes:
> -Eric H. Jung
> -----Original Message-----
> From: Lachezar Dobrev []
> Sent: Thursday, September 05, 2002 10:51 AM
> To:
> Subject: Re: AXIS and JMX Architecture.
>   Hiya...
>   Well... JBoss.Net is a nice piece of software, but it is designed for
> in-jboss-running, and that says they have a Servlet container ( in fact it
> does not run withowt a servlet container).
>   My idea was to COMPLETELY withdraw that servlet stuff...
>   I agree, that they have made quite some classes, that could be taken as
> base for my project, but running throughout someone else's code is hell.
>   Like I wrote: Can anyone help to explain how do I create an Engine
> Configuration, that would take the deployed objects from within the
> MBeanServer.
>   What should I do to implement a provider similar to the JavaRPC one (I
> know I have to extend the BasicProvider, but what else?).
>   Now... What i need are some pointers as to:
>    BasicProvider.invoke(...): how to extract the Call object from the
> MessageContext, how to get the name of the service?
>    How do I implement the SOAPService class, i.e. what Handler should I
> to create these services for the EngineConfiguration.getService()...
>   Too many questions, to little answers.
>   Lachezar
> > have a look at
> > there is a project going on for that stuff.
> > They call it
> > I think it is exacltly what you are looking for.
> > The use axis (beta2 I think)
> >
> > hope that helps,
> > Kolja
> >
> > Am Donnerstag, 5. September 2002 10:24 schrieb Lachezar Dobrev:
> > >   Hello.
> > >   Please excuse me, if you have received my first message, but it
> > > that I have not been registered with the list then.
> > >
> > >   I am trying to create an JMX Adaptor for the SOAP protocol.
> > >   The idea is to make it ABSOLUTELY independable. I.E. no
> > > requirement, simple port listener and so on. I found Apache SOAP to be
> very
> > > hard to use, because of its very heavy requirement for a web-service
> > > container.
> > >   I tried AXIS, and found, that the SimpleAxisServer
> > > (org.apache.axis.transport.http.SimpleAxisServer) can be used with
> > > small adjustments to intergrate with a JMX architecture. So I did.
> > >   Next is the thing, that was very easy for the Apache SOAP, but I
> no
> > > way to do it with AXIS.
> > >
> > >   With Apache SOAP i creted a ConfigManager class, that would list the
> > > MBeans as services, so each time the "list" was done it got a list of
> the
> > > current MBeans instantiated within the JMX server. I also created a
> > > provider, that would implement calling the MBeans. It was quite
> > > stright-forward. If it wasn't for the ServletContainer requirement, I
> would
> > > have used Apache SOAP.
> > >
> > >   My question is if anyone, ANYONE can give some advices on how to
> > > implement similar job with the AXIS SOAP implementation.
> > >
> > >   I could really use some help. The "Integration Guide" has no real
> > > information on how to do that, or is VERY vague, so that I would not
> > > understand that.
> > >
> > >   Looking forward to hearing from the list: Lachezar
> >
> > --
> >
> > ---------------------------------------------------------
> > Kolja Fricke, Dipl.-Ing.
> > technologies gmbh
> > Theodorstrasse 42-90            22761 Hamburg, Germany
> > Fon (+49) 040 / 890 584 - 0     Fax (+49) 040 / 890 584 - 20
> > ---------------------------------------------------------
> >

View raw message