May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-929) SQL Exception when entities with composite keys are retrieved

by Venkat Kakula (JIRA)

SQL Exception when entities with composite keys are retrieved ------------------------------------------------------------- Key: EJBTHREE-929 URL: http://jira.jboss.com/jira/browse/EJBTHREE-929 Project: EJB 3.0 Issue Type: Bug Environment: Windows XP SP2; JBoss 4.0.5 GA with EJB 3.0 Reporter: Venkat Kakula After migrating an OC4J/TopLink Essentials project to JBoss/Hibernate, there were some breakdowns. I have some entities with composite keys (specifically - 4 ID fields). There is a separate ID Key class. These field names do not match the database fields directly but are mapped with @Column(name="A_B_C" nullable="false") style notation with the field names as aBC. The SQL generated thus looks for 'TABLEONE0_'.'aBC' specifically on the ID fields of the entity instead of 'TABLEONE0_'.'A_B_C' they should be mapping to. The rest of the attributes map out alright. By the way I just wanted to note that all the code that is breaking down was working fine on OC4J with toplink - FYI. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-789) build.xml and component-info.xml - version numbers and imports need to be updated

by Vladimir Ralev (JIRA)

build.xml and component-info.xml - version numbers and imports need to be updated --------------------------------------------------------------------------------- Key: EJBTHREE-789 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Vladimir Ralev Priority: Critical The repository-zip target's comp-version, like this (use appropriate version string): <target name="repository-zip" depends="jars" description="Create the repository.jboss.com jboss/ejb3 component contents">  <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />  <zip destfile="${build.lib}/ejb3-deployer.zip"> <zipfileset dir="${build.lib}"> <include name="ejb3.deployer/**" /> </zipfileset> </zip>  <zip destfile="${build.lib}/jboss-ejb3-repo.zip">  <zipfileset dir="${build.etc}" prefix="${comp-version}"> <include name="component-info.xml" /> </zipfileset>  <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer"> <include name="ejb3-deployer.zip" /> </zipfileset>  <zipfileset dir="${build.lib}" prefix="${comp-version}/lib"> <include name="hibernate-client.jar" /> <include name="jboss-ejb3-client.jar" /> </zipfileset>  <zipfileset dir="${build.lib}" prefix="${comp-version}/resources"> <include name="ejb3-clustered-sfsbcache-service.xml" /> <include name="ejb3-entity-cache-service.xml" /> <include name="ejb3-interceptors-aop.xml" /> </zipfileset> </zip> </target> and ejb3\src\etc\component-info.xml (the version attribute): <project name="jboss/ejb3-component-info"> <component id="jboss/ejb3" licenseType="lgpl" version="1.0.0.CR9-jboss4.0.5" description="The EJB3 deployer for integration with jboss-4.0.x"> <artifact id="ejb3-clustered-sfsbcache-service.xml"/> <artifact id="ejb3-entity-cache-service.xml"/> <artifact id="ejb3-interceptors-aop.xml"/> <artifact id="ejb3.deployer" /> <artifact id="hibernate-client.jar"/> <artifact id="jboss-ejb3-client.jar"/> <import componentref="javassist"> <compatible version="3.2.0.CR1"/> <compatible version="3.2.0.CR2"/> </import> <import componentref="hibernate-annotations"> <compatible version="3.2.0.GA"/> </import> <import componentref="hibernate-entitymanager"> <compatible version="3.2.0.GA"/> </import> <import componentref="jboss/remoting"> <compatible version="1.4.1_final"/> <compatible version="1.4.2.GA"/> </import> <import componentref="jboss/aop"> <compatible version="1.5.1.GA"/> <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE? </import> <export> <include input="hibernate-client.jar"/> <include input="jboss-ejb3-client.jar"/> </export> </component> </project> -- 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

14 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBRULES-789) I am trying to execute Fibonnaci program of jboss examples but it is giving following error "org.drools.rule.InvalidRulePackage: Rule Compilation error The operator + is undefined for the argument type(s) Integer, int The operator + is undefined for the "

by Venkat Garlapati (JIRA)

