Nabble - RIFE - users

Re: Continuable callstack outside a ContinuableObject?

2008-07-08T04:28:38Z

Hi Geert,

At this time I'm not able to use the instrumentation agent due to some artifacts in Jadex which are not Java 1.5 compatible yet. But I will try to use the instrumentation agent for the testcases.

The UnsupportedOperationException is thrown from the pause() method and I agree that this is because the class isn't loaded from the continuation classloader at this time.

My problem is, that I don't understand why - and why only after the loopback / callback. Simply call pause and later resume the continuation without a type of cycle in the method-callstack works fine.

To make this clearer without going through my sample code here comes a (short) execution flow:

"-" are steps in a class,
"->" or "<-" indicates a switch into another class or a switch back to the caller
"[...]" marks an explanation

    - create a runner
    -> start the continuable object via the runner
        <- the continuable object pause and execution resumes in the TestCase [pause works here]
    - create a NON-continuable object (POJO)
    - get the continuable object through the ContinuationContext with the provided continuation-ID
    - call a setter method on the continuable object and set the NON-continuable in the continuable
    -> resume the continuation via the runner
       - the continuable object checks if the NON-continuable isn't null
       - the continuable object calls a method on the NON-continuable [parameter "this" or empty]
          - the NON-continuable object test the parameter
             [when "this" was provided by the continuable object "this" is used,
              else the continuable is accessed through the ContinuationContext ]
          [CYCLE / LOOP-BACK]
        -> the NON-continuable object calls a method on the continuable object
             [different from execute, say test() for now]
                - continuable objects test() method try to pause()

The last pause() call throws the UnsupportedOperationException, prior the cycle/loopback the pause() call works.
I tested this for a long time and I found no way to get this cycle/loopback works at all.

So my essential question is:
Is it possible to implement such a callback / loopback / cycle with Rife-Continuations or is this a use case that isn't supported/desired (yet)?

Hopeful,

Claas

Geert Bevin wrote:

Hi Claas,

I haven't tried out your sample code yet, but it seems to me that the  
bytecode manipulation isn't happening for that pause() method, thus  
causing the UnsupportedOperationException to be thrown. This is most  
probably due to the ContinuableObject class not being loaded by the  
custom classloader. You'll have to verify that.

If at all possible for you, it might be easier to drop the custom  
classloader entirely and to use the Java 1.5 instrumentation agent.  
More information about this here: http://rifers.org/docs/api/com/uwyn/rife/continuations/instrument/ContinuationsAgent.html

Hope this helps,

Geert


On 08 Jul 2008, at 11:49, Claas Altschaffel wrote:

Hello!
I have a problem with the Rife-Continuations in combination with
non-continuable objects.

I try to use the continuations to replace thread pools in an open  
source
multi agent system called Jadex. Continuations works so far, until i  
try to
make a loopback call from a non-continuable object to a continuable  
object
and then pause the continuation.

This is the (slightly modified) callstack:
TestClass.someMethod()    [e.g.  something like a executor or a test  
case]
 --> ContinuableRunner.start(ContinuableObject)
    --> ContinuableObject.execute()
            [pause continuation, set non-continuable object and resume
continuation]
       --> NonContinuableObject.someMethod()
          --> TestClass.loopbackTest()
             -->ContinuableObject.pauseContinuationMethod()
                --> pause() [called in the pauseContinuation]

After the loopback-method, the pause() call in the ContinuableObject  
throws
an UnsupportedOperationException.

Also a simplified callstack doesn't work:
 TestClass.someMethod()
    --> ContinuableRunner.start(ContinuableObject)
       --> ContinuableObject.execute()
            [pause continuation, set non-continuable object and resume
continuation]
           --> NonContinuableObject.someMethod()
              --> ContinuableObject.loopbackTest()
                --> pause() [called in the loopbackTest() method]

The second example only loops from the continuable object to the
non-continuable object,but the pause method throws the same exception.

In the attachement are two testcases and the needed classes. Hope  
this makes
my problem a little bit clearer. The testcases should work with the  
rife svn
tree.

Is it possible to implement such callstack with Rife-Continuations?  
And if
yes, can anybody tell me what i make wrong?

Testcases:
http://www.nabble.com/file/p18335150/testcases.tar.gz testcases.tar.gz
-- View this message in context: 
http://www.nabble.com/Continuable-callstack-outside-a-ContinuableObject--tp18335150s9330p18335150.html
Sent from the RIFE - users mailing list archive at Nabble.com.


--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Continuable callstack outside a ContinuableObject?

2008-07-08T03:05:14Z

Hi Claas,

I haven't tried out your sample code yet, but it seems to me that the
bytecode manipulation isn't happening for that pause() method, thus
causing the UnsupportedOperationException to be thrown. This is most
probably due to the ContinuableObject class not being loaded by the
custom classloader. You'll have to verify that.

If at all possible for you, it might be easier to drop the custom
classloader entirely and to use the Java 1.5 instrumentation agent.
More information about this here: http://rifers.org/docs/api/com/uwyn/rife/continuations/instrument/ContinuationsAgent.html

Hope this helps,

Geert

On 08 Jul 2008, at 11:49, Claas Altschaffel wrote:

