[jboss-svn-commits] JBL Code SVN: r15436 - in labs/jbosstm/workspace/baframework/trunk: demo and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri Sep 28 09:46:16 EDT 2007
Author: maciej.machulak
Date: 2007-09-28 09:46:16 -0400 (Fri, 28 Sep 2007)
New Revision: 15436
Added:
labs/jbosstm/workspace/baframework/trunk/demo/changelog.txt
labs/jbosstm/workspace/baframework/trunk/demo/contributors.txt
labs/jbosstm/workspace/baframework/trunk/demo/license.txt
labs/jbosstm/workspace/baframework/trunk/demo/readme.txt
Modified:
labs/jbosstm/workspace/baframework/trunk/build.xml
labs/jbosstm/workspace/baframework/trunk/demo/build.xml
labs/jbosstm/workspace/baframework/trunk/readme.txt
Log:
Changes in build.xml file, rewritten readme.txt document
Modified: labs/jbosstm/workspace/baframework/trunk/build.xml
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/build.xml 2007-09-28 13:43:30 UTC (rev 15435)
+++ labs/jbosstm/workspace/baframework/trunk/build.xml 2007-09-28 13:46:16 UTC (rev 15436)
@@ -28,7 +28,7 @@
<property name="xts.home" location="/home/raistlin/Desktop/RedHat/jbossts/xts/xts-install"/>
<!-- You should not need to modify anything below this point -->
- <property name="jboss.profile" value="all"/>
+ <property name="jboss.profile" value="default"/>
<property name="jboss.server" value="${jboss.home}/server/${jboss.profile}"/>
<property name="jboss.aop.dir" location="${jboss.server}/deploy/jboss-aop-jdk50.deployer"/>
<property name="javaee.dir" location="${jboss.server}/lib"/>
Modified: labs/jbosstm/workspace/baframework/trunk/demo/build.xml
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/demo/build.xml 2007-09-28 13:43:30 UTC (rev 15435)
+++ labs/jbosstm/workspace/baframework/trunk/demo/build.xml 2007-09-28 13:46:16 UTC (rev 15436)
@@ -21,16 +21,18 @@
@author JBoss Inc.
-->
-<project name="BADemo" default="ear" basedir=".">
+<project name="BADemo" default="compile" basedir=".">
<!-- You should modify the next two lines -->
<property name="jboss.home" value="/home/raistlin/Desktop/RedHat/jboss-4.2.1.GA"/>
<property name="xts.home" location="/home/raistlin/Desktop/RedHat/jbossts/xts/xts-install"/>
- <!-- You should not need to modify anything below this point -->
+ <!-- You may modify the next two lines -->
<property name="jboss.profile" value="default"/>
+ <property name="jboss.aop.dir" location="${jboss.home}/server/${jboss.profile}/deploy/jboss-aop-jdk50.deployer"/>
+
+ <!-- You should not modify anything below this point -->
<property name="jboss.server" value="${jboss.home}/server/${jboss.profile}"/>
- <property name="jboss.aop.dir" location="${jboss.server}/deploy/jboss-aop-jdk50.deployer"/>
<property name="baframework.dir" value="..\build"/>
<property name="build.dir" value="build"/>
<property name="build.config" value="${build.dir}/config"/>
@@ -43,6 +45,7 @@
<property name="ext.compile" value="${ext.libs} jaxrpc.jar servlet.jar"/>
<property name="ext.package" value="${ext.libs} jbossts-common.jar commons-logging.jar stax-api-1.0.jar wstx-asl-2.0.3.jar"/>
+
<target name="clean">
<delete dir="${build.dir}"/>
</target>
@@ -71,22 +74,22 @@
</fileset>
<fileset dir="${jboss.server}/deploy/jbossws.sar" includes="*.jar"/>
<fileset dir="${baframework.dir}" includes="baframework-client.jar"/>
- <fileset dir="${jboss.aop.dir}" includes="jboss-aop-jdk50.jar"/>
</path>
<path id="build.classpath">
<pathelement location="${build.dir}/classes"/>
</path>
+ <path id="jboss.aop.classpath">
+ <fileset dir="${jboss.aop.dir}" includes="jboss-aop-jdk50.jar"/>
+ </path>
+
<path id="run.classpath">
<path refid="classpath"/>
<path refid="build.classpath"/>
+ <path refid="jboss.aop.classpath"/>
</path>
- <path id="jboss.aop.classpath">
- <fileset dir="${jboss.aop.dir}" includes="jboss-aop-jdk50.jar"/>
- </path>
-
<target name="compile" depends="init" description="compile the source">
<mkdir dir="${build.dir}"/>
<javac destdir="${build.dir}/classes" classpathref="classpath">
@@ -114,7 +117,7 @@
<jar destfile="${build.dir}/config.jar" basedir="${build.config}"/>
</target>
- <target name="service" depends="aopc, config" description="make the service distribution">
+ <target name="service" depends="config" description="create the service archive">
<copy file="${resources.dir}/jaxws-handlers-server.xml" todir="${build.dir}/classes/com/jboss/ba/demo/service/"/>
<jar destfile="${build.dir}/webapps/hotel.jar">
<metainf dir="${resources.dir}">
@@ -130,7 +133,7 @@
</jar>
</target>
- <target name="client" depends="service" description="make the client distribution">
+ <target name="client" depends="service" description="create the client archive">
<copy file="${resources.dir}/jaxws-handlers-client.xml" todir="${build.dir}/classes/com/jboss/ba/demo/client/"/>
<war destfile="${build.dir}/webapps/bademo.war">
<webinf dir="${resources.dir}">
@@ -149,7 +152,7 @@
</war>
</target>
- <target name="ear" depends="client" description="make the distribiution">
+ <target name="ear" depends="client" description="create the archive">
<ear earfile="${build.dir}/bademo.ear" appxml="${resources.dir}/application.xml">
<fileset dir="${build.dir}" includes="config.jar"/>
<fileset dir="${build.dir}/webapps" includes="*.jar *.war"/>
@@ -162,7 +165,7 @@
<taskdef name="aopc" classname="org.jboss.aop.ant.AopC" classpathref="jboss.aop.classpath"/>
- <target name="aopc" depends="compile">
+ <target name="aopc">
<aopc compilerclasspathref="run.classpath" verbose="false">
<classpath path="${build.dir}"/>
<src path="${build.dir}"/>
Added: labs/jbosstm/workspace/baframework/trunk/demo/changelog.txt
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/demo/changelog.txt (rev 0)
+++ labs/jbosstm/workspace/baframework/trunk/demo/changelog.txt 2007-09-28 13:46:16 UTC (rev 15436)
@@ -0,0 +1,7 @@
+Thu Sep 28 11:12:00 GMT 2007
+
+- support for compile time AOP
+- example of compensation on a Web Service
+- cleaned descriptions in the demo application
+- debugged code (preparing towards 0.2.2)
++---+
Property changes on: labs/jbosstm/workspace/baframework/trunk/demo/changelog.txt
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosstm/workspace/baframework/trunk/demo/contributors.txt
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/demo/contributors.txt (rev 0)
+++ labs/jbosstm/workspace/baframework/trunk/demo/contributors.txt 2007-09-28 13:46:16 UTC (rev 15436)
@@ -0,0 +1,4 @@
+Individual contributors list:
+
+- Maciej P. Machulak (mmachulak at redhat.com)
+- Jonathan J. Halliday (jhalliday at redhat.com)
Property changes on: labs/jbosstm/workspace/baframework/trunk/demo/contributors.txt
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosstm/workspace/baframework/trunk/demo/license.txt
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/demo/license.txt (rev 0)
+++ labs/jbosstm/workspace/baframework/trunk/demo/license.txt 2007-09-28 13:46:16 UTC (rev 15436)
@@ -0,0 +1,280 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
Property changes on: labs/jbosstm/workspace/baframework/trunk/demo/license.txt
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosstm/workspace/baframework/trunk/demo/readme.txt
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/demo/readme.txt (rev 0)
+++ labs/jbosstm/workspace/baframework/trunk/demo/readme.txt 2007-09-28 13:46:16 UTC (rev 15436)
@@ -0,0 +1,144 @@
+JBoss, Home of Professional Open Source
+Copyright 2007, Red Hat Middleware LLC, and individual contributors
+as indicated by the @author tags.
+See the copyright.txt in the distribution for a full listing
+of individual contributors.
+This copyrighted material is made available to anyone wishing to use,
+modify, copy, or redistribute it subject to the terms and conditions
+of the GNU General Public License, v. 2.0.
+This program is distributed in the hope that it will be useful, but WITHOUT A
+WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+PARTICULAR PURPOSE. See the GNU General Public License for more details.
+You should have received a copy of the GNU General Public License,
+v. 2.0 along with this distribution; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+MA 02110-1301, USA.
+
+(C) 2007,
+ at author JBoss Inc.
+
+### Business Activity Framework & Demo Application
+### Version: 0.1
+### Date: July 31, 2007
+### Author: Maciej Machulak (mmachulak at redhat.com)
+### WWW: http://labs.jboss.com/jbosstm/baframework
+
+Contents:
+1. Introduction
+2. Building Business Activity Framework
+3. Building Business Activity Demo Application
+4. Other documentation
+
+
+### 1. Introduction
+
+The Business Activity Framework is a fully novel comprehensive solution for building
+transactional Web Services with accordance to the model defined in the WS-BusinessActivity
+specification. It provides a lightweight API that consists of a set of easy to learn and
+intuitive annotations and operations. It significantly facilitates development of transaction
+aware Web Services and releases programmers from mixing transaction related code with business
+logic of their applications.
+Web Services must be simply annotated with a set of defined annotations and the framework
+transparently applies all necessary transactional mechanisms to enable participation in
+long-running Business Activities.
+
+IMPORTANT NOTICE:
+This is the first release of the framework and is aimed mainly for testing.
+
+It it assumed that demo application is tested locally - Coordinator has been set to
+following address: http://localhost:8080. This is set in the following file:
+ws-c.war (WEB-INF/web.xml)
+
+ <init-param>
+ <param-name>BaseHttpURI</param-name>
+ <param-value>http://localhost:8080/xts/soap/</param-value>
+ </init-param>
+
+The client application uses the http://localhost:8080 address to lookup Web Services
+by default as well. This can be changed in the following source file:
+com/jboss/ba/demo/client/HotelService.java
+
+It is possible to use either deployment time of compile time AOP instrumentation. By
+default JBoss Application Server comes bundled with a JBoss AOP Deployer (this deployer,
+however, must be enabled explicitly - please refer to the JBoss AOP documentation for
+further instructions.
+
+
+### 2. Building Business Activity framework
+
+Building the BA Framework requires following components:
+- JDK (version 1.5)
+ (available at http://java.sun.com/javase/downloads/index_jdk5.jsp)
+- Ant build tool (version 1.7.0)
+ (available at http://ant.apache.org/)
+- JBoss Application Server (version 4.2.1 GA)
+ (available at http://labs.jboss.com/jbossas/)
+- JBoss Transaction Service (version 4.2.3 SP5)
+ (available at http://labs.jboss.com/jbosstm/)
+
+1) Edit 'build.xml' file and set following properties:
+ - jboss.home (e.g. "/home/mmachulak/dev/jboss-4.2.1.GA")
+ - xts.home" (e.g. "/home/mmachulak/dev/JBossTS/XTS/xts-install")
+
+2) Run 'ant'
+ This produces following files:
+ - build/baframework-client.jar
+ - build/baframework.aop
+
+ 'baframework-client.jar' file needs to be in the classpath of the application that wants
+ to use the framework.
+ 'baframework.aop' file must be deployed with the application as shown in the following
+ example of application.xml file:
+
+ <application>
+ <module>
+ <ejb>MyEJB.jar</ejb>
+ </module>
+
+ <module>
+ <java>baframework.aop</java>
+ </module>
+ </application>
+
+ For the use of the demo application it is not necessary to copy those files anywhere.
+
+
+### 3. Building Business Activity Demo Application
+
+Building the BA Framework Demo Application requires following components:
+- JDK (version 1.5)
+ (available at http://java.sun.com/javase/downloads/index_jdk5.jsp)
+- Ant build tool (version 1.7.0)
+ (available at http://ant.apache.org/)
+- JBoss Application Server (version 4.2.0 GA)
+ (available at http://labs.jboss.com/jbossas/)
+- JBoss Transaction Service (version 4.2.3 SP5)
+ (available at http://labs.jboss.com/jbosstm/)
+
+1) Go to the demo/ directory (i.e. 'cd demo/')
+
+2) Edit 'build.xml' file and set following properties:
+ - jboss.home (e.g. "/home/mmachulak/dev/jboss-4.2.0.GA")
+ - xts.home" (e.g. "/home/mmachulak/dev/JBossTS/XTS/xts-install")
+
+3) Run 'ant'
+ This produces the following file:
+ - build/bademo.ear
+
+ This archive contains the demo application (hotel.jar), the framework's client library
+ (baframework-client.jar), the framework (baframework.aop) and the required infrastructure
+ for WS-BusinessActivity.
+
+4) Run 'ant deploy'
+ This copies the bademo.ear file to the deployment directory of the JBoss Application Server.
+
+Demo application is accessible through the following address: http://localhost:8080/bademo
+
+All necessary information related to using the demo application has been provided on web pages
+that are the part of the demo application.
+
+
+### 4. Other documentation
+
+All documentation directly related to the Business Activity framework can be found on the
+website of this framework (http://labs.jboss.com/jbosstm/baframework).
Property changes on: labs/jbosstm/workspace/baframework/trunk/demo/readme.txt
___________________________________________________________________
Name: svn:executable
+ *
Modified: labs/jbosstm/workspace/baframework/trunk/readme.txt
===================================================================
--- labs/jbosstm/workspace/baframework/trunk/readme.txt 2007-09-28 13:43:30 UTC (rev 15435)
+++ labs/jbosstm/workspace/baframework/trunk/readme.txt 2007-09-28 13:46:16 UTC (rev 15436)
@@ -18,8 +18,8 @@
@author JBoss Inc.
### Business Activity Framework & Demo Application
-### Version: 0.1
-### Date: July 31, 2007
+### Version: 0.2.1
+### Date: September 28, 2007
### Author: Maciej Machulak (mmachulak at redhat.com)
### WWW: http://labs.jboss.com/jbosstm/baframework
@@ -61,7 +61,7 @@
It is possible to use either deployment time of compile time AOP instrumentation. By
default JBoss Application Server comes bundled with a JBoss AOP Deployer (this deployer,
however, must be enabled explicitly - please refer to the JBoss AOP documentation for
-further instructions.
+further instructions).
### 2. Building Business Activity framework
@@ -110,7 +110,7 @@
(available at http://java.sun.com/javase/downloads/index_jdk5.jsp)
- Ant build tool (version 1.7.0)
(available at http://ant.apache.org/)
-- JBoss Application Server (version 4.2.0 GA)
+- JBoss Application Server (version 4.2.1 GA)
(available at http://labs.jboss.com/jbossas/)
- JBoss Transaction Service (version 4.2.3 SP5)
(available at http://labs.jboss.com/jbosstm/)
@@ -118,10 +118,19 @@
1) Go to the demo/ directory (i.e. 'cd demo/')
2) Edit 'build.xml' file and set following properties:
- - jboss.home (e.g. "/home/mmachulak/dev/jboss-4.2.0.GA")
+ - jboss.home (e.g. "/home/mmachulak/dev/jboss-4.2.1.GA")
- xts.home" (e.g. "/home/mmachulak/dev/JBossTS/XTS/xts-install")
3) Run 'ant'
+
+4) (OPTIONAL STEP) Applying the aspect during compile-time
+
+ Run 'ant aopc'
+ This performs the bytecode instrumentation at compile-time - the application server
+ (e.g. JBoss AS) does not have to be configured to instrument AOP bytecode at class
+ load time.
+
+5) Run 'ant ear'
This produces the following file:
- build/bademo.ear
@@ -129,7 +138,7 @@
(baframework-client.jar), the framework (baframework.aop) and the required infrastructure
for WS-BusinessActivity.
-4) Run 'ant deploy'
+6) Run 'ant deploy'
This copies the bademo.ear file to the deployment directory of the JBoss Application Server.
Demo application is accessible through the following address: http://localhost:8080/bademo
More information about the jboss-svn-commits
mailing list