Menu
▾
▴
#2 v0.1.5.p1 - Service1 calls Service2 insithe the ServENT
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 the ZIP file form here and UNZIP in the
servent directory. This action will override old libraries
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.
ZIP file