[
https://issues.apache.org/jira/browse/TAP5-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089170#comment-14089170
]
Thiago H. de Paula Figueiredo commented on TAP5-2369:
-----------------------------------------------------
Hello, Alexey!
Are you sure that, in the environments you listed, components and mixins are
resolved, but pages aren't? This is very, very weird, as the scanning for
pages, components and mixins is exactly the same for all of them. In addition,
you can package pages in component libraries, which are delivered as a JAR, and
they work. In addition, the scanning works the same in exploded or non-exploded
WARs, because Tapestry doesn't scan files in the filesystem directly. Instead,
it scans the classpath using the classloader, so it doesn't matter where the
.class file is as long as it's in the classpath.
> war/ear archive scan for t5 pages
> ---------------------------------
>
> Key: TAP5-2369
> URL: https://issues.apache.org/jira/browse/TAP5-2369
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.3.7
> Reporter: Alexey Chalov
> Priority: Minor
>
> Some application servers (like websphere liberty profile) does not create
> exploded directories for java archives, that leads to pages scan failure.
> Components and mixins are resolved normally. So, no pages except for default
> tapestry ones are available.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