>
> Hello!
> I have a problem with the Rife-Continuations in combination with
> non-continuable objects.
>
> I try to use the continuations to replace thread pools in an open
> source
> multi agent system called Jadex. Continuations works so far, until i
> try to
> make a loopback call from a non-continuable object to a continuable
> object
> and then pause the continuation.
>
> This is the (slightly modified) callstack:
> TestClass.someMethod() [e.g. something like a executor or a test
> case]
> --> ContinuableRunner.start(ContinuableObject)
> --> ContinuableObject.execute()
> [pause continuation, set non-continuable object and resume
> continuation]
> --> NonContinuableObject.someMethod()
> --> TestClass.loopbackTest()
> -->ContinuableObject.pauseContinuationMethod()
> --> pause() [called in the pauseContinuation]
>
> After the loopback-method, the pause() call in the ContinuableObject
> throws
> an UnsupportedOperationException.
>
> Also a simplified callstack doesn't work:
> TestClass.someMethod()
> --> ContinuableRunner.start(ContinuableObject)
> --> ContinuableObject.execute()
> [pause continuation, set non-continuable object and resume
> continuation]
> --> NonContinuableObject.someMethod()
> --> ContinuableObject.loopbackTest()
> --> pause() [called in the loopbackTest() method]
>
> The second example only loops from the continuable object to the
> non-continuable object,but the pause method throws the same exception.
>
> In the attachement are two testcases and the needed classes. Hope
> this makes
> my problem a little bit clearer. The testcases should work with the
> rife svn
> tree.
>
> Is it possible to implement such callstack with Rife-Continuations?
> And if
> yes, can anybody tell me what i make wrong?
>
> Testcases:
> http://www.nabble.com/file/p18335150/testcases.tar.gz testcases.tar.gz
> -- View this message in context:
> http://www.nabble.com/Continuable-callstack-outside-a-ContinuableObject--tp18335150s9330p18335150.html
> Sent from the RIFE - users mailing list archive at Nabble.com.
>
>
> >

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Continuable callstack outside a ContinuableObject?

2008-07-08T02:49:16Z

Hello!
I have a problem with the Rife-Continuations in combination with
non-continuable objects.

I try to use the continuations to replace thread pools in an open source
multi agent system called Jadex. Continuations works so far, until i try to
make a loopback call from a non-continuable object to a continuable object
and then pause the continuation.

This is the (slightly modified) callstack:
TestClass.someMethod() [e.g. something like a executor or a test case]
--> ContinuableRunner.start(ContinuableObject)
--> ContinuableObject.execute()
[pause continuation, set non-continuable object and resume
continuation]
--> NonContinuableObject.someMethod()
--> TestClass.loopbackTest()
-->ContinuableObject.pauseContinuationMethod()
--> pause() [called in the pauseContinuation]

After the loopback-method, the pause() call in the ContinuableObject throws
an UnsupportedOperationException.

Also a simplified callstack doesn't work:
TestClass.someMethod()
--> ContinuableRunner.start(ContinuableObject)
--> ContinuableObject.execute()
[pause continuation, set non-continuable object and resume
continuation]
--> NonContinuableObject.someMethod()
--> ContinuableObject.loopbackTest()
--> pause() [called in the loopbackTest() method]

The second example only loops from the continuable object to the
non-continuable object,but the pause method throws the same exception.

In the attachement are two testcases and the needed classes. Hope this makes
my problem a little bit clearer. The testcases should work with the rife svn
tree.

Is it possible to implement such callstack with Rife-Continuations? And if
yes, can anybody tell me what i make wrong?

Testcases:
http://www.nabble.com/file/p18335150/testcases.tar.gz testcases.tar.gz
-- View this message in context:
http://www.nabble.com/Continuable-callstack-outside-a-ContinuableObject--tp18335150s9330p18335150.html
Sent from the RIFE - users mailing list archive at Nabble.com.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Rife/Continuations execute with parameters

2008-07-07T00:47:17Z

Hi Lionel,

On 07 Jul 2008, at 09:25, Lionel Touati wrote:

> Hi Geert,
>
> Thanks for the pointers. I'll do that. What I've found out is that
> parent / child continuation support does not seem to work. I've got
> an issue as the parent continuation id is never set in the child
> one. Do you think it'll be solved in the snapshot ( I want to use it
> to support back links).

that's strange, I just went through some unit tests and the parent
child continuation IDs are set correctly. Would you be able to isolate
a test case with what you're seeing so that I can check what's going
on for you. Best verify with the latest snapshot though, I can't
remember all the fixes that went in over the last year ;-)

> Regarding continuation parameter, I couldn't find anything that
> relates to my problem, probably because I'l lacking on how the
> internal of continuations work. What I've done to support it is the
> following:
> use
> com
> .uwyn
> .rife
> .continuations
> .ContinuationContext.getActiveContext().setCallAnswer(parameter) to
> set a parameter, and using the callanswer to to create the state
> object in the call state, and then modifying the callTargetRetriever
> to pass it as a parameter of the constructor for my child
> continuation class. It's a bit tedious but it works.
>
> Do you think it'd be possible to add a ... parameter to the call
> method that will be able to pass the parameters ? It'd make my life
> much easyer.

I can look into adding this, please file an issue in RIFE's jira, I'll
try to make some time to look into it soon.

> Otherwise, it was really simple to hook Tapestry & Rife together,
> just a mater of creating several classes, and a tapestry service to
> make the thing work

Cool, I like this kind of stuff :-)

Take care,

Geert

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Rife/Continuations execute with parameters

2008-07-07T00:25:51Z

Hi Geert,

Thanks for the pointers. I'll do that. What I've found out is that parent / child continuation support does not seem to work. I've got an issue as the parent continuation id is never set in the child one. Do you think it'll be solved in the snapshot ( I want to use it to support back links).

Regarding continuation parameter, I couldn't find anything that relates to my problem, probably because I'l lacking on how the internal of continuations work. What I've done to support it is the following:

