[
https://issues.apache.org/jira/browse/SLING-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roy Teeuwen updated SLING-6223:
-------------------------------
Component/s: Scripting
> Impossible to create HTL resource type that starts with a number inside the
> foldername
> --------------------------------------------------------------------------------------
>
> Key: SLING-6223
> URL: https://issues.apache.org/jira/browse/SLING-6223
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Roy Teeuwen
> Priority: Critical
>
> We have versioned resource types in folders concerning the release date. For
> example /apps/myapp/1702/components/mycomponent
> Now when switching from jsp to HTL, we get following exception:
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException:
> Compilation errors in
> apps/myapp/1702/components/mycomponent/SightlyJava_main.java:
> Line 19, column 971 : The declared package "apps.myapp" does not match the
> expected package "apps.myapp.1702.components.mycomponent"
> Line 19, column 981 : Syntax error on token ".1702", delete this token
> at
> org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:143)
> I guess this is because it translates the folders to package names, and 1702
> is not a valid package identifier, but why isn’t it throwing this exception
> then in all the already existing jsp components?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
