Re: [uportal-dev] uP3 persistence libraries

2007-11-16 Thread Cris J Holdorph

There are few 'trends' that "most" in the community seem to agree on.

Eclipse was the first I noticed in this community.

Hibernate and Spring were the second and third (not sure the order).  I 
don't think you'll find much dissension on using Hibernate.


But  If you really wanted to open the door and think about all the 
reasons why or not, to use Hibernate, there is one downside.


RedHat/JBoss and Interface 21 do not get along.  I get the impression 
that some people use iBatis not because they think it's better then 
Hibernate, but because of the riff here and a desire to use something 
"other" then Hibernate.


Personally, I'd use Hibernate.  +1.

 Cris J H

Eric Dalquist wrote:
As I progress with the Pluto 1.1 integration in the trunk I'm getting 
closer to the point of needing to write some new DAOs to persist some 
portlet domain objects. I would like to propose using Hibernate 3 for 
_new_ DAO implementations. Initially this just provides an easy way to 
write DAOs for object persistence, in the very long term we could plan 
on moving all DAOs to Hibernate to take advantage of schema creation and 
cross-database support. For 3.0 Hibernate would only be used for new 
DAOs and all existing data access code would remain as is.


-Eric


--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


[uportal-dev] uP3 persistence libraries

2007-11-16 Thread Eric Dalquist
As I progress with the Pluto 1.1 integration in the trunk I'm getting 
closer to the point of needing to write some new DAOs to persist some 
portlet domain objects. I would like to propose using Hibernate 3 for 
_new_ DAO implementations. Initially this just provides an easy way to 
write DAOs for object persistence, in the very long term we could plan 
on moving all DAOs to Hibernate to take advantage of schema creation and 
cross-database support. For 3.0 Hibernate would only be used for new 
DAOs and all existing data access code would remain as is.


-Eric


smime.p7s
Description: S/MIME Cryptographic Signature


Re: [uportal-dev] removing RunXSLT

2007-11-16 Thread Eric Dalquist

+1

Susan Bramhall wrote:

I think this is a no brainer but just to be sure..

I propose removing the RunXSLT tool and all its accompanying xsl files 
from uPortal trunk (uP3).  There was an ant target to run it which has 
already been removed.  It was invented and used to convert data from 
uPortal 2.0 to 2.1 or 2.1 to 2.3 - I forget which.  Its function is 
entirely subsumed by Cernunnos.  Just delete it?


Susan



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [uportal-dev] uP3 persistence libraries

2007-11-16 Thread Drew Wills

+1

Hibernate-style DAOs will (eventually) make the Import/Export features 
more straightforward and easier to maintain.


drew wills

Eric Dalquist wrote:
As I progress with the Pluto 1.1 integration in the trunk I'm getting 
closer to the point of needing to write some new DAOs to persist some 
portlet domain objects. I would like to propose using Hibernate 3 for 
_new_ DAO implementations. Initially this just provides an easy way to 
write DAOs for object persistence, in the very long term we could plan 
on moving all DAOs to Hibernate to take advantage of schema creation and 
cross-database support. For 3.0 Hibernate would only be used for new 
DAOs and all existing data access code would remain as is.


-Eric


--
Andrew Wills
UNICON, Inc.
Office:  (480) 558-2476
http://code.google.com/p/cernunnos/

--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


Re: [uportal-dev] uP3 persistence libraries

2007-11-16 Thread Lennard Fuller

+1
We've used hibernate pretty extensively on a number of projects,  both 
large and small, overall I've been very pleased with the results.  You 
are likely already aware of this, but the Spring community no longer 
recommends using the HibernateTemplate and instead prefers a 
template-less approach since the original reasons for the creation/usage 
of the HibernateTemplate no longer exist.


Here is an article on the subject.

http://blog.interface21.com/main/2007/06/26/so-should-you-still-use-springs-hibernatetemplate-andor-jpatemplate/

Eric Dalquist wrote:
As I progress with the Pluto 1.1 integration in the trunk I'm getting 
closer to the point of needing to write some new DAOs to persist some 
portlet domain objects. I would like to propose using Hibernate 3 for 
_new_ DAO implementations. Initially this just provides an easy way to 
write DAOs for object persistence, in the very long term we could plan 
on moving all DAOs to Hibernate to take advantage of schema creation 
and cross-database support. For 3.0 Hibernate would only be used for 
new DAOs and all existing data access code would remain as is.


-Eric



--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


Re: [uportal-dev] removing RunXSLT

2007-11-16 Thread Drew Wills

+1

drew wills

Eric Dalquist wrote:

+1

Susan Bramhall wrote:

I think this is a no brainer but just to be sure..

I propose removing the RunXSLT tool and all its accompanying xsl files 
from uPortal trunk (uP3).  There was an ant target to run it which has 
already been removed.  It was invented and used to convert data from 
uPortal 2.0 to 2.1 or 2.1 to 2.3 - I forget which.  Its function is 
entirely subsumed by Cernunnos.  Just delete it?


Susan



--
Andrew Wills
UNICON, Inc.
Office:  (480) 558-2476
http://code.google.com/p/cernunnos/

--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


[uportal-dev] removing RunXSLT

2007-11-16 Thread Susan Bramhall

I think this is a no brainer but just to be sure..

I propose removing the RunXSLT tool and all its accompanying xsl files 
from uPortal trunk (uP3).  There was an ant target to run it which has 
already been removed.  It was invented and used to convert data from 
uPortal 2.0 to 2.1 or 2.1 to 2.3 - I forget which.  Its function is 
entirely subsumed by Cernunnos.  Just delete it?


Susan

--
It's no use trying to be clever--we are all clever here; just try to be kind--a 
little kind.
-- F.J. Foakes Jackson


--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev