[
https://issues.apache.org/jira/browse/TAP5-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias updated TAP5-1837:
---
Attachment: TAP-1837-5.4.1.patch
As this issue persists in Tapestry 5.4.0 I updated the patch with Lance's
sug
[
https://issues.apache.org/jira/browse/TAP5-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias updated TAP5-1837:
---
Attachment: TAP5-1837-2.patch
The problem was just that I couldn't extract the bean definition from
Applicati
[
https://issues.apache.org/jira/browse/TAP5-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias updated TAP5-1837:
---
Attachment: TAP5-1837.patch
Includes check for known type of Spring beans in SpringModuleDef
[
https://issues.apache.org/jira/browse/TAP5-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias updated TAP5-1837:
---
Comment: was deleted
(was: Includes check for known type of Spring beans in SpringModuleDef)
> NPE on reg
[
https://issues.apache.org/jira/browse/TAP5-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam updated TAP5-1837:
---
Attachment: t5sandbox.tar.gz
Demo project with problematic bean in applicationContext.xml
> NPE on re