use com.uwyn.rife.continuations.ContinuationContext.getActiveContext().setCallAnswer(parameter) to set a parameter, and using the callanswer to to create the state object in the call state, and then modifying the callTargetRetriever to pass it as a parameter of the constructor for my child continuation class. It's a bit tedious but it works.

Do you think it'd be possible to add a ... parameter to the call method that will be able to pass the parameters ? It'd make my life much easyer.

Otherwise, it was really simple to hook Tapestry & Rife together, just a mater of creating several classes, and a tapestry service to make the thing work

Re: Rife/Continuations execute with parameters

2008-07-07T00:14:00Z

Hi Lionel,

sounds like you're doing cool stuff, please keep us posted!

First, I really should release a new version of RIFE but never seem to
be able to find the time. I strongly suggest that you download one of
the nightly napshots and use the RIFE/Continuations jar that's in
there. There have been some bug fixes for the standalone continuations
support in there.

For your question, you can use 'call-answer' continuations for what
you describe. You can find examples in the tests here: http://svn.rifers.org/rife/trunk/src/unittests/com/uwyn/rife/continuations/

Hope this helps,

Geert

On 05 Jul 2008, at 09:23, Lionel Touati wrote:

>
> Hi ,
>
> We're in the process of plugin Rife/Continuations to our existing
> Tapestry frontend. It works great but I'm having a small issue. I'd
> like to be able to call subcontinuations with parameters. For example
> I'm doing a search in Flow 1, and I'd like to start Flow2 with the
> result of this search.
>
> I could not find anything to do it, so my question is, is it
> possible ? (I'm using the BasicContinuableRunner)
>
> Thanks for any thought / pointers

Re: How to initialize a self-instantiated Element, so that processTemplate can be called?

2008-07-07T00:08:56Z

Hi,

what happens is indeed that RIFE can only generate exit values when
the web application is actually being used. There's some requite data
which is only available when a request object is available. So, you
need to make that request somehow. I think that for this, RIFE's out-
of-container testing could allow you to do what you want: http://rifers.org/wiki/display/RIFE/Out+of+container+testing

Retrieve your existing site instance and perform a request on the
element that would normally print out that template. Then you have
several options, either the output is exactly what you want, and you
can use response.getText(). Another option is to use
response.getTemplate(), and only use parts of your template structure.

Hope this helps,

Geert

On 04 Jul 2008, at 17:53, kodde wrote:

>
> Hi folks,
>
> I really enjoy using RIFE for my small project here, but currently I
> am stuck at a problem with Element objects and their not yet
> initialized contexts. I will try to explain my problem in detail:
>
> I have written an Executor class called "RequestUpdater" which gets
> executed every minute. I want this RequestUpdate to send an email on
> each execution, which basically works fine by now.
> Because I really like the templating system provided by Rife, I wanted
> to create the mail body via templates. Usually this would be no
> problem, because I could simply extend the Element class, select a
> template and call the "processTemplate" method. Now here comes the
> problem:
>
> Within my RequestUpdater (extending Executor) there is no
> processTemplate or anything approrpiate (of course not). So I tried to
> instantiate an existing class extending the Element class and called
> the processTemplate from there. Unfortunately I only get the
> Exception:
>
> "This element executed a method that requires a fully initialized
> element context"
>
> which I basically understand, but I don't know how to initialize the
> context of the element on my own. I tried something like
> Site.getRepInstance().resolveId("myId").getImplementationBlueprint but
> this doesn't work either (it's always null).
>
> So is there any possibility to use the template mechanism from within
> an Executor or do I have to hard code the output instead of using
> setOutput and EXIT:QUERY methods??
>
> Thanks in advance for your suggestions, and please excuse my bad
> English, it's not my mother tongue ;)
> >

Rife/Continuations execute with parameters

2008-07-05T00:23:22Z

Hi ,

We're in the process of plugin Rife/Continuations to our existing
Tapestry frontend. It works great but I'm having a small issue. I'd
like to be able to call subcontinuations with parameters. For example
I'm doing a search in Flow 1, and I'd like to start Flow2 with the
result of this search.

I could not find anything to do it, so my question is, is it
possible ? (I'm using the BasicContinuableRunner)

Thanks for any thought / pointers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

How to initialize a self-instantiated Element, so that processTemplate can be called?

2008-07-04T08:53:35Z

Hi folks,

I really enjoy using RIFE for my small project here, but currently I
am stuck at a problem with Element objects and their not yet
initialized contexts. I will try to explain my problem in detail:

I have written an Executor class called "RequestUpdater" which gets
executed every minute. I want this RequestUpdate to send an email on
each execution, which basically works fine by now.
Because I really like the templating system provided by Rife, I wanted
to create the mail body via templates. Usually this would be no
problem, because I could simply extend the Element class, select a
template and call the "processTemplate" method. Now here comes the
problem:

Within my RequestUpdater (extending Executor) there is no
processTemplate or anything approrpiate (of course not). So I tried to
instantiate an existing class extending the Element class and called
the processTemplate from there. Unfortunately I only get the
Exception:

"This element executed a method that requires a fully initialized
element context"

which I basically understand, but I don't know how to initialize the
context of the element on my own. I tried something like
Site.getRepInstance().resolveId("myId").getImplementationBlueprint but
this doesn't work either (it's always null).

So is there any possibility to use the template mechanism from within
an Executor or do I have to hard code the output instead of using
setOutput and EXIT:QUERY methods??

Thanks in advance for your suggestions, and please excuse my bad
English, it's not my mother tongue ;)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: mapping a bean instance to template

