WELD-862 and Seam Cron
by Peter Royle
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks. Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which prevents Cron from running properly with Weld. I have been able to carry on developing Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will work with the version of Weld already deployed in JBoss AS and Glassfish, which will contain the bug. The workaround mentioned in the bug report is to deep copy the InvocationContext. I attempted to do this by serialising and unserialising the InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any advice for me about how I might be able to work around this bug to support existing versions of Weld?
Cheers,
Pete R
1 month, 4 weeks
Adding Classes at Run-time
by Jason Lee
I have an odd question. I have a situation where I'm manually opening a
JAR and adding its classes to the ClassLoader. What I'd like to be able
to do is have Weld scan these classes for any relevant annotations and
take the proper actions, just as if the JARs were in the classpath when
the application started. I've been staring at the JavaDocs (build
locally, btw, as I can't find them on the web :| ) but I don't see any
way to request that Weld inspect a given class. Is it there and I'm
missing it? Am I going to have cobble together that functionality? Am
I asking for something that can't be done (right now)? Any nudges in
the right direction would be much appreciated. :)
--
Jason Lee, SCJP
President, Oklahoma City Java Users Group
Senior Java Developer, Sun Microsystems
http://blogs.steeplesoft.com
13 years, 10 months
Conversation termination
by Nicklas Karlsson
Hi,
Would it be acceptable to add a conversation termination request token in
Weld?
If found in the request parameter map (e.g. named "nocid"), the
WeldPhaseListener.getConversationId would return null. This could be used in
commandLink f:params to stop conversation propagation. The problem is that
there is no(?) nice way of getting rid of the cid after the
ConversationAwareViewHandler adds it for non-transient conversations since
it ends up in the form action and not per-component.
As I see it, it's not breaking the specification and would just be a usable
add-on with little foreseeable side-effets.
--
---
Nik
14 years, 9 months
Need Help
by geschtli
Hello
I'm can't resolve a problem with weld.
I have some beens, they are all called in this manner,
@Named("myBean")
@SessionScoped
@Stateful
public class MyBean implements Serializable
No one has a transient object.
All is working good, how long the beans are not passivated.
After that, they cannot be reactivated and the application crashes
with an weld proxie ClassCastException.
Must the user than after bean passivation do an explizit jndi lookup?
--
View this message in context: http://weld-development-discussions.46994.n3.nabble.com/Need-Help-tp29895...
Sent from the Weld development discussions mailing list archive at Nabble.com.
14 years, 9 months
