April 2013 - seam-issues - Jboss List Archives

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

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5086: ------------------------------------- Summary: 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 updated JBSEAM-5085: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=928002 > 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

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

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5085: ------------------------------------- Summary: 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

[JBoss JIRA] (JBSEAM-5084) seam-gen dependency management with ivy is not updated

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5084: ------------------------------------- Summary: seam-gen dependency management with ivy is not updated Key: JBSEAM-5084 URL: https://issues.jboss.org/browse/JBSEAM-5084 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.Final Reporter: Marek Novotny Fix For: 2.3.1.CR1 The seam-gen ivy setup is not totally updated and do not use Seam BOM. Version 2.3.0 of Ivy could manage the dependency management from Seam BOM. Old behavior of ivy extension is documented here http://in.relation.to/Bloggers/ManagingTheDependenciesOfASeamgenProjectWi... -- 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-5083) SeamViewHandler adds conversation id even if conversation is not long running

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBSEAM-5083: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=921660 > SeamViewHandler adds conversation id even if conversation is not long running > ----------------------------------------------------------------------------- > > Key: JBSEAM-5083 > URL: https://issues.jboss.org/browse/JBSEAM-5083 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam adds a conversation id even if the conversation is not long running into URL. > Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- 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-5083) SeamViewHandler adds conversation id even if conversation is not long running

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5083. ----------------------------------- Resolution: Done fixed by changed the condition for adding conversation id. > SeamViewHandler adds conversation id even if conversation is not long running > ----------------------------------------------------------------------------- > > Key: JBSEAM-5083 > URL: https://issues.jboss.org/browse/JBSEAM-5083 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam adds a conversation id even if the conversation is not long running into URL. > Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- 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-5083) SeamViewHandler adds conversation id even if conversation is not long running

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5083: ------------------------------------- Summary: SeamViewHandler adds conversation id even if conversation is not long running Key: JBSEAM-5083 URL: https://issues.jboss.org/browse/JBSEAM-5083 Project: Seam 2 Issue Type: Bug Components: JSF Integration Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.1.CR1 Seam adds a conversation id even if the conversation is not long running into URL. Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- 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-5082) seam-gen generated JUnitSeamTest deployment should use org.jboss.seam.mock.MockSeamListener instead of the SeamListener

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5082?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5082. ----------------------------------- Resolution: Done resolved by adding web-test.xml for using MockSeamListener > seam-gen generated JUnitSeamTest deployment should use org.jboss.seam.mock.MockSeamListener instead of the SeamListener > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-5082 > URL: https://issues.jboss.org/browse/JBSEAM-5082 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Per documentation http://docs.jboss.org/seam/latest/reference/en-US/html_single/#testfrmwk-... > MockSeamListener should be used for SeamTest arquillian tests, instead of the "real" SeamListener. > The SeamTest template should be modified to use a test-only web.xml with MockSeamListener configured. -- 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-5082) seam-gen generated JUnitSeamTest deployment should use org.jboss.seam.mock.MockSeamListener instead of the SeamListener

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5082: ------------------------------------- Summary: seam-gen generated JUnitSeamTest deployment should use org.jboss.seam.mock.MockSeamListener instead of the SeamListener Key: JBSEAM-5082 URL: https://issues.jboss.org/browse/JBSEAM-5082 Project: Seam 2 Issue Type: Bug Affects Versions: 2.3.0.Final Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.1.CR1 Per documentation http://docs.jboss.org/seam/latest/reference/en-US/html_single/#testfrmwk-... MockSeamListener should be used for SeamTest arquillian tests, instead of the "real" SeamListener. The SeamTest template should be modified to use a test-only web.xml with MockSeamListener configured. -- 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-5081) Upgrade Hibernate Search version to latest final 4.2.0.Final

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5081: ------------------------------------- Summary: Upgrade Hibernate Search version to latest final 4.2.0.Final Key: JBSEAM-5081 URL: https://issues.jboss.org/browse/JBSEAM-5081 Project: Seam 2 Issue Type: Bug Components: Build Reporter: Marek Novotny Priority: Critical Fix For: 2.3.1.CR1 Update latest versions through org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final BOM -- 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