2008-06-30T01:08:55Z

Hi,

this is not possible. Some basic questions arise here though, how do
you format each bean property?

One way this is handled, is through RIFE/Crud, which has an API that
let's you do things like this. RIFE/Crud is being folded into RIFE
itself for the next release, so this will be even easier. You can
experiment with it and the samples (http://svn.rifers.org/rife/trunk/src/examples/tutorial/11_crud/src/
) if you download the latest snapshot.

Hope this helps,

Geert

On 30 Jun 2008, at 00:11, dk wrote:

>
> I want to use setBean() method to send all the fields in a bean but I
> don't want to write the template with all these lines. Instead, is
> there a mechanism to write the template like
> <bean:packacename.SomeClass/> .
>
> Thanks
> >

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

mapping a bean instance to template

2008-06-29T15:11:31Z

I want to use setBean() method to send all the fields in a bean but I
don't want to write the template with all these lines. Instead, is
there a mechanism to write the template like
<bean:packacename.SomeClass/> .

Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: question about Crud and Vector or List combination

2008-06-25T23:41:33Z

Nope, sorry, that isn't supported.

On 25 Jun 2008, at 22:06, dk wrote:

>
> A have a brief question,
>
> Is it possible to use Vector of ArrayList in a Crud Bean.
>
> Thanks
> >

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

question about Crud and Vector or List combination

2008-06-25T13:06:35Z

A have a brief question,

Is it possible to use Vector of ArrayList in a Crud Bean.

Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: custom authentication and participant

2008-06-20T11:10:59Z

Hi Rodrigue,

>
> As I said, I am now using a custom version of the identified
> mechanism. However I am getting confused once again. When you say
> "for that to work, you have to make sure that your authentication
> element executes before the rest"
> it seems to me that because all my elements inherit from the
> authentication element, the authentication always executes before the
> rest, does it not...?

You're correct. The last applications I developed with RIFE did not
use inheritance for authentication, but rather an embedded element as
a login box which then stored the credentials in the request as
attributes, leaving the site accessible but to guests and authorized
people.

> By inheriting from Auth, am I not insured that
> getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME) will return a
> non-null value?

Yes, you are.

> Also, the existing documentation is already quite substantial, so
> thanks to the work you and others have done. I'd be happy to try to
> extend it as soon as I have time, which means once my project in which
> I use rife is finished.

Cool, every bit of help is much appreciated.

Take care,

geert

--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "rife-users" group.
To post to this group, send email to rife-users@...
To unsubscribe from this group, send email to rife-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: custom authentication and participant

2008-06-20T09:04:26Z

Hi Geert,

Thanks for your answer. I did read the authentication system
internals, which was helpful in understanding how it works.

As I said, I am now using a custom version of the identified
mechanism. However I am getting confused once again. When you say
"for that to work, you have to make sure that your authentication
element executes before the rest"
it seems to me that because all my elements inherit from the
authentication element, the authentication always executes before the
rest, does it not...?
By inheriting from Auth, am I not insured that
getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME) will return a
non-null value?

Also, the existing documentation is already quite substantial, so
thanks to the work you and others have done. I'd be happy to try to
extend it as soon as I have time, which means once my project in which
I use rife is finished.

Rodrigue

On Jun 20, 4:22 pm, Geert Bevin <gbe...@...> wrote:

