Reorganizing wsrp4j into modules corresponding to jars

[David Jencks <dj...@apache.org>]

I've recently started looking at wsrp4j and for my own understanding 
I've reorganized the project into modules corresponding to the output 
jars.  These modules are also set up to be maven projects, so the 
entire wsrp4j project now builds using maven multiproject:install.  I 
haven't tried it yet but usually ant build scripts, if needed, can be 
generated by maven.

In addition, I believe that the use of castor persistence is somewhat 
peripheral to the core functionality of wsrp4j, and likely to be 
replaced in most embeddings of wsrp4j in portal projects, so I've moved 
that into a separate module.

The jars from code in cvs currently seem to have circular dependencies 
from some of the persistence code to the consumer and producer classes. 
  I've made some simple modifications to eliminate these dependencies.

My next step is to write some "installation" modules to install the 
appropriate war/jars into tomcat and possibly other web servers to 
eliminate the server-specific code in the main build.

I noticed that splitting the source into modules corresponding to the 
jars is one of the tasks on the todo list, so I thought I'd offer this 
work and ask if it's desired and how best it could be integrated.

Currently my modifications are in a subversion repository started from 
a cvs snapshot.  Although it would be possible to reorganize the 
project in cvs I'd strongly suggest that bowing to the gentle pressure 
from the apache infrastructure folks and moving to subversion first 
would make a reorganization much easier and have the usual subversion 
advantages such as preserving history for moved files.

If there's interest I will look into making my subversion wsrp4j repo 
publically accessible.

Many thanks,
david jencks

Re: Reorganizing wsrp4j into modules corresponding to jars

[Salvador Trujillo Gonzalez <ji...@sc.ehu.es>]

