Set auto-import="false" for all hibernate-mapping elements in hibernate mapping files.
--------------------------------------------------------------------------------------
Key: JBPM-725
URL: http://jira.jboss.com/jira/browse/JBPM-725
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM 3.1.2, jBPM 3.1.1
Reporter: Stefan Lang
Assigned To: Tom Baeyens
The auto-import attribute of the hibernate-mapping elements in all hbm.xml files is not set.
Thus it is possible to use unqualified class names in Hibernate queries.
The problem is that name clashes with client code are very probable.
E.g. we have an "Event" entity class, jbpm has one too, so the following:
"select Event as e ..."
causes a hibernate exception.
We have set the auto-import attribute to "false" in all jbpm hbm files and
it works now as expected.
--
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
Get the jboss-4.0-testsuite-sun-1.5 passing
-------------------------------------------
Key: JBAS-3611
URL: http://jira.jboss.com/jira/browse/JBAS-3611
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Dimitris Andreadis
Fix For: JBossAS-4.0.5.GA
Container task for sun jdk1.5 test run failures
--
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
Get the ejb3-4.0 testsuite passing
----------------------------------
Key: JBAS-3582
URL: http://jira.jboss.com/jira/browse/JBAS-3582
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Dimitris Andreadis
Assigned To: Bill Burke
Fix For: JBossAS-4.0.5.CR1
There are currenlty 28 failures
--
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
Set up project in SVN
---------------------
Key: JBCLUSTER-136
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-136
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Q3Y6
Determine where in the repository the project should reside, layout project structure, etc.
--
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
Replace direct uses of Log4J by JBoss logging.
----------------------------------------------
Key: JBPORTAL-1020
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1020
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.4 Final, 2.2 Branch
Reporter: Chris Laprun
Priority: Minor
Fix For: 2.6.Alpha1
--
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
documentation for Ldap/Portal integration
-----------------------------------------
Key: JBPORTAL-1046
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1046
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Documentation
Affects Versions: 2.6.Alpha1
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.Alpha1
Create documentation of configuring Portal with LDAP. It needs to cover new implementation of identity modules in 2.6
--
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
LdapExtLoginModule should detect communication failures midstream
-----------------------------------------------------------------
Key: JBAS-3661
URL: http://jira.jboss.com/jira/browse/JBAS-3661
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.4.GA
Reporter: Anil Saldhana
Assigned To: Scott M Stark
There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the:
http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotifi...
such that it can do graceful processing.
--
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
Enable Streaming State Transfer for Cluster partition state
-----------------------------------------------------------
Key: JBAS-3515
URL: http://jira.jboss.com/jira/browse/JBAS-3515
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta
The only remaining non-JBossCache state transfer in AS 5 is for HASessionState (EJB 2x SFSBs.) But, to be complete we want to add it as an option, and use it by default.
--
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
Throw javax.ejb.ConcurrentAccessException when two threads access the same SFSB instance
----------------------------------------------------------------------------------------
Key: EJBTHREE-666
URL: http://jira.jboss.com/jira/browse/EJBTHREE-666
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Gavin King
Priority: Critical
Fix For: EJB 3.0 RC9 - FD
See section 4.13.3 of the EJB Core Contracts specification.
I need this for Seam.
--
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
IIOP binding
------------
Key: EJBTHREE-667
URL: http://jira.jboss.com/jira/browse/EJBTHREE-667
Project: EJB 3.0
Issue Type: Task
Reporter: Carlo de Wolf
Fix For: EJB 3.0 RC9 - FD
Make IIOP binding work in the EJB3 stack.
To use IIOP on an EJB bean, the following code is used:
@RemoteBinding(factory=org.jboss.ejb3.iiop.IORFactory.class)
--
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