228 Posts

February 26th, 2013 13:00

Hello Robert,

I believe the problem that results in the behaviour you described has been identified as a defect in the current vWorkspace Java Connector. We have an open defect with the description 'Java connector not passing correct information on device/connector' and the ID 213704. This item is being reviewed by the development team and is currently scheduled to be resolved in the next vWorkspace Java Connector release.

Best Regards

David

No Events found!

Top