Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[smila-dev] RE: EclipseLink JPA vs. our Bin/Xml Storage

i will plunge into this on friday, as tomorrow I have one day of vacation.

 

Kind regards

Thomas Menzel @ brox IT-Solutions GmbH

 

From: Igor.Novakovic@xxxxxxxxxxx [mailto:Igor.Novakovic@xxxxxxxxxxx]
Sent: Mittwoch, 15. Oktober 2008 17:35
To: Thomas Menzel
Cc: smila-dev@xxxxxxxxxxx; Marius Cimpean
Subject: AW: EclipseLink JPA vs. our Bin/Xml Storage

 

Hi Tom,

 

I share your opinion concerning EclipseLink, but I think we should discuss this in more detail with Doug. Perhaps is there something about EclipseLink that we have overlooked and could be used in our other persistence services like delta indexing storage & buffer storage.

 

As far I’m concerned you can take over the task „storage requirements“. I just wanted to provide some starting point for our discussion.

So please open a Bugzilla issue on this and let us discuss this matter there.

 

Cheers

Igor

 

Von: Thomas Menzel [mailto:tmenzel@xxxxxxx]
Gesendet: Mittwoch, 15. Oktober 2008 16:39
An: Novakovic, Igor, M-E-D; Schumacher, Jürgen, M-ED
Cc: Smila project developer mailing list; Marius Cimpean
Betreff: EclipseLink JPA vs. our Bin/Xml Storage

 

hi,

 

I looked @ their project page and don’t think it is applicable to us as far as I can see.

from what I understand this is just an automated persistence layer for an object model similar to Hibernate which is not quite our use case.

 

what are ur thoughts on this?

 

in regard to the discussion about the requirements to the storages: I welcome your contributions but like to take the lead in the discussion as this is (at least was) my area of responsibility.

this will also include that I will change/add/merge the content there as needed in particular in regard with what marius provided.

 

in that context I will open a bugzilla for both and would ask that communications occurs there in order to have it in one place.

in the past, and even today, I have written on the wiki discussion page. but I deem this rather invisible.

 

is that OK with u?

 

Kind regards

Thomas Menzel @ brox IT-Solutions GmbH

 

From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Igor.Novakovic@xxxxxxxxxxx
Sent: Dienstag, 14. Oktober 2008 10:07
To: DOUGLAS.CLARKE@xxxxxxxxxx
Cc: smila-dev@xxxxxxxxxxx; shaun.smith@xxxxxxxxxx
Subject: [smila-dev] AW: CQ 2747: Usage of JPA

 

Hi Doug,

 

like Jürgen already said, we are in the middle of discussion about (re)designing our persistence layer in SMILA.

The entry point in wiki for this topic is http://wiki.eclipse.org/SMILA/Component_Requirements.

(The two other pages, which Jürgen mentioned below, are linked to this page.)

 

We would be more than happy to get you feedback on this.

Could you please take a look at these three wiki pages? (It won’t cost you much time since they are very concise ;-)

That do you think? Can EclipseLink fulfill our requirements?

 

BTW: Jürgen and I will take a closer look on EclipseLink today.

 

Best regards

Igor

 

Von: Schumacher, Jürgen, M-ED
Gesendet: Dienstag, 14. Oktober 2008 09:36
An: DOUGLAS.CLARKE@xxxxxxxxxx
Cc: shaun.smith@xxxxxxxxxx; Novakovic, Igor, M-E-D
Betreff: RE: CQ 2747: Usage of JPA

 

Yes, sure, we should always use other Eclipse projects if possible. I don’t think that we want to fiddle with ODEs persistence currently (actually, in our default setup we switch it off as much as possible to get the best performance – but it has to be there), but of course SMILA has its own persistence needs. It would probably be interesting to have a look at EclipseLink for this. I’ve Cc’ed one of our co-leads because he is currently thinking and planning on the SMILA persistence layer (see http://wiki.eclipse.org/SMILA/Component_Requirements/Record_Binary_Storage_Requirements and http://wiki.eclipse.org/SMILA/Component_Requirements/Record_XML_Storage_Requirements for some current discussions). I think we will have to have a closer look at the EclipseLink pages first to see where you could help us.

 

Thanks,

Juergen.

 

From: DOUGLAS.CLARKE@xxxxxxxxxx [mailto:DOUGLAS.CLARKE@xxxxxxxxxx]
Sent: Tuesday, October 14, 2008 9:25 AM
To: Schumacher, Jürgen, M-ED
Cc: shaun.smith@xxxxxxxxxx
Subject: RE: CQ 2747: Usage of JPA

 

It would be great to get the EclipseLink JPA implementation supported as well. I don't yet know much about ODE but if we could find a way to leverage multiple projects under RT together I believe it would make our platform solution stronger.

 

Doug

-----Original Message-----
From: Juergen.Schumacher@xxxxxxxxxxx [mailto:Juergen.Schumacher@xxxxxxxxxxx]
Sent: Tuesday, October 14, 2008 3:03 AM
To: DOUGLAS.CLARKE@xxxxxxxxxx
Cc: Shaun Smith
Subject: RE: CQ 2747: Usage of JPA

Doug,

 

we do not use JPA immediately currently. We want to use Apache ODE, a BPEL engine, to orchestrate the services in SMILA and ODE uses JPA (OpenJPA actually) to persist process definitions and message exchange states (i.e. the current state of a process instance). I do not know, why they choose JPA. There is also an ODE module that seems to implement the same things using hibernate but by default ODE uses the JPA implementation.

 

Hope this helps.

 

Regards,

Juergen Schumacher.

 

SMILA committer

 

From: DOUGLAS.CLARKE@xxxxxxxxxx [mailto:DOUGLAS.CLARKE@xxxxxxxxxx]
Sent: Monday, October 13, 2008 11:55 PM
To: Schumacher, Jürgen, M-ED
Cc: shaun.smith@xxxxxxxxxx
Subject: CQ 2747: Usage of JPA

 

Juergen,

 

I would like to better understand your usage of JPA. Do you also have an out of the box JPA implementation included or are you just using the JPA standard to allow JPA implementations to plug in?

 

Doug Clarke

 

EclipseLink Project co-Lead

 

 


Back to the top