Hot deploy of Seam components in a WAR
--------------------------------------
Key: JBSEAM-997
URL: http://jira.jboss.com/jira/browse/JBSEAM-997
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.2.1.GA
Seam JavaBean components deployed into WEB-INF/dev should be subject to hot re-deploy w/o a container restart.
--
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
Missing namespace entry in components.xml
-----------------------------------------
Key: JBSEAM-956
URL: http://jira.jboss.com/jira/browse/JBSEAM-956
Project: JBoss Seam
Issue Type: Task
Components: Framework
Affects Versions: 1.1.6.GA
Environment: Seam-gen -> auto-generated components.xml file
Reporter: Mark Schmatz
Priority: Minor
In the auto-generated components.xml file there's a xml namespace entry missing. It's:
xmlns:framework="http://jboss.com/products/seam/framework"
Without it you're not able to define entity queries like
<framework:entity-query name="countries" ejbql="from Country c" />
--
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
iText support should allow .pdf and .html file extensions
---------------------------------------------------------
Key: JBSEAM-677
URL: http://jira.jboss.com/jira/browse/JBSEAM-677
Project: JBoss Seam
Issue Type: Feature Request
Affects Versions: 1.1.5.GA
Reporter: Norman Richards
It should be possible to to use the iText support with urls like myDocument.pdf. This will work better with browsers, work better when the user saves the document and look much nicer.
--
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-215?page=comments#action_12355237 ]
Pete Muir commented on JBSEAM-215:
----------------------------------
Updated xsd to add in all attributes for start-page and page. Deleted end-state (not defined for pageflow). Put the xsd in the standard seam (rather than jbpm) namespace (i.e. http://jboss.com/products/seam/pageflow).
I made it so that start-page supports everything page does apart from end-conversation and end-task. Is node a valid element in a pageflow or should I delete it from the xsd?
> Create an XML schema or DTD for pageflow
> ----------------------------------------
>
> Key: JBSEAM-215
> URL: http://jira.jboss.com/jira/browse/JBSEAM-215
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: BPM
> Reporter: Gavin King
> Assigned To: Pete Muir
> Priority: Blocker
> Fix For: 1.2.1.GA
>
> Attachments: pageflow-1.0.xsd
>
>
> like it says
--
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
EntityManagerProxy should be serializable
-----------------------------------------
Key: JBSEAM-996
URL: http://jira.jboss.com/jira/browse/JBSEAM-996
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0.GA
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.2.1.GA
--
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
Use javassist for proxies
-------------------------
Key: JBSEAM-989
URL: http://jira.jboss.com/jira/browse/JBSEAM-989
Project: JBoss Seam
Issue Type: Task
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.2.1.GA
Seam already has a dependency to javassist, so let's kick cglib 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
Debug page improvements
-----------------------
Key: JBSEAM-987
URL: http://jira.jboss.com/jira/browse/JBSEAM-987
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Pete Muir
Priority: Critical
The debug should be available on every page. We could either use some (ajax) control to make it appear (e.g. a collapsed panel) or have a keyboard shortcut. The debug page should include an h:messages component.
--
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
@Converter, @Validator
----------------------
Key: JBSEAM-980
URL: http://jira.jboss.com/jira/browse/JBSEAM-980
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Gavin King
Assigned To: Gavin King
Fix For: 1.2.1.GA
I think it's a good idea to let users avoid editing faces-config.xml when creating validators and converters.
@Converter(id="....")
public class FooConverter implements Converter { .... }
@Converter(targetClass="....")
public class FooConverter implements Converter { .... }
@Validator(id="....")
public class FooValidator implements Validator { .... }
We would scan for these guys at startup, and register them with JSF.
--
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-215?page=all ]
Pete Muir reassigned JBSEAM-215:
--------------------------------
Assignee: Pete Muir (was: Gavin King)
> Create an XML schema or DTD for pageflow
> ----------------------------------------
>
> Key: JBSEAM-215
> URL: http://jira.jboss.com/jira/browse/JBSEAM-215
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: BPM
> Reporter: Gavin King
> Assigned To: Pete Muir
> Priority: Blocker
> Fix For: 1.2.1.GA
>
> Attachments: pageflow-1.0.xsd
>
>
> like it says
--
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
Remove dependency on org.jboss.util.NotImplementedException
-----------------------------------------------------------
Key: JBSEAM-973
URL: http://jira.jboss.com/jira/browse/JBSEAM-973
Project: JBoss Seam
Issue Type: Task
Components: Core
Affects Versions: 1.1.6.GA
Environment: Any
Reporter: Mike Quilleash
The UiComponent seam component uses org.jboss.util.NotImplementedException. Would suggest this is removed and replaced with the standard java.lang.UnsupportedOperationException.
I prefer to have a minimal jar set for maintainence of projects so I would prefer to not have to pull in utility classes like this.
--
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