November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3431) Add missing ids to Seam examples

by Jozef Hartinger (JIRA)

Add missing ids to Seam examples -------------------------------- Key: JBSEAM-3431 URL: https://jira.jboss.org/jira/browse/JBSEAM-3431 Project: Seam Issue Type: Task Components: Examples Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Attachments: dvd.patch Absence of ids on certains elements in seam examples is a problem for automated testing. -- 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

17 years, 4 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3529) use more representive names for hot and standard classpath entries

by Dan Allen (JIRA)

use more representive names for hot and standard classpath entries ------------------------------------------------------------------ Key: JBSEAM-3529 URL: https://jira.jboss.org/jira/browse/JBSEAM-3529 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.CR1 Reporter: Dan Allen Assignee: Dan Allen The classpath entry for hot deployable components is currently src/action and the path for non-hot deployable components is src/model. That problem is that we are mixing the function of the classes with the way they get deployed. The classpath entries should have names which represent how they are handled. The suggested mapping is as follows: src/action -> src/hot src/model -> src/main -- 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

17 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1872) A way to use ear bundled rather tha OC4J bundled ANTLR for Hibernate

by Pete Muir (JIRA)

A way to use ear bundled rather tha OC4J bundled ANTLR for Hibernate -------------------------------------------------------------------- Key: JBSEAM-1872 URL: http://jira.jboss.com/jira/browse/JBSEAM-1872 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Currently the example and doc use a workaround to make Hibernate use an older version of ANTLR. Max tells me this is bad. -- 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, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3324) messages example with tomcat + embedded throws a ncdf exception

by Jay Balunas (JIRA)

messages example with tomcat + embedded throws a ncdf exception --------------------------------------------------------------- Key: JBSEAM-3324 URL: https://jira.jboss.org/jira/browse/JBSEAM-3324 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Fix For: 2.1.0.BETA2 Deployed the messages example to tomcat with jboss embedded installed. It deployed fine, but when first accessed I see : Aug 25, 2008 2:05:21 PM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet Faces Servlet threw exception java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:457) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:141) at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:87) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 4 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3333) seam-gen generated test configuration fails on JDK6

by Jozef Hartinger (JIRA)

seam-gen generated test configuration fails on JDK6 --------------------------------------------------- Key: JBSEAM-3333 URL: https://jira.jboss.org/jira/browse/JBSEAM-3333 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.0.BETA1 Environment: JDK6 update 7 Fedora 9 Reporter: Jozef Hartinger When running seam-gen generated tests configuration failure appears. See attached file for detailed output. Problem does not appear on JDK5. -- 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

17 years, 4 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3076) Update Weblogic reference guide with new patch information

by Jay Balunas (JIRA)

Update Weblogic reference guide with new patch information ---------------------------------------------------------- Key: JBSEAM-3076 URL: http://jira.jboss.com/jira/browse/JBSEAM-3076 Project: Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.0.3.GA, 2.1.0.BETA1 A user has let me know that BEA just released the latest patch to solve some of their handling of EJB3 which was causing issues with one of Seam EJBs as described in the reference guide. -- 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, 4 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2901) seam-gen unable to clear off database catalog name

by Ashish Kulkarni (JIRA)

seam-gen unable to clear off database catalog name -------------------------------------------------- Key: JBSEAM-2901 URL: http://jira.jboss.com/jira/browse/JBSEAM-2901 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.GA Environment: Seam 2.0.1.GA, JDk 1.5.0_11, Windows XP, ANT 1.7.0 Reporter: Ashish Kulkarni Hi there, If I use a database catalog name when generating a project using seam-gen say, for h2 database, and then, I decide to use seam-gen for another database that doesn't use catalogs, like PostgreSQL, there is no way of clearing off the database catalog name unless I manually do that. In short, I need to edit seam-gen/build.properties manually for this. Can seam-gen deal with this in some way? Best Regards, Ashish. -- 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, 4 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3498) Icefaces example - conversation timeout in booking process

by Jozef Hartinger (JIRA)

Icefaces example - conversation timeout in booking process ---------------------------------------------------------- Key: JBSEAM-3498 URL: https://jira.jboss.org/jira/browse/JBSEAM-3498 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Login works fine now but in the middle of booking process (after submiting hotel page) user is redirected to main page and conversation timeout message is displayed. Conversation remains present in workspace manager but switching to it results in main page again. -- 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

17 years, 4 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3669) SVN's Seam Reference Guide link is outdated

by omarps (JIRA)

SVN's Seam Reference Guide link is outdated ------------------------------------------- Key: JBSEAM-3669 URL: https://jira.jboss.org/jira/browse/JBSEAM-3669 Project: Seam Issue Type: Bug Components: Documentation Issues Reporter: omarps The SVN's Seam Reference Guide link is outdated. In the page Translating Seam into your own language (http://www.seamframework.org/Documentation/TranslatingSeamIntoYourOwnLang...), it refers to a SVN repository that has been moved. It points to: http://anonsvn.jboss.org/repos/seam/branches/Seam_2_0/doc/Seam_Reference_.... The righ url might be: http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_0/doc/Seam_... -- 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

17 years, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3564) Two Seam examples cannot run at the same time on AS5

by Jozef Hartinger (JIRA)

Two Seam examples cannot run at the same time on AS5 ---------------------------------------------------- Key: JBSEAM-3564 URL: https://jira.jboss.org/jira/browse/JBSEAM-3564 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.CR1, 2.0.3.CR1 Environment: JDK6 AS 5.0.0.CR2 Reporter: Jozef Hartinger It is not possible to run AS5 with two seam examples deployed at the same time. I am getting "org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: jboss.j2ee:jar=jboss-seam.jar,service=EJB3 already registered." when the second one is being deployed. Both the examples work fine when deployed alone. -- 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

17 years, 4 months

4
9
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 November 2008