September 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3445) s:defaultAction doesn't work for h:commandLink

by Pete Muir (JIRA)

s:defaultAction doesn't work for h:commandLink ---------------------------------------------- Key: JBSEAM-3445 URL: https://jira.jboss.org/jira/browse/JBSEAM-3445 Project: Seam Issue Type: Bug Components: JSF Controls Reporter: Pete Muir Fix For: 2.1.1.CR1 -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2519) SeamTest class does not support dependent testing

by Olivier Thierry (JIRA)

SeamTest class does not support dependent testing ------------------------------------------------- Key: JBSEAM-2519 URL: http://jira.jboss.com/jira/browse/JBSEAM-2519 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: Seam 2.0.0.GA + TestNG 5.1 + Maven Surefire plugin Reporter: Olivier Thierry When you use dependent testing in a test class extending SeamTest, either with dependsOnGroups or dependsOnMethods, the test crash on begin phase with the following stack trace : begin(fr.myCompany.test.ServiceOrganisationTest) Time elapsed: 0.126 sec <<< FAILURE! java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:169) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124) at org.jboss.seam.mock.BaseSeamTest.begin(BaseSeamTest.java:920) at org.jboss.seam.mock.SeamTest.begin(SeamTest.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:552) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:322) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:156) at org.testng.internal.Invoker.invokeMethod(Invoker.java:365) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:785) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) at org.testng.TestRunner.privateRun(TestRunner.java:693) at org.testng.TestRunner.run(TestRunner.java:574) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:241) at org.testng.SuiteRunner.run(SuiteRunner.java:145) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901) at org.testng.TestNG.runSuitesLocally(TestNG.java:863) at org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:69) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:78) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) -- 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

16 years, 2 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2346) s:selectItems - noSelectionLabel is not hidden after first selection of a value

by Wolfgang Schwendt (JIRA)

s:selectItems - noSelectionLabel is not hidden after first selection of a value ------------------------------------------------------------------------------- Key: JBSEAM-2346 URL: http://jira.jboss.com/jira/browse/JBSEAM-2346 Project: JBoss Seam Issue Type: Bug Environment: CVS-based Seam 2.0.1 Reporter: Wolfgang Schwendt Priority: Minor <s:selectItems> offers that the user can specify an (optional) "noSelectionLabel" to be placed at the top of the selection list. It further provides a hideNoSelectionLabel option -- if this property is true, the noSelectionLabel will be hidden when a value is selected. And exactly the latter functionality has a bug, but only as far as the user's FIRST selection is concerned. When the users makes his _first_ selection and submits the form, then the noSelectionLabel is still displayed when the page is redisplayed by the server, no matter whether or not hideNoSelection was set to "true". However, when the users makes additional requests, the hideNoSelectionLabel functionality works correctly. Reason for the bug: caching behavior of org.jboss.seam.ui.component.UISelectItems.getValue() Too understand why there is a bug, consider the following scenario: A page with <h:selectOneMenu> and <s:selectItems var="myVar" label="#{myVar.name}" value="#{resultList}" noSelectionLabel="* Your choice please *" hideNoSelectionLabel="true"/> as its child component. When the user makes a selection and submits the form, the UISelectOne components checks during the "Process validations" JSF phase whether the submitted input value matches one of the available options (SelectItems). Consequently, the UISelectOne component calls the getValue() method of its org.jboss.seam.ui.component.UISelectItems child component in order to retrieve a list of SelectItem s. Then, if if validation was successful because a matching value was found, the user's selection is either written to the model (during JSF Update model phase) or if we don't make it to the Update model phase, because some other component had a validation error, the user's selection is stored in the value property of the UISelectOne component. When we finally reach the "Render response" phase and the same page should be redisplayed, the UISelectOne component gets rendered again. In order to render the selection list items, org.jboss.seam.ui.component.UISelectItems.getValue() gets called another time. But now it doesn't re-calculate its list of SelectItems. Take a look at the code: org.jboss.seam.ui.component.UISelectItems.getValue() @Override public Object getValue() { if (value == null || originalValue == null || !originalValue.equals(super.getValue())) { ... } return value; } Note that "value" is not null, because during "Process validations" org.jboss.seam.ui.component.UISelectItems.getValue() was already called which lead to value being set. Therefore, getValue() returns the OLD cached list of SelectItem s, which was calculated during Process Validations and therefore still includes the noSelectionLabel! And therefore getValue() doesn't take into account that the user made a selection and that the noSelectionLabel should now be hidden. -- 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

