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
8 months
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
14 years, 4 months
Weld 2
by Pete Muir
All
I'm pleased to say that development on Weld 2 will start in earnest next week. Weld 2 will be implementing CDI 1.1.
Jozef Hartinger is starting part time on this. He will be doing 30hrs a week until his thesis finishes, at which point he will switch to full time. Jozef has previously worked for the JBoss QA department, and was a big contributor to the CDI 1.0 TCK. He's also been a contributor to Seam for many years. Welcome Jozef!
Jozef will send out more info, like info on the branch for Weld 2 on github, and get JIRA set up to report bugs against 2.0.0 next week.
With this in mind we will have a weekly IRC meeting at 2pm UK time to keep everyone up to date with the status of the development. Here's the first one http://www.timeanddate.com/worldclock/fixedtime.html?msg=Weld+2.0+meeting.... I'll add you to a calendar invite if you want, just send me a note.
At this meeting we'll hear from Jozef about progress on Weld 2, and Martin Kouba, who is now leading the CDI TCK, about progress on the CDI 1.1 TCK.
Best,
Pete
14 years, 10 months
Syncing weld to maven central
by Pete Muir
Hi guys
A couple of issues have been raised:
1) the current weld-parent-core has SNAPSHOT deps in them. These need removing. Ales, can you make sure to upgrade these for Weld 1.1.3? Then we can sync that.
2) We need to eradicate the JBoss repository eventually. I think most of the core deps are now in central (IIRC the main offender was the JBoss spec APIs, which are now in central). We can then remove the repo definition from the parent pom, and just insert it into the ones that need it (all the testsuite stuff). Joel is looking to see if we can exclude individual artifacts from the sync, if he can I recommend we just don't sync the test related artifacts, as they aren't generally useful. Ales, can you look into this for 1.1.3 as well?
Otherwise, Joel's analysis was that we were good to go, so if we get the above done, it should be straightforward to sync 1.1.3.
:-)
14 years, 11 months
how to inspector the out jected bean?
by 宿宝臣
hi all,
I'm just beginning to study weld, so if this is a noob question, please
forgive me:-)
I want to list all the beans produced by @Produces at any time, in order to
inspect how @Produces and @Inject works, that is, when and how will
@Produces out inject a bean to container, and when and how @Inject inject a
bean into my code. I don't know if any way there? Somewhat listener? or
somewhat interceptor? any sample code?
Thanks in advance for any help!
--
--
Su Baochen
14 years, 11 months
