seam-gen setup and create-project with support for individual JBoss domain
--------------------------------------------------------------------------
Key: JBSEAM-3827
URL: https://jira.jboss.org/jira/browse/JBSEAM-3827
Project: Seam
Issue Type: Patch
Components: Build
Affects Versions: 2.1.1.CR2
Reporter: Stephan Heffner
Priority: Optional
Attachments: jboss-seam-gen-domain.patch
I'll attach a small patch to support a user defined value of JBoss version and domain. Predefined values are 'default' or 'standard' (Version 5.x).
Maybe it's useful for others as well.
--
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
Exclude build directories in generated IntelliJ IDEA project
------------------------------------------------------------
Key: JBSEAM-3907
URL: https://jira.jboss.org/jira/browse/JBSEAM-3907
Project: Seam
Issue Type: Patch
Components: Tools
Affects Versions: 2.1.1.GA
Reporter: Pawel Wrzeszcz
Assignee: Dan Allen
Priority: Minor
Directories 'dist' and 'exploded-archives' should be marked as excluded in the IntelliJ IDEA module file created by seam-gen.
I realize this is minor, but saves a couple of clicks and prevents IDEA from 1) reloading a whole project during the build and 2) detecting facets in the build directories.
Really short path attached.
--
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
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
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
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
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
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
Only enable ManagedEntityInterceptor when needed
------------------------------------------------
Key: JBSEAM-3708
URL: https://jira.jboss.org/jira/browse/JBSEAM-3708
Project: Seam
Issue Type: Feature Request
Components: Core
Reporter: Pete Muir
Priority: Critical
Fix For: 2.1.1.CR2
The MEI is only needed for:
* JavaBeans in a cluster that are conversation scoped
or
* EJBs that are conversation scoped
Add some configuration to <core:init /> to allow the user to enable clustering mode (or autodetect) and upgrade the isInterceptorEnabled method to take account of this.
--
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