September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-37) Support automatic form validation via form-validator name equality/lookup

by Lincoln Baxter III (JIRA)

Support automatic form validation via form-validator name equality/lookup ------------------------------------------------------------------------- Key: SEAMFACES-37 URL: https://jira.jboss.org/browse/SEAMFACES-37 Project: Seam Faces Issue Type: Feature Request Components: UI Components, Validation & Conversion Reporter: Lincoln Baxter III Attach a UIFormValidator to a UIForm via name resolution. If the name of the form matches the name of the validator, attach the validator to the form and enable it. -- 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

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMFACES-28) ObjectConverter and EntityConverter

by Pete Muir (JIRA)

ObjectConverter and EntityConverter ----------------------------------- Key: SEAMFACES-28 URL: https://jira.jboss.org/browse/SEAMFACES-28 Project: Seam Faces Issue Type: Feature Request Components: Transactions & Persistence, Validation & Conversion Reporter: Pete Muir Priority: Critical Given class Foo { Bar bar; // Getters and setters List<Bar> bars; // Getters and setters } <h:selectOneMenu value="#{foo.bar}" > <f:selectItems value="#{foo.bars}" var="bar" itemLabel="#{bar.label}" itemValue="#{bar}" /> <s:convertEntity /> || <s:convertObject /> </h:selectOneMenu> I want to be able to have my setter/getter reference an object and not write the boilerplate for converting to/from a string. I also want to reference a managed entity, and have that managed entity set back into the setter so I can see the changes updated in the database with no boilerplate, and avoid LIEs. -- 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

13 years, 2 months

7
12
0 / 0

[JBoss JIRA] Created: (SEAM-21) Create cluster test and automate it

by Ondrej Skutka (JIRA)

Create cluster test and automate it ----------------------------------- Key: SEAM-21 URL: https://issues.jboss.org/browse/SEAM-21 Project: Seam 3 Issue Type: Task Reporter: Ondrej Skutka Assignee: Martin Gencur Choose an appropriate example for the cluster test (princess rescue?) and automate a simple failover scenario. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4146) "no file extension in servlet path" exception whenever a servlet throws an exception

by Matthew Lieder (JIRA)

"no file extension in servlet path" exception whenever a servlet throws an exception ------------------------------------------------------------------------------------ Key: JBSEAM-4146 URL: https://jira.jboss.org/jira/browse/JBSEAM-4146 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Java 6, Tomcat 6 Reporter: Matthew Lieder Attachments: SeamTestcase1.zip Pretty easy to reproduce: call a servlet from a Seam webapp that throws an exception, which will result in a Tomcat HTTP 500 error page that ,instead of displaying the servlet's exception, displays a "no file extension in servlet path" exception. See the attached testcase. I have yet to find a good workaround; only way seems to be to hack Seam's codebase myself. The problem definitely seems to be in org.jboss.seam.mock.MockViewHandler.getActionURL(...), as indicated by JBSEAM-2921. -- 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

13 years, 2 months

13
27
0 / 0

[JBoss JIRA] Created: (SEAMINTL-15) DB-based messages and other external sources

by Nicklas Karlsson (JIRA)

DB-based messages and other external sources -------------------------------------------- Key: SEAMINTL-15 URL: https://jira.jboss.org/browse/SEAMINTL-15 Project: Seam i18n Issue Type: Feature Request Reporter: Nicklas Karlsson (hope this is not an obsolute one) Refactor the producing of the messages so that you could e.g. specialize a producer method if you want to produce messages from a DB. Currently the only way(?) is to write an extension that loads the stuff and explicitly places the messages in the appscoped component. -- 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

13 years, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (SOLDER-48) Provide injectable system properties

by Dan Allen (JIRA)

Provide injectable system properties ------------------------------------ Key: SOLDER-48 URL: https://jira.jboss.org/browse/SOLDER-48 Project: Seam Solder Issue Type: Feature Request Components: Core Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.Beta2 To compliment the generic java.util.Properties resource loader, Solder should allow the system properties (System.getProperties()) to be injected. Introduce @System for this purpose (to complement @Client): @Inject @System Properties properties; Consider naming the system properties so they can be referenced from EL. @Named("sysProp") It could then be used as: #{sysProp['os.name']} A singular name is being suggested to be consistent with other implicit EL variables, such as initParam, param and header. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
7
0 / 0

