Hi, On 3/1/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
SamindaThe only problem is that the individual rules don't signal whether they matched. The true/false is not an indication.
That's why i was thinking of having a signalling variable inside
of and for as
follows,
public class RegexProc
On 3/1/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
SamindaI don't understand the
scenario. I would say that was a misconfig and I would expect an
exception to be thrown when registering the second RH with the same URI
root. Paul
So there is a one-to-one mapping between RH and uri-root. So the imp
On Wed, 2006-03-01 at 16:06 +, Paul Fremantle wrote:
> Saminda
>
> The only problem is that the individual rules don't signal whether
> they matched. The true/false is not an indication.
>
> So I was imagining this:
>
>
>http://foo/.*";>
>
>
>http://bar/.*";>
>
I still have problems with the SynapseObject proposal.1) I think it is much simpler for administrators to use what I call "real" XML. In other words, if there is a ClientIdentification mediator, then we either use simpler type properties to configure it, or we create a new schema that defines the c
Hi folks!
This is an automatic reminder that the weekly Synapse developer chat
will be occurring tomorrow, March 02, at:
5AM PST, 8AM EST, 1PM GMT, 7PM SLT
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-synapse, and is scheduled to last
one ho
SamindaThe only problem is that the individual rules don't signal whether they matched. The true/false is not an indication.So I was imagining this: http://foo/.*"> http://bar/.*">
PaulOn 3/1/06, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Title: Propo
SamindaI don't understand the scenario. I would say that was a misconfig and I would expect an exception to be thrown when registering the second RH with the same URI root. Paul
On 3/1/06, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi Paul,
I just need to clarify the following small matter.
i
Hi Paul,
I just need to clarify the following small matter.
i hope following scenario is valid. :-)
Assume, we have following synapse.xml for an example
...
http://fremantle.org/resources/"> paul pass proxy:80
http://fremantle.org/resources/"> [1..n]
...
so a mediator can reg
Thanks
Paul... I think this should suffice... +1
-Original Message-From: Paul Fremantle
[mailto:[EMAIL PROTECTED]Sent: Wednesday, March 01, 2006 4:15
PMTo: synapse-dev@ws.apache.orgSubject: Re: get(String
url) issues for getting external resourcesHow about this
implementa
+1On 3/1/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
How about this implementation of what you are describing.1) Lets indirect this out of SynEnv:SynapseEnvironment { ResourceHelper getResourceHelper();}public interface ResourceHelper {
OMElement get(String uri); // get a resource OMEl
How about this implementation of what you are describing.1) Lets indirect this out of SynEnv:SynapseEnvironment { ResourceHelper getResourceHelper();}public interface ResourceHelper {
OMElement get(String uri); // get a resource OMElement get(String uri, ResourceUpdateAware mediator); //
+1
-Original Message-From: Paul Fremantle
[mailto:[EMAIL PROTECTED]Sent: Wednesday, March 01, 2006 3:35
PMTo: synapse-dev@ws.apache.orgSubject: Re: get(String
url) issues for getting external resourcesHow about this
implementation of what you are describing.1) Lets indirec
How about this implementation of what you are describing.1) Lets indirect this out of SynEnv:public interface ResourceHelper { OMElement get(String uri);
On 3/1/06, Soumadeep <[EMAIL PROTECTED]> wrote:
Paul
is right, instead of passing an object we could have property files which will
hav
13 matches
Mail list logo
