You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Ate Douma <at...@douma.nu> on 2004/04/22 14:20:38 UTC
Re: [J2] Unable to use Oacle for J2 because of problems with OBJ,
Torque and HSQLDB dependencies: OJB FieldConversion
Related to my previous mail (HSQLDB reliability) is the mapping of
JetspeedObjectID to an INTEGER field in OJB repository_registry.xml.
After I found out about the problem of the mapping I searched for a way
to let OJB do an conversion.
The FieldConversion interface is available for that and it turned out
that an implementation for JetspeedObjectID was already written, just
not used yet (or anymore).
After looking up the first reference to a JetspeedObjectID I found in
that for the PortletApplicationDefinitionImpl.id mapping the conversion
attribute referencing the ObjectIDtoLongFieldConversion implementation
of FieldConversion was commented out. So I enabled it again.
Wrong. Now I got an IllegalArgumentException thrown.
I've attached the test case result which shown the error and stack trace
for it.
Note: I did put logging messages in the ObjectIDtoLongFieldConversion
sqlToJava and javaToSql methods to see what was passed in and you'll
notice one of these (sqlToJava) in the test case results.
What is going wrong here I really don't know as this probably requires
detailed OJB knowledge which I don't have.
I have a bad feeling though it could be related to the fact that this id
field has autoincrement defined and from the error log you can see the
problem seems to come from code handling that. If thats the cause of it
then probably OJB doesn't support FieldConversion for autoincrement
fields which would be a real bummer as it really is required here.
Anyway, I leave this to the OJB expects to look into it. My current
expertise ends here. I saw Brian McCallister joined the club so maybe he
can shine some light on this?
Well, this is the last problem for now I have to get Oracle usage.
Hopefully once these are resolved no other will pop up (note I didn't
got passed the allBuild yet, running J2 is still way off as such).
I am more than willing to test any workaround or fix on oracle so as
soon as anyone got something to test just let me know.
Regards,
Ate
Ate Douma wrote:
> I've created Blocking issue JS2-18 last night after a long frustrated
> day trying to get J2 ready to use Oracle as db.
>
> In that issue I identified (at least) 5 major problems I like to ask
> attention to.
>
> Although JIRA is fine for issue tracking I think the mailing list is
> more interactive to discuss these issues.
> Therefore I created this mail as a wrapper for the several problems
> which I will describe separately as reply to this mail.
>
> I am very dependent on Oracle for running J2 as it is required for my
> client. Furthermore, in our project we will start developing portlets
> based on J2 any time now (I know its kind of early for that but we need
> some result before the summer and hopefully our development will provide
> lots of feedback to J2 to help it get out of the door sooner).
>
> Regards, Ate
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>
> .
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [J2] Unable to use Oacle for J2 because of problems with OBJ,
Torque and HSQLDB dependencies: OJB FieldConversion
Posted by Ate Douma <at...@douma.nu>.
Sorry, forgot to attach the test case result
Ate Douma wrote:
> Related to my previous mail (HSQLDB reliability) is the mapping of
> JetspeedObjectID to an INTEGER field in OJB repository_registry.xml.
>
> After I found out about the problem of the mapping I searched for a way
> to let OJB do an conversion.
> The FieldConversion interface is available for that and it turned out
> that an implementation for JetspeedObjectID was already written, just
> not used yet (or anymore).
>
> After looking up the first reference to a JetspeedObjectID I found in
> that for the PortletApplicationDefinitionImpl.id mapping the conversion
> attribute referencing the ObjectIDtoLongFieldConversion implementation
> of FieldConversion was commented out. So I enabled it again.
> Wrong. Now I got an IllegalArgumentException thrown.
> I've attached the test case result which shown the error and stack trace
> for it.
> Note: I did put logging messages in the ObjectIDtoLongFieldConversion
> sqlToJava and javaToSql methods to see what was passed in and you'll
> notice one of these (sqlToJava) in the test case results.
>
> What is going wrong here I really don't know as this probably requires
> detailed OJB knowledge which I don't have.
> I have a bad feeling though it could be related to the fact that this id
> field has autoincrement defined and from the error log you can see the
> problem seems to come from code handling that. If thats the cause of it
> then probably OJB doesn't support FieldConversion for autoincrement
> fields which would be a real bummer as it really is required here.
>
> Anyway, I leave this to the OJB expects to look into it. My current
> expertise ends here. I saw Brian McCallister joined the club so maybe he
> can shine some light on this?
>
> Well, this is the last problem for now I have to get Oracle usage.
> Hopefully once these are resolved no other will pop up (note I didn't
> got passed the allBuild yet, running J2 is still way off as such).
>
> I am more than willing to test any workaround or fix on oracle so as
> soon as anyone got something to test just let me know.
>
> Regards,
>
> Ate
>
>
> Ate Douma wrote:
>
>> I've created Blocking issue JS2-18 last night after a long frustrated
>> day trying to get J2 ready to use Oracle as db.
>>
>> In that issue I identified (at least) 5 major problems I like to ask
>> attention to.
>>
>> Although JIRA is fine for issue tracking I think the mailing list is
>> more interactive to discuss these issues.
>> Therefore I created this mail as a wrapper for the several problems
>> which I will describe separately as reply to this mail.
>>
>> I am very dependent on Oracle for running J2 as it is required for my
>> client. Furthermore, in our project we will start developing portlets
>> based on J2 any time now (I know its kind of early for that but we
>> need some result before the summer and hopefully our development will
>> provide lots of feedback to J2 to help it get out of the door sooner).
>>
>> Regards, Ate
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>>
>>
>>
>> .
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>
>