datasource redeployed on explode
--------------------------------
Key: JBSEAM-3866
URL: https://jira.jboss.org/jira/browse/JBSEAM-3866
Project: Seam
Issue Type: Bug
Components: Tools
Affects Versions: 2.1.1.GA
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.1.2.CR1
The datasource is being redeployed during hot deployment (ant explode) as a result of the -ds.xml file being copied with overwrite="true".
--
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
Member cann't access wikiNode which read_access_level setted to himself
-----------------------------------------------------------------------
Key: JBSEAM-3871
URL: https://jira.jboss.org/jira/browse/JBSEAM-3871
Project: Seam
Issue Type: Bug
Components: Wiki
Affects Versions: 2.1.1.GA
Reporter: wu haixing
Assignee: Christian Bauer
If a member create a document want to see by himself,currentAccessLevel Filter cann't get the document because the member's access level obviously less than WikiNode's READ_ACCESS_LEVEL setted to administrator's accessLevel.
--
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
Upgrade to RichFaces 3.3.0.GA
-----------------------------
Key: JBSEAM-3894
URL: https://jira.jboss.org/jira/browse/JBSEAM-3894
Project: Seam
Issue Type: Task
Components: Build
Reporter: Jay Balunas
Priority: Critical
Fix For: 2.1.2.CR1
RichFaces 3.3.0 has been released and Seam should upgrade to it.
--
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
Boolean tests during Initialization consistent with JDK
-------------------------------------------------------
Key: JBSEAM-3747
URL: https://jira.jboss.org/jira/browse/JBSEAM-3747
Project: Seam
Issue Type: Patch
Components: Core
Affects Versions: 2.1.1.CR1
Reporter: Anthony Whitford
Priority: Minor
I noticed code like:
boolean autoCreate = "true".equals(factory.attributeValue("auto-create"));
Java already has some boolean semantics that I would expect to be leveraged for consistency. The line could be replaced with:
boolean autoCreate = Boolean.parseBoolean(factory.attributeValue("auto-create"));
There is a subtle difference in that parseBoolean will do a case insensitive comparison, but at least this is consistent with core Java.
See: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#parseBoolean...
and: http://java.sun.com/javase/6/docs/api/java/lang/Boolean.html#valueOf(java...
The above change also removes "magic values" repeated ("true").
Very minor issue, but also easy to fix.
--
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
allow callbacks to components that implement HttpSessionActivationListener interface
------------------------------------------------------------------------------------
Key: JBSEAM-3782
URL: https://jira.jboss.org/jira/browse/JBSEAM-3782
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.CR1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.1.1.CR2
Seam adds the HttpSessionActivationListener interface to all non-EJB components to capture session passivation and activation events. Seam then channels these callbacks to the @PrePassivate and @PostActivate methods on the component, respectively. However, Seam is not honoring components which might have already implemented this interface. Allow calls to sessionWillPassivate and sessionDidActivate to proceed on to the component if the bean class implements HttpSessionActivationListener.
--
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
seam-gen - entity is not mapped in war project on AS5
-----------------------------------------------------
Key: JBSEAM-3821
URL: https://jira.jboss.org/jira/browse/JBSEAM-3821
Project: Seam
Issue Type: Bug
Components: Tools
Affects Versions: 2.1.1.CR2
Environment: JDK5
JBoss AS 5.0.0.GA
Reporter: Jozef Hartinger
Fix For: 2.1.2.CR1
Attachments: genWarRich.txt
When accessing generated entity page the application is failing on "org.hibernate.hql.ast.QuerySyntaxException: Vehicle is not mapped [select vehicle from Vehicle vehicle]" . I am using standard release-process.txt database tables. To reproduce the issue:
1.) Create new war project and generate entities.
2.) Log into the application and click PersonList or VehicleList
--
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
Update release-process.txt to include the functional test execution
-------------------------------------------------------------------
Key: JBSEAM-3714
URL: https://jira.jboss.org/jira/browse/JBSEAM-3714
Project: Seam
Issue Type: Task
Components: Build, Test Harness
Affects Versions: 2.1.1.CR1
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 2.1.1.CR2
The release-process.txt needs to be updated to include steps and instructions for the functional tests using selenium.
--
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
Support testing of wicket/seam apps
-----------------------------------
Key: JBSEAM-3696
URL: https://jira.jboss.org/jira/browse/JBSEAM-3696
Project: Seam
Issue Type: Feature Request
Reporter: Clint Popetz
Assignee: Clint Popetz
We need to provide an AbstractSeamTest subclass that integrates the context creation/destruction into the lifecycle of WicketTester and formTester.
--
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
debug.xhtml should have switch disabled by default
--------------------------------------------------
Key: JBSEAM-3705
URL: https://jira.jboss.org/jira/browse/JBSEAM-3705
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 2.1.0.SP1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 2.1.1.CR1
There is really no use case where the debug.xhtml should become part of a workspace (switching enabled). Obviously, this only affects development since the debug page isn't even present in production. Right now, when you visit the debug page and inspect a conversation, it becomes the last viewed page in that conversation, which is really annoying.
--
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
CLONE - Adding New Role to Group fails
--------------------------------------
Key: JBSEAM-3704
URL: https://jira.jboss.org/jira/browse/JBSEAM-3704
Project: Seam
Issue Type: Bug
Components: Examples, Security
Affects Versions: 2.1.0.GA
Environment: JDK 5
JBoss AS 4.2.3
Reporter: Julien Hattier
Assignee: Shane Bryzak
I am getting ClassCastException when trying to add new role. To reproduce try adding new role that will be member of some other exsting role.
--
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