[jira] Assigned: (SLING-581) ObjectContentManagerFactoryImpl missing an SCR service interface

[ https://issues.apache.org/jira/browse/SLING-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-581: -- Assignee: Carsten Ziegeler ObjectContentManagerFactoryImpl missing an SCR service

[jira] Closed: (SLING-581) ObjectContentManagerFactoryImpl missing an SCR service interface

[ https://issues.apache.org/jira/browse/SLING-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-581. -- Resolution: Fixed Fix Version/s: JCR OCM 2.0.4 ObjectContentManagerFactoryImpl missing

[jira] Updated: (SLING-581) ObjectContentManagerFactoryImpl missing an SCR service interface

[ https://issues.apache.org/jira/browse/SLING-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-581: --- Affects Version/s: JCR OCM 2.0.2 ObjectContentManagerFactoryImpl missing an SCR service

[jira] Reopened: (SLING-581) ObjectContentManagerFactoryImpl missing an SCR service interface

[ https://issues.apache.org/jira/browse/SLING-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-581: - As explained in [1] can we please revert this fix and close this bug as works-for-me. As an

Re: [jira] Commented: (SLING-577) Patch Submission: JSP tag to evaluate JCR properties using EL

Hi, Tobias Bocanegra (JIRA) schrieb: directly accessing the DB is discouraged since all content should come from the repository. I would like to rephrase this: Directly accessing the DB is not optimal in Sling, but may be used in certain use cases. Content should be accessed through the

Re: [jira] Commented: (SLING-577) Patch Submission: JSP tag to evaluate JCR properties using EL

Hi David, your tag seems to not only access the property (which would really be possible using JSTL out of the box) but to also evaluate the contents of the property as a JSTL expression. I am not fluent enough with JSTL to tell whether such a thing is possible or not with JSTL out of the

Re: ObjectContentManagerFactoryImpl still deploying as delayed component?

Felix Meschberger wrote: Hi, Can we please revert this fix (Rev. 679680, fix for 581), because it is _not_ the real fix ;-) Ups, I didn't spend too much time looking at the activate method :( Now, I'm wondering what the better way is: adding the component as a listener in the activate

Re: ObjectContentManagerFactoryImpl still deploying as delayed component?

Hi, Carsten Ziegeler schrieb: Felix Meschberger wrote: Hi, Can we please revert this fix (Rev. 679680, fix for 581), because it is _not_ the real fix ;-) Ups, I didn't spend too much time looking at the activate method :( Now, I'm wondering what the better way is: adding the component as

script include

hi all, i'm looking for a way to include a jsp script from within another but respecting the resource type hierarchy. so for example: + myapp + A + A.jsp + content.jsp + B - sling:resourceSuperType = A + B.jsp and in my B.jsp i want to do something like:

[jira] Created: (SLING-583) Implement a file system resource provider

Implement a file system resource provider - Key: SLING-583 URL: https://issues.apache.org/jira/browse/SLING-583 Project: Sling Issue Type: New Feature Components: Samples

[jira] Commented: (SLING-583) Implement a file system resource provider

[ https://issues.apache.org/jira/browse/SLING-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616891#action_12616891 ] Felix Meschberger commented on SLING-583: - Committed an initial implementation of

Filesystem Resource Provider

Hi all, In SLING-583 I propose ResourceProvider to access filesystem resources and also committed an initial version of it to the samples/fsprovider folder in trunk. Regards Felix [1] https://issues.apache.org/jira/browse/SLING-583 PS: From the issue: The idea is to implement a

Re: script include

Hi Toby, Tobias Bocanegra schrieb: hi all, i'm looking for a way to include a jsp script from within another but respecting the resource type hierarchy. so for example: + myapp + A + A.jsp + content.jsp + B - sling:resourceSuperType = A + B.jsp and in my B.jsp

RE: ObjectContentManagerFactoryImpl still deploying as delayed component?

-Original Message- From: Felix Meschberger [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 5:30 AM To: sling-dev@incubator.apache.org Subject: Re: ObjectContentManagerFactoryImpl still deploying as delayed component? Hi, Can we please revert this fix (Rev. 679680,

Re: ObjectContentManagerFactoryImpl still deploying as delayed component?

Hi Craig Craig L. Ching schrieb: I'm still getting myself caught up with the way you're handling dependency versions, don't get me wrong, I understand why you're doing it this way, it's just taking me more time than it should to get used to it :-P No worry. I also didn't realize this concrete

Re: script include

On 7/25/08, janandith jayawardena [EMAIL PROTECTED] wrote: Hi, taking the given layout + myapp + A + A.jsp + content.jsp + B - sling:resourceSuperType = A + B.jsp If I use sling:include resource=/A addSelector=content / in B.jsp can I use

Re: script include

hi felix, On 7/25/08, Felix Meschberger [EMAIL PROTECTED] wrote: Hi Toby, Tobias Bocanegra schrieb: hi all, i'm looking for a way to include a jsp script from within another but respecting the resource type hierarchy. so for example: + myapp + A + A.jsp +