Recent changes to bugs

hibernate many-to-one with unique="true" gens map error

Jeff — Thu, 28 Apr 2005 15:10:52 -0000

if you try and use the 'unique' parameter in a hibernate
many-to-one mapping u end up with two entries in the
generated mapping file.

<many-to-one
name="TARequestType"

class="com.trulogica.truaccess.request.model.TAReque
stType"
cascade="none"
outer-join="auto"
update="false"
insert="false"
unique="false"
column="requestTypeId"
unique="false"
/>

Not sure if this a bug or a feature :)

HibernateDoclet fails with exception: null hibernate.xdt:168

Jeff — Thu, 28 Apr 2005 14:01:50 -0000

[hibernatedoclet] xdoclet.template.TemplateException:
Invoking method in class
xdoclet.modules.hibernate.HibernateTagsHandler failed:
ifHasCompositeId, line=168 of template file:
jar:file:C:\_cvs_\branches\Br_V35_Dev\src\lib\xdoclet\lib\ xdoclet-hibernate-module-
1.2.3.jar!/xdoclet/modules/hibernate/resources/hibernate.
xdt, exception: null

I am getting this exception when I run hibernate doclet.
It occurs in 1.2.2 and 1.2.3 but not in 1.2.1.

Anyone have any ideas what the problem could be?

has wrong at inheritance

KWK — Fri, 17 Dec 2004 15:09:32 -0000

The problem is.
I use EJB class who extends certain SUPER class who in
one's part implements certain interface.

Here is an example:

public interface MyInt {
public void test1 () throws RemoteException;
}
---------------------------------------------
public class MyImpl implements MyInt, SessionBean {
/**
* @ejb:interface-method
* @ejb:transaction type="Supports"
*/
public void test1 () {...}
}
---------------------------------------------
/**
* @ejb:bean
* name="pack.My"
* jndi-name="pack.My"
* local-jndi-name="pack.MyLocal"
* type="Stateless" transaction-type="Container"
* view-type="both"
* @ejb:interface extends="pack.MyInt,
javax.ejb.EJBObject"
* local-extends="javax.ejb.EJBLocalObject"
* @ejb:home extends="javax.ejb.EJBHome" local-
extends="javax.ejb.EJBLocalHome"
*/

public class MyEJB extends MyImpl {
/**
* @ejb:interface-method
* @ejb:transaction type="Supports"
*/
public void test2 ();
}

After generation next info appears in the ejb-jar.xml:

<container-transaction >
<method >
<ejb-name>MyImpl</ejb-name>
<method-intf>Remote</method-intf>
<method-name>test1</method-name>
<method-params>
</method-params>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>

<container-transaction >
<method >
<ejb-name>pack.My</ejb-name>
<method-intf>Remote</method-intf>
<method-name>test2</method-name>
<method-params>
</method-params>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>

I think you haven't presumed such a strange inheritance
structure but nevertheless it exists.

Hibernate 2.1 support in hibernatedoclet

Ignacio Merani — Mon, 08 Nov 2004 19:21:16 -0000

I've noticed that when you specify version 2.1 in
hibernatedoclet, some things don't work as espected.
For example in:

@hibernate.set inverse=true

the inverse attribute doesn't appear in the generated
mapping. I've tryed to map a class using both versions
(2.0 and 2.1) and the resulting mappings differs a lot,
the 2.0 generated mapping weigths 11K and the 2.1
version 7K. It seems that more atts are lost in the 2.1
version.

jboss_xml.xdt

Kevin McIntyre — Tue, 16 Mar 2004 23:06:54 -0000

Why? This is infinitely harder to keep track of ejbs
that are accessed in web apps.

<XDtClass:forAllClassTags
tagName="jboss:ejb-ref-jndi">
<ejb-ref>
<ejb-ref-name>ejb/<XDtClass:classTagValue
tagName="jboss:ejb-ref-jndi"
paramName="ref-name"/></ejb-ref-name>
<jndi-name><XDtClass:classTagValue
tagName="jboss:ejb-ref-jndi"
paramName="jndi-name"/></jndi-name>
</ejb-ref>
</XDtClass:forAllClassTags>

sample code would fail -

