Fork me on GitHub

Rat (Release Audit Tool) results

The following document contains the results of Rat (Release Audit Tool).

*****************************************************
Summary
-------
Generated at: 2017-03-11T23:36:41-05:00

Notes: 0
Binaries: 0
Archives: 0
Standards: 2

Apache Licensed: 0
Generated Documents: 0

JavaDocs are generated, thus a license header is optional.
Generated files do not require license headers.

2 Unknown Licenses

*****************************************************

Files with unapproved licenses:

  C:/projects/fgsms/fgsms-ws-notification/pom.xml
  C:/projects/fgsms/fgsms-ws-notification/readme.md

*****************************************************

*****************************************************
  Files with Apache License headers will be marked AL
  Binary files (which do not require any license headers) will be marked B
  Compressed archives will be marked A
  Notices, licenses etc. will be marked N
 !????? C:/projects/fgsms/fgsms-ws-notification/pom.xml
 !????? C:/projects/fgsms/fgsms-ws-notification/readme.md
 
*****************************************************

 Printing headers for text files without a valid license header...
 
=====================================================
== File: C:/projects/fgsms/fgsms-ws-notification/pom.xml
=====================================================
<?xml version="1.0" encoding="UTF-8"?>
<!--
 This Source Code Form is subject to the terms of the Mozilla Public
 License, v. 2.0. If a copy of the MPL was not distributed with this
 file, You can obtain one at http://mozilla.org/MPL/2.0/.

 If it is not possible or desirable to put the notice in a particular
 file, then You may include the notice in a location (such as a LICENSE
 file in a relevant directory) where a recipient would be likely to look
 for such a notice.

 

 
 U.S. Government, Department of the Army
 Army Materiel Command
 Research Development Engineering Command
 Communications Electronics Research Development and Engineering Center

-->

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.mil-oss</groupId>
		<artifactId>fgsms-parent</artifactId>
		<version>7.0.0</version>
	</parent>
	
	
	<artifactId>fgsms-ws-notification</artifactId>
	<packaging>pom</packaging>
	<name>fgsms WS-Notification Parent</name>
	<description>An extremely simple implementation WS-Notification client and broker implementation with minimal dependencies</description>
	
	
	<modules>
	 <module>fgsms-wsnotification-client</module>
	 <module>fgsms-wsnotification-spec</module>
	 <module>fgsms-wsnotification-broker-jar</module>
	 <module>fgsms-wsnotification-broker-war</module>
	</modules>
	
	
</project>

=====================================================
== File: C:/projects/fgsms/fgsms-ws-notification/readme.md
=====================================================
# WS-Notification Broker implementation

This package is a number of WS-Notification libraries, written primarily as a super
simple example for WSN. At the time this was written, the only thing
that existed was Apache CXF's implementation, which was closely tied to
the CXF stack and difficult to separate. Thus this library was born.

## fgsms-wsnotification-spec
Basically, we have a spec library, which is essentially `wsimport`'s all of the
OASIS provided XSD's and WSDL's. 


## fgsms-wsnotification-broker-jar and fgsms-wsnotification-broker-war

The broker jar is a super simple, minimally implemented WS-Notification broker.
It only implements the bare minimum that FGSMS needs in order to deliver the 
alerts to subscribers. It's not very robust and is really only suitable for testing
and would most likely fall apart at volume. FGSMS only uses this for integration
tests. The WAR file is just a wrapper for the broker JAR to make it deployable
in Tomcat with Apache CXF. It is stateless, all data is stored in memory 

It should deploy the following endpoints

http://localhost:8080/fgsms.WSNBroker/services/
/WSN-Broker/RegistrationManager
/WSN-Broker/Broker
/WSN-Broker/PullPoint
/WSN-Broker/CreatePullPoint
/WSN-Broker/SubscriptionManager


## fgsms-wsnotification-client

This library has some reusable bits to make writing an async notification WS-N
client. It's used by the WS-Notification SLA Alerting plugin for FGSMS.



client notify interfaces with a callback delegate is present, implement interface 
`org.miloss.fgsms.wsn.clientcallback.IWSNCallBack`


example:

````
import org.miloss.fgsms.wsn.WSNotificationBroker;
import org.miloss.fgsms.wsn.client.NotificationService;
import org.oasis_open.docs.wsn.b_2.Notify;
import org.oasis_open.docs.wsn.brw_2.NotificationBroker;
import javax.xml.datatype.DatatypeConfigurationException;