You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/07 12:37:28 UTC
[jira] Created: (JCR-2453) Break the spi2dav dependency to
jcr-server
Break the spi2dav dependency to jcr-server
------------------------------------------
Key: JCR-2453
URL: https://issues.apache.org/jira/browse/JCR-2453
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
Reporter: Jukka Zitting
Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
AW: Problem using populate.jsp
Posted by GUNACKER Simon <sg...@EUROFUNK.COM>.
Thank you, marcel.
That solved my issues.
Regards, simon
> -----Ursprüngliche Nachricht-----
> Von: mreutegg@day.com [mailto:mreutegg@day.com] Im Auftrag von Marcel
> Reutegger
> Gesendet: Dienstag, 19. Jänner 2010 14:25
> An: dev
> Betreff: Re: Problem using populate.jsp
>
> Hi,
>
> the user list would have been the better place to ask.
>
> On Tue, Jan 19, 2010 at 14:04, GUNACKER Simon <sg...@eurofunk.com>
> wrote:
> > It doesn't work for me; I wonder if this has to do
> with my jackrabbit hopping around behind a proxy.
> > Any hints?
>
> yes, that's probably the issue. the jsp does http requests. you must
> start the jvm with proxy parameters. see here:
> http://java.sun.com/j2se/1.5.0/docs/guide/net/proxies.h
> tml
>
> regards
> marcel
http://www.Taglocity.com Tags: Produktanalyse, Personalakt, jackrabbit, Problem
Re: Problem using populate.jsp
Posted by Marcel Reutegger <ma...@gmx.net>.
Hi,
the user list would have been the better place to ask.
On Tue, Jan 19, 2010 at 14:04, GUNACKER Simon <sg...@eurofunk.com> wrote:
> It doesn't work for me; I wonder if this has to do with my jackrabbit hopping around behind a proxy.
> Any hints?
yes, that's probably the issue. the jsp does http requests. you must
start the jvm with proxy parameters. see here:
http://java.sun.com/j2se/1.5.0/docs/guide/net/proxies.html
regards
marcel
Problem using populate.jsp
Posted by GUNACKER Simon <sg...@EUROFUNK.COM>.
Hey guys,
when installing jackrabbit, there is this populate.jsp?
It doesn't work for me; I wonder if this has to do with my jackrabbit hopping around behind a proxy.
Any hints?
I'm sorry if this is the wrong mailing list; wasn't sure Where to post that question.
Regards, Simon
http://www.Taglocity.com Tags: Personalakt, jackrabbit, Problem, Produktanalyse
[jira] Updated: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2453:
-------------------------------
Attachment: JCR-2453.patch
Attached an initial draft of the required changes.
All the shared constants are moved to jackrabbit-webdav.
For now the patch simply copies the relevant code in the shared classes to o.a.j.spi2dav.server. More work is needed to avoid the duplication.
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797612#action_12797612 ]
Jukka Zitting commented on JCR-2453:
------------------------------------
I solved part of this issue by explicitly excluding the troublesome transitive dependencies in revision 896870.
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-2453.
-------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Assignee: angela
> Fix For: 2.2.0
>
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela reassigned JCR-2453:
---------------------------
Assignee: angela
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Assignee: angela
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797619#action_12797619 ]
Jukka Zitting commented on JCR-2453:
------------------------------------
> the jackrabbit-webdav project must not have any notion of JCR
What about existing classes like o.a.j.webdav.observation.ObservationConstants?
I definitely agree that we don't want to introduce a JCR API dependency on jackrabbit-webdav. But just like we include support for other WebDAV extensions like DASL or the extra properties used by Microsoft, can we not also include similar support for the JCR extensions?
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802228#action_12802228 ]
angela commented on JCR-2453:
-----------------------------
why not moving the shared code to jcr-commons? actually i already happen to put code shared davex and the server into the commons
package before... it would have been natural to move the rest as well. i can take care of that.
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797620#action_12797620 ]
angela commented on JCR-2453:
-----------------------------
> What about existing classes like o.a.j.webdav.observation.ObservationConstants?
as far as i know there is no JCR constant in there... it's a custom extension of webdav that isn't defined
by either of the dav-rfcs.
If you want to move the jcr-remoting specific stuff to the webdav project they should at least be
renamed from JCR-something to Jackrabbit-something or Day-something and put into a different *Constants
class in order to make sure that those constants have nothing to do with standard webdav.
i really don't want JCR to appear in the dav library... it's hard enough to explain why jackrabbit, which is known
as reference implementation for JCR, provides it's own webdav library. we definitely should avoid anything that
introduces additional confusions. no jcr strings within the dav-library...
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2453) Break the spi2dav dependency to
jcr-server
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797613#action_12797613 ]
angela commented on JCR-2453:
-----------------------------
i don't agree with the proposed changes. the jackrabbit-webdav project must not have any notion of JCR as
it is designed to work with any kind of webdav implementation. the constants invented for the JCR remoting over
webdav do not belong there from my point of view.
> For now the patch simply copies the relevant code in the shared classes to o.a.j.spi2dav.server
then i would rather copy the constants to spi2dav.
> Break the spi2dav dependency to jcr-server
> ------------------------------------------
>
> Key: JCR-2453
> URL: https://issues.apache.org/jira/browse/JCR-2453
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Jukka Zitting
> Attachments: JCR-2453.patch
>
>
> Currently the spi2dav component has a dependency on the jcr-server component, which is troublesome due to the extra transitive dependencies and which strictly speaking should not be necessary from an architectural point of view.
> The dependency exists mostly for sharing a number of JCR-specific WebDAV constants. I'd like to push those constants down to jackrabbit-webdav as they are essentially just shared strings and as jackrabbit-webdav already contains a number of constants used by JCR extensions.
> In addition to constant values, code in the following classes is shared between jcr-server and spi2dav: JcrValueType, NamespacesProperty, NodeTypesProperty, SearchResultProperty, SubscriptionImpl, ValuesProperty. The shared code in JcrValueType and SubscriptionImpl is mostly just about mapping constant value mappings and could fairly easily be moved to jackrabbit-webdav. The Property classes are a but trickier, but it looks like it would be possible to split the code to separate server- and client-side classes for jcr-server and spi2dav.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.