You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Torsten Schlabach <ts...@apache.org> on 2005/03/06 20:01:19 UTC
Status of repository integration work
Hi again,
sorry if I am in my question and discussion mode current, but ...
I had a look at these two documents:
http://wiki.apache.org/lenya/Repository
http://wiki.apache.org/lenya/RepositoryRequirements
>> 4. Reasons ->
>> # why slide?
>> * JCR is not ready
Are they still applicable?
Has an integration with Slide really been done as the document says?
If yes, is the code in trunk and are there any hints anywehere how to
use it?
If no: Is this still the plan? Or has this been superceeded by Jackrabbit?
Is there any code or any firm concept yet for Jackrabbit?
Regards,
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Torsten Schlabach wrote:
> >> michi is working on hiding the repository behind the sitetree.
>
> I am not sure I understand what you mean. Actually I did not understand
> that discussion, though I had read it. What is "sitetree" in terms of
> Java classes?
http://lenya.apache.org/apidocs/1.4/org/apache/lenya/cms/site/package-summary.html
provides access to the site tree. michi hopes to make it transactional
with jackrabbitt from what i understood
What impact would this move have for example on the
> LenyaSourceFactory?
none, as the content would still reside in the same location
> >> it would definitely make sense to get a better picture of what needs
> >> to happen to move the content to a repository
>
> Are you saying we don't have a clear blueprint of this step yet?
yes
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by Torsten Schlabach <ts...@apache.org>.
>> michi is working on hiding the repository behind the sitetree.
I am not sure I understand what you mean. Actually I did not understand
that discussion, though I had read it. What is "sitetree" in terms of
Java classes? What impact would this move have for example on the
LenyaSourceFactory?
>> it would definitely make sense to get a better picture of what needs
>> to happen to move the content to a repository
Are you saying we don't have a clear blueprint of this step yet?
Regards,
Torsten
Gregor J. Rothfuss schrieb:
> Torsten Schlabach wrote:
>
>> >> (although the blog publication contains some experimental webdav
>> >> stuff)
>>
>> Yes. But it was removed in 1.4.
>
>
> http://svn.apache.org/viewcvs.cgi/lenya/trunk/src/webapp/lenya/pubs/blog/webdav.xmap?rev=123497&view=markup
>
>
>
>> - we will never be able to access anyting outside the webapp, which is
>> somewhat in contrast to "and avoids data lock-in." (from
>> http://lenya.apache.org/index.html, Introducion).
>> - we will never be able to access anything but files.
>
>
> it was mapped to context:// as a stopgap.
>
>> Do I get it right that in order to experiment with repository
>> integration this would be the hook to start with? Do I get it right
>> that from the fact that this component has the mentioned restrictions,
>> there is no sample / experimental code on repository integration yet?
>
>
> there was a discussion on that recently. michi is working on hiding the
> repository behind the sitetree. moving all content access to the
> repository is going to be a lot of work.
>
>> In practice and right now - on our productive systems - it would make
>> my file much easier if the content directory of a publication could be
>> outside the LENYA_WEBAPP tree, so I could for example access the same
>> publication with different instances of Lenya. (Think of smooth
>> migration of of testing 1.4 to decide if it's ready for users yet.
>> Yes, you CAN copy it back and forth, but then it's very easy to loose
>> track of what changed you've done in which copy.)
>
>
> you can use symlinks for that purpose
>
>> I will try some experiments on this unless someone of you guys tells
>> me that I shouldn't or I overlooked something and I should rather put
>> my energy somewhere else.
>
>
> it would definitely make sense to get a better picture of what needs to
> happen to move the content to a repository
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Trying to run 1_2_X
Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:
> J. Wolfgang Kaltz wrote:
>
>> In BRANCH_1_2_X, they are
>> xmldb-common-2003-09-02.jar and xmldb-xupdate-2003-10-14.jar
>>
>> In Cocoon, they are
>> xmldb-common-20030701.jar and xmldb-xupdate-20040205.jar
>>
>> So it looks like Lenya would like to use a newer "xmldb-common", but
>> has an older "xmldb-xupdate" - but, since all end up in the runtime
>> WEB-INF/lib, there is no telling which classes the classloader will
>> find first (alphabetical ? in this case it's the older one)
>
>
> michi patched one of them (i think xmldb-update).
right, whereas I currently cannot find the original of XUpdate, but I
guess I could
figure it out again what I actually patched. Anyway, I have added the
code to the jar.
> i would suggest to examine the patch and move it upstream (so that
> cocoon can also use the patch) and then use the same versions for
> cocoon and lenya
agreed
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Trying to run 1_2_X
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
J. Wolfgang Kaltz wrote:
> In BRANCH_1_2_X, they are
> xmldb-common-2003-09-02.jar and xmldb-xupdate-2003-10-14.jar
>
> In Cocoon, they are
> xmldb-common-20030701.jar and xmldb-xupdate-20040205.jar
>
> So it looks like Lenya would like to use a newer "xmldb-common", but has
> an older "xmldb-xupdate" - but, since all end up in the runtime
> WEB-INF/lib, there is no telling which classes the classloader will find
> first (alphabetical ? in this case it's the older one)
michi patched one of them (i think xmldb-update). i would suggest to
examine the patch and move it upstream (so that cocoon can also use the
patch) and then use the same versions for cocoon and lenya
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Trying to run 1_2_X
Posted by "J. Wolfgang Kaltz" <ka...@interactivesystems.info>.
Gregor J. Rothfuss schrieb:
> J. Wolfgang Kaltz wrote:
>
>> Regarding the QuartzScheduler
>>
>> I see there are two jars implementing it in the Lenya WEB-INF/lib:
>> quartz-1.4.2.jar and quartz-scheduler.jar
>>
>> This is almost certainly causing the problem ("NoSuchMethodError").
>> The Cocoon 2.1.6 distribution only has "quartz-1.4.2.jar"
>> So I guess "quartz-scheduler.jar" is an older version, which was
>> forgotten and should be removed ? Or is there are a reason we need it
>> (e.g. specific bugs or the like)
>
>
> i already removed it in the trunk. it turns out the older quartz did not
> implement some methods that our interface was expecting anyway. make
> sure to test scheduling if you remove it.
Yes, this is exactly what I've just been doing :)
I tested it in Jetty and Tomcat, and it seems to work fine. So I will go
ahead and remove it.
On the same subject, there are these 2 duplicate libraries ending up in
Lenya runtime:
xmldb-common
xmldb-update
In BRANCH_1_2_X, they are
xmldb-common-2003-09-02.jar and xmldb-xupdate-2003-10-14.jar
In Cocoon, they are
xmldb-common-20030701.jar and xmldb-xupdate-20040205.jar
So it looks like Lenya would like to use a newer "xmldb-common", but has
an older "xmldb-xupdate" - but, since all end up in the runtime
WEB-INF/lib, there is no telling which classes the classloader will find
first (alphabetical ? in this case it's the older one)
So should these 2 libraries be simply removed from BRANCH_1_2_X/lib ? I
built and did a few quick tests without them, without any problems.
I suppose they should also be removed from trunk/lib ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Trying to run 1_2_X
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
J. Wolfgang Kaltz wrote:
> Regarding the QuartzScheduler
>
> I see there are two jars implementing it in the Lenya WEB-INF/lib:
> quartz-1.4.2.jar and quartz-scheduler.jar
>
> This is almost certainly causing the problem ("NoSuchMethodError"). The
> Cocoon 2.1.6 distribution only has "quartz-1.4.2.jar"
> So I guess "quartz-scheduler.jar" is an older version, which was
> forgotten and should be removed ? Or is there are a reason we need it
> (e.g. specific bugs or the like)
i already removed it in the trunk. it turns out the older quartz did not
implement some methods that our interface was expecting anyway. make
sure to test scheduling if you remove it.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Trying to run 1_2_X
Posted by "J. Wolfgang Kaltz" <ka...@interactivesystems.info>.
Regarding the QuartzScheduler
I see there are two jars implementing it in the Lenya WEB-INF/lib:
quartz-1.4.2.jar and quartz-scheduler.jar
This is almost certainly causing the problem ("NoSuchMethodError"). The
Cocoon 2.1.6 distribution only has "quartz-1.4.2.jar"
So I guess "quartz-scheduler.jar" is an older version, which was
forgotten and should be removed ? Or is there are a reason we need it
(e.g. specific bugs or the like)
Wolfgang
J. Wolfgang Kaltz schrieb:
> Hi all
>
> I'm trying to run a fresh (unchanged) checkout of the 1_2_X branch,
> within Jetty.
> First, there seems to be a problem with web.xml. Copying the header from
> the Cocoon sources makes it go away.
>
> The next problem is apparently related to the "QuartzScheduler" :
> (...)
> Caused by: java.lang.NoSuchMethodError:
> org.quartz.core.QuartzScheduler.<init>(Lorg/quartz/core/QuartzSchedulerResources;Lorg/quartz/core/SchedulingContext;JJ)V
>
> at
> org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:320)
>
> at
> org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:270)
>
> at
> org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:320)
>
> at
> org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:283)
>
> at
> org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:277)
>
> at
> org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
>
> at
> org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:522)
>
> at
> org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:541)
>
> at
> org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:283)
>
> at org.apache.cocoon.Cocoon.initialize(Cocoon.java:280)
> (...)
>
> so Lenya doesn't start. I'm not sure how to track down this problem -
> any ideas ?
>
>
> Wolfgang
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Trying to run 1_2_X
Posted by "J. Wolfgang Kaltz" <ka...@interactivesystems.info>.
Hi all
I'm trying to run a fresh (unchanged) checkout of the 1_2_X branch,
within Jetty.
First, there seems to be a problem with web.xml. Copying the header from
the Cocoon sources makes it go away.
The next problem is apparently related to the "QuartzScheduler" :
(...)
Caused by: java.lang.NoSuchMethodError:
org.quartz.core.QuartzScheduler.<init>(Lorg/quartz/core/QuartzSchedulerResources;Lorg/quartz/core/SchedulingContext;JJ)V
at
org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:320)
at
org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:270)
at
org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:320)
at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:283)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:277)
at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:522)
at
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:541)
at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:283)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:280)
(...)
so Lenya doesn't start. I'm not sure how to track down this problem -
any ideas ?
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Rolf Kulemann wrote:
> Of course,
> writing is mountain of work. Try a find and grep for java.io in the
> Lenya sources.
the main problem was that a lot of code was not avalonized and had no
access to the excalibur source resolver. this still holds true for tasks
in 1.4, but the rest of the code base pretty much has access now.
we can therefore replace all java.io in those classes.
> In the past we started on a sprint to port sitemaps to
> use the lenya protocol, but it never got checked in. IMHO it is a key
> for smooth switch to the repo.
agreed.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by Rolf Kulemann <ro...@apache.org>.
On Sun, 2005-03-06 at 23:00, Torsten Schlabach wrote:
> >> it would definitely make sense to get a better picture of what needs
> >> to happen to move the content to a repository
>
> Has the decision to base whatever we do on JSR-170 been formally made?
>
> Like this:
>
> +---------------------------------------------------+
> | L e n y a |
> +---------------------------------------------------+
> | JSR-170-API |
> +---------------------------------------------------+
> | File System | WebDAV | Xindice | SQL | Jackrabbit |
> +-------------+--------+---------+-----+------------+
>
> Asserting this,
>
> - do we know of any acticities in the Cocoon project in regards to at
> least reading from a JSR-170 repository?
> - do you know by heart if either the JSR-170 suggest a scheme name for
> repository access or if anyone else already came up with one? I don't
> think this should be called "lenya" as this would put Lenya in the role
> of a repository.
No, the idea of the Lenya scheme is as follows. The LEnya scheme is used
to port smothly to a repository like JCR. The scheme impl. decides,
which files are read from a repo. or still from fs. Thus it hides the
details of the storage. E.g. we could read all stuff from content/* from
the repo and all *.xsl from the fs. Users would always access the files
via the lenya protocol. If so, we could later decide which files should
also be moved to the repo. This approach would also enable to read all
content files from the repo with little sitemap changes. Of course,
writing is mountain of work. Try a find and grep for java.io in the
Lenya sources. In the past we started on a sprint to port sitemaps to
use the lenya protocol, but it never got checked in. IMHO it is a key
for smooth switch to the repo.
>
> It might be a nice step to at least be able to for example draw pictures
> from a repository with something like
>
> <img arc="jsr-170://myfavpic.gif">.
No, this is not good. What if we use the fs for images? of course we
won't, but the jcr has to be abstracted anyway by a Lenya API, since JCR
is still low level as JDBC. I fear people expect to much of JCR.
The last days I thought about implementing a central asset stor with
jcr, without touching the other files of Lenya. This would be an
isolated prototype, but I HAVE NO TIME. ATM, I'm not working on
commercial Lenya projects and I'm mot able to spent any free time to
work on Lenya. The time I have I spent with making releases and PMC
stuff.
For the asset store, I would also leverage a plain old relational DB to
store reference counting of assets in docs etc.
However, if some people want we can try to use the Apache Con Europe to
hack a a bit.
--
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by Torsten Schlabach <ts...@apache.org>.
>> it would definitely make sense to get a better picture of what needs
>> to happen to move the content to a repository
Has the decision to base whatever we do on JSR-170 been formally made?
Like this:
+---------------------------------------------------+
| L e n y a |
+---------------------------------------------------+
| JSR-170-API |
+---------------------------------------------------+
| File System | WebDAV | Xindice | SQL | Jackrabbit |
+-------------+--------+---------+-----+------------+
Asserting this,
- do we know of any acticities in the Cocoon project in regards to at
least reading from a JSR-170 repository?
- do you know by heart if either the JSR-170 suggest a scheme name for
repository access or if anyone else already came up with one? I don't
think this should be called "lenya" as this would put Lenya in the role
of a repository.
It might be a nice step to at least be able to for example draw pictures
from a repository with something like
<img arc="jsr-170://myfavpic.gif">.
In a next step we could try to make the repository meta data available
in Lenya for example in the Kupu image drawer. We could still assume
that pictures will be put into the repository by other means.
Might this also circumwent this recent asset upload discussion which I
did not understand as well?
WDYT?
Regards,
Torsten
Gregor J. Rothfuss schrieb:
> Torsten Schlabach wrote:
>
>> >> (although the blog publication contains some experimental webdav
>> >> stuff)
>>
>> Yes. But it was removed in 1.4.
>
>
> http://svn.apache.org/viewcvs.cgi/lenya/trunk/src/webapp/lenya/pubs/blog/webdav.xmap?rev=123497&view=markup
>
>
>
>> - we will never be able to access anyting outside the webapp, which is
>> somewhat in contrast to "and avoids data lock-in." (from
>> http://lenya.apache.org/index.html, Introducion).
>> - we will never be able to access anything but files.
>
>
> it was mapped to context:// as a stopgap.
>
>> Do I get it right that in order to experiment with repository
>> integration this would be the hook to start with? Do I get it right
>> that from the fact that this component has the mentioned restrictions,
>> there is no sample / experimental code on repository integration yet?
>
>
> there was a discussion on that recently. michi is working on hiding the
> repository behind the sitetree. moving all content access to the
> repository is going to be a lot of work.
>
>> In practice and right now - on our productive systems - it would make
>> my file much easier if the content directory of a publication could be
>> outside the LENYA_WEBAPP tree, so I could for example access the same
>> publication with different instances of Lenya. (Think of smooth
>> migration of of testing 1.4 to decide if it's ready for users yet.
>> Yes, you CAN copy it back and forth, but then it's very easy to loose
>> track of what changed you've done in which copy.)
>
>
> you can use symlinks for that purpose
>
>> I will try some experiments on this unless someone of you guys tells
>> me that I shouldn't or I overlooked something and I should rather put
>> my energy somewhere else.
>
>
> it would definitely make sense to get a better picture of what needs to
> happen to move the content to a repository
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Torsten Schlabach wrote:
> >> (although the blog publication contains some experimental webdav
> >> stuff)
>
> Yes. But it was removed in 1.4.
http://svn.apache.org/viewcvs.cgi/lenya/trunk/src/webapp/lenya/pubs/blog/webdav.xmap?rev=123497&view=markup
> - we will never be able to access anyting outside the webapp, which is
> somewhat in contrast to "and avoids data lock-in." (from
> http://lenya.apache.org/index.html, Introducion).
> - we will never be able to access anything but files.
it was mapped to context:// as a stopgap.
> Do I get it right that in order to experiment with repository
> integration this would be the hook to start with? Do I get it right that
> from the fact that this component has the mentioned restrictions, there
> is no sample / experimental code on repository integration yet?
there was a discussion on that recently. michi is working on hiding the
repository behind the sitetree. moving all content access to the
repository is going to be a lot of work.
> In practice and right now - on our productive systems - it would make my
> file much easier if the content directory of a publication could be
> outside the LENYA_WEBAPP tree, so I could for example access the same
> publication with different instances of Lenya. (Think of smooth
> migration of of testing 1.4 to decide if it's ready for users yet. Yes,
> you CAN copy it back and forth, but then it's very easy to loose track
> of what changed you've done in which copy.)
you can use symlinks for that purpose
> I will try some experiments on this unless someone of you guys tells me
> that I shouldn't or I overlooked something and I should rather put my
> energy somewhere else.
it would definitely make sense to get a better picture of what needs to
happen to move the content to a repository
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by Torsten Schlabach <ts...@apache.org>.
>> (although the blog publication contains some experimental webdav
>> stuff)
Yes. But it was removed in 1.4.
I just digged into the source code a little bit. I think I finally got
some understanding of all the Avalon/Excalibur stuff. Took me years of
my life ...
The LenyaSourceFactory is delegating to the context:// scheme of Cocoon.
This means in other words: Unless we change that,
- we will never be able to access anyting outside the webapp, which is
somewhat in contrast to "and avoids data lock-in." (from
http://lenya.apache.org/index.html, Introducion).
- we will never be able to access anything but files.
Do I get it right that in order to experiment with repository
integration this would be the hook to start with? Do I get it right that
from the fact that this component has the mentioned restrictions, there
is no sample / experimental code on repository integration yet?
In practice and right now - on our productive systems - it would make my
file much easier if the content directory of a publication could be
outside the LENYA_WEBAPP tree, so I could for example access the same
publication with different instances of Lenya. (Think of smooth
migration of of testing 1.4 to decide if it's ready for users yet. Yes,
you CAN copy it back and forth, but then it's very easy to loose track
of what changed you've done in which copy.)
I will try some experiments on this unless someone of you guys tells me
that I shouldn't or I overlooked something and I should rather put my
energy somewhere else.
Torsten
Gregor J. Rothfuss schrieb:
> Torsten Schlabach wrote:
>
>> On the same topic:
>>
>> Does this link have anything in common with reality:
>>
>> http://lenya.apache.org/1_2_x/components/repository/webdav.html
>>
>
> it merely contains some setup hints for webdav, and should ideally have
> been somewhere else. it suggests that there is webdav integration, which
> there is not currently (although the blog publication contains some
> experimental webdav stuff)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Torsten Schlabach wrote:
> On the same topic:
>
> Does this link have anything in common with reality:
>
> http://lenya.apache.org/1_2_x/components/repository/webdav.html
>
it merely contains some setup hints for webdav, and should ideally have
been somewhere else. it suggests that there is webdav integration, which
there is not currently (although the blog publication contains some
experimental webdav stuff)
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Status of repository integration work
Posted by Torsten Schlabach <ts...@apache.org>.
On the same topic:
Does this link have anything in common with reality:
http://lenya.apache.org/1_2_x/components/repository/webdav.html
Regards,
Torsten
Torsten Schlabach schrieb:
> Hi again,
>
> sorry if I am in my question and discussion mode current, but ...
>
> I had a look at these two documents:
>
> http://wiki.apache.org/lenya/Repository
> http://wiki.apache.org/lenya/RepositoryRequirements
>
> >> 4. Reasons ->
> >> # why slide?
> >> * JCR is not ready
>
> Are they still applicable?
> Has an integration with Slide really been done as the document says?
> If yes, is the code in trunk and are there any hints anywehere how to
> use it?
> If no: Is this still the plan? Or has this been superceeded by Jackrabbit?
>
> Is there any code or any firm concept yet for Jackrabbit?
>
> Regards,
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org