headers
Carsten Ziegeler (Created) (JIRA | 10 Feb 13:25
Picon
Favicon

[jira] [Created] (SLING-2417) Start level should be changed for upgrades

Start level should be changed for upgrades
------------------------------------------

                 Key: SLING-2417
                 URL: https://issues.apache.org/jira/browse/SLING-2417
             Project: Sling
          Issue Type: New Feature
          Components: Installer
    Affects Versions: Installer Core 3.3.4
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Installer Core 3.3.6

The start level of a bunde is currently only set if a bundle is newly installed, but not during an update. We
should set the start level in these cases as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |
headers
Carsten Ziegeler (Created) (JIRA | 10 Feb 10:39
Picon
Favicon

[jira] [Created] (SLING-2416) Launcher jar should not be closed when framework restarts

Launcher jar should not be closed when framework restarts
---------------------------------------------------------

                 Key: SLING-2416
                 URL: https://issues.apache.org/jira/browse/SLING-2416
             Project: Sling
          Issue Type: Bug
          Components: Launchpad
    Affects Versions: Launchpad Base 2.3.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Launchpad Base 2.4.0

When the framework is restarted during bootstrapping, e.g. if a system fragment is uninstalled, the
launchar jar should not be closed. Otherwise this might result in "zip already closed" exceptions on some jdks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |
headers
Chaitanya Atreya (Created) (JIRA | 10 Feb 02:07
Picon
Favicon

[jira] [Created] (SLING-2415) Ability to delete child nodes, without deleting the parent node in SlingPostServlet

Ability to delete child nodes, without deleting the parent node in SlingPostServlet
-----------------------------------------------------------------------------------

                 Key: SLING-2415
                 URL: https://issues.apache.org/jira/browse/SLING-2415
             Project: Sling
          Issue Type: New Feature
          Components: Servlets
            Reporter: Chaitanya Atreya

Provide a way to delete all the child nodes of a given node in the SlingPostServlet, without deleting the
parent node itself.

There are many situations where one might want to delete only the child nodes, while keeping the parent node
intact. 

One way to do this now is to use the :applyTo request parameter for each child node. However, this requires
first fetching all the child nodes, which can be avoided with this feature.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 2 comments |
headers
Carsten Ziegeler (Created) (JIRA | 9 Feb 21:38
Picon
Favicon

[jira] [Created] (SLING-2414) Install bundles in the order of their start level

Install bundles in the order of their start level
-------------------------------------------------

                 Key: SLING-2414
                 URL: https://issues.apache.org/jira/browse/SLING-2414
             Project: Sling
          Issue Type: Improvement
          Components: Installer
    Affects Versions: Installer Core 3.3.4
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Installer Core 3.3.6

The bundle install tasks are currently sorted by URL - which doesn't provide any advantage. We should
rather sort them by sort level, this allows bundles with lower start level to be resolved before ones with a
higher start level

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |
headers
Justin Edelson (Created) (JIRA | 9 Feb 17:40
Picon
Favicon

[jira] [Created] (SLING-2413) RequestProcessorMBeanImpl needs internal refactoring to be extended

RequestProcessorMBeanImpl needs internal refactoring to be extended
-------------------------------------------------------------------

                 Key: SLING-2413
                 URL: https://issues.apache.org/jira/browse/SLING-2413
             Project: Sling
          Issue Type: Improvement
            Reporter: Justin Edelson
            Assignee: Justin Edelson

the instance variable names are too generic (min/max/sum) and the add data method is too specific.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 2 comments |
headers
Justin Edelson (Created) (JIRA | 9 Feb 17:37
Picon
Favicon

[jira] [Created] (SLING-2412) add peak call and recursion depth statistics to RequestProcessor mbean

add peak call and recursion depth statistics to RequestProcessor mbean
----------------------------------------------------------------------

                 Key: SLING-2412
                 URL: https://issues.apache.org/jira/browse/SLING-2412
             Project: Sling
          Issue Type: Improvement
          Components: Engine
            Reporter: Justin Edelson

The SlingMainServlet has include and recursion depth limit setting, but there's no way to determine what
the peak level actually is. These should be available via JMX.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 0 comments |
headers
Justin Edelson (Created) (JIRA | 9 Feb 16:12
Picon
Favicon

[jira] [Created] (SLING-2411) ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently

ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently
-------------------------------------------------------------------------------

                 Key: SLING-2411
                 URL: https://issues.apache.org/jira/browse/SLING-2411
             Project: Sling
          Issue Type: Improvement
            Reporter: Justin Edelson

The ResourceDecorator currently has two methods:
decorate(Resource)
decorate(Resource, HttpServletRequest)

The JcrResourceResolver uses the latter method when resolve(HttpServletRequest,String) is invoked.
In all other cases, the former method is used. This behavior is correct.

However, the JcrResourceResolver (and any future ResourceResolver implementation for that matter)
really doesn't have any control over how it is invoked. For example, at present <sling:include> and
<sling:forward> call resolve(String), not resolve(HttpServletRequest,String) (see
http://s.apache.org/lL5). But even if we did a code audit within Sling and fixed all the cases like this,
we don't have any control over downstream applications which may or may not invoke the two-argument
resolve() method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 7 comments |
headers
Carsten Ziegeler (Created) (JIRA | 9 Feb 16:03
Picon
Favicon

[jira] [Created] (SLING-2410) Problems with pathes ending with .jsp in WebSphere

Problems with pathes ending with .jsp in WebSphere
--------------------------------------------------

                 Key: SLING-2410
                 URL: https://issues.apache.org/jira/browse/SLING-2410
             Project: Sling
          Issue Type: Bug
          Components: Launchpad
    Affects Versions: Launchpad Base 2.3.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Launchpad Base 2.4.0

Found a potential problem with pathes ending with *.jsp and WebSphere. The Sling web.xml contains the
following mapping:

    <!-- Overwrite Mappings which may be present in default web.xml files -->
    <servlet-mapping>
        <servlet-name>sling</servlet-name>
        <url-pattern>*.jsp</url-pattern>
    </servlet-mapping>

With the idea to not have any default web.xml grabbing .jsp requests.

The problem is that servlet path and path info values for requests matching the
*.jsp pattern are defined differently than if the mapping would be /.

Thus a request /path/index.jsp mapping *.jsp gets:
    servlet path = /path/index.jsp
    path info = null
(Continue reading)

Permalink | Reply | 2 comments |
headers
Carsten Ziegeler (Created) (JIRA | 9 Feb 11:22
Picon
Favicon

[jira] [Created] (SLING-2409) If configuration is removed by config admin, state of provided artifact should either be uninstalled or ignored

If configuration is removed by config admin, state of provided artifact should either be uninstalled or ignored
---------------------------------------------------------------------------------------------------------------

                 Key: SLING-2409
                 URL: https://issues.apache.org/jira/browse/SLING-2409
             Project: Sling
          Issue Type: Bug
          Components: Installer
    Affects Versions: Installer Core 3.3.4
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Installer Core 3.3.6

If a configuration is removed through the config admin, the write back handling kicks in. If there is a
handler which provided this resource and it can be removed, the state is correctly set to uninstalled.
However, if the configuration has been provided by a provider and can't or shouldn't be removed, the state
is still INSTALLED. It should rather be IGNORED

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 2 comments |
headers
Christan Keller (Created) (JIRA | 9 Feb 10:46
Picon
Favicon

[jira] [Created] (SLING-2408) JcrNodeResourceIterator logs on error level for deleted Nodes

JcrNodeResourceIterator logs on error level for deleted Nodes
-------------------------------------------------------------

                 Key: SLING-2408
                 URL: https://issues.apache.org/jira/browse/SLING-2408
             Project: Sling
          Issue Type: Improvement
    Affects Versions: JCR Resource 2.0.10
            Reporter: Christan Keller
            Priority: Minor

If you get a JcrNodeResourceIterator for examply via a ResourceResolver.resolve().
And you iterate over its entries. 
If it hapens that one of this entry is removed concurrently, the Ieterator gets an ItemNotFoundException
and logs an Error.
The behavior is correct. Iterator goes on. The existant amount of Nodes is returned.

So I would set the log-level to warn, as this case is not an error.

Condtion:
---------------
Stirng path = /some/path
session.getNode(path).remove()

session.save();
resolverOtherSession.resolve(path)

Exception
---------------
2012 09:35:22.719 *ERROR* [pool-9-thread-3]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Carsten Ziegeler (Created) (JIRA | 9 Feb 09:24
Picon
Favicon

[jira] [Created] (SLING-2407) Configuration write back handles delete too aggressive

Configuration write back handles delete too aggressive
------------------------------------------------------

                 Key: SLING-2407
                 URL: https://issues.apache.org/jira/browse/SLING-2407
             Project: Sling
          Issue Type: Bug
          Components: Installer
    Affects Versions: JCR Installer 3.1.2
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: JCR Installer 3.1.4

When a configuration is removed from config admin, the removal is handled too aggressiv. The
handleRemoval method does not check:
a) if the provided path is a path provisioned by the jcr installer
b) if the configuration is in /libs, then it should not be removed at all and stay as default

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |

Gmane