April 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5091) SeamInterceptor doesn't work on EJB @Schedule methods

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5091: ------------------------------------- Summary: SeamInterceptor doesn't work on EJB @Schedule methods Key: JBSEAM-5091 URL: https://issues.jboss.org/browse/JBSEAM-5091 Project: Seam 2 Issue Type: Bug Components: EJB3 Affects Versions: 2.3.0.Final Reporter: Marek Schmidt Fix For: 2.3.1.CR1 Description of problem: Having a @Scope(ScopeType.APPLICATION) @Singleton @Name("statistics") public class Statistics { @In(create=true) Foo foo; @Schedule(hour="*", minute="*", second="*/10", info="every tenth") public void generateReport(Timer timer) { // do stuff with foo } } gets NullPointerException accessing "foo". Seam interceptors doesn't seem to work on time-out methods. The problem seems to be that the SessionBeanInterceptor doesn't implement the @AroundTimeout method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5090) Seam Text documentation falsely claims that forward slash creates italics

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5090?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5090. --------------------------------- Resolution: Done fixed by correcting Seam documentation and iText demo source > Seam Text documentation falsely claims that forward slash creates italics > ------------------------------------------------------------------------- > > Key: JBSEAM-5090 > URL: https://issues.jboss.org/browse/JBSEAM-5090 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Reporter: Ron Šmeral > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam Text [documentation|http://docs.jboss.org/seam/latest/reference/en-US/html_sing...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: > {panel} > {code} > You /must/ have some text following a heading! > {code} > HTML result: > {code} > You must have some text following a heading! > {code} > {panel} > which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). > The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5072) Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5072: ------------------------------------------------- Luan Cestari <lcestari(a)redhat.com> made a comment on [bug 904174|https://bugzilla.redhat.com/show_bug.cgi?id=904174] Hi Marek, In InitilizeTimers class he used Seam API to find or create the timers ( Component.getInstance(nme, true, true)). About using the JNDI, I remember that we tried but it didn`t work as well. I Also talked with a guy from SEG that confirmed about TCCL. Regards, Luan > Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context > -------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-5072 > URL: https://issues.jboss.org/browse/JBSEAM-5072 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final > Reporter: Luan Cestari > > Description of problem: > Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context. In other words, Seam can`t find the beans in context, even that they are there (due the annotations and logs that confirm that). > EAP 6`s documentation that gives the steps to migrate Seam 2 applications: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati... > Version-Release number of selected component (if applicable): > Seam 2.2 in EAP 6 > How reproducible: > Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will lookup for Seam/Quartz bean, but can`t find it. > Actual results: > Can`t find the bean > Expected results: > Find the bean > Additional info: > salesforce link: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc.ove... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5090) Seam Text documentation falsely claims that forward slash creates italics

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5090?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5090: ---------------------------------- Summary: Seam Text documentation falsely claims that forward slash creates italics (was: CLONE - Seam Text documentation falsely claims that forward slash creates italics) Fix Version/s: 2.3.1.CR1 > Seam Text documentation falsely claims that forward slash creates italics > ------------------------------------------------------------------------- > > Key: JBSEAM-5090 > URL: https://issues.jboss.org/browse/JBSEAM-5090 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Reporter: Ron Šmeral > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam Text [documentation|http://docs.jboss.org/seam/latest/reference/en-US/html_sing...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: > {panel} > {code} > You /must/ have some text following a heading! > {code} > HTML result: > {code} > You must have some text following a heading! > {code} > {panel} > which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). > The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5090) CLONE - Seam Text documentation falsely claims that forward slash creates italics

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5090?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5090: ---------------------------------- Description: Seam Text [documentation|http://docs.jboss.org/seam/latest/reference/en-US/html_sing...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: {panel} {code} You /must/ have some text following a heading! {code} HTML result: {code} You must have some text following a heading! {code} {panel} which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. was: Seam Text [documentation|http://documentation-devel.engineering.redhat.com/docs/en-U...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: {panel} {code} You /must/ have some text following a heading! {code} HTML result: {code} You must have some text following a heading! {code} {panel} which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. > CLONE - Seam Text documentation falsely claims that forward slash creates italics > --------------------------------------------------------------------------------- > > Key: JBSEAM-5090 > URL: https://issues.jboss.org/browse/JBSEAM-5090 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Reporter: Ron Šmeral > Assignee: Marek Novotny > > Seam Text [documentation|http://docs.jboss.org/seam/latest/reference/en-US/html_sing...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: > {panel} > {code} > You /must/ have some text following a heading! > {code} > HTML result: > {code} > You must have some text following a heading! > {code} > {panel} > which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). > The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5090) CLONE - Seam Text documentation falsely claims that forward slash creates italics

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5090?page=com.atlassian.jira.plugi... ] Marek Novotny moved JBPAPP-10715 to JBSEAM-5090: ------------------------------------------------ Project: Seam 2 (was: JBoss Enterprise Application Platform 4 and 5) Key: JBSEAM-5090 (was: JBPAPP-10715) Workflow: GIT Pull Request workflow (was: jira) Component/s: Documentation Issues (was: Documentation) (was: Seam2) Security: (was: Public) Docs QE Status: (was: NEW) > CLONE - Seam Text documentation falsely claims that forward slash creates italics > --------------------------------------------------------------------------------- > > Key: JBSEAM-5090 > URL: https://issues.jboss.org/browse/JBSEAM-5090 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Reporter: Ron Šmeral > Assignee: Marek Novotny > > Seam Text [documentation|http://documentation-devel.engineering.redhat.com/docs/en-U...] currently contains several code examples that show that the forward slash is translated into HTML italics tag , like the following: > {panel} > {code} > You /must/ have some text following a heading! > {code} > HTML result: > {code} > You must have some text following a heading! > {code} > {panel} > which does not work, since this is not even included in the Seam Text grammar file, which defines only the star ( * ) as the symbol for emphasis (translated into italics). > The examples in the documentation need to be fixed, and this also affects the Seam iText example and its HTML Conversion feature, which uses Seam Text and includes a text with the forward slashes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5086) localization settings via component.xml doesn't work

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5086. --------------------------------- Assignee: Marek Novotny Resolution: Deferred I marked it as Deferred, because order of WAR initialization is not in Seam full competences, but rather application or container competences. The scanning order of WAR from application point of view can be managed only in web.xml. Loading of the listener _com.sun.faces.config.ConfigureListener_ is done from existence of the Tag Library Definition in WAR or from the _javax.servlet.ServletContainerInitializer_. Adding _com.sun.faces.config.ConfigureListener_ before _org.jboss.seam.SeamListener_ is just emphasing that we need to have initialized Mojarra before we do Seam initialization, because there are Seam components which rely on initialized JSF environment. > localization settings via component.xml doesn't work > ---------------------------------------------------- > > Key: JBSEAM-5086 > URL: https://issues.jboss.org/browse/JBSEAM-5086 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.0.Final > Reporter: Tomas Remes > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Adding following snippet to components.xml does not work as expected: > <inter:locale-config default-locale="cs" supported-locales="en cs"/> > And it produces following message in server log after application deployment: > "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." > If you check class org.jboss.seam.international.LocaleConfig.java and its initLocaleConfig() method, then you'll notice that application variable resolves always to null in this case, therefore the locales are never set correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5086) localization settings via component.xml doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5086: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> made a comment on [bug 903177|https://bugzilla.redhat.com/show_bug.cgi?id=903177] Real issue here is the order of Mojarra initialization in WAR. Everytime you see the following error message "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." you are experiencing different order of applicaiton initialization than Seam and your web application will expect. If correct order is processed you couldn't see that error at all. Correct order is when Mojarra is initialized before Seam is processing configuration. The only working way now is to specify com.sun.faces.config.ConfigureListener in web.xml before org.jboss.seam.servlet.SeamListener configuration to strictly get such order AFAIK. > localization settings via component.xml doesn't work > ---------------------------------------------------- > > Key: JBSEAM-5086 > URL: https://issues.jboss.org/browse/JBSEAM-5086 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.0.Final > Reporter: Tomas Remes > Fix For: 2.3.1.CR1 > > > Adding following snippet to components.xml does not work as expected: > <inter:locale-config default-locale="cs" supported-locales="en cs"/> > And it produces following message in server log after application deployment: > "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." > If you check class org.jboss.seam.international.LocaleConfig.java and its initLocaleConfig() method, then you'll notice that application variable resolves always to null in this case, therefore the locales are never set correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5086) localization settings via component.xml doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5086: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> made a comment on [bug 903177|https://bugzilla.redhat.com/show_bug.cgi?id=903177] Edited release note and inserted it into the 2.2.0 RN book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_F... Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-23 > localization settings via component.xml doesn't work > ---------------------------------------------------- > > Key: JBSEAM-5086 > URL: https://issues.jboss.org/browse/JBSEAM-5086 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.0.Final > Reporter: Tomas Remes > Fix For: 2.3.1.CR1 > > > Adding following snippet to components.xml does not work as expected: > <inter:locale-config default-locale="cs" supported-locales="en cs"/> > And it produces following message in server log after application deployment: > "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." > If you check class org.jboss.seam.international.LocaleConfig.java and its initLocaleConfig() method, then you'll notice that application variable resolves always to null in this case, therefore the locales are never set correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5085) Pages rewrite doesn't rewrite s:link params

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5085?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5085: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> made a comment on [bug 928002|https://bugzilla.redhat.com/show_bug.cgi?id=928002] Edited release note and inserted it into the 2.2.0 RN book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_F... Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-23 > Pages rewrite doesn't rewrite s:link params > ------------------------------------------- > > Key: JBSEAM-5085 > URL: https://issues.jboss.org/browse/JBSEAM-5085 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Reporter: Marek Novotny > Fix For: 2.3.1.CR1 > > > Having this in the pages.xml: > <page view-id="/entry.xhtml"> > <rewrite pattern="/entry/{blogEntryId}" /> > <rewrite pattern="/entry" /> > > <param name="blogEntryId" > value="#{blogEntry.id}"/> > > <action execute="#{entryAction.loadBlogEntry(blogEntry.id)}"/> > </page> > and a link to entry in a page: > <s:link id="link" view="/entry.xhtml" propagation="none" value="#{blogEntry.title}"> > <f:param name="blogEntryId" value="#{blogEntry.id}"/> > </s:link> > this should render as a link to "/entry/foo", but it renders as "/entry?blogEntryId=roadmap11" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2013