June 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-73) Follow Seam 3 example naming scheme

by Jozef Hartinger (JIRA)

Follow Seam 3 example naming scheme ----------------------------------- Key: SEAMSECURITY-73 URL: https://issues.jboss.org/browse/SEAMSECURITY-73 Project: Seam Security Issue Type: Task Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Priority: Minor Please, follow these naming constraints for the sample application to be consistent with other Seam 3 demos. {noformat} folder name: {example} artifact id: seam-{module}-example-{example} context path: {module}-{example} package: org.jboss.seam.{module}.examples.{example} {noformat} * use dashes as delimiters * if the example name uses dashes ( - ), these are removed in the package name Current violations: * openid-op ** incorrect package name * openid-rp ** incorrect package name * saml-idp ** incorrect artifact id ** incorrect context path (finalName) ** incorrect package name * saml-sp ** incorrect artifact id ** incorrect context path (finalName) ** incorrect package name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-80) NullPointer in org.jboss.seam.security.external.OpenIdPrincipalImpl.getAttribute(OpenIdPrincipalImpl.java:48) when there is no value for given alias.

by Marek Smigielski (JIRA)

NullPointer in org.jboss.seam.security.external.OpenIdPrincipalImpl.getAttribute(OpenIdPrincipalImpl.java:48) when there is no value for given alias. ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: SEAMSECURITY-80 URL: https://issues.jboss.org/browse/SEAMSECURITY-80 Project: Seam Security Issue Type: Bug Reporter: Marek Smigielski NullPointer in org.jboss.seam.security.external.OpenIdPrincipalImpl.getAttribute(OpenIdPrincipalImpl.java:48) when there is no value for given alias. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-55) Use catalog for XMLSchema hosted on w3.org in the external/ xjc goal

by Marek Schmidt (JIRA)

Use catalog for XMLSchema hosted on w3.org in the external/ xjc goal -------------------------------------------------------------------- Key: SEAMSECURITY-55 URL: https://issues.jboss.org/browse/SEAMSECURITY-55 Project: Seam Security Issue Type: Task Affects Versions: 3.0.0.Final Reporter: Marek Schmidt Priority: Minor The current xjc task downloads the http://www.w3.org/2001/XMLSchema from the w3.org, which is commonly serving only HTTP 503 responses. The build should use a local copy of the schema (catalog). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SOLDER-93) Add more thorough tests for @Requires

by Dan Allen (JIRA)

Add more thorough tests for @Requires ------------------------------------- Key: SOLDER-93 URL: https://issues.jboss.org/browse/SOLDER-93 Project: Seam Solder Issue Type: Enhancement Components: Core Affects Versions: 3.0.0.CR4 Reporter: Dan Allen Add more thorough tests for @Requires for scenarios in which the required class is referenced in the bean that relies on that class. Currently, the only reference to the required class is in the @Requires annotation as a string. Test scenarios: - @Requires on package-info.java references class on classpath - inject required class into bean in package - use required class as return value of method on bean in package - use required class a super class of bean in package - do not include injected class in shrinkwrap archive - make sure deployment succeeds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-18) Provide exception type mapping (to deal with vendor-specific exception types)

by Dan Allen (JIRA)

Provide exception type mapping (to deal with vendor-specific exception types) ----------------------------------------------------------------------------- Key: SEAMCATCH-18 URL: https://jira.jboss.org/browse/SEAMCATCH-18 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Affects Versions: Alpha2 Reporter: Dan Allen Assignee: Jason Porter There are cases when the useful information about an exception is only available in an implementation-specific exception. It would be useful to provide an exception type mapping infrastructure so that implementation-specific exceptions can be mapped to portable exception types. A classic example is JPA provider exceptions. Hibernate throws a SQLGrammarException in cases where the SQL statement is invalid (has a syntax error or refers to an invalid table/column). However, if you are writing portable JPA code, you cannot catch this exception. Thus, it would be useful to be able to catch an portable exception that represents this vendor-specific exception. Obviously, the actual mapping in this example would be done in the persistence module. Catch needs to provide some mechanism for an integration to register the mappings, which it will honor when notifying handlers. It should be noted that this is a very popular feature from Spring. Refer to SessionFactoryUtils for an example of the exception type mapping. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-56) Fix documentation

by Jason Porter (JIRA)

Fix documentation ----------------- Key: SEAMCATCH-56 URL: https://issues.jboss.org/browse/SEAMCATCH-56 Project: Seam Catch Issue Type: Task Reporter: Jason Porter Assignee: Jason Porter Add areas that are missing, clarify sections with images where possible, add a trouble shooting section -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-50) Interceptor that propagates exceptions

by Nicklas Karlsson (JIRA)

Interceptor that propagates exceptions -------------------------------------- Key: SEAMCATCH-50 URL: https://issues.jboss.org/browse/SEAMCATCH-50 Project: Seam Catch Issue Type: Feature Request Reporter: Nicklas Karlsson Assignee: Jason Porter A simple CDI interceptor that catches everything the execution throws and fires an exception handling event for them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-41) Provide SPI for registering HandlerMethod programatically

by Jozef Hartinger (JIRA)

Provide SPI for registering HandlerMethod programatically --------------------------------------------------------- Key: SEAMCATCH-41 URL: https://issues.jboss.org/browse/SEAMCATCH-41 Project: Seam Catch Issue Type: Feature Request Components: Framework Integration Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Assignee: Jason Porter It would be nice to offer registerHandlerMethod(HandlerMethod<?> method) for other modules to be able to register handler methods. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-57) Seam persistence fails in AS7 looking up the transaction manager from jndi

by Jason Porter (JIRA)

Seam persistence fails in AS7 looking up the transaction manager from jndi -------------------------------------------------------------------------- Key: SEAMPERSIST-57 URL: https://issues.jboss.org/browse/SEAMPERSIST-57 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Environment: AS7 Reporter: Jason Porter Assignee: Stuart Douglas The TransactionManager is no longer available via JNDI in AS7 whenever a transaction is started via Seam Persistence it fails when it tries to find the transaction manager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAM-93) Seam3 Booking example NPE in bookHotel on AS7

by Marek Schmidt (JIRA)

Seam3 Booking example NPE in bookHotel on AS7 --------------------------------------------- Key: SEAM-93 URL: https://issues.jboss.org/browse/SEAM-93 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Environment: jboss-7.0.0.Beta4-SNAPSHOT, build #1194, standalone Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: Future Clicking "Book Hotel" on a Hotel Details page leads to javax.ejb.EJBTransactionRolledbackException {quote} ... #{bookingAgent.bookHotel}: javax.ejb.EJBTransactionRolledbackException: javax.faces.FacesException: #{bookingAgent.bookHotel}: javax.ejb.EJBTransactionRolledbackException ... Caused by: java.lang.NullPointerException at org.jboss.seam.examples.booking.booking.BookingAgent.bookHotel(BookingAgent.java:108) [classes:] ... {quote} Seems like bookHotel not run in the same conversation scope for some reason (pretty faces issue, maybe?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2011