DOH!

After actually having some time away from my screen it turns out I was
being a dufus!

Going through my logs it appears that for some reason the webservice
hadn't refreshed in the mid-tier cache and was still running the '='
qual instead of the 'LIKE' qual... very odd.

Restarted tomcat on the mid-tier and all now appears to be happy

Thanks for the help though...

*hangs head in shame*

On 08/03/07, Carey Matthew Black <[EMAIL PROTECTED]> wrote:
Stephen,

What do you think is the functional difference between the following:
(They look like they would produce the same thing to me.)

> So in theory this would expand to:
>
> ('Account Name' LIKE "ACCOUNT NAME"+"%")
>
> Whch isn't really what I want, what I really want is:
>
> ('Account Name' LIKE "ACCOUNT NAME%")


However, one option would be to set up the Web Service as this...
('Account Name' LIKE XPATH(/ROOT/Account_name))

Then tell the Web Service client to pass in a value for Account_name
that ends in a "%".
Also keep in mind that they could just as easily pass in this value
too "%ACCOUNT NAME" and not have the trailing "%" in that case.


You might even opt for several operations that would allow the
WebServices client to choose if they want a LIKE with a forced
trailing "%", just a straight LIKE qualification, or maybe even the
old equals search as a third option.

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.



On 3/8/07, Stephen Earl <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I'm sure I've missed something really simple but I'm trying to get the
> following scenario to work but for the life of me I can't, so here
> goes:
>
> I have a webservice which is querying an underlying form based on data
> being provided by the WS client, the webservice is configured with the
> following qualification:
>
> ('Account Name' = XPATH(/ROOT/Account_name))
>
> This quite rightly only allows an '=' match, so we thought OK, let's
> make it a like statement with the following qualification:
>
> ('Account Name' LIKE XPATH(/ROOT/Account_name)+"%")
>
> So in theory this would expand to:
>
> ('Account Name' LIKE "ACCOUNT NAME"+"%")
>
> Whch isn't really what I want, what I really want is:
>
> ('Account Name' LIKE "ACCOUNT NAME%")
>
> How in a WebService qualification could I achieve this?
>
> I know my easiest option is for me to specify to the consumer that
> they should send their request with the '%' suffix in the request and
> that would take care of it for me, but they aren't very receptive to
> that idea...
>
> Any thoughts?
>
> Thanks muchly as always
>
> Stephen.
>
> 
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to