[weld-issues] [JBoss JIRA] Commented: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object
[ https://issues.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589503#comment-12589503 ] John Ament commented on WELD-80: I'll need to review the test a bit more, but I am able to reproduce this in AS 6. In the ejb3 aop xml file, set the timeout low (the default is 5 minutes, that's enough). Set the session timeout in web.xml high (60 minutes). In a session scoped bean, create a reference to a local SFSB. make an initial request, then wait 5-10 minutes. The EJB will passivate, then on next invocation of the session scoped bean attempt to access the SFSB. This may be more of a spec issue though, the more I think about it. CDI scope and EJB passivation need to be linked. > Passivation of stateful session beans results in a loss of reference to > injected object > --- > > Key: WELD-80 > URL: https://issues.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 >Reporter: John Ament > Fix For: TBC > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-871) Publish snapshots for weld-osgi-bundle
[ https://issues.jboss.org/browse/WELD-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589438#comment-12589438 ] Dan Allen commented on WELD-871: I added the profile flag to the Weld-nightly build. > Publish snapshots for weld-osgi-bundle > -- > > Key: WELD-871 > URL: https://issues.jboss.org/browse/WELD-871 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration >Affects Versions: 1.1.0.Final >Reporter: Dan Allen >Assignee: Dan Allen >Priority: Minor > > It appears that the snapshots for the weld-osgi-bundle are not being > published to the JBoss snapshots repository: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/weld/ > The main weld artifacts are there, so it's clear that this is just the case > of a missing artifact. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Resolved: (WELD-871) Publish snapshots for weld-osgi-bundle
[ https://issues.jboss.org/browse/WELD-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Allen resolved WELD-871. Assignee: Dan Allen Resolution: Done Done. Snapshots are now being published. > Publish snapshots for weld-osgi-bundle > -- > > Key: WELD-871 > URL: https://issues.jboss.org/browse/WELD-871 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration >Affects Versions: 1.1.0.Final >Reporter: Dan Allen >Assignee: Dan Allen >Priority: Minor > > It appears that the snapshots for the weld-osgi-bundle are not being > published to the JBoss snapshots repository: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/weld/ > The main weld artifacts are there, so it's clear that this is just the case > of a missing artifact. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object
[ https://issues.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589377#comment-12589377 ] Pete Muir commented on WELD-80: --- John, we think with AS6 Final this should be much improved. Could you give it a spin and let us know what issues you hit? > Passivation of stateful session beans results in a loss of reference to > injected object > --- > > Key: WELD-80 > URL: https://issues.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 >Reporter: John Ament > Fix For: TBC > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object
[ https://issues.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589366#comment-12589366 ] Pete Muir commented on WELD-80: --- Test is org.jboss.weld.tests.enterprise.EnterpriseBeanTest.testPassivationOfEjbs(HelloAction) > Passivation of stateful session beans results in a loss of reference to > injected object > --- > > Key: WELD-80 > URL: https://issues.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 >Reporter: John Ament > Fix For: TBC > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589335#comment-12589335 ] Pete Muir commented on WELD-867: Nope, in Weld 1.0 this work was done inside the Context object -- http://anonsvn.jboss.org/repos/weld/core/tags/1.0.0/impl/src/main/java/org/jboss/weld/context/AbstractMapContext.java and look at getBeans() in http://anonsvn.jboss.org/repos/weld/core/tags/1.0.0/impl/src/main/java/org/jboss/weld/BeanManagerImpl.java > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589334#comment-12589334 ] Mark Struberg commented on WELD-867: Ah oki, but that was the one we used to get handed over to our Extension Contexts as well with weld-1.0. And now we seem to get the naked Contextual and not the wrapped SerializableContextual. > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589330#comment-12589330 ] Pete Muir commented on WELD-867: Yes, this is the one that is used to wrap all Beans inside the built in Context implementations. This was in Weld 1.0 and is in Weld 1.1... The built in Bean objects are not serializable, and the wrapping has always happened inside the Context. > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[
https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589327#comment-12589327
]
Mark Struberg commented on WELD-867:
what about this one? :)
* @author pmuir
*
*/
public class SerializableContextualImpl, I> extends
ForwardingContextual implements SerializableContextual
and
/**
* A serializable version of contextual that knows how to restore the
* original bean if necessary.
*
* @author Pete Muir
* @author Marius Bogoevici
*/
public interface SerializableContextual, I> extends
Serializable, Contextual
{
C get();
}
taken from
http://repo2.maven.org/maven2/org/jboss/weld/weld-core/1.0.0/weld-core-1.0.0-sources.jar
and
http://repo2.maven.org/maven2/org/jboss/weld/weld-spi/1.0/weld-spi-1.0-sources.jar
> CreationalContext implementations need to be serializable
> -
>
> Key: WELD-867
> URL: https://issues.jboss.org/browse/WELD-867
> Project: Weld
> Issue Type: Feature Request
> Components: Built-in beans, Clustering, Scopes & Contexts
>Affects Versions: 1.1.0.Final
>Reporter: Gerhard Petracek
> Fix For: 1.2.0.Beta1
>
>
> for custom scope implementations it's required that the creationalcontext is
> serializable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589323#comment-12589323 ] Pete Muir commented on WELD-867: Bean has never been Serializable in any final release of Weld, of this I am sure :-) Agreed on the CC stuff. > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589317#comment-12589317 ] Mark Struberg commented on WELD-867: Yes, that was the origin or our discussion. My argument is: a) the CreationalContext definition is currently broken regarding Serialization. Agree? b) So we need to fix the CC anyway, which means that we can also clarify the Bean part of the spec and even improve it by defining the original Weld behaviour (Weld 1.0, which was _THE_ RI for the official spec, DID serialize Beans properly!) as the standard. > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589300#comment-12589300 ] Pete Muir commented on WELD-867: Ok, I retitled the issue. Mark, AFAICS Weld's CC impl is serializable as long as the Bean implements PassivationCapable and the bean impl is serializable. Isn't the real issue here that the Bean passed to a custom Context impl by Weld isn't serializable? I think what we discussed before on IRC is having Weld wrap this bean if passed to custom context in a serializable wrapper that knows how to serialize/deserialize as you and Stuart discussed. > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (WELD-867) CreationalContext implementations need to be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated WELD-867: --- Summary: CreationalContext implementations need to be serializable (was: bean implementations should be serializable) Description: for custom scope implementations it's required that the creationalcontext is serializable. (was: for custom scope implementations it's required that beans are serializable. -> one of the following classes should implement java.io.Serializable https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/RIBean.java https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/AbstractBean.java https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/ManagedBean.java) > CreationalContext implementations need to be serializable > - > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that the creationalcontext is > serializable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) bean implementations should be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589295#comment-12589295 ] Mark Struberg commented on WELD-867: As I said in my initial comment: the main problem is not the serialization of Bean itself, but serialization of CreationalContexts containing those Beans! CreationalContext itself is not Serializable yet and there is no passivationId for them of course... > bean implementations should be serializable > --- > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that beans are serializable. > -> one of the following classes should implement java.io.Serializable > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/RIBean.java > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/AbstractBean.java > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/ManagedBean.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-867) bean implementations should be serializable
[ https://issues.jboss.org/browse/WELD-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589294#comment-12589294 ] Pete Muir commented on WELD-867: Personally I don't think there is any reason to make Bean implement serializable, it's better to use the spec defined mechanism of getPassivationCapableBean > bean implementations should be serializable > --- > > Key: WELD-867 > URL: https://issues.jboss.org/browse/WELD-867 > Project: Weld > Issue Type: Feature Request > Components: Built-in beans, Clustering, Scopes & Contexts >Affects Versions: 1.1.0.Final >Reporter: Gerhard Petracek > Fix For: 1.2.0.Beta1 > > > for custom scope implementations it's required that beans are serializable. > -> one of the following classes should implement java.io.Serializable > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/RIBean.java > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/AbstractBean.java > https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/ManagedBean.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-871) Publish snapshots for weld-osgi-bundle
[ https://issues.jboss.org/browse/WELD-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589286#comment-12589286 ] Pete Muir commented on WELD-871: Just need to add -Pbundles to the build command... > Publish snapshots for weld-osgi-bundle > -- > > Key: WELD-871 > URL: https://issues.jboss.org/browse/WELD-871 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration >Affects Versions: 1.1.0.Final >Reporter: Dan Allen >Priority: Minor > > It appears that the snapshots for the weld-osgi-bundle are not being > published to the JBoss snapshots repository: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/weld/ > The main weld artifacts are there, so it's clear that this is just the case > of a missing artifact. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-870) Add injection point information to exception message when injection into observer fails
[ https://issues.jboss.org/browse/WELD-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589267#comment-12589267 ] Pete Muir commented on WELD-870: They should be. > Add injection point information to exception message when injection into > observer fails > --- > > Key: WELD-870 > URL: https://issues.jboss.org/browse/WELD-870 > Project: Weld > Issue Type: Enhancement > Components: Events >Affects Versions: 1.1.0.Final >Reporter: Dan Allen > > Injections that fail when an observer method is invoked are massively hard to > track down. Here's the information you get: > org.jboss.weld.exceptions.IllegalArgumentException: WELD-001324 Argument bean > must not be null >at > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:714) >at > org.jboss.seam.exception.control.HandlerMethodImpl.notify(HandlerMethodImpl.java:187) >at > org.jboss.seam.exception.control.ExceptionHandlerDispatch.executeHandlers(ExceptionHandlerDispatch.java:128) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >at java.lang.reflect.Method.invoke(Method.java:616) >at > org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) >at > org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) >at > org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) >at > org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) >at > org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) >at > org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) >at > org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) >at > org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) >at > org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) >at > org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) >at > org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632) >at > org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) >at > org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) > I expect to see the type and qualifiers at the failing injection point. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
