re: [OT] Scaffold:StorageBeanBase Use Cases???

[Mete Kural]

Thanks for the useful input Ted.

>I'm now working with transparent approaches now, like that used by 
>Hibernate.

Are you going to include classes to facilitate these approaches in the Scaffold 
package, or are they going to be in a seperate package? 
Do you think using JDO would be a good alternative to Hibernate? Why don't you go the 
JDO way? Is it because there is no good open source JDO implementation out there?

>The Access class was basically a Data Access Object/Repository class. 
>This does seem like the better way to go.

In that case I will use the Access class approach for an upcoming project. Should I 
subclass the AccessBase class for non-SQL data access or should I completely re-write 
my own Access class from scratch? I'm not doing any SQL access so do you think there 
is an incentive for me to subclass AccessBase to avoid some extra work?

Thanks a lot for all the useful information and your wonderful book :-)

Thanks,
Mete

-- Original Message --
From: Ted Husted <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Date:  Fri, 04 Apr 2003 08:59:28 -0500

>The StorageBeanBase was designed for SQL. To employ another storage 
>method, so yes, the idea is that would define another StorageBean 
>implementation.
>
>Though, in practice, I wasn't happy with the way StorageBean deployed. 
>I'm now working with transparent approaches now, like that used by 
>Hibernate.
>
>The Access class was basically a Data Access Object/Repository class. 
>This does seem like the better way to go.
>
>-Ted.
>
>-- 
>Ted Husted,
>Struts in Action 
>
>
>
>-
>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]

re: [OT] Scaffold:StorageBeanBase Use Cases???

[Ted Husted]

The StorageBeanBase was designed for SQL. To employ another storage 
method, so yes, the idea is that would define another StorageBean 
implementation.

Though, in practice, I wasn't happy with the way StorageBean deployed. 
I'm now working with transparent approaches now, like that used by 
Hibernate.

The Access class was basically a Data Access Object/Repository class. 
This does seem like the better way to go.

-Ted.

--
Ted Husted,
Struts in Action 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[OT] Scaffold:StorageBeanBase Use Cases???

[Mete Kural]

Hi all,
The Access class in commons-scaffold 
(http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/scaffold/) that is referred to 
in the book "Struts in Action" is deprecated. StorageBean interface is recommended in 
the javadoc instead. There is a StorageBeanBase class that implements StorageBean, but 
it seemed to me that it was designed for SQL data access. Would you recommend me to 
subclass the StorageBeanBase class for data access other than SQL data, or is it 
better to completely re-write our own StorageBeanBase class that implements the 
StorageBean interface? Are there any users of the Scaffold package out there?
Thanks,
Mete



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]