[savara-commits] savara SVN: r117 - in validator/trunk: jbossesb/src/main/configs and 1 other directory.
do-not-reply at jboss.org
do-not-reply at jboss.org
Mon Dec 7 12:57:30 EST 2009
Author: objectiser
Date: 2009-12-07 12:57:30 -0500 (Mon, 07 Dec 2009)
New Revision: 117
Added:
validator/trunk/jbossesb/src/main/configs/pi4soa.xml
Removed:
validator/trunk/distribution/src/files/jbossesb/build.xml
validator/trunk/distribution/src/files/jbossesb/models/
validator/trunk/distribution/src/files/jbossesb/pi4soa.sar/
validator/trunk/distribution/src/files/jbossesb/readme.txt
Log:
SAVARA-49 - remove unnecessary pi4soa.sar and models folder. Moved pi4soa.xml to the validator.esb module.
Deleted: validator/trunk/distribution/src/files/jbossesb/build.xml
===================================================================
--- validator/trunk/distribution/src/files/jbossesb/build.xml 2009-12-07 16:21:38 UTC (rev 116)
+++ validator/trunk/distribution/src/files/jbossesb/build.xml 2009-12-07 17:57:30 UTC (rev 117)
@@ -1,75 +0,0 @@
-<project name="validator" default="deploy" basedir=".">
-
- <property name="target-server" value="${org.jboss.esb.server.home}/server/${org.jboss.esb.server.config}" />
-
-<!-- ==================================================================== -->
-<!-- This section handles the discovery of the messaging platform. -->
-<!-- ==================================================================== -->
-
- <target name="messaging-config" >
- <property name="org.jboss.esb.server.deploy.dir"
- value="${target-server}/deploy"/>
-
- <condition property="messaging.present">
- <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging"/>
- </condition>
- <condition property="messaging.present">
- <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging.sar"/>
- </condition>
-
- <condition property="jbossmq.present">
- <not>
- <isset property="messaging.present"/>
- </not>
- </condition>
- </target>
-
- <!-- dependencies specific to JBoss Messaging -->
- <target name="messaging-dependencies" if="messaging.present" depends="messaging-config">
- <property name="jms.service.file" value="jbm-queue-service.xml"/>
- <property name="jms.description" value="JBoss Messaging"/>
- </target>
-
- <!-- dependencies specific to JBoss MQ -->
- <target name="jbossmq-dependencies" if="jbossmq.present" depends="messaging-config">
- <property name="jms.service.file" value="jbmq-queue-service.xml"/>
- <property name="jms.description" value="JBoss MQ"/>
- </target>
-
-<!-- ==================================================================== -->
-<!-- This section handles the deploy and undeploy targets. -->
-<!-- ==================================================================== -->
-
- <target name="deploy" depends="register-validator-filter,messaging-dependencies,jbossmq-dependencies">
- <echo message="Deploy pi4soa.sar, savara-validator-jbossesb.esb files to the target server '${target-server}'." />
- <copy todir="${target-server}/deploy/pi4soa.sar">
- <fileset dir="${basedir}/pi4soa.sar">
- <exclude name="jms/**" />
- </fileset>
- </copy>
- <copy todir="${target-server}/deploy/pi4soa.sar"
- file="${basedir}/pi4soa.sar/jms/${jms.service.file}" />
- <copy todir="${target-server}/deploy/savara-validator-jbossesb.esb">
- <fileset dir="${basedir}/savara-validator-jbossesb.esb" />
- </copy>
- </target>
-
- <target name="undeploy" depends="unregister-validator-filter">
- <echo message="Undeploy pi4soa.sar, savara-validator-jbossesb.esb files from the target sever '${target-server}'."/>
- <delete dir="${target-server}/deploy/pi4soa.sar" />
- <delete dir="${target-server}/deploy/savara-validator-jbossesb.esb" />
- </target>
-
- <target name="register-validator-filter">
- <echo message="register the validator filter in the jbossesb-properties file" />
- <delete file="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" />
- <copy file="${basedir}/conf/jbossesb-properties-validator.xml" tofile="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" />
- </target>
-
- <target name="unregister-validator-filter">
- <echo message="unregister the validator filter from the jbossesb-properties file" />
- <delete file="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" />
- <copy file="${basedir}/conf/jbossesb-properties.xml" tofile="${target-server}/deploy/jbossesb.sar/jbossesb-properties.xml" />
- </target>
-
-</project>
Deleted: validator/trunk/distribution/src/files/jbossesb/readme.txt
===================================================================
--- validator/trunk/distribution/src/files/jbossesb/readme.txt 2009-12-07 16:21:38 UTC (rev 116)
+++ validator/trunk/distribution/src/files/jbossesb/readme.txt 2009-12-07 17:57:30 UTC (rev 117)
@@ -1,37 +0,0 @@
-Required to deploy the validator libraries.
-- ANT
-
-Folder structures
------------------------
-1 - pi4soa.sar
-
-2 - savara-validator-jbossesb.esb It contains the monitor config file (WS-CDL file) that will be used by the Filter.
-
-3 - conf/ It contains the proper configuration for governance deployment.
-
-4 - models It contains the WS-CDL models archive.
-
-
-
-Instructions for deploying/undeploying by using ANT (recommended)
-------------------------------------------------------------------
-1 - Go to $savara/install directory.
-
-2 - Run "ant deploy-savara-validator" to deploy the validator libraries.
-
-3 - Run "ant undeploy-savara-validator" to undeploy the validator libraries.
-
-
-
-Deploying validator libraries manually
------------------------------------------------------------
-
-1 - Copy the "pi4soa.sar", "monitor.esb" two libraries to the $JBossESB/server/config (e.g. default)/deploy folder.
-
-2 - Open up the "jbossesb-properties.xml", which is loated in the $JBossESB/server/$domain/deploy/jbossesb.sar folder.
-
- Add following "monitor filter" in the file, at the bottom of the '<properties name="filter">' xml block.
-
- ' <property name="org.jboss.soa.esb.filter.10" value="org.pi4soa.jbossesb.monitor.MonitorFilter" /> '
-
-
Added: validator/trunk/jbossesb/src/main/configs/pi4soa.xml
===================================================================
--- validator/trunk/jbossesb/src/main/configs/pi4soa.xml (rev 0)
+++ validator/trunk/jbossesb/src/main/configs/pi4soa.xml 2009-12-07 17:57:30 UTC (rev 117)
@@ -0,0 +1,38 @@
+<!--
+/*
+# * Copyright 2005-8 Pi4 Technologies Ltd
+# *
+# * Licensed under the Apache License, Version 2.0 (the "License");
+# * you may not use this file except in compliance with the License.
+# * You may obtain a copy of the License at
+# *
+# * http://www.apache.org/licenses/LICENSE-2.0
+# *
+# * Unless required by applicable law or agreed to in writing, software
+# * distributed under the License is distributed on an "AS IS" BASIS,
+# * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# * See the License for the specific language governing permissions and
+# * limitations under the License.
+# *
+# *
+# * Change History:
+# * 16, June 2008: Initial version created by gary
+# */
+-->
+
+<pi4soa>
+ <container>
+ <serviceTracker class="org.pi4soa.service.tracker.jms.JMSServiceTracker" >
+ <jmsConnectionFactory>ConnectionFactory</jmsConnectionFactory>
+ <jmsDestination>topic/tracker</jmsDestination>
+ <recordMessagePayload>true</recordMessagePayload>
+ </serviceTracker>
+ </container>
+ <monitor>
+ <serviceTracker class="org.pi4soa.service.tracker.jms.JMSServiceTracker" >
+ <jmsConnectionFactory>ConnectionFactory</jmsConnectionFactory>
+ <jmsDestination>topic/tracker</jmsDestination>
+ <recordMessagePayload>true</recordMessagePayload>
+ </serviceTracker>
+ </monitor>
+</pi4soa>
\ No newline at end of file
More information about the savara-commits
mailing list