16 years, 2 months

9
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3906) Attachements are not shown in outlook

by Milos Zikic (JIRA)

Attachements are not shown in outlook ------------------------------------- Key: JBSEAM-3906 URL: https://jira.jboss.org/jira/browse/JBSEAM-3906 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Any Reporter: Milos Zikic Assignee: Pete Muir When sending mail with attachements, attachments are not shown in Outlook 2007. -- 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

16 years, 2 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2578) Provide support for creating bookmarks in pdf

by Terry (JIRA)

Provide support for creating bookmarks in pdf --------------------------------------------- Key: JBSEAM-2578 URL: http://jira.jboss.com/jira/browse/JBSEAM-2578 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.CR2 Environment: n/a Reporter: Terry Priority: Minor Fix For: 2.1.0.GA Provide support to add bookmarks in pdf generated by seam. bookmark appears as an index which when clicked jump to certain section of the page. -- 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

16 years, 3 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3776) Update release-process with cluster testing steps

by Jay Balunas (JIRA)

Update release-process with cluster testing steps ------------------------------------------------- Key: JBSEAM-3776 URL: https://jira.jboss.org/jira/browse/JBSEAM-3776 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.1.2.GA We need to add some basic cluster testing steps to the release process. This is closely related to JBSEAM-3397. -- 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

16 years, 3 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3989) Map conversations to URI spaces for REST integration

by Christian Bauer (JIRA)

Map conversations to URI spaces for REST integration ---------------------------------------------------- Key: JBSEAM-3989 URL: https://jira.jboss.org/jira/browse/JBSEAM-3989 Project: Seam Issue Type: Feature Request Components: WS Reporter: Christian Bauer Some old feature idea: We'll probably have a mechanism for transporting conversation identifiers in HTTP headers. However, I'm thinking that the way this should be implemented is with explicit automatically created resources that identify a particular conversation "workspace". See Bill's blog about JMS integration and how you'd model a transaction resource RESTfully. This is the same approach just for Seam conversations. -- 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

16 years, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3988) Support for mapping RESTful XHTML resource representations with Facelets templates

by Christian Bauer (JIRA)

