December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAM-14) Figure out how to get ${project.version} replaces in ref guide and readme

by Dan Allen (JIRA)

Figure out how to get ${project.version} replaces in ref guide and readme ------------------------------------------------------------------------- Key: SEAM-14 URL: https://issues.jboss.org/browse/SEAM-14 Project: Seam 3 Issue Type: Task Components: Build Infrastructure Reporter: Dan Allen Assignee: Dan Allen Priority: Minor -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
5
0 / 0

[JBoss JIRA] Created: (SEAM-3) Merge "API" javadoc from IMPL to API

by Pete Muir (JIRA)

Merge "API" javadoc from IMPL to API ------------------------------------ Key: SEAM-3 URL: https://jira.jboss.org/jira/browse/SEAM-3 Project: Seam 3 Issue Type: Task Components: Build Infrastructure Reporter: Pete Muir -- 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

3
3
0 / 0

[JBoss JIRA] Created: (SOLDER-61) Write documentation for JBoss Logging

by Dan Allen (JIRA)

Write documentation for JBoss Logging ------------------------------------- Key: SOLDER-61 URL: https://issues.jboss.org/browse/SOLDER-61 Project: Seam Solder Issue Type: Feature Request Components: Documentation Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Fix For: 3.0.0.CR1 Seam Solder is the project that exposes JBoss Logging to the community (it's the face of JBoss Logging). We need a dedicated chapter on JBoss Logging: 1. What is it? 2. Why do we need it? 3. Is it portable (yes) 4. How do you use it? 5. How does tooling play in? 6. What does Solder add? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1620) "java.lang.IllegalStateException: No application context active" thrown on legacy components.xml declaration

by Przemyslaw Jaskierski (JIRA)

"java.lang.IllegalStateException: No application context active" thrown on legacy components.xml declaration ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1620 URL: http://jira.jboss.com/jira/browse/JBSEAM-1620 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: Tomcat 6.0.13 Reporter: Przemyslaw Jaskierski Fix For: 2.0.0.CR1 Reporting on Gavin's demand. After migrating from 1.3.0 ALPHA to latest 2.0.0 cvs snapshot I got this exception because on my classpath was an alternate components.xml with core:microcontainer. Please see forum topic for complete description. Posting only stacktrace here. java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1707) at org.jboss.seam.Component.getInstance(Component.java:1757) at org.jboss.seam.Component.getInstance(Component.java:1740) at org.jboss.seam.Component.getInstance(Component.java:1719) at org.jboss.seam.core.ResourceBundle.instance(ResourceBundle.java:209) at org.jboss.seam.jsf.SeamApplicationMessageBundle.handleGetObject(SeamApplicationMessageBundle.jav a:28) at java.util.ResourceBundle.getObject(ResourceBundle.java:380) at java.util.ResourceBundle.getString(ResourceBundle.java:346) at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:151) at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122) at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:828) at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:486) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:381) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Jul 7, 2007 7:21:43 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.conf ig.ConfigureListener javax.faces.FacesException: java.lang.IllegalStateException: No application context active at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:387) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1707) at org.jboss.seam.Component.getInstance(Component.java:1757) at org.jboss.seam.Component.getInstance(Component.java:1740) at org.jboss.seam.Component.getInstance(Component.java:1719) at org.jboss.seam.core.ResourceBundle.instance(ResourceBundle.java:209) at org.jboss.seam.jsf.SeamApplicationMessageBundle.handleGetObject(SeamApplicationMessageBundle.jav a:28) at java.util.ResourceBundle.getObject(ResourceBundle.java:380) at java.util.ResourceBundle.getString(ResourceBundle.java:346) at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:151) at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:122) at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:828) at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:486) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:381) ... 15 more -- 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

15 years

3
2
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-24) Add built-in configurable exception handler

by Dan Allen (JIRA)

