You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matthias Rothe <ma...@gmx.com> on 2007/08/30 11:41:16 UTC
Project Ideas
Dear all,
Since I've profited from using libraries of the Apache Commons Project I'd like to give something back to the community.
Lately I've been working on two library projects. One aims at creating a collections framework that seamlessly integrates with the JCF (Java Collections Framework) while permitting transparent persistence.
Say you've got an ArrayList of data objects you need to work with and store away. Usually you would have to load the objects from some source (XML, database etc.) put them into the ArrayList to manipulate or use them and later store any changes to them yourself.
I think this can be done more transparently by telling the ArrayList were to get its objects, work on those objects and let the ArrayList handle all the persistence issues. That would make working with persistent objects as simple as working with in memory ones.
By using a strategy pattern any kind of data source could be wrapped and therefore become accessible for any collection type.
---
The second project is a physics related library containing classes for all sorts of measuring units, their prefixes and measurables, objects that take a subtype of Number and a measuring unit.
Those measurables will be capable of converting themselves into target measurables of the same or a related measuring unit. Say you have an object of the measurable type meters and want to convert it to miles. All you would need to do is passing the meters object the desired measuring unit and prefix and you'd get a new measurable of the target unit and prefix and the converted value.
Furthermore all measurables, measuring units and prefixes will be able to tell their names (and values) in a locale sensitive way, either abbreviated (e.g. km) or fully (e.g. kilometer).
---
What do you think about these project ideas? Would the resulting libraries be of any help to you?
I'm looking forward to hearing from you!
Kind regards,
Matt Rothe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Project Ideas
Posted by John <jh...@txttools.co.uk>.
Hi,
login to JIRA and raise your enhancements as New Features:
https://issues.apache.org/jira/
John.
Matthias Rothe wrote:
> Dear all,
>
> Since I've profited from using libraries of the Apache Commons Project I'd like to give something back to the community.
>
> Lately I've been working on two library projects. One aims at creating a collections framework that seamlessly integrates with the JCF (Java Collections Framework) while permitting transparent persistence.
>
> Say you've got an ArrayList of data objects you need to work with and store away. Usually you would have to load the objects from some source (XML, database etc.) put them into the ArrayList to manipulate or use them and later store any changes to them yourself.
>
> I think this can be done more transparently by telling the ArrayList were to get its objects, work on those objects and let the ArrayList handle all the persistence issues. That would make working with persistent objects as simple as working with in memory ones.
>
> By using a strategy pattern any kind of data source could be wrapped and therefore become accessible for any collection type.
>
> ---
>
> The second project is a physics related library containing classes for all sorts of measuring units, their prefixes and measurables, objects that take a subtype of Number and a measuring unit.
>
> Those measurables will be capable of converting themselves into target measurables of the same or a related measuring unit. Say you have an object of the measurable type meters and want to convert it to miles. All you would need to do is passing the meters object the desired measuring unit and prefix and you'd get a new measurable of the target unit and prefix and the converted value.
>
> Furthermore all measurables, measuring units and prefixes will be able to tell their names (and values) in a locale sensitive way, either abbreviated (e.g. km) or fully (e.g. kilometer).
>
> ---
>
> What do you think about these project ideas? Would the resulting libraries be of any help to you?
>
> I'm looking forward to hearing from you!
>
> Kind regards,
> Matt Rothe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Project Ideas
Posted by Matt Rothe <ma...@gmx.com>.
Concerning my proposed Persistent Collections Framework (PCF) and the comparison with Hibernate I have to say that one is no substitute of the other.
Hibernate aims at object-relational mapping and works specifically with relational databases of one kind or another.
The PCF would however work with any data source, be it XML or CSV files, databases or anything imaginable. As long as there existed a strategy for accessing it, it could be used.
So in one way my proposal is far more general than Hibernate. In another it's also usable in situations where there is no relational database available or Hibernate would be far to heavyweight. Hibernate obviously focuses on the enterprise environment and therefore might not be appropriate for other situations, such as single place applications, mobile deployment and such.
Please consider these issues and let me know what you think about my argument.
Thanks for pointing me to JSR-275 for the other project idea.
Matt
-------- Original-Nachricht --------
> Datum: Thu, 30 Aug 2007 04:51:00 -0700 (PDT)
> Von: Matt Benson <gu...@yahoo.com>
> An: Jakarta Commons Developers List <de...@commons.apache.org>
> Betreff: Re: Project Ideas
>
> --- Matthias Rothe <ma...@gmx.com> wrote:
>
> > Dear all,
> >
> > Since I've profited from using libraries of the
> > Apache Commons Project I'd like to give something
> > back to the community.
> >
> > Lately I've been working on two library projects.
> > One aims at creating a collections framework that
> > seamlessly integrates with the JCF (Java Collections
> > Framework) while permitting transparent persistence.
> >
> > Say you've got an ArrayList of data objects you need
> > to work with and store away. Usually you would have
> > to load the objects from some source (XML, database
> > etc.) put them into the ArrayList to manipulate or
> > use them and later store any changes to them
> > yourself.
> >
> > I think this can be done more transparently by
> > telling the ArrayList were to get its objects, work
> > on those objects and let the ArrayList handle all
> > the persistence issues. That would make working with
> > persistent objects as simple as working with in
> > memory ones.
> >
> > By using a strategy pattern any kind of data source
> > could be wrapped and therefore become accessible for
> > any collection type.
> >
>
> I confess I don't immediately see how this would be
> feasible to do in a way that would make it easier to
> use than e.g. Hibernate, so I won't comment further
> than that on this one.
>
> > ---
> >
> > The second project is a physics related library
> > containing classes for all sorts of measuring units,
> > their prefixes and measurables, objects that take a
> > subtype of Number and a measuring unit.
> >
> > Those measurables will be capable of converting
> > themselves into target measurables of the same or a
> > related measuring unit. Say you have an object of
> > the measurable type meters and want to convert it to
> > miles. All you would need to do is passing the
> > meters object the desired measuring unit and prefix
> > and you'd get a new measurable of the target unit
> > and prefix and the converted value.
> >
> > Furthermore all measurables, measuring units and
> > prefixes will be able to tell their names (and
> > values) in a locale sensitive way, either
> > abbreviated (e.g. km) or fully (e.g. kilometer).
> >
>
> I think you should be following JSR-275 wrt this one.
> :)
>
> br,
> Matt
>
> > ---
> >
> > What do you think about these project ideas? Would
> > the resulting libraries be of any help to you?
> >
> > I'm looking forward to hearing from you!
> >
> > Kind regards,
> > Matt Rothe
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail:
> > dev-help@commons.apache.org
> >
> >
>
>
>
>
> ____________________________________________________________________________________
> Pinpoint customers who are looking for what you sell.
> http://searchmarketing.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Project Ideas
Posted by Matt Benson <gu...@yahoo.com>.
--- Matthias Rothe <ma...@gmx.com> wrote:
> Dear all,
>
> Since I've profited from using libraries of the
> Apache Commons Project I'd like to give something
> back to the community.
>
> Lately I've been working on two library projects.
> One aims at creating a collections framework that
> seamlessly integrates with the JCF (Java Collections
> Framework) while permitting transparent persistence.
>
> Say you've got an ArrayList of data objects you need
> to work with and store away. Usually you would have
> to load the objects from some source (XML, database
> etc.) put them into the ArrayList to manipulate or
> use them and later store any changes to them
> yourself.
>
> I think this can be done more transparently by
> telling the ArrayList were to get its objects, work
> on those objects and let the ArrayList handle all
> the persistence issues. That would make working with
> persistent objects as simple as working with in
> memory ones.
>
> By using a strategy pattern any kind of data source
> could be wrapped and therefore become accessible for
> any collection type.
>
I confess I don't immediately see how this would be
feasible to do in a way that would make it easier to
use than e.g. Hibernate, so I won't comment further
than that on this one.
> ---
>
> The second project is a physics related library
> containing classes for all sorts of measuring units,
> their prefixes and measurables, objects that take a
> subtype of Number and a measuring unit.
>
> Those measurables will be capable of converting
> themselves into target measurables of the same or a
> related measuring unit. Say you have an object of
> the measurable type meters and want to convert it to
> miles. All you would need to do is passing the
> meters object the desired measuring unit and prefix
> and you'd get a new measurable of the target unit
> and prefix and the converted value.
>
> Furthermore all measurables, measuring units and
> prefixes will be able to tell their names (and
> values) in a locale sensitive way, either
> abbreviated (e.g. km) or fully (e.g. kilometer).
>
I think you should be following JSR-275 wrt this one.
:)
br,
Matt
> ---
>
> What do you think about these project ideas? Would
> the resulting libraries be of any help to you?
>
> I'm looking forward to hearing from you!
>
> Kind regards,
> Matt Rothe
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> For additional commands, e-mail:
> dev-help@commons.apache.org
>
>
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org