Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: xbean spring experiments
Date: Wed, 24 Oct 2007 10:40:36 -0400
Message-ID: 
 <49336C35F4B12E4FA1B5D9B63B187C2D054F4EA5@USCIMPLM004.net.plm.eds.com>
In-Reply-To: <6C79997C-D9C8-4668-BFB6-F1EB14AC0A34@yahoo.com>
Thread-Topic: xbean spring experiments
Thread-Index: AcgWNzK5RXFkWUkURD6AcBvhybZirAAFAoxg
References: <6C79997C-D9C8-4668-BFB6-F1EB14AC0A34@yahoo.com>
From: "Weaver, Scott" <weavers@ugs.com>
To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>

I think the trunk has moved to 100% Maven 2.  That being said, I have no
clue how to build it.  Since the trunk represents Jetspeed 2.2, which
will be java 5 compliant, can we dump the javadoc annotations in favor
of using true annotations instead?  Other than that, I am +1 on seeing
how the xbean stuff pans out.

-scott

> -----Original Message-----
> From: David Jencks [mailto:david_jencks@yahoo.com]
> Sent: Wednesday, October 24, 2007 4:10 AM
> To: Jetspeed Developers List
> Subject: xbean spring experiments
>=20
> A while back I suggested that using xbean-spring to generate a schema
> for the spring config files might make jetspeed configuration
> simpler, and IIRC I got some favorable feedback for this idea.  I had
> a bit of spare time recently and set up a bit of build structure for
> this and added the javadoc "annotations" for a few components and
> converted the administation and security-* spring config files.
> However I don't know how to tell if this breaks anything since it
> doesn't seem that trunk produces a working portal at the moment.  I
> may not have time to work on this continually for a bit so I thought
> I'd show what I have so far, so I opened JS2-794.
>=20
> I haven't been active for quite a while so don't want to barge in and
> commit this without discussion review and approval.  I think that
> committing everything except the modified spring config files should
> be very low risk since the xbean context falls back to the behavior
> of the spring context when presented with regular spring xml.  I'm
> nervous about  committing the config file changes until we can tell
> that they work, but with only these changes to apply maintaining a
> patch wouldn't be difficult.
>=20
> If anyone has time to take a look that would be great and if you are
> all too busy getting 2.1.3 out that is fine too, perhaps I will have
> time to get some more stuff converted soon.
>=20
> many thanks
> david jencks
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org