[seam-issues] [JBoss JIRA] Commented: (SEAMWICKET-18) Make Wicket Conversational control optional
[
https://issues.jboss.org/browse/SEAMWICKET-18?page=com.atlassian.jira.plu...
]
Jozef Hartinger commented on SEAMWICKET-18:
-------------------------------------------
Or perhaps use Seam Conversation (https://github.com/seam/conversation) instead of
directly depending on Weld SPI.
Make Wicket Conversational control optional
-------------------------------------------
Key: SEAMWICKET-18
URL: https://issues.jboss.org/browse/SEAMWICKET-18
Project: Seam for Apache Wicket
Issue Type: Feature Request
Affects Versions: 3.0.0.Beta1
Reporter: Clint Popetz
Assignee: Clint Popetz
Fix For: 3.0.0.Final
From Pete's suggestions:
- define an api which allows wicket to control conversations
- use service providers (META-INF/services) to discover impls
- provide a built in impl which can use Weld, if it (WeldManager) is on the classpath
- degrade gracefully if no impl is available
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira