March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-979) Seam scan's for pageflows on startup

by Pete Muir (JIRA)

Seam scan's for pageflows on startup ------------------------------------ Key: JBSEAM-979 URL: http://jira.jboss.com/jira/browse/JBSEAM-979 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Core Affects Versions: 1.2.0.GA Reporter: Pete Muir -- 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

17 years, 10 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2660) Rename exception context variables

by Gavin King (JIRA)

Rename exception context variables ---------------------------------- Key: JBSEAM-2660 URL: http://jira.jboss.com/jira/browse/JBSEAM-2660 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.1.GA, 2.0.0.GA Reporter: Gavin King Priority: Blocker Fix For: 2.0.2.GA, 2.1.0.GA We have a name collision on the name "org.jboss.seam.exception", we need to use the names: org.jboss.seam.exception.caughtException org.jboss.seam.exception.handledException in the Exceptions component and the debug page. -- 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

17 years, 10 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2769) Implement Dynamic permission resolver for Seam Security

by Shane Bryzak (JIRA)

Implement Dynamic permission resolver for Seam Security ------------------------------------------------------- Key: JBSEAM-2769 URL: http://jira.jboss.com/jira/browse/JBSEAM-2769 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.1.0.BETA1 We need a permission resolver for resolving role -> permission assigned permissions. They should be based on a PermissionStore similar to how we have an IdentityStore for identity management. We also need the management components for managing these permissions. -- 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

17 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2784) Backport of Alex's code about portlet support (From 2.1.0.A1)

by Thomas Heute (JIRA)

Backport of Alex's code about portlet support (From 2.1.0.A1) ------------------------------------------------------------- Key: JBSEAM-2784 URL: http://jira.jboss.com/jira/browse/JBSEAM-2784 Project: JBoss Seam Issue Type: Feature Request Components: Portal Reporter: Thomas Heute Assigned To: Pete Muir Priority: Blocker As per our discussion, we would like to have the JBoss Portlet Bridge being able to work with Seam 2.0.2.GA. Hopefully you know what's needed to be backported. Thanks ! -- 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

17 years, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2720) expose overrideable createRequest() and createResponse() methods in AbstractSeamTest.Request

by Matt Drees (JIRA)

expose overrideable createRequest() and createResponse() methods in AbstractSeamTest.Request -------------------------------------------------------------------------------------------- Key: JBSEAM-2720 URL: http://jira.jboss.com/jira/browse/JBSEAM-2720 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Reporter: Matt Drees Priority: Minor There are times when I'd like to substitute my own HttpServletResponse implementation in a SeamTest request. I might do this if I want to allow getOutputStream() to return a real output stream, so I can test actions that directly write to it (excel document generation, for example). It'd be handy if AbstractSeamTest made it convenient for me to do this; right now I'm relying on reflection tricks to get & set the private field. -- 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

17 years, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2758) Update WebSphere chapter with a note about Seam specific EJB's

by Jay Balunas (JIRA)

Update WebSphere chapter with a note about Seam specific EJB's -------------------------------------------------------------- Key: JBSEAM-2758 URL: http://jira.jboss.com/jira/browse/JBSEAM-2758 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor See comment on websphere blog for more details. http://in.relation.to/Bloggers/WebSphereRunningSeamsJEE5BookingExample#co... Basically just differentiate Seam internal EJBs from example EJBs so that users know that they are needed in any of there apps - not just the examples. -- 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

17 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2482) Possible work around for Weblogic "varargs" EJB issue

by Jay Balunas (JIRA)

Possible work around for Weblogic "varargs" EJB issue ----------------------------------------------------- Key: JBSEAM-2482 URL: http://jira.jboss.com/jira/browse/JBSEAM-2482 Project: JBoss Seam Issue Type: Task Components: Documentation, Examples Affects Versions: 2.0.1.CR1 Reporter: Jay Balunas Priority: Minor Attachments: full-stack-of-ejb-transient-error.txt There is a know issue with weblogic and support for EJBs that use variable arguments. This is documented in the reference guide for more details. I've attached the full stack trace from the console. The main errors revolve around EJB3 timers - there may be a way to disable timers through the weblogic.xml deployment descriptor, or perhaps a different file. There are other warnings around EJB synchronization, but they may still function. If solved the reference docs should be updated. -- 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

