January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-274) More flexible mapping of URLs to view ids

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=all ] Norman Richards updated JBSEAM-274: ----------------------------------- Fix Version/s: 2.1.0.GA (was: 2.0.2.GA) > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assigned To: Norman Richards > Fix For: 2.1.0.GA > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2194) Terrible error message for DTD not found when reading *.xml config file

by Scott Bader (JIRA)

Terrible error message for DTD not found when reading *.xml config file ----------------------------------------------------------------------- Key: JBSEAM-2194 URL: http://jira.jboss.com/jira/browse/JBSEAM-2194 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR3 Environment: Eclipse 3.3 JBoss 4.2.2 Reporter: Scott Bader Priority: Minor Problem experienced when application was reading login.page.xml file, but it could potentially happen anywhere when reading an XML file where DTD is not found. Seeing debug page with: Exception during request processing: Caused by java.lang.RuntimeException with message: "org.dom4j.DocumentException: jboss.com Nested exception: jboss.com" Stacktrace snippet: org.dom4j.DocumentException: jboss.com Nested exception: jboss.com at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:343) at org.jboss.seam.util.XML.getRootElement(XML.java:21) at org.jboss.seam.navigation.Pages.getDocumentRoot(Pages.java:950) ... Nested exception: java.net.UnknownHostException: jboss.com at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.Socket.connect(Socket.java:519) Recommend added error handling in org.jboss.seam.util.XML.getRootElement method or better yet org.jboss.seam.navigation.Pages.getDocumentRoot method and log the problem there. -- 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, 11 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2547) Seam remoting cannot decode Collection objects correctly

by P C (JIRA)

Seam remoting cannot decode Collection objects correctly -------------------------------------------------------- Key: JBSEAM-2547 URL: http://jira.jboss.com/jira/browse/JBSEAM-2547 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.GA Environment: JBoss 4.x AS, Javascript and Seam Integration Reporter: P C Assigned To: Shane Bryzak Through the use of Seam Remoting, I find that there is a "bug" in how seam decodes Collection objects on the client side (javascript). For example, on the server side, I am doing the following in a stateless seam bean: @Stateless@Name ("test") class TestAction implements Test { List getTestItems() {...} } On the Client Side (Javascript): var test = Seam.Component.getInstance("test"); test.getTestItems(callBack); var callBack(result) { } When the seam proxy decodes the message it cannot determine the object types inside the returned collection so it returns someting undefined. But if I define Generics then it works: List<ConcreteClass> getTestItems() {...} It seams to me that the Seam Proxy has trouble parsing objects in an abstract collection. -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2526) org.jboss.seam.core.SeamResourceBundle::getKeys()

by Antoni Jakubiak (JIRA)

org.jboss.seam.core.SeamResourceBundle::getKeys() ------------------------------------------------- Key: JBSEAM-2526 URL: http://jira.jboss.com/jira/browse/JBSEAM-2526 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1 Reporter: Antoni Jakubiak Priority: Trivial Please, take a look at this code: org.jboss.seam.core.SeamResourceBundle public Enumeration<String> getKeys() { List<java.util.ResourceBundle> pageBundles = getPageResourceBundles(); List<ResourceBundle> bundles = getBundlesForCurrentLocale(); Enumeration<String>[] enumerations = new Enumeration[bundles.size() + pageBundles.size()]; int i = 0; for (; i < pageBundles.size(); i++) { enumerations[i++] = pageBundles.get(i).getKeys(); } for (; i < bundles.size(); i++) { enumerations[i] = bundles.get(i).getKeys(); } [...] } Loops doesn't look ok for me. I think, it shoud be: int j = 0; int i; for (i = 0; i < pageBundles.size(); i++, j++) { enumerations[ j ] = pageBundles.get(i).getKeys(); } for (i = 0; i < bundles.size(); i++, j++) { enumerations[ j ] = bundles.get(i).getKeys(); } -- 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, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2392) document p:html

by Norman Richards (JIRA)

