Sounds like a bug to me. The service parameters are actually an array,
deliniated with slashes. I suspect that you are passing a single string,
"foo/bar" and getting the array of strings { "foo", "bar" }.
----- Original Message -----
From: "Chris Merrill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 04, 2002 1:16 PM
Subject: [Tapestry-developer] '/' not allowed in static binding?
> I have a static binding (for the context in a Direct
> component) that contains the path of a URL for an
> external link. When the listener gets the context,
> however, everything after (and including) the first
> '/' is not included. I was under the impression that
> the context is simply a string - with no special
> meanings. Why is the '/' treated specially?
>
> Chris
>
> *********************************
> Chris Merrill
> [EMAIL PROTECTED]
> *********************************
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
