[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, 3 months
[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">
<!-- The binary component version -->
<property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />
<!-- Pack the ejb3.deployer -->
<zip destfile="${build.lib}/ejb3-deployer.zip">
<zipfileset dir="${build.lib}">
<include name="ejb3.deployer/**" />
</zipfileset>
</zip>
<!-- Create a zip file with the component structure -->
<zip destfile="${build.lib}/jboss-ejb3-repo.zip">
<!-- The component-info.xml -->
<zipfileset dir="${build.etc}" prefix="${comp-version}">
<include name="component-info.xml" />
</zipfileset>
<!-- The bin/ejb3.deployer -->
<zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer">
<include name="ejb3-deployer.zip" />
</zipfileset>
<!-- The lib client jars -->
<zipfileset dir="${build.lib}" prefix="${comp-version}/lib">
<include name="hibernate-client.jar" />
<include name="jboss-ejb3-client.jar" />
</zipfileset>
<!-- The resources deploy descriptors -->
<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, 3 months
[JBoss JIRA] Created: (JBPORTAL-1493) Separate internal configuration state (DB / LDAP) from the exposed meta data of the property
by Julien Viet (JIRA)
Separate internal configuration state (DB / LDAP) from the exposed meta data of the property
--------------------------------------------------------------------------------------------
Key: JBPORTAL-1493
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1493
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Identity
Reporter: Julien Viet
Assigned To: Boleslaw Dawidowicz
Fix For: 2.8 Final
For example :
public String getName();
public String getType();
public String getAccessMode();
public String getUsage();
public LocalizedString getDisplayName();
public LocalizedString getDescription();
is what client of the API will care about.
public String getMappingDBType();
public String getMappingLDAPValue();
public String getMappingDBValue();
public boolean isMappedDB();
public boolean isMappedLDAP();
is an internal implementation detail that the client should not know about, as it is part of the configuration of the property, not the usage.
--
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, 5 months
[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, 5 months