February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-977) table creation ignores exception

by Ariane van der Steldt (JIRA)

table creation ignores exception -------------------------------- Key: EJBTHREE-977 URL: http://jira.jboss.com/jira/browse/EJBTHREE-977 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Environment: Postgresql Reporter: Ariane van der Steldt Priority: Critical When the deployment code fails to create a table, it rather silently ignores the issue. Log fragment: 2007-05-31 15:48:45,646 DEBUG [org.hibernate.tool.hbm2ddl.SchemaUpdate] create table UserRight_`group` (rights_id int8 not null, userGroups_id int8 not null) 2007-05-31 15:48:45,651 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] Unsuccessful: create table UserRight_`group` (rights_id int8 not null, userGroups_id int8 not null) 2007-05-31 15:48:45,651 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] ERROR: syntax error at or near "`" JBoss finished the whole deployment and does not give any other complaints than this. My suspicion is that SchemaUpdate catches an exception somewhere, prints this line but then forgets to pass on the exception, causing the EJB deployment to "succeed" incorrectly. Table UserRight_`group` was an automatic concatenation, due to a ManyToMany relation between entity UserRight and entity Group, where the latter was escaped using back ticks, as described here: http://jira.jboss.org/jira/browse/EJBTHREE-637 A bugreport about the incorrect name can be found here: http://jira.jboss.org/jira/browse/EJBTHREE-976 -- 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, 2 months

2
1
0 / 0

[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, 2 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, 2 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

14 years, 2 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

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JASSIST-46) repository.jboss.org does not contain latest version (3.7.0)

by Martin Burger (JIRA)

repository.jboss.org does not contain latest version (3.7.0) ------------------------------------------------------------ Key: JASSIST-46 URL: http://jira.jboss.com/jira/browse/JASSIST-46 Project: Javassist Issue Type: Task Reporter: Martin Burger Assigned To: Shigeru Chiba Jboss' Maven 2 repository does not contain version 3.7.0 of javassist: http://repository.jboss.org/maven2/org/jboss/javassist/ -- 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, 3 months

2
1
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, 3 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1434) Drools Spring

by Mark Proctor (JIRA)

Drools Spring ------------- Key: JBRULES-1434 URL: http://jira.jboss.com/jira/browse/JBRULES-1434 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Fix For: FUTURE -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1398) Document constraint weighting in the solver manual

by Geoffrey De Smet (JIRA)

Document constraint weighting in the solver manual -------------------------------------------------- Key: JBRULES-1398 URL: http://jira.jboss.com/jira/browse/JBRULES-1398 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional use examination examples? -- 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

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2008