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
I was talking to Ales and Lincoln on IRC about how Weld handles modular environments. Whilst we have a full structure for representing module visibility relationships, we don't have any way of expressing that a bean is private to a module - all beans are exported. I don't think this really is consistent with how modular systems work, and so I think we need to add this to the BDA contract e.g.
public Collection<String> getPrivateBeanClasses();
I would suggest returning private/hidden classes rather than public ones here, as it means non-modular envs don't need to adjust their code much to have everything work as normal.
Some conversation-related questions
1. In WeldPhaseListener.activateConversations(), it appears as if the
conversation context is never activated if an unknown cid comes in.
Shouldn't the conversation context still be active but with a transient
conversation? Moving the conversationContext.activate(cid); before the check
2. Is there any way of setting the conversation timeout globally? The
constant defined in AbstractConversationContext appears to be injected into
the constructor of the ConversationImpl. If it would be acquired from a
producer method, could it then be specialized?
3. Should we have a concept of a "foreground conversation" in Weld so that
an incoming cid to a known, non-transient conversation would resurrect the
conversation even if it has been expired (but not yet cleaned up)? If I read
the code correctly, a cid that comes in after the expire time has passed is
still taken into use for the request but at the end marked as ended and then
cleaned up as transient.
It's with great pleasure that I announce the second release of the Griffon
This particular release enables other plugins to contribute beans tot the
BeanManager during application startup. To demonstrate the usage of this
plugin in conjunction with Griffon I've ported one of Weld's examples (the
numberguess game; swing version) into Griffon. The source code can be seen
It contains all the original source code except NumberGamesFrame. You'll
need Griffon 0.9.3 to run it.
Follow these steps to give it a whirl:
1. Download Griffon from http://griffon.codehaus.org/Download
2. Once your paths are configured (you can check this by running 'griffon
help') invoke the following commands inside the application's directory
griffon clean // this will pull all plugins and deps; you need a
griffon compile // compiles the code, yum!
griffon run-app // runs the application in standalone mode
All feedback welcome.
View this message in context: http://weld-development-discussions.46994.n3.nabble.com/ANN-Weld-plugin-0...
Sent from the Weld development discussions mailing list archive at Nabble.com.