[jira] Commented: (SLING-567) sling.include inclides fragments in the wrong order

[ https://issues.apache.org/jira/browse/SLING-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12623583#action_12623583 ] Felix Meschberger commented on SLING-567: - actually, what is returned is perfectly

[jira] Created: (SLING-619) Add a java servlet scripting engine

Add a java servlet scripting engine --- Key: SLING-619 URL: https://issues.apache.org/jira/browse/SLING-619 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee:

[jira] Created: (SLING-620) Use value map to render resources

Use value map to render resources - Key: SLING-620 URL: https://issues.apache.org/jira/browse/SLING-620 Project: Sling Issue Type: Improvement Components: Servlets Get Affects Versions: Servlets

[jira] Created: (SLING-621) DefaultSlingScript should not flush the output after the script ends

DefaultSlingScript should not flush the output after the script ends Key: SLING-621 URL: https://issues.apache.org/jira/browse/SLING-621 Project: Sling Issue Type: Bug

[jira] Resolved: (SLING-621) DefaultSlingScript should not flush the output after the script ends

[ https://issues.apache.org/jira/browse/SLING-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-621. - Resolution: Fixed Committed fix in Rev. 687015 and deployed snapshot build version

Build Failure with Revision 687019

Dear team, I've tried to build sling from scratch following the description Getting and Building Sling. Unfortunately that fails with the following error ... [INFO] [INFO] Building Sling - Scripting - JSP Support

RE: Build Failure with Revision 687019

This occurs when building with JDK 6, because the ScriptException class is slightly different in JDK 6 vs BSF. I edited BetterScriptException to pass the message as the super argument, and initialize the cause exception using initCause. That then works on either JDK. Rory Rory Douglas Senior

Re: Build Failure with Revision 687019

Rory Douglas wrote: This occurs when building with JDK 6, because the ScriptException class is slightly different in JDK 6 vs BSF. I edited BetterScriptException to pass the message as the super argument, and initialize the cause exception using initCause. That then works on either JDK.

Re: Build Failure with Revision 687019

Here it is (should have done this earlier ;-) Regards, Rory Carsten Ziegeler wrote: Rory Douglas wrote: This occurs when building with JDK 6, because the ScriptException class is slightly different in JDK 6 vs BSF. I edited BetterScriptException to pass the message as the super argument,

Re: Build Failure with Revision 687019

Rory Douglas wrote: Here it is (should have done this earlier ;-) :) Don't worry :) Many thanks for the patch, Rory - it should now work as expected. Thanks Carsten -- Carsten Ziegeler [EMAIL PROTECTED]

Umlaut problem

Hi all, This problem is driving me nuts... I don't get UTF-8 Umlaute correctly into the JCR. I double-checked everything to ensure the page is *really* UTF-8, and lately I discovered the thing with the hidden FormEncoding parameter. But instead of getting a clean 'ü', I still get something like

Re: Umlaut problem

hi, the FormEncoding parameter was renamed to _charset_ (see [0]): so: input name=_charset_ type=hidden value=UTF-8/ should do the trick. regards, toby [0] https://issues.apache.org/jira/browse/SLING-298 On 8/19/08, Juerg Meier [EMAIL PROTECTED] wrote: Hi all, This problem is driving me