November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-484) Repackage built-in components

by Gavin King (JIRA)

Repackage built-in components ----------------------------- Key: JBSEAM-484 URL: http://jira.jboss.com/jira/browse/JBSEAM-484 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.0.CR1 get rid of the list of classes in addComponents() move debug components to debug jar get rid of special casing in Scanner add @Name("foo", scannerIgnore=true) -- 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

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-456) Interceptor tries to access UserTransaction interface, but this is not allowed for CMT

by Guy Veraghtert (JIRA)

Interceptor tries to access UserTransaction interface, but this is not allowed for CMT -------------------------------------------------------------------------------------- Key: JBSEAM-456 URL: http://jira.jboss.com/jira/browse/JBSEAM-456 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.BETA1 Environment: Glassfish Reporter: Guy Veraghtert In method getEntityManager() in class ManagedPersistenceContext a call is made to the UserTransaction interface: isActive(). According to the EJB 3.0 specification (p.81) this is not allowed for CMT. Seam requires the usage of CMT. (Occurs when adding @In to an entityManager-field, according to seam doc 11.4). Patched locally in class ManagedPersistenceContext : @Unwrap public EntityManager getEntityManager() throws NamingException, SystemException { if ( !Lifecycle.isDestroying() /*&& Transactions.isTransactionActive()*/ ) { try { entityManager.joinTransaction(); } catch (TransactionRequiredException e) { } } return entityManager; } -- 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

3
12
0 / 0

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

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-304?page=all ] Gavin King reassigned JBSEAM-304: --------------------------------- Assignee: Michael Yuan (was: Gavin King) > 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: Michael Yuan > 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] Created: (JBSEAM-511) @Begin during a nested conversation that has ended

by Gavin King (JIRA)

@Begin during a nested conversation that has ended -------------------------------------------------- Key: JBSEAM-511 URL: http://jira.jboss.com/jira/browse/JBSEAM-511 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.BETA2, 1.1.0.BETA1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 This was not welldefined. @Begin(join=true) should be a no-op in this case @Begin(nested=true) should cause an exception -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-385) @In(create=true) is noisy for persistence contexts

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-385?page=all ] Gavin King closed JBSEAM-385. ----------------------------- Resolution: Done Done. Now no longer needed for any built-in component, or any component marked auto-create=true. > @In(create=true) is noisy for persistence contexts > -------------------------------------------------- > > Key: JBSEAM-385 > URL: http://jira.jboss.com/jira/browse/JBSEAM-385 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > > I hate seeing: @In(create=true) EntityManager em everywhere. > Perhaps we need some kind of @Startup component for conversation scope? -- 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-385) @In(create=true) is noisy for persistence contexts

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-385?page=all ] Gavin King updated JBSEAM-385: ------------------------------ Fix Version/s: 1.1.0.CR1 We now need to introduce a generic autoCreate setting. > @In(create=true) is noisy for persistence contexts > -------------------------------------------------- > > Key: JBSEAM-385 > URL: http://jira.jboss.com/jira/browse/JBSEAM-385 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > > I hate seeing: @In(create=true) EntityManager em everywhere. > Perhaps we need some kind of @Startup component for conversation scope? -- 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] Created: (JBSEAM-493) join=true|false, pageflow="..." for <begin-conversation>

by Gavin King (JIRA)

join=true|false, pageflow="..." for <begin-conversation> -------------------------------------------------------- Key: JBSEAM-493 URL: http://jira.jboss.com/jira/browse/JBSEAM-493 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.CR1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 <begin-conversation> should have the same options as @Begin furthermore, <end-conversation> should have the same options as @End -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-509) JSF phase events

by Gavin King (JIRA)

JSF phase events ---------------- Key: JBSEAM-509 URL: http://jira.jboss.com/jira/browse/JBSEAM-509 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.CR1 Raise Seam events for the JSF lifecycle. Also introduce jBPM event types for pageflow: <page name="edit" view-id="/editCustomer.xhtml"> <event type="invoke-application"> <action expression="customerHome.update"/> </event> </page> This is something like a page action, but supports other lifecycle phases. -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-259) Builtin components defined in builtin-components.xml

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-259?page=all ] Gavin King closed JBSEAM-259. ----------------------------- Resolution: Done Done, all built-in components have moved to proper namespaces. > Builtin components defined in builtin-components.xml > ---------------------------------------------------- > > Key: JBSEAM-259 > URL: http://jira.jboss.com/jira/browse/JBSEAM-259 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > > Instead of code in the Initialization class, we should register builtin components in an XML file. -- 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-381) instance-per-nested-conversation components

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-381?page=all ] Gavin King closed JBSEAM-381. ----------------------------- Resolution: Done > instance-per-nested-conversation components > ------------------------------------------- > > Key: JBSEAM-381 > URL: http://jira.jboss.com/jira/browse/JBSEAM-381 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.CR1 > > > Especially for the "pageflow" built-in component, we need to be able to specify that a component has an instance per nested conversation. This could be addressed as a new scope (NESTED_CONVERSATION), or it could be a tweak on CONVERSATION scoped components. -- 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