-Brian
On Tuesday, October 21, 2003, at 05:48 PM, Armin Waibel wrote:
Hi Brian,
On Tue, 21 Oct 2003 17:37:22 -0400, Brian McCallister <[EMAIL PROTECTED]> wrote:
17:29:48,031 INFO [STDOUT] Candidate object [EMAIL PROTECTED] class [com.forthillcompany.eva.model.Profile] is not a subtype of [com.forthillcompany.eva.model.Profile] or any type of proxy. NOT INCLUDED in result collection
OJB is deployed as a sar, using the following descriptor for the class:
<class-descriptor class="com.forthillcompany.eva.model.Profile" table="Profiles">
<field-descriptor name="profileId" column="profileid" jdbc-type="INTEGER"
primarykey="true" autoincrement="true" sequence-name="UniqueIdentifier"
/>
<field-descriptor name="login" column="login" jdbc-type="VARCHAR"/>
<field-descriptor name="passcode" column="passcode" jdbc-type="VARCHAR"/>
<field-descriptor name="email" column="email" jdbc-type="VARCHAR"/>
<collection-descriptor name="users" element-class-ref="com.forthillcompany.eva.model.User">
<inverse-foreignkey field-ref="profileId"/>
</collection-descriptor>
</class-descriptor>
The only oddity is that the repository-xml is deployed in the sar, seperate from the ejb deployment (am using sessions beans to access OJB). Am thinking that there may be a classloader issue between the sar and session beans.
Think you are right. Try to include the all OJB jars (+ libraries) and your bean jars in the sar.
regards, Armin
JBoss 3.2.2, OJB from cvs this morning.
-Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
