Re: option overwrite:=true
Hi Vladislav, hi, I have this in my pom.xml: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId extensionstrue/extensions configuration instructions Sling-Initial-Content initial-content;overwrite:=true /Sling-Initial-Content /instructions /configuration /plugin But if I reinstall bundle I have still old files in Sling. This could be an issue. Please, would you mind reporting this issue in Jira [1]?. Regards, Juanjo. [1] https://issues.apache.org/jira/browse/SLING
Re: option overwrite:=true
Unfortunately, I don't have access for creating new issue. Can you create this issue, please? /**/ Best regards / S pozdravem Vladislav Krejčiřík http://www.vkrejcirik.info Juan José Vázquez Delgado napsal(a): Ok, no problem. For which component? JCR ContentLoader
Re: option overwrite:=true
Unfortunately, I don't have access for creating new issue. You can signup for an account here [1]. [1] https://issues.apache.org/jira/secure/Dashboard.jspa Regards, Juanjo.
[jira] Created: (SLING-859) option overwrite:=true
option overwrite:=true -- Key: SLING-859 URL: https://issues.apache.org/jira/browse/SLING-859 Project: Sling Issue Type: Bug Components: JCR Contentloader Environment: MS Windows XP, intel core 2 duo Reporter: Vladislav Krejcirik I have this in my pom.xml: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId extensionstrue/extensions configuration instructions Sling-Initial-Content initial-content;overwrite:=true /Sling-Initial-Content /instructions /configuration /plugin But if I reinstall bundle I have still old files in Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-859) option overwrite:=true
[ https://issues.apache.org/jira/browse/SLING-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-859: Assignee: Juan Jose Vazquez Delgado Remaining Estimate: 0h Original Estimate: 0h option overwrite:=true works form me in Sling trunk revision 744966. Can you look for any stack trace in Sling error log?. In the other hand, how are you re-installing the bundle? with the Felix web console?. option overwrite:=true -- Key: SLING-859 URL: https://issues.apache.org/jira/browse/SLING-859 Project: Sling Issue Type: Bug Components: JCR Contentloader Environment: MS Windows XP, intel core 2 duo Reporter: Vladislav Krejcirik Assignee: Juan Jose Vazquez Delgado Original Estimate: 0h Remaining Estimate: 0h I have this in my pom.xml: plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId extensionstrue/extensions configuration instructions Sling-Initial-Content initial-content;overwrite:=true /Sling-Initial-Content /instructions /configuration /plugin But if I reinstall bundle I have still old files in Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Proposal: Extend o.a.s.j.c.i.r.XmlReader to support XSL transformations
Hi Vidar, Vidar Ramdal schrieb: On Fri, Feb 13, 2009 at 7:30 PM, Felix Meschberger fmesc...@gmail.com wrote: Hi, Sounds like an interesting idea, we could even provide some default transformations... The only fear I have is, that this might introduce a huge pile of dependencies ? I think we should be fine by just depending on Xalan, which again depends on Xerces. I'll have a look at it over the weekend. Sorry for the late reply. Incidentally, I just played around with XSLT over the weekend and JAXP (javax.xml.transform) seems to have everything in it, so it perfectly works without any more depdencies. Regards Felix
Re: Proposal: Extend o.a.s.j.c.i.r.XmlReader to support XSL transformations
Vidar Ramdal schrieb: On Fri, Feb 13, 2009 at 6:22 PM, Vidar Ramdal vi...@idium.no wrote: One easy way to get extensible format support, at least when speaking of XML formats, is to let XmlReader look for a reference to an XSL stylesheet in the XML file (?xml-stylesheet type=text/xsl href=stylesheet.xsl?). I've come really close to implementing this, but I have hit a wall when it comes to resolving the location of the XSL. In the example above, one would consider stylesheet.xsl to be a relative path to the XSL - relative from the XML file. However, I can't make XmlReader resolve the XSL file, as XmlReader only gets an InputStream of the XML, which contains no information on the XML's location. One option would be to change o.a.s.j.c.i.ContentReader#parse(InputStream, ContentCreator) to parse(URL, ContentCreator). This would mean making ContentReaders responsible for opening and closing the InputStream from the URL. It seems that every caller of ContentReader.parse knows the URL of the inputstream it is passing to the ContentReader, so that should not be too much work. +1 to this change. It makes perfect sense. Another option would be to only support absolute URLs when refering to the XSL file. This works in my current implementation, as long as the XSL is not located in a bundle. But in many cases the XSL *would* be supplied in a bundle, I believe bundle resources can be addressed by bundle://bundle-id/etc, but I don't know the bundle ID before the bundle is installed, right? Any suggestions? Lets go with the ContentReader API change you propose. It is not exported from the bundle so we are free to adapt it as we need. Regards Felix
Re: documentation for server-side ECMAscript
Lars Trieloff's cheat sheet might also help: http://dev.day.com/microsling/content/blogs/main/cheatsheet.html Michael On Tue, Feb 17, 2009 at 9:16 AM, Felix Meschberger fmesc...@gmail.comwrote: Hi, Valentin Jacquemin schrieb: Something that helped me a lot was to have a look at the unit tests particularly under /sling_src_home/scripting/javascript/src/test/java/org/apache/sling/scripting (it seems that the Sling svn is not alive anymore.. ) Yes, the Apache SVN server seems to be out of service at the moment :-( Regards Felix My 0.5 cents ;) On Mon, Feb 16, 2009 at 8:19 PM, Felix Meschberger fmesc...@gmail.com wrote: Hi, There are a few server side scripts in the sample modules as well as the integration tests (look for .esp files). Additionally [1] might also help. Regards Felix [1] http://cwiki.apache.org/SLING/scripting-variables.html vkrejcirik schrieb: Hi, can I ask you, if it exists any documentation or examples of server-side ECMAscript which is uses for rendering of content? -- Michael Marth | http://dev.day.com/
Re: JCR meetup in Amsterdam?
Hi, On Fri, Feb 13, 2009 at 10:55 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: On Thu, Feb 12, 2009 at 11:05 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: The meetup will only happen if we can find enough attendees, presentations and sponsors. Please let me know, preferably already by the end of this week, if you'd be interested in participating. As was pointed out in private, I didn't leave any place for people to sign up. I just created a wiki page for that, see [1]. You can also email me in private if you like. [1] http://wiki.apache.org/jackrabbit/JcrMeetupMarch2009 Thanks for everyone who's already signed up on the wiki or in private email! However, we're still short of enough interest to make the meetup worth organizing. So please let me know if you're considering attending. If we can't find enough interest, we'll do just a normal BoF session at the ApacheCon. BR, Jukka Zitting
Compilation failure: org.osgi.framework.Constants stuff
Hi, I'm unable to build Sling at the moment (fresh checkout, clean install): INFO] Compilation failure /Users/vramdal/dev/sling-trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java:[396,68] cannot find symbol symbol : variable FRAMEWORK_STORAGE location: interface org.osgi.framework.Constants /Users/vramdal/dev/sling-trunk/launchpad/base/src/main/java/org/apache/sling/launchpad/base/impl/Sling.java:[397,72] cannot find symbol symbol : variable FRAMEWORK_BEGINNING_STARTLEVEL location: interface org.osgi.framework.Constants I see Felix (Meschberger) has updated the dependency to (Apache) Felix Framework 1.5.0-SNAPSHOT - maybe something has changed in 1.5.0-SNAPSHOT since then? -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway
[jira] Created: (SLING-860) OpenId authenticator problem
OpenId authenticator problem Key: SLING-860 URL: https://issues.apache.org/jira/browse/SLING-860 Project: Sling Issue Type: Question Components: Extensions Reporter: Michael Marth Priority: Minor this is probably a configuration problem, but I do not know how to get around this: Using the OpenId authenticator I cannot write to the repository. -- How to reproduce: - install bundle espblog from samples - install bundle openid from extensions - in system config switch off allow anon access as described in openid-authenticator description - do openid login (and make sure you have no http basic auth credentials in the request) - try to write to repository - javax.jcr.AccessDeniedException: /: not allowed to modify item -- I believe the openid_user has no write acccess which would explain this behaviour. But how do I get around it? Do I have to write my own AccessManager? Do I miss something? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-857) Support XSL transformations when importing XML for initial-content
[ https://issues.apache.org/jira/browse/SLING-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vidar S. Ramdal resolved SLING-857. --- Resolution: Fixed Support XSL transformations when importing XML for initial-content -- Key: SLING-857 URL: https://issues.apache.org/jira/browse/SLING-857 Project: Sling Issue Type: New Feature Components: JCR Contentloader Reporter: Vidar S. Ramdal Assignee: Vidar S. Ramdal Priority: Minor Fix For: JCR Contentloader 2.0.4 Attachments: SLING-857.diff As described at http://markmail.org/thread/qxi6qw77vgymrdim Implementing support for XSL transformations while loading initial-content XML, by looking for the xml-stylesheet processing instruction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-857) Support XSL transformations when importing XML for initial-content
[ https://issues.apache.org/jira/browse/SLING-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vidar S. Ramdal updated SLING-857: -- Attachment: SLING-857.diff Patch for the jcr/contentloader bundle. This implements support for ?xml-stylesheet? processing instructions in initial-content XML. The reference to the XSL file is relative to the location of the XML file. For relative URLs (bundle:// protocol) to work, you must set felix.service.urlhandlers=true in sling.properties. Support XSL transformations when importing XML for initial-content -- Key: SLING-857 URL: https://issues.apache.org/jira/browse/SLING-857 Project: Sling Issue Type: New Feature Components: JCR Contentloader Reporter: Vidar S. Ramdal Assignee: Vidar S. Ramdal Priority: Minor Fix For: JCR Contentloader 2.0.4 Attachments: SLING-857.diff As described at http://markmail.org/thread/qxi6qw77vgymrdim Implementing support for XSL transformations while loading initial-content XML, by looking for the xml-stylesheet processing instruction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
felix.service.urlhandlers disabled?
Is there a reason for felix.service.urlhandlers=false in sling.properties? I had another case with this earlier, and I was under the impression that urlhandlers were to be enabled by default in the next release [1]. [1] http://markmail.org/message/qwfetelev7qjrzge -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway
Re: Proposal: Extend o.a.s.j.c.i.r.XmlReader to support XSL transformations
On Tue, Feb 17, 2009 at 1:05 PM, Felix Meschberger fmesc...@gmail.com wrote: Lets go with the ContentReader API change you propose. It is not exported from the bundle so we are free to adapt it as we need. Patch awaiting approval at https://issues.apache.org/jira/browse/SLING-857 -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway
[jira] Commented: (SLING-859) option overwrite:=true
[
https://issues.apache.org/jira/browse/SLING-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674317#action_12674317
]
Vladislav Krejcirik commented on SLING-859:
---
I re-install bundle with Felix web console.
In inital content is every node of type nt:unstructured.
error log:
17.02.2009 20:18:05.453 *ERROR* [Background
Updateorg.apache.servicemix.smx-sling.servicemix-sling-console (45)]
org.apache.sling.jcr.contentloader.internal.Loader Cannot load initial content
for bundle org.apache.servicemix.smx-sling.servicemix-sling-console : no
definition found in parent node's node type for new node: no matching child
node definition found for {}servicemix
javax.jcr.nodetype.ConstraintViolationException: no definition found in parent
node's node type for new node: no matching child node definition found for
{}servicemix: no matching child node definition found for {}servicemix
at
org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:752)
at
org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:718)
at
org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:665)
at org.apache.jackrabbit.core.NodeImpl.addNode(NodeImpl.java:1987)
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:470)
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:416)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:362)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:339)
at
org.apache.sling.jcr.contentloader.internal.Loader.installContent(Loader.java:246)
at
org.apache.sling.jcr.contentloader.internal.Loader.registerBundleInternal(Loader.java:172)
at
org.apache.sling.jcr.contentloader.internal.Loader.registerBundle(Loader.java:112)
at
org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:130)
at
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619)
at
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3601)
at org.apache.felix.framework.Felix._startBundle(Felix.java:1595)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1544)
at
org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4040)
at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3268)
at org.apache.felix.framework.Felix._updateBundle(Felix.java:1905)
at org.apache.felix.framework.Felix.updateBundle(Felix.java:1748)
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:389)
at
org.apache.felix.webconsole.internal.core.InstallAction$2.doRun(InstallAction.java:281)
at
org.apache.felix.webconsole.internal.core.InstallAction$InstallHelper.run(InstallAction.java:329)
Caused by: javax.jcr.nodetype.ConstraintViolationException: no matching child
node definition found for {}servicemix
at
org.apache.jackrabbit.core.nodetype.EffectiveNodeType.getApplicableChildNodeDef(EffectiveNodeType.java:735)
at
org.apache.jackrabbit.core.NodeImpl.getApplicableChildNodeDefinition(NodeImpl.java:878)
at
org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:748)
... 24 more
javax.jcr.nodetype.ConstraintViolationException: no matching child node
definition found for {}servicemix
at
org.apache.jackrabbit.core.nodetype.EffectiveNodeType.getApplicableChildNodeDef(EffectiveNodeType.java:735)
at
org.apache.jackrabbit.core.NodeImpl.getApplicableChildNodeDefinition(NodeImpl.java:878)
at
org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:748)
at
org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:718)
at
org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:665)
at org.apache.jackrabbit.core.NodeImpl.addNode(NodeImpl.java:1987)
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:470)
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:416)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:362)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:339)
at
org.apache.sling.jcr.contentloader.internal.Loader.installContent(Loader.java:246)
at
org.apache.sling.jcr.contentloader.internal.Loader.registerBundleInternal(Loader.java:172)
at
[VOTE] Source Tree Restructuring
Hi, we recently discussed the new structure for our source tree. To finalize this, I'll start this vote (lazy consensus applies). The following is the initial setup - we can of course move a bundle to one or the other location after the initial restructuring. But as we are heading for a release real soon now, we should do this asap! The outline above splits up the integration tests for the bundles and the contrib area (both tests are in the corresponding launchpad directories). This is in order to be able to build and test Sling without the contrib stuff. The contrib stuff will be buildable by a profile - as well as the example. So please cast your votes. trunk/ +-- maven (Maven Plugins) +-- parent/ (Parent Project) +-- launchpad (Launchpad Application) +-- app +-- webapp +-- base +-- bundles +-- content +-- tests +-- bundles/ +-- api (The Sling API) +-- engine (The Sling Core Engine) +-- scripting (ScriptEngines) +-- api +-- core +-- javascript +-- jsp +-- jsp-taglib +-- commons (Helper libraries) +-- log +-- json +-- osgi +-- mime +-- testing +-- scheduler +-- threads +-- jcr (JCR related modules) +-- api +-- base +-- classloader +-- contentloader +-- jackrabbit-api +-- jackrabbit-server +-- ocm +-- resource +-- webdav +-- servlets (Servlet Support) +-- get +-- post +-- resolver +-- extensions (Extension bundles) +-- adapter +-- bundleresource +-- httpauth +-- event +-- openidauth +-- threaddump +-- contrib (Contributions etc.) +-- commons +-- scripting (ScriptEngines) +-- freemarker +-- java +-- jst +-- python +-- ruby +-- scala +-- velocity +-- jcr (JCR related modules) +-- jackrabbit-client +-- launchpad (Launchpad Application) +-- jcrapp +-- testing (contrib stuff) +-- extensions (Extension bundles) +-- apt +-- dojo +-- dojo-sling +-- i18n +-- gwt +-- jcrinstall +-- obr (OBR Server, was osgi/obr) +-- runmode +-- samples +-- ... existing samples ... Thanks Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Source Tree Restructuring
+1 Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Source Tree Restructuring
just out of curiosity: why is jcrinstall not in jcr ? i find it awkward, that a JCR based framework keeps a JCR based bundle/config loading in contrib :-) regards, toby On 2/17/09, Carsten Ziegeler cziege...@apache.org wrote: Hi, we recently discussed the new structure for our source tree. To finalize this, I'll start this vote (lazy consensus applies). The following is the initial setup - we can of course move a bundle to one or the other location after the initial restructuring. But as we are heading for a release real soon now, we should do this asap! The outline above splits up the integration tests for the bundles and the contrib area (both tests are in the corresponding launchpad directories). This is in order to be able to build and test Sling without the contrib stuff. The contrib stuff will be buildable by a profile - as well as the example. So please cast your votes. trunk/ +-- maven (Maven Plugins) +-- parent/ (Parent Project) +-- launchpad (Launchpad Application) +-- app +-- webapp +-- base +-- bundles +-- content +-- tests +-- bundles/ +-- api (The Sling API) +-- engine (The Sling Core Engine) +-- scripting (ScriptEngines) +-- api +-- core +-- javascript +-- jsp +-- jsp-taglib +-- commons (Helper libraries) +-- log +-- json +-- osgi +-- mime +-- testing +-- scheduler +-- threads +-- jcr (JCR related modules) +-- api +-- base +-- classloader +-- contentloader +-- jackrabbit-api +-- jackrabbit-server +-- ocm +-- resource +-- webdav +-- servlets (Servlet Support) +-- get +-- post +-- resolver +-- extensions (Extension bundles) +-- adapter +-- bundleresource +-- httpauth +-- event +-- openidauth +-- threaddump +-- contrib (Contributions etc.) +-- commons +-- scripting (ScriptEngines) +-- freemarker +-- java +-- jst +-- python +-- ruby +-- scala +-- velocity +-- jcr (JCR related modules) +-- jackrabbit-client +-- launchpad (Launchpad Application) +-- jcrapp +-- testing (contrib stuff) +-- extensions (Extension bundles) +-- apt +-- dojo +-- dojo-sling +-- i18n +-- gwt +-- jcrinstall +-- obr (OBR Server, was osgi/obr) +-- runmode +-- samples +-- ... existing samples ... Thanks Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Closed: (SLING-851) SlingNodeStore.accept() requiring all values of an array query parameter
[
https://issues.apache.org/jira/browse/SLING-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Mietz Egli closed SLING-851.
-
Verified fixed in revision 745256. Thanks!
SlingNodeStore.accept() requiring all values of an array query parameter
Key: SLING-851
URL: https://issues.apache.org/jira/browse/SLING-851
Project: Sling
Issue Type: Bug
Components: Extensions
Environment: URL:
http://svn.apache.org/repos/asf/incubator/sling/trunk/extensions/dojo-sling
Repository Root: http://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 741703
Node Kind: directory
Schedule: normal
Last Changed Author: fmeschbe
Last Changed Rev: 734658
Last Changed Date: 2009-01-15 02:25:41 -0800 (Thu, 15 Jan 2009)
Reporter: Paul Mietz Egli
Assignee: Felix Meschberger
Attachments: SlingNodeStore.patch, test.html
Queries against a SlingNodeStore that contain properties with multiple values
like the following do not return any objects:
div dojoType=dojox.data.SlingNodeStore url=/content jsId=nodeStore
query={ 'jcr:primaryType' : ['nt:folder','nt:file'] }/div
The accept() method of SlingNodeStore appears to require that the node
property value matches ALL of the query array values, not just one value.
Changing the method to set the onematch bool to true if any of the elements
in the array match appears to solve this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] Source Tree Restructuring
Tobias Bocanegra wrote: just out of curiosity: why is jcrinstall not in jcr ? i find it awkward, that a JCR based framework keeps a JCR based bundle/config loading in contrib :-) :) Actually I agree that jcrinstall should be moved into jcr but into contrib/jcr :) We're moving all stuff which is not ready to be released into the contrib folder and jcrinstall is one of them. Carsten -- Carsten Ziegeler cziege...@apache.org
