Recent changes to bugs

Thread visualisation

2007-12-16T12:40:11Z

I am dealing with a thread issue in OpenCOMJ v1.3.3

In the visualition package, the VisualGraph.GraphPanel implements the Runnable interface.

When a GraphPanel object is created, a thread is launched.

This thread is never stopped.

When the visualisation package is used for several debug visualisation, this leads to a big overhead.

I propose to stop the thread when it positioningCounter >= MAX_POSITION_TIME, an relaunch it when necessary (for instance, new component created or old-one removed).

If doing that, when mouse is "grabbing" a component, a repaint action should be necessary.

I have not verified that this problem also occurs in laster versions.

--
Thomas Pareaud

UDPTransport.Close()

2007-11-29T14:36:51Z

The close method of the UDPTransport component, closes the socket but does not remove listeners(EvHandlers).

Additionally, since individual sockets can be shared by different components closing a socket affects other components when various listeners are in place.

Hence, It might be necessary to change the implementation of the close() mehtod, so when this is called individual instances remove only their listeners (EvHandlers). The socket will be closed automatically when no more listeners for this socket extist.

UDPTransport, NotifyMsgHandlers

2007-10-22T18:54:24Z

The method NotifyMsgHandlers forwards notifications to all available MsgHandlers. This is incorrect since notifications should only be sent to interested MsgHandlers. A Possible solution to this could be:

protected void NotifyMsgHandlers(String id, byte[] data, Object from){
for(int i=0; i<EvHandlers.size();i++){
MsgListener a = EvHandlers.get(i);
try{
if(a.ElementIdenetifier.equalsIgnoreCase(id))
a.ElementListener.Deliver(a.ElementIdenetifier,
data,data.length,from);
}
catch(Exception e){
}
}
}

Block and non-blocking

2007-05-31T15:28:21Z

The IForward implementations of EventReceive() and Receive() are incomplete for certain components i.e only the one in use is implemented.

File Locations

2007-03-04T22:07:41Z

File reads from locations not linked to Gridkit environment variable; hence, won't work in certain installations

Receptacle Attributes

2007-01-11T15:54:51Z

Cannot attach meta data attributes to multireceptacles with dynamic context - missing from metainterface.java should have the following:

if((type.equalsIgnoreCase("OpenCOM.OCM_SingleReceptacle"))||(type.equalsIgnoreCase("OpenCOM.OCM_MultiReceptacle"))||(type.equalsIgnoreCase("OpenCOM.OCM_MultiReceptacleDynamicContext"))
||(type.equalsIgnoreCase("OpenCOM.OCM_MultiReceptacleContext"))||(type.equalsIgnoreCase("OpenCOM.OCM_MultiReceptacleParallel"))){

Will be fixed in next release

GridKit - SOAPToMulticast::ExtractEndpoint

2006-12-03T11:50:21Z

Hello,

to my mind, the method SOAPToMulticast::ExtractEndpoint may not work in at least one case:

if the substring before "://" is less than 3 of length, then the third index will return a bad value...

I would change the code of this method to:

private String ExtractEndpoint(String URL){
// Extract the IP & port from the passed URL String to_URL = URL;
int port = -1;
int index=0;
if(to_URL.contains("://")){
index = to_URL.indexOf("://")+3;
}
to_URL = to_URL.substring(index);
// never used
//int secondIndex = to_URL.indexOf(":");
int thirdIndex = to_URL.indexOf("/");
String a_URL = to_URL.substring(0, thirdIndex);
return a_URL;
}

A more convenient way to do so should be to use a StringTokenizer objet. But it may be as using a tank to kill a fly :) (French Joke)

Thomas Pareaud
Phd studient at Laas-Cnrs
Toulouse/France

Resource Overload during visualisation

2006-11-10T14:23:23Z

On call of visualisation() significant resource
overload encountered.

OCM_MultiReceptacleContext

2006-11-10T14:22:12Z

The OCM_MultiReceptacleContext is unusable after first
round of disconnections

Delete Component

2006-11-10T14:12:45Z

The delete component operation throws null pointer
exceptions in some situations