[JBoss JIRA] Created: (JBAS-3776) Update SerialVersionUIDUnitTestCase to test against new versions
by Ryan Campbell (JIRA)
Update SerialVersionUIDUnitTestCase to test against new versions
----------------------------------------------------------------
Key: JBAS-3776
URL: http://jira.jboss.com/jira/browse/JBAS-3776
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Ryan Campbell
Priority: Critical
Fix For: JBossAS-4.0.6.CR1
Here is how to build the .ser database of serialVersionUIDs:
Builid jboss-4.0.5 with jdk14
cd build/output
java -XX:MaxPermSize=512m -Xmx2000m -cp ../../varia/output/classes org.jboss.tools.SerialVersionUID jboss-4.0.5.GA/
cp serialuid.ser $WORK/Branch_4_0/testsuite/src/etc/serialVersionUID/405.ser
Then the SerialVersionUIDUnitTestCase needs to be updated to test against 4.0.3SP1, 4.0.4, and 4.0.5.
The badpackages list will probably need to be different for each version.
--
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
19 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-649) Query Performance within transaction decreasing progressively when using default FlushModeType.AUTO
by Andreas Zimmer (JIRA)
Query Performance within transaction decreasing progressively when using default FlushModeType.AUTO
---------------------------------------------------------------------------------------------------
Key: EJBTHREE-649
URL: http://jira.jboss.com/jira/browse/EJBTHREE-649
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Environment: WinXP SP2, Oracle 9i Enterprise Rel. 9.2.0.1.0, JBoss 4.0.4GA, EJB3.0 RC8-FD
Reporter: Andreas Zimmer
Query Performance within a Transaction is progressively decreasing when working with EJB3.0 default FlushModeType.AUTO:
20 queries/reads within transaction - 10 msecs average per query/read
1000 (same as before) queries/reads within transaction - 130 msecs average per query/read (factor 13+)
With FlushModeType.COMMIT query performance within the same scenario ist constant at expected 10 msecs but FlushModeType.COMMIT imposes restrictions which our projects can't cope with. We need updates within transaction being visible in subsequent queries of the same transaction.
The case is explained in some detail in the JBoss Forum Thread as provided in JBoss Forum Reference.
--
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
19 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-694) @OneToOne relation fails, when foreign key is in inverse side
by Martin Isheim (JIRA)
@OneToOne relation fails, when foreign key is in inverse side
-------------------------------------------------------------
Key: EJBTHREE-694
URL: http://jira.jboss.com/jira/browse/EJBTHREE-694
Project: EJB 3.0
Issue Type: Bug
Components: EJB3 Extensions
Affects Versions: EJB 3.0 RC8 - FD
Environment: JBoss AS 4.0.4 GA3 with jboss-EJB-3.0_RC8-FD installed as described in the release.
Reporter: Martin Isheim
I defined a OneToOne relation from "UserEntity" to "PasswordEntity", with the foreign key in the "PasswordEntity" (for historical reasons).
With EntityManager.persist() the entities were inserted into the database, but the foreignKey column in "PasswordEntity" is empty.
Reading the "UserEntity" provides an empty relation.
Here the getter from "UserEntity":
<code>
private PasswordEntity password;
@OneToOne(optional = true, cascade = CascadeType.ALL)
@PrimaryKeyJoinColumn(name = "ENTITYKEY", referencedColumnName = "USERKEY")
public PasswordEntity getPassword() {
return password;
}
</code>
Since the relation is unidirectional, "PaswordEntity" has no getter/setter.
Regards.
--
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
19 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-684) Ejb3 deployer does not allow method overriding with Java 1.5 Covariant return types
by Swarn Dhaliwal (JIRA)
Ejb3 deployer does not allow method overriding with Java 1.5 Covariant return types
-----------------------------------------------------------------------------------
Key: EJBTHREE-684
URL: http://jira.jboss.com/jira/browse/EJBTHREE-684
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Environment: Jboss-4.0.4.GA with ejb3 installed using the installer 'jboss-4.0.4.GA-Patch1-installer.jar'
Reporter: Swarn Dhaliwal
We have ejb3 entities which use method overiding with java 1.5 covariant return types. The code works correctly in jboss-4.0.4rc1 with ejb3 installed using the installer.
However when trying to deploy the same code in the aforementioned version a compilation exception is thrown indicating that there are duplicate methods in the class. The code looks like the following :
public abstract class AbstractEntity {
protected abstract Object getId();
}
public class ConcreteEntity extends AbstractEntity {
public String getId() {
return id;
}
}
--
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
19 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-753) Incorect SQL with Compound Primary Keys
by SYARHEI MELESHKEVICH (JIRA)
Incorect SQL with Compound Primary Keys
---------------------------------------
Key: EJBTHREE-753
URL: http://jira.jboss.com/jira/browse/EJBTHREE-753
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Environment: Tested on JBoss 4.0.4GA and jboss-EJB-3.0_Embeddable_ALPHA_9
Reporter: SYARHEI MELESHKEVICH
Priority: Blocker
Incorect SQL with duplicate columns generates when deployng example from Java EE 5 Tutorial http://java.sun.com/javaee/5/docs/tutorial/doc/PersistenceEJB2.html
@IdClass(order.entity.LineItemKey.class)
@Entity
@Table(name = "EJB_ORDER_LINEITEM")
public class LineItem {
@Id
public int getItemId() {
return itemId;
}
@Id
@Column(name="ORDERID", nullable=false, insertable=false, updatable=false)
public Integer getOrderId() {
return orderId;
}
}
public final class LineItemKey implements java.io.Serializable {
private Integer orderId;
private int itemId;
...
public Integer getOrderId() {
return orderId;
}
...
}
generates:
insert into EJB_ORDER_LINEITEM (ORDERID, quantity, VENDORPARTNUMBER, orderId, itemId) values (?, ?, ?, ?, ?)
ORDERID comes from LineItem class and orderId from LineItemKey.
--
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
19 years, 3 months