[
https://issues.apache.org/jira/browse/XAP-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Turyn, Michael updated XAP-320:
-------------------------------
Description:
Cyclic dependency graph:
xap.util.ResourceDictionary [depends on] xap.log.Logger [depends on]
xap.util.XapException [depends on] xap.util.ResourceDictionary ....
---error shows up when doing the dojo load of XapException: ResourceDictionary
is loaded by it, and itstop-level xap.log.Logger.getLogger() is not understood.
The priority is "Minor" because this is invisible to the user; it however stops
the debugger on every load if you're in "stop on exceptions" mode, annoying.
We can work around this by initialising ResourceDictionary's logger when the
first instance of it is created, but this seems inadequate---I'd rather feel
like we can depend on dojo loading to work or let us know when it can't.
was:
Cyclic dependency graph:
xap.util.ResourceDictionary [depends on] xap.log.Logger [depends on]
xap.util.XapException [depends on] xap.util.ResourceDictionary ....
---error shows up when doing the dojo load of XapException: ResourceDictionary
is loaded by it, and itstop-level xap.log.Logger.getLogger() is not understood.
The priority is "Minor" because this is invisible to the user; it however stops
the debugger on every load if you're in "stop on exceptions" mode, annoying.
> xap.util.ResourceDictionary: loading error.
> --------------------------------------------
>
> Key: XAP-320
> URL: https://issues.apache.org/jira/browse/XAP-320
> Project: XAP
> Issue Type: Bug
> Reporter: Turyn, Michael
> Priority: Minor
>
> Cyclic dependency graph:
> xap.util.ResourceDictionary [depends on] xap.log.Logger [depends on]
> xap.util.XapException [depends on] xap.util.ResourceDictionary ....
> ---error shows up when doing the dojo load of XapException:
> ResourceDictionary is loaded by it, and itstop-level
> xap.log.Logger.getLogger() is not understood.
> The priority is "Minor" because this is invisible to the user; it however
> stops the debugger on every load if you're in "stop on exceptions" mode,
> annoying.
> We can work around this by initialising ResourceDictionary's logger when the
> first instance of it is created, but this seems inadequate---I'd rather feel
> like we can depend on dojo loading to work or let us know when it can't.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
