Sylvain,
I'm currently writing such a source ;-)
Sylvain
did you finish it yet?
Did not yet see anything in the SVN.
Regards,
Torsten
Torsten Schlabach wrote:
Hi all,
did anyone yet write any - maybe experimental - code for Cocoon to use
a repository through the JCR (aka JSR-170)
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Will the scheme be named jcr?
Yes, but the scheme can be anything you want, especially as you may
use several repositories within the same webapp, and therefore use
jcr1, jcr2, etc.
ah!
Please, do jcr://repo/*
Sylvain Wallez wrote:
Torsten Schlabach wrote:
Sylvain,
I'm currently writing such a source ;-)
Will it show up in a separate block in 2.2-dev soon?
Yes. Maybe even 2.1, as I needed for a 2.1 project.
cool. I would be happy to help and testdrive when you will check in your
stuff
Michi
--
Michael Wechner wrote:
what about specifying the repo as parameter, e.g.
map:generate src=jcr://...
map:parameter name=repo value=.../
/map:generate
Because this is a source, not a generator. The parameter would be a
parameter to the generator.
Regards, Upayavira
Upayavira wrote:
Michael Wechner wrote:
what about specifying the repo as parameter, e.g.
map:generate src=jcr://...
map:parameter name=repo value=.../
/map:generate
Because this is a source, not a generator. The parameter would be a
parameter to the generator.
ok. Well, I thought the
Michael Wechner wrote:
Upayavira wrote:
Michael Wechner wrote:
what about specifying the repo as parameter, e.g.
map:generate src=jcr://...
map:parameter name=repo value=.../
/map:generate
Because this is a source, not a generator. The parameter would be a
parameter to the generator.
ok. Well,
Reinhard Poetz wrote:
Michael Wechner wrote:
Upayavira wrote:
Michael Wechner wrote:
what about specifying the repo as parameter, e.g.
map:generate src=jcr://...
map:parameter name=repo value=.../
/map:generate
Because this is a source, not a generator. The parameter would be a
parameter to the
Sylvain Wallez wrote:
Or we could also have a RepositorySelector and select a repository using
the first path element.
Instead of path element, you could use subprotocol
jcr:repo1://path/
Hmm... that may be a good option as an
application also need to access a repository directly and not only
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Or we could also have a RepositorySelector and select a repository
using the first path element.
Instead of path element, you could use subprotocol
jcr:repo1://path/
I like it, as it allows to use jcr://path to use the default (or single)
Sylvain Wallez wrote:
Reinhard Poetz wrote:
Michael Wechner wrote:
Upayavira wrote:
Michael Wechner wrote:
what about specifying the repo as parameter, e.g.
map:generate src=jcr://...
map:parameter name=repo value=.../
/map:generate
Because this is a source, not a generator. The parameter would
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Or we could also have a RepositorySelector and select a repository
using the first path element.
Instead of path element, you could use subprotocol
jcr:repo1://path/
I like it, as it allows to use jcr://path to use the default
Hi all,
did anyone yet write any - maybe experimental - code for Cocoon to use a
repository through the JCR (aka JSR-170) API?
I am thinking of an Avalon / Excalibur source (which is the right
current term?) which would maybe implement a scheme, so I could write
map:generate src=jcr://... /
Torsten Schlabach wrote:
Hi all,
did anyone yet write any - maybe experimental - code for Cocoon to use
a repository through the JCR (aka JSR-170) API?
I am thinking of an Avalon / Excalibur source (which is the right
current term?) which would maybe implement a scheme, so I could write
Sylvain,
I'm currently writing such a source ;-)
Will it show up in a separate block in 2.2-dev soon?
Will the scheme be named jcr?
Regards,
Torsten
Sylvain Wallez schrieb:
Torsten Schlabach wrote:
Hi all,
did anyone yet write any - maybe experimental - code for Cocoon to use
a repository
Torsten Schlabach wrote:
Sylvain,
I'm currently writing such a source ;-)
Will it show up in a separate block in 2.2-dev soon?
Yes. Maybe even 2.1, as I needed for a 2.1 project.
Will the scheme be named jcr?
Yes, but the scheme can be anything you want, especially as you may use
several
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Will the scheme be named jcr?
Yes, but the scheme can be anything you want, especially as you may
use several repositories within the same webapp, and therefore use
jcr1, jcr2, etc.
ah!
Please, do jcr://repo/* instead!
I thought
16 matches
Mail list logo