[JBoss JIRA] Created: (SEAMJMS-48) Documentation fixes for CR2

by John Ament (JIRA)

Documentation fixes for CR2 --------------------------- Key: SEAMJMS-48 URL: https://issues.jboss.org/browse/SEAMJMS-48 Project: Seam JMS Issue Type: Task Components: Documentation Affects Versions: 3.0.0.CR1 Reporter: Marek Schmidt Assignee: John Ament Fix For: 3.0.0.CR2 1. docs/reference/src/main/docbook/en-US/messaging.xml In the FormBean example, there is no QueueBuilder.send(String) method, should be sendString instead 2. docs/reference/src/main/docbook/en-US/messaging.xml "This API is still experimental, and will be tested further in Beta2." this tip should be updated or removed for CR1 3. Docbook java program listings has to be role="JAVA", (role="Java" apparently doesn't work) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-83) IdentityImpl.logout not invalidating session

by bschoen (JIRA)

IdentityImpl.logout not invalidating session -------------------------------------------- Key: SEAMSECURITY-83 URL: https://issues.jboss.org/browse/SEAMSECURITY-83 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: bschoen The method IdentityImpl.logout does not invalidate the users session. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-39) Add <distributable/> to web-fragment.xml

by Jozef Hartinger (JIRA)

Add <distributable/> to web-fragment.xml ---------------------------------------- Key: SEAMREMOTING-39 URL: https://issues.jboss.org/browse/SEAMREMOTING-39 Project: Seam Remoting Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Priority: Critical The semantics of the <distributable/> element in web.xml is such that all web fragments have to have one if the web application is supposed to be on the whole distributable. >From the JSR-315: {quote} The web.xml resulting from the merge is considered <distributable> only if all its web fragments are marked as <distributable> as well. {quote} Therefore, provided Seam Remoting can be used in a distributable application, its web-fragment should contain the tag. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMJMS-37) API declares compile-time dependency on CDI API

by Jozef Hartinger (JIRA)

API declares compile-time dependency on CDI API ----------------------------------------------- Key: SEAMJMS-37 URL: https://issues.jboss.org/browse/SEAMJMS-37 Project: Seam JMS Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Priority: Critical Fix For: 3.0.0.CR1 The scope of CDI API dependency should be "provided" instead of "compile" [INFO] org.jboss.seam.jms:seam-jms-api:jar:3.0.0.Beta2 [INFO] +- org.jboss.spec:jboss-javaee-6.0:pom:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.resource:jboss-connector-api_1.5_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar:1.0.0.Final:provided [INFO] | | \- javax.xml:jaxrpc-api:jar:1.1:provided [INFO] | | \- javax.xml.soap:saaj-api:jar:1.3:provided [INFO] | +- org.jboss.spec.javax.el:jboss-el-api_2.2_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.4_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.enterprise.deploy:jboss-jad-api_1.2_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.0_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.xml.registry:jboss-jaxr-api_1.0_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_1.1_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.servlet.jsp:jboss-jsp-api_2.2_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.0.Final:provided [INFO] | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:1.0.0.Final:provided [INFO] | +- javax.activation:activation:jar:1.1:provided [INFO] | +- com.sun.faces:jsf-api:jar:2.0.3-b05:provided [INFO] | +- javax.jws:jsr181-api:jar:1.0-MR1:provided [INFO] | +- javax.mail:mail:jar:1.4.2:provided [INFO] | +- javax.servlet:jstl:jar:1.2:provided [INFO] | +- org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar:1.0.0.Final:provided [INFO] | +- org.jboss.resteasy:jaxrs-api:jar:2.1.0.GA:provided [INFO] | +- stax:stax-api:jar:1.0.1:provided [INFO] | \- javax.validation:validation-api:jar:1.0.0.GA:provided [INFO] +- javax.enterprise:cdi-api:jar:1.0-SP4:compile [INFO] | +- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:jar:1.0.0.Final:compile [INFO] | \- javax.inject:javax.inject:jar:1:compile [INFO] \- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2011