Re: Help with Digester xmlrules to create a complex object

2006-07-05 Thread Simon Kitching
Hi Hernan, On Wed, 2006-07-05 at 19:29 -0300, Hernán Seoane wrote: Hello, I'm having some trouble with Digester when trying to create a complex object from the following xml: Competition CompetitionNameCompetition/CompetitionName PrizeOnOffer2000/PrizeOnOffer

Re: Help with Digester xmlrules to create a complex object

2006-07-05 Thread Hernán Seoane
Thank you very much, Simon!!! Using the targetoffset attribute in the call-method-rule solved my problem. Hernán On 7/5/06, Simon Kitching [EMAIL PROTECTED] wrote: Hi Hernan, On Wed, 2006-07-05 at 19:29 -0300, Hernán Seoane wrote: Hello, I'm having some trouble with Digester when trying to

Re: Help with digester!

2004-05-17 Thread José Antonio Pérez Testa
It looks like everything is ok. Look at the logs and see what's happening. Maybe some problem with the arguments types. Try the method addCallMethod(String pattern, String methodName, int paramCount, String[] paramTypes) and explicitly set the argument types. I've found a similar problem in

Re: Help with digester

2003-05-29 Thread C F
Thanks for the helpful info. I had actually tried pretty much what you suggested but as your predicted, there were some issues with that. Anyway, I agree with you that explicit declarations would help here, but I'm trying to conform to a schema that has elements that allow mixed content

Re: Help with digester

2003-05-27 Thread Craig R. McClanahan
On Tue, 27 May 2003, C F wrote: Date: Tue, 27 May 2003 13:31:16 -0700 (PDT) From: C F [EMAIL PROTECTED] Reply-To: Jakarta Commons Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Help with digester Hello, Could somebody please give me an example of how I might try to

Re: help with digester in weblogic

2002-12-17 Thread robert burrell donkin
hi marco i think i can give you an explanation. weblogic runs under restrictive security environment. this prevents one of the pre-java 1.4 reflection bug workarounds from working. what you can see should be just a warning (rather than an error). digester should still run fine after this