On Wed, 2007-01-24 at 22:32 +0900, Gav.... wrote: > > > -----Original Message----- > > From: Thorsten Scherler [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, 24 January 2007 8:54 PM > > To: dev@forrest.apache.org > > Subject: Re: PoC StAX implementation of dispatcher > > > > On Wed, 2007-01-24 at 13:41 +1100, David Crossley wrote: > > > Thorsten Scherler wrote: > > > > > > > > To make the version compile you need to download > > > > the JSR 173 API from > > > > http://www.ibiblio.org/maven2/stax/stax-api/1.0/stax-api-1.0.jar > > > > and copy it to lib/api/. We cannot redistribute the API (it was once a > > > > discussion on cocoon-dev when the jcr got introduced). > > > > > > Would you please explain that further. > > > > I cannot post any citation from the mail I referred since I just saw > > that it was a private list where I read it. > > > > Bottom line of the mail was that the JSR-170 terms of license allowed by > > Sun's lawyers for the JCR specification (which includes the JCR > > interface jar) are not compatible with ASF. > > You sure about that ? I have not looked deeply into it so I apologise, but > With me being on a number of Apache Mailing Lists, JSR-170 rang a bell > When I saw it in your mail. > > Please take a look at :- > > http://jackrabbit.apache.org/ (Jackrabbit) > http://jcp.org/en/jsr/detail?id=170 (ASF is member of expert group) > http://www.openwfe.org/openwfe-jcr-beancoder.html (Used with Maven) >
Actually the background mail came from one PMC member of Jackrabbit. I actually do not have much time to research whether we can directly include the lib in the dispatcher, so I think downloading and install is the safest way. > > > > Futher it was pointed out that the JCR API (as interface), will either > > already be present in the J2SE engine (with or without an implementation > > from java 6 up) or must be downloaded and installed by the user (either > > directly in $JAVA_HOME/lib or into the location I pointed out before > > (whiteboard/dispatcher/lib/api)). > > > > The following has to be done once: > > cd whiteboard/dispatcher/lib > > mkdir api > > cd api > > wget http://www.ibiblio.org/maven2/stax/stax-api/1.0/stax-api-1.0.jar . > > I think I would prefer %FORREST_HOME%/lib/optional , keeps all these > Required but not endorsed jars in the same place, and no need to > Re-write anything when things move from one place to another, i.e. > From whiteboard to plugin. > Hmm, the dispatcher is standalone. Like said if you want StAX support on your OS you will have to place it into the JAVA lib. salu2 > > > > After this you can > > ./build.sh > > ./dispatch. > > I could probably do a build.bat version for us windoze users, will dispatch > Require the same treatment ? > > Gav... > > > > > salu2 > > > > P.S.: Does this answer your question? > > > > > > -David >
