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
Would it be acceptable to add a conversation termination request token in
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.
I'm can't resolve a problem with weld.
I have some beens, they are all called in this manner,
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.