17 years, 10 months

3
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2491) Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released

by Marcus Adair (JIRA)

Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released ----------------------------------------------------------------- Key: JBSEAM-2491 URL: http://jira.jboss.com/jira/browse/JBSEAM-2491 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.1.CR1 Reporter: Marcus Adair According to the groovy-all.jar/META-INF/MANIFEST.MF file, Groovy 1.1 beta is still be used. 1.5 was released in 12/2007 and appears to solve some gotchas related to its use with Seam. See: http://docs.codehaus.org/display/GROOVY/2007/12/07/Groovy+1.5+released -- 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

17 years, 10 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2657) Seam-mail fails when invoked from custom servlet bound with web:context-filter

by Przemyslaw Jaskierski (JIRA)

Seam-mail fails when invoked from custom servlet bound with web:context-filter ------------------------------------------------------------------------------ Key: JBSEAM-2657 URL: http://jira.jboss.com/jira/browse/JBSEAM-2657 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Environment: Seam 2.0.1 and 2.0.2-SNAPSHOT from 13 feb 2008, plain Tomcat 6.0, JSF RI 1.2_07. Reporter: Przemyslaw Jaskierski (Reporting as FR as requested by Pete. Please, read linked thread for the full context). I try to send an email from one of services. The same code: renderer.render(/WEB-INF/emailTemplates/test.xhtml); invoked from application-scoped component with method annotated as @Observer(foo) 1. works when a synchronous event is invoked in JSF action using Events.instance().raiseEvent(foo) 2. fails when invoked using Events.instance().raiseAsynchronousEvent(foo) from the same JSF action 3. fails when invoked as both synchronous and asynchronous events from custom servlet bound with web:context-filter. Case 2. and 3. both lead to this exception: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) at org.jboss.seam.mock.MockFacesContext.<init>(MockFacesContext.java:60) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.init(FaceletsRenderer.java:95) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.run(FaceletsRenderer.java:77) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:169) Pete's response: (2) is untested and I wouldn't necessarily expect (3) to work. File a JIRA feature request for (3) please - but it will require some redesign on how we render mails (hopefully make it much more robust) -- 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

17 years, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1946) seam 2.0's persistence:managed-persistence-context not support openjpa

by clf clf (JIRA)

seam 2.0's persistence:managed-persistence-context not support openjpa ---------------------------------------------------------------------- Key: JBSEAM-1946 URL: http://jira.jboss.com/jira/browse/JBSEAM-1946 Project: JBoss Seam Issue Type: Bug Components: Core Environment: tomacat 6+ myfaces 1.2.0 + seam 2.0 ga+ spring 2.0.6 + openjpa 0.9.7 Reporter: clf clf I try to test the Seam's compatibility with openjpa. The web project is tomacat + myfaces + seam + spring jpa + openjpa. I define entityManagerFactory in the application.xml [code]  <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="dataSource" ref="dataSource"/> <property name="loadTimeWeaver"> <bean class="org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver"/> </property> <property name="jpaVendorAdapter">   <bean id="jpaAdapter" class="org.springframework.orm.jpa.vendor.OpenJpaVendorAdapter"> <property name="database" value="HSQL"/> <property name="showSql" value="true"/> </bean> </property> </bean> [/code] And Define managed-persistence-context in component.xml [code] <persistence:managed-persistence-context name="courseEntityManager" entity-manager-factory="#{entityManagerFactory}" auto-create="true" /> [/code] The Web Project reports Error [code] 2007-09-21 09:21:09,981 ERROR [org.jboss.seam.jsf.SeamPhaseListener] - <uncaught exception> java.lang.RuntimeException: could not proxy delegate at org.jboss.seam.persistence.HibernatePersistenceProvider.proxyDelegate(HibernatePersistenceProvider.java:102) Caused by: java.lang.ClassCastException: org.apache.openjpa.persistence.EntityManagerImpl at org.jboss.seam.persistence.HibernatePersistenceProvider.proxyDelegate(HibernatePersistenceProvider.java:98) [/code] I also test seam with toplink and hibernate,and find toplink fail,hibernate success It seems to me that seam's persistence:managed-persistence-context only supports hibernate as entity-manager-factory and not supports other jpa implementation. -- 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

17 years, 10 months

4
18
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 March 2008