axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shankar S" <sshan...@prodapt.com>
Subject RE: Dynamic publishing
Date Tue, 01 Oct 2002 06:34:13 GMT
Hi,

You are right with regard to your example.
But, lets think in this perspective.
WS could be used in cases like provding an interface to a very generic and
basic information on the web like weather forecast, Forex informatiom,
Stocks and exchange of any business information between hetrogenous/legecy
systems.

Lets not view it as just exposing a business object. We would be having a
lot of security ...may be an authentication or so..may be not everyone wil
have acces to itand only registered/paid guys will have acess to the WS.

It is not advisable to expose all out objects WS.
BTW, As a good design ground rules, we should not expose Entity
Beans...instead we should expose Session Bean and let the session bean talk
to entity bean.

I request you guys to comment on my reply please.

Thanks,
Shankar Shanmugam

-----Original Message-----
From: Ricky Ho [mailto:riho@cisco.com]
Sent: Tuesday, October 01, 2002 11:52 AM
To: axis-user@xml.apache.org
Subject: RE: Dynamic publishing


SOAP is more an RPC mechanism than a "remote Object" mechanism.  I doubt it
would be scalable.  From the lesson we learnt in EJB, if we shouldn't
expose EntityBean, then expose a web service per object instance is even
much worse.

Rgds, Ricky

At 10:48 AM 10/1/2002 +0700, Tuan Le Viet wrote:
>Dug,
>
>My idea was to have a more OO approach. I'll have a manager which manages
>lifetime of Account service. Each service will be published when necessary
>and unpublished when it's no longer needed.
>This would not be a nightmore for scalability right?
>
>Cheers,
>
>Tuan
>
>         -----Original Message-----
>         From: Doug Davis [mailto:dug@us.ibm.com]
>         Sent: 2002/10/01 (火) 8:16
>         To: axis-user@xml.apache.org
>         Cc:
>         Subject: RE: Dynamic publishing
>
>
>
>
>
>
>
>
>         Sorry - missed that, but why would you really want to deploy one
> service
>         per account?  That's going to be a scalability nightmare.  Why
> not just
>         have the account number in a soap header, as a param on an rpc
> call or even
>         in the URL (ie.
>         http://localhost:8080/axis/services/BankServices?account=12345  -
> to the
>         client the URL is just a string so adding on ?account=12345
> should be no
>         big deal).
>         -Dug
>
>
>         "Tuan Le Viet" <tuanle@Cybersoft-VN.com> on 09/30/2002 08:17:30 PM
>
>         Please respond to axis-user@xml.apache.org
>
>         To:    <axis-user@xml.apache.org>
>         cc:
>         Subject:    RE: Dynamic publishing
>
>
>
>         As I understand, jws is just a java source file. Axis will
> publish this
>         java class as web service automatically.
>
>         However, this wouldn't solve my problem as my intention is to
> create a web
>         service for each instance of the same class.
>
>         Cheers,
>
>         Tuan
>
>               -----Original Message-----
>               From: Doug Davis [mailto:dug@us.ibm.com]
>               Sent: 2002/10/01 (火) 7:06
>               To: axis-user@xml.apache.org
>               Cc:
>               Subject: RE: Dynamic publishing
>
>
>
>
>
>
>
>
>               What about deploying (dropping) a jws file - Aixs processes
> that
>               dynamically.
>               -Dug
>
>
>               "Tuan Le Viet" <tuanle@Cybersoft-VN.com> on 09/30/2002
> 07:59:17 PM
>
>               Please respond to axis-user@xml.apache.org
>
>               To:    <axis-user@xml.apache.org>
>               cc:
>               Subject:    RE: Dynamic publishing
>
>
>
>               Grant,
>
>               It's obviously your solution is a feasible work-around.
> However, as
>         you
>               stated, it's really a big mess.
>
>               Now I consider switching to GLUE which supports dynamic
> publishing
>         from the
>               beginning. If you're interested, take a look at
>               http://www.themindelectric.com
>
>               However, I really do hope that there is a clean solution
> using Axis.
>               Probably in near future.
>
>               Cheers,
>
>               Tuan
>
>                     -----Original Message-----
>                     From: Grant Echols (JanusLogix)
> [mailto:gechols@januslogix.com]
>                     Sent: 2002/09/30 (月) 22:09
>                     To: axis-user@xml.apache.org
>                     Cc:
>                     Subject: Re: Dynamic publishing
>
>
>
>                     Tuan,
>
>                     I have a similar need but for a totally different
> reason. We
>         have a
>               services
>                     framework and want to dynamically publish public
> 'service entry
>               points' at
>                     runtime through Axis SOAP. We only have a Java class
> file and
>         an
>               associated
>                     interface as parameters so we have to make up the
> rest of the
>               difference.
>                     Right now we're spawning Java2WSDL and WSDL2Java back
> to back
>         so I
>               can get a
>                     .WSDD file and then call the AdminClient to deploy the
>         deploy.wsdd
>               file. Its
>                     a mess and I wish there was a better way to do this.
> At this
>         point we
>               were
>                     too unsure of the deploy.wsdd file format to generate
it
>         ourselves.
>               Perhaps
>                     even having this documented, or having a class that
> we could
>               instantiate and
>                     call instead of actually spawning the wsdl...
> utilities would
>         be
>               better. But
>                     for now, its working...:-(
>
>                     I'm hoping someone has a better way and will respond,
> but if
>         you're
>               still
>                     stuck you could possibly consider this route as an
> interim
>         solution.
>
>                     Grant
>
>                     ----- Original Message -----
>                     From: "Tuan Le Viet" <tuanle@Cybersoft-VN.com>
>                     To: <axis-user@xml.apache.org>
>                     Sent: Thursday, September 26, 2002 11:13 PM
>                     Subject: Dynamic publishing
>
>
>                     > Hi there,
>                     >
>                     > Does Axis support "dynamic publishing"?
>                     >
>                     > My intention:
>                     >
>                     > +I have a class called BankAccount with 3 methods:
>                     >
>                     >            +void deposit(int amount)
>                     >
>                     >            +void withdraw(int amount)
>                     >
>                     >            +int checkBalance()
>                     >
>                     > +I have a class Bank, which have 1 method: String
>         getAccount(String
>                     accountNo).
>                     >
>                     > +I statically publish it as Web service, users will
> call
>         getAccount
>               method
>                     to get the URL to BankAccount web service, for
> example: if user
>               called
>                     getAccount("12345"), URL returned is:
>                     http://somehost/axis/services/account12345
>                     >
>                     > +users then interact with this BankAccount
> webservice to
>         deposit,
>                     withdraw, checkBalance.
>                     >
>                     > +In order to achieve this, it's required to
dynamically
>         publish
>               each
>                     BankAccount instance as a web service.
>                     >
>                     > Is this possible with Axis?
>                     >
>                     > I would really appreciate any pointers.
>                     >
>                     > Cheers,
>                     >
>                     > Tuan
>                     >
>                     >
>                     >
>                     >
>                     >
>                     >
>
>
>





Mime
View raw message