You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Dan O'Neill <do...@gmail.com> on 2005/03/24 13:16:24 UTC
Simple question....
I'm tired trying to get them to work. Do Client-side service-specific
handlers work? If you put them in client-config.wsdd? I know that if I
change them to global they work?
I've got some working by using setClientHandlers() in the client code
but I don't always have the luxury of changing people's java client?
Re: Simple question....
Posted by Dan O'Neill <do...@gmail.com>.
Well not really.... I catch errors messages about services... The
users rate how well they felt the service processed the data... Work
out the uptime of services etc. The speed of the service related to
other services that do the same thing... Etc,
I don't really know the parts that others are doing but Its a very
interesting project/application if nothing else.
And your right alot of it does come down to how well you design the system.
Dan
On Thu, 24 Mar 2005 08:36:36 -0900, Elaine Nance
<el...@commerce.state.ak.us> wrote:
> Well, I think design, design, design is going to be your problem
> first rather than code, code, code.
>
> What you're describing sounds like your application is a tunnel
> through which services pass so you can meter them. Kind of
> defeats the measurements, doesn't it?
>
> Global Handler as switchboard . . .
>
> Dan O'Neill wrote:
> > Ahhh... you see... I'm building a distributed system. Its part of a
> > much larger project and Im actually only building a prototype
> > application and doing some modelling.
> >
> > The application however needs input from both the client and service.
> > This input is passed to my application service which then proceeses it
> > and uses it to build a model of both the client users and the services
> > that they use.
> > Its all to do with WebService reputation and which webservice to
> > choose for a particular job. I cant really say any more because its a
> > rather large college project that many people are working on.
> >
> > The client you see then rates the webservice and so forth..... But you
> > see if I make a soap call while the handlers are set to global it will
> > start a never ending loop which eventually crashes everything from
> > client to server!
> >
> > I hope that answers some of your questions.....
> >
> > Dan
> >
> > On Thu, 24 Mar 2005 08:00:57 -0900, Elaine Nance
> > <el...@commerce.state.ak.us> wrote:
> >
> >>Dan,
> >>
> >>Here are also simple questions, not particularly aimed at you:
> >>
> >>Why would your service be responsible for what the subscriber
> >>does to handle the responses? If the interface is fully
> >>specified by the wsdl then the client will be able to consume it.
> >>
> >>What, specifically, are you doing that you need to concern
> >>yourself with client-side handlers?
> >>
> >>I'm not being a smartie here. I see a lot of posts similar to
> >>yours and I wonder why:
> >>
> >> 1) the provider wants to be responsible for the subscriber -
> >>frankly I'd love it if our enterprise IT even *thought* about
> >>providing usable client code. I will absolutely settle for a
> >>wsdl which doesn't make me hand-code parsers for every
> >>string-wrapped xml document.
> >>
> >> 2) so many services don't seem to be designed as services -
> >>it's as if the cart is driving the horse, as in "we already have
> >>the application/interfaces/classes that we'd like to expose as a
> >>web service" . . .
> >>
> >> 3) SOAP is decided as the solution when the problem hasn't
> >>been analyzed
> >>
> >>Elaine
> >>
> >>
> >>Dan O'Neill wrote:
> >>
> >>>I'm tired trying to get them to work. Do Client-side service-specific
> >>>handlers work? If you put them in client-config.wsdd? I know that if I
> >>>change them to global they work?
> >>>
> >>>I've got some working by using setClientHandlers() in the client code
> >>>but I don't always have the luxury of changing people's java client?
> >>>
> >>
> >><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> | Computers are useless. They can only give you answers.
> >> | -- Pablo Picasso --
> >><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>
> >>
> >
> >
> >
>
> --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | Computers are useless. They can only give you answers.
> | -- Pablo Picasso --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
--
Classic Family Guy.....
"Yes, but no sprinkles. For every sprinkle i find, i shall KILL you." - Stewie
"And Joe, I've had new neighbors before, but none of them were half
the man you are. Since you're half a man already, that splits them
into some kind of fraction I can't even measure." - Peter
"Hello, 911? It's Quagmire. Yeah, it's caught in the window this time." Quagmire
"I got an idea, an idea so smart my head would explode if I even began
to know what I was talking about." - Peter
Re: Simple question....
Posted by Elaine Nance <el...@commerce.state.ak.us>.
Well, I think design, design, design is going to be your problem
first rather than code, code, code.
What you're describing sounds like your application is a tunnel
through which services pass so you can meter them. Kind of
defeats the measurements, doesn't it?
Global Handler as switchboard . . .
Dan O'Neill wrote:
> Ahhh... you see... I'm building a distributed system. Its part of a
> much larger project and Im actually only building a prototype
> application and doing some modelling.
>
> The application however needs input from both the client and service.
> This input is passed to my application service which then proceeses it
> and uses it to build a model of both the client users and the services
> that they use.
> Its all to do with WebService reputation and which webservice to
> choose for a particular job. I cant really say any more because its a
> rather large college project that many people are working on.
>
> The client you see then rates the webservice and so forth..... But you
> see if I make a soap call while the handlers are set to global it will
> start a never ending loop which eventually crashes everything from
> client to server!
>
> I hope that answers some of your questions.....
>
> Dan
>
> On Thu, 24 Mar 2005 08:00:57 -0900, Elaine Nance
> <el...@commerce.state.ak.us> wrote:
>
>>Dan,
>>
>>Here are also simple questions, not particularly aimed at you:
>>
>>Why would your service be responsible for what the subscriber
>>does to handle the responses? If the interface is fully
>>specified by the wsdl then the client will be able to consume it.
>>
>>What, specifically, are you doing that you need to concern
>>yourself with client-side handlers?
>>
>>I'm not being a smartie here. I see a lot of posts similar to
>>yours and I wonder why:
>>
>> 1) the provider wants to be responsible for the subscriber -
>>frankly I'd love it if our enterprise IT even *thought* about
>>providing usable client code. I will absolutely settle for a
>>wsdl which doesn't make me hand-code parsers for every
>>string-wrapped xml document.
>>
>> 2) so many services don't seem to be designed as services -
>>it's as if the cart is driving the horse, as in "we already have
>>the application/interfaces/classes that we'd like to expose as a
>>web service" . . .
>>
>> 3) SOAP is decided as the solution when the problem hasn't
>>been analyzed
>>
>>Elaine
>>
>>
>>Dan O'Neill wrote:
>>
>>>I'm tired trying to get them to work. Do Client-side service-specific
>>>handlers work? If you put them in client-config.wsdd? I know that if I
>>>change them to global they work?
>>>
>>>I've got some working by using setClientHandlers() in the client code
>>>but I don't always have the luxury of changing people's java client?
>>>
>>
>><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> | Computers are useless. They can only give you answers.
>> | -- Pablo Picasso --
>><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>
>
>
--
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Computers are useless. They can only give you answers.
| -- Pablo Picasso --
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: Simple question....
Posted by Dan O'Neill <do...@gmail.com>.
Ahhh... you see... I'm building a distributed system. Its part of a
much larger project and Im actually only building a prototype
application and doing some modelling.
The application however needs input from both the client and service.
This input is passed to my application service which then proceeses it
and uses it to build a model of both the client users and the services
that they use.
Its all to do with WebService reputation and which webservice to
choose for a particular job. I cant really say any more because its a
rather large college project that many people are working on.
The client you see then rates the webservice and so forth..... But you
see if I make a soap call while the handlers are set to global it will
start a never ending loop which eventually crashes everything from
client to server!
I hope that answers some of your questions.....
Dan
On Thu, 24 Mar 2005 08:00:57 -0900, Elaine Nance
<el...@commerce.state.ak.us> wrote:
> Dan,
>
> Here are also simple questions, not particularly aimed at you:
>
> Why would your service be responsible for what the subscriber
> does to handle the responses? If the interface is fully
> specified by the wsdl then the client will be able to consume it.
>
> What, specifically, are you doing that you need to concern
> yourself with client-side handlers?
>
> I'm not being a smartie here. I see a lot of posts similar to
> yours and I wonder why:
>
> 1) the provider wants to be responsible for the subscriber -
> frankly I'd love it if our enterprise IT even *thought* about
> providing usable client code. I will absolutely settle for a
> wsdl which doesn't make me hand-code parsers for every
> string-wrapped xml document.
>
> 2) so many services don't seem to be designed as services -
> it's as if the cart is driving the horse, as in "we already have
> the application/interfaces/classes that we'd like to expose as a
> web service" . . .
>
> 3) SOAP is decided as the solution when the problem hasn't
> been analyzed
>
> Elaine
>
>
> Dan O'Neill wrote:
> > I'm tired trying to get them to work. Do Client-side service-specific
> > handlers work? If you put them in client-config.wsdd? I know that if I
> > change them to global they work?
> >
> > I've got some working by using setClientHandlers() in the client code
> > but I don't always have the luxury of changing people's java client?
> >
>
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | Computers are useless. They can only give you answers.
> | -- Pablo Picasso --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
--
Classic Family Guy.....
"Yes, but no sprinkles. For every sprinkle i find, i shall KILL you." - Stewie
"And Joe, I've had new neighbors before, but none of them were half
the man you are. Since you're half a man already, that splits them
into some kind of fraction I can't even measure." - Peter
"Hello, 911? It's Quagmire. Yeah, it's caught in the window this time." Quagmire
"I got an idea, an idea so smart my head would explode if I even began
to know what I was talking about." - Peter
Re: Simple question....
Posted by Elaine Nance <el...@commerce.state.ak.us>.
Scott,
I'm really a newbie to SOAP and Java, but I'd probably use a
resource file and make it as simple as possible.
For example:
resource location true/false
But I find that the simplest method which completely solves a
problem is usually the best. Unnecessary complexity in software
should be against the law, except it's even worse to write
unmaintainable code.
Elaine
Scott Wilson wrote:
> Hi Elaine,
>
> I've got a similar problem to Dan, and haven't seen any great answers
> posted to date...
>
> I'm doing some R&D on 'secure' federated resource discovery using SAML
> to pass attributes about the principal to a bunch of repositories along
> with their query.
>
> So far, so good. I have a nice federated search client that can talk SRW
> & SAML, and signs its messages. (If you send SAML assertions, you really
> must sign them).
>
> The only thing is, my search client also needs to be able to
> cross-search repositories that are open access. In this case, the client
> has to be configured such that if a target is known to support digital
> signatures, it must sign the message (and expect a signed response),
> whereas if the target is open-access, the message exchange goes vanilla.
> If I sign my messages to 'vanilla' targets they reject my request (not
> understanding my "MustUnderstand" - even if they do somehow fail to
> notice this problem, I reject their responses as they don't have a
> required security header).
>
> I've been using WSS4J to handle signing, configured via the
> client-config.wsdd file.
>
> I'd rather manage this in the configuration properties than coding it
> into the client. But if the only answer is to make my classes smart
> enough to programmatically sort out WSS4J, then so be it...
>
> - Scott
>
> On 25 Mar 2005, at 04:00, Elaine Nance wrote:
>
>> Dan,
>>
>> Here are also simple questions, not particularly aimed at you:
>>
>> Why would your service be responsible for what the subscriber does to
>> handle the responses? If the interface is fully specified by the wsdl
>> then the client will be able to consume it.
>>
>> What, specifically, are you doing that you need to concern yourself
>> with client-side handlers?
>>
>> I'm not being a smartie here. I see a lot of posts similar to yours
>> and I wonder why:
>>
>> 1) the provider wants to be responsible for the subscriber - frankly
>> I'd love it if our enterprise IT even *thought* about providing usable
>> client code. I will absolutely settle for a wsdl which doesn't make
>> me hand-code parsers for every string-wrapped xml document.
>>
>> 2) so many services don't seem to be designed as services - it's as
>> if the cart is driving the horse, as in "we already have the
>> application/interfaces/classes that we'd like to expose as a web
>> service" . . .
>>
>> 3) SOAP is decided as the solution when the problem hasn't been
>> analyzed
>>
>>
>> Elaine
>>
>>
>> Dan O'Neill wrote:
>>
>>> I'm tired trying to get them to work. Do Client-side service-specific
>>> handlers work? If you put them in client-config.wsdd? I know that if I
>>> change them to global they work?
>>> I've got some working by using setClientHandlers() in the client code
>>> but I don't always have the luxury of changing people's java client?
>>
>>
>>
>> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> | Computers are useless. They can only give you answers.
>> | -- Pablo Picasso --
>> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
--
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Computers are useless. They can only give you answers.
| -- Pablo Picasso --
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: Simple question....
Posted by Scott Wilson <s....@bangor.ac.uk>.
Hi Elaine,
I've got a similar problem to Dan, and haven't seen any great answers
posted to date...
I'm doing some R&D on 'secure' federated resource discovery using SAML
to pass attributes about the principal to a bunch of repositories along
with their query.
So far, so good. I have a nice federated search client that can talk
SRW & SAML, and signs its messages. (If you send SAML assertions, you
really must sign them).
The only thing is, my search client also needs to be able to
cross-search repositories that are open access. In this case, the
client has to be configured such that if a target is known to support
digital signatures, it must sign the message (and expect a signed
response), whereas if the target is open-access, the message exchange
goes vanilla. If I sign my messages to 'vanilla' targets they reject my
request (not understanding my "MustUnderstand" - even if they do
somehow fail to notice this problem, I reject their responses as they
don't have a required security header).
I've been using WSS4J to handle signing, configured via the
client-config.wsdd file.
I'd rather manage this in the configuration properties than coding it
into the client. But if the only answer is to make my classes smart
enough to programmatically sort out WSS4J, then so be it...
- Scott
On 25 Mar 2005, at 04:00, Elaine Nance wrote:
> Dan,
>
> Here are also simple questions, not particularly aimed at you:
>
> Why would your service be responsible for what the subscriber does to
> handle the responses? If the interface is fully specified by the wsdl
> then the client will be able to consume it.
>
> What, specifically, are you doing that you need to concern yourself
> with client-side handlers?
>
> I'm not being a smartie here. I see a lot of posts similar to yours
> and I wonder why:
>
> 1) the provider wants to be responsible for the subscriber - frankly
> I'd love it if our enterprise IT even *thought* about providing usable
> client code. I will absolutely settle for a wsdl which doesn't make
> me hand-code parsers for every string-wrapped xml document.
>
> 2) so many services don't seem to be designed as services - it's as
> if the cart is driving the horse, as in "we already have the
> application/interfaces/classes that we'd like to expose as a web
> service" . . .
>
> 3) SOAP is decided as the solution when the problem hasn't been
> analyzed
>
>
> Elaine
>
>
> Dan O'Neill wrote:
>> I'm tired trying to get them to work. Do Client-side service-specific
>> handlers work? If you put them in client-config.wsdd? I know that if I
>> change them to global they work?
>> I've got some working by using setClientHandlers() in the client code
>> but I don't always have the luxury of changing people's java client?
>
>
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | Computers are useless. They can only give you answers.
> | -- Pablo Picasso --
> <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
Re: Simple question....
Posted by Elaine Nance <el...@commerce.state.ak.us>.
Dan,
Here are also simple questions, not particularly aimed at you:
Why would your service be responsible for what the subscriber
does to handle the responses? If the interface is fully
specified by the wsdl then the client will be able to consume it.
What, specifically, are you doing that you need to concern
yourself with client-side handlers?
I'm not being a smartie here. I see a lot of posts similar to
yours and I wonder why:
1) the provider wants to be responsible for the subscriber -
frankly I'd love it if our enterprise IT even *thought* about
providing usable client code. I will absolutely settle for a
wsdl which doesn't make me hand-code parsers for every
string-wrapped xml document.
2) so many services don't seem to be designed as services -
it's as if the cart is driving the horse, as in "we already have
the application/interfaces/classes that we'd like to expose as a
web service" . . .
3) SOAP is decided as the solution when the problem hasn't
been analyzed
Elaine
Dan O'Neill wrote:
> I'm tired trying to get them to work. Do Client-side service-specific
> handlers work? If you put them in client-config.wsdd? I know that if I
> change them to global they work?
>
> I've got some working by using setClientHandlers() in the client code
> but I don't always have the luxury of changing people's java client?
>
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Computers are useless. They can only give you answers.
| -- Pablo Picasso --
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~