@DataModel should not require a setter
--------------------------------------
Key: JBSEAM-1868
URL: http://jira.jboss.com/jira/browse/JBSEAM-1868
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: SEAM 2.0.BETA1
Reporter: Felix Ho?feld
Priority: Blocker
This patch http://lists.jboss.org/pipermail/jboss-cvs-commits/2007-August/039852.html
requires all methods annotated with @Datamodels to have a corresponding setter.
This makes the Seam 2.0 migration much harder than necessary. My project has lots of lists that are created on the fly when the get-Method is called. So these are really readonly. Seam 2.0 will require to add empty setters to all these components.
IMHO a setter should not even be required when susing @DataModelSelection. The datamodel should be available from the context it was outjected to. Pre Seam 2.0 this was not required so this is a clear regression to me. On the other hand adding emty setters is not that hard...
--
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
document page parameter usage with no value attribute
-----------------------------------------------------
Key: JBSEAM-1847
URL: http://jira.jboss.com/jira/browse/JBSEAM-1847
Project: JBoss Seam
Issue Type: Task
Components: Documentation
Affects Versions: 2.0.0.BETA1
Reporter: Matt Drees
Page parameters are well documented, but the documentation makes it appear that the value attribute is required. A look at a seam-gened app shows this is not true. So what is the behavior of something like
<page param="personFrom"/>
?
I'm guessing it stores the request parameter in the event context or something, but documentation would be fantastic.
--
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
seam-gen not adding mail files to the eclipse .classpath
--------------------------------------------------------
Key: JBSEAM-1829
URL: http://jira.jboss.com/jira/browse/JBSEAM-1829
Project: JBoss Seam
Issue Type: Bug
Reporter: Chris Lowe
To a vanilla seam-gen project, the Eclipse build path needs updating to add lib/mail.jar and lib/mail-ra.jar (note: JAR and not RAR) - it would be useful to get this from the docs or have seam-gen make the necessary setup rather than having to work it 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
factory name collisions ignored?
--------------------------------
Key: JBSEAM-1827
URL: http://jira.jboss.com/jira/browse/JBSEAM-1827
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.BETA1
Environment: cvs
Reporter: Matt Drees
Priority: Minor
Just looking through Init.java, it looks like users aren't notified if they try to make two factories with the same name.
See forum for details.
--
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
document flush-mode attribute in <begin-conversation>
-----------------------------------------------------
Key: JBSEAM-1861
URL: http://jira.jboss.com/jira/browse/JBSEAM-1861
Project: JBoss Seam
Issue Type: Task
Components: Documentation
Affects Versions: 2.0.0.BETA1
Reporter: Matt Drees
Priority: Minor
The documentation mentions you can use @Begin(flushMode=FlushModeType.MANUAL), but doesn't mention that you can use <begin-conversation flush-mode="manual">.
--
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
Mistyped in documents regarding setting up Seam environment
-----------------------------------------------------------
Key: JBSEAM-1799
URL: http://jira.jboss.com/jira/browse/JBSEAM-1799
Project: JBoss Seam
Issue Type: Task
Components: Documentation
Affects Versions: 2.0.0.BETA1
Environment: JBoss AS 4.2.0
Reporter: Joshua Jackson
Fix For: 2.0.0.CR1
1. Configuring jBPM in Seam.
Version: 2.0.0.Beta1
Chapter: 25
Sub chapter: 6
Since Seam 2.0 uses jpdl 3.2.x, we need to add this element
Code:
<service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
2. Bootstrapping JPA In seam
Chapter: 25
Sub-chapter: 25.3.2
Page: 221
Code:
<persistence:managed-persistence-context name="entityManager" session-factory="#{entityManagerFactory}"/>
It should've been entity-manager-factory instead of session-factory
--
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
Evaluate EL in exception redirect view-id
-----------------------------------------
Key: JBSEAM-1813
URL: http://jira.jboss.com/jira/browse/JBSEAM-1813
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.2.1.GA
Reporter: steve tynor
Currently, it's not possible to use EL in the view-id string in an page exception handler. This makes it awkward to redirect to different pages depending on the cause for a given exception. See forum reference for a use case and a workaround.
--
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
Bootstrap should be initialized using bootstrap.deployResourceBases instead of bootstrap.deployResourceBase
-----------------------------------------------------------------------------------------------------------
Key: JBSEAM-1791
URL: http://jira.jboss.com/jira/browse/JBSEAM-1791
Project: JBoss Seam
Issue Type: Bug
Components: Test Harness
Affects Versions: 2.0.0.BETA1
Reporter: Chris Rudd
I am currently working on projects that contain multiple Seam EJB jars and multiple Seam Pojo jars. When the test harness uses the deployResourceBase (singular) the first jar that is found with the resource is the only one deployed. This creates a problem when there are multiple seam jars.
Please change the code to call deployResourceBases (plural) so that all jars containing the resource will be deployed.
Affects BaseSeamTest.startJbossEmbeddedIfNeccisary (2.0.0.BETA1) or EmbeddedBootstrap.startAndDeployResources (CVS HEAD)
--
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
The equals method in org.jboss.seam.framework.Identifier refrences derived.
---------------------------------------------------------------------------
Key: JBSEAM-1794
URL: http://jira.jboss.com/jira/browse/JBSEAM-1794
Project: JBoss Seam
Issue Type: Bug
Components: Framework
Affects Versions: 2.0.0.BETA1
Reporter: tzman
The equals method checks for an instance of the derived type org.jboss.seam.framework.EntityIdentifier
--
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