Actually this is the default Appfuse User class. And the class has no-arg
constructor.
I've been debuggin jboss now. During jboss startup,
javassist.util.proxy.ProxyFactory.setField() method throws the exception in
the following highlighted line.
private void setField(String fieldName
I have found on Jumpstart Doublenegative a mixin which matches my needs.
It's the ZoneUpdater mixin by Inge Solvoll, and it is very easy to setup.
Here is the source code of the ZoneUpdater :
http://tinybits.blogspot.com/2010/03/new-and-better-zoneupdater.html
Here is the demonstration in
After a jboss restart and clean deploy, the application is deployed fine.
Below is what I did:
- javassist.jar is removed from JBOSS_HOME/server/default/lib folder.
- javassist-3.9.0-GA.jar is put inside JBOSS_HOME/server/default/lib
folder.
- javassist-3.9.0-GA.jar is removed from WEB
Dear List members,
I experienced a strange problem while combining Beaneditor annotations
with objects fetched through a lazy OneToOne association.
Beaneditor annotations on setter methods like
(@DataType(value="longtext") or @NonVisual) gets ignored when the
OneToOne association is lazy fetched (
I upgraded our organization to 3.12.0.GA javassist and a lot of issues
went away. Still a few issues, and I think the guy who patched it for
us submitted that patch to javassist, but it's light-years less
problematic than 3.9.
Christian
On Jul 9, 2010, at 5:37 AM, Halil Karakose wrote:
A
Thanks for your reply Thiago.
Unfortunately, correct me if I'm wrong, the ComponentModel (as of version
5.1.0.5, that I'm using) only returns the components that were annotated
with @InjectComponent or @Component in the containing page or parent
component, that makes it of little use :(
I'm sure
Sorry to be a pest, but how could I find a champion to apply the patch
for TAP5-1201? I understand Howard's busy and his time is probably
better spent on bigger issues than this, but I hope that some other
committer would be able to pick this up and apply the one-line change
that would restore func
Thiago, this snippet, at least in T5.1, does not always work. Tapestry also
"listens" the submit event of the form (in fact, it replaces the onsubmit
property of the form). So, if you have bad luck, the submission of the form
will ocurr before FCK can update the linked field.
To ensure that FCK u