Bean Number 1
/**
* @ejb.bean
* name="Type"
* jndi-name="ejb/Type"
* primkey-field="id"
* cmp-version="2.x"
*
* @web.ejb-ref
* name="Type"
* description=""
* home="package.TypeHome"
* link="Type"
* remote="package.Type"
* type="Entity"
*/

Bean Number 2
/**
*
* @ejb.ejb-ref
* ejb-name="Type"
* view-type="remote"
* ref-name="Type"
*
* @jboss.ejb-ref-jndi
* jndi-name="ejb/Type"
* ref-name="Type"
*/

Invalid Transaction Details generated

Ed Hillmann — Wed, 22 Oct 2003 00:17:17 -0000

I've got an Entity Bean, and I've defined a local/local
home interface for it (no Remote Interfaces at all). On
the bean, I've got a method which is defined for the
local home, where I define that transactions are not
supported...

/**
* Validates referencing items.
*
* @ejb.home-method
* @ejb.transaction type="NotSupported"
*/

When I generate the deployment descriptor, method-
transaction entries are defined for both the local-home
and the home interfaces of the entity bean. When I
attempt to deploy my application, the container knocks
it back, because it can't find the Home interface (rightly
so, as it doesn't exist).

This occurs in the beta 3 release of 1.2, but not in the
beta 1 release.

Thanks,
Ed

dataobject template error with pkClass

Xavier Martin — Tue, 15 Oct 2002 22:32:14 -0000

This part of template produces unqualified class name
that generate compiler errors:

public <XDtEjbPk:pkClass/> getPrimaryKey() {

<XDtEjbPk:ifDoesntHavePrimkeyField>

<XDtClass:classOf><XDtEjbPk:pkClass/></XDtClass:classOf>
pk = new
<XDtClass:classOf><XDtEjbPk:pkClass/></XDtClass:classOf>(<XDtEjbPk:pkfieldListFrom
name="this"/>);

return pk;

...
}

it must be:

public <XDtEjbPk:pkClass/> getPrimaryKey() {

<XDtEjbPk:ifDoesntHavePrimkeyField>

<XDtEjbPk:pkClass/> pk = new
<XDtEjbPk:pkClass/>(<XDtEjbPk:pkfieldListFrom
name="this"/>);

return pk;

...
}

or an import statement inserted.

value-object don't work, period

M P — Mon, 07 Oct 2002 04:19:01 -0000

1.2 Beta 1

@ejb.value-object name="Something" match="*"

build.xml has <valueobject/>

No 'value' objects are generated. I don't see any
inner classes either - how do value objects differ from
Data objects anyway?

finders don't work, period

M P — Mon, 07 Oct 2002 04:16:28 -0000

1.2 Beta 1

@ejb.finder signature="java.util.Collection findAll()"

findAll is not generated.

I tried, local, remote, both.

XDoclet - incompatibilty with jdk1.4 & l

Anonymous — Fri, 04 Oct 2002 07:01:49 -0000

I recently upgraded a project from using jdk 1.3 to
jdk1.4. I then has errors with the log4j jar as the word
assert had been used which is now a keyword in 1.4. I
downloaded the latest log4j where the Category Class is
deprecated and the CategoryFactory class no longer
exists. I then got compile errors with the xdoclet.jar I
was using. I then downloaded xdoclet 1.2.0 beta which
would not unzip. I then downloaded version 1.1.2 which
is now unzipped and working. However now when I
compile I get the following error:

BUILD FAILED
file:C:/Eclipse/workspace/agent/build.xml:80:
java.lang.NoClassDefFoundError:
org/apache/log4j/Category

Total time: 3 seconds

Line "80" in build.xml is highlighted below:

<target name="ejbdoclet" depends="prepare">
<taskdef name="ejbdoclet"
classname="xdoclet.ejb.EjbDocletTask"
classpath="lib/xdoclet.jar"/>

<ejbdoclet sourcepath="${java.src}"
destdir="${java.src}"
classpathref="classpath"
packagenames="com.ag.armata.agent.entity,
com.ag.armata.agent.sf.impl"
excludedtags="@version,@author"> <=-- LINE 80!

Are the lastest xdoclet jars still using this deprecated
class? And Category does still exist in the jar which is
in my classpath so why can it not be found? The error
seems to be coming in through the xdoclet jar.