Project swallow
|
|
Description
bug1
There was a problem when a service (S1) deployed within the Servent calls another service (S2) deployed in the same or other Servent.
In case S2 uses complex types as parameters and event if the library is already included in the S1 service library directory, the parameter class is not found.
This bug was not appreciable if those parameters where an interface with different implementations. It was not appreciable either if the S2 library was not included in the S1 library directory. In these cases the needed library is downloaded at runtime form S2 (codebase must be specified in S2).
bug2
It depend of your Servent configuration, when you use ServiceContext.getService (...) you can get an exception related with the connection time out. This is because the port to the local CSS servent can be wrong
Solution
To solve this problem quickly it has been necessary to modify the ProxyFramework libraries as well as some Servent classes. If you are running the Servent you can download libraries form here. Remember to copy all them in the correct directory and remove old JAR files
If you are using and old development that uses old proxyframework libraries, you do not need to change those libraries, that will work fine with new development.
If you are not using the previous scenario where S1 calls S2, you can wait untill the next Servent version will be available.