![]() |
|
|
|
|
Issue Type:
|
![Feature Request]() Feature Request
|
|
Affects Versions:
|
1.1.9.Final |
|
Assignee:
|
Jozef Hartinger
|
|
Created:
|
05/Feb/13 12:05 PM
|
|
Description:
|
I'm currently working at migrating a fairly big project (100+ services split in 16 different projects). Until now an home grown solution was used to manually "inject" the requested service like "ServiceHelper.getService(MyService.class)".
The problem with this approach is that no circular dependency is ever checked (which is bad).
Anyways, when circular dependencies are found and DeploymentException is thrown by Weld, it would be very nice to prettify the exception and print the dependency tree to pin point more easily the circular dependency problem (which in big project can be fairly difficult to point out).
There's probably some string utilities in the Hibernate project that could help to perform this task ? I'm thinking about the entity debugging that is showing the entity mapping as a tree.
Hope this is possible,
Big thanks !
|
|
Project:
|
Weld
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Mathieu Lachance
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