> Hi Rodrigue,
>
> sorry that the documentation is a bit lacking in this regard. Have you
> read through thishttp://rifers.org/wiki/display/RIFE/Authentication+system+internals
> ? I think that you should be able to get a better idea of how the
> authentication internals work. Also make sure to read the Javadoc of
> the relevant interfaces/classes.
>
> As far as storing variables somewhere after the authentication
> proceeds, this can be done in several ways. First, if you only want
> this to be available to all the other elements in the same request,
> it's best to use request attributes for this:http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#s...)
>
> This is what the identified element does. Of course, for that to work,
> you have to make sure that your authentication element executes before
> the rest, either by having it precede the others:http://rifers.org/wiki/display/RIFE/Precedence
>
> or by embedding it into your template and give it a high priority:http://rifers.org/wiki/display/RIFE/Embedded+element+priorities
>
> If you want to store these variables for a longer time, you can still
> access the regular HTTP session within RIFE, you just have to turn on
> raw access:http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#s...)
>
> After that you can use the unmanaged HTTP request and access the
> session:http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#g...()
>
> Other ways of doing this is by creating stateful components:http://rifers.org/wiki/display/RIFE/Stateful+components
>
> ... and if you don't want to store your RIFE flow state on the client-
> side, you can use other back-end stores, like sessions for instance:http://rifers.org/wiki/display/RIFE/Configurable+state+storage
>
> Hope this helps and if you find areas in the documentation that could
> use some improvement, please feel free to contribute.
>
> Take care,
>
> Geert
>
> On 20 Jun 2008, at 11:10, Rodrigue wrote:
>
>
>
>
>
> > Hi Matthias,
>
> > I have finally managed to do what I wanted to do, maybe not in the
> > best way though.
>
> > You didn't have to explicitly worry about the IdentifiableUsersManager
> > interface because your custom manager implements RoleUsersManager,
> > which extends IdentifiableUsersManager. Still, you certainly had to
> > implement getLogin() and getAttributes(). I only implement
> > IdentifiableUsersManager because I don't need the role feature.
> > However, I have written a custom class that extends
> > RoleUsersAttributes so that the getAttributes() method on the
> > RoleUserIdentity returns my custom object in which I can store more
> > information than just login, password, and role.
>
> > I read the user's guide section on managing user data (
> >http://rifers.org/wiki/display/RIFE/GuideDatabaseUsers#GuideDatabaseU...
> > ) but wasn't sure how to link that to my custom credentials manager.
>
> > Also, about your IDENTIFIED element, I don't think it is used at all
> > unless you have other elements that inherits from it, so I wasn't sure
> > either about how to use it.
>
> > Anyway, my application works at the moment so I will keep going even
> > though I doubt I am really managing my user data the best way. Also,
> > some details of rife are still obscure to me. I am not sure how the
> > identity information is saved. I think it is sent to the client and I
> > don't know how to explicitly keep it on the server side (which, in my
> > understanding, would require defining a db table).
>
> > All that is a bit of thinking aloud but maybe it can help somebody
> > who'll read it. In the meantime, I'll keep tinkering with rife until I
> > understand it more. At any rate, thanks for your help.
>
> > Rodrigue
>
> > On Jun 19, 11:09 am, Matthias Barmeier
> > <matthias.barme...@...> wrote:
> >> Hi Rodrigue,
>
> >> my Factory is really simple:
>
> >> package de.sourcepark.ms2.rife;
>
> >> import com.uwyn.rife.authentication.CredentialsManager;
> >> import
> >> com
> >> .uwyn
> >> .rife.authentication.credentialsmanagers.CredentialsManagerFactory;
> >> import com.uwyn.rife.ioc.HierarchicalProperties;
> >> import com.uwyn.rife.ioc.exceptions.PropertyValueException;
>
> >> No Id on have a Manager that implementes the interface you
> >> mentioned my
> >> decalaration is:
>
> >> public class MS2CredentialsManager implements CredentialsManager,
> >> RoleUsersManager
>
> >> What I have copied from some examples and not really understand is
> >> this
> >> main.xml element:
>
> >> <element id="IDENTIFIED"
> >> extends="rife/authenticated/identified.xml">
> >> <property name="authElementId">AuthClient</property>
> >> <childtrigger name="authid"/>
> >> </element>
>
> >> May be this creates the things you need on the fly.
>
> >> Ciao
> >> Matthias
>
> >> Rodrigue wrote:
> >>> Hi Matthias,
>
> >>> thank you again for your reply. I still have some trouble though.
>
> >>> When I call
>
> >>> RoleUserIdentity identity =
> >>> (RoleUserIdentity
> >>> )getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> >>> the identity is null. After looking at the rife source code I found
> >>> out that this is because my credentials manager does not implement
> >>> IdentifiableUsersManager. So I am now wondering what does your
> >>> de.sourcepark.ms2.rife.MS2CredentialsManagerFactory return in
> >>> getCredentialsManager?
> >>> Have you written your own CredentialsManager that also implements
> >>> IdentifiableUsersManager?
>
> >>> Rodrigue
>
> >>> On Jun 19, 9:57 am, Matthias Barmeier
> >>> <matthias.barme...@...> wrote:
>
> >>>> Hi Rodrigue,
>
> >>>> I use an entry element class as arrival:
>
> >>>> <arrival destid="EntryElement"/>
>
> >>>> The EntryElement is configured like:
>
> >>>> <element id="Entry"
> >>>> implementation="de.sourcepark.ms2.rife.EntryElement"
> >>>> inherits="AuthClient">
> >>>> <outbean name="customer" prefix="pre_"
>
> >>>> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
> >>>> <autolink srcexit="ClientCustomerEdit"/>
> >>>> <autolink srcexit="CustomerChangePw"/>
> >>>> </element>
>
> >>>> In the class I can call:
>
> >>>> RoleUserIdentity identity =
> >>>> (RoleUserIdentity
> >>>> )getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> >>>> to get the identity object and then:
>
> >>>> identity.getLogin()
>
> >>>> To get the username. In the EntryElement you can set if you like a
> >>>> global var to reflect the logged in user and his role.
>
> >>>> Hope this helps.
>
> >>>> Ciao
> >>>> Matthias
>
> >>>> Rodrigue wrote:
>
> --
> Geert Bevin
> Terracotta -http://www.terracotta.org
> Uwyn "Use what you need" -http://uwyn.com
> RIFE Java application framework -http://rifers.org
> Music and words -http://gbevin.com

Re: custom authentication and participant

2008-06-20T08:22:30Z

Hi Rodrigue,

sorry that the documentation is a bit lacking in this regard. Have you
read through this http://rifers.org/wiki/display/RIFE/Authentication+system+internals
? I think that you should be able to get a better idea of how the
authentication internals work. Also make sure to read the Javadoc of
the relevant interfaces/classes.

As far as storing variables somewhere after the authentication
proceeds, this can be done in several ways. First, if you only want
this to be available to all the other elements in the same request,
it's best to use request attributes for this:
http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#setRequestAttribute(java.lang.String,%20java.lang.Object)

This is what the identified element does. Of course, for that to work,
you have to make sure that your authentication element executes before
the rest, either by having it precede the others:
http://rifers.org/wiki/display/RIFE/Precedence

or by embedding it into your template and give it a high priority:
http://rifers.org/wiki/display/RIFE/Embedded+element+priorities

If you want to store these variables for a longer time, you can still
access the regular HTTP session within RIFE, you just have to turn on
raw access:
http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#setProhibitRawAccess(boolean)

After that you can use the unmanaged HTTP request and access the
session:
http://rifers.org/docs/api/com/uwyn/rife/engine/ElementSupport.html#getHttpServletRequest()

