November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-395?page=all ] Gavin King updated JBSEAM-395: ------------------------------ Fix Version/s: 1.1.5.GA (was: 1.1.1.GA) > Alternate "dispatcher" strategies > --------------------------------- > > Key: JBSEAM-395 > URL: http://jira.jboss.com/jira/browse/JBSEAM-395 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.5.GA > > > Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-401) Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-401?page=all ] Gavin King updated JBSEAM-401: ------------------------------ Fix Version/s: 1.1.1.GA (was: 1.1.0.GA) > Contexts.destroy(BusinessProcessContext) hits the database after the seam managed transaction ends > -------------------------------------------------------------------------------------------------- > > Key: JBSEAM-401 > URL: http://jira.jboss.com/jira/browse/JBSEAM-401 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.1.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-304) deployable GlassFish example

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-304?page=all ] Gavin King updated JBSEAM-304: ------------------------------ Summary: deployable GlassFish example (was: Deploy targets for GlassFish) > deployable GlassFish example > ---------------------------- > > Key: JBSEAM-304 > URL: http://jira.jboss.com/jira/browse/JBSEAM-304 > Project: JBoss Seam > Issue Type: Feature Request > Components: Examples > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.GA > > > Roger Kitain has contributed deploy script stuff for GlassFish. (We won't have a generic deploy target, since glassfish requires the awful ejb-link stuff.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-304) Deploy targets for GlassFish

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-304?page=all ] Gavin King updated JBSEAM-304: ------------------------------ Fix Version/s: 1.1.0.GA (was: 1.1.0.CR1) Description: Roger Kitain has contributed deploy script stuff for GlassFish. (We won't have a generic deploy target, since glassfish requires the awful ejb-link stuff.) (was: Roger Kitain has contributed deploy script stuff for GlassFish.) Priority: Critical (was: Major) What we really need is a "glassfish" example. Hopefully Michael can put one together. > Deploy targets for GlassFish > ---------------------------- > > Key: JBSEAM-304 > URL: http://jira.jboss.com/jira/browse/JBSEAM-304 > Project: JBoss Seam > Issue Type: Feature Request > Components: Examples > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.GA > > > Roger Kitain has contributed deploy script stuff for GlassFish. (We won't have a generic deploy target, since glassfish requires the awful ejb-link stuff.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-395?page=all ] Gavin King updated JBSEAM-395: ------------------------------ Fix Version/s: 1.1.1.GA (was: 1.1.0.CR1) I will slip it, we need this release. > Alternate "dispatcher" strategies > --------------------------------- > > Key: JBSEAM-395 > URL: http://jira.jboss.com/jira/browse/JBSEAM-395 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.1.GA > > > Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-293) Add well defined precedence for component overriding with the same name.

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-293?page=all ] Gavin King updated JBSEAM-293: ------------------------------ Fix Version/s: 1.1.1.GA (was: 1.1.0.CR1) slip! > Add well defined precedence for component overriding with the same name. > ------------------------------------------------------------------------ > > Key: JBSEAM-293 > URL: http://jira.jboss.com/jira/browse/JBSEAM-293 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.1 > Reporter: Jason Long > Assigned To: Gavin King > Fix For: 1.1.1.GA > > Attachments: SEAM-293-doc-patch.txt, SEAM-293-patch.txt > > > Add well defined precidence for component overriding with the same name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-432) Support @IfInvalid functionality without @IfInvalid

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-432?page=all ] Gavin King updated JBSEAM-432: ------------------------------ Fix Version/s: 1.1.0.CR1 Assignee: Gavin King > Support @IfInvalid functionality without @IfInvalid > --------------------------------------------------- > > Key: JBSEAM-432 > URL: http://jira.jboss.com/jira/browse/JBSEAM-432 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Christian Bauer > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > > The "Previous Page" button has to Update Model Values, but not Process Validations: > <h:form> > <f:facet name="beforeInvalidField"> > <h:graphicImage value="/img/attention.gif" > width="18" height="18" > styleClass="attentionImage"/> > </f:facet> > <f:facet name="afterInvalidField"> > <s:message/> > </f:facet> > <f:facet name="aroundInvalidField"> > <s:span styleClass="errors"/> > </f:facet> > <div class="errors" align="center"> > <h:messages globalOnly="true"/> > </div> > <s:validateAll> > <div class="entry"> > <div class="label">#{messages['Firstname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.firstname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Lastname']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.lastname}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label">#{messages['Email']}:</div> > <div class="input"> > <s:decorate> > <h:inputText size="32" required="true" > value="#{register.user.email}"/> > </s:decorate> > </div> > </div> > <div class="entry"> > <div class="label"> </div> > <div class="input"> > <h:commandButton value="#{messages['PrevPage']}" styleClass="button" > action="register"/> > <h:commandButton value="#{messages['NextPage']}" styleClass="button" > action="#{register.enterProfile}"/> > </div> > </div> > </s:validateAll> > </h:form> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-374) Normalize the event model

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-374?page=all ] Gavin King updated JBSEAM-374: ------------------------------ Fix Version/s: 1.1.1.GA (was: 1.1.0.CR1) slip > Normalize the event model > ------------------------- > > Key: JBSEAM-374 > URL: http://jira.jboss.com/jira/browse/JBSEAM-374 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.1.GA > > > Currently some events can be handled by either an @Observer method, or a method binding in events.xml. Ideally we would like this to be true for ALL events, but for now our integration with JSF and jBPM is not quite that deep. Nevertheless, there are some things we could do to allow a more consistent model where everything can be handled by either a method binding or an annotated method: > (1) Rebuild the page actions functionality on top of the Seam event bus - defining standard org.jboss.seam.page.<viewId> events that can be handled via @Observer("org.jboss.seam.page./myViewId.xhtml") > (2) Introduce "outcome observers" for JSF: if I have <h:commandButton action="myOutcome"/>, allow us to handle it using @Observer("org.jboss.seam.outcome.myOutcome") > (3) Ditto for jBPM: if I have <transition name="myTransition" ... />, allow us to handle it using @Observer("org.jboss.seam.transition.myTransition") > (4) Finally, introduce annotations layered over @Observer: @RenderPage("/myViewId.xhtml"), @Outcome("myOutcome"), @Transition("myTransition") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-426) Stateful bean destruction wants extended EM to join a transaction and fails

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-426?page=all ] Gavin King closed JBSEAM-426. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done Assignee: Gavin King this was already fixed. > Stateful bean destruction wants extended EM to join a transaction and fails > --------------------------------------------------------------------------- > > Key: JBSEAM-426 > URL: http://jira.jboss.com/jira/browse/JBSEAM-426 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Christian Bauer > Assigned To: Gavin King > Fix For: 1.1.0.BETA2 > > > @Name("register") > @Scope(ScopeType.CONVERSATION) > @Stateful > public class RegisterBean implements Register { > @In > private User currentUser; > @In(create = true) > private EntityManager caveatEmptorEM; > @In(create=true) > private transient FacesMessages facesMessages; > private String verifyPassword; > public String getVerifyPassword() { > return verifyPassword; > } > public void setVerifyPassword(String verifyPassword) { > this.verifyPassword = verifyPassword; > } > @Begin(join = true, flushMode = FlushModeType.MANUAL) > public String enterAccount() { > System.out.println("################### FLUSHMODE" + > ((HibernateEntityManager)caveatEmptorEM).getSession().getFlushMode()); > if ( > verifyPasswordMismatch(currentUser.getPassword()) > || > usernameExists(currentUser.getUsername()) > ) { > return null; // Redisplay page > } else { > return "profile"; > } > } > @IfInvalid(outcome = Outcome.REDISPLAY) > public String enterProfile() { > return "confirm"; > } > @End > public String doRegister() { > System.out.println("################### FLUSHMODE" + > ((HibernateEntityManager)caveatEmptorEM).getSession().getFlushMode()); // This is also wrong, different issue > if ( usernameExists(currentUser.getUsername()) ) > return "register"; > caveatEmptorEM.persist(currentUser); > caveatEmptorEM.flush(); > // Remove the "currentUser" from the session context. This is a detached object > // after this method returns. We don't want it to leak into the next conversation! > Contexts.getSessionContext().remove("currentUser"); > facesMessages > .addFromResourceBundle("SuccessfulRegistration"); > return "login"; > } > @Remove @Destroy > public void destroy() {} > ... > } > Exception during @Destroy: > 00:03:34,505 DEBUG [org.jboss.seam.contexts.Contexts] destroying: conversation > 00:03:34,505 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preDestroy.conversation > 00:03:34,505 DEBUG [org.jboss.seam.contexts.Contexts] destroying: register > 00:03:34,505 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preDestroy.register > 00:03:34,506 DEBUG [org.jboss.seam.Component] trying to inject with hierarchical context search: caveatEmptorEM > 00:03:34,506 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: caveatEmptorEM > 00:03:34,507 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} > 00:03:34,507 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preRemoveVariable.register > 00:03:34,507 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postRemoveVariable.register > 00:03:34,507 DEBUG [org.jboss.seam.interceptors.RemoveInterceptor] Stateful component was removed: register > 00:03:34,508 WARN [org.jboss.seam.contexts.Contexts] Could not destroy component: register > javax.ejb.EJBException: java.lang.IllegalStateException: EntityManager is closed > at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) > ... > Caused by: java.lang.IllegalStateException: EntityManager is closed > at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java:42) > at org.hibernate.ejb.AbstractEntityManagerImpl.joinTransaction(AbstractEntityManagerImpl.java:447) > at org.hibernate.ejb.AbstractEntityManagerImpl.joinTransaction(AbstractEntityManagerImpl.java:442) > at org.jboss.seam.core.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:91) > at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.seam.util.Reflections.invoke(Reflections.java:17) > at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:101) > at org.jboss.seam.Component.callComponentMethod(Component.java:1642) > at org.jboss.seam.Component.unwrap(Component.java:1663) > at org.jboss.seam.Component.getInstance(Component.java:1501) > at org.jboss.seam.Component.getInstance(Component.java:1461) > at org.jboss.seam.Component.getInstanceToInject(Component.java:1688) > at org.jboss.seam.Component.injectFields(Component.java:1218) > at org.jboss.seam.Component.inject(Component.java:988) > at org.jboss.seam.interceptors.BijectionInterceptor.bijectTargetComponent(BijectionInterceptor.java:48) > I can't make the doRegister() method @End @Remove @Destroy, it throws exceptions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-196) search box

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-196?page=all ] Gavin King closed JBSEAM-196. ----------------------------- Resolution: Won't Fix I doubt I will ever implement this :) > search box > ---------- > > Key: JBSEAM-196 > URL: http://jira.jboss.com/jira/browse/JBSEAM-196 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Priority: Optional > > Create a JSF component for search box which submits its value as a request parameter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006