You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by Glenn Nielsen <gl...@voyager.apg.more.net> on 2001/07/12 17:35:55 UTC

Re: using jjar (was Re: thoughts on new builds (was: Re:[UPDATE]Converting existingtaglibs to use new build))

Have you considered using SOAP, UDDI, and WSDL.
Perhaps we can leverage those technologies to provide a directory
service for different java technology API's, etc.

Rather than have one location where all the archives are stored,
they can be distributed anywhere as long as the WSDL registry is
kept up to date on one central server.

I haven't had time to look at how jjar works.

Regards,

Glenn

"Geir Magnusson Jr." wrote:
> 
> James Strachan wrote:
> >
> > Hi Geir
> >
> > I've had a little play with JJAR and it looks great. How shall we proceed?
> >
> > I'm guessing we'll need a shared repository document of all the JARs and
> > where they can be downloaded from. Were you indending for the repository.xml
> > to be on the jakarta site, shared across all jakarta projects, or for each
> > seperate project to have their own?
> 
> Right now, I have it on a publically accessable machine (but mine...)
> and will move to jakarta.
> 
> I think that to start, we can at least be the keepers of the jakarta
> ones, and anything else that is useful.  But the design intent is to
> allow non-jakarta projects (say, JDOM) to host their own - our
> repository map would keep a pointer to either the jar directly, or
> another map there in JDOM-land.  Not sure yet.
> 
> For the momement, for jakarta projects, it can work either way.  The
> only requirement is that the jar manifest contains the 'project' name
> and version of that distro.  Its assumed that a format of
> 
> X.Y-Z
> 
> is sufficient for versioning anything.  It's not clear if Y can be
> '1.2', for example, but if we keep the versioning simple (i.e. break on
> first . then on - ) it gives projects a bit of freedom.  We just don't
> want to get wacky...
> 
> >
> > I'll gladly help all I can integrating jjar into the jakarta-taglibs build
> > process (as an optional target).
> 
> How do you see it working?  In just the build process, or at runtime?
> My vision for this kind of stuff is to see how far we can push
> runtime-ish stuff...  However, the build process use is easy, as it's
> just another use of runtime...
> 
> geir
> 
> --
> Geir Magnusson Jr.                           geirm@optonline.net
> System and Software Consulting
> Developing for the web?  See http://jakarta.apache.org/velocity/
> You have a genius for suggesting things I've come a cropper with!

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

Re: using jjar (was Re: thoughts on new builds (was:Re:[UPDATE]Converting existingtaglibs to use new build))

Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
Glenn Nielsen wrote:
> 
> Have you considered using SOAP, UDDI, and WSDL.
> Perhaps we can leverage those technologies to provide a directory
> service for different java technology API's, etc.

Yep - what I was trying to achieve with jjar is smallness, so it's easy
to get or include with a package.  I found a very small SAX parser and
use that.  The whole thing is quite small.

But yes, maybe UDDI is the way to go - let it boostrap itself and then
use UDDI for a better repository.

One strategy might be to stay the course with what we have, and figure
out what we really want, what is really effective, then roll a 2nd
version using UDDI...

> 
> Rather than have one location where all the archives are stored,
> they can be distributed anywhere as long as the WSDL registry is
> kept up to date on one central server.

Right.
 
> I haven't had time to look at how jjar works.

It's pretty simple.. :)

geir
 
> Regards,
> 
> Glenn
> 
> "Geir Magnusson Jr." wrote:
> >
> > James Strachan wrote:
> > >
> > > Hi Geir
> > >
> > > I've had a little play with JJAR and it looks great. How shall we proceed?
> > >
> > > I'm guessing we'll need a shared repository document of all the JARs and
> > > where they can be downloaded from. Were you indending for the repository.xml
> > > to be on the jakarta site, shared across all jakarta projects, or for each
> > > seperate project to have their own?
> >
> > Right now, I have it on a publically accessable machine (but mine...)
> > and will move to jakarta.
> >
> > I think that to start, we can at least be the keepers of the jakarta
> > ones, and anything else that is useful.  But the design intent is to
> > allow non-jakarta projects (say, JDOM) to host their own - our
> > repository map would keep a pointer to either the jar directly, or
> > another map there in JDOM-land.  Not sure yet.
> >
> > For the momement, for jakarta projects, it can work either way.  The
> > only requirement is that the jar manifest contains the 'project' name
> > and version of that distro.  Its assumed that a format of
> >
> > X.Y-Z
> >
> > is sufficient for versioning anything.  It's not clear if Y can be
> > '1.2', for example, but if we keep the versioning simple (i.e. break on
> > first . then on - ) it gives projects a bit of freedom.  We just don't
> > want to get wacky...
> >
> > >
> > > I'll gladly help all I can integrating jjar into the jakarta-taglibs build
> > > process (as an optional target).
> >
> > How do you see it working?  In just the build process, or at runtime?
> > My vision for this kind of stuff is to see how far we can push
> > runtime-ish stuff...  However, the build process use is easy, as it's
> > just another use of runtime...
> >
> > geir
> >
> > --
> > Geir Magnusson Jr.                           geirm@optonline.net
> > System and Software Consulting
> > Developing for the web?  See http://jakarta.apache.org/velocity/
> > You have a genius for suggesting things I've come a cropper with!
> 
> --
> ----------------------------------------------------------------------
> Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> MOREnet System Programming               |  * if iz ina coment.      |
> Missouri Research and Education Network  |  */                       |
> ----------------------------------------------------------------------

-- 
Geir Magnusson Jr.                           geirm@optonline.net
System and Software Consulting
Developing for the web?  See http://jakarta.apache.org/velocity/
You have a genius for suggesting things I've come a cropper with!