July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3152) Remoting does not work with qualified component names

by Dan Allen (JIRA)

Remoting does not work with qualified component names ----------------------------------------------------- Key: JBSEAM-3152 URL: http://jira.jboss.com/jira/browse/JBSEAM-3152 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.3.GA, 2.1.0.BETA1 Remoting does not escape dots in a component name, thus generating JavaScript that does not run. For instance, if the name of the component is com.example.remoting.componentName, the InterfaceGenerator produces: Seam.Remoting.type.com.mydomain.throwaway.manager.prototype.methodName = ... Obviously, this isn't going to work. A reasonable quick fix is to replace dots with underscores. -- 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

16 years, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3102) Hibernate query at startup

by ricardo campos (JIRA)

Hibernate query at startup -------------------------- Key: JBSEAM-3102 URL: http://jira.jboss.com/jira/browse/JBSEAM-3102 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: JBoss 4.2.2.GA, Seam 2.0.2.SP1 Reporter: ricardo campos I believe the problem I posted here to be an issue: http://www.seamframework.org/Community/HibernateQueryAtStartup I'm getting "java.lang.IllegalStateException: No active session context" when executing a Hibernate query in a @Startup Component... -- 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

16 years, 3 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3085) Renderer is only partially functional when used asynchronously

by Dan Allen (JIRA)

Renderer is only partially functional when used asynchronously -------------------------------------------------------------- Key: JBSEAM-3085 URL: http://jira.jboss.com/jira/browse/JBSEAM-3085 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Reporter: Dan Allen Fix For: 2.1.0.GA The Renderer, which is used to render Facelet templates, is partially crippled when used asynchronously. First of all, it throws an exception while setting up the MockFacesContext() because it tries to retrieve an Application from the real JSF FactoryFinder. That isn't going to work because JSF is not properly initialized. That leads to the second problem, which is that if the template has any JSF component tags, they aren't rendered because its not a real JSF environment. I think the solution is to use JSFUnit to emulate a JSF environment so that the Renderer can be used asynchronous. Otherwise, we cannot send email messages that use JSF components in the background. The second solution is to document that you cannot render JSF markup in your email if used asynchronously. This affects the /examples/mail demo application. -- 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

16 years, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2912) Translating Seam into your own language (sl-SI)

by Andrej Marolt (JIRA)

Translating Seam into your own language (sl-SI) ----------------------------------------------- Key: JBSEAM-2912 URL: http://jira.jboss.com/jira/browse/JBSEAM-2912 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: Andrej Marolt I would like to begin the process of translating Seam into Slovenian. (sl-SI) Language: Slovenian Locale: Slovenia -- 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

16 years, 3 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3192) Refer to enclosing class when enforcing @Restrict

by Pete Muir (JIRA)

Refer to enclosing class when enforcing @Restrict ------------------------------------------------- Key: JBSEAM-3192 URL: https://jira.jboss.org/jira/browse/JBSEAM-3192 Project: Seam Issue Type: Bug Components: Wicket Reporter: Pete Muir Fix For: 2.1.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3163) components.xml <property> parsing for sets

by Pete Muir (JIRA)

components.xml <property> parsing for sets ------------------------------------------ Key: JBSEAM-3163 URL: http://jira.jboss.com/jira/browse/JBSEAM-3163 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Assigned To: Norman Richards Priority: Critical Fix For: 2.1.0.BETA1 See the wiki tests for an example of this failing. -- 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

16 years, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2684) #{entityQuery.dataModel} returns empty model

by Alex Savitsky (JIRA)

#{entityQuery.dataModel} returns empty model -------------------------------------------- Key: JBSEAM-2684 URL: http://jira.jboss.com/jira/browse/JBSEAM-2684 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Alex Savitsky Priority: Critical When referenced from a JSF dataTable, a dataModel property from a conversation-scoped EntityQuery ALWAYS returns an empty model. The resultList property works normally, though. Placing the EntityQuery in session scope works, too. -- 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

16 years, 3 months

4
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3147) FacesMessage I18N keys are evaluated differently between "redirect" and "render" navigations

by Michael Youngstrom (JIRA)

FacesMessage I18N keys are evaluated differently between "redirect" and "render" navigations -------------------------------------------------------------------------------------------- Key: JBSEAM-3147 URL: http://jira.jboss.com/jira/browse/JBSEAM-3147 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.2.SP1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.3.GA When using FacesMessages.addFromResourceBundle() message resolution is deferred until after the phase it was added in. Though I'm not exactly sure why it is done this way it is causing problems with "render" vs "redirect" navigations. In the case of a "render" the Pages component changes the current viewID prior to the end of the phase. So when the FacesMessages component processes it's FacesMessages at the end of the phase the viewId is going to be different than what it would be for a "redirect". This can be a problem if you are using Seam Page bundles. IMO the message really should come from the page where the action was invoked not the destination page. If the FacesMessage component defers FacesMessage creation because it wants to do interpolation after the phase is complete perhaps we can change FacesMessages to immediately look up the message key and then lazily interpolate that message? I can go ahead and fix this if nobody has an objection. Mike -- 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

16 years, 3 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2978) SeamFramework Wiki Login following clicking onto "Link" results in "HTTP Status 400 - Missing parentNodeId parameter"

by Leonid Maslov (JIRA)

SeamFramework Wiki Login following clicking onto "Link" results in "HTTP Status 400 - Missing parentNodeId parameter" --------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2978 URL: http://jira.jboss.com/jira/browse/JBSEAM-2978 Project: Seam Issue Type: Bug Components: Wiki Environment: Firefox 2.0.0.14 Win XP Reporter: Leonid Maslov Assigned To: Christian Bauer Priority: Minor h3. Scenario: * Go to Seam Framework site * Ensure Your are not logged in * Open any forum item * Enter Your cedentials and click "Login" * See "Login successful, welcome <username>." message * Click on "Link" link near the forum item title. * *Page fails with _HTTP Status 400 - Missing parentNodeId parameter_* and current page is: http://www.seamframework.org/docDisplay_d.seam h3. Expected result: The page stays the same as forum item page and without errors -- 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

16 years, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1485) Configure Default Interceptors

by Bruno E. Grossi (JIRA)

Configure Default Interceptors ------------------------------ Key: JBSEAM-1485 URL: http://jira.jboss.com/jira/browse/JBSEAM-1485 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: Linux with only Tomcat, not JBoss Reporter: Bruno E. Grossi Create an configuration option to disable some default interceptors that there are never used, improving the application's performance. On some systems there are no necessity of some interceptors, for example, the transactional ones (RollbackInterceptor, TransactionInterceptor and ManagedEntityIdentityInterceptor) that degrade performance. -- 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

16 years, 3 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008