Enterprise Client Community

Hi again!

Here comes my doubt about the dispatcher info.

At the moment we need to specify the package names specifically in the dispatcherinfo.xml in order for the dispatcher to take them into account.
For example now in my project structure I have something like:

managedbeans.macros

managedbeans.users

managedbeans.reports

and I declare the full package path for each of them in the dispatcherinfo.xml

Would it be a problem that during the dispatcherinfo.xml analysis the subpackages from the "managedbeans" package were also included automatically? (if it is a very dramatic change also the activation of this functionallity via flag could be interesting).

Thanks!

Best regards

David

Hi,

yes this is possible, and yes: we will add an own activation flag in the XML definition in order to keep compatibility.

Am not 100% sure, but should be in next update.

Regards, Björn

Hi,

I have to step back from what I said... there is no API that provides a list of all packages. The Package.getPackages() only delivers these ones which are already loaded...

Reagrds, Björn

There is only a dirty way, to implement this (for many cases):
Ask the classloader for a resource path (e.g.):
- this.getClass().getClassLoader().getResource("managebean/dispatcher")
(replace . by /)

You get the URL or the resource. This is a zip or a directory.
Here you can ask for: ".list", to get all packages.
This list can be filtered by the dispatcher-info.xml information's for sub packages.

Enougth about dirty implementations. Maybe you just want to add the subpackages within dispatcher-info.xml ;-)

Kind regards
Roland

Precisely I was doing it as you, Roland, mentioned and the result of the filtering was returned in the initRegisteredPackages(...) that Björn introduced.
In development environment it is working fine, nevertheless in the production system we had problems to access the files in that way.
So we had to step back to the manual listing again, what a pity