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
3 months, 2 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, 11 months
weld developer mailing list subscription
by Mehdi Heidarzadeh
Hi @ all
I have subscribed to weld developer mailing list.
But I don't see any email or discussion!
Just some weld dev digest messages.
Do you use other ways to discuss about weld or I might have done something
wrong?
Thanks
--
Mehdi Heidarzadeh Ardalani
Independent JEE Consultant, Architect and Developer.
http://www.TheBigJavaBlog.com
14 years
Fwd: [JBoss JIRA] (WELD-510) Support for Portlet 2.0
by Pete Muir
Guys, We still don't have portlet support? Ales, can you work with Marko on this as you are close to each other?
Begin forwarded message:
> From: "Adam Michalik (JIRA)" <jira-events(a)lists.jboss.org>
> Subject: [JBoss JIRA] (WELD-510) Support for Portlet 2.0
> Date: 20 April 2012 19:13:17 GMT+05:30
> To: pmuir(a)bleepbleep.org.uk
>
>
> [ https://issues.jboss.org/browse/WELD-510?page=com.atlassian.jira.plugin.s... ]
>
> Adam Michalik edited comment on WELD-510 at 4/20/12 9:41 AM:
> -------------------------------------------------------------
>
> I have attached a test project.
>
> Steps to reproduce:
> 1) Download Liferay Portal Community Edition 6.1.0 CE budled with Tomcat from http://www.liferay.com/downloads/liferay-portal/available-releases
> 2) Unpack to - let's call it - ${LIFERAY_HOME}
> 3) Start Liferay with {LIFERAY_HOME}/tomcat-xxx/bin/startup.sh
> 4) Go to http://localhost:8080 to finish setup
> 5) Unzip the attached project, run mvn package
> 6) Copy the war file to ${LIFERAY_HOME}/deploy
> 7) Log in as the admin user and add the weld-510 portlet
> 8) Observe stacktrace in Liferay's logs ({LIFERAY_HOME}/tomcat-xxx/logs/catalina.out)
>
> The portlet works fine without Weld:
> 1) In web.xml disable the WeldCrossContextFilter filter and filter-mapping
> 2) In HelloWorld class toggle from @Model to @ManagedBean
> 3) run mvn package -P!weld
> 4) deploy to Liferay
> 5) The portlet appears fine
>
> was (Author: hattifnat):
> Steps to reproduce:
> 1) Download Liferay Portal Community Edition 6.1.0 CE budled with Tomcat from http://www.liferay.com/downloads/liferay-portal/available-releases
> 2) Unpack to - let's call it - ${LIFERAY_HOME}
> 3) Start Liferay with {LIFERAY_HOME}/tomcat-xxx/bin/startup.sh
> 4) Go to http://localhost:8080 to finish setup
> 5) Unzip the attached project, run mvn package
> 6) Copy the war file to ${LIFERAY_HOME}/deploy
> 7)Log in as the admin user and add the weld-510 portlet
> 8) Observe stacktrace in Liferay's logs ({LIFERAY_HOME}/tomcat-xxx/logs/catalina.out)
>
> The portlet works fine without Weld:
> 1) In web.xml disable the WeldCrossContextFilter filter and filter-mapping
> 2) In HelloWorld class toggle from @Model to @ManagedBean
> 3) run mvn package -P!weld
> 4) deploy to Liferay
> 5) The portlet appears fine
>
>> Support for Portlet 2.0
>> -----------------------
>>
>> Key: WELD-510
>> URL: https://issues.jboss.org/browse/WELD-510
>> Project: Weld
>> Issue Type: Feature Request
>> Affects Versions: 1.0.1.Final
>> Reporter: Neil Griffin
>> Assignee: Marko Strukelj
>> Priority: Blocker
>> Fix For: 1.1.3.Final
>>
>> Attachments: weld-510.zip
>>
>>
>> There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue.
>> Original Post:
>> http://www.portletfaces.org/community/forums/-/message_boards/message/430...
>> Here is a simple stacktrace of the problem:
>> Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment
>> at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119)
>> at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener
>> The code for the bridge API is here:
>> http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid...
>> The code for the bridge IMPL is here:
>> http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid...
>> And the code for a sample portlet is here:
>> http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-...
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
14 years