Other ways of doing this is by creating stateful components:
http://rifers.org/wiki/display/RIFE/Stateful+components

... and if you don't want to store your RIFE flow state on the client-
side, you can use other back-end stores, like sessions for instance:
http://rifers.org/wiki/display/RIFE/Configurable+state+storage

Hope this helps and if you find areas in the documentation that could
use some improvement, please feel free to contribute.

Take care,

Geert

On 20 Jun 2008, at 11:10, Rodrigue wrote:

>
> Hi Matthias,
>
> I have finally managed to do what I wanted to do, maybe not in the
> best way though.
>
> You didn't have to explicitly worry about the IdentifiableUsersManager
> interface because your custom manager implements RoleUsersManager,
> which extends IdentifiableUsersManager. Still, you certainly had to
> implement getLogin() and getAttributes(). I only implement
> IdentifiableUsersManager because I don't need the role feature.
> However, I have written a custom class that extends
> RoleUsersAttributes so that the getAttributes() method on the
> RoleUserIdentity returns my custom object in which I can store more
> information than just login, password, and role.
>
> I read the user's guide section on managing user data (
> http://rifers.org/wiki/display/RIFE/GuideDatabaseUsers#GuideDatabaseUsers-sect1additionaldata
> ) but wasn't sure how to link that to my custom credentials manager.
>
> Also, about your IDENTIFIED element, I don't think it is used at all
> unless you have other elements that inherits from it, so I wasn't sure
> either about how to use it.
>
> Anyway, my application works at the moment so I will keep going even
> though I doubt I am really managing my user data the best way. Also,
> some details of rife are still obscure to me. I am not sure how the
> identity information is saved. I think it is sent to the client and I
> don't know how to explicitly keep it on the server side (which, in my
> understanding, would require defining a db table).
>
> All that is a bit of thinking aloud but maybe it can help somebody
> who'll read it. In the meantime, I'll keep tinkering with rife until I
> understand it more. At any rate, thanks for your help.
>
> Rodrigue
>
> On Jun 19, 11:09 am, Matthias Barmeier
> <matthias.barme...@...> wrote:
>> Hi Rodrigue,
>>
>> my Factory is really simple:
>>
>> package de.sourcepark.ms2.rife;
>>
>> import com.uwyn.rife.authentication.CredentialsManager;
>> import
>> com
>> .uwyn
>> .rife.authentication.credentialsmanagers.CredentialsManagerFactory;
>> import com.uwyn.rife.ioc.HierarchicalProperties;
>> import com.uwyn.rife.ioc.exceptions.PropertyValueException;
>>
>> No Id on have a Manager that implementes the interface you
>> mentioned my
>> decalaration is:
>>
>> public class MS2CredentialsManager implements CredentialsManager,
>> RoleUsersManager
>>
>> What I have copied from some examples and not really understand is
>> this
>> main.xml element:
>>
>> <element id="IDENTIFIED"
>> extends="rife/authenticated/identified.xml">
>> <property name="authElementId">AuthClient</property>
>> <childtrigger name="authid"/>
>> </element>
>>
>> May be this creates the things you need on the fly.
>>
>> Ciao
>> Matthias
>>
>> Rodrigue wrote:
>>> Hi Matthias,
>>
>>> thank you again for your reply. I still have some trouble though.
>>
>>> When I call
>>
>>> RoleUserIdentity identity =
>>> (RoleUserIdentity
>>> )getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>>
>>> the identity is null. After looking at the rife source code I found
>>> out that this is because my credentials manager does not implement
>>> IdentifiableUsersManager. So I am now wondering what does your
>>> de.sourcepark.ms2.rife.MS2CredentialsManagerFactory return in
>>> getCredentialsManager?
>>> Have you written your own CredentialsManager that also implements
>>> IdentifiableUsersManager?
>>
>>> Rodrigue
>>
>>> On Jun 19, 9:57 am, Matthias Barmeier
>>> <matthias.barme...@...> wrote:
>>
>>>> Hi Rodrigue,
>>
>>>> I use an entry element class as arrival:
>>
>>>> <arrival destid="EntryElement"/>
>>
>>>> The EntryElement is configured like:
>>
>>>> <element id="Entry"
>>>> implementation="de.sourcepark.ms2.rife.EntryElement"
>>>> inherits="AuthClient">
>>>> <outbean name="customer" prefix="pre_"
>>
>>>> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
>>>> <autolink srcexit="ClientCustomerEdit"/>
>>>> <autolink srcexit="CustomerChangePw"/>
>>>> </element>
>>
>>>> In the class I can call:
>>
>>>> RoleUserIdentity identity =
>>>> (RoleUserIdentity
>>>> )getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>>
>>>> to get the identity object and then:
>>
>>>> identity.getLogin()
>>
>>>> To get the username. In the EntryElement you can set if you like a
>>>> global var to reflect the logged in user and his role.
>>
>>>> Hope this helps.
>>
>>>> Ciao
>>>> Matthias
>>
>>>> Rodrigue wrote:
> >

Re: custom authentication and participant

2008-06-20T02:10:59Z

Hi Matthias,

I have finally managed to do what I wanted to do, maybe not in the
best way though.

You didn't have to explicitly worry about the IdentifiableUsersManager
interface because your custom manager implements RoleUsersManager,
which extends IdentifiableUsersManager. Still, you certainly had to
implement getLogin() and getAttributes(). I only implement
IdentifiableUsersManager because I don't need the role feature.
However, I have written a custom class that extends
RoleUsersAttributes so that the getAttributes() method on the
RoleUserIdentity returns my custom object in which I can store more
information than just login, password, and role.

