Hey all,
we are currently developing an application based on Weld 1.0.1 and
MyFaces CODI. Unfortunately we have some strange problems regarding
CODI's @Transactional not always being applied correctly. It seems to
be completely ignored in some situations.
I've reproduced this problem with
Hi Christian!
The major difference between Weld and OpenWebBeans in the interceptor area is
that Weld strictly follows the Bean Definition Archive (BDA) part of the
spec. This got added pretty late (in the last few weeks before the spec went
final and imo is complete crap [1] ;)
In Weld you
Try to unzip the jar into web-inf/classes and add its beans.xml content to
the one in web-inf.
This was suggested to my by the glassfish team... :-)
sent from my Android phone
On Mar 9, 2011 1:31 PM, Christian Kaltepoth christ...@kaltepoth.de
wrote:
Hey all,
we are currently developing an
Hi Mark,
thank you very much for your response. I've tried your suggestion and
it worked great. I didn't knew about the BDA part in the spec and
assumed that CODI's beans.xml would globally enable the interceptor.
You are right! This BDA stuff is crap! :-)
@Matthias: Nice workaround! ;)
Thanks
Hi, i have this code:
*a4j:region*
*h:selectBooleanCheckbox*value=#{subtipo.seleccionado} id=checks
disabled=#{VDBean.modoEdicion ==
false} onchange=call some javascript code
I have not used a4j:actionparam, but under richfaces, I have successfully used
a4j:support
f:setPropertyActionListener target=#{target1} value=#{value1} /
f:setPropertyActionListener target=#{target2} value=#{value2} /
/a4j:support
Perhaps that will do what you need.
On Wed, Mar 9,
Thanks Myke but I'm using myfaces tomahawk, not richfaces.
I also tried a more simple code:
In the JSP:
h:commandButton value=seleccionar
actionListener=#{VisitaDomiciliarBean.seleccionar} id=seleccionarLink
style=display:none
*f:param
7 matches
Mail list logo
