[
https://issues.apache.org/jira/browse/SLING-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-41:
---
Summary: Create synthetic content in sling:include if real content does not
exist (was: Create
[
https://issues.apache.org/jira/browse/SLING-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-41.
--
Resolution: Fixed
First I added another implementation of the Content interface:
org.apache.slin
[
https://issues.apache.org/jira/browse/SLING-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-41:
---
Component/s: Content
Add Content component as the SyntheticContent has been created as part of
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532592
]
Felix Meschberger commented on SLING-31:
Hmm, the BundleDeployFileMojo has a Java five attribute (@Override) at
Potential NullPointerException when initializing Components
---
Key: SLING-42
URL: https://issues.apache.org/jira/browse/SLING-42
Project: Sling
Issue Type: Bug
Components: Co
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532632
]
Felix Meschberger commented on SLING-31:
Thanks for the hint. I will update the the Sling parent pom to reer to
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-31:
--
Assignee: Felix Meschberger
> maven-sling-plugin: build failure caused by qdox/maven-plug
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-31:
--
Attachment: pom.diff
Maven 2.07, I only had Maven Plugin Plugin 2.0 in my local m2 repo.
Adding Maven Plu
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532622
]
olli edited comment on SLING-31 at 10/5/07 4:19 AM:
Maven 2.0.7, I only had Maven Plugin Pl
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-31.
Resolution: Fixed
Fix Version/s: 2.0.0
Added
or
[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532653
]
Felix Meschberger commented on SLING-40:
Removed the old interfaces in the org.apache.sling.core.mapper package
[
https://issues.apache.org/jira/browse/SLING-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-42:
--
Assignee: Felix Meschberger
> Potential NullPointerException when initializing Components
[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532659
]
Felix Meschberger commented on SLING-40:
Renamed the URLMapperFilter to ComponentResolverFilter and added the
[
https://issues.apache.org/jira/browse/SLING-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-42.
--
Resolution: Fixed
Fixed by reorganizing the order in which the ComponentRequestHandlerImpl is
ac
[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-40.
--
Resolution: Fixed
This issue can be closed as the service has been implemented and the old
URLMa
[
https://issues.apache.org/jira/browse/SLING-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-39.
--
Resolution: Fixed
Adapted various parts in Sling Core for this.
(1) The methods to access the re
Hi all,
As we are new to the incubator, we have to report monthly and the
reports are due again :-)
I created a page on our wiki [1] to catch what we ultimately would
report. Please add anything you might feel needed such that we can
finalize the report by Oct. 10.
Thanks and Regards
Felix
[1]
Extend the sling-app project by support to build a complete jar file
Key: SLING-43
URL: https://issues.apache.org/jira/browse/SLING-43
Project: Sling
Issue Type: Improvemen
Hi Edgar,
Sorry for the belated answer, I was busy fixing issues and extending
Sling over the last few days.
Taking your original mail apart for easier tracking of the issues
raised.
Am Montag, den 24.09.2007, 11:34 -0300 schrieb Edgar Poce:
> First of all congratulations for the good work!. I'
Hi,
Am Montag, den 24.09.2007, 11:34 -0300 schrieb Edgar Poce:
> Another doubt is what's the recommended practice to create a simple
> sling component with write capabilities, how the component should
> access the jcr repository to perform write operations? and how the jcr
> session should be acqu
Add ContentManager.create(String path, Content content) method
--
Key: SLING-44
URL: https://issues.apache.org/jira/browse/SLING-44
Project: Sling
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/SLING-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-43.
--
Resolution: Fixed
Commited the extend pom with a new build profile "full", which builds said JAR
Hi all,
Upon replying to Edgar's question regarding writing Content, I came to
thinking, that the ContentManager is a core interface of Sling and
probably should be made available more prominently. The most prominent
location for an interface in Sling would be the Sling API itself.
What do you th
[
https://issues.apache.org/jira/browse/SLING-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-44:
---
Description:
The create(String, Class, Map) method was once assumed to take the
responsibility
Felix Meschberger wrote:
> Hi all,
>
> Upon replying to Edgar's question regarding writing Content, I came to
> thinking, that the ContentManager is a core interface of Sling and
> probably should be made available more prominently. The most prominent
> location for an interface in Sling would be
Am Freitag, den 05.10.2007, 17:14 +0200 schrieb Carsten Ziegeler:
> > What do you think ? If feedback is positive, I would also include this
> > in the Sling API proposal (SLING-28).
> >
> I'm not sure - it definitly makes repository based components much
> easier, but draws in some stuff into the
On 5 Oct 2007, at 15:56, Felix Meschberger wrote:
What do you think of moving the o.a.s.content.ContentManager interface
to the Sling API and provide it through the ComponentRequest
instead of
having to access a request attribute:
public interface ComponentRequest extends HttpServletReq
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
> Having done some work recently with Day Communique, one of the
> annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because we initially did not extend
HttpServletRequest but
On 5 Oct 2007, at 17:30, Felix Meschberger wrote:
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because w
29 matches
Mail list logo
