BTW, the server I set up for webwork.org is still available so if you
want to link webwork.sourceforge.net to this an put up some nice project
page, the server issue page, and the builds go ahead...
/kjetilhp
> -----Original Message-----
> From: Rickard [mailto:ri...@mi...]
> Sent: Monday, February 04, 2002 8:36 AM
> To: Kjetil Paulsen
> Cc: web...@li...
> Subject: Re: [Webwork-devel] Release - thoughts and issues
>=20
>=20
> Kjetil Paulsen wrote:
>=20
> > I'm really looking forward to the release of webwork but I=20
> do have some
> > second thoughts on all the deployment errors showing up=20
> from different
> > servers - I know most of them are probably server bugs, but I don't
> > think most developers will see this, and will not be happy with the
> > release if it doesn't deploy nicely to their current=20
> development server.
>=20
>=20
> I agree, this is very annoying, and no it would be hard to see what's=20
> the real cause of these errors if all you do is deploy webwork.ear.
>=20
>=20
> > We separate the actual framework and the examples - this=20
> because most of
> > the 'bugs' are related to the 3rd party libs that are used - many
> > containers are not happy with libs that are being deployed=20
> which already
> > exists in the container, and since the 'core' probably will=20
> deploy on
> > most containers, people can live with the fact that all=20
> examples doesn't
> > work on their container - at least if we try make a list stating the
> > issues with the most common servers.=20
>=20
> What would this mean, concretely? I mean, webwork.jar is=20
> already created=20
> as a separate jar file. Do you want two deployable .ear files? What=20
> would the "core" one include?
>=20
> /Rickard
>=20
> --=20
> Rickard =D6berg
> Author of "Mastering RMI"
> Chief Architect, TheServerSide.com
> The Middleware Company - We Build Experts!
>=20
|
