August 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-67) security-openid-rp/op examples fail with 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed

by Marek Schmidt (JIRA)

security-openid-rp/op examples fail with 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed ------------------------------------------------------------------------------------------------------------------------------- Key: SEAMSECURITY-67 URL: https://issues.jboss.org/browse/SEAMSECURITY-67 Project: Seam Security Issue Type: Bug Environment: JBossAS 6.1.0-SNAPSHOT+Weld 1.1.1 Reporter: Marek Schmidt Since the upgrade of OpenID4Java to 0.9.6 the openid example combo (security-openid-rp/op) fails with HTTP Status 400 - 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed The example seems to work fine if downgraded to 0.9.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-75) security-openid-rp/op examples fail on AS7 with 0x704: I/O transport error

by Marek Schmidt (JIRA)

security-openid-rp/op examples fail on AS7 with 0x704: I/O transport error -------------------------------------------------------------------------- Key: SEAMSECURITY-75 URL: https://issues.jboss.org/browse/SEAMSECURITY-75 Project: Seam Security Issue Type: Bug Environment: jboss-7.0.0.Beta4-SNAPSHOT, build 1199 Reporter: Marek Schmidt Fix For: Future Attachments: server.log The openid examples fail on AS7 with the following HTTP 400 error. Note that the steps to reproduce are the same SEAMSECURITY-67, but this is a different issue, as this is a different error message and also occurs with OpenID4Java 0.9.5 {quote} HTTP Status 400 - 0x704: I/O transport error: type Status report message 0x704: I/O transport error: description The request sent by the client was syntactically incorrect (0x704: I/O transport error: ). {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-182) BeanManager from ServletContext in RewriteConfiguration is NULL with OWB

by Thomas Andraschko (JIRA)

BeanManager from ServletContext in RewriteConfiguration is NULL with OWB ------------------------------------------------------------------------ Key: SEAMFACES-182 URL: https://issues.jboss.org/browse/SEAMFACES-182 Project: Seam Faces Issue Type: Bug Components: CDI Integration, Configuration API Affects Versions: 3.0.1 Environment: Tomcat 7, OWB 1.1.0, MyFaces 2.0.5 or 2.1.1, SeamFaces 3.0.1, SeamPersistence 3.0.0, SeamXmlConfig 3.0.0 Reporter: Thomas Andraschko Priority: Critical BeanManager from ServletContext in RewriteConfiguration is NULL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-169) Seam Faces does not work with OWB

by Thomas Andraschko (JIRA)

Seam Faces does not work with OWB --------------------------------- Key: SEAMFACES-169 URL: https://issues.jboss.org/browse/SEAMFACES-169 Project: Seam Faces Issue Type: Bug Components: Build & Distribution, CDI Integration Affects Versions: 3.0.1 Environment: Tomcat 7, OWB 1.1.0, MyFaces 2.0.5 or 2.1.0, SeamFaces 3.0.1, SeamPersistence 3.0.0, SeamXmlConfig 3.0.0 Reporter: Thomas Andraschko SeamFaces does not work with OWB. Following exception occurs: 07.06.2011 13:25:17 org.apache.myfaces.webapp.AbstractFacesInitializer initFaces SCHWERWIEGEND: An error occured while initializing MyFaces: null java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:796) at java.util.HashMap$KeyIterator.next(HashMap.java:828) at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:25) at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:43) at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:34) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43) at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2105) at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:118) at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2292) at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:537) at javax.faces.application.ApplicationWrapper.publishEvent(ApplicationWrapper.java:329) at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:248) at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:140) at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4521) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5004) at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:4999) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 07.06.2011 13:25:17 org.apache.catalina.core.StandardContext startInternal SCHWERWIEGEND: Error listenerStart 07.06.2011 13:25:17 org.apache.catalina.core.StandardContext startInternal SCHWERWIEGEND: Context [/my-webapp] startup failed due to previous errors 07.06.2011 13:25:17 org.apache.webbeans.web.lifecycle.WebContainerLifecycle afterStopApplication INFO: OpenWebBeans Container was stopped for context path, [/my-webapp] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
8
0 / 0

[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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 8 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

12 years, 8 months

7
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2011