[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2775) package-info.java should be optional:"convention over configuration"
by E. Jung (JIRA)
package-info.java should be optional:"convention over configuration"
--------------------------------------------------------------------
Key: JBSEAM-2775
URL: http://jira.jboss.com/jira/browse/JBSEAM-2775
Project: JBoss Seam
Issue Type: Feature Request
Reporter: E. Jung
Currently, package-info.java is required when referring to custom Seam components in components.xml. However, to further align Seam with the "convention over configuration" philosophy, this file can be optional by making some assumptions:
1. In the absence of package-info.java , the XML namespace in components.xml for custom components has a well-defined mapping to a Java package
2. This mapping can be defined as:
a. The XML namespace must be parsable by java.net.URL, otherwise automatic mapping is aborted
a. Protocol (scheme), the www/ subdomain, port, query parameters, anchors (references), and userInfo are ignored, if present.
b. The top-level domain becomes the root Java package
c. Subdomains become Java packages under the root package, applied in right-to-left order as specified in the URI.
d. The path, as returned by URL.getPath(), is mapped to further Java packages such that each path element becomes another Java package appended in left-to-right order
Examples:
http://www.company.com/department/product ==> com.company.department.product
https://company.com/department/product ==> com.company.department.product
ftp://www.company.org/department/product ==> org.company.department.product
abc://company.org/department/product ==> org.company.department.product
company.net/foo/bar/baz ==> net.company.foo.bar.baz
http://ericjung:password@www.company.com:8080/foo/bar/baz#anchor?param1=3... ==> com.company.foo.bar.baz
--
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
17 years, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2309) UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
by Denis Forveille (JIRA)
UserTransaction.commit() may throw a RollbackException(), in that case don't try to perform a UserTransaction.rollback()
------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2309
URL: http://jira.jboss.com/jira/browse/JBSEAM-2309
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.GA, 1.2.1.GA
Reporter: Denis Forveille
In the org.jboss.seam.util.Work class, the call to userTransaction.commit() is surrounded by a try/catch(Exception). In the catch block, if an exception occurs during the commit, a UserTransaction.rollback() is attempted. This may fail as the UserTransaction.commit() may throw a RollbackException, and in that case the UserTransaction ihas already been rollbacked. So an attempt to perform a rollback on the UserTransaction result in an illegalstate exception. This happens to us when something goes wrong in the beforeCommit() methods and hibernate throws a StaleObjectStateException()
We use seam 1.2.1 + POJO + WebSphere v61.0..13
The code could be something like this (Class Work.java):
try {
T result = work();
if (begin) {
log.debug("committing transaction");
userTransaction.commit();
}
return result;
} catch (Exception e) {
if (begin) {
log.debug("rolling back transaction");
if (userTransaction.getStatus() != STATUS_NO_TRANSACTION) {
userTransaction.rollback();
}
}
throw e;
}
Or the code could explicitely catch the RollbackException
This could be applied at any place in the code when a UserTransaction.commit() is called.
--
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
17 years, 12 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-884) ICEFaces dataPaginator causes duplicate ID exception
by henrik lindberg (JIRA)
ICEFaces dataPaginator causes duplicate ID exception
----------------------------------------------------
Key: JBSEAM-884
URL: http://jira.jboss.com/jira/browse/JBSEAM-884
Project: JBoss Seam
Issue Type: Bug
Components: ICE Faces Integration
Affects Versions: 1.1.6.GA
Environment: Seam 1.1.6.GA, ICEFaces 1.5.3
Reporter: henrik lindberg
Assigned To: Gregory Dick
Priority: Critical
When using a data paginator with a data table duplicate ids are created for all paginator facets except the first added facet.
The attached code illustrates the problem. Use the facelet to add test data, a duplicate id exception is thrown when a new test data is added.
Refresh the page (using browser) to see that data was added, try to add another (refresh again).
Editing out all facets for the paginator except one makes the code work.
--
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
17 years, 12 months