[wsas-java-dev] svn commit r149 - in wsas/java/trunk: . etc
modules/servlet-edition
svn at wso2.com
svn at wso2.com
Mon Dec 4 13:49:59 PST 2006
Author: deepal
Date: Mon Dec 4 13:49:59 2006
New Revision: 149
Modified:
wsas/java/trunk/README.txt
wsas/java/trunk/etc/src-dist-README.txt
wsas/java/trunk/modules/servlet-edition/README.txt
Log:
rename META_INF into META-INF
Modified: wsas/java/trunk/README.txt
==============================================================================
--- wsas/java/trunk/README.txt (original)
+++ wsas/java/trunk/README.txt Mon Dec 4 13:49:59 2006
@@ -35,7 +35,7 @@
2. POJO to Web service feature is still at an experimental stage.
One can upload jar/zip file and can create an AAR out of it.
If you uploaded a jar/zip file which has a services.xml file in its
-META_INF directory, when its transformed into AAR its services.xml
+META-INF directory, when its transformed into AAR its services.xml
will be replaced by the generated services.xml. In addition to this,
the user cannot associate any library dependencies or web content with
the generated AAR file.
Modified: wsas/java/trunk/etc/src-dist-README.txt
==============================================================================
--- wsas/java/trunk/etc/src-dist-README.txt (original)
+++ wsas/java/trunk/etc/src-dist-README.txt Mon Dec 4 13:49:59 2006
@@ -1,111 +1,111 @@
-WSO2 WSAS v at wso2wsas_version@ Java - Source Distribution
---------------------------------------------------------
-
-Welcome to the WSO2 WSAS @wso2wsas_version@ source distributiuon
-
-Whats new
----------
-
-* WS-Trust & WS-SecureConversation support
-* Improved WS-Security support, including signing & encryption,
- demonstrated using samples
-* WS-SecurityPolicy driven configuration for Apache Rampart
-* In-built Spring Support including the ability to upload spring beans and
- expose them as Web services.
-* Improved System, Service & operation statistics
-* Improved Logging configuration
-* Transport management
-* Keystore and certificate management
-* Runs on Geronimo App server
-* SMTP & JMS transport support
-* Ability to add/remove transport bindings to services
-* Grpahical & textual views of message flows
-* Limited WSDL 2.0 support
-
-For more information on WSO2 WSAS, visit the "WSO2 Oxygen Tank" at
-http://wso2.org/library
-
-Known Issues
-------------
-
-1. The AJAX dynamic client feature is still at an experimental stage.
-It has been successfully tested for simple types, simple type arrays
-and complex types but we still do not support complex type arrays.
-
-2. POJO to Web service feature is still at an experimental stage.
-One can upload jar/zip file and can create an AAR out of it.
-If you uploaded a jar/zip file which has a services.xml file in its
-META_INF directory, when its transformed into AAR its services.xml
-will be replaced by the generated services.xml. In addition to this,
-the user cannot associate any library dependencies or web content with
-the generated AAR file.
-
-Due to limitations in Axis2, method overloading is not supported, and
-hence the WSDL for services where methods are overloaded cannot be generated.
-Hence all WSDL based functionality related to services will not work for
-such services.
-
-3. Once in a while user might encounter the message
- "Your session has expired please login".
-When this happens, you will be automatically logged out and you would need
-to login again to continue your work.
-
-4. WS-Policy support is still in the experimental stage and limited to single
-port scenarios.
-
-5. You cannot have two different versions of the Apache Sandesha2 module
-in the system.
-
-System Requirements
--------------------
-1. Java Runtime Environment 1.4 or 1.5
-2. Maven 1.0.2 (http://maven.apache.org/
-3. Operating System
- Tested on Windows XP, Linux(Fedora core, Ubuntu and Gentoo), Mac OS X
-
-
-Setting Up the Environment and Tools
--------------------------------------
-Maven:
-
-The WSO2 WSAS build is based on Maven. Hence the prerequisites to build WSO2 WSAS
-from source distribution is to have Maven & JDK installed. Extensive instruction
-guides are available at the Maven site.
-
-This guide however contains the easiest path for quick environment setting.
-Advanced users who wish to know more about Maven can visit here.
-
- * MS Windows
- 1. Download and run the Windows installer package
- 2. Set the 'Environment Variables'
- ( create system variable MAVEN_HOME and edit path.
- eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
- path %MAVEN_HOME%\bin)
- 3. Make sure that system variable JAVA_HOME is set to the location of your JDK,
- eg. C:\Program Files\Java\jdk1.5.0_02
- 4. Run maven --version to verify that it is correctly installed.
-
- * Unix based OS (Linux etc)
-
-The tar ball or the zip archive is the best option. Once the archive is downloaded
-expand it to a directory of choice and set the environment variable MAVEN_HOME and
-add MAVEN_HOME/bin to the path as well. More instructions for installing Maven in
-Unix based operating systems can be found here.
-
-Once Maven is properly installed you can start building WSO2 WSAS.
-Building WSO2 WSAS from the Source Distribution
-
-The source distribution is available as a zipped archive. All the necessary build
-scripts are included with the source distribution. Expand the source archive to a
-directory of your choice. You can run the following commands inside that directory
-to build WSO2 WSAS.
-
-List of commands that can be run are as follows:
-
-Note: The first time you run Maven it will automatically download
-the dependent jars. Therefore, first run will take more time.
-Maven release To create the complete release artifacts including
-Standalone Edition, Servlet Edition, and source distributions.
-
-maven dist - To create Standalone Edition and Servlet Edition distributions.
+WSO2 WSAS v at wso2wsas_version@ Java - Source Distribution
+--------------------------------------------------------
+
+Welcome to the WSO2 WSAS @wso2wsas_version@ source distributiuon
+
+Whats new
+---------
+
+* WS-Trust & WS-SecureConversation support
+* Improved WS-Security support, including signing & encryption,
+ demonstrated using samples
+* WS-SecurityPolicy driven configuration for Apache Rampart
+* In-built Spring Support including the ability to upload spring beans and
+ expose them as Web services.
+* Improved System, Service & operation statistics
+* Improved Logging configuration
+* Transport management
+* Keystore and certificate management
+* Runs on Geronimo App server
+* SMTP & JMS transport support
+* Ability to add/remove transport bindings to services
+* Grpahical & textual views of message flows
+* Limited WSDL 2.0 support
+
+For more information on WSO2 WSAS, visit the "WSO2 Oxygen Tank" at
+http://wso2.org/library
+
+Known Issues
+------------
+
+1. The AJAX dynamic client feature is still at an experimental stage.
+It has been successfully tested for simple types, simple type arrays
+and complex types but we still do not support complex type arrays.
+
+2. POJO to Web service feature is still at an experimental stage.
+One can upload jar/zip file and can create an AAR out of it.
+If you uploaded a jar/zip file which has a services.xml file in its
+META-INF directory, when its transformed into AAR its services.xml
+will be replaced by the generated services.xml. In addition to this,
+the user cannot associate any library dependencies or web content with
+the generated AAR file.
+
+Due to limitations in Axis2, method overloading is not supported, and
+hence the WSDL for services where methods are overloaded cannot be generated.
+Hence all WSDL based functionality related to services will not work for
+such services.
+
+3. Once in a while user might encounter the message
+ "Your session has expired please login".
+When this happens, you will be automatically logged out and you would need
+to login again to continue your work.
+
+4. WS-Policy support is still in the experimental stage and limited to single
+port scenarios.
+
+5. You cannot have two different versions of the Apache Sandesha2 module
+in the system.
+
+System Requirements
+-------------------
+1. Java Runtime Environment 1.4 or 1.5
+2. Maven 1.0.2 (http://maven.apache.org/
+3. Operating System
+ Tested on Windows XP, Linux(Fedora core, Ubuntu and Gentoo), Mac OS X
+
+
+Setting Up the Environment and Tools
+-------------------------------------
+Maven:
+
+The WSO2 WSAS build is based on Maven. Hence the prerequisites to build WSO2 WSAS
+from source distribution is to have Maven & JDK installed. Extensive instruction
+guides are available at the Maven site.
+
+This guide however contains the easiest path for quick environment setting.
+Advanced users who wish to know more about Maven can visit here.
+
+ * MS Windows
+ 1. Download and run the Windows installer package
+ 2. Set the 'Environment Variables'
+ ( create system variable MAVEN_HOME and edit path.
+ eg: "C:\Program Files\Apache Software Foundation\maven-1.0.2";
+ path %MAVEN_HOME%\bin)
+ 3. Make sure that system variable JAVA_HOME is set to the location of your JDK,
+ eg. C:\Program Files\Java\jdk1.5.0_02
+ 4. Run maven --version to verify that it is correctly installed.
+
+ * Unix based OS (Linux etc)
+
+The tar ball or the zip archive is the best option. Once the archive is downloaded
+expand it to a directory of choice and set the environment variable MAVEN_HOME and
+add MAVEN_HOME/bin to the path as well. More instructions for installing Maven in
+Unix based operating systems can be found here.
+
+Once Maven is properly installed you can start building WSO2 WSAS.
+Building WSO2 WSAS from the Source Distribution
+
+The source distribution is available as a zipped archive. All the necessary build
+scripts are included with the source distribution. Expand the source archive to a
+directory of your choice. You can run the following commands inside that directory
+to build WSO2 WSAS.
+
+List of commands that can be run are as follows:
+
+Note: The first time you run Maven it will automatically download
+the dependent jars. Therefore, first run will take more time.
+Maven release To create the complete release artifacts including
+Standalone Edition, Servlet Edition, and source distributions.
+
+maven dist - To create Standalone Edition and Servlet Edition distributions.
maven jar - Compiling and building the jars
\ No newline at end of file
Modified: wsas/java/trunk/modules/servlet-edition/README.txt
==============================================================================
--- wsas/java/trunk/modules/servlet-edition/README.txt (original)
+++ wsas/java/trunk/modules/servlet-edition/README.txt Mon Dec 4 13:49:59 2006
@@ -35,7 +35,7 @@
2. POJO to Web service feature is still at an experimental stage.
One can upload jar/zip file and can create an AAR out of it.
If you uploaded a jar/zip file which has a services.xml file in its
-META_INF directory, when its transformed into AAR its services.xml
+META-INF directory, when its transformed into AAR its services.xml
will be replaced by the generated services.xml. In addition to this,
the user cannot associate any library dependencies or web content with
the generated AAR file.
More information about the Wsas-java-dev
mailing list