Be the first to post a text review of Secure Mobile Agents (SeMoA). Rate and review a project by clicking thumbs up or thumbs down in the right column.

• semoa 070901 file released: semoa-launcher_traywin_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-launcher_traysolx86_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-web_src_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-webservice_src_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-webservice_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-web_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-tools_src_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-tools_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-starter_src_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago

• semoa 070901 file released: semoa-starter_070901.zip

  SeMoA-Distribution (Version 01.09.2007) * Added alias and info for ServletLauncher and HttpResourceStoreImpl. * ClassResource has been excluded from all classes in package 'de.fhg.igd.logging', again, because this package is exported to a detached JAR file. We do not want to have all the overhead classes needed by ClassResource in this case. * Added command line option '-info' to the HTTP resource store. * Replaced inline WhatIs keys with defined constants * The main() method of the LSProxy checks, if another LSProxy server is currently running on the same host. This prevents errors in case the user runs more than one SeMoA server with enabled ATLAS_PROXY (e.g. if STANDALONE is enabled). * Method certificates() has been adjusted to fully comply JavaDoc description. * The Web service engine allows to deploy, undeploy, list, and reset Web service handlers, now. * The Multicast daemon (Vicinity) allows to set the TimetToLive (TTL) of the generated multicast packets, now. This enables visibility of SeMoA server accross the boundaries of the local subnet. * Bugfix: Up to know, only certificate chains with a maximum length of 2 certificates have been verified, correctly. * The AXIS v1.3 framework which is part of SeMoA's Web service engine has been exchanged by the current framework version AXIS v1.4. * Bugfix: Handler can be deployed in the service context according to service names which contain slashes ('/'), now. * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Different AXIS base directories for server configuration are allowed for different plattforms, now. The client configuration is still shared between all local platforms (should be fixed in future). * Added two aliases for providers used by Apache WSS4J * Added missing keyUsage bits as constants * Transfered installation, testing, and example guidelines from the website into Latex files * The Webservice framework support separate 'client-config.wsdd' (and 'server-config.wsdd') files per platform, now. If the optional command line option '-axisclientconf' is omitted, then the 'client-config.wsdd' file is stored in the directory given by the mandatory command line option '-axisbase'. Furthermore, the output of WebserviceServiceImpl.toString has been adjusted. * Using the defined constant to lookup a distinguished name via Ship request. * Added the extended launchAgent method to the public interface, which allows the user to chose between synchronous and asynchronous agent launching. * The CBR starter class has been modified as follows: 1) Using the launchAgent method synchronously instead of asynchronously because of problems with Thread handling 2) Using a direct SHIP request to request the distinguished name of the destination server in 'secure' mode of the FetchAgent, if the destination server is not visible via Vicinity. * Minor extension of class CertificateStore: added method equals() and hashCode(). * The HttpJob has been extended to return the current SSL Session via the request attribute 'javax.net.ssl.SSLSession', if the current connection is a HTTPS connection. * Bugfix: Name.toString() is printed in the right order (as given in the constructor), now * Some major modifications of the Webservice framework: - The WebserviceManager checks, if the given object has already been handled by this class, thus the object is a generated Webservice client stub. In this case, the object is ignored by the methods onPublication() and onRectraction(). Thus, it's possible to publish an object, which has been generated and returned by the onLookup() method, within the same path in the Environment where the user has search for before. This procedure will not raise an exception anymore, if this specific path is controlled by the WebserviceManager which results in a call of the onPublication() method in the described scenario. - The WebserviceManager does explicitly test if a Web service found through UDDI is still online by probing the WSDL URL. If not, the next suitable Web service is chosen. - The previous version of ClientProxyFactory did not support Web services throwing exceptions from other packages than the one of the Web service itself. This has been fixed. The Web service stub locator class is searched in all generated source paths, now. Furhtermore, another method is used to receive the Web service's binding stub, because the previous implementation did not work properly for some specific WSDL examples automatically generated on server side - i.e. the port of AthenticationManager is 'auth-manager' whereas the proper method to receive the binding stub is 'getAuthenticationManager()' (not 'getauth-manager()' as presumed before). - toString() methods have been added to UddiProxy and UddiServiceImpl. * Updated FlexProvider to v1.4 * Since the SeMoA Platform shall be published via SourceForge.net, the license and file headers have been changed. * Icons have been added for the Website (favicon.ico) and to choose as program symbol for shortcuts. * Some more adjustments for migration to SourceForge.

  posted 836 days ago