document p:html --------------- Key: JBSEAM-2392 URL: http://jira.jboss.com/jira/browse/JBSEAM-2392 Project: JBoss Seam Issue Type: Task Components: PDF Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor The html to pdf tag needs some documentation. -- 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, 11 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1145) "javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO

by Alex Savitsky (JIRA)

"javax.persistence.TransactionRequiredException: no transaction is in progress" thrown during flush of a transient entity in a @Transactional POJO -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1145 URL: http://jira.jboss.com/jira/browse/JBSEAM-1145 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Tomcat + Microcontainer (has also been tried on Tomcat + JOTM, Tomcat + Atomikos, Tomcat + JBoss Transactions, all with the same result) Seam-managed Tx and PC, long-running conversations with manual flush Reporter: Alex Savitsky When persisting a transient entity during manual flush, an exception "javax.persistence.TransactionRequiredException: no transaction is in progress" is thrown, unless getEntityManager().joinTransaction() is executed prior to flush() - despite declaring the POJO as @Transactional and using Seam-managed transactions and persistence contexts. When persisting a managed entity, however, no exceptions are thrown and update completes normally. -- 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, 11 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2543) Typos in Seam documentation

by Joshua Partogi (JIRA)

Typos in Seam documentation --------------------------- Key: JBSEAM-2543 URL: http://jira.jboss.com/jira/browse/JBSEAM-2543 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.1.CR2 Reporter: Joshua Partogi Priority: Minor 1. On point 32.2.1, Testing Seam application (the second example block): processPayment method should have been boolean instead of void 2. On point 12.1, Seam and JBoss Rules (both of the example block): the <drools:rule-files> value should have .drl suffix instead of policyPricingRules only -- 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1034) Usage of jBPM core:process-definitions needs clarification

by Arjan van Bentem (JIRA)

Usage of jBPM core:process-definitions needs clarification ---------------------------------------------------------- Key: JBSEAM-1034 URL: http://jira.jboss.com/jira/browse/JBSEAM-1034 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml: <core:jbpm> <core:pageflow-definitions> <value>createDocument.jpdl.xml</value> <value>editDocument.jpdl.xml</value> <value>approveDocument.jpdl.xml</value> </core:pageflow-definitions> <core:process-definitions> <value>documentLifecycle.jpdl.xml</value> </core:process-definitions> </core:jbpm> Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line <property name="hbm2ddl.auto">create-drop</property> is changed into <property name="hbm2ddl.auto">update</property> Apparently using <core:pageflow-definitions> is considered to be a developers tool: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819 I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that. Arjan. -- 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, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-652) Allow use of EHCache with <s:cache/>

by Gavin King (JIRA)

Allow use of EHCache with <s:cache/> ------------------------------------ Key: JBSEAM-652 URL: http://jira.jboss.com/jira/browse/JBSEAM-652 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor -- 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, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2542) Seam-gen generates false s:link in menu.xhtml (the logout button)

by Mark Schmatz (JIRA)

Seam-gen generates false s:link in menu.xhtml (the logout button) ----------------------------------------------------------------- Key: JBSEAM-2542 URL: http://jira.jboss.com/jira/browse/JBSEAM-2542 Project: JBoss Seam Issue Type: Bug Reporter: Mark Schmatz Seam-gen generates the following code in the menu.xhtml page: <s:link view="/home.xhtml" action="#{identity.logout}" value="Logout" rendered="#{identity.loggedIn}"/> We have here both, the 'view' and the 'action' attribute at the same time. Is this well-defined? I would propose to discard the 'view' attribute and replace the EL in the 'action' attribute with: #{authenticator.logout} Additionally, in the Authenticator class the logout method should be provided (automatically generated by Seam-gen) which invokes 'identity.logout(). In the pages.xml a respective navigation to the "/home.xhtml" page should be performed. The advantage - besides having a proper s:link - is that one can do additional stuff in the logout method before and/or after logging out. -- 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, 11 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008