: Tuesday, October 01, 2002 11:52 AM
To: [EMAIL PROTECTED]
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
: RE: Dynamic publishing
Just my opinion of course, but a couple of things immediately come to
mind...lets say you have thousands and thousands of bank accounts you're
looking at having Axis manage a ton of services - which as of now I doubt
Le Viet" [EMAIL PROTECTED] on 10/01/2002 07:42:22 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: Dynamic publishing
Hi Dug,
I totally agree with you that Axis should just worry about SOAP processing,
back-end system should deal with other issues.
My idea
ed by
Axis. Then, in your service you can just get the full URL (or get the
Servlet Request
object) and get the parameters (account) you want/need.
-Dug
"Tuan Le Viet" [EMAIL PROTECTED] on 10/01/2002 08:04:57 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE
AccountSoapBindingImpl, how do I get ServletRequest object?
Cheers,
Tuan
-Original Message-
From: Doug Davis [mailto:[EMAIL PROTECTED]]
Sent: 2002/10/01 (火) 19:12
To: [EMAIL PROTECTED]
Cc:
Subject: RE: Dynamic publishing
]
To: [EMAIL PROTECTED]
Sent: Monday, September 30, 2002 6:04 PM
Subject: Re: Dynamic publishing
I agree that dynamic endpoints are handy; .net remoting does it BTW,
though
that doesnt help.
why not look at what the Axis engine is up to and maybe call it directly?
Adding an API to do everything
?
Cheers,
Tuan Le
-Original Message-
From: Doug Davis [mailto:[EMAIL PROTECTED]]
Sent: 2002/10/01 (火) 18:06
To: [EMAIL PROTECTED]
Cc:
Subject: RE: Dynamic publishing
Just my opinion of course, but a couple of things
- Original Message -
From: "Doug Davis" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 30, 2002 6:16 PM
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 s
- Original Message -
From: Tuan Le Viet [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 01, 2002 4:42 AM
Subject: RE: Dynamic publishing
SOAP stand for Simple OBJECT Access Protocol?
Not in SOAP 1.2; it stands for 'SOAP', on the grounds it is neither simple
or object
. Then, in your service you can just get the full URL (or get the
Servlet Request
object) and get the parameters (account) you want/need.
-Dug
Tuan Le Viet [EMAIL PROTECTED] on 10/01/2002 08:04:57 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: Dynamic publishing
Ask the message context for it:
MessageContext.getCurrentContext().getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST);
-Dug
"Tuan Le Viet" [EMAIL PROTECTED] on 10/01/2002 08:47:24 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: Dynamic publis
- Original Message -
From: "Doug Davis" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 01, 2002 5:12 AM
Subject: RE: Dynamic publishing
By default, if you use the URLMapper, yes axis will want the base URL to
be:
http://host:port/axis/service/accoun
guys.
Cheers,
Tuan
-Original Message-
From: Ricky Ho [mailto:[EMAIL PROTECTED]]
Sent: 2002/10/01 (火) 23:53
To: [EMAIL PROTECTED]
Cc:
Subject: RE: Dynamic publishing
Your suggested approach
- Original Message -
From: Tuan Le Viet [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 01, 2002 18:32
Subject: RE: Dynamic publishing
Hi Ricky,
Apparently, my approach is strongly discouraged by all the gurus.
Probably I'm an OO nut :-). I should really put more
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
:
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
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 30, 2002 4:59 PM
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
=12345 - to the
client the URL is just a string so adding on ?account=12345 should be no
big deal).
-Dug
"Tuan Le Viet" [EMAIL PROTECTED] on 09/30/2002 08:17:30 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:RE: Dynamic publishing
As I understand, j
-Original Message-
From: Doug Davis [mailto:[EMAIL PROTECTED]]
Sent: 2002/10/01 (火) 8:16
To: [EMAIL PROTECTED]
Cc:
Subject: RE: Dynamic publishing
Sorry - missed that, but why would you really want to deploy
-
From: Doug Davis [mailto:[EMAIL PROTECTED]]
Sent: 2002/10/01 (火) 8:16
To: [EMAIL PROTECTED]
Cc:
Subject: RE: Dynamic publishing
Sorry - missed that, but why would you really want to deploy one
service
per account? That's
20 matches
Mail list logo
