[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2783) SeamDisc Example Changes Display of Table When Filtering on Artist
by scott duke (JIRA)
SeamDisc Example Changes Display of Table When Filtering on Artist
------------------------------------------------------------------
Key: JBSEAM-2783
URL: http://jira.jboss.com/jira/browse/JBSEAM-2783
Project: JBoss Seam
Issue Type: Feature Request
Components: Examples
Affects Versions: 2.1.0.A1
Reporter: scott duke
I came across this when I updated my Trinidad libraries and I see Seam 2.1.0 is having the same issue. When you run SeamDiscs example with the newer Trinidad libraries the graphics on the filtered tables changes. From the home page, go into the "Artists" menu option. You see the artist listing having a gray background table. When you type a letter in the "filter on artist" inputText, the table changes completely.
I was able to narrow this down to Trinidad v1.2.1 supporting the tag: <tr:panelPartialRoot>. Using this version, the tag is present and works correctly. Using a later version it does not. I have not seen any information about this tag being depricated. I see in the snapshot of seam v2.1.0 the xhtml has been changed to not use the tag, but the problem with the listings exist.
--
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
17 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2883) create more informative start page for seam-gen
by Dan Allen (JIRA)
create more informative start page for seam-gen
-----------------------------------------------
Key: JBSEAM-2883
URL: http://jira.jboss.com/jira/browse/JBSEAM-2883
Project: Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.1.0.A1, 2.0.1.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.GA
Attachments: tg-now-running.png
The start page on seam-gen is not very welcoming. While the bullet items are accurate and give some indication of what the developer has at his/her disposal, it doesn't give any instructions on where to go next.
I came across a screenshot of the start page for TurboGears and immediately recognized that it is time to improve. Ruby on Rails has something similar.
Ideas for what to include:
Identify the moving parts: entity class, action class, Facelet template
Give a brief overview of commands that can be used for development (explode/deploy)
Information about Seam and seamframework.org
--
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
17 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2608) Natural conversation for wildcard view-id
by Jacob Orshalick (JIRA)
Natural conversation for wildcard view-id
-----------------------------------------
Key: JBSEAM-2608
URL: http://jira.jboss.com/jira/browse/JBSEAM-2608
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.1.GA
Reporter: Jacob Orshalick
Priority: Optional
When a natural conversation spans a number of pages you currently have to explicitly state the named conversation for each view-id. It would be nice to simply specify the natural conversation for a wildcard view-id.
For example, if my conversation spans the following:
Code:
<conversation name="Checkout"
parameter-name="cart"
parameter-value="#{cart.cartId}"/>
<page view-id="/checkout/checkout1.jsp" conversation="Checkout" />
<page view-id="/checkout/checkout2.jsp" conversation="Checkout" />
<page view-id="/checkout/checkout3.jsp" conversation="Checkout" />
<page view-id="/checkout/confirm.jsp" conversation="Checkout" />
Instead I would prefer to use:
Code:
<page view-id="/checkout/*" conversation="Checkout" />
This is also especially useful for free navigation situations within the conversation that do not have navigation rules (i.e. the conversation spans many pages but can access any page at any time) to avoid specifying each view-id in pages.xml.
--
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
17 years, 10 months