Support for mapping RESTful XHTML resource representations with Facelets templates ---------------------------------------------------------------------------------- Key: JBSEAM-3988 URL: https://jira.jboss.org/jira/browse/JBSEAM-3988 Project: Seam Issue Type: Feature Request Components: WS Reporter: Christian Bauer Assignee: Jozef Hartinger What I wrote a while ago about this feature: I'm thinking about a special provider that can marshal an object graph into an XHTML (not just XML) response body and back from an XHTML request body to an object graph. This is about the "connectedness" of resources, see the O'Reilly REST book. As a developer I should write a Facelets XHTML template that defines the transformation. Imagine that you write it the same way you write a JSF template today, with bidirectional binding using EL expressions, from object getter/setter pair to XML attribute or element value. We can even have built-in Facelets "widgets" that render certain microformats. Seam has some machinery for this already but we might need an extra interceptor on resource methods to trigger the transformation. Or we use Seams pages.xml navigation rules ("when this resource method finishes, render this template"). Later I did some prototype experiments - note that this only considers uni-directional mapping for GET, handling POST/PUT resource representation is more difficult: package org.jboss.seam.resteasy; import java.lang.annotation.*; /** * @author Christian Bauer */ @Target({ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) @Documented @Inherited public @interface FaceletsXhtmlResponse { String template(); } package org.jboss.seam.resteasy; import org.jboss.seam.core.Interpolator; import org.jboss.seam.faces.Renderer; import org.jboss.seam.log.Log; import org.jboss.seam.log.Logging; import javax.ws.rs.ProduceMime; import javax.ws.rs.core.MediaType; import javax.ws.rs.core.MultivaluedMap; import javax.ws.rs.ext.MessageBodyWriter; import javax.ws.rs.ext.Provider; import java.io.IOException; import java.io.OutputStream; import java.lang.annotation.Annotation; import java.lang.reflect.Type; /** * @author Christian Bauer */ @Provider @ProduceMime("application/xhtml+xml") public class FaceletsXhtmlProvider implements MessageBodyWriter<Object> { Log log = Logging.getLog(FaceletsXhtmlProvider.class); public boolean isWriteable(Class<?> type, Type genericType, Annotation[] annotations) { for (Annotation annotation : annotations) { if (annotation.annotationType().equals(FaceletsXhtmlResponse.class)) { return true; } } return false; } public long getSize(Object o) { return -1; } public void writeTo(Object o, Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType, MultivaluedMap<String, Object> httpHeaders, OutputStream entityStream) throws IOException { log.debug("writing XHTML response for entity type: " + type.getName()); FaceletsXhtmlResponse respAnnotation = null; for (Annotation annotation : annotations) { if (annotation.annotationType().equals(FaceletsXhtmlResponse.class)) respAnnotation = (FaceletsXhtmlResponse) annotation; } if (respAnnotation == null) throw new IllegalStateException("@FaceletsXhtmlResponse annotation disappeared"); String template = getTemplatePath(respAnnotation); log.debug("rendering XHTML template: " + template); String output = Renderer.instance().render(template); entityStream.write(output.getBytes()); } protected String getTemplatePath(FaceletsXhtmlResponse annotation) { return isTemplatePathInterpolated() ? Interpolator.instance().interpolate(annotation.template()) : annotation.template(); } protected boolean isTemplatePathInterpolated() { return true; } } @Name("customerResource") @Path("/customer") public class CustomerResource { @GET @ProduceMime("application/xhtml+xml") @FaceletsXhtmlResponse( template = "#{somePath}/customerTemplate.xhtml" ) @Out(value = "customers", scope = ScopeType.EVENT) public List<Customer> getCustomers() { return mockCustomers(); } } <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:t="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core"> <head> <title>Customers</title> </head> <body> <ul> <t:repeat var="cust" value="#{customers}"> <li> <h:outputText value="#{cust.name}"/> </li> </t:repeat> </ul> </body> </html> -- 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

16 years, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3703) bug in JbpmElResolver

by Gergely Nagy (JIRA)

bug in JbpmElResolver --------------------- Key: JBSEAM-3703 URL: https://jira.jboss.org/jira/browse/JBSEAM-3703 Project: Seam Issue Type: Bug Components: BPM Reporter: Gergely Nagy I could not pass a jbpm context variable to a seam component. I'm using seam 2.0.2.SP1, but the same code is still present in trunk. I tracked down the bug to the following method in class org.jboss.seam.bpm.JbpmELResolver public Object getValue(ELContext context, Object base, Object property) { if ( base==null && property!=null ) { return resolver.resolveVariable( (String) base ); } else { return null; } } note that base is passed into resolveVariable instead of property. I think it should be property. also, the isResolved property of ELContext is not set to true. If i manually set these two values in a debugging session, the code worked as expected. Proposed fix: public Object getValue(ELContext context, Object base, Object property) { if ( base==null && property!=null ) { context.setPropertyResolved(true); return resolver.resolveVariable( (String) property ); } else { return null; } } A bit more context: I had this in my workflow description: <task-node name="importanttask"> <task name="justdoit"> <assignment pooled-actors="#seamcomponent.getActor(taskInstance)}"/> </task> <transition to="nextstep" name="donext"/> </task-node> Without the above fix, the getActor() method on seamcomponent is called with null, with the fix i get passed in the actual task instance. -- 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

16 years, 3 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4133) Add converters support into e:cell

by Alexey Kakunin (JIRA)

Add converters support into e:cell ---------------------------------- Key: JBSEAM-4133 URL: https://jira.jboss.org/jira/browse/JBSEAM-4133 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Environment: CentOS 5.2, Java 1.6 Reporter: Alexey Kakunin Priority: Minor It whould be nice to be able to add converters for cells in Excel export (e:cell tag). In this case will will allow to use same objects, as used to display normal HTML tables, but cuntrol output text by converters (like we are doing to HTML table) -- 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

16 years, 3 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2009