Add built-in configurable exception handler ------------------------------------------- Key: SEAMSERVLET-24 URL: https://issues.jboss.org/browse/SEAMSERVLET-24 Project: Seam Servlet Issue Type: Feature Request Components: Catch integration Affects Versions: 3.0.0.Alpha3 Reporter: Dan Allen Assignee: Dan Allen Fix For: 3.0.0.Beta1 Add the configuration based exception handler which can be configured with Seam Config. Refer to the implementation in the REST module. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4559) Servlet Filter to pick up security information for Seam after Java EE web container security

by Anil Saldhana (JIRA)

Servlet Filter to pick up security information for Seam after Java EE web container security -------------------------------------------------------------------------------------------- Key: JBSEAM-4559 URL: https://jira.jboss.org/jira/browse/JBSEAM-4559 Project: Seam Issue Type: Feature Request Components: Security Reporter: Anil Saldhana Fix For: 3.0.0.BETA1 Shane, as discussed, it will be beneficial to have a Servlet Filter that populates the seam security layer with the results of the Web Container security enforced by the servlet container. This will not only allow seam users to utilize the Servlet Spec mandated FORM, BASIC, CLIENT-CERT, DIGEST forms of authentication but also utilize features such as SPNego (via JBoss Negotiation) out of the box with minimal configuration. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (SOLDER-59) Create utility for printing the version number of an extension

by Dan Allen (JIRA)

Create utility for printing the version number of an extension -------------------------------------------------------------- Key: SOLDER-59 URL: https://issues.jboss.org/browse/SOLDER-59 Project: Seam Solder Issue Type: Feature Request Components: Core Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Fix For: 3.0.0.CR1 Quite often, extension writers will want to log the version number of their extension for debugging, compliance or other purposes. We should provide a convenient utility for doing so, possibly even one that handles the logging itself. See CoreExtension for one example and Weld's Bootstrap class for another example. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (SOLDER-47) Cannot use Solder in Glassfish 3.1

by Jason Porter (JIRA)

Cannot use Solder in Glassfish 3.1 ---------------------------------- Key: SOLDER-47 URL: https://jira.jboss.org/browse/SOLDER-47 Project: Seam Solder Issue Type: Bug Reporter: Jason Porter Please see http://java.net/jira/browse/GLASSFISH-14808 for additional information I communicated to Siva. Siva has closed this bug saying it's not a bug because weld-extensions.jar doesn't have a beans.xml file, which isn't valid, it doesn't need one. You can see the exceptions I've been fighting trying to get my catch jaxrs example running in glassfish 3.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

6
16
0 / 0

[JBoss JIRA] Created: (SEAMJMS-2) Message Destinations may be declared by specifying a @Resource annotation as part of a producer field

by Jordan Ganoff (JIRA)

Message Destinations may be declared by specifying a @Resource annotation as part of a producer field ----------------------------------------------------------------------------------------------------- Key: SEAMJMS-2 URL: https://jira.jboss.org/browse/SEAMJMS-2 Project: Seam JMS Issue Type: Feature Request Components: Injection Reporter: Jordan Ganoff Priority: Blocker >From JSR-299-20090521.pdf: 3.7.2. Declaring a message destination A message destination may be declared by specifying a type Topic or Queue. @Resource annotation as part of a producer field declaration of The @Resource annotation specifies the metadata needed to obtain the topic or queue from the component environment. @Resource(name="java:global/env/jms/PaymentQueue") @Produces @PaymentProcessor Queue paymentQueue; @Resource(name="java:global/env/jms/Prices") @Produces @Prices Topic pricesTopic; The bindings and deployment type of the resource are determined by the producer field declaration. -- 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

15 years

2
6
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-19) Remove Weld dependency

by Shane Bryzak (JIRA)

Remove Weld dependency ---------------------- Key: SEAMREMOTING-19 URL: https://issues.jboss.org/browse/SEAMREMOTING-19 Project: Seam Remoting Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.CR1 There is some Weld-specific class usage in the remoting code related to conversation management - we need to remove this. An alternative might be to use reflection instead. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
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 December 2010