I read the user's guide section on managing user data (
http://rifers.org/wiki/display/RIFE/GuideDatabaseUsers#GuideDatabaseUsers-sect1additionaldata
) but wasn't sure how to link that to my custom credentials manager.

Also, about your IDENTIFIED element, I don't think it is used at all
unless you have other elements that inherits from it, so I wasn't sure
either about how to use it.

Anyway, my application works at the moment so I will keep going even
though I doubt I am really managing my user data the best way. Also,
some details of rife are still obscure to me. I am not sure how the
identity information is saved. I think it is sent to the client and I
don't know how to explicitly keep it on the server side (which, in my
understanding, would require defining a db table).

All that is a bit of thinking aloud but maybe it can help somebody
who'll read it. In the meantime, I'll keep tinkering with rife until I
understand it more. At any rate, thanks for your help.

Rodrigue

On Jun 19, 11:09 am, Matthias Barmeier
<matthias.barme...@...> wrote:

> Hi Rodrigue,
>
> my Factory is really simple:
>
> package de.sourcepark.ms2.rife;
>
> import com.uwyn.rife.authentication.CredentialsManager;
> import
> com.uwyn.rife.authentication.credentialsmanagers.CredentialsManagerFactory;
> import com.uwyn.rife.ioc.HierarchicalProperties;
> import com.uwyn.rife.ioc.exceptions.PropertyValueException;
>
> No Id on have a Manager that implementes the interface you mentioned my
> decalaration is:
>
> public class MS2CredentialsManager implements CredentialsManager,
> RoleUsersManager
>
> What I have copied from some examples and not really understand is this
> main.xml element:
>
> <element id="IDENTIFIED"
> extends="rife/authenticated/identified.xml">
> <property name="authElementId">AuthClient</property>
> <childtrigger name="authid"/>
> </element>
>
> May be this creates the things you need on the fly.
>
> Ciao
> Matthias
>
> Rodrigue wrote:
> > Hi Matthias,
>
> > thank you again for your reply. I still have some trouble though.
>
> > When I call
>
> > RoleUserIdentity identity =
> > (RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> > the identity is null. After looking at the rife source code I found
> > out that this is because my credentials manager does not implement
> > IdentifiableUsersManager. So I am now wondering what does your
> > de.sourcepark.ms2.rife.MS2CredentialsManagerFactory return in
> > getCredentialsManager?
> > Have you written your own CredentialsManager that also implements
> > IdentifiableUsersManager?
>
> > Rodrigue
>
> > On Jun 19, 9:57 am, Matthias Barmeier
> > <matthias.barme...@...> wrote:
>
> >> Hi Rodrigue,
>
> >> I use an entry element class as arrival:
>
> >> <arrival destid="EntryElement"/>
>
> >> The EntryElement is configured like:
>
> >> <element id="Entry"
> >> implementation="de.sourcepark.ms2.rife.EntryElement" inherits="AuthClient">
> >> <outbean name="customer" prefix="pre_"
>
> >> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
> >> <autolink srcexit="ClientCustomerEdit"/>
> >> <autolink srcexit="CustomerChangePw"/>
> >> </element>
>
> >> In the class I can call:
>
> >> RoleUserIdentity identity =
> >> (RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> >> to get the identity object and then:
>
> >> identity.getLogin()
>
> >> To get the username. In the EntryElement you can set if you like a
> >> global var to reflect the logged in user and his role.
>
> >> Hope this helps.
>
> >> Ciao
> >> Matthias
>
> >> Rodrigue wrote:

Re: custom authentication and participant

2008-06-19T03:09:20Z

Hi Rodrigue,

my Factory is really simple:

package de.sourcepark.ms2.rife;

import com.uwyn.rife.authentication.CredentialsManager;
import
com.uwyn.rife.authentication.credentialsmanagers.CredentialsManagerFactory;
import com.uwyn.rife.ioc.HierarchicalProperties;
import com.uwyn.rife.ioc.exceptions.PropertyValueException;

No Id on have a Manager that implementes the interface you mentioned my
decalaration is:

public class MS2CredentialsManager implements CredentialsManager,
RoleUsersManager

What I have copied from some examples and not really understand is this
main.xml element:

<element id="IDENTIFIED"
extends="rife/authenticated/identified.xml">
<property name="authElementId">AuthClient</property>
<childtrigger name="authid"/>
</element>

May be this creates the things you need on the fly.

Ciao
Matthias

Rodrigue wrote:

> Hi Matthias,
>
> thank you again for your reply. I still have some trouble though.
>
> When I call
>
> RoleUserIdentity identity =
> (RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> the identity is null. After looking at the rife source code I found
> out that this is because my credentials manager does not implement
> IdentifiableUsersManager. So I am now wondering what does your
> de.sourcepark.ms2.rife.MS2CredentialsManagerFactory return in
> getCredentialsManager?
> Have you written your own CredentialsManager that also implements
> IdentifiableUsersManager?
>
> Rodrigue
>
>
>
> On Jun 19, 9:57 am, Matthias Barmeier
> <matthias.barme...@...> wrote:
>
>> Hi Rodrigue,
>>
>> I use an entry element class as arrival:
>>
>> <arrival destid="EntryElement"/>
>>
>> The EntryElement is configured like:
>>
>> <element id="Entry"
>> implementation="de.sourcepark.ms2.rife.EntryElement" inherits="AuthClient">
>> <outbean name="customer" prefix="pre_"
>>
>> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
>> <autolink srcexit="ClientCustomerEdit"/>
>> <autolink srcexit="CustomerChangePw"/>
>> </element>
>>
>> In the class I can call:
>>
>> RoleUserIdentity identity =
>> (RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>>
>> to get the identity object and then:
>>
>> identity.getLogin()
>>
>> To get the username. In the EntryElement you can set if you like a
>> global var to reflect the logged in user and his role.
>>
>> Hope this helps.
>>
>> Ciao
>> Matthias
>>
>> Rodrigue wrote:
>>

Re: custom authentication and participant

2008-06-19T03:02:02Z

Hi Matthias,

thank you again for your reply. I still have some trouble though.

When I call

RoleUserIdentity identity =
(RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);

the identity is null. After looking at the rife source code I found
out that this is because my credentials manager does not implement
IdentifiableUsersManager. So I am now wondering what does your
de.sourcepark.ms2.rife.MS2CredentialsManagerFactory return in
getCredentialsManager?
Have you written your own CredentialsManager that also implements
IdentifiableUsersManager?

Rodrigue

On Jun 19, 9:57 am, Matthias Barmeier
<matthias.barme...@...> wrote:

> Hi Rodrigue,
>
> I use an entry element class as arrival:
>
> <arrival destid="EntryElement"/>
>
> The EntryElement is configured like:
>
> <element id="Entry"
> implementation="de.sourcepark.ms2.rife.EntryElement" inherits="AuthClient">
> <outbean name="customer" prefix="pre_"
>
> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
> <autolink srcexit="ClientCustomerEdit"/>
> <autolink srcexit="CustomerChangePw"/>
> </element>
>
> In the class I can call:
>
> RoleUserIdentity identity =
> (RoleUserIdentity)getRequestAttribute(Identified.IDENTITY_ATTRIBUTE_NAME);
>
> to get the identity object and then:
>
> identity.getLogin()
>
> To get the username. In the EntryElement you can set if you like a
> global var to reflect the logged in user and his role.
>
> Hope this helps.
>
> Ciao
> Matthias
>
> Rodrigue wrote:
> > Hi Matthias,
>
> > Thank you for your reply. I actually have the authentication working
> > as well. However I am now struggling to set and get values in the
> > session once the authentication is successful. Basically, once the
> > credentials are checked and correct, I want to add 2 variables in the
> > session so that all the elements in the subsite that inherits from
> > AUTH can have access to them.
>
> > I thought this should be done with global variables but I don't know
> > how to set and get them. I have tried to extend the
> > RoleUserAuthenticated class and do a setOutput() inside the
> > acceptedCredentials() hook. I ran into an exception saying "beanClass
> > cannot be null" thrown by ElementSupport.generateEmptyForm().
>
> > Are you trying to do something similar with your inbean and outbean?
> > If so, how does the inbean gets created and populated?
>
> > I have spent a few hours reading the wiki, the cookbook, the javadoc,
> > the source code, and I am now confused on how to do what I want. Also,
> > how to get access to the credentials object from an element that
> > inherits from AUTH? It seems tht it is possible only if you have the
> > 'login' value...Really, I don't know where to look now.
>
> > I'd really appreciate any help.
>
> > Rodrigue
>
> > On Jun 18, 5:02 pm, Matthias Barmeier
> > <matthias.barme...@...> wrote:
>
> >> Hi,
>
> >> I have written a CredentialsManager to. I am not sure how this rife
> >> magic works but this is my configuration:
>
> >> main.xml:
>
> >> <element id="AuthClient" extends="rife/authenticated/memory.xml">
> >> <property name="password_encryption">SHA</property>
> >> <property name="role">Client,Admin</property>
> >> 
> >> <property name="authvar_type">cookie</property>
> >> <property name="template_name">authentication.admin</property>
> >> <property
> >> name="credentialsmanagerfactory_class">de.sourcepark.ms2.rife.MS2CredentialsManagerFactory</property>
> >> <submission name="credentials">
> >> <param name="login"/>
> >> <param name="password"/>
> >> </submission>
>
> >> <childtrigger name="authid"/>
> >> </element>
>
> >> <element id="CustomerChangePw"
>
> >> implementation="de.sourcepark.ms2.rife.customer.EditCustomerPw"
> >> url="/customerchangepw" inherits="AuthClient">
> >> <inbean name="customer" prefix="pre_"
>
> >> classname="de.sourcepark.ms2.rife.customer.CBCustomerPwEdit"/>
> >> <outbean name="customer" prefix="pre_"
>
> >> classname="de.sourcepark.ms2.rife.customer.CBCustomerActiveEdit"/>
> >> <autolink srcexit="ClientCustomerEdit"/>
> >> <autolink srcexit="CustomerChangePw"/>
>
> >> </element>
>
> >> this works perfect for me.
>
> >> Hope this helps.
>
> >> Ciao
> >> Matthias
>
> >> Rodrigue wrote:
>
> >>> Hi,
>
> >>> I am working on my first Rife project and I need to authenticate my
> >>> users against a SOAP server. To do this, assuming I have understood
> >>> the way it works, I have written a class that implements
> >>> CredentialsManagerFactory to return my own CredentialsManager. I have
> >>> added a credentialsmanagerfactory_class property to my authentication
> >>> element. I have two questions though:
>
> >>> - Should I use the memory-based or the db authentication? Does it
> >>> matter at all since I won't use either the users xml file or the user
> >>> table? Or should I not add any participant for the authentication in
> >>> my participants.xml?
> >>> - If I need to declare a participant, how should I declare it? No
> >>> users.xml param or no datasource?
>
> >>> Rodrigue