|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Tips/hints/pointers/advice on working with a databaseHello people and other sentient life forms :-)
I'm currently trying to figure out most of this platform and I've hit the famous wall in regard to how to structure out a database driven application (currently thinking about using hibernate). So basicly I'm asking for any pointers or advice on how to structure out ones application to bind data from the database to window system in a manner that will not come back to haunt my dreams later on. ;-) Any help would be appriciated. :-) -- Regards Christian Michelsen |
|
|
Re: Tips/hints/pointers/advice on working with a databaseOn Netbeans 6.1,use Web app with Visual JSF lib, use persistance API for best result.(Most of the things are wizard Driven) [Little difficult to maintain] Otherwise use Hibernate , hard code your app. (But easy to maintain) http://www.hibernate.org is good enough. On Mon, Jul 7, 2008 at 2:43 PM, Christian August Michelsen <chris-m@...> wrote: Hello people and other sentient life forms :-) -- Sun Campus Ambassador SMVD University (www.smvdu.ac.in) |
|
|
Re: Tips/hints/pointers/advice on working with a database> ...in a manner that will not come back to haunt my dreams later on. ;-)
Heh, this is bound to happen anyhow. It's just a matter of "how much" ;-) I've used both Hibernate and Cayenne and they both require the master ClassLoader as they are not written with a restrictive / secure container in mind. But you might want to experiment with something else if you feel in the mood. --emi -- Emilian Bold +40 740235562 http://www.emilianbold.ro Java and NetBeans Platform-loving consulting services from Timisoara, Romania. |
|
|
RE: Tips/hints/pointers/advice on working with a databaseChristian,
If you do not know for sure where your dreams may take you, and especialy if your application is actually (domain or business) data driven -- rather than driven by currently implemented database structure, I would make a pitch for incorporating some of the Java (EE) blueprint structures for a layer between the database and the window (presentation) system. -----Original Message----- From: Christian August Michelsen [mailto:chris-m@...] Sent: Monday, July 07, 2008 5:13 AM To: dev@... Subject: [openide-dev] Tips/hints/pointers/advice on working with a database Hello people and other sentient life forms :-) I'm currently trying to figure out most of this platform and I've hit the famous wall in regard to how to structure out a database driven application (currently thinking about using hibernate). So basicly I'm asking for any pointers or advice on how to structure out ones application to bind data from the database to window system in a manner that will not come back to haunt my dreams later on. ;-) Any help would be appriciated. :-) -- Regards Christian Michelsen |
|
|
Re: Tips/hints/pointers/advice on working with a databaseEmilian Bold skrev:
> Heh, this is bound to happen anyhow. It's just a matter of "how much" ;-) True, I just live in blissfull denial. ;-) > I've used both Hibernate and Cayenne and they both require the master > ClassLoader as they are not written with a restrictive / secure > container in mind. > > But you might want to experiment with something else if you feel in the mood. Got any pointers on how to start on actually implementing Hibernate/Cayenne in an application? ? ;) *promises cookies(*) for response(s)* (Usefull code samples get's a soda aswell ;p ) -- Some info about what I'm actually trying to do -- I'm porting an app I made quite some time ago to control certain aspects of Zen-Cart (www.zen-cart.com) as a way of learning the neatbeans platform. Basicly the app let's me control products and categories, and my thinking was then that I should implement the "model" part of the application in one module for categories and one for products. My current thinking is to create two modules for the "model" part (products and categories) and two modules for the GUI to keep it seperated (atleast in theory). But as to how to accomplish this with Hibernate/Cayenne/Toplink/JPA/Ibatis eludes me. ;) What I've found so far is some people creating a .jar file with the persistence layer and then wrapping this in a netbeans module, which to me seemed to be a really wierd way of going about things. Any insights would be greatly appriciated (and is rewarded with cookies ;) I hope this mail hasn't been utterly confusing or illegible ;-) -- Best regards Christian Michelsen (*) Cookies to be handed out at The Gathering 2009 ;) |
| Free Forum Powered by Nabble | Forum Help |