I am trying to execute Fibonnaci program of jboss examples but it is giving following error "org.drools.rule.InvalidRulePackage: Rule Compilation error The operator + is undefined for the argument type(s) Integer, int The operator + is undefined for the " --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-789 URL: http://jira.jboss.com/jira/browse/JBRULES-789 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Eclipse with Jboss Rules 3.0.5 plugin Reporter: Venkat Garlapati Assigned To: Mark Proctor -- 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3648) Need a clustered ejb compatibility test

by Scott M Stark (JIRA)

Need a clustered ejb compatibility test --------------------------------------- Key: JBAS-3648 URL: http://jira.jboss.com/jira/browse/JBAS-3648 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-3.2.8.SP1 Reporter: Scott M Stark Assigned To: Brian Stansberry We need a test of a 3.2.x client talking to a 4.0.x clustered ejb to validate interop. -- 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

14 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3925) Unification of transports to Remoting 2.2.0

by Scott M Stark (JIRA)

Unification of transports to Remoting 2.2.0 ------------------------------------------- Key: JBAS-3925 URL: http://jira.jboss.com/jira/browse/JBAS-3925 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, EJB2, EJB3, JB5-Messaging, Naming, Remoting Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta2 We need to drop the legacy transports and align on remoting implementations based on the 2.2.0 release of remoting. This task is a container for the subtasks needed to accomplish this. -- 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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3927) Update naming service to using remoting based proxy

by Scott M Stark (JIRA)

Update naming service to using remoting based proxy --------------------------------------------------- Key: JBAS-3927 URL: http://jira.jboss.com/jira/browse/JBAS-3927 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Naming, Remoting Reporter: Scott M Stark Assigned To: Scott M Stark The integration of the NamingService with the legacy detached invoker needs to be factored out and replaced with a remoting based proxy. -- 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

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1343) Create an Ant task to execute a TestDriver

by Julien Viet (JIRA)

Create an Ant task to execute a TestDriver ------------------------------------------ Key: JBPORTAL-1343 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1343 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Fix For: 2.8 Final An org.jboss.portal.common.test.driver.TestDriver is executed in Ant though the usage of the org.jboss.portal.common.test.junit.JUnitAdapter which adaps the TestDriver protocol to junit. It has several limitations : - the way to pass parameters to the test driver is convoluted and basically an hack (that works) - it is not possible to filter the set of tests returned by the TestDriver easily which force many times to create subclasses in order to execute each test separately -- 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-133) Figure out how to generically do the equivalent of setAccessible() for the javassist constructed reflection objects

by Adrian Brock (JIRA)

Figure out how to generically do the equivalent of setAccessible() for the javassist constructed reflection objects ------------------------------------------------------------------------------------------------------------------- Key: JBMICROCONT-133 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-133 Project: JBoss MicroContainer Issue Type: Task Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock See the associated forum discussion and the TODO in JavassistReflectionFactory -- 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

14 years, 6 months

5
14
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-127) ClassInfo tests testing annotation attribute values

by Adrian Brock (JIRA)

ClassInfo tests testing annotation attribute values --------------------------------------------------- Key: JBMICROCONT-127 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-127 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Need to write some tests for the annotation attributes in the main ClassInfo tests. Currently, it only tests that it got the correct annotations, not that those annotations have the correct values. Kabir does have some other basic "standup tests" for this, but they are not excercising all the edge cases. -- 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

14 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-118) Fix the introspection assumption in ClassInfo

by Adrian Brock (JIRA)

Fix the introspection assumption in ClassInfo --------------------------------------------- Key: JBMICROCONT-118 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-118 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Priority: Minor Fix For: JBossMC_2_0_0_CR1 Although the javassist version of the ClassInfo works fine, there are still some places in the base ClassInfoImpl that assume introspection (i.e. java.lang.reflect objects). The javassist impl works around these issues by subclassing. Additionally, the deprecated ClassInfo.getType() needs removing. This will require understanding where it is currently used and fixing it (I think it is mainly related to determining the classloader?) Moving this method and its dependencies to the ReflectClassInfoImpl Whether we actually remove the deprecated method is another issue since it is useful to temporarily fix problems (in future) where we don't provide an equivalent in the ClassInfo api. -- 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

14 years, 6 months

6
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007