right ---
makes perfect sense; i forgot one could choose which CMP fields made it into the
interfaces (i must have started to take my stock set or pattern of xdoclet tags for
granted, and forgot the basics!).
thanks so much!
mike
View the original post :
http://www.jboss.org/index.html?modul
Forgot to add that you also need to set your flag in the ejbCreates, the ejbLoad and
the ejbActivate.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3823278#3823278
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3823278
Don't expose the CMP field in the interface, instead expose a method that sets the CMP
field and your flag.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3823276#3823276
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3
hmmm... on second thought, i think i'm back to where i started from:
how would my non-cmp entity bean field know when to invalidate its privately stored
preparsed DOM? some kind of callback from the CMP layer is the only way i can think
of, so my bean can find out when one of its CMP fields was
oh boy, silly me :-)
i realized the answer is clearly that i've got the wrong approach... i forgot that i
can mix cmp and non-cmp fields in an entity bean, and that way i can have a non-cmp
field provide the parsed xml DOM, storing it in an instance variable between
invocations. then, the jboss
