[
https://issues.apache.org/jira/browse/TAP5-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100741#comment-14100741
]
Alexey Chalov commented on TAP5-2369:
-------------------------------------
You see, WLP and WAS are two different products, whatever IBM specialists might
say, WAS and WLP are not compatible. I just noticed, if i unpack war/ear into
WLP dropins directory - page scan performs correctly and everything is ok, the
above problem appears only in case of packaged archives. This is definitely
classpath/classloading issue. Moreover, I tried to turn on JRebel, that scans
classes and forces them to be loaded and this leads to normal t5 startup(!).
Not a weird situation,as I understand, but nevertheless it happens.
Ok, I'll try to use fix, that you suggested, but it seems it will not help...
I'll report on test results later. Thank you for your time.
> 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)
