December 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

15 years, 10 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

15 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-4651) myfaces and commons-el should only be referenced by test suite

by Stan Silvert (JIRA)

myfaces and commons-el should only be referenced by test suite -------------------------------------------------------------- Key: JBAS-4651 URL: http://jira.jboss.com/jira/browse/JBAS-4651 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert The myfaces jar and the commons-el jar are only used by the test suite. Right now they are referenced in build-thirdparty.xml in the full build. We need to figure out if these jars can be referenced by the test suite only. -- 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

15 years, 11 months

1
1
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

15 years, 11 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

15 years, 12 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

15 years, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBJMX-109) loaderRepositoryClass="..." seems to be useless

by David Schlotfeldt (JIRA)

loaderRepositoryClass="..." seems to be useless ----------------------------------------------- Key: JBJMX-109 URL: http://jira.jboss.com/jira/browse/JBJMX-109 Project: JBoss JMX Issue Type: Feature Request Affects Versions: JBossAS-4.0.0 Reporter: David Schlotfeldt This isn't exactly an error, and maybe we just aren't suppose to use it, but DTD and documentation says we can specify an implementation of org.jboss.mx.loading.LoaderRepository to use in many xml files, such as jboss-app.xml, with the loaderRepositoryClass attribute. Well even though you can -- you can't. You can't because a number of classes including UnifiedClassLoader cast objects directly to UnifiedLoaderRepository3 instead of LoaderRepository. Which means your implementations actually need to extend UnifiedLoaderRepository3. Also HeirarchicalLoaderRepository3 is not flexible. You would think it would be possible to create a hierarchy of LoaderRepositorys but you can't. This is because it expects its parent to be a UnifiedLoaderRepository3 -- okay fine, whatever. So you should at least be able a HeirarchicalLoaderRepository3 object as a parent to another HeirarchicalLoaderRepository3 object since UnifiedLoaderRepository3 extends UnifiedLoaderRepository3. You can't . Why? Well because I am PRETTY SURE that HeirarchicalLoaderRepository3.getPackageClassLoaders(..) returns a Set of PkgClassLoader objects while UnifiedLoaderRepository3 .getPackageClassLoaders(..) (the method it overrides!) returns a Set of RepositoryClassLoader objects. When HeirarchicalLoaderRepository3 calls getPackageClassLoaders(...) on its parent repository it casts items to RepositoryClassLoader , since that is what UnifiedLoaderRepository3 returns. This means if you make HeirarchicalLoaderRepository3 have a parent of type HeirarchicalLoaderRepository3 you will get a ClassCastException since.. well.. a PkgClassLoader isn't a RepositoryClassLoader class. LoadMgr3 is actually programmed to expect the Set returned by getPackageClassLoaders(...) to be both RepositoryClassLoader and PkgClassLoader objects probably because of this. I COMPLETELY understand how code gets messy through time but this code should really be cleaned up -- especially if we are allowing users to specify a LoaderRepository implementation. As it stands the loaderRepositoryClass attribute SEEMS to be useless to specify your own implementation. -- 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

16 years

3
2
0 / 0

[JBoss JIRA] Created: (JASSIST-39) failure to compile an instance method which invokes a static method in a different class and both methods have the same return type, name and argument types

by twieger (JIRA)

failure to compile an instance method which invokes a static method in a different class and both methods have the same return type, name and argument types ------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JASSIST-39 URL: http://jira.jboss.com/jira/browse/JASSIST-39 Project: Javassist Issue Type: Bug Reporter: twieger Assigned To: Shigeru Chiba The testcase below demonstrates the problem. The first invocation of CtNewMethod#make works, the second one fails. It looks like the problem is related with MemberResolver#lookupMethod. The check to enable the creation of a recursively called method is not precise enough. It actually succeeds, although the current method is an instance method, and the method which shall be invoked is a static method. ========================================== package experimental; import javassist.CannotCompileException; import javassist.ClassPool; import javassist.CtClass; import javassist.CtNewMethod; import org.testng.annotations.Test; public class TestJavaAssist { @Test public void testJavaAssist() throws CannotCompileException { ClassPool classPool = new ClassPool(); classPool.appendSystemPath(); CtClass ctClass = classPool.makeClass("Test"); CtNewMethod.make("public String foox(){return experimental.TestJavaAssist.foo();}", ctClass); CtNewMethod.make("public String foo(){return experimental.TestJavaAssist.foo();}", ctClass); } public static final String foo() { return "foo"; } } -- 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

16 years

2
1
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

16 years

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1793) Isolate management code in a management sub module for the identity module

by Julien Viet (JIRA)

Isolate management code in a management sub module for the identity module -------------------------------------------------------------------------- Key: JBPORTAL-1793 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1793 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: Identity-1.0 Reporter: Julien Viet Assigned To: Boleslaw Dawidowicz Fix For: Identity-1.1 -- 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

16 years

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 2007