 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | How to realize extendable data objects? | How to realize extendable data objects? 2003-09-23 - By Igor Cunko
Back
Simple solution will be to define interface for Attributes and then set
attributes in collection which belongs to Material. It requires a little
thinking about applicable operations on Attributes but shouldn't be so
complicated. You can also introduce XML in equation so you can define
attributes via XSD and have simple marshal/unmarshal and persistence. I
don't think there is specific pattern which fits out of box.
Igor
> -- --Original Message-- --
> From: Udo Cirkel [mailto:u.cirkel@(protected)]
> Sent: Tuesday, September 23, 2003 10:10 AM
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: How to realize extendable data objects?
>
> Hi all,
>
> i have a question belonging to the realization of data objects.
> Which approach or pattern is appropriate to solve the following problem:
>
> - We are developing a supply chain management application that has to be
> devided and delivered in modules.
> Depending on the business requirements of a customer an installation
> can
> embrace different modules.
> A modules realizes a set of functionality like production planning,
> stock
> management, controlling, ...
>
> - The data object "material" plays a central role in the application
> under
> discussion.
> The "material" class has a lot of attributes (e.g. description, value,
> safety stock, delivery time, ...).
> Theses attributes are used by serveral application modules.
>
> - The application must be extendable, so that new functionalities
> (modules)
> can be added in future without
> changing the existing modules.
>
> => How can we realize a data object - e.g. "material" - that has a set of
> initial attributes and
> that can be automatically extended in future (adding new attributes)
> by
> deploying new modules ???
>
> Does there exist an appropriate pattern for this problem?
> Can i solve it using ejbs or daos?
>
> Any suggestions are welcomed.
> Bye,
>
> Udo
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive: http://archives.java.sun.com/archives/j2eepatterns-
> interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
