[jira] Resolved: (SLING-172) Sling console configuration management does not display multivalue selects correctly
[ https://issues.apache.org/jira/browse/SLING-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-172. - Resolution: Fixed Fixed a generics issue in the commons/json project: The generic arguments where declared as Collection and Map. Such arguments do not accept ArrayList because the generic type hierarchy is ignored, thus String != Object. The fix is to declare the arguments as Collection and Map (I think it is a valid assumption to require String-keyed maps. Maybe this assumption is wrong, and we might then have to change this to Map. Fixed in Rev. 613081. To use (1) compile commons/json and install in local maven repo and (2) rebuild osgi/console-web and deploy to Sling Please close if this fixes your issue. Thanks. > Sling console configuration management does not display multivalue selects > correctly > > > Key: SLING-172 > URL: https://issues.apache.org/jira/browse/SLING-172 > Project: Sling > Issue Type: Bug > Components: Console >Affects Versions: 2.0.0 > Environment: Windows XP, Java 1.5, Tomcat 6.x >Reporter: Alexander Saar >Assignee: Felix Meschberger >Priority: Minor > Attachments: screenshot-1.jpg > > > The display of multivalue selection boxes in the configuration management > section of the Sling console does not work. The array of possible selections > is split into single characters and each of them is displayed as a single > entry in the selection list. This prevents changing the log level and other > multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GHOP issue 2: Design two related logos for the sling project
Here's what I think are the final logos. http://bitliquid.com/private/sling/final/ (It's pretty much the same as the previous proposal, but with some additional variations, for B&W and for a favicon) - Are there any remaining issues? Otherwise,where should I upload these? On 17/01/2008, at 7:27 PM, Felix Meschberger wrote: Hi Paul, Am Donnerstag, den 17.01.2008, 09:11 +0100 schrieb Bertrand Delacretaz: Hi Paul, On Jan 17, 2008 6:59 AM, Paul Walker <[EMAIL PROTECTED]> wrote: http://bitliquid.com/private/sling/Proposal-2-1.jpg http://bitliquid.com/private/sling/Proposal-2-1.svg... Great work! I like it. ++1. Thanks. ...The variant on the bottom was made to address Bertrand Delacretaz's concern about the S blending into the top Border. I prefer the other version, but it's not all up to me… I do prefer this bottom variant, though it might need another interruption in the line that goes from the S to the G, somewhere close to the G. But if people prefer the top logos, no big deal - let's hear what others think. I only just now realized why there are actually two µ logos. Probably having the line uninterrupted is slightly better ? Because it mimicks the word "Sling" a bit by creating the illusion of a sling. If we would interrupt at the g, the µ might seem to hang out in the air ? BTW: The logo also looks good when printed B&W. Regards Felix -Bertrand
[jira] Resolved: (SLING-169) Update jackrabbit references to 1.4
[ https://issues.apache.org/jira/browse/SLING-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padraic Hannon resolved SLING-169. -- Resolution: Fixed Fix Version/s: 2.0.0 Checked in with revision 612985 > Update jackrabbit references to 1.4 > --- > > Key: SLING-169 > URL: https://issues.apache.org/jira/browse/SLING-169 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Padraic Hannon >Assignee: Padraic Hannon > Fix For: 2.0.0 > > Attachments: sling-jackrabbit-1.4.patch > > > Now that jackrabbit has released the 1.4 version we should update references > within sling to 1.4 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-169) Update jackrabbit references to 1.4
[ https://issues.apache.org/jira/browse/SLING-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padraic Hannon reassigned SLING-169: Assignee: Padraic Hannon > Update jackrabbit references to 1.4 > --- > > Key: SLING-169 > URL: https://issues.apache.org/jira/browse/SLING-169 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Padraic Hannon >Assignee: Padraic Hannon > Fix For: 2.0.0 > > Attachments: sling-jackrabbit-1.4.patch > > > Now that jackrabbit has released the 1.4 version we should update references > within sling to 1.4 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Everything is a Resource
Hi all, I finally somewhat finished the prototype [1] implementation of the "Everything is a Resource" concept and updated the wiki page. The prototype is not 100% complete yet - Filter support and Resource Events are not implemented yet - but I think it nicely shows where I wanted to be heading. In particular it is now possible to directly address scripts (and servlets) to call them without requiring a node to be existing in the repository just to have a hook. In addition, OCM mapping is supported through the Adapter framework thus being able to split OCM mapping and resource resolution. Of course I think, the concept and implementation is worth it. Therefore, I would like to merge this into the trunk sometime next week, unless there are objections. Regards Felix [1] http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/resource Am Samstag, den 29.12.2007, 20:51 +0100 schrieb Felix Meschberger: > Hi all, > > After the recent thread on scripting "everything" and some off-line > discussions around this matter, I come to the conclusion, that it is > about time to introduce the Sling Paradigm: > > Everything is a Resource > > If Sling would be enhanced to make the ResourceResolver more flexibel > and powerful by the addition of ResourceProvider instances to define a > virtual resource tree accessible (and iterable) through the > ResourceResolver, we can make Sling much more scriptable than it is > today. > > The idea is to make servlets and filters registered as OSGi services > available through the ResourceResolver just like normal scripts. The > ServletResolver and Filter handlers could then just ask the > ResourceResolver for resources and adaptTo(Servlet.class) and > adaptTo(Filter.class), resp. Calling scripts from other scripts would > also be available through resolving the script Resource through the > ResourceResolver and adaptTo(SlingScript.class). > > Thus we drop the ScriptResolver, while the SerlvetResolver mainly > remains for Sling to be able to handle requests. > > Of course the adaptor mechanism must be enhanced to make it extensible. > I propose the definition of a Adaptable interface defining the > adaptTo(Class) method and an AdapterFactory mechanism providing easy > extensibility. This is built after the Eclipse PlatformObject, > IAdapterManager and IAdapterFactory but leverages the OSGi service > registry instead of the Eclipse Plugin mechanism. > > I wrote up a wiki page on this concept at [1]. > > Comments are welcome. I will try to set up a first prototype in the > whiteboard in the next few days. > > Regards > Felix > > [1] http://cwiki.apache.org/SLING/everything-is-a-resource.html
Re: Rethinking Exceptions in Sling
Hi all, After all the feedback and some silent time, I updated the Wiki [1] and the prototype [2] as follows: * Remove HttpStatusCodeException * Add ResourceNotFoundException I noone objects, I will start implementing these changes to the API sometime next week and also start adapting the uses throughout the repository. Regards Felix [1] http://cwiki.apache.org/confluence/x/DR4B [2] http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/effective_exceptions Am Samstag, den 29.12.2007, 20:58 +0100 schrieb Felix Meschberger: > Hi all, > > Prompted by a blog by Alexander Klimetschek [1] and a very interesting > paper on exceptions [2] I set back to think about the exceptions in the > Sling API and wrote a wiki page on this subject [3]. > > To summarize, we should make the SlingException a RuntimeException and > all exceptions defined in the Sling API extend SlingException. Together > with appropriate catching inside Sling itself (letting RuntimeExceptions > pass through generally) this should help us streamline exception > handling. > > A prototype API definition may be found in the whiteboard at [4]. > > What do you think ? > > Regards > Felix > > [1] > http://weblogs.goshaky.com/weblogs/alexkli/entry/exception_best_practices > [2] http://dev2dev.bea.com/pub/a/2006/11/effective-exceptions.html > [3] http://cwiki.apache.org/SLING/effective-exceptions.html > [4] > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/effective_exceptions
Re: Upgrade Jackrabbit Dependencies
Hi, On Jan 17, 2008 8:20 PM, <[EMAIL PROTECTED]> wrote: > Will do, got my apache login info yesterday. You now also have the required karma to commit to incubator/sling. BR, Jukka Zitting
Re: Upgrade Jackrabbit Dependencies
Will do, got my apache login info yesterday. Pih Sent via BlackBerry from T-Mobile -Original Message- From: Felix Meschberger <[EMAIL PROTECTED]> Date: Thu, 17 Jan 2008 08:02:51 To:sling-dev@incubator.apache.org Subject: Re: Upgrade Jackrabbit Dependencies Hi Paddy, Am Mittwoch, den 16.01.2008, 09:25 -0800 schrieb Padraic Hannon: > I created a jira ticket: https://issues.apache.org/jira/browse/SLING-169 Thanks. So, I suggest you just go ahead and apply the patch :-) Regards Felix
[jira] Created: (SLING-173) SlingRequestPathInfo fails to parse extension in some cases
SlingRequestPathInfo fails to parse extension in some cases --- Key: SLING-173 URL: https://issues.apache.org/jira/browse/SLING-173 Project: Sling Issue Type: Bug Components: Core Reporter: Bertrand Delacretaz For example in this case: ResourceMetadata.RESOLUTION_PATH = "/ujax-tests" requestPath = "/ujax-tests/12005879509741.json" The extension is null instead of being .json. The MicroslingRequestPathInfoTest class from the the microsling-core project might help in fixing this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Reference to SlingRepository
Hi Carsten,
I have installed the newest SCR bundle (Rev 612379). The line numbers
have changed, but the problem still persists:
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.felix.scr.impl.DependencyManager.invokeBindMethod(DependencyManager.java:873)
at
org.apache.felix.scr.impl.DependencyManager.bind(DependencyManager.java:655)
at
org.apache.felix.scr.impl.ImmediateComponentManager.createImplementationObject(ImmediateComponentManager.java:204)
at
org.apache.felix.scr.impl.ImmediateComponentManager.createComponent(ImmediateComponentManager.java:134)
at
org.apache.felix.scr.impl.AbstractComponentManager.activateInternal(AbstractComponentManager.java:402)
at
org.apache.felix.scr.impl.AbstractComponentManager.enableInternal(AbstractComponentManager.java:323)
at
org.apache.felix.scr.impl.AbstractComponentManager.access$000(AbstractComponentManager.java:36)
at
org.apache.felix.scr.impl.AbstractComponentManager$1.run(AbstractComponentManager.java:94)
at
org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:85)
17.01.2008 16:38:12 *ERROR* o.a.f.scr: Unexpected problem executing task
(java.lang.NullPointerException)
java.lang.NullPointerException
at
org.apache.felix.scr.impl.ImmediateComponentManager.disposeImplementationObject(ImmediateComponentManager.java:271)
at
org.apache.felix.scr.impl.ImmediateComponentManager.deleteComponent(ImmediateComponentManager.java:151)
at
org.apache.felix.scr.impl.AbstractComponentManager.deactivateInternal(AbstractComponentManager.java:469)
at
org.apache.felix.scr.impl.AbstractComponentManager.disableInternal(AbstractComponentManager.java:486)
at
org.apache.felix.scr.impl.AbstractComponentManager.enableInternal(AbstractComponentManager.java:331)
at
org.apache.felix.scr.impl.AbstractComponentManager.access$000(AbstractComponentManager.java:36)
at
org.apache.felix.scr.impl.AbstractComponentManager$1.run(AbstractComponentManager.java:94)
at
org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:85)
Do I need to update anything else? Let me add that I'm able to get a
reference if I use the following:
/**
* @scr.reference
*/
private Repository repository;
Is it possible that the SLingRepository service is not available and
that this has lead to the problem? I have checked the components page in
the Sling console and have a factory for both: javax.jxr.Repository and
org.apache.sling.jcr.api.SlingRepository
Regards,
Alex
Carsten Ziegeler schrieb:
Hi,
Alexander Saar wrote:
Hi all,
not sure if this is the right place to ask as this is somehow OSGi
related, but I'm currently working on a service that integrates via
SCR and tries which has a reference to the SlingRepository service.
I used the following code:
/**
* @scr.reference
*/
private SlingRepository repository;
protected void bindRepository(SlingRepository repository) {
this.repository = repository;
}
just as a minor improvement: you don't need to write the bind method,
the scr plugin will generate it for you (like it generates the unbind
method as well).
Apart from that, I think I've seen this problem in an older version of
the SCR implementation (not the plugin). The line numbers from your
stacktrace do not match latest from Felix svn. So I suggest to check
latest SCR first.
Carsten
Re: Everything is a Resource
On Jan 17, 2008 4:29 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...So I set out to moving around everything Seems like SVN is slow > again, so it will take some time to get through... Same here, Sling SVN operations are extermely slow this afternoon. -Bertrand
Re: Everything is a Resource
Hi Carsten, Am Mittwoch, den 16.01.2008, 11:36 +0100 schrieb Carsten Ziegeler: > Felix Meschberger wrote: > > > > Agreed. I could imagine to move the AdapterFactory and AdapterManager > > interfaces to the Sling API, which would also somewhat illustrate more > > about the underlying concept. > Ok. So I set out to moving around everything Seems like SVN is slow again, so it will take some time to get through > > > > > Still, I cannot decide where to put the AdapterManagerImpl and the > > SlingAdaptle classes Maybe in a new commons/util bundle, which > > encapsulates such miscellaneous stuff or even a very tiny > > commons/adapter bundle ? > Hmm, the question is if this is common stuff or not :) If the interfaces > move to the API, it's not common anymore, so I would rather put it > somewhere into the "sling" category and perhaps create a sling/adapter > bundle? You are right. I create a sling/adapter project with the AdapterManagerImpl Regards Felix
[jira] Assigned: (SLING-172) Sling console configuration management does not display multivalue selects correctly
[ https://issues.apache.org/jira/browse/SLING-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-172: --- Assignee: Felix Meschberger > Sling console configuration management does not display multivalue selects > correctly > > > Key: SLING-172 > URL: https://issues.apache.org/jira/browse/SLING-172 > Project: Sling > Issue Type: Bug > Components: Console >Affects Versions: 2.0.0 > Environment: Windows XP, Java 1.5, Tomcat 6.x >Reporter: Alexander Saar >Assignee: Felix Meschberger >Priority: Minor > Attachments: screenshot-1.jpg > > > The display of multivalue selection boxes in the configuration management > section of the Sling console does not work. The array of possible selections > is split into single characters and each of them is displayed as a single > entry in the selection list. This prevents changing the log level and other > multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-172) Sling console configuration management does not display multivalue selects correctly
[ https://issues.apache.org/jira/browse/SLING-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559954#action_12559954 ] Felix Meschberger commented on SLING-172: - Thanks for reporting. This is a new issue upto now unknown to me. > Sling console configuration management does not display multivalue selects > correctly > > > Key: SLING-172 > URL: https://issues.apache.org/jira/browse/SLING-172 > Project: Sling > Issue Type: Bug > Components: Console >Affects Versions: 2.0.0 > Environment: Windows XP, Java 1.5, Tomcat 6.x >Reporter: Alexander Saar >Assignee: Felix Meschberger >Priority: Minor > Attachments: screenshot-1.jpg > > > The display of multivalue selection boxes in the configuration management > section of the Sling console does not work. The array of possible selections > is split into single characters and each of them is displayed as a single > entry in the selection list. This prevents changing the log level and other > multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-168) Add fileupload to ujax post servlet
[ https://issues.apache.org/jira/browse/SLING-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-168. --- Resolution: Fixed Committed with minor changes in revision 612842 - file to upload was missing in patch + added some comments and TODO notes. Thanks for your contribution - it's sooo easy when people provide tests with their patches! > Add fileupload to ujax post servlet > --- > > Key: SLING-168 > URL: https://issues.apache.org/jira/browse/SLING-168 > Project: Sling > Issue Type: Improvement > Components: microsling >Reporter: Tobias Bocanegra >Assignee: Bertrand Delacretaz > Attachments: fileupload-r612570.patch > > > currently uploaded files are handled like 'normal' fields and their > value is read via the MultipartPostParameter's getString(). the result > is that the properties get the string content of the uploaded files. i > think this is not what people want. > i suggest to implement a default behaviour that creates an 'nt:file' > subnode for that uploaded file if the parent node is a nt:folder, or create a > nt:resource otherwise. > enctype="multipart/form-data"> > > > results in : > + home > + tripod [nt:folder] >+ portrait [nt:file] > + jcr:content [nt:resource] >- jcr:data (data of uploaded file) > or: > + home > + tripod [nt:unstructured] >+ portrait [nt:resource] >- jcr:data (data of uploaded file) > if the name is not specified, i.e. has an /* suffix, the name of the uploaded > file is used for node creation. > if the file is not uploaded at all, the node is not deleted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-172) Sling console configuration management does not display multivalue selects correctly
[ https://issues.apache.org/jira/browse/SLING-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Saar updated SLING-172: - Attachment: screenshot-1.jpg > Sling console configuration management does not display multivalue selects > correctly > > > Key: SLING-172 > URL: https://issues.apache.org/jira/browse/SLING-172 > Project: Sling > Issue Type: Bug > Components: Console >Affects Versions: 2.0.0 > Environment: Windows XP, Java 1.5, Tomcat 6.x >Reporter: Alexander Saar > Attachments: screenshot-1.jpg > > > The display of multivalue selection boxes in the configuration management > section of the Sling console does not work. The array of possible selections > is split into single characters and each of them is displayed as a single > entry in the selection list. This prevents changing the log level and other > multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-172) Sling console configuration management does not display multivalue selects correctly
[ https://issues.apache.org/jira/browse/SLING-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Saar updated SLING-172: - Priority: Minor (was: Major) > Sling console configuration management does not display multivalue selects > correctly > > > Key: SLING-172 > URL: https://issues.apache.org/jira/browse/SLING-172 > Project: Sling > Issue Type: Bug > Components: Console >Affects Versions: 2.0.0 > Environment: Windows XP, Java 1.5, Tomcat 6.x >Reporter: Alexander Saar >Priority: Minor > Attachments: screenshot-1.jpg > > > The display of multivalue selection boxes in the configuration management > section of the Sling console does not work. The array of possible selections > is split into single characters and each of them is displayed as a single > entry in the selection list. This prevents changing the log level and other > multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-172) Sling console configuration management does not display multivalue selects correctly
Sling console configuration management does not display multivalue selects correctly Key: SLING-172 URL: https://issues.apache.org/jira/browse/SLING-172 Project: Sling Issue Type: Bug Components: Console Affects Versions: 2.0.0 Environment: Windows XP, Java 1.5, Tomcat 6.x Reporter: Alexander Saar The display of multivalue selection boxes in the configuration management section of the Sling console does not work. The array of possible selections is split into single characters and each of them is displayed as a single entry in the selection list. This prevents changing the log level and other multivalue selections with the console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-168) Add fileupload to ujax post servlet
[ https://issues.apache.org/jira/browse/SLING-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-168: - Assignee: Bertrand Delacretaz > Add fileupload to ujax post servlet > --- > > Key: SLING-168 > URL: https://issues.apache.org/jira/browse/SLING-168 > Project: Sling > Issue Type: Improvement > Components: microsling >Reporter: Tobias Bocanegra >Assignee: Bertrand Delacretaz > Attachments: fileupload-r612570.patch > > > currently uploaded files are handled like 'normal' fields and their > value is read via the MultipartPostParameter's getString(). the result > is that the properties get the string content of the uploaded files. i > think this is not what people want. > i suggest to implement a default behaviour that creates an 'nt:file' > subnode for that uploaded file if the parent node is a nt:folder, or create a > nt:resource otherwise. > enctype="multipart/form-data"> > > > results in : > + home > + tripod [nt:folder] >+ portrait [nt:file] > + jcr:content [nt:resource] >- jcr:data (data of uploaded file) > or: > + home > + tripod [nt:unstructured] >+ portrait [nt:resource] >- jcr:data (data of uploaded file) > if the name is not specified, i.e. has an /* suffix, the name of the uploaded > file is used for node creation. > if the file is not uploaded at all, the node is not deleted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Using X-Sling-Warning headers?
Hi,
Am Donnerstag, den 17.01.2008, 14:09 +0100 schrieb Bertrand Delacretaz:
> Hi,
>
> I've added this (in revision 612806) to SlingScriptServlet.service(),
> to use an X-Sling-Warning HTTP header to indicate an abnormal
> non-critical condition:
This is certainly of value during development. But I think, this (at
least this concrete example) is of little to no use for end users. They
cannot do anything about it any way. I would rather have some logging
entry or so...
>
> final String contentType = request.getResponseContentType();
> if(contentType == null) {
> res.addHeader("X-Sling-Warning",
> request.getClass().getSimpleName() + " does not provide a
> Content-Type");
> res.setContentType("text/plain");
> } else {
> res.setContentType(contentType);
> }
>
> In such a case (response Content-Type is not as expected), having the
> X-Sling-Warning header right next to other headers makes is easy to
> spot the problem, when troubleshooting one's app.
Well, I don't think, this to be a problem, because setting the content
type on behalf of the script may be seen as convenience but also as
tampering with what the script does... So in this case, we probably
would rather just not do anything if the
request.getResponseContentType() is not set.
> What do you think of using such X-Sling-... headers where it makes sense?
I am not really sure, whether it would really help or just be another
place to look at besides the log (and yes, logging must of course be
enhanced !).
Regards
Felix
Re: Log Level config in Sling console
Hi Felix, Felix Meschberger schrieb: Attachements don't work on Apache Lists (generally) ... Thanks for the hint. This is a known issue (at least to me). Thus it would be nice to have a JIRA, where you also can attache the screenshot. Thanks. Will do that. Regards, Alex
Re: Log Level config in Sling console
Hi Alex, Am Donnerstag, den 17.01.2008, 14:16 +0100 schrieb Alexander Saar: > Hello Sling team, > during my work with Sling I noticed that the Sling console does > notdisplay the values for the Log Level in the LogbackManager > configuration correctly. (see attached screenshot) Attachements don't work on Apache Lists (generally) ... > Has somebody else experienced similar problems? If so I will add an > issue to the JIRA. This is a known issue (at least to me). Thus it would be nice to have a JIRA, where you also can attache the screenshot. Thanks. Regards Felix
Re: WebDAV
Hi Bertrand, Am Donnerstag, den 17.01.2008, 14:23 +0100 schrieb Bertrand Delacretaz: > On Jan 16, 2008 6:02 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > ...I added a WebDAV bundle (jcr/webdav)... > > I have added (revision 612808) a webdav-resource-config.xml to the > bundle (hardcoded for now), to map nt:file and related nodetypes in > the "usual" way. Thanks for that. I excluded this configuration for now, because I am reluctant to this solution ... But since this is a first shot, it is probably a good move. Though, I would read the config file and set the configuration in the init() method and not in the activate() method. What I am thinking of, would be the following: * We declare all IOHandlers in org.apache.jackrabbit.server.io as SCR services. * The Sling WebDAV support listens for such services and looks at one (or two) service reference properties to decide whether to use the IOHandler service as a property or io handler or both. Whenever such a service is bound or unbound, the ResurceConfig is updated (maybe by cycling the WebDAV Servlet ??) * The standard IOManagerImpl and PropertyManagerImpl would not be configurable and always be used * The node types list for the and elements could be a String[] property for the WebDAV support service. * For the filtering, the class is a string property and the nodetypes and namespaces are settings are String[] properties for the WebDAV support service. WDYT ? Regards Felix > > -Bertrand
Re: Eating exceptions in activate() methods?
Hi,
Am Donnerstag, den 17.01.2008, 14:24 +0100 schrieb Bertrand Delacretaz:
> The diffs of my revision 612808 changes include this, in
> SimpleWebDavServlet.activate():
>
>try {
> -httpService.registerServlet(context, this, initparams, null);
> -
> -// set the contextPath field to signal successfull registration
> -this.contextPath = context;
> -
> -} catch (NamespaceException ne) {
> -// context collision
> -
> -} catch (ServletException se) {
> -// servlet initialization failure
> -
> -}
>
> + // Register servlet, and set the contextPath field to
> signal successful registration
> + httpService.registerServlet(context, this, initparams, null);
> + this.contextPath = context;
>
> Was there any reason to eat these exceptions?
Actually, they should not be eaten silently. This is just a left-over
from the get it up and running quickly time.
Rather my intention would be to catch them and log them with an
appropriate message. I would let them go up to the SCR because that one
cannot do anything about it other than screaming.
Regards
Felix
>
> To me it seems better to let the framework know that something went wrong.
>
> -Bertrand
[jira] Closed: (SLING-170) WebDAV: Prevent NullPointerException when not supplying a workspace
[ https://issues.apache.org/jira/browse/SLING-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-170. --- Resolution: Fixed Implemented the redirect to the default workspace in Rev. 612782 > WebDAV: Prevent NullPointerException when not supplying a workspace > --- > > Key: SLING-170 > URL: https://issues.apache.org/jira/browse/SLING-170 > Project: Sling > Issue Type: Improvement > Components: Repository >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: 2.0.0 > > > When accessing the root of the Simple WebDAV Servlet, a NullPointerException > may be thrown by the Jackrabbit implementation (This will be the cause for > another issue of course). > For our implementation it would make sense to redirect (temporarily) to the > default workspace if the servlet root is accessed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Reference to SlingRepository
Hi,
Alexander Saar wrote:
Hi all,
not sure if this is the right place to ask as this is somehow OSGi
related, but I'm currently working on a service that integrates via SCR
and tries which has a reference to the SlingRepository service.
I used the following code:
/**
* @scr.reference
*/
private SlingRepository repository;
protected void bindRepository(SlingRepository repository) {
this.repository = repository;
}
just as a minor improvement: you don't need to write the bind method,
the scr plugin will generate it for you (like it generates the unbind
method as well).
Apart from that, I think I've seen this problem in an older version of
the SCR implementation (not the plugin). The line numbers from your
stacktrace do not match latest from Felix svn. So I suggest to check
latest SCR first.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
[jira] Closed: (SLING-171) NPE in SlingScriptResolver#findScript() implementation
[ https://issues.apache.org/jira/browse/SLING-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-171. -- Resolution: Fixed > NPE in SlingScriptResolver#findScript() implementation > -- > > Key: SLING-171 > URL: https://issues.apache.org/jira/browse/SLING-171 > Project: Sling > Issue Type: Bug > Components: Scripting >Reporter: christian >Assignee: Carsten Ziegeler >Priority: Minor > Attachments: scriptresolver.patch > > > calling findScript() with non null arguments which point to a script a NPE is > thrown... > There are two little issues in the implementaiton which I chnaged (s. > attached patch) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-171) NPE in SlingScriptResolver#findScript() implementation
[ https://issues.apache.org/jira/browse/SLING-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-171: --- Assignee: Carsten Ziegeler > NPE in SlingScriptResolver#findScript() implementation > -- > > Key: SLING-171 > URL: https://issues.apache.org/jira/browse/SLING-171 > Project: Sling > Issue Type: Bug > Components: Scripting >Reporter: christian >Assignee: Carsten Ziegeler >Priority: Minor > Attachments: scriptresolver.patch > > > calling findScript() with non null arguments which point to a script a NPE is > thrown... > There are two little issues in the implementaiton which I chnaged (s. > attached patch) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-171) NPE in SlingScriptResolver#findScript() implementation
NPE in SlingScriptResolver#findScript() implementation -- Key: SLING-171 URL: https://issues.apache.org/jira/browse/SLING-171 Project: Sling Issue Type: Bug Components: Scripting Reporter: christian Priority: Minor Attachments: scriptresolver.patch calling findScript() with non null arguments which point to a script a NPE is thrown... There are two little issues in the implementaiton which I chnaged (s. attached patch) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Reference to SlingRepository
Hi all,
not sure if this is the right place to ask as this is somehow OSGi
related, but I'm currently working on a service that integrates via SCR
and tries which has a reference to the SlingRepository service.
I used the following code:
/**
* @scr.reference
*/
private SlingRepository repository;
protected void bindRepository(SlingRepository repository) {
this.repository = repository;
}
Bundling work fine (with SCR plugin) and the SCR config file looks ok to me:
http://www.osgi.org/xmlns/scr/v1.0.0";>
name="com.day.cq.workflow.osgi.WorkflowServiceWrapper">
class="com.day.cq.workflow.osgi.WorkflowServiceWrapper"/>
value="/cq-workflow/content"/>
value="CQ-INF/nodetypes/workflow.cnd"/>
value="com.day.cq.workflow.osgi.WorkflowServiceWrapper"/>
interface="org.apache.sling.jcr.api.SlingRepository" cardinality="1..1"
policy="static" bind="bindRepository" unbind="unbindRepository"/>
But when I deploy my service, I get the following exception:
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.felix.scr.impl.DependencyManager.invokeBindMethod(DependencyManager.java:886)
at
org.apache.felix.scr.impl.DependencyManager.bind(DependencyManager.java:668)
at
org.apache.felix.scr.impl.ImmediateComponentManager.createImplementationObject(ImmediateComponentManager.java:204)
at
org.apache.felix.scr.impl.ImmediateComponentManager.createComponent(ImmediateComponentManager.java:134)
at
org.apache.felix.scr.impl.AbstractComponentManager.activateInternal(AbstractComponentManager.java:412)
at
org.apache.felix.scr.impl.AbstractComponentManager.enableInternal(AbstractComponentManager.java:333)
at
org.apache.felix.scr.impl.AbstractComponentManager.access$000(AbstractComponentManager.java:45)
at
org.apache.felix.scr.impl.AbstractComponentManager$1.run(AbstractComponentManager.java:103)
at
org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:85)
17.01.2008 14:21:18 *ERROR* o.a.f.scr: Unexpected problem executing task
(java.lang.NullPointerException)
java.lang.NullPointerException
at
org.apache.felix.scr.impl.ImmediateComponentManager.disposeImplementationObject(ImmediateComponentManager.java:271)
at
org.apache.felix.scr.impl.ImmediateComponentManager.deleteComponent(ImmediateComponentManager.java:151)
at
org.apache.felix.scr.impl.AbstractComponentManager.deactivateInternal(AbstractComponentManager.java:479)
at
org.apache.felix.scr.impl.AbstractComponentManager.disableInternal(AbstractComponentManager.java:496)
at
org.apache.felix.scr.impl.AbstractComponentManager.enableInternal(AbstractComponentManager.java:341)
at
org.apache.felix.scr.impl.AbstractComponentManager.access$000(AbstractComponentManager.java:45)
at
org.apache.felix.scr.impl.AbstractComponentManager$1.run(AbstractComponentManager.java:103)
at
org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:85)
Any idea what might be the cause for that problem and how to solve it?
Best regards,
Alex
Eating exceptions in activate() methods?
The diffs of my revision 612808 changes include this, in
SimpleWebDavServlet.activate():
try {
-httpService.registerServlet(context, this, initparams, null);
-
-// set the contextPath field to signal successfull registration
-this.contextPath = context;
-
-} catch (NamespaceException ne) {
-// context collision
-
-} catch (ServletException se) {
-// servlet initialization failure
-
-}
+ // Register servlet, and set the contextPath field to
signal successful registration
+ httpService.registerServlet(context, this, initparams, null);
+ this.contextPath = context;
Was there any reason to eat these exceptions?
To me it seems better to let the framework know that something went wrong.
-Bertrand
Re: WebDAV
On Jan 16, 2008 6:02 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...I added a WebDAV bundle (jcr/webdav)... I have added (revision 612808) a webdav-resource-config.xml to the bundle (hardcoded for now), to map nt:file and related nodetypes in the "usual" way. -Bertrand
Log Level config in Sling console
Hello Sling team, during my work with Sling I noticed that the Sling console does notdisplay the values for the Log Level in the LogbackManager configuration correctly. (see attached screenshot) Has somebody else experienced similar problems? If so I will add an issue to the JIRA. Kind regards, Alex
Using X-Sling-Warning headers?
Hi,
I've added this (in revision 612806) to SlingScriptServlet.service(),
to use an X-Sling-Warning HTTP header to indicate an abnormal
non-critical condition:
final String contentType = request.getResponseContentType();
if(contentType == null) {
res.addHeader("X-Sling-Warning",
request.getClass().getSimpleName() + " does not provide a
Content-Type");
res.setContentType("text/plain");
} else {
res.setContentType(contentType);
}
In such a case (response Content-Type is not as expected), having the
X-Sling-Warning header right next to other headers makes is easy to
spot the problem, when troubleshooting one's app.
What do you think of using such X-Sling-... headers where it makes sense?
-Bertrand
Re: autoDeployBundle profile in our parent POM?
On Jan 17, 2008 11:26 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...Can we name it "autoInstallBundle" to not mixup the meaning of "deploy"... Ok, I have added this "autoInstallBundle" profile to parent/pom.xml. -Bertrand
Re: autoDeployBundle profile in our parent POM?
Hi Bertrand, Sounds usefull. Can we name it "autoInstallBundle" to not mixup the meaning of "deploy" with what maven thinks id deployment. In addition, the sling plugin supports a "deploy" goal, which deploys the bundle(s) to an OBR. Apart from that, I think, this is certainly a valid addition. I usually just rely on my command line history or hack the 30-some characters in. Regards Felix Am Donnerstag, den 17.01.2008, 09:45 +0100 schrieb Bertrand Delacretaz: > Hi, > > The patch shown below allows one to auto-install Sling bundles when > building them, using "-P autoDeployBundle" on the mvn command line. > > WDYT, should we do this? I find it useful for development, but maybe > you guys are doing this differently? > > -Bertrand > > Index: parent/pom.xml > === > --- parent/pom.xml (revision 612756) > +++ parent/pom.xml (working copy) > @@ -206,6 +206,35 @@ > > > > + > + > + > +autoDeployBundle > + > + false > + > + > + > + > + org.apache.sling > + maven-sling-plugin > + > + > + install-bundle > + > +install > + > + > + > + > + > + > + > + > + > > > Sling Development List
[jira] Commented: (SLING-170) WebDAV: Prevent NullPointerException when not supplying a workspace
[ https://issues.apache.org/jira/browse/SLING-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559881#action_12559881 ] Felix Meschberger commented on SLING-170: - Created JCR-1319 to prevent this NPE. > WebDAV: Prevent NullPointerException when not supplying a workspace > --- > > Key: SLING-170 > URL: https://issues.apache.org/jira/browse/SLING-170 > Project: Sling > Issue Type: Improvement > Components: Repository >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: 2.0.0 > > > When accessing the root of the Simple WebDAV Servlet, a NullPointerException > may be thrown by the Jackrabbit implementation (This will be the cause for > another issue of course). > For our implementation it would make sense to redirect (temporarily) to the > default workspace if the servlet root is accessed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: autoDeployBundle profile in our parent POM?
Bertrand Delacretaz wrote: On Jan 17, 2008 10:16 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: ... assume its working for you. What maven version are you using?... It does work for me with mvn 2.0.7. Maybe Maven checks if your name is "Bertrand" ;-) Ah, I always suspected this (ok, a simple sudo should do I guess...) :) I'll retry once you committed it :) Perhaps it wasn't maven's fault this time but "someone" too stupid to type the right xml... Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
Re: WebDAV
On Jan 16, 2008 6:02 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...I added a WebDAV bundle (jcr/webdav) which adds functionality to Sling > to expose a repository over WebDAV... Thanks, I'm using it in usling-webapp now and it works fine! -Bertrand
[jira] Created: (SLING-170) WebDAV: Prevent NullPointerException when not supplying a workspace
WebDAV: Prevent NullPointerException when not supplying a workspace --- Key: SLING-170 URL: https://issues.apache.org/jira/browse/SLING-170 Project: Sling Issue Type: Improvement Components: Repository Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: 2.0.0 When accessing the root of the Simple WebDAV Servlet, a NullPointerException may be thrown by the Jackrabbit implementation (This will be the cause for another issue of course). For our implementation it would make sense to redirect (temporarily) to the default workspace if the servlet root is accessed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: autoDeployBundle profile in our parent POM?
On Jan 17, 2008 10:16 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ... assume its working for you. What maven version are > you using?... It does work for me with mvn 2.0.7. Maybe Maven checks if your name is "Bertrand" ;-) -Bertrand
Re: autoDeployBundle profile in our parent POM?
Hi, I tried the same last week and it did not work on my machine (for whatever reason). I assume its working for you. What maven version are you using? Apart from that +1 Carsten Bertrand Delacretaz wrote: Hi, The patch shown below allows one to auto-install Sling bundles when building them, using "-P autoDeployBundle" on the mvn command line. WDYT, should we do this? I find it useful for development, but maybe you guys are doing this differently? -Bertrand Index: parent/pom.xml === --- parent/pom.xml (revision 612756) +++ parent/pom.xml (working copy) @@ -206,6 +206,35 @@ + + + +autoDeployBundle + + false + + + + + org.apache.sling + maven-sling-plugin + + + install-bundle + +install + + + + + + + + + Sling Development List -- Carsten Ziegeler [EMAIL PROTECTED]
autoDeployBundle profile in our parent POM?
Hi, The patch shown below allows one to auto-install Sling bundles when building them, using "-P autoDeployBundle" on the mvn command line. WDYT, should we do this? I find it useful for development, but maybe you guys are doing this differently? -Bertrand Index: parent/pom.xml === --- parent/pom.xml (revision 612756) +++ parent/pom.xml (working copy) @@ -206,6 +206,35 @@ + + + +autoDeployBundle + + false + + + + + org.apache.sling + maven-sling-plugin + + + install-bundle + +install + + + + + + + + + Sling Development List
Re: GHOP issue 2: Design two related logos for the sling project
Hi Paul, Am Donnerstag, den 17.01.2008, 09:11 +0100 schrieb Bertrand Delacretaz: > Hi Paul, > > On Jan 17, 2008 6:59 AM, Paul Walker <[EMAIL PROTECTED]> wrote: > > http://bitliquid.com/private/sling/Proposal-2-1.jpg > > http://bitliquid.com/private/sling/Proposal-2-1.svg... > > Great work! I like it. ++1. Thanks. > > > ...The variant on the bottom was made to address Bertrand Delacretaz's > > concern about the S blending into the top Border. I prefer the other > > version, but it's not all up to me… > > I do prefer this bottom variant, though it might need another > interruption in the line that goes from the S to the G, somewhere > close to the G. > > But if people prefer the top logos, no big deal - let's hear what others > think. I only just now realized why there are actually two µ logos. Probably having the line uninterrupted is slightly better ? Because it mimicks the word "Sling" a bit by creating the illusion of a sling. If we would interrupt at the g, the µ might seem to hang out in the air ? BTW: The logo also looks good when printed B&W. Regards Felix > > -Bertrand
Re: GHOP issue 2: Design two related logos for the sling project
Hi Paul, On Jan 17, 2008 6:59 AM, Paul Walker <[EMAIL PROTECTED]> wrote: > http://bitliquid.com/private/sling/Proposal-2-1.jpg > http://bitliquid.com/private/sling/Proposal-2-1.svg... Great work! I like it. > ...The variant on the bottom was made to address Bertrand Delacretaz's > concern about the S blending into the top Border. I prefer the other > version, but it's not all up to me… I do prefer this bottom variant, though it might need another interruption in the line that goes from the S to the G, somewhere close to the G. But if people prefer the top logos, no big deal - let's hear what others think. -Bertrand
