December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1155) Search federation

by Thomas Heute (JIRA)

Search federation ----------------- Key: JBPORTAL-1155 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1155 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.Beta1 The search federation needs to handle the federation of several search services. Each search service will be independent and can use any technology (Lucene, Hibernate Search...) -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-692) Modify all smoke tests to run in non-clustered AND clustered version.

by Ovidiu Feodorov (JIRA)

Modify all smoke tests to run in non-clustered AND clustered version. --------------------------------------------------------------------- Key: JBMESSAGING-692 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-692 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-690) Add distributed queue smoke test

by Ovidiu Feodorov (JIRA)

Add distributed queue smoke test -------------------------------- Key: JBMESSAGING-690 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-690 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-689) Add distributed topic smoke test

by Ovidiu Feodorov (JIRA)

Add distributed topic smoke test -------------------------------- Key: JBMESSAGING-689 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-689 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-691) Add failover smoke test

by Ovidiu Feodorov (JIRA)

Add failover smoke test ----------------------- Key: JBMESSAGING-691 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-691 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-598) add timeout config per client invocation

by Tom Elrod (JIRA)

add timeout config per client invocation ---------------------------------------- Key: JBREM-598 URL: http://jira.jboss.com/jira/browse/JBREM-598 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) Would like to be able to control timeout per invocation. Probably best way to do this is pass as part of metadata map passed to the invoke method within Client. -- 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, 5 months

3
5
0 / 0

[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, 5 months

6
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-793) OneToMany (parent-child) with composite PK fails when inserting a child.

by Gunnar Grim (JIRA)

OneToMany (parent-child) with composite PK fails when inserting a child. ------------------------------------------------------------------------ Key: EJBTHREE-793 URL: http://jira.jboss.com/jira/browse/EJBTHREE-793 Project: EJB 3.0 Issue Type: Bug Environment: Linux Reporter: Gunnar Grim OneToMany (parent-child) with composite PK on the child side fails when inserting a child. Only the first part of the PK has a value. Before em.persist, both key attributes have values but JBoss attempts to insert null into the second key attribute. The application works fine on Sun Java Application Server 9.0 but fails on JBoss 4.0.5-GA. The (stripped down) entity beans: @Entity @Table(name = "RelMain") public class RelMain implements Serializable { private Long itsMainID; private String itsMainText; private Set<RelSub> itsSubs; public RelMain(Long pMainID) { itsMainID = pMainID; } @Id @Column(name = "MainID", nullable = false) public Long getMainID() { return itsMainID; } public void setMainID(Long pMainID) { itsMainID = pMainID; } @Column(name = "MainText") public String getMainText() { return itsMainText; } public void setMainText(String pMainText) { itsMainText = pMainText; } @OneToMany(mappedBy="main", cascade={CascadeType.REMOVE}) public Set<RelSub> getSubs() { return itsSubs; } public void setSubs(Set<RelSub> pSubs) { itsSubs = pSubs; } } @Entity @Table(name = "RelSub") public class RelSub implements Serializable { private Long itsMainID; private String itsSubNo; private int itsSubValue; private RelMain itsMain; public RelSub(Long pMainID, String pSubNo) { itsMainID = pMainID; itsSubNo = pSubNo; } @Id @Column(name = "MainID", nullable = false) public Long getMainID() { return itsMainID; } public void setMainID(Long pMainID) { itsMainID = pMainID; } @Id @Column(name = "SubNo", nullable = false) public String getSubNo() { return itsSubNo; } public void setSubNo(String pSubNo) { itsSubNo = pSubNo; } @Column(name = "SubValue") public int getSubValue() { return itsSubValue; } public void setSubValue(int pSubValue) { itsSubValue = pSubValue; } @ManyToOne @JoinColumns({ @JoinColumn(name="MainID", insertable=false, updatable=false) }) public RelMain getMain() { return itsMain; } public void setMain(RelMain pMain) { itsMain = pMain; } } -- 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, 5 months

2
2
0 / 0

[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, 5 months

2
1
0 / 0

[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, 5 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006