XValidation should support converting java fields named with $ into the faces component id separator character
--------------------------------------------------------------------------------------------------------------
Key: SEAMFACES-38
URL: https://jira.jboss.org/browse/SEAMFACES-38
Project: Seam Faces
Issue Type: Feature Request
Components: UI Components, Validation & Conversion
Reporter: Lincoln Baxter III
@Inject @InputField password$input
== password:input
no need for the annotation value
dollar signs become the faces component separator character if you don't provide an annotation value
if you provide an annotation value, it wins
@Inject @InputField("form:foo") password$input
== form:foo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide parody for Seam 2 support tags not included in JSF2 & do not belong in a component library
--------------------------------------------------------------------------------------------------
Key: SEAMFACES-36
URL: https://jira.jboss.org/browse/SEAMFACES-36
Project: Seam Faces
Issue Type: Feature Request
Components: UI Components
Reporter: Lincoln Baxter III
Support for basic HTML simplification tag:
A tag that can be used to generate any HTML element:
<s:tag type="div" rendered="true">
...
</s:tag>
Also, a determination must be made on which major components still need to be required. Separate JIRAs are filed for each component when this takes place.
http://docs.jboss.com/seam/2.2.0.GA/en-US/html_single/#controls.tags
s:button -- deprecated in favor of h:button
s:conversationId -- https://jira.jboss.org/browse/SEAMFACES-32
s:taskId -- to be integrated in BPM faces-sub-modules
s:link -- deprecated in favor of h:link
s:conversationPropagation -- https://jira.jboss.org/browse/SEAMFACES-35
s:defaultAction -- https://jira.jboss.org/browse/SEAMFACES-34
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support appending conversationId in JSF rendered links, h:link
--------------------------------------------------------------
Key: SEAMFACES-32
URL: https://jira.jboss.org/browse/SEAMFACES-32
Project: Seam Faces
Issue Type: Feature Request
Components: Conversations
Reporter: Lincoln Baxter III
Weld currently supports this automatically -- it shouldn't.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide support for URL-rewriting / Bookmarking
-----------------------------------------------
Key: SEAMFACES-31
URL: https://jira.jboss.org/browse/SEAMFACES-31
Project: Seam Faces
Issue Type: Feature Request
Reporter: Lincoln Baxter III
Support contextual URL-rewriting and bookmarking
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide <s:cache> for saving regions of rendered output to Cache
----------------------------------------------------------------
Key: SEAMFACES-30
URL: https://jira.jboss.org/browse/SEAMFACES-30
Project: Seam Faces
Issue Type: Feature Request
Components: UI Components
Reporter: Lincoln Baxter III
In order to optimize performance in database lookups and component rendering, support a tag to save regions of rendered output to a cache. This has already been implemented, and just needs to be ported from Seam 2 to Seam 3 Faces.
http://docs.jboss.com/seam/2.2.0.GA/en-US/html_single/#d0e21898
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Headless JSF rendering
----------------------
Key: SEAMFACES-12
URL: https://jira.jboss.org/jira/browse/SEAMFACES-12
Project: Seam Faces
Issue Type: Feature Request
Components: JSF CDI Integration
Reporter: Nicklas Karlsson
Seam 2 proved that by switching out enough stuff, you can do a headless JSF render to a String.
Seam 3 would benefit from a more complete mocked solution that would allow us to boostrap a JSF container and mock-render against that
There is a Mojarra Issue for this at https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1456
In the meantime we should examine ICEfaces, FacesTester etc for tips.
--
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
Complementing annotations for adding anything that can be put in faces-config.xml
---------------------------------------------------------------------------------
Key: SEAMFACES-3
URL: https://jira.jboss.org/jira/browse/SEAMFACES-3
Project: Seam Faces
Issue Type: Feature Request
Reporter: Nicklas Karlsson
Assignee: Lincoln Baxter III
We should have annotations for everything that can be defined in faces-config.xml
Take for example @PhaseListener, we should have an extension that processes all these annotations and calls LifeCycle.addPhaseListener. It might even be possible to have CDI injection into the phase listener through this method.
JSF should have booted by the time CDI processes the extensions, but if not, the job could always be postponed until we see the JSF application constructed event.
--
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
s:debug
-------
Key: SEAMFACES-6
URL: https://jira.jboss.org/jira/browse/SEAMFACES-6
Project: Seam Faces
Issue Type: Feature Request
Reporter: Nicklas Karlsson
Assignee: Lincoln Baxter III
The return of the s:debug that never really got completed in Seam 2 ;-)
A <s:debug/> tag that can be dropped in a page and you can bring up a display of what's in the context, the active Seam config, perhaps even some performance numbers for the page, security stuff, persistence stuff.
The ability to add custom facets in this for displaying own data is nice, too.
--
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
Security concerns regarding Seam.Remoting.eval()
------------------------------------------------
Key: JBSEAM-3592
URL: https://jira.jboss.org/jira/browse/JBSEAM-3592
Project: Seam
Issue Type: Task
Components: Remoting
Reporter: Drew Kutchar
Assignee: Shane Bryzak
A malicious user can import the seam/remoting/resource/remote.js and use Seam.Remoting.eval() to bypass @WebRemote restrictions and call any arbitrary method? This can be a very serious security hole, even if Seam Remoting is not enabled (by marking any components using @WebRemote).
Shane Bryzak stated that he is aware of this issue and has disabled Seam.Remoting.eval() functionality until he finds a way for expression evaluations to honor the @WebRemote annotation.
This JIRA is created to track Shane's work.
--
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