You can use subclipse (http://subclipse.tigris.org/) for Eclipse/SVN
integration.

On Tue, 21 Sep 2004, Julie MacNaught wrote:

> Wow.
>
> It would be nice to be able to incorporate this work.  I have been
> thinking about the subversion thing, but I haven't wanted to bite it
> off.   I've been resisting it because I use eclipse/CVS integration
> pretty seamlessly.
>
> What do others think?
>
> David Jencks wrote:
>
> > I've recently started looking at wsrp4j and for my own understanding
> > I've reorganized the project into modules corresponding to the output
> > jars.  These modules are also set up to be maven projects, so the
> > entire wsrp4j project now builds using maven multiproject:install.  I
> > haven't tried it yet but usually ant build scripts, if needed, can be
> > generated by maven.
> >
> > In addition, I believe that the use of castor persistence is somewhat
> > peripheral to the core functionality of wsrp4j, and likely to be
> > replaced in most embeddings of wsrp4j in portal projects, so I've
> > moved that into a separate module.
> >
> > The jars from code in cvs currently seem to have circular dependencies
> > from some of the persistence code to the consumer and producer
> > classes.  I've made some simple modifications to eliminate these
> > dependencies.
> >
> > My next step is to write some "installation" modules to install the
> > appropriate war/jars into tomcat and possibly other web servers to
> > eliminate the server-specific code in the main build.
> >
> > I noticed that splitting the source into modules corresponding to the
> > jars is one of the tasks on the todo list, so I thought I'd offer this
> > work and ask if it's desired and how best it could be integrated.
> >
> > Currently my modifications are in a subversion repository started from
> > a cvs snapshot.  Although it would be possible to reorganize the
> > project in cvs I'd strongly suggest that bowing to the gentle pressure
> > from the apache infrastructure folks and moving to subversion first
> > would make a reorganization much easier and have the usual subversion
> > advantages such as preserving history for moved files.
> >
> > If there's interest I will look into making my subversion wsrp4j repo
> > publically accessible.
> >
> > Many thanks,
> > david jencks
> >
> >
>
>

RE: Reorganizing wsrp4j into modules corresponding to jars

[Carsten Ziegeler <cz...@apache.org>]

 
Julie MacNaught wrote:
> Wow.
> 
> It would be nice to be able to incorporate this work.  I have 
> been thinking about the subversion thing, but I haven't 
> wanted to bite it 
> off.   I've been resisting it because I use eclipse/CVS integration 
> pretty seamlessly.
> 
> What do others think?
> 
Yes, this reorganization sounds great!

As most other portal projects have already migrated to svn or will migrate
soon, I think we should migrate wsrp4j as well. 
So I think we should first migrate and then reorganize the migrated
version.

Carsten
> David Jencks wrote:
> 
> > I've recently started looking at wsrp4j and for my own 
> understanding 
> > I've reorganized the project into modules corresponding to 
> the output 
> > jars.  These modules are also set up to be maven projects, so the 
> > entire wsrp4j project now builds using maven 
> multiproject:install.  I 
> > haven't tried it yet but usually ant build scripts, if 
> needed, can be 
> > generated by maven.
> >
> > In addition, I believe that the use of castor persistence 
> is somewhat 
> > peripheral to the core functionality of wsrp4j, and likely to be 
> > replaced in most embeddings of wsrp4j in portal projects, so I've 
> > moved that into a separate module.
> >
> > The jars from code in cvs currently seem to have circular 
> dependencies 
> > from some of the persistence code to the consumer and producer 
> > classes.  I've made some simple modifications to eliminate these 
> > dependencies.
> >
> > My next step is to write some "installation" modules to install the 
> > appropriate war/jars into tomcat and possibly other web servers to 
> > eliminate the server-specific code in the main build.
> >
> > I noticed that splitting the source into modules 
> corresponding to the 
> > jars is one of the tasks on the todo list, so I thought I'd 
> offer this 
> > work and ask if it's desired and how best it could be integrated.
> >
> > Currently my modifications are in a subversion repository 
> started from 
> > a cvs snapshot.  Although it would be possible to reorganize the 
> > project in cvs I'd strongly suggest that bowing to the 
> gentle pressure 
> > from the apache infrastructure folks and moving to subversion first 
> > would make a reorganization much easier and have the usual 
> subversion 
> > advantages such as preserving history for moved files.
> >
> > If there's interest I will look into making my subversion 
> wsrp4j repo 
> > publically accessible.
> >
> > Many thanks,
> > david jencks
> >
> >
> 
> 

Re: Reorganizing wsrp4j into modules corresponding to jars

[Julie MacNaught <jm...@apache.org>]

Wow.

It would be nice to be able to incorporate this work.  I have been 
thinking about the subversion thing, but I haven't wanted to bite it 
off.   I've been resisting it because I use eclipse/CVS integration 
pretty seamlessly.

What do others think?

David Jencks wrote:

> I've recently started looking at wsrp4j and for my own understanding 
> I've reorganized the project into modules corresponding to the output 
> jars.  These modules are also set up to be maven projects, so the 
> entire wsrp4j project now builds using maven multiproject:install.  I 
> haven't tried it yet but usually ant build scripts, if needed, can be 
> generated by maven.
>
> In addition, I believe that the use of castor persistence is somewhat 
> peripheral to the core functionality of wsrp4j, and likely to be 
> replaced in most embeddings of wsrp4j in portal projects, so I've 
> moved that into a separate module.
>
> The jars from code in cvs currently seem to have circular dependencies 
> from some of the persistence code to the consumer and producer 
> classes.  I've made some simple modifications to eliminate these 
> dependencies.
>
> My next step is to write some "installation" modules to install the 
> appropriate war/jars into tomcat and possibly other web servers to 
> eliminate the server-specific code in the main build.
>
> I noticed that splitting the source into modules corresponding to the 
> jars is one of the tasks on the todo list, so I thought I'd offer this 
> work and ask if it's desired and how best it could be integrated.
>
> Currently my modifications are in a subversion repository started from 
> a cvs snapshot.  Although it would be possible to reorganize the 
> project in cvs I'd strongly suggest that bowing to the gentle pressure 
> from the apache infrastructure folks and moving to subversion first 
> would make a reorganization much easier and have the usual subversion 
> advantages such as preserving history for moved files.
>
> If there's interest I will look into making my subversion wsrp4j repo 
> publically accessible.
>
> Many thanks,
> david jencks
>
>