We have an application that uses the Media Manager Bean from Julian Salerno. This has been in operation for some months and has had a number of enhancements over this period.
With release of Servoy 2.2.3 the bean has broken, I am in concerned that this is a regression of the earlier class path issue we experienced in pre 2.2.1 versions of Servoy. Firstly has anyone else experienced this problem on other beans etc and more importantly can it be fixed asap.
We have reverted to 2.2.1 and the problem has resolved its self, this is obviously not an ideal solution.
We were able to release our software against R2.2.1 following a number of classpath and JWS fixes in the Servoy engine.
Up to this point in time, those using my plugins have remained on 2.2.1.
Gordon has ventured onwards
2.2.3 (and maybe 2.2.2 ?) appear to suffer from a similar/same set of Developer startup problems.
I am not sure whether Gordon is observing this is Server or Developer, but I would ask the Servoy guys to take look at any code changes/omissions that may have re-introduced these bugs.
2.2.3 (and maybe 2.2.2 ?) appear to suffer from a similar/same set of Developer startup problems.
I am not sure whether Gordon is observing this is Server or Developer, but I would ask the Servoy guys to take look at any code changes/omissions that may have re-introduced these bugs.
We had no choice other than to use 2.2.3 its a fresh install on a clients machine.
The install is on developer and the beans are not showing. I have installed Julians beans several times and am confident that they are correctly located in the required folders.
The aim is to run this as a server not developer
Forgive my lack of knowledge, but if it works in 2.2.1 it seem logical that it should be ok in upgrades, unless bits of the code are regressing. It is very disappointing that if each time there is a minor enhancement to Servoy several of its key selling points ie beans stop working !!!