OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

Hi,

we implemented a SpringContextDispatcher, which inherits from org.eclnt.workplace.WorkpageDispatcher and overrides the readObject-Method so that all Objects being read run through a Spring BeanPostProcessing.

Our class has a constructor and as soon as that constructor contains the following line:
Code:

autoWireProcessor.setBeanFactory(applicationContext.getAutowireCapableBeanFactory());

... the UI Development tools do not show the Beans we have entered in the dispatcherinfo.xml. These Beans are in a different Package than Dispatcher and SpringContextDispatcher.

There exists a workaround to cope with this: Adding references to our beans in the project setup/configuration as additionalmanagedbean. If you do that, our Beans are shown in the Bean Browser, but instead of within, next to the Bean Browser (see workaround.jpg, the prefix "d." actually is written in the name attribute of the additionalmanagedbean tag).

Any hints to explain this behaviour are welcome.

Thanks,

Björn

Hi,

yes, they are displayed below the dispatcher... but the expression to drag & drop from still is right. So it's just a display issue within the bean browser.

We'll change this and render them below the "d"... but treat this as "B-issue". So somewhere in 1-2 months.

OK with you?

Regards, Björn

The Problem was that the Spring Core Beans Jar, which contains the classes we use in our SpringContextDispatcher-Class was not visible to the Development Tools.

Using the classpathextension-Attribut in the project configuration to refence the JAR needed fixed the problem.

Thanks Björn Müller for your help on this issue.

Regards,

Björn