Hi Carl,
On Wed, Mar 2, 2011 at 10:37 PM, Carl Hall c...@hallwaytech.com wrote:
Looks like I have bought some cycles to work on this. I am familiarizing
myself with the code now. I'll plan to first replace the homegrown impl with
logback. Any suggestions on direction or features are most
Hi,
Am Donnerstag, den 03.03.2011, 08:29 + schrieb Sarwar Bhuiyan:
Hi felix, how does it work in the sling jsps then? Grabbing the object
from the session and casting it works in the JSP but not in a sling
servlet. (This is with us using the embedded dependencies bundle with
the same jar
On 03.03.11 07:01, Unmesh Joshi unmeshjo...@gmail.com wrote:
1. Why would the classes be resolved in JSP components when exported
from a OSGI bundle which includes all the shared jars.
Here they are not getting loaded by shared ear class loader.
If these are JSPs running inside Sling, I would
On Thu, Mar 3, 2011 at 10:27 AM, Alexander Klimetschek
aklim...@adobe.com wrote:
On 03.03.11 07:01, Unmesh Joshi unmeshjo...@gmail.com wrote:
If these are JSPs running inside Sling, I would guess: it might be that
the classloader used by the JSP scripting engine actually directly uses
the
On 03.03.11 14:44, Unmesh Joshi unmeshjo...@gmail.com wrote:
When JSP running inside sling is trying to get session objects, it is
ALWAYS getting deserialized by weblogic. See the following stack
trace. This does not happen when Sling servlet is trying to get
session data. Is something special
The actual deserialization is going on and it happens only when
session.getAttribute is called from JSP in sling. If its called from
SlingServlet, which is in OSGI bundle, this doesn't happen.
We do not need serialization at all, but not sure why this kind of
thing is happening only when called
Hey,
I have a node:
/content/page
whose sling:resourceType = /apps/foo/bar
So, GET /content/page.html will be handled by /apps/foo/bar/html.jsp
I cannot modify sling:resourceType of /content/page.
However, I would like GET /content/page.edit.html to be handled by
Hi Sam
I think the RequestDispatcherOptions[0] might be what you're looking
for. It allows you to control certain aspects of re-dispatching
(forwarding and including) a request, including forcing a
different resource type. You could use this API in a servlet
registered for the edit selector, as
Hi,
Am Donnerstag, den 03.03.2011, 17:07 + schrieb Carl Hall:
There seem to be 3 things to accomplish here:
* Change logging order to have slf4j write into the LogService then have a
LogListener that will handle writing to logback, etc.
I would not do that. Rather keep the structure as
Hi,
One last word ;-)
Lets move this discussion to dev@ ;-)
Regards
Felix
Am Donnerstag, den 03.03.2011, 17:07 + schrieb Carl Hall:
There seem to be 3 things to accomplish here:
* Change logging order to have slf4j write into the LogService then have a
LogListener that will handle
10 matches
Mail list logo
