[ http://jira.jboss.com/jira/browse/JBSEAM-293?page=all ]
Gavin King updated JBSEAM-293:
------------------------------
Fix Version/s: 1.1.0.CR2
(was: 1.1.1.GA)
Priority: Blocker (was: Major)
This is now a blocking problem, since the new scanning code breaks the ability to override built-in components!
> Add well defined precedence for component overriding with the same name.
> ------------------------------------------------------------------------
>
> Key: JBSEAM-293
> URL: http://jira.jboss.com/jira/browse/JBSEAM-293
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 1.0.1
> Reporter: Jason Long
> Assigned To: Gavin King
> Priority: Blocker
> Fix For: 1.1.0.CR2
>
> Attachments: SEAM-293-doc-patch.txt, SEAM-293-patch.txt
>
>
> Add well defined precidence for component overriding with the same name.
--
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
special characters (accented a) display wrong in booking example (probably encoding-issue)
-------------------------------------------------------------------------------------------
Key: JBSEAM-520
URL: http://jira.jboss.com/jira/browse/JBSEAM-520
Project: JBoss Seam
Issue Type: Bug
Components: Examples
Affects Versions: 1.1.0.CR1
Environment: http://seam.demo.jboss.com
or
Jboss 5.0.0 beta1on Linux
Reporter: Dr. Rolf Mertig
log into the booking example (e.g. on http://seam.demo.jboss.com)
and enter into the search for Hotel field:
Mel
Instead of
Meliá White House
one sees:
Meli? White House
i.e., the accented "a" at the end (Meliá) is not displayed.
There is also a posting from Monday Nov 20th with more details on my Linux setup on
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=94738
This should really work out of the box on any Linux environment.
It definitely should work on http://seam.demo.jboss.com
which I suppose is a Redhat - server.
--
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
New scanning code broke J2EE compatibility
------------------------------------------
Key: JBSEAM-519
URL: http://jira.jboss.com/jira/browse/JBSEAM-519
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.0.CR1
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.1.0.CR2
Because Dispatcher has an @Stateless annotation.
--
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
portal example is broken in CR1
-------------------------------
Key: JBSEAM-515
URL: http://jira.jboss.com/jira/browse/JBSEAM-515
Project: JBoss Seam
Issue Type: Bug
Components: Examples
Affects Versions: 1.1.0.CR1
Reporter: Gavin King
Assigned To: Gavin King
Priority: Minor
Fix For: 1.1.0.CR2
--
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
HibernateSessionFactory should not have an install dependency to mc
-------------------------------------------------------------------
Key: JBSEAM-517
URL: http://jira.jboss.com/jira/browse/JBSEAM-517
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0.CR1
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.1.0.CR2
This breaks all Hibernate examples on JBoss!
--
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
dist does not include sema-gen src dir
--------------------------------------
Key: JBSEAM-516
URL: http://jira.jboss.com/jira/browse/JBSEAM-516
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.0.CR1
Reporter: Gavin King
Assigned To: Gavin King
Priority: Trivial
Fix For: 1.1.0.CR2
--
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
[ http://jira.jboss.com/jira/browse/JBSEAM-116?page=all ]
Gavin King updated JBSEAM-116:
------------------------------
Fix Version/s: 1.1.1.GA
(was: 1.1.0.GA)
> Pluggable conversationId handler
> --------------------------------
>
> Key: JBSEAM-116
> URL: http://jira.jboss.com/jira/browse/JBSEAM-116
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Reporter: Gavin King
> Assigned To: Gavin King
> Priority: Critical
> Fix For: 1.1.1.GA
>
>
> Currently, there is no way to plug in a user-defined strategy for decoding and encoding the conversationId in the request/response.
> We need this to really properly support AJAX/Soap invocations.
--
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
install JSF RI on JBoss using seam-gen
---------------------------------------
Key: JBSEAM-496
URL: http://jira.jboss.com/jira/browse/JBSEAM-496
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Reporter: Gavin King
Fix For: 1.1.0.GA
Would be great if we could ask if they want to use the JSF RI in "seam setup", and if they do then install the RI in JBoss, and generate a project that uses the RI. This would need to be reversible, since the Seam examples only run on MyFaces, OOTB.
--
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
[ http://jira.jboss.com/jira/browse/JBSEAM-65?page=all ]
Gavin King closed JBSEAM-65.
----------------------------
Assignee: Gavin King (was: Thomas Heute)
> Rework autodiscovery architecture
> ---------------------------------
>
> Key: JBSEAM-65
> URL: http://jira.jboss.com/jira/browse/JBSEAM-65
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Reporter: Gavin King
> Assigned To: Gavin King
> Priority: Blocker
>
> Currently, we have some component auto-discovery stuff that works with JBoss EJB3 deployer. Among the many issues that have arisen with this is the problem that we are not always on JBoss. We need a generic auto-discovery mechanism that scans the archive with seam.properties in it and auto-deploys the seam components.
> I've realized we cannot release without this, so it is now the highest priority issue.
--
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