[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4323) Allow EL-based StyleClass and Style Attributes to be Reevaluated After the First Row of a Spreadsheet, i.e. Support Conditional Styles on Any Cell
by Sean Gurevich (JIRA)
Allow EL-based StyleClass and Style Attributes to be Reevaluated After the First Row of a Spreadsheet, i.e. Support Conditional Styles on Any Cell
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4323
URL: https://jira.jboss.org/jira/browse/JBSEAM-4323
Project: Seam
Issue Type: Feature Request
Components: Excel
Affects Versions: 2.1.2.GA
Environment: Developing on Windows XP.
Reporter: Sean Gurevich
Currently, the Seam Excel library caches (maps) the worksheet cell's styles by the cell's UIComponent. Effectively, this leads to the styleClass and style attributes' evaluation to occur only once for the first row of data, then all subsequent rows inherit the styles. I have a need to apply conditional styling to cells in a row where the value expression in a styleClass/style attribute is reevaluated for each row of data, similar in behavior to a typical data iterator in JSF.
In my discussion with Nicklas Karlsson, he's proposed a solution involving an attribute to disable this caching behavior; however retaining the default behavior for anyone that relies on the performance advantage of the caching.
--
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
15 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4264) add ability to get current index from within e:worksheet
by Eric Jung (JIRA)
add ability to get current index from within e:worksheet
--------------------------------------------------------
Key: JBSEAM-4264
URL: https://jira.jboss.org/jira/browse/JBSEAM-4264
Project: Seam
Issue Type: Feature Request
Components: Excel
Reporter: Eric Jung
Priority: Minor
Fix For: 2.1.2.GA
If you have a collection of items with an arbitrary count, there is currently no straightforward way to dynamically output the collection row-wise. Is there any way to add a varStatus attribute like c:forEach and ui:repeat have? I'm open to other ideas, too, like using a binding for e:worksheet, but that doesn't seem to help the problem.
Here's an example of what I'd like to do:
<e:worksheet name="#{messages.mySheet}" value="#{myService.someList}" var="d" startRow="31" varStatus="status">
<e:cell column="1" row="#{status.rowIndex}" value="#[d.foo}"/>
<e:cell column="2" row="#{status.rowIndex}" value="#[d.foo2}"/>
<e:cell column="3" row="#{status.rowIndex}" value="#[d.foo3}"/>
<e:cell column="1" row="#{status.rowIndex}" value="#[d.foo4}"/>
<e:cell column="2" row="#{status.rowIndex}" value="#[d.foo5}"/>
<e:cell column="3" row="#{status.rowIndex}" value="#[d.foo6}"/>
</e:worksheet>
--
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
15 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4373) exception handling on login and getters broken.
by deanhiller (JIRA)
exception handling on login and getters broken.
-----------------------------------------------
Key: JBSEAM-4373
URL: https://jira.jboss.org/jira/browse/JBSEAM-4373
Project: Seam
Issue Type: Bug
Components: Exception Handling
Affects Versions: 2.1.1.GA
Environment: tomcat 6.0.16 and jboss 5.0.1 and seam version above
Reporter: deanhiller
We added special code to simulate a bug in 4 different cases
1. login
2. getter method
3. setter method
4. action method
#3 and #4 failed as expected and redirected to the error page. #1 and #2 however do NOT work.
#1. redisplays the login page and does NOT execute the Seam Exceptions.handle logic to determine next page to redirect to(ie. since it does not execute this, it does not go to my error.xhtml page and just redisplays the login page with a cryptic message the user will not understand....transaction failed)...I need something to make them call support and tell them they hit a bug but in this case, it doesn't really look like a bug
#2 is even worse, it takes the exception message and displays it in the s:message after the component in the form so developer exception messages or worse....some random libraries message shows up to the user confusing them. It shows like it some normal "Number must be less than 10" error message". It also does not execute the Exceptions.handle logic which is why it is not correctly redirecting to the error.xhtml page.
This is very very bad in that if any seam apps out there have bugs(and they will of course), it does not give a nice clean "We screwed up message" to the user.
thanks,
Dean
--
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
15 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4029) NPE in JBossClusterMonitor.locateJBoss when other non-JBoss JMX servers are present
by Joshua Davis (JIRA)
NPE in JBossClusterMonitor.locateJBoss when other non-JBoss JMX servers are present
-----------------------------------------------------------------------------------
Key: JBSEAM-4029
URL: https://jira.jboss.org/jira/browse/JBSEAM-4029
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.1.GA
Environment: Seam 2.1.1.GA, JBoss AS 4.2.2.GA, JDK 1.5.0_12, Linux
Reporter: Joshua Davis
Seam 2.1.1.GA doesn't start up when there is another JMX server.
Repro:
# Specify system properties so that the sun JMX server is also started: -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
# Start JBoss with any Seam 2.1.1.GA application.
# Observe the following error on startup:
{code}
2009-03-21 17:38:51,065 [main ] INFO javax.servlet.ServletContextListener - Welcome to Seam 2.1.1.GA
2009-03-21 17:38:55,248 [main ] ERROR org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/] - Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.jmx.jbossClusterMonitor
at org.jboss.seam.Component.newInstance(Component.java:2106)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:112)
at org.jboss.seam.init.Initialization.init(Initialization.java:735)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:35)
...
Caused by: java.lang.NullPointerException
at org.jboss.seam.jmx.JBossClusterMonitor.locateJBoss(JBossClusterMonitor.java:145)
at org.jboss.seam.jmx.JBossClusterMonitor.create(JBossClusterMonitor.java:54)
...
{code}
--
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
15 years, 4 months