Hi Geert
Here's my element definition
element implementation=Register id=REGISTER url=/register.asp
submission name=register
bean classname=UserInfo/
bean classname=RoleUser/
/submission
/element
And as i wrote below validation worked for all 2 beans but
First question is closed too.
I should generateForm for second bean too like this:
generateForm(template, user);
generateForm(template, userInfo);
Geert, please correct http://rifers.org/wiki/display/RIFE/GuideDatabaseUsers
wiki page in Managing additional user data section, you should add
Hi,
I have this simple site :
site
arrival destid=Start/
element id=Start url=/start implementation=com.test.Start
exit name=started /
flowlink srcexit=started destid=Second
datalink srcoutput=counter destinput=counter/
Sorry, I made a mistake in copying the code. The second datalink is in the
element Second like this:
site
arrival destid=Start/
element id=Start url=/start implementation=com.test.Start
exit name=started /
flowlink srcexit=started destid=Second
What's the implementation of Second?
On 12 Jan 2007, at 13:19, Jean-Marie Galliot wrote:
Sorry, I made a mistake in copying the code. The second datalink is
in the
element Second like this:
site
arrival destid=Start/
element id=Start url=/start implementation=com.test.Start
Hi Jean-Marie,
the reason why this happens is that RIFE dynamically uses the outputs
at any given time. For example, when you generate an exit to go to a
first element the output values can be different than the output
values for another exit link. There are several other mechanics at
Hi Henk,
this seems to be a regression bug that creeped in a little while ago,
can you please file a Jira issue for this?
Best regards,
Geert
On 11 Jan 2007, at 20:39, Henk wrote:
Hi,
is it possible that, when using a named output bean, an object of
type java.util.Date does not get
Geert,
another problem
I have not-bean field
!--V 'FORM:SECRET:passwordConfirmation'--maxLength=50 size=25
tabindex=5!--/V--
and i generate it by hands
public void processElement() throws EngineException {
...
builder.generateField(template, PASSWORD_CONFIRMATION, null, null);
...
}
than in
RIFE only lets parameters through that are declared. If you have a
standalone parameter that is not part of a bean as a property, you'll
have to add it yourself to the submission.
Best regards,
Geert
On 12 Jan 2007, at 16:31, Maxim Grigoriev wrote:
Geert,
another problem
I have
This issue is fixed and has been committed to Subversion.
On 11 Jan 2007, at 11:50, Erik Bogghed wrote:
Hi Geert,
It works fine. What is the purpose of template.clear()?
Thanks,
Erik
On Jan 10, 2007, at 11:40 PM, Geert Bevin wrote:
Hi Erik,
I looked into your example and I can reproduce
Hi David,
did you have a chance to package a minimal example for me so that I
look at this?
I agree that it would be nice to integrate something more intuitive
for dynamic selects in 1.6. Your input on this is much appreciated,
any suggestions to simplify the API, even if it doesn't work
Hi All,
There are two things that would be really helpful in 1.6 that occur
to me today:
1) a new constraint, a compliment to .inList() namely .notInList
(), for example
.addConstraint(new ConstrainedProperty(username)..notEmpty
(true).notNull(true).notInList(root, bin, system, mysql,
I'll try to get to it this weekend. I've been coding away trying to
get this app ready for friendly testing...
David
On Jan 12, 2007, at 10:51 AM, Geert Bevin wrote:
Hi David,
did you have a chance to package a minimal example for me so that I
look at this?
I agree that it would be nice
Hi David,
I agree with both, the second one has actually already been planned
here http://uwyn.com/issues/browse/RIFE-188, but for 1.7. Can you add
an issue for the first one?
Thanks!
Geert
On 12 Jan 2007, at 19:58, David HM Spector wrote:
Hi All,
There are two things that would be
Thanks, I commented on RIFE-321, I don't think it needs an additional
constraint.
On 12 Jan 2007, at 20:29, David HM Spector wrote:
done! I created two feature requests, one [RIFE-320] for notInList
() and one [RIFE-321] for the regexp suggestion.
--
Geert Bevin
Uwyn Use what you need -
David HM Spector wrote:
a regex capability for both inList() and my proposed compliment to it
would be great.. .and could make it easier to keep potentially
insecure crud (like SQL injections) from being pushed through forms.
Shouldn't PreparedStatements make SQL injections a non-issue?
--
Hi Christian,
totally correct!
... and if you don't want to use prepared statements, using the query
builders in RIFE will automatically protect the values that you
provide against SQL injection.
Take care,
Geert
On 12 Jan 2007, at 23:26, Christian Vest Hansen wrote:
David HM Spector
17 matches
Mail list logo
