January 2011 - seam-issues - Jboss List Archives

[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

13 years, 3 months

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

13 years, 3 months

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

13 years, 3 months

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

13 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-21) Add functional tests for remoting examples

by Seam Framework (JIRA)

Add functional tests for remoting examples ------------------------------------------ Key: SEAMREMOTING-21 URL: https://issues.jboss.org/browse/SEAMREMOTING-21 Project: Seam Remoting Issue Type: Task Affects Versions: 3.0.0.Beta1 Reporter: Seam Framework Fix For: 3.0.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
5
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

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-24) Manifest.mf files in jars generated from the module contain unreachable Implementation-URL

by Martin Gencur (JIRA)

Manifest.mf files in jars generated from the module contain unreachable Implementation-URL ------------------------------------------------------------------------------------------ Key: SEAMREMOTING-24 URL: https://issues.jboss.org/browse/SEAMREMOTING-24 Project: Seam Remoting Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Martin Gencur The URL is specified in each module's pom.xml via <url>....</url>. You can override it for submodules, otherwise it will be inherited. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (SOLDER-51) Decouple service handler annotation from implementation class

by Dan Allen (JIRA)

Decouple service handler annotation from implementation class ------------------------------------------------------------- Key: SOLDER-51 URL: https://issues.jboss.org/browse/SOLDER-51 Project: Seam Solder Issue Type: Feature Request Components: Core Reporter: Dan Allen The current design of the service handler configuration prevents modules from being able to deliver a service annotation in the api since it requires a direct reference to the implementation class. @ServiceHandler(MyServiceHandler.class) Switch to either a string or adopt the annotation binding concept from CDI (like interceptors) Also, support the use of the service handler annotation on stereotypes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (SEAM-18) seam/build/checkout.sh have wrong repo name for Remoting module

by Marek Novotny (JIRA)

seam/build/checkout.sh have wrong repo name for Remoting module --------------------------------------------------------------- Key: SEAM-18 URL: https://issues.jboss.org/browse/SEAM-18 Project: Seam 3 Issue Type: Bug Reporter: Marek Novotny Checkout.sh script contains list of all Seam 3 module repos for cloning modules. Remoting module is there as js-remoting instead of remoting. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAM-1) Provide JBoss Logging 3

by Pete Muir (JIRA)

Provide JBoss Logging 3 ----------------------- Key: SEAM-1 URL: https://jira.jboss.org/jira/browse/SEAM-1 Project: Seam 3 Issue Type: Feature Request Reporter: Pete Muir JBoss Logging 3 will offer typesafe logging with built in i8ln/l10n for both log messages and exceptions -- 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, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011