Is there any planned transactional wrapper around lists, queues
or EDU.oswego.cs.dl.util.concurrent.Channel ?
Cheers,
Guillaume
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi there,
I am using jelly with the sql taglibs to generate an xml file filled
with data from a database.
Some of the sql scripts I use involve selecting ranges of values using
'=' as an operator like in
select * from ${databaseTable} where id = 1
When using the = directly, I get an error from
I have xml I need to map to my bean. It is very similar to the
CustomerBean example, except I am using Collection instead of and array
of objects (i.e. Order[]). Here is a sample of the xml, followed by my
class, followed by my .betwixt file. The problem I am having is the
List is always
AFAIK nothing like that scheduled. I was wondering how would this look
like for something ordered like a list?
What would happen if transaction a added a an enttry at position 0 and
transaction b another one at position 1? Would this even be allowed in
parallel? How would the resulting list look
I will be out of the office starting 01/13/2005 and will not return until
01/14/2005.
I will respond to your message when I return.
Even though the current javascript mask validator ignores password fields
the validation algorithm is still revealed since (in Struts) the javascript
to call that validator with the appropriate regexp is still generated.
I also think that we shouldn't restrict what validation can be specified
When you read or write the bean using Betwixt, try
writer.getXMLIntrospector().getConfiguration().setWrapCollectionsInElement(false);
or
reader.getXMLIntrospector().getConfiguration().setWrapCollectionsInElement(false);
where writer or reader is your BeanWriter or BeanReader.
Tim
I think you want this ...
IntrospectionConfiguration.setWrapCollectionsInElement(false)
Jason
-Original Message-
From: Matt Goodwin [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 13, 2005 11:02 AM
To: Jakarta Commons Users List
Subject: [betwixt] Collection property question
I
Even though you tell the user the password rules they still shouldn't be
able to see the details of how you're validating the password. I believe
validator should ship with the secure best practices implemented by
default and make the user enable/disable as they want.
David
--- Niall Pemberton
I have that set. It appears that my class is not being recognized in
the parse process. My add method on my class is never called.
Matt
Jason Wood wrote:
I think you want this ...
IntrospectionConfiguration.setWrapCollectionsInElement(false)
Jason
-Original Message-
From: Matt
Harald,
It really looks like this is a bug.
I've made a test at fixing but... we have no infrastructure to really
test the taglib and such a bug... it seems easy to do so with hsqldb
around... Someone with experience with this taglib would be more than
welcome doing so.
Can you give a try to
Could you send the complete code you are using to read with?
Tim
-Original Message-
From: Matt Goodwin [mailto:[EMAIL PROTECTED]
Sent: Thu 1/13/2005 2:58 PM
To: Jakarta Commons Users List
Subject: Re: [betwixt] Collection property question
I have that set. It appears that my class
public void testReadBean() {
try {
File file = new File(FILE1);
BeanReader beanReader = new BeanReader();
beanReader.registerBeanClass(AgentStatement.class);
AgentStatement statement =
(AgentStatement)beanReader.parse(file);
}
That sounds fine in theory, but I can't see how we could actually implement
that in reality. When the validation javascript is being rendered there is
no knowledge of whether the associated form field is a password type or
not and just having the actual validators ignoring password fields isn't
Do any rules exist that will execute if an unexpected element or attribute
is encountered in an XML file.
For the following xml
tag-a/
tag-b/
tag-c/
And the following code
Digester dig = new Digester();
dig.addObjectCreate(*/tag-a, ATag.class);
15 matches
Mail list logo
