diff options
| author | nash <nash@13f79535-47bb-0310-9956-ffa450edef68> | 2011-03-30 19:50:51 +0000 |
|---|---|---|
| committer | nash <nash@13f79535-47bb-0310-9956-ffa450edef68> | 2011-03-30 19:50:51 +0000 |
| commit | 3a569a2f00bf172cddfd567149774ee808a2a242 (patch) | |
| tree | 5b18450a44f7f33a4d3c56780393f15331150347 /sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release | |
| parent | c1fc4bd1ac2a2133b870e4314424cfd050bef607 (diff) | |
Create branch for 1.6.2
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1087059 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to '')
9 files changed, 5437 insertions, 0 deletions
diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/CHANGES b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/CHANGES new file mode 100644 index 0000000000..dc0403e8ef --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/CHANGES @@ -0,0 +1,1516 @@ +Changes With Apache Tuscany SCA 1.6.1 November 2010
+===================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+TUSCANY-3780 Build error in maven-incremental-build
+TUSCANY-3770 Tomcat 7 reports a memory leak when stopping a Tuscany webapp
+TUSCANY-3765 itest/wsdlgen creates classes that don't run on JDK 5
+TUSCANY-3764 Some LICENSE/NOTICE files in individual module jars aren't consistent with the LICENSE/NOTICE files in the binary distribution
+TUSCANY-3762 Tuscany SCA Eclipse plugin doesn't install correctly
+TUSCANY-3761 Using node-launcher to launch the domain manager doesn't work
+TUSCANY-3759 binding-erlang-runtime isn't compatible with the current version of Erlang/OTP
+TUSCANY-3743 binding.atom returns incorrect HTTP response code from If-Unmodified-Since
+TUSCANY-3742 binding.atom service problems with If-Modified-Since and If-Unmodified-Since headers
+TUSCANY-3737 feed-aggregator and feed-agggregator-webapp samples throw java.io.CharConversionException
+TUSCANY-3735 binding.atom can't connect to Apache Tuscany blog Atom feed
+TUSCANY-3734 binding.atom renders non-ASCII UTF-8 characters incorrectly
+TUSCANY-3730 Store tutorial fails to run from binary distribution because of missing database files
+TUSCANY-3729 Delete directories from 1.6.1 branch and 1.x trunk
+TUSCANY-3726 The store-dojo sample and its runtime dependencies should be included in the binary distribution
+TUSCANY-3723 binding-erlang modules and samples should be included in the binary distribution
+TUSCANY-3722 Tuscany SCA Java 1.x binary distribution could include an incorrect jaxws-api-2.1.jar
+TUSCANY-3707 itest/databindings/jaxb-bottom-up fails if not connected to internet
+TUSCANY-3706 Build failures in itests when using JDK 5
+TUSCANY-3699 samples/helloworld-ws-sdo README instructions are wrong and produce incorrect results
+TUSCANY-3698 JMS Binding erases the stack trace of RuntimeException's
+TUSCANY-3697 samples/osgi-supplychain ant script builds incorrect jar files
+TUSCANY-3693 tutorials/store/warehouse-spring doesn't work
+TUSCANY-3692 tutorials/store/store-eu doesn't work
+TUSCANY-3690 demos/xml-bigbank fails because remote services aren't available
+TUSCANY-3689 databinding-saxon corrupts XML documents when transforming from XMLStreamReader to NodeInfo
+TUSCANY-3685 build.xml file in samples/implementation-pojo-extension doesn't have a run target
+TUSCANY-3684 build.xml file in samples/domain-management doesn't work
+TUSCANY-3683 Service with RMI Binding cannot be promoted
+TUSCANY-3680 "clean" target in generated build.xml files fails with empty target directory
+TUSCANY-3678 Tuscany SCA source distribution contents don't match binary distribution
+TUSCANY-3676 Problems using Eclipse with samples in the Tuscany SCA Java binary distribution
+TUSCANY-3639 Wire interceptors not created until binding interceptors have executed in Service wire
+TUSCANY-3634 JMS Session is not closed when replyDest is null, then OutOfMemoroy
+TUSCANY-3625 Issue converting case on methodName for WSDL-derived operation used with binding.ejb reference
+TUSCANY-3615 itest/implementation-osgi produces bundle cache errors
+TUSCANY-3589 Domain manager produces "get - Error getting data" message when doing a search
+TUSCANY-3588 NullPointerException when adding composite in Domain Manager GUI
+TUSCANY-3587 Domain manager produces "post - Error getting data" message when adding a composite
+TUSCANY-3569 PolicyConfigurationException: The are unfulfilled intents for binding in reference
+TUSCANY-3561 Domain manager throws policy exception if definitions.xml file is read after .composite file
+TUSCANY-3551 ClassCastException in SCA Store Tutorial Integration Test
+TUSCANY-3550 Build failure in itest/osgi-implementation DSInterfacesTestCase
+TUSCANY-3540 Axis2SCAReferenceBindingProvider throws exception if servlet host not present
+TUSCANY-3490 Tuscany SCA binary distribution doesn't include implementation.web support
+TUSCANY-3475 Travel sample launcher for payment-bpel hangs before returning
+TUSCANY-3466 Cannot stop component or its services and references if one of them fails to start
+TUSCANY-3193 Domain Manager GUI does not put <binding.sca> entries in generated node confiig files
+TUSCANY-3037 binding-notification-producer failure on message send
+TUSCANY-1794 mvn builds larger sample-calculator-webapp.war than ant package
+TUSCANY-242 SCDL loader should trim the whitespaces when the element text is parsed
+
+Other commits:
+r1030676 Add a note to RELEASE_NOTES mentioning the Tuscany Eclipse update site
+r1029129 Fix incorrect war name to exclude from binary distribution
+r1028770 Update LICENSE file
+r1028725 Update LICENSE file to match the binary distribution lib directory contents
+r1028703 Remove SNAPSHOT from namespace string
+r1028696 Fix copyright notice dates
+r1028691 Fix copyright notice dates
+r1027738 Change release date and update list of changes
+r1027728 Update version number of jar file in README description
+r1026272 Add note to README about possible delays receiving chat messages
+r1026251 Remove explicit host name and port number from sample files
+r1026240 Change RSS feed to Atom feed so that it works with the atomAggregator service
+r1025930 Add test to ensure If-Modified-Since returns 304 if feed is unmodified
+r1025533 Fix typos
+r1023826 Use jar file contributions so that the store tutorial works when running from the binary distribution
+r1023378 Replace target/classes by target/demo-bigbank.jar in test classpath
+r1023375 Change run target to unzip jar file into classes directory (fix problem introduced in r1003117)
+r1023240 Exclude unwanted files from source distribution
+r1022055 Replace compile-time dependency on jaxws-rt by jaxws-api
+r1006269 Replace compile-time dependency on jaxws-rt by jaxws-api
+r1006263 Add compile-time dependency on binding-ws-axis2
+r1003145 Add timeout for stock quote service invocation and improve handling of connectivity errors
+r1003122 Remove redundant classpath dependencies
+r1003119 Remove redundant saxon dependency
+r1003117 Fix run target problem with using classes directory instead of jar file, and remove redundant saxon dependency
+r1003051 Remove redundant classpath entries
+r1003026 Fix incorrect shutdown instructions
+r1002885 Remove bundle jars under target/.felix from binary distribution
+r1002862 Add instructions for building the tutorial
+r1002859 Add build.xml to tutorials directory in binary distribution
+r1002848 Replace tabs by spaces
+r1002835 Fix indentation
+r1002816 Delete duplicate lines
+r1002811 Delete duplicate line
+r1002093 Fix resource exclusion patterns so that files under the target directory aren't incorrectly treated as resources
+r1002090 Use consistent resource exclusion patterns in all build files for the Store tutorial
+r1002088 Update README instructions
+r1002086 Add main class so that a run target is generated in build.xml
+r1002085 Add explicit ${basedir} references to ensure paths are correct when running from a top-level build
+r1002083 Add run targets to launch the nodes
+r1002077 Fix cut and paste error
+r1002075 Use hand-built build.xml file containing code to create the sample database
+r1002074 Use hand-built build.xml file containing code to create the sample database
+r1001759 Fix tuscany.version property setting
+r1001737 Fix main class name
+r1001710 Fix incorrect substitution parameters in message template
+r1001709 Add missing samples to README and tidy up some text
+r1001702 Update properties for generated build.xml
+r1001694 Generate build.xml instead of build-dependency.xml
+r1001501 Fix typos
+r1001069 Describe running and building the demo separately
+r1001060 Describe running and building the demo separately
+r1001054 Decouple run target from compile target
+r1001047 Put dojo files in correct location in jar file and include dijit
+r1001042 Delete redundant files and redundant entries in pom.xml and build.xml
+r1001036 Fix typo on web page
+r1000963 Fix typos and add maven build information
+r1000905 Explain that the WAR file is intentionally omitted from the binary distribution
+r1000902 Fix problems with the README file
+r1000896 Update README instructions to cover the case of the servlet container not using port 8080
+r1000887 Include dijit in maven build as well as ant build
+r1000878 Delete temporary dojo directory after maven packaging
+r1000868 Remove unused dojo dependency
+r1000787 Improvements to the README instructions
+r1000769 Minor improvements to the README instructions
+r1000768 Fix a numbe of problems in the README instructions
+r1000642 Add code to avoid a hang on exit with Tuscany SCA 1.6.1 (workaround for TUSCANY-3277)
+r1000626 Tidy up the README instructions to not require compiling before running
+r1000619 Tidy up the README instructions to cover all options for building and running
+r1000425 Update CORBA sample READMEs to include instructions for using ant
+r1000266 Fix notification sample build.xml and README files to provide clear instructions that work
+r1000237 Fix confusing prompt message
+r1000026 Add junit test dependency
+r999922 Exclude generated eclipse project files from the binary distribution and fix other inconsistencies
+r999921 Exclude generated eclipse project files from the source distribution
+r999920 Keep the generated tuscany-sca-manifest.jar in sync with the contents of the lib directory
+r999910 Update instructions for running this sample without needing to compile it first, and document the issue described in TUSCANY-1994
+r999904 Unzip files to target/database and target/classes before running sample (see TUSCANY-1994)
+r999902 Exclude geronimo-activation_1.1_spec and junit dependencies
+r999901 Fix incorrect version number for commons-lang and exclude junit dependencies
+r999899 Change junit dependency to test scope
+r999898 Change junit dependency to test scope
+r998521 Reorganize directory structure to make import into Eclipse work
+r998370 Reorder modules to satisfy dependency relationships
+r998367 Reorder modules to satisfy dependency relationships
+r998365 Fix svn:ignore property to add build.xml
+r998341 Add build.xml to samples directory
+r998332 Fix README references to incorrect module name
+r998330 Make "compile" the default target in build.xml
+r998328 Add missing code generation to build.xml file
+r998270 Add build.xml file to demos directory
+r998259 Add build.xml file to tutorials/store directory
+r998250 Replace generated build.xml file by a handwritten one
+r998248 Correct dependency in pom so that generated build.xml file is correct
+r998247 Generate a build.xml file from the maven build
+r998238 Add source directory to make the generated build.xml file work correctly
+r998237 Add build.xml file to svn with generated dependencies
+r998155 Delete generated build.xml files from svn
+r998083 Update recommended MAVEN_OPTS setting
+r998082 Add build.xml file with generated dependencies
+r998069 Add build.xml file with generated dependencies
+r998020 Generate build.xml instead of build-dependency.xml
+r997853 Delete .project file from svn
+r997848 Fix svn properties to ignore generated files
+r997840 Delete .project files from svn
+r997683 Fix incorrect mvn project names
+r997651 Fix svn properties to ignore generated files
+r997254 Remove tutorials/travelsample directory from source and binary distributions
+r996380 Update release documentation files for 1.6.1
+r959912 Add java.net2 repository (needed for mimepull-1.2.jar)
+r959536 Add build-dependency.xml to svn:ignore list
+r942469 Exclude junit 3.8 dependency brought in by wss4j and use junit 4.5 instead
+r921260 add ignores
+r915259 Correct the composite name
+
+Changes With Apache Tuscany SCA 1.6 January 2010
+================================================== +Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY): + +TUSCANY-3448 - SCA Property and Reference annotation processing in web application results in incorrect computed names +TUSCANY-3438 - Add calculator-corba samples to 1.6 release +TUSCANY-3435 - store-secure is missing build.xml +TUSCANY-3434 - Simple-bigbank-spring fails with ContributionReadException: Error reading manifest null +TUSCANY-3430 - Domain-management sample fails when trying to add deployables to a domain composite and wire them +TUSCANY-3429 - Databinding sample fails with AxisFault: The system cannot infer the transport information from the /ComponentA URL. +TUSCANY-3428 - Callbacks-jms fails with NPE +TUSCANY-3427 - Calculator distributed fails when starting domain manager +TUSCANY-3418 - <wireFormat.jmsText> is broken in some use cases +TUSCANY-3408 - Fix reference to missing namespace hortname in generated WSDL +TUSCANY-3394 - PropertyAnnotationtestCase vtest failing +TUSCANY-3389 - Tuscany Policies is returning an error code of 401 instead of 403 when an authenticated user requests a service which is not authorized for their role +TUSCANY-3382 - 1.x seems to have a dependency on a SNAPSHOT release of Lucene somewhere? +TUSCANY-3379 - useParentHandlers in JDKLoggingPolicy cannot be set +TUSCANY-3348 - PERF: handleCallback is not optimized +TUSCANY-3347 - composites that repesent implementation.jee component type are registered in the composite model resolver under a single name +TUSCANY-3312 - Potential memory leak in Java interface handling +TUSCANY-3309 - Invoker recieves a Message with no header data for a request that contained a SOAP header +TUSCANY-3303 - Concurrent access issue during wsdlgen +TUSCANY-3288 - Can't use non-Item type with atom Collection +TUSCANY-3283 - Generated WSDL not WS-I compliant in some cases +TUSCANY-3275 - alert-aggregator-webapp failes to start +TUSCANY-3272 - holder-ws-service falure +TUSCANY-3269 - Server name incorrect in WSDL when using separate web server +TUSCANY-3267 - <binding.ws> doesn't work when <interface.java> is used +TUSCANY-3266 - Run As Tuscany fails with NPE +TUSCANY-3265 - JMS itest PropertiesTestCase failure +TUSCANY-3264 - tutorial/store-test failure +TUSCANY-3260 - CORBA Extension test to ensure ORB is stopped fails in recent SUN JDK 6_014 +TUSCANY-3259 - wireFormat.jsonrpc removed from binding +TUSCANY-3256 - PolicyConfigurationException raised incorrectly when using operation level policy +TUSCANY-3255 - Consolidate JMS session management in JMSResourceFactory +TUSCANY-3250 - Implement multiple application context support using MANIFEST header +TUSCANY-3247 - Cannot get WidgetImplementationFactory (NoSuchMethodException) +TUSCANY-3240 - SpringXMLComponentTypeLoader leaves open a file handle to the application-context.xml +TUSCANY-3238 - Use of WS binding results in exception when returning data +TUSCANY-3237 - Use of collections for implicit SCA reference/property injection in constructors +TUSCANY-3235 - Exception thrown in JAXBContentCache.getPackages() when running applications with Java 2 security enabled +TUSCANY-3232 - Remove non-ASCII character from host-webapp LICENSE file +TUSCANY-3213 - ProblemImpl resides in assembly and means that other module have to access an impl packed to create a problem +TUSCANY-3202 - Bean name as service names for implicit services +TUSCANY-3200 - Correct a small inconsistency between the NOTICE file in web-javascript-dojo and the binary distro NOTICE file +TUSCANY-3199 - WebImplementationProcessor should prefix web.componentType URI with WEB-INF +TUSCANY-3198 - impl.jee : Generated EJBImplementation type has wrong information when more than one bean is present in a EJB module +TUSCANY-3195 - Inherently-provided intents do not work at operation level +TUSCANY-3185 - Warning message of duplicates during multiple application context processing +TUSCANY-3178 - The runtime doesn't read the validation schema extension point from the extension point registry and hence doesn't pick up any schemas that are added programatiically. +TUSCANY-3177 - The extension registry is no created until after runtime start and hence it's not available for updating in a way that will be taken note of at start time +TUSCANY-3174 - Allow extension points to be updated and exercised programmatically +TUSCANY-3173 - Restarting webapp leads to OutOfMemory: Permgen space in JSONRPC binding +TUSCANY-3167 - Look to cache JAXBPropertyDescriptor in XMLRootElementUtil +TUSCANY-3166 - Atom fails to set wrapper handler in top down case +TUSCANY-3165 - Failures in itest/contribution-jee +TUSCANY-3163 - Non-ascii characters in Corba binding code cause compile error +TUSCANY-3162 - problem building JAXBContext when package has mixed JAXBs, non-JAXBs +TUSCANY-3156 - Provide itest for the no-manifest scenarios in spring implementation module +TUSCANY-3153 - imported XSDefinition should be set with XmlSchema as well +TUSCANY-3149 - Restarting webapp leads to OutOfMemory: Permgen space +TUSCANY-3148 - Remove explicit version dependence from JEE zip based itests. +TUSCANY-3141 - Generated WSDL for void unwrapped operations has a return part for the response message +TUSCANY-3140 - Implementation.jee: The interface bound to the Runtimewire is not loaded with the class loader from implementation +TUSCANY-3128 - Spring app context classloader doesn't find contribution artifacts if the contribution isn't also on the application classpath +TUSCANY-3127 - NPE in JMS binding when it appear in same service a JSONRPC binding and $self$ reference is obtained +TUSCANY-3125 - policySets & intents not resolved on binding.http +TUSCANY-3124 - Check for wireFormat/OperationSelector before "get" operation +TUSCANY-3121 - binding.atom should leverage introspection when setting up call to mediator +TUSCANY-3120 - JMSBindingProcessor does not preserve file contents +TUSCANY-3116 - operationProperties attribute gets discarded +TUSCANY-3114 - There are no unit tests for the RSS binding +TUSCANY-3113 - RSS Binding is failing to detect whether the Java component implementation supports RSS feeds +TUSCANY-3112 - Links for the feed items are missing for an RSS feed created by the RSS binding on a Java component implentation that uses the Tuscany Dayta APIs +TUSCANY-3110 - Extend the Atom binding so that the description of the feed can be set +TUSCANY-3310 - JCA_10050/51 has incorectly named composite file +TUSCANY-3109 - NullPointerException thrown when using Atom binding on a Java component implementation class that does not have a get() method +TUSCANY-3104 - Using "FileSystemXmlApplicationContext" to load multiple application context files has problems with relative path identification +TUSCANY-3099 - NumberFormatException occurs when parsing a JMSPriority attribute with string value +TUSCANY-3098 - NPE in JMSBindingProcessor writing out property with no name +TUSCANY-3097 - External ear contribution processes all composite files in a Java EE Application and its modules. +TUSCANY-3096 - Switch off SCA Annotation support for Implementation.Spring +TUSCANY-3095 - DefaultBeanModelProcessor contror expects Class<implementation> but bindings need to use this processor also +TUSCANY-3086 - DefaultContributionFactory does not directly implement ContributionFactory interface +TUSCANY-3080 - NPE thrown while checking for Spring Version +TUSCANY-3078 - substitutionGroup is missing in ATOM binding, HTTP binding, and Widget impl +TUSCANY-3077 - SCA node cannot be stopped as ConversationManagerImpl holds a thread pool using ScheduledExecutorService +TUSCANY-3076 - Dealock in binding.ws for 2 concurrent callbacks +TUSCANY-3075 - The composite processor shouldn't write out references and services generated to handle callbacks. +TUSCANY-3070 - ModuleActivators being picked up twice from the classpath +TUSCANY-3069 - Implementation.spring cannot resolve the location or bean classes if the contribution is not on the TCCL +TUSCANY-3068 - Validate wire format and operation selection SCDL elements +TUSCANY-3065 - Double use exposure in JAXBDataSource +TUSCANY-3063 - Handle special characters when generating JSON-RPC SMD +TUSCANY-3059 - OperationProperties JMSDeliveryMode set in headers JMSDeliveryMode +TUSCANY-3058 - JMSBindingProcessor write methods write out 'JMSCorrelationId' instead of 'JMSCorrelationID' +TUSCANY-3052 - Component and Services not recognized from application composite of EAR used in impl.jee +TUSCANY-3057 - binding.jms fails to lookup ConnectionFactory +TUSCANY-3056 - Webapp samples are failing in Geronimo (issues caused by inverse-classloading) +TUSCANY-3054 - Introduce JavaInterfaceFactory impl employing caching of JavaInterface(s) based on Class +TUSCANY-3053 - Spring Jar Location testcase failing because of the URI issue +TUSCANY-3052 - Component and Services not recognized from application composite of EAR used in impl.jee +TUSCANY-3043 - Move the testcases available in implementation-spring-old module into itest/spring module. +TUSCANY-3042 - Fail to generate Widget JS when using binding http with json-rpc wire format/operation selector +TUSCANY-3041 - policySets & intents not resolved on implementation.jee +TUSCANY-3032 - ejb-linkType should be string +TUSCANY-3031 - Ensure that JMS jmsObject wore format works if the service interface is specified as WSDL +TUSCANY-3030 - itest\exceptions ExceptionsTestCase testRemote fails +TUSCANY-3018 - EarContributionProcessor's URL.setURLStreamHandlerFactory() fails with factory already defined error +TUSCANY-3017 - Validate Spring Binary Version used +TUSCANY-3011 - JMS binding schema contains a required headers element under OperationProperties +TUSCANY-3008 - Contribution-jee/testContributeEAR_Enhanced16 failing in maven but not in eclipse +TUSCANY-3005 - null one arg methods and void returns fail jmsdefault WF +TUSCANY-3002 - writeStartElement calls in JMSBindingProcessor do not pass namespace URI +TUSCANY-3000 - Turn databinding Mediator into a utility registered with UtilityExtensionPoint +TUSCANY-2999 - Property injection not working in implementation.widget js client +TUSCANY-2998 - Items added to store Shopping Cart not showing properly when using dojo based javaScript proxy +TUSCANY-2997 - Dojo based javascript for Atom Binding has unecessary dojo.require for XHR +TUSCANY-2996 - binding.jms/wireFormat.object - allow single parameters to be passed wrapped or unwrapped depending on user configuration +TUSCANY-2995 - BPEL error handling causes tests to block +TUSCANY-2993 - store-dojo sample doesn't work in IE +TUSCANY-2987 - Sort out jms operation selector mapping to service operations +TUSCANY-2986 - Separate callback processing from operation selector processing +TUSCANY-2984 - Potential IndexOutOfBounds in DojoModuleActivator +TUSCANY-2978 - sample apps for jee contribution processing tests +TUSCANY-2977 - determine implementation.jee component type from application composite if one is available +TUSCANY-2976 - Remove default "ConnectionFactory" in JMSBinding model +TUSCANY-2972 - Fix contribution classloader so that artifacts inside JEE archives can be found +TUSCANY-2968 - Provide support for binding.http based on OASIS draft specification +TUSCANY-2967 - For binding.jms, consider a more natural exception handling strategy for non-XML, non-Object wireFormats +TUSCANY-2966 - Adjust binding.jms code since JMS BytesMessage bytes payload can only be read once +TUSCANY-2965 - For JMS binding, add a jmsBytesXML wireFormat analogous to jmsTextXML +TUSCANY-2964 - Fix JMS operationSelector schema element name to operationSelector.jmsdefault to match OASIS +TUSCANY-2962 - Throw an exception if multiple same-name operations are detected by WSDL intf introspector +TUSCANY-2953 - Fix sca.tld in branches-1.x +TUSCANY-2937 - AtomAgreggator test cases failures +TUSCANY-2930 - Add wireFormat.jmsDefault for the JMS binding +TUSCANY-2906 - WSDL/XSD imports should use location/schemaLocation as hints and not fail due to locations that don't map to actual locations +TUSCANY-2900 - WSDL Generation does not respect all binding.ws entries +TUSCANY-2878 - Consider upgrade to dojo 1.3 +TUSCANY-2868 - Vtest code for Java SCA assembly component of 2009_02_24 +TUSCANY-2757 - Top down round trip problem where wrapper elements are marked as nillable by JAXB during WSDL generation +TUSCANY-2640 - Should use package(s) when possible in creating JAXBContext, not set of Classes +TUSCANY-2626 - Investigate why endpoint reference and wsdlLocation are not in the sca-binding-webservice.xsd schema file +TUSCANY-2552 - Implement a search function for the domain manager home page + +
+Changes With Apache Tuscany SCA 1.5.1 October 2009
+==================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+
+TUSCANY-2640 - Should use package(s) when possible in creating JAXBContext, not set of Classes
+TUSCANY-2878 - Moving to Dojo dependencies to Dojo 1.3.0 official release
+TUSCANY-2906 - Resolve wsdl:import and xsd:import using namespace
+TUSCANY-2967 - back out the trial change to bytes format messages so that all wire formats consistently return faults as JMS Object messages.
+TUSCANY-2978 - Add more JEE tests to help show that the nested composites are resolved/built correctly.
+TUSCANY-2984 - Adding prioritization while starting module activators to allow module activators dependencies to start first
+TUSCANY-3018 - EarContributionProcessor's URL.setURLStreamHandlerFactory() fails with factory already defined error
+TUSCANY-3052 - Update JEE processing to resolve the JEEImplementation composite.
+TUSCANY-3058 - Correct use of JMSCorrelationID to use an uppercase trailing 'D'
+TUSCANY-3059 - correct perationProperties JMSDeliveryMode set in headers JMSDeliveryMode
+TUSCANY-3062 - another work round to get resolution doing something in the domain manager
+TUSCANY-3063 - Adding new tests to ensure JSON-RPC binding can handle special characters when generating SMD
+TUSCANY-3065 - fix double use exposure in JAXBDataSource
+TUSCANY-3068 - Improve validation in JMS processors.
+TUSCANY-3069 - Implementation.spring cannot resolve the location or bean classes if the contribution is not on the TCCL
+TUSCANY-3070 - Work round to treat the symptom of activators being discovered twice on the classpath.
+TUSCANY-3075 - don't write out the services and references generated to handle callbacks.
+TUSCANY-3076 - The DefaultWorkScheduler only has 10 threads in the pool and it causes deadlock.
+TUSCANY-3077 - Allow the thread pool for conversation manager to be shutdown
+TUSCANY-3086 - Making DefaultContributionFactory implement contribution factory interface to avoid issues with model extention point
+TUSCANY-3080 - NPE thrown while checking for Spring Version
+TUSCANY-3096 - Switch off SCA Annotation support for Implementation.Spring
+TUSCANY-3097 - Add test to see if the application composites of modules inside anEAR are processed (they shouldn't be)
+TUSCANY-3098 - don't throw an NPE is a property doesn't have a name
+TUSCANY-3099 - log an error if an invalid header priority is entered
+TUSCANY-3104 - Using "FileSystemXmlApplicationContext" to load multiple application context files has problems with relative path identification
+TUSCANY-3109 - Added unit test for using Atom binding on a Java component implementation class that does not have a get() method
+TUSCANY-3110 - Updated the atom binding so that the description can be set using the description attribute.
+TUSCANY-3111 - Fixed NPE when using the RSS binding
+TUSCANY-3112 - Make sure that the feed entry has the links set on it otherwise the title of the item in the RSS feed will not be converted to a URL
+TUSCANY-3113 - Added get() method to the rss.Collections interface
+TUSCANY-3114 - Added a basic get test for the RSS feed
+TUSCANY-3116 - add support for the operationPropertyName attribute to the JMS binding model
+TUSCANY-3120 - improve write processing so that it writes out what has been entered and ignores defaults where possible.
+TUSCANY-3121 - binding.atom should leverage introspection when setting up call to mediator
+TUSCANY-3124 - Check for wireFormat/operationSelector before other operations
+TUSCANY-3125 - enable policy processing in binding.http
+TUSCANY-3128 - force the bean factory classloader to be the contribution classloader as it's reset by the application context on refresh.
+TUSCANY-3140 - Test for difference between loadtime and runtime classloaders
+TUSCANY-3141 - Generated WSDL for void unwrapped operations has a return part for the response message
+TUSCANY-3148 - remove version dependency from zip based JEE itests
+TUSCANY-3149 - Generally be more careful about removing object references in host-webapp.
+TUSCANY-3153 - imported XSDefinition should be set with XmlSchema as well
+TUSCANY-3155 - Support for spring implementation location as folder without manifest scenario
+TUSCANY-3162 - problem building JAXBContext when package has mixed JAXBs, non-JAXBs
+TUSCANY-3163 - Fixing non-ascii characters that were producing build failure when using IBM JDK 1.6
+TUSCANY-3166 - Making the test case works using the generated java interface
+TUSCANY-3167 - Look to cache JAXBPropertyDescriptor in XMLRootElementUtil
+TUSCANY-3169 - invalid characters in generated reference binding names
+TUSCANY-3170 - add callback URI configuration support to domain manager
+TUSCANY-3171 - domain manager does not load definitions.xml files
+TUSCANY-3172 - domain manager doesn't report errors cleanly to the nodes
+TUSCANY-3174 - Add workspace manager updates to workspace
+TUSCANY-3177 - create the extension point registry earlier so that any programmatic changes to it are reflected in the runtime configuration
+TUSCANY-3178 - read the validation schema extension point from the extension point registry rather than creating a local copy
+TUSCANY-3185 - Warning message of duplicates during multiple spring application context processing
+TUSCANY-3193 - fully support binding.sca in the domain manager
+TUSCANY-3195 - merge fix from 1.x to 1.5.1 for Inherently-provided intents do not work at operation level
+TUSCANY-3198 - keep generated EJB component implementations distinct.
+TUSCANY-3199 - WebImplementationProcessor should prefix web.componentType URI with WEB-INF
+TUSCANY-3200 - Add the dojo copyright to the NOTICE file to be consistent with the top level binary NOTICE file
+TUSCANY-3202 - Spring bean name as service names for implicit services
+TUSCANY-3213 - ProblemImpl resides in assembly and means that other module have to access an impl packed to create a problem
+TUSCANY-3235 - Java2 security problem
+TUSCANY-3237 - Remove auto indexing logic for constructors
+TUSCANY-3238 - Use of WS binding results in exception when returning data
+TUSCANY-3240 - Closing reader after processing spring application-context.xml
+TUSCANY-3247 - Making interfaces and instantiatng widget factory via extension point mechanism
+TUSCANY-3248 - Removing quoted tokens to avoid issues on linux/mac os environment
+TUSCANY-3249 - providing on/off feature for multiple application context support
+TUSCANY-3251 - Fix interface compatibility checking for callback operations
+TUSCANY-3254 - null returned by RequestContext.getCallbackReference()
+TUSCANY-3255 - Consolidate JMS session management in JMSResourceFactory
+TUSCANY-3264 - Tyiding up how we write the schema prefix as per StAX spec
+TUSCANY-3267 - ensure wrapper elements have nillable=false
+TUSCANY-3272 - create class to run holder tests when run from the distribution
+TUSCANY-3292 - fixing how spring context path is calculated
+
+Changes With Apache Tuscany SCA 1.5 May 2009
+============================================
+
+- Add dependency on jaxws (as the code now uses the Holder class) so it compiles on pre-JDK6
+- Merge branch 'tuscany-2663'
+- Remove unneeded deploy.xml and .componentType files
+- Reverting changes from revision #734356 and there was some merge conflicts that were not supposed to get to svn.
+- TUSCANY-2463 - Properly register default attribute processor to handle extended attributes
+- Exclude xsd module from base
+- Fixes for TUSCANY-2772
+- Renaming test cases to follow same naming pattern
+- Updating testcase to JUnit 4
+- TUSCANY-2463 - Storing extended attributes in a second list, wrapped into a extension class that stores the attribute QName, it's value
+- Removing obsolet test composite
+- TUSCANY-2663 - UPdating test scenarios to split valid extended element from invalid scenario where require attribute has empty value
+- TUSCANY-2463 - Last adjustments to test processors to support the extension attribute wrapper
+- TUSCANY-2463 - Fixing model object definition for extended attribute processor
+- copy stest framework from 2.x to consider potentially reusing in 1.x
+- Tuscany 2768 - sample showing web services Holder support (input/output parameters)
+- Start adding resources for a test of folder and zip contributions which contain application jars
+- TUSCANY-2783 - Adding schema for GData binding
+- TUSCANY-2783 - Integrating GData schema to tuscany schema
+- TUSCANY-2781 - Adding schema for Corba binding
+- TUSCANY-2781 - Integrating Corba schema to tuscany schema
+- TUSCANY-2781 - Fixing Corba schema with right binding name
+- TUSCANY-2784 - Adding schema for Java EE implementation
+- TUSCANY-2784 - Integrating Java EE schema to sca schema
+- Move to a seperate itest as that makes the itest simpler
+- Add an itest for folder contributions and zip contributions containing jars
+- Demonstrate how the non-JAXWS base class can be used. Add some ignores.
+- Start looking at seperating out the JMS service side listener functions into a pluggable module so different runtime environments can plug in their own runtime specific code. This should help the geronimo plugin support JMS using the Geronimo JMS provider and JCA, and any others who are using Tuscany deeply embedded in a container. Not in the build yet or used by the current JMS binding till it gets a bit further
+- and related to r737718 a module for the current JMS binding listener code that uses the 'asf' approach of a JMS listener spawning unmanaged threads to process messages
+- TUSCANY-2794 - JMS callback property variable ends with space - not a valid Javaidentifier
+- Removing holder-ws-service from pom as it seems the sample is not available
+- Process services in component pre-processing.
+- Start to add some JMS host interfaces
+- Start to add some JMS host default implementations
+- Fixes for TUSCANY-2771
+- Make jms host an extension point
+- Make the default jms host use the jms host extension point
+- Remove unused code
+- Add method to get the service destination to the jms host as you need that to get callbacks working
+- Implement the getDestination method in the default jms host
+- Intial cut at changing the jms binding to use the jms host for the service listener
+- Update the pom.xml to include a jms host
+- Update the pom.xml to include a jms host
+- update the jms itests to include a jms host
+- TUSCANY-2663 - Workaround for 'java.lang.IllegalStateException: The current state is not START_DOCUMENT' when in WebSphere env
+- Refactoring common code to simplify processing extended attributes
+- Adding support for extended attributes to webservices binding
+- Fixing test failures by ignoring tuscany NS when processing extended attributes
+- Adding support for extended attributes to EJB binding
+- Adding support for writing extended attributes to EJB binding
+- Adding support for extended attributes to java implementation
+- Removing System.out from WS Policy processor
+- Adding support for extended attributes to java interface
+- Adding support for extended attributes to wsdl interface
+- Remove some targetNamespace attributes
+- Remove some targetNamespace attributes
+- TUSCANY-2291, Separate the mixed callback error validation test from the other callback tests so that the error doesn't affect the rest of the tests
+- Removing obsolete dependency
+- Fixing sca.tld copy by adding rtexprvalue attribute
+- TUSCANY-2798: Add an itest for a service sending the response to the response destination defined on the jms binding element if the request message doesn't have a replyTo set
+- TUSCANY-2798: Fix the jms binding to use the destination in the binding response element when the request message has no replyto
+- TUSCANY-2776 The JMSBindingProcessor does not perform validation of binding properties
+- TUSCANY-2803 - Improvement to component matching in NodeImpl
+- TUSCANY-2463 - New test case that exercises extended attributes in bindings
+- Removing system.out from AnyAttribute test case
+- Removing unused imports
+- TUSCANY-2701 NPE when verifying conformance item ASM60006 in OASIS sepc
+- TUSCANY-2799 - don't return responses inside arrays. Generally reorg the code so that the message processors only worry about getting data in and out of JMS message while the interceptors worry about whether the data should be wrapped as an array. In this way the forward path can do array wrapping in order to keep databinding happy while the response path can omit array wrapping
+- Commit update to jms sca binding left off the change to the JMS binding to use the JMS Host
+- TUSCANY-2799 Fix NPE in JMS Object wire format when a null object is returned. Add a test also.
+- Remove target namespace from contribution.xml of distributed calculator
+- Add jms host modules to the build
+- TUSCANY-2820: start adding support for the varrious property elements on the jms binding
+- Fixes for TUSCANY-2451
+- Update validation tests for jms binidng updates
+- Correct dependency with backlevel version
+- TUSCANY-2823 Callback problem with COMPOSITE scoped implementation
+- Add support for operation property properties to binding.jms
+- Add support for resourceAdapter and its properties
+- Add support for resourceAdapter and its properties
+- TUSCANY-2821 Added JMS Binding APIs public Set<String> getOperationNames() and public Object getOperationProperty(String opName, String propName ).
+- TUSCANY-2463 - Fixing Web Service binding processor to propertly get a reference to Extended Attribute processor
+- Fixes for MTOM TestCase
+- TUSCANY-2824 - Turn the binding.ws policy handlers back on. The ws policy handlers are now present but commented out as they are causing problems in the Axis 1.4.1 stack. Update the keys for the binding.ws tests cases so they remain valid for a long time.
+- TUSCANY-2835 JMS Binding does not save operation names unless there are properties.
+- Merge branch 'bpel-resolver'
+- Removing system.out used for debug
+- Fix the TLD to use jsp taglib 2.1 xsd
+- TUSCANY-2463 - Enabling extended attribute support for default sca binding
+- Apply the TLD fix to use jsp taglib 2.1 xsd in the other copy sca.tld
+- Simplify so you can use createNode() instead of createNode(null, null)
+- Add jms itest using a response ConnectionFactory
+- Move jms responsecf itest to its own module to make it eaisier to debug
+- Remove erronious warning about response connection factory not being processed
+- TUSCANY-2841: start to add support for using a seperate response connection factory
+- Update for resource factory changes
+- Update noreply itest for change to not return Object arrays
+- Add jms noreply itest to itest build
+- Update jms response connectionFactory itest to correctly setup jndi resources
+- TUSCANY-2839: Start at supporting services invoked by oneway requests not needing a response connection factory
+- TUSCANY-2824 - turn WSSecurity based policy back on. Two not so great fixes here. Firstly WSSecurityPolicyHandler pushes a property into the Axis configuration context to force Rampart to recognize the policy. I haven't discovered what part of our configuration is required to do this properly. Secondly I fixed the helloworld-ws-service-secure test case to reference the wsdl on binding.ws. Without this you get a NPE in axis/rampart as it fails to map binding operations to port type operation using QNames (don't know why it thinks these are QNames). Our generated WSDL has the generated binding in a different namespace to the port type. Associating the wsdl binding with binding.ws means that the binding is not generated at the made up QNames match. I also updated a few key stores as the runtime was complaining about X509 certificate version numbers.
+- Add a jms oneway itest with a nondefault connection factory
+- Set svn ignores
+- Make sure resource factory gets set before use to avoid any NPEs
+- TUSCANY-2825 JMSBindingProcessor missing 'write' method implementation
+- TUSCANY-2847 - Updating composite used to verify any element processing
+- TUSCANY-2836 remove DEFAULT_DESTINATION_NAME and DEFAULT_RESPONSE_DESTINATION_NAME and use null instead as these are just strings to indicated that there is no destination rather than being a default destination
+- Fix for TUSCANY-2846
+- Reenable a commented out test as the jira has been fixed
+- Add a JMS test for exceptions using a non-SCA JMS client. Doesn't actually test the responses yet but the framework is there to send and receive the messages to the sca service
+- UPdate jms exceptions testcase so the object format tests work
+- Add the jms nonsca excpetions test to build
+- Fixes for TUSCANY-2840
+- Change XMLTextMessageProcessor to override the createFaultMessage to handle FaultExceptions
+- Activate text and object tests in the jms nonsca client exxceptions test
+- Activate the unchecked exception test, still need to establish what the response should really look like
+- Correct test name
+- Partial fix for exceptions for sca clients using text xml wireformat
+- Update JAXWSFaultExceptionMapper to handle extra contsructor
+- Comment out failing assertions for the time being
+- Update with JIRA about the problem
+- Fix for TUSCANY-2779. Thanks zhulei for the patch.
+- Remove old test thats nolonger applicable
+- TUSCANY-2839: Add checks to bypass response processing for oneway operations
+- TUSCANY-2845: Change JMS binding so unchecked exceptions are returned as RuntimeExceptions
+- Use Logger instead e.printStackTrace
+- Fix for TUSCANY-2854: remove the use of "tempuri.org"
+- TUSCANY 2855 - Adding Holder WS Sample
+- TUSCANY-2855 Holder sample not appearing (part 2, missed a few files)
+- Fix the JAXBException if package-info annotated with @XmlSchema is present without ObjectFactory
+- Fix for TUSCANY-2702
+- Fix for TUSCANY-2860
+- Fixes for TUSCANY-2840-Part2
+- Fixes for TUSCANY-2840-Part3
+- Add a method that returns an unchecked exception
+- Add ignores
+- Commit some code to write out composite model during processing. Uncomment to use.
+- TUSCANY-2859: Add a closeResponseConnection method to the JMSResourceFactory
+- TUSCANY-2849 Unable to define operation-level intents on binding.jms
+- TUSCANY-2861: Add an itest for sending/receiving null
+- Add jms-nulls itest to build
+- TUSCANY-2861: Fix Object wireformat to deal with receiveing a null message correctly
+- Fix already closed bug when the responseConnection is the same as the request connection
+- Fix already closed bug with oneway requests
+- Add BPEL document resolver to defer to namespace imports if document is not found in current contribution
+- Make property ids optional
+- Fix for TUSCANY-2550
+- Fix for TUSCANY-2550
+- TUSCANY-2867 - Pass checked exceptions as InvocationTargetExceptions. Don't rely on boolean fault flag for messages of object type. Thanks for the patch Kaushik
+- TUSCANY-2857 Correct handling of JMSDeliveryMode and JMSPriority
+- Improve some assembly component tests to be more specific
+- TUSCANY-2856 'property' validation conflicts with osoa spec
+- Correct the type of message that CompositeProcessor reports for a CompositeReadException and correct a few tests to take account of this and another couple of exception funnies.
+- Fix the push/pop out of sequence issue
+- Adding new store-secure sample to exercise security policy in web 2.0 extensions
+- Adding support to enable SSL when using binding-http using Confidentiality policy intent
+- Minor cleanup on the policy properties
+- Refactoring confidentiality policy support for http bindings to it's own module
+- Updating NodeWebAppServletHost to provide new version of addServletMapping
+- Updating WebAppServletHost to provide new version of addServletMapping
+- Adding support for enabling and configuring authentication for embedded http server using policy
+- Removing empty folder
+- TUSCANY-2868 - Add more assembly/component test cases. Thanks for the patch Jun Guo
+- TUSCANY-2864 - Fix end of test comment. Thanks for the patch emily
+- TUSCANY-2874 - Add ASM_6030_TestCase - thanks for the patch Susan
+- Fix for TUSCANY-2875
+- Fix for TUSCANY-2875
+- TUSCANY-2897 JMSBinding model should be QNames not Strings
+- TUSCANY-2871 ClassCastException using atom-abdera binding
+- Only create a transport description for the JMS transport if JMS is configured to be in use.
+- Fixes for TUSCANY-2642, 2909, 2910
+- Fixes for TUSCANY-2642
+- Remove SpringSCAPropertyElement.java.orig
+- Removing empty folder
+- TUSCANY-2905 Implement third rule which is supposed to look for an operation name in the root element of the XML payload
+- TUSCANY-2907 Stest code
+- Adding code to use full binding uri when provided, otherwise using relative path - note that code is commented out for now
+- TUSCANY-2884 - more composite vtests. Thanks for the patch Susan.
+- Updating-DWR-dependency-level-to-2.0.3
+- Placing gif jpg files used for testing in test resource folder
+- Moving to use DOJO 1.3.0b3
+- Update scn urls required by continuuns builds
+- Updating project name to help identify (1.x) versus (2.x) builds in continuuns environment
+- Fix the J2W generation issue which misses the target namespace
+- Make the artifactURI "" resolve to the sourceURL.
+- Added an EAR packaging type. Updated WAR to use PackageType.WAR.
+- o JavaEE processors to introspect WAR, JAR and EAR files and create model objects
+- Missing and wrongly placed license headers.
+- Updated the methods to throw ContributionReadException.
+- Java EE Introspection code using OpenEJB.
+- URI "" corresponds to the archive as an artifact.
+- Fix a regression caused by r755474
+- Use the JavaEE optional extension to compute SCA references and SCA properties from Remote EJB3 references and EnvEntries.
+- Use the JavaEE extensions to compute SCA services, SCA references and SCA properties from EJB3 business interfaces, Remote EJB3 references and EnvEntries.
+- Only introspect the fault type if the JAXWS interface processor hasn't figured out the databinding
+- Produce xsi:type for local elements
+- Add contribution-jee to the build to avoid break
+- Removing obsolete schema file for binding-gdata
+- Removing @author per Apache best practices
+- Adding support for Jaas authentication policy to component services
+- Removing system.out debug message
+- Wrapping the invocation with a message, in order to pass extra information during invocation
+- Removing @author per Apache best practices
+- Properly handling business/runtime exception with new invocation method
+- Small method name change
+- Removing unused imports
+- Adding support for LDAP Realm authentication policy
+- Adding support for LDAP Realm authentication policy
+- Fixes for TUSCANY-2914
+- Fixes for TUSCANY-2922
+- Fixes for TUSCANY-2922
+- TUSCANY-2923 Stest code ASM_0024 - ASM_0043
+- TUSCANY-2926 Stest code invalid ignore tag
+- Use the JavaEE extensions to compute SCA services, SCA references and SCA properties from EJB3 business interfaces, Remote EJB3 references and EnvEntries.
+- TUSCANY-2932 Throw org.apache.tuscany.sca.data.collection.NotFoundException on 404 errors if AtomReferenceBindingProvider.supportsFeedEntries() is false
+- TUSCANY-2931 - Start of test for different in request and response wire formats. Infrastructure not working properly just yet.
+- Do not throw exception if the jar is not an EJB jar.
+- TUSCANY-2932 Correctly handle NotFoundException as a 404 in AtomBindingListenerServlet
+- Adding module to the build.
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- TUSCANY-2933 - Runtime changes to properly define widget functions in it's own namespace
+- TUSCANY-2933 - Updating photo-gallery sample to use widget Java Script fuctions in the new tuscany.sca namespace
+- TUSCANY-2933 - Updating store sample to use widget Java Script fuctions in the new tuscany.sca namespace
+- TUSCANY-2933 - Updating store samples to use widget Java Script fuctions in the new tuscany.sca namespace
+- TUSCANY-2933 - Updating domain manager ui to use widget Java Script fuctions in the new tuscany.sca namespace
+- TUSCANY-2933 - Updating store tutorial to use widget Java Script fuctions in the new tuscany.sca namespace
+- TUSCANY-2933 - Updating widget test html to use widget Java Script fuctions in the new tuscany.sca namespace
+- Store scenario using widget packaged as a webapp
+- Adding store-webapp to build
+- TUSCANY-2838 - Updating implementation widget to properly register component java script in a webapp environment
+- TUSCANY-2838 - Missing files required by implementation widget to properly register component java script in a webapp environment
+- Update scadomain to support passing in the default port in the domain uri
+- TUSCANY-2936 Extension point API for Java EE
+- Commenting out since an issue in openejb is resulting in problems with WAR processing.
+- Set some svn ignores
+- TUSCANY-2936 Extension point API for Java EE
+- Minor formatting
+- Adding provided binding URI to avoid issues when service is deployed in a webapp environment
+- Minor formatting and removing unused imports
+- Adding test case to test atom feed reference using generic collection interface
+- Move JAAS service policy provider from binding wire to the operation wire
+- add some ignores
+- add some ignores
+- Set svn ignores
+- TUSCANY-2918, Update jms support so that the service listener can be pluggable via host-jms
+- Move fault type introspection to the the fault mapper
+- Fixes for TUSCANY-2906
+- Fixes for TUSCANY-2941
+- Don't fall over if there is no introspector, e.g. if contribution-jee-impl is not loaded
+- TUSCANY-2931 - allow separate request and response wire formats in binding.jms. The tuscany binding.jms XSD has been extended to allow a response wireFormat element to be specified. The knock on effect of all this is that the Operation interface has been changed to allow input and output wrapper info to be held separately. Also Interface has some new operations. There are changes across the code base to take account of this interface change.
+- Add a namespace to the missing component type composite
+- Remove these files as they are no longer required. Replaced by RRB... versions.
+- Example of how we could describe what exceptions are expected in stests
+- Take testcase out of build as its now broken, see TUSCANY-2942
+- Add jira number
+- Take testcase out of build as its broken, see TUSCANY-2943
+- Take store-test out of build as its broken, see TUSCANY-2944
+- Remove old "getWireFormatInterfaceContract" operation
+- Take fialing tests out of build, see TUSCANY-2945
+- TUSCANY-2934 - wire up the wire format writers
+- TUSCANY-2937 - Renaming FeedAggregatorTestCase and adding @Ignore on failing tests as described in jira
+- TUSCANY-2837 - Adding Javascript extension points to be used by implementtion.widget and any web related extensions that have Javascript proxy dependencies
+- TUSCANY-2837 - Updates to start using Javascript extension points to generate js client proxies
+- TUSCANY-2837 - Atom Binding Javascript extension point implementation
+- TUSCANY-2837 - JSONRPC Binding Javascript extension point implementation
+- TUSCANY-2837 - Updating sample app dependencies to add javascript dependencies for atom and jsonrpc bindings
+- TUSCANY-2837 - Adding new modules to build
+- TUSCANY-2837 - Adding javadoc comments to JavascriptProxyFactory
+- TUSCANY-2837 - Extending Javascript extension to provide the js proxy client file
+- Removing duplicated file that is already available in main/resources
+- TUSCANY-2837 - Adding new js dependencies
+- TUSCANY-2837 - Adding new js dependencies
+- TUSCANY-2946, take failing test out of build
+- TUSCANY-2947, take itest out of build as its failing
+- TUSCANY-2948, take jms-format test out of build for now
+- TUSCANY-2944 don't raise NPE if the component type model cannot be determined
+- TUSCANY-2950 enclose etags in speech marks
+- TUSCANY-2937 uncomment ignored tests as underlying etag issue is fixed under TUSCANY-2950.
+- Workaround the jaxws-api maven issue (merged from 2.x)
+- TUSCANY-2944 - Enable tests as recent changes from slaws in revision #759149 fixes the problems we were seeing.
+- TUSCANY-2931 - update operation matching to be based on operation name. Add a complex type based interface back into to the test case.
+- Process SCA Property and Reference annotations.
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- Reversing the changes committed accidentally in the last commit.
+- Put back the TUSCANY-2946 failing test into the build to see if anyone else gets it
+- Fixes for TUSCANY-2945, 2947, 2948
+- Fixes for TUSCANY-2945, 2947, 2948
+- Fixes for TUSCANY-2945, 2947, 2948
+- Added the missing JSP spec dependency.
+- Set svn:ignore
+- Set svn:ignore
+- Make sure SCA domain is closed
+- Move the componentType files into the resource folder so that maven copy them into the target/classes
+- Removing obsolet place holder module
+- Removing eclipse/maven generated files
+- TUSCANY-2878 - New extensions to generate javascript proxies when using dojo
+- TUSCANY-2878 - Module responsible to add register dojo toolkit in web environment under '/dojo'. This is usefull in embedded environment
+- TUSCANY-2878 - JavaScript Generator extension point. Used by implementation.widget to allow multiple implementations of js generator (e.g. tuscany specific and dojo based)
+- TUSCANY-2878 - Changes to support new JavaScript Generator extension point and new generators for tuscany specific scripts and dojo toolkit
+- TUSCANY-2878 - New store sample app using dojo version of implementation widget
+- TUSCANY-2878 - Adding new modules and sample apps to build
+- TUSCANY-2878 - Removing obsolete file
+- TUSCANY-2878 - Adjusting modules to add implementation-widget-runtime-tuscany as dependency
+- TUSCANY-2878 - Adjusting modules to add implementation-widget-runtime-tuscany as dependency
+- TUSCANY-2878 - Moving tests to implementation-widget-runtime-tuscany and minor pom adjusts
+- TUSCANY-2955 SCA annotation processing for impl.web, impl.ejb, impl.jee
+- Moving Erlang binding to 1.x branch
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- TUSCANY-2878 - Missed module activator files from last committs
+- TUSCANY-2878 - Renaming resource bundle used by monitor to match name expected in code
+- svn propset svn:ignore
+- svn propset svn:ignore
+- svn propset svn:ignore
+- TUSCANY-2878 - Missed dojo javascript generator from last commit
+- TUSCANY-2878 - Missed dojo javascript extension poing to atom binding
+- TUSCANY-2878 - Missed dojo javascript extension poing to jsonrpc binding
+- TUSCANY-2956 Java EE Archive introspection
+- TUSCANY-2878 - Removing unnecessary .Service from generated dojo jsonrpc javascript proxy
+- TUSCANY-2878 - Moving dojo.requires to before store.js and fixing invocation of services to follow dojo pattern
+- TUSCANY-2878 - Moving dojo resources to it's own folder to avoid issues with clean target that was removing other non-dojo resources.
+- TUSCANY-2956 Java EE Archive introspection
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- Added configurable thread pools, fixed problem with ReferenceServiceTestCase.testMultipleMethod() test case, added writing to binding processor - problems with testing
+- TUSCANY-2935 Integration tests for Java EE contribution processing
+- Minor typo on method declaration
+- Renaming core-web-xxx modules to web-javascript-xxx modules
+- Refactoring javascript extension points packages to follow the same naming pattern used by it's modules.
+- Fix minor copy error in input vs. output var name
+- Set svn:ignore and update the module names
+- Make the openejb version consistent and fix the NPE & UnsupportedModuleType
+- Comment out the test case due to TUSCANY-2957
+- Make sure the outputWrapperStyle is set
+- TUSCANY-2952, fix jms listener to work in weblogic 10.x
+- Copy zip/folder nested jar support change from 2.x to 1.x
+- Added a configuration to work around http://jira.codehaus.org/browse/MECLIPSE-544
+- TUSCANY-2862 - Fixing issues when calculating contribution location and provided composite had spaces
+- TUSCANY-2862 - Fixing URI issues when processing jar contributions that had artifacts with space on it's name
+- TUSCANY-2862 - Further changes to handled folder contributions that have artifacts with space in the name
+- Fix TUSCANY-2957
+- Add remotable check to avoid perf penality from Holder processing for local calls
+- TUSCANY-2938 - Fixing how we calculate request path based on contextPath and ServletPath to make operations working in both embedded and webapp hosted environment
+- TUSCANY-2871 - Providing better exception when feed entry is not supported
+- Refacroting testcase to use same package pattern for the module
+- Removing empty directory
+- Removing empty directory
+- TUSCANY-2958 JEEImplementationImpl, WebImplementationImpl and EJBImplementationImpl need to implement PolicySetAttachPoint
+- General improvements for messaging, fixed some issues regarding communication with real Erlang nodes
+- Change to use port 8085 as 8081 has a conflict on the continuum server
+- Change JMS server port to try to avoid conflict on continuum server
+- Add a println of the problem to see what it says when running on the continuum machine as the test is assing for me
+- Exclude the module that has conflicting classes with the JDK
+- Separate the contribution JEE sample scenarios from the contribution JEE itests so we can see the source for the samples and more easily mix and match to construct the various combinations required. Add a new test relating to a single sample scenario to explore the problem with classloading where the JEE archive classloader is not available during contribution resolution.
+- Set a bunch of svn ignores
+- Messaging improvements
+- TUSCANY-2851, start of an itest for exceptions in Java component initilization
+- Add more complete test for the various lifecycle exceptions
+- TUSCANY-2851, fix exceptions during init processing of java components to call destroy
+- Use explicit version to fix continuum build
+- Use explicit verison to fix continuum build
+- Change to port 8085 to avoid conflict on continuum build
+- Change some jms ports to try to fix continuum build conflicts
+- Change some jms ports to try to fix continuum build conflicts
+- Comment out tests which don't work on continuum build machine
+- TUSCANY-2972 - Sample code for fixing up classloaders for JEE archives. No where near done yet but allows us to experiment and explore the problems.
+- Added support for Erlang Atoms
+- Try another port for the continuum machine build
+- Comment out the http service as its not used by the test an seems to ause a problem in continuum
+- Bump up 1.x trunk version to 1.6-SNAPSHOT
+- General improvements
+- TUSCANY-2976: Apply patch from Greg Dritschler to Remove default 'ConnectionFactory' in JMSBinding model
+- TUSCANY-2972 instigate contribution type specific class loading to allow the JEE classloader to be used independently of jar, zip, dir classloading schemes
+- Start adding some more JEE samples. No guarantee that these actually work yet as I haven't run them in a JEE runtime but a place to start.
+- Start of a testcase which show implemntation.jee pointing at an ear is processed correctly
+- Add test dependency
+- It should be EAR instead of EJB.
+- Type should be WAR instead of EAR.
+- Set the EJB classloader in EJBModuleInfo.
+- Move testcase to an itest
+- New itest for jee external ear's
+- Set svn ignores
+- Update to introspect external ear archives
+- Rename testcase as it works now (as long as you've the NPE fixed openejb jar)
+- Add exclusion to avoid the conflicting jdk classes from felix
+- Add "Extensible" support for the ContributionMetaData/Contribution/Import/Export models (TUSCANY-2983)
+- TUSCANY-2968 - Creating a new http binding based on current tuscany one
+- Removing unecessary @Ignore
+- TUSCANY-2968 - Adding new binding processor and making necessary adjustment to move to spec namespace
+- Adding gdata dependencies to LICENSE file (copied from 1.4 release)
+- Updating pom version to reflect changes made in trunk in preparation for release
+- TUSCANY-2968 - Adding module to handle json-rpc wireformat and initial support for it
+- Add an external ear modelresolver approach to the jee itest
+- Improve the handling of INOUT and OUT parameters using JAX-WS Holder
+- Remove bundle module from the pom.xml as it's now moved
+- Put back distribution/bundle that was inadvertently removed in r766999
+- Put back distribution\bundle into the build
+- TUSCANY-2930 main part of separating wireFormat.jmsdefault out from wireFormat.jmsTextXML. I've spotted a few more things that need fixing but this basic functionality passes all of our current JMS tests and now better matched what the specification says about default format.
+- TUSCANY-2930 extend default format test for the chase where default is specified on reference but not on the service
+- Move the JAX-WS holder testing logic to interface-java-jaxws
+- TUSCANY-2986 - move the callback processing into a separate interceptor to allow other operation selectors to use it. Don't have any others just yet but about to add another one.
+- TUSCANY-2987 code to make nativeOperation based operation selection work and add new operation selector (jmsUser) that allows you to specify what JMS message property holds the operation name. No test cases yet.
+- TUSCANY-2977 determine implementation.jee component type from application composite if one is available
+- o Updated artifactId to the correct (long) one.
+- TUSCANY-2987, TUSCANY-2964. Rename operation selector that allows the user to specify which message property holds the operation name. Add tests cases for this and the default selector. Rename default selector to be all lowers case (it's still in the Tuscany namespace though)
+- TUSCANY-2965 - add a jmsBytesXML wireFormat analogous to jmsTextXML
+- TUSCANY-2966 - reset bytes message after read in operation selector so that following wire format can re-read bytes if required.
+- Update the tuscany part of the JMS binding schema to take account of recent wireFormat and opertionSelector changes. These schema type are not wired into the binding.jms schema at the moment (we rely on anys) but it's useful to keep track of the shape of these elements.
+- Add some ignores
+- TUSCANY-2626 - add EndpointReference back into the binding.ws schema. This is not the wsa:EnpointReference though. To get this to work I have had EndpointReference goes in the target namespace. The code to read EndpointReference still reads wsa:EndpointReference so this shouldn't break anyone already using that but at least it gives the reader an idea about what can validly go in the schema.
+- Fix the ArrayOutofBoundException that causes the hang of itest/helloworld-bpel
+- set svn:ignore
+- Make sure the default mode is set to INOUT if the type is Holder.class
+- TUSCANY-2626 add file missed in previous commit for this JIRA
+- The war file generated by the jee sample project has a long name. Updating the url accordingly.
+- Code update to support external EAR has broken this test. Ignoring the test for now.
+- TUSCANY-2953 Fix sca.tld in branches-1.x
+- Uncommenting contribution-jee itest.
+- TUSCANY-2997 - Removing unecessary load of dojo base component
+- TUSCANY-2998 - Fixing sample usage of dojo based JavaScript proxies to avoid issues when invoking shopingCart service (e.g loading shoopingCart contents)
+- TUSCANY-2999 - Fixing property initialization in implementation widget
+- TUSCANY-2968 - Adding model and processors for JSONRPC Operation Selector
+- TUSCANY-2968 - Starting to bring up JSON RPC runtime pieces as wire format for binding.http
+- Add an itest for setting the JMS Time-To-Live header
+- Remove unused xsds
+- Add exclusion to avoid the conflicting jdk classes from felix
+- Make sure the checked exception is tested against the target operation
+- MOving data-engine-helper to contrib
+- Removing data-engine-helper from pom as it was moved to contrib
+- Fix for TUSCANY-3000
+- Add a apace for the error message
+- Fix the clone()
+- TUSCANY-2996 - Add support for wrapSingle attribute that, when set true, ensures that single parameters are wrapped in an array on the wire. When set false single parameters will not be wrapped on the wire. Multiple parameters will always be wrapped.
+- Add ignore
+- TUSCANY-2965 - add fault handling code for wireFormat.bytesXML
+- TUSCANY-2993 Fix global variable handling that was causing store-dojo to fail with internet explorer
+- Move the Holder logic into JAXWS interface processor
+- Start to add contribution level SDO type registration
+- Set svn:ignore
+- Add annotation dependency as the provided scope is not transitive
+- Update to cargo plugin 1.0
+- Refactor the data transformation and copy logic into Mediator utility
+- Add jee contribution samples to the build as the contribution-jee itest depends on it
+- TUSCANY-3002: fix writeStartElement calls in JMSBindingProcessor do not pass namespace
+- Clean up imports
+- TUSCANY-3006 - Disabling failing test cases
+- TUSCANY-2968 - Updating binding-http schema and moving wireFormat and operationSelector to tuscany-sca-core.xsd to be sharable
+- TUSCANY-2968 - Changing binding to tuscany namespace and other small updates
+- TUSCANY-2968 - Renaming new binding.http module to avoid confusion with the oasis draft, as we are not really implementing the whole spec but just following the wireFormat and operationSelector options implemented in binding.jms
+- Double the time the test waits for the time to live to be set into the initial context as it's failing on my machine with the existing timeout.
+- TUSCANY-2978 - Add some more sample archives based on the scenarios here http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Java+EE+Integration
+- TUSCANY-2978 - Add test code to exercise new JEE sample archives including code to show how to process an archive that appears outside of the contribution that references it. See TestExternalEarModelResolver.java. Some jee processing changes were required to make this work.
+- TUSCANY-3008 disable reference test in testContributeEAR_Enhanced16 until this problem is fixed
+- Remove the unused mediator lookup
+- TUSCANY-2968 - JSONRPC operation selector
+- TUSCANY-2968 - Moving unit tests to iTest to avoid circular references
+- TUSCANY-2968 - Further changes trying to add the json-rpc wireformat and operation selector interceptors to the invocation chain
+- TUSCANY-2968 - Minor update to make serice providers follow the same implementation pattern
+- Set context for mediateFault as well.
+- Fixing NPE when no operation provided when creating invoker
+- TUSCANY-2968 - Discovering and adding wire format and operation selector interceptors via extension point, but inside binding provider
+- TUSCANY-2968 - JSONRPC invocation using operation selector and wire formats working end to end
+- TUSCANY-2968 - Enabling test that invoke remote jsonrpc services using the new operation selector/wire format implementation
+- TUSCANY-2968 - Adding databinding dependencies to integration tests
+- TUSCANY-2968 - Setting JSON dataBinding on service interface contract
+- TUSCANY-2968 - Enabling more tests that are currently passing
+- Add host-jetty dependency as binging-http needs are servlet host. For some reason this test works OK in Eclipse but doesn't work in Maven. So eclipse is picking up the jetty dependency from somewhere else. Ass some ignores also.
+- Tidy comment
+- TUSCANY-3005 - Take account of the case where there are either no input parameters or a void return type (or both). Thanks for the patch Kaushik.
+- TUSCANY-2968 - Fixing data binding related issues to properly transform to/from json format as needed
+- USCANY-2968 - Enabling more tests that are currently passing
+- TUSCANY-2968 - Fixing exception handling issues to properly report exceptions as json error responses
+- USCANY-2968 - Enabling more tests that are currently passing
+- Small clean up and formatting on tests
+- TUSCANY-2968 - Fixing NPE with pure http binding
+- Removing unwanted files, got in accidentaly
+- Renaming Spring modules as old
+- Refactoring Spring module
+- moving spring-runtime to spring-sca
+- Refactoring Spring Module
+- Changing Spring Dependencies
+- Refactoring Spring Module
+- Refactoring Spring Module
+- TUSCANY-2959 - Store-android patch from Sanni Lookman
+- Adding missing Apache headers to store-android
+- Restoring catalog activity as backup/reference
+- TUSCANY-2900 - Add code to generate JMS binding and service/port to generated wsdl. Add itest to explore the different ways of configuring generated WSDL.
+- TUSCANY-3011 correct JMS binding XSD to make OperationalProperties/Headers optional as per the OSOA spec
+- Performance enhancement to avoid processing the deployable composite twice when starting a node
+- Add a new soap/jms transport module copied from the Apache WS Commons transports but with the code backported to work with Axis2 1.4.1
+- Merging changes from binding-http-new that introduces support to wire format and operation selector to the main binding-http.
+- Fix for TUSCANY-2962
+- Leverage optimization from the Axiom 1.2.7
+- Remove unused classes
+- Merging HTTPBindingProcessor from binding-http-new that introduces support to wire format and operation selector to the main binding-http.
+- Renaming binding-http-new-jsonrpc* to binding-http-jsonrpc*
+- Adjusting pom with recent module name refactoring/changes
+- Removing obsolete modules that have been merged or renamed.
+- Fix for TUSCANY-3017
+- Abandon trying to use the new Axis2 JMS transport for now as its proving too messy tryingto backport it to the 1.4.1 release. Now trying a new approach which modifies the JMS transport from Axis2 1.4.1
+- Start bringing up Tuscany version of JMS transport so the setMessageListener not allowed in a JEE container can be fixed
+- Add support for using Tuscany threads instead on setMessageListener in a JEE container environment
+- Fix NPE bug in TUSCANY-2962 fix
+- TUSCANY-2967 Fix up just jmsBytes wire format to return exceptions as bytes to see if this is what we want
+- TUSCANY-3031 Ensure that JMS wire formats that don't required a data transformation work when interface.wsdl is used. Use the component type interface rather than the service
+- A tool to save to disc the WSDL for each service, with binding.ws, within all of the deployable composites in a specified contribution
+- Exclude work session.ser from build
+- Add missing license headers
+- Add missing license headers
+- Rename tests and add license header
+- Add missing license header
+- Add missing license header
+- Exclude cruft from bin distro
+- Excelude multiple sca bindings from bundle build
+- Exclude bouncycastle
+- Update legal files
+- Remove provided csope from spring dependencies
+- Add spring runtime module
+- Mereg bouncy castle excludes from 1.5 to 1.x
+- Exclude dojo files
+- TUSCANY-3030 if the fault exception mapper is null try getting it from the registry before returning the fault unmapped. This takes care of the case there the mapper is null just because the JavaRuntimeModuleActivator is started before the DatabindingModuleActivator
+- TUSCANY-3032 - fix binding.ejb schema so that ejb-link-name is a string not an NCName
+- Correct typo in exclude
+- TUSCANY-3025 - Appying Sanni Lookman patch plus small fixes to make it run successfully
+- TUSCANY-2967 - to aid investigation of possible exception processing refactoring enhance format tests to test checked and unchecked exceptions. Also add a wf.jmsText test.
+- Do BytesMessage.reset() on BytesMP, DefaultMP to be consistent across wire formats.
+- Apply patch for TUSCANY-3033 from Pradeep. Thanks.
+- Removing obsolete FIXME tags, as exceptions are handled ok on wireFormat interceptor already
+- Reporting fault message with exception in json representation, when jsonrpc operation selector interceptor can't parse json request
+- Updating java doc for HTTP JSON-RPC wireformat/operation selector extensions
+- Properly handle SMD requests in JSON-RPC wire format/operation selector
+- Reverting changes as this would make sample stop working due to TUSCANY-3042
+- Add jms host to bundle to fix running jms samples
+
+Changes With Apache Tuscany SCA 1.4 December 2008
+==================================================
+
+- Features and/or Enhancements
+
+Core
+ * Enhancements to Spring integration
+ o Support for Spring version 2.5.5
+ o Spring Schema location changed to http://www.osoa.org/xmlns/sca/1.0/spring-sca.xsd
+ o Support for Implementation Policies to Spring Components
+ o Support for basic SCA annotations with Spring beans
+ o Improved user guide documentation
+ * Axis2 Runtime
+ o Support for Axis2 version 1.4.1
+ o Support for MTOM message optimization
+ * JMS
+ o Support for SCA callbacks with JMS binding
+ o Support for new subscription Header element from latest WD3 spec draft
+ o Support for @requestConnection / @responseConnection
+ o Improved user guide documentation
+ * Tracing
+ o Support for Aspect Oriented Tracing
+
+Web 2.0 Extensions
+ * ATOM Binding
+ o Support for eTags, last-modified headers, complete support for location header
+ o Support for streaming postMedia and putMedia
+ o Support for negotiated content types
+ * HTTP Binding
+ o Support for eTags
+
+Other Extensions
+ * Corba Binding (GSoC)
+ * GData Binding (GSoC)
+
+Tools
+ * Tuscany Eclipse Plugins enhancements to be compatible with new Eclipse Ganymede release
+
+Samples/Tutorial/Demos
+ * Improved simple-bigbank-spring samples to demonstrate various SCA bindings with Spring
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2585 Support for <import/> tag in Spring Application Context
+ * TUSCANY-2623 Atom binding JavaScript client needs model to XML serialization
+ * TUSCANY-2634 Implementation Policies for implementation.spring
+ * TUSCANY-2654 Support for SCA Annotations in Spring Implementation
+ * TUSCANY-2655 Create itest for SCA annotations with Spring Implementation
+ * TUSCANY-2656 More improvement to the spring itest
+ * TUSCANY-2665 Issue noticed in itest-contribution while starting the CalculatorClient
+ * TUSCANY-2666 Improvement in Spring BigBank Sample test
+ * TUSCANY-2672 Compilation Error Building SCA CORBA Binding Runtime
+ * TUSCANY-2455 Exception not thrown on duplicate component names within a composite
+ * TUSCANY-2550 Ensure Spring Implementation works with binding.sca/jsonrpc/rss/atom
+ * TUSCANY-2549 Documentation on Spring Implementation for SCA Java User Guide
+ * TUSCANY-2613 Upgrade Implementation Spring version from 2.0.8 to 2.5.5
+ * TUSCANY-2641 Enhancements to Tuscany Logging and tracing
+ * TUSCANY-2567 Support for streaming postMedia and putMedia in Atom binding
+ * TUSCANY-2537 Demonstrate Atom Binding end to end caching (ETag, Last-modified use) in
+ * TUSCANY-2504 Atom binding support for negotiated content types
+ * TUSCANY-2516 HTTP binding should support etag and if-modified headers
+ * TUSCANY-2597 Generation of AtomPub workspace/service document
+ * TUSCANY-2477 Atom binding support for eTags, last-modified header
+ * TUSCANY-2487 Test Cases for different data type supported by JSONRPC binding
+ * TUSCANY-2517, TUSCANY-2520, TUSCANY-2521, TUSCANY-2522 Improvements in spring big bank sample
+
+Changes With Apache Tuscany SCA 1.3.3 Xxxxxxx 2008
+==================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2635 Pool stateless-scoped Java impl instances
+
+
+Changes With Apache Tuscany SCA 1.3.2 October 2008
+==================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2628 Fix some other file license headers that should refer to the OSOA license
+ * TUSCANY-2620 Fix license header for sca.tld
+ * TUSCANY-2618 Add required attribute elements to sca.tld
+ * TUSCANY-2615 Fix NPE in databinding and a nested exception test in vtests
+ * TUSCANY-2614 Fix missing headers reported by RAT during release
+ * TUSCANY-2598 Patch to support zip protocol type
+ * TUSCANY-2592 Reduce size of demo/mortgage-loanapproval doc
+ * TUSCANY-2591 Invalid JMS Message Property in binding.jms
+ * TUSCANY-2590 Pool JAXB marshaller/unmarshallers for a given JAXBContext
+ * TUSCANY-2587 Inconsistent service naming in promoted service scenarios
+ * TUSCANY-2561 Soap intents are lower case while the policy framework says that they should be upper case
+ * TUSCANY-2538 Tuscany object model does not handle unknown content in composite files
+ * TUSCANY-2531 Problems with generated wsdl when using non service package
+ * TUSCANY-2513 Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation
+ * TUSCANY-2501 InterfaceContract is not established on reference when it's not calculated by introspection
+ * TUSCANY-2463 Provide capability for handling attribute extensions to standard SCA elements in composite file
+ * TUSCANY-2398 Problem with using interface.java on reference when using interface.wsdl in service with a doc/lit/bare wsdl
+
+Changes With Apache Tuscany SCA 1.3.1 August 2008
+=================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2539 File handle on composite affecting behaviour of tuscany deployments in websphere.
+ * TUSCANY-2535 Tuscany dosn't run if install on a WebSphere server that has itself been installed in a directory with a space in the name
+ * TUSCANY-2534 WebSphere issue java.lang.ClassCastException
+ * TUSCANY-2531 Problems with generated wsdl when using non service package
+ * TUSCANY-2519 "throws Exception" causes failure in JAXB type generation
+ * TUSCANY-2514 tuscany-host-{tomcat,jetty} and jsr181-api should be optional dependencies for binding.ws clients
+ * TUSCANY-2505 Problem in case: start with DLW wsdl, generate Java w/ wsimport, throw away WSDL and use <intf.java>, when wrapper elem used named type (not anonymous)
+ * TUSCANY-2389 null elements in Object array not getting passed over binding.ws
+
+
+Changes With Apache Tuscany SCA 1.3 August 2008
+===============================================
+
+- Features and/or Enhancements
+
+ We have graduated as a top level Apache project. The incubating disclaimer has been removed
+ and the artifact names and version no longer containg the "-incubating" string.
+
+ * Core
+ - More improvements to the Distributed Domain story
+ - Old domain and node code has been removed
+ - Improved runtime Java2WSDL processing
+ - No longer relies on Axis code
+ - Support for core validation monitoring
+ - A pluggable monitor can be used to trap and process validation messages
+ - Performance improvements
+ - Java 2 security enablement across the code base
+ * Extensions
+ - Validation monitoring added to extension processors
+ - Databinding improvements
+ - JSR250 annotation support
+ - OSGi support improvements
+ - Better BPEL support
+ * Tools
+ - No significant changes
+ * Samples/Tutorial/Demos
+ - No significant changes
+ * Testing
+ - more spec verifaction tests
+ - validation itests
+
+Changes With Apache Tuscany SCA 1.2.1 (incubating) June 2008
+============================================================
+
+Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2304 SCA client Hang Forver after getting exceptions from remote web service
+
+
+Changes With Apache Tuscany SCA 1.2 (incubating) April 2008
+===========================================================
+
+- Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-2027
+ * TUSCANY-1999
+ * TUSCANY-2037
+ * TUSCANY-2034
+ * TUSCANY-2038
+ * TUSCANY-2043
+ * TUSCANY-2046
+ * TUSCANY-2047
+ * TUSCANY-2028
+ * TUSCANY-1873
+ * TUSCANY-2049
+ * TUSCANY-2035
+ * TUSCANY-1206
+ * TUSCANY-2036
+ * TUSCANY-1771
+ * TUSCANY-2013
+ * TUSCANY-1926
+ * TUSCANY-1917
+ * TUSCANY-1949
+ * TUSCANY-1941
+ * TUSCANY-2045
+ * TUSCANY-2057
+ * TUSCANY-2055
+ * TUSCANY-2056
+ * TUSCANY-2072
+ * TUSCANY-2047
+ * TUSCANY-2073
+ * TUSCANY-1977
+ * TUSCANY-2075
+ * TUSCANY-1894
+ * TUSCANY-2079
+ * TUSCANY-2078
+ * TUSCANY-2080
+ * TUSCANY-2068
+ * TUSCANY-1950
+ * TUSCANY-2077
+ * TUSCANY-2056
+ * TUSCANY-2088
+ * TUSCANY-2086
+ * TUSCANY-2094
+ * TUSCANY-2106
+
+ Features and/or Enhancements
+
+ * Core
+ - Interceptor Enhancements
+ - Phase-based interceptor ordering to allow contribution of new interceptors and also define the order in witch they should be invoked
+ - Pass-by-reference SPI to allow interceptors to indicate if they support pass-by-reference
+ - PolicyProvider SPIs to allow extensions to plugin policy interceptors
+ - Support for JAXWS annotations and mapping of faults to Java exceptions according to JAXWS specification
+ - Improvement of contribution service to allow it to be used outside of the runtime environment
+ - Support for Contribution Import/Export resource
+ - Enhanced Distributed Domain story using Workspace
+ - Implementation of a SCA domain allowing a system administrator to manage contributions, composites and sca nodes that run these composites
+ - Set of core services providing management capabilities
+ - Administration web interface
+ - This is a work in progress and you can see it in action in samples/calculator-distributed. Other samples that use distributed operation are yet to move over to the workspace.
+ - Enhanced support for SCA Policy spec
+ - Ability to apply external policy definitions to a SCA composition
+ - Ability to spread policy definitions to multiple definitions.xml files available across the sca domain
+ - Bug fixes
+ - Improvements of http binding to support servlet components
+ - Enable Tuscany to run inside an OSGi runtime
+
+ * Web 2.0 Extensions
+ - Enhancements to implementation.widget (support for properties)
+ - New atom binding based on Apache Abdera
+ - Refactoring of rss-rome binding
+ * Other Extensions
+ - Binding JMS
+ - greatly simplified the use of the JMS binding, support locating JMS resources from JNDI, and better compliance with the SCA JMS binding spec
+ - see the doc page for more details: http://incubator.apache.org/tuscany/sca-java-bindingjms.html
+ - Enhancements to Binding RMI
+ - Support shared RMI registry and use 999x as the ports in test case to avoid 1099 conflict
+ - Enhancements to Groovy extension
+ - Support for 'native' groovy classes
+ - Enhancements to OSGi bundle contributions
+ - Support Bundle URLs to be added as contributions
+
+ * Tools
+ - Eclipse plugin providing a Tuscany runtime Library and Tuscany launcher in Eclipse environment
+ - An updatesite is also available to facilitate the plugin installation using the Eclipse update manager
+
+ * Samples/Tutorial/Demos
+ - calculator-distributed migrated to use new Tuscany Distributed Workspace
+ - sample-calculator-ws-secure-webapp
+ - sample-helloworld-jms-webapp
+ - new jms samples
+ - improve bigbank demo to include support for policies
+ - tutorial store changes
+ - use of import/export
+ - development of contribution without requiring dependencies on the Tuscany runtime
+ - usage of new sca domain infrastructure
+
+ * Testing
+ - Web Container Testing Framework integrated with (Tomcat, Jetty, Geronimo and Websphere)
+
+
+Changes With Apache Tuscany SCA 1.1 (incubating) January 2008
+===============================================================
+
+- Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-1939
+ * TUSCANY-1914
+ * TUSCANY-1854
+ * TUSCANY-1931
+ * TUSCANY-1547
+ * TUSCANY-1909
+ * TUSCANY-1919
+ * TUSCANY-1930
+ * TUSCANY-1806
+ * TUSCANY-1804
+ * TUSCANY-1916
+ * TUSCANY-1913
+ * TUSCANY-1834
+ * TUSCANY-1857
+ * TUSCANY-1687
+ * TUSCANY-1801
+ * TUSCANY-1742
+ * TUSCANY-1762
+ * TUSCANY-1945
+ * TUSCANY-1595
+ * TUSCANY-1594
+ * TUSCANY-1849
+ * TUSCANY-1836
+ * TUSCANY-1934
+ * TUSCANY-1902
+ * TUSCANY-1608
+ * TUSCANY-1943
+ * TUSCANY-1896
+ * TUSCANY-1626
+ * TUSCANY-1797
+ * TUSCANY-1601
+ * TUSCANY-1415
+
+- Better JMS support
+ * binding.jms supporting point to point text based messaging only
+ * New SOAP/JMS sample (helloworld-ws-reference/service-jms)
+
+- Improvements in PolicyFramework Support
+ * Support for policy specifications on operation elements in a composite definition
+ * Separate sample (calculator-implementation-policies) to demonstrate use of Implementation Policies
+ (uses logging and JAAS Authentication)
+
+- Modeling of client side java script components
+ * See implementation.widget
+
+- Evolving support for doman API suggested by assembly spec including a standalone node and nodes running
+ connected together in a domain. This is still experimental.
+
+- Class loading and OSGI improvements
+ * Enable Tuscany to be run in a multi-classloader environment including inside OSGi. By default,
+ Tuscany continues to run using a single CLASSPATH-based classloader.
+ * Contributions no longer need to be in the CLASSPATH. All import/export dependencies across contributions should be
+ explicitly specified (as described in the spec).
+
+- JAXB based POJO transformations
+
+Changes With Apache Tuscany SCA 1.0.1 (incubating) November 2007
+================================================================
+
+The Tuscany SCA Java 1.0.1 is mainly a bug-fix release. It also comes with some improvements as listed below.
+
+- Fix the following JIRA issues (http://issues.apache.org/jira/browse/TUSCANY):
+ * TUSCANY-1848
+ * TUSCANY-1857
+ * TUSCANY-1859
+ * TUSCANY-1801
+ * TUSCANY-1823
+ * TUSCANY-1839
+ * TUSCANY-1814
+ * TUSCANY-1818
+ * TUSCANY-1834
+ * TUSCANY-1637
+ * TUSCANY-1826
+ * TUSCANY-1823
+ * TUSCANY-1819
+ * TUSCANY-1821
+ * TUSCANY-1822
+ * TUSCANY-1806
+ * TUSCANY-1808
+ * TUSCANY-1756
+ * TUSCANY-1757
+
+- Fix build issues with Maven 2.0.7 and JDK 6
+
+- Reduce memory consumption for WSDLs that import large XSDs
+
+- Add more logging statements for better servicibility
+
+- Add an extension point to allow extensions to plug-in extension schemas.
+
+- Add a demo application to showcase XML integration story
+
+- Improve in databinding framework
+ * Add support for JSON Databindings and other refactoring
+ * Set databinding for introspected data type and enhance the checking of wrapper style
+ * Improve the tree-based XMLStreamReader and convert Bean & DOM to use this approach
+ * Add a tree-iterator based XMLStreamReader base impl
+ * Add default element info to java interface
+ * Rename Interface.setDefaultDataBinding to resetDataBinding
+
+- Limit the method injection to setters and allow the setter annotation to override field annotation
+
+- Evolving support in Intent and Policy handling
+ * Add support for policies in implementation
+ * Fix the algorithm for macthing policySets defined on bindings for the wire
+ * Add policy intent for implementation.java
+ * Extend java implementation type to recognize and apply policies, adding util support for this in Policy module
+ * Add policy module for logging
+
+- Evolving development in the SCA Domain/Node
+
+- Update NOTICE files with missing dependencies
+
+
+Changes With Apache Tuscany SCA 1.0 (incubating) September 2007
+===============================================================
+
+- Tuscany Java SCA now implements V1.0 of the core SCA
+ specifications
+ SCA Assembly Model V1.0
+ SCA Java Common Annotations and APIs V1.0
+ SCA Java Component Implementation V1.0
+ SCA Web Services Binding V1.0
+ Including callbacks, conversations and callable references
+
+
+- Support for ws-security configurable in the web services binding
+ thro Tuscany SCA policy intents and policysets using the policy framework
+ introduced in the last release.
+
+ Note : This release supports specifications of policies around axis2
+ config params - see helloworld-ws-service-secure sample. The policy
+ intents that have been tested are authentication, integrity and
+ confidentiality.
+ There is no sample or test that exercises confidentiality since there
+ are some unresolved licensing issue around bouncycastle libraries.
+ However, users who are not encumbered by the bouncycastle license
+ restrictions can try the 'confidentiality' intent. See FAQ -
+ http://incubator.apache.org/tuscany/tuscany-sca-java-faq.html
+
+ This release does not include support for WS-Policy
+ attachments in Tuscany Policysets for ws-security.
+
+
+- An XQuery component implementation type
+ implementation-xquery
+
+
+- A Databinding for converting data to and from nodes for XQuery
+ processing
+ databinding-saxon
+
+
+- OSGI support has been extended to allow Tuscany contributions
+ packaged as OSGI bundles hence taking advantage of OSGI's bundle
+ loading an dependency management capabilities
+
+
+- A BPEL component implementation type experimental implementation
+based on SCA BPEL Client and Implementation V1.0. At the moment only
+supports BPEL process as services.
+ implementation-bpel
+
+
+- The distributed runtime implementation has been separated out
+ into
+ *) domain
+ *) node
+ It is now wrapped by a SCADomain interface as is the standalone
+ runtime.
+
+ Note: This release does not include support for WebApp host deployment
+ for a distributed SCA Domain
+
+
+
+- The web service binding will now generate WSDL automatically
+ based on the service interface if no WSDL is provided
+
+
+- A new "store" sample and associated document show how a
+ simple store front application can be constructed
+ samples/store
+
+- The following features of this release are still experimental:
+ - BPEL implementation type, integrating with Apache ODE
+ - OSGI implementation type, integrating with Apache Felix
+ - XQuery implementation type
+
+
+
+Changes With Apache Tuscany SCA 0.99 (incubating) August 2007
+=============================================================
+
+The following are the significant additions to release 0.99
+over and above all of what was offered in release 0.91.
+
+- A version of the default sca binding that works between
+ components runing in separate Java virtual machines
+ binding-sca-axis
+
+- A simple node implementation and a service discovery
+ function for running sca applications distributed
+ across more than one node
+ distributed
+ distributed-impl
+
+- integration with OSGi runtimes is now supported with
+ a new implementation-osgi component type
+
+- PUB/SUB interactions are now supported by using new
+ notification binding and implementation types, and
+ samples demonstrating the feature.
+
+- The Tuscany runtime now has a policy framework supporting
+ the SCA policy specification
+
+- the endpoint URIs used by SCA bindings has been rationalized
+ and now follows the SCA Assembly specification
+
+- binding-ajax has been renamed to binding-dwr
+
+Changes With Apache Tuscany SCA 0.91 (incubating) July 2007
+===========================================================
+
+The following are the significant additions to release 0.91
+over and above all of what was offered in release 0.90.
+
+
+- Enhancements to support multiple contributions to the SCA Domain
+
+- The inclusion of a alternative simplified extensions-helper
+SPI layer to faciliate rapid development of extensions
+
+- More Implementation Extenstions
+ Spring
+ WebResource
+
+- More Binding Extensions
+ AJAX
+ EJB
+ RSS/ATOM Feeds
+
+- Demos that demonstrate the use of a mix of extensions
+ alert-aggregator-webapp
+ bigbank-account
+ bigbank-calculator
+ bigbank-stockquote
+
+
+- Samples
+ Samples to demostrate use of Spring, Resource, AJAX extensions
+
+Changes With Apache Tuscany SCA 0.90 (incubating) June 2007
+===========================================================
+
+- Implementations for all of the Java Annotations and API Specification V1.0 found at
+ (http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications)
+ apart from the following.
+ @ComponentName
+ Conversation
+ RequestContext
+
+- New assembly model implementation taking into account SCA 1.0 artifacts
+ Data duplication between assembly model and runtime removed
+
+- Simple single process domain support
+ Contribution support to scope items being deployed into the runtime
+
+- Improved Package/Class naming consistency across modules
+
+- Extensions now loaded via Java service mechanism
+ Refactored extensions to use new SPIs (see below)
+
+- Maven and Ant based sample builds in the binary distribution
+
+- Implementation Extensions
+ Java
+ Script supporting (Ruby, Python, Groovy, JavaScript)
+
+- Binding Extensions
+ Axis2
+ RMI
+ JSONRPC
+
+-Databinding Extensions
+ Axiom
+ JAXB
+ SDO
+
+- Host environments
+ Embedded
+ Tomcat
+ Jetty
+ RMI
+
+- A clear set of SPIs intended to be stable over future releases
+ SCA assembly model
+ org.apache.tuscany.sca.assembly
+ org.apache.tuscany.sca.interfacedef
+ org.apache.tuscany.sca.interfacedef.java
+ org.apache.tuscany.sca.interfacedef.wsdl
+ org.apache.tuscany.sca.policy
+
+ SCA contribution model
+ org.apache.tuscany.sca.contribution
+
+ Runtime extensions
+ org.apache.tuscany.sca.core
+ org.apache.tuscany.sca.invocation
+ org.apache.tuscany.sca.provider
+ org.apache.tuscany.sca.runtime
+ org.apache.tuscany.sca.work
+
+ Data binding support
+ org.apache.tuscany.sca.databinding
+
+ Embedding Tuscany
+ org.apache.tuscany.sca.host.embedded
+
+ Servlet container integration
+ org.apache.tuscany.sca.http
+
+- For this point release a partial set of JavaDoc is provided to
+ be filled out as we close on release 1.0
\ No newline at end of file diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/README b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/README new file mode 100644 index 0000000000..7f6a4487b4 --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/README @@ -0,0 +1,19 @@ +Apache Tuscany SCA 1.6.1 November 2010 README +============================================= + +Welcome to the Tuscany SCA 1.6.1 release. + +See the RELEASE_NOTES file for information specific to this release. + +In the binary release see the INSTALL file for information on how to +install the release. + +In the source distribution see the BUILDING file for information on +building the source code. + + + + + + + diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/RELEASE_NOTES b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/RELEASE_NOTES new file mode 100644 index 0000000000..f5ae2b2602 --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/RELEASE_NOTES @@ -0,0 +1,139 @@ +Apache Tuscany SCA 1.6.1 November 2010 Release Notes +==================================================== + +Apache Tuscany provides a runtime based on the Service Component +Architecture. SCA is a set of specifications aimed at simplifying SOA +Application Development which are being standardized at OASIS as part +of Open Composite Services Architecture (Open CSA) - http://www.oasis-opencsa.org/. + +Overview +-------- + + The Apache Tuscany SCA 1.6.1 release includes implementations of the + main SCA specifications including: + + SCA Assembly Model V1.0 + SCA Policy Framework V1.0 + SCA Java Common Annotations and APIs V1.0 + SCA Java Component Implementation V1.0 + SCA Spring Component Implementation V1.0 + SCA BPEL Client and Implementation V1.0 + SCA Web Services Binding V1.0 + SCA EJB Session Bean Binding V1.0 + + It also includes implementations of many features not yet defined + by SCA specifications, including: + + - SCA bindings for Direct Web Remoting, RSS and ATOM Feeds, + HTTP resources, JSON-RPC, PUB/SUB Notifications, and RMI. + - SCA implementation types for OSGI, XQuery, BPEL, Widget and various + dynamic languages including Groovy, Javascript, Python and Ruby + - Databindings for Service Data Objects (SDO), JAXB, XmlBeans, + Axis2's AXIOM, JSON, SAXON, DOM, SAX and StAX + + The Tuscany SCA Runtime can be configured as a single node SCA domain or + as an SCA domain distributed across multiple nodes. + In addition Tuscany SCA supports the following host-deployment options: - + - running standalone + - running with distributed nodes across multiple JVMs + - running with embedded Jetty or Tomcat + - running as part of a standard web application + + The Webapp samples included in this release have been tried and tested on + - Tomcat 5.5.20 and Tomcat 6.0.14 + - Jetty 6.1.3 + - Geronimo 2.0.2 Tomcat6 jee5 + - WebSphere 6.1 fix pack 9 + +See the CHANGES file for a detailed list of the features in this release. + +Release packaging +----------------- + +The source distribution contains the entire release contents in source form, comprising +- Tuscany runtime modules +- Tuscany tools +- integration and verification tests +- samples, tutorials and demos +- maven build files for all the above + +The binary distribution contains +- the Tuscany runtime modules in binary form +- third-party runtime dependencies for these modules +- samples, tutorials and demos with full source code and pre-built jar files +- ant scripts for running and building the samples, tutorials and demos +- maven build files for building the samples, tutorials and demos + +The Tuscany runtime modules and tools are available from the Maven repository + https://repository.apache.org/content/groups/public/ + +The Apache Tuscany SCA Tools Core Feature for Eclipse is available at the Eclipse update site + http://www.apache.org/dist/tuscany/java/sca/1.6.1/tuscany-sca-1.6.1-updatesite/ + +Notes: + +1. The following Tuscany runtime modules are distributed via the maven repository only and are + not included in the binary distribution: + tuscany-binding-sca-corba-1.6.1.jar (conflicts with tuscany-binding-sca-1.6.1.jar) + tuscany-host-corba-jee-1.6.1.jar (conflicts with tuscany-host-corba-jse-1.6.1.jar) + tuscany-node-launcher-osgi-1.6.1-jar (needs dependencies not in binary distro lib directory) + tuscany-policy-transaction-1.6.1.jar (has dependency conflicts with binary distro lib directory) + +2. The following Tuscany runtime modules are included in the binary distribution but are not included + in tuscany-sca-all-1.6.1.jar and tuscany-sca-manifest.jar: + tuscany-binding-atom-js-dojo-1.6.1.jar (conflicts with tuscany-binding-atom-js-1.6.1.jar) + tuscany-binding-jsonrpc-js-dojo-1.6.1.jar (conflicts with tuscany-binding-jsonrpc-js-1.6.1.jar) + tuscany-host-tomcat-1.6.1.jar (conflicts with tuscany-host-jetty-1.6.1.jar) + tuscany-implementation-widget-runtime-dojo-1.6.1.jar (conflicts with tuscany-implementation-widget-runtime-1.6.1.jar) + tuscany-web-javascript-dojo-1.6.1.jar (conflicts with tuscany-web-javascript-1.6.1.jar) + If these files are needed at runtime, the classpath must be set up to include these jars explicitly + and exclude the jars for which conflicts are indicated above. + +3. The Erlang binding and samples require Erlang/OTP to be installed. This isn't included in the + binary distribution and must be downloaded and installed separately if required. + +4. For samples, demos, and tutorials packaged as web applications (.war files), the .war files + are omitted from the binary distribution to save space (except for the calculator sample). + These .war files can be created using the ant scripts provided. + +5. The Tuscany SCA Eclipse Tools Feature and Plug-in are distributed via the Tuscany Eclipse + update site only. + +6. Other Tuscany tools are distributed via the maven repository only, except for the following jar + which is also included in the binary distribution: + tuscany-wsdl2java-1.6.1.jar (needed by the helloworld-bpel sample) + +Support +------- + +For more information on Apache Tuscany visit the website at: + + http://tuscany.apache.org/ + +Any issues with this release can be reported to Apache Tuscany +using the mailing lists or in the JIRA issue tracker. + + Mailing list archives: + + http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/ + http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/ + + Jira: + + http://issues.apache.org/jira/browse/TUSCANY + +To join the project's mailing lists follow the instructions at: + + http://tuscany.apache.org/mailing-lists.html + +To find out more about OASIS Open CSA go to: + + http://www.oasis-opencsa.org. + +Apache Tuscany welcomes your help. Any contribution, including code, +testing, improving the documentation, or bug reporting is always +appreciated. + +Thank you for using Apache Tuscany! + +- The Tuscany Team. diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/INSTALL b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/INSTALL new file mode 100644 index 0000000000..f2a3c6336b --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/INSTALL @@ -0,0 +1,26 @@ +Installing the Apache Tuscany SCA 1.6.1 November 2010 Release binary distribution +================================================================================= + +Unzip Tuscany binary distribution archive and you get the following: + +tuscany-sca-1.6.1 + INSTALL - this help file + LICENSE - the Apache License and any dependecy licenses + NOTICE - attribution notices associated with the licenses + README - readme for the release + RELEASE_NOTES - description of this release + CHANGES - A note of the major changes in this release + + /demos - Demo applications showcasing the use of Apache Tuscany + + /lib - The tuscany-sca-all and tuscany-sca-manifest jars and all their dependencies + + /modules - all of the individual Tuscany jars + + /samples - all the Tuscany samples, see the README in that directory + + /tutorial - The store tutorial, see the README in that directory + + + + diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/LICENSE b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/LICENSE new file mode 100644 index 0000000000..11f89e750a --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/LICENSE @@ -0,0 +1,3134 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + 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. + + +=============================================================================================================== + +APACHE TUSCANY SCA SUBCOMPONENTS: + +Apache Tuscany SCA for Java includes a number of subcomponents with +separate copyright notices and license terms. Your use of these subcomponents +is subject to the terms and conditions of the following licenses. + +================================================================================ + +The tuscany-implementation-script jar temporarily includes one file under the following BSD license: + + Copyright (c) 2006, Sun Microsystems, Inc. + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are met: + + - Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + + - Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + + - Neither the name of the Sun Microsystems, Inc. nor the names of + contributors may be used to endorse or promote products derived from this + software without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED + WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A + PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY + DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, + PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE + OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH + DAMAGE. + +================================================================================ + +The tuscany-assembly-xsd jar includes XSD files under the following SCA Collaboration license: + +(c) Copyright SCA Collaboration 2006, 2007 + +License for the Service Component Architecture JavaDoc, Interface +Definition files and XSD files. + +The Service Component Architecture JavaDoc, Interface Definition files, +and XSD files are being provided by the copyright holders under the +following license. By using and/or copying this work, you agree that +you have read, understood and will comply with the following terms and +conditions: + +Permission to copy, display, make derivative works of, and distribute +the Service Component Architecture JavaDoc, Interface Definition Files +and XSD files (the "Artifacts") in any medium without fee or royalty is +hereby granted, provided that you include the following on ALL copies +of the Artifacts, or portions thereof, that you make: + +1. A link or URL to the Artifacts at this location: +http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications + +2. The full text of this copyright notice as shown in the Artifacts. + +THE ARTIFACTS ARE PROVIDED "AS IS," AND THE AUTHORS MAKE NO +REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE +ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, INCLUDING, BUT NOT +LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR +PURPOSE, NON-INFRINGEMENT OR TITLE. + +THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, +INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY +USE OR DISTRIBUTION OF THE ARTIFACTS. + +The name and trademarks of the Authors may NOT be used in any manner, +including advertising or publicity pertaining to the Service Component +Architecture Specification or its contents without specific, written +prior permission. Title to copyright in the Service Component +Architecture Specification and the JavaDoc, Interface Definition Files +and XSD Files will at all times remain with the Authors. + +No other rights are granted by implication, estoppel or otherwise. + +Revision level 1.1, last updated on 2007/11/19 + +================================================================================ + +The tuscany-assembly-xsd jar includes files under the following copyright and license: + +Copyright (c) 2004 World Wide Web Consortium (Massachusetts Institute of Technology, +European Research Consortium for Informatics and Mathematics, Keio University). +All Rights Reserved. This work is distributed under the W3C(r) Software License [1] +in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied +warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + + [1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 + +W3C® SOFTWARE NOTICE AND LICENSE +http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 + +This work (and included software, documentation such as READMEs, or other related items) +is being provided by the copyright holders under the following license. By obtaining, +using and/or copying this work, you (the licensee) agree that you have read, understood, +and will comply with the following terms and conditions. + +Permission to copy, modify, and distribute this software and its documentation, with or +without modification, for any purpose and without fee or royalty is hereby granted, provided +that you include the following on ALL copies of the software and documentation or portions +thereof, including modifications: + + 1. The full text of this NOTICE in a location viewable to users of the redistributed or + derivative work. + 2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. + If none exist, the W3C Software Short Notice should be included (hypertext is preferred, + text is permitted) within the body of any redistributed or derivative code. + 3. Notice of any changes or modifications to the files, including the date changes were + made. (We recommend you provide URIs to the location from which the code is derived.) + +THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO +REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES +OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR +DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER +RIGHTS. + +COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL +DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION. + +The name and trademarks of copyright holders may NOT be used in advertising or publicity +pertaining to the software without specific, written prior permission. Title to copyright +in this software and any associated documentation will at all times remain with copyright +holders. + +================================================================================ + +The tuscany-host-webapp and tuscany-sca-api jars include files under the following +copyrights and license: + +Copyright Notices + +(C) Copyright BEA Systems, Inc., Cape Clear Software, International Business Machines Corp, Interface21, IONA Technologies, +Oracle, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG., Siemens AG., Software AG., Sybase +Inc., TIBCO Software Inc., 2005, 2007. All rights reserved. + +(C) Copyright BEA Systems, Inc., Cape Clear Software, International Business Machines Corp, Interface21, IONA +Technologies, Oracle, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG., Siemens +AG., Software AG., Sun Microsystems, Inc., Sybase Inc., TIBCO Software Inc., 2005, 2008. All rights reserved. + +License + +Permission to copy, display and distribute the Service Component Architecture Specification and/or +portions thereof, without modification, in any medium without fee or royalty is hereby granted, provided +that you include the following on ALL copies of the Service Component Architecture Specification, or +portions thereof, that you make: + +1. A link or URL to the Service Component Architecture Specification at this location: +· http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications + +2. The full text of the copyright notice as shown in the Service Component Architecture Specification. + +BEA, Cape Clear, IBM, Interface21, IONA, Oracle, Primeton, Progress Software, Red Hat, Rogue Wave, +SAP, Siemens, Software AG., Sun, Sybase, TIBCO (collectively, the "Authors") agree to grant you a +royalty-free license, under reasonable, non-discriminatory terms and conditions to patents that they deem +necessary to implement the Service Component Architecture Specification. + +THE Service Component Architecture SPECIFICATION IS PROVIDED "AS IS," AND THE +AUTHORS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, +REGARDING THIS SPECIFICATION AND THE IMPLEMENTATION OF ITS CONTENTS, +INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A +PARTICULAR PURPOSE, NON-INFRINGEMENT OR TITLE. + +THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL +OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY USE OR +DISTRIBUTION OF THE Service Components Architecture SPECIFICATION. + +The name and trademarks of the Authors may NOT be used in any manner, including advertising or +publicity pertaining to the Service Component Architecture Specification or its contents without specific, +written prior permission. Title to copyright in the Service Component Architecture Specification +will at all times remain with the Authors. + +No other rights are granted by implication, estoppel or otherwise. + +=============================================================================== + +The tuscany-binding-jsonrpc-runtime and tuscany-implementation-web-runtime jars +include the file jsonrpc.js which is under the following copyright and license: + +/* + * JSON-RPC JavaScript client + * + * $Id: jsonrpc.js,v 1.36.2.3 2006/03/08 15:09:37 mclark Exp $ + * + * Copyright (c) 2003-2004 Jan-Klaas Kollhof + * Copyright (c) 2005 Michael Clark, Metaparadigm Pte Ltd + * + * This code is based on Jan-Klaas' JavaScript o lait library (jsolait). + * + * 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. + * + */ + +/* + * Modifications for Apache Tuscany: + * - JSONRpcClient_createMethod changed so callback is last arg + */ + +================================================================================= + +The tuscany-web-javascript-dojo and demo-bigbank jars include a redistribution of + dojotoolkit V1.3.0 +under the following copyright and license: + +The "New" BSD License: +********************** + +Copyright (c) 2005, The Dojo Foundation +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + + * Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + * Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + * Neither the name of the Dojo Foundation nor the names of its contributors + may be used to endorse or promote products derived from this software + without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND +ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE +FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +================================================================================= + +APACHE TUSCANY SCA REDISTRIBUTED FILES: + +The Apache Tuscany SCA binary distribution includes a number of +redistributed files with separate copyright notices and license terms. +Your use of these redistributed files is subject to the terms and conditions +of the following licenses. + +=============================================================================== + +The following files are redistributed in executable form under Apache Software License 2.0: + abdera-client-0.4.0-incubating.jar + abdera-core-0.4.0-incubating.jar + abdera-extensions-html-0.4.0-incubating.jar + abdera-extensions-json-0.4.0-incubating.jar + abdera-extensions-main-0.4.0-incubating.jar + abdera-i18n-0.4.0-incubating.jar + abdera-parser-0.4.0-incubating.jar + abdera-server-0.4.0-incubating.jar + activeio-2.0-r118.jar + activemq-all-5.2.0.jar + addressing-1.3.mar + annogen-0.1.0.jar + annotations-api-6.0.14.jar + aopalliance-1.0.jar + axiom-api-1.2.7.jar + axiom-dom-1.2.7.jar + axiom-impl-1.2.7.jar + axis2-adb-1.4.1.jar + axis-ant-1.4.jar + axis2-codegen-1.4.1.jar + axis2-java2wsdl-1.4.1.jar + axis2-kernel-1.4.1.jar + axis2-mtompolicy-1.4.1.jar + bsf-all-3.0-beta2.jar + catalina-6.0.14.jar + cglib-nodep-2.2.jar + commons-collections-3.1.jar + commons-codec-1.3.jar + commons-fileupload-1.2.jar + commons-httpclient-3.1.jar + commons-io-1.4.jar + commons-jexl-1.1.jar + commons-lang-2.3.jar + commons-logging-1.1.1.jar + coyote-6.0.14.jar + derby-10.3.1.4.jar + gdata-client-1.0.jar + gdata-client-meta-1.0.jar + gdata-core-1.0.jar + gdata-media-1.0.jar + geronimo-common-1.2-beta.jar + geronimo-connector-1.2-beta.jar + geronimo-core-1.2-beta.jar + geronimo-deployment-1.2-beta.jar + geronimo-ejb_3.0_spec-1.0.jar + geronimo-interceptor-1.2-beta.jar + geronimo-j2ee-1.2-beta.jar + geronimo-j2ee-connector_1.5_spec-1.1.jar + geronimo-j2ee-jacc_1.0_spec-1.1.jar + geronimo-j2ee-management_1.0_spec-1.1.jar + geronimo-javamail_1.4_spec-1.2.jar + geronimo-jms_1.1_spec-1.1.jar + geronimo-jpa_3.0_spec-1.0.jar + geronimo-jta_1.0.1B_spec-1.0.jar + geronimo-kernel-1.2-beta.jar + geronimo-management-1.2-beta.jar + geronimo-naming-1.2-beta.jar + geronimo-security-1.2-beta.jar + geronimo-spec-j2ee-connector-1.5-rc4.jar + geronimo-spec-jta-1.0.1B-rc4.jar + geronimo-stax-api_1.0_spec-1.0.1.jar + geronimo-system-1.2-beta.jar + geronimo-transaction-1.2-beta.jar + geronimo-util-1.2-beta.jar + httpcore-4.0-beta1.jar + httpcore-nio-4.0-beta1.jar + jettison-1.0.1.jar + jetty-6.1.7.jar + jetty-util-6.1.7.jar + jinterface-1.5.3.1.jar + json-rpc-1.0.jar + juli-6.0.14.jar + log4j-1.2.13.jar + lucene-core-2.9.1.jar + lucene-highlighter-2.9.1.jar + lucene-memory-2.9.1.jar + mex-1.41-impl.jar + neethi-2.0.4.jar + ode-bpel-api-1.1.1.jar + ode-bpel-compiler-1.1.1.jar + ode-bpel-dao-1.1.1.jar + ode-bpel-epr-1.1.1.jar + ode-bpel-obj-1.1.1.jar + ode-bpel-runtime-1.1.1.jar + ode-bpel-schemas-1.1.1.jar + ode-bpel-store-1.1.1.jar + ode-dao-jpa-1.1.1.jar + ode-dao-jpa-ojpa-derby-1.1.1.zip + ode-jacob-1.1.1.jar + ode-jacob-ap-1.1.1.jar + ode-scheduler-simple-1.1.1.jar + ode-utils-1.1.1.jar + openjpa-all-0.9.7-incubating.jar + openjpa-persistence-0.9.7-incubating.jar + opensaml-1.1.jar + org.apache.felix.bundlerepository-1.0.3.jar + org.apache.felix.framework-1.0.4.jar + org.apache.felix.main-1.0.4.jar + org.apache.felix.shell-1.0.1.jar + org.apache.felix.shell.tui-1.0.1.jar + rampart-core-1.4.jar + rampart-policy-1.4.jar + rampart-trust-1.4.jar + regexp-1.3.jar + spring-beans-2.5.5.jar + spring-context-2.5.5.jar + spring-core-2.5.5.jar + tranql-connector-1.1.jar + tuscany-sdo-api-r2.1-1.1.1.jar + tuscany-sdo-impl-1.1.1.jar + tuscany-sdo-lib-1.1.1.jar + tuscany-sdo-tools-1.1.1.jar + woden-api-1.0M8.jar + woden-impl-dom-1.0M8.jar + wss4j-1.5.4.jar + wstx-asl-3.2.4.jar + xalan-2.7.0.jar + xbean-naming-2.7.jar + xercesImpl-2.8.1.jar + xml-apis-1.3.03.jar + xmlbeans-2.3.0.jar + xmlParserAPIs-2.6.0.jar + xml-resolver-1.1.jar + xmlsec-1.4.2.jar + XmlSchema-1.4.2.jar +and are subject to the following copyrights: + XmlSchema-1.4.2.jar + - Portions Copyright 2006 International Business Machines Corp. + ode-bpel-api-1.1.1.jar + - Copyright 1999-2006 Intalio - This product includes software developed by Intalio (http://www.intalio.com) + - Copyright 2006 Sybase - This product includes software developed by Sybase.(http://www.sybase.com) + +=============================================================================== + +The files: + commons-discovery-0.2.jar + commons-primitives-1.0.jar +are redistributed in executable form and are licensed under the following terms: + +/* ==================================================================== + * The Apache Software License, Version 1.1 + * + * Copyright (c) 2000 The Apache Software Foundation. All rights + * reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in + * the documentation and/or other materials provided with the + * distribution. + * + * 3. The end-user documentation included with the redistribution, + * if any, must include the following acknowledgment: + * "This product includes software developed by the + * Apache Software Foundation (http://www.apache.org/)." + * Alternately, this acknowledgment may appear in the software itself, + * if and wherever such third-party acknowledgments normally appear. + * + * 4. The names "Apache" and "Apache Software Foundation" must + * not be used to endorse or promote products derived from this + * software without prior written permission. For written + * permission, please contact apache@apache.org. + * + * 5. Products derived from this software may not be called "Apache", + * nor may "Apache" appear in their name, without prior written + * permission of the Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED + * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR + * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND + * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, + * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT + * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * ==================================================================== + * + * This software consists of voluntary contributions made by many + * individuals on behalf of the Apache Software Foundation. For more + * information on the Apache Software Foundation, please see + * <http://www.apache.org/>. + * + * Portions of this software are based upon public domain software + * originally written at the National Center for Supercomputing Applications, + * University of Illinois, Urbana-Champaign. + */ + +=============================================================================== + +The file: + axion-1.0-M3-dev.jar +is redistributed in executable form and is licensed under the following terms: + +Copyright (c) 2002-2003 Axion Development Team. All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + +1. Redistributions of source code must retain the above + copyright notice, this list of conditions and the following + disclaimer. + +2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in + the documentation and/or other materials provided with the + distribution. + +3. The names "Tigris", "Axion", nor the names of its contributors may + not be used to endorse or promote products derived from this + software without specific prior written permission. + +4. Products derived from this software may not be called "Axion", nor + may "Tigris" or "Axion" appear in their names without specific prior + written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT +OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT +LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE +OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +The "Axion Development Team" is defined to be: + + * Chuck Burdick + * James Burke + * Morgan Delagrange + * Geir Magnusson Jr. + * Martin Poeschl + * Steve Polyak + * Daniel Rall + * Ahimanikya Satapathy + * Doug Sale + * James Strachan + * Rodney Waldhoff + * Jason van Zyl + +License changes are to be determined by a simple majority vote of the +Axion Development Team. + +=============================================================================== + +The file: + dom4j-1.6.1.jar +is redistributed in executable form and is licensed under the following terms: + +Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved. + +Redistribution and use of this software and associated documentation +("Software"), with or without modification, are permitted provided +that the following conditions are met: + +1. Redistributions of source code must retain copyright + statements and notices. Redistributions must also contain a + copy of this document. + +2. Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and the + following disclaimer in the documentation and/or other + materials provided with the distribution. + +3. The name "DOM4J" must not be used to endorse or promote + products derived from this Software without prior written + permission of MetaStuff, Ltd. For written permission, + please contact dom4j-info@metastuff.com. + +4. Products derived from this Software may not be called "DOM4J" + nor may "DOM4J" appear in their names without prior written + permission of MetaStuff, Ltd. DOM4J is a registered + trademark of MetaStuff, Ltd. + +5. Due credit should be given to the DOM4J Project - + http://www.dom4j.org + +THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS +``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT +NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL +METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, +INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED +OF THE POSSIBILITY OF SUCH DAMAGE. + +=============================================================================== + +The EMF files: + codegen-2.2.3.jar + codegen-ecore-2.2.3.jar + common-2.2.3.jar + ecore-2.2.3.jar + ecore-change-2.2.3.jar + ecore-xmi-2.2.3.jar + xsd-2.2.3.jar +and AspectJ files: + aspectjlib-1.6.2.jar + aspectjrt-1.6.2.jar +are redistributed in executable form, with source code available at + http://www.eclipse.org/modeling/emf/downloads/ + http://www.eclipse.org/aspectj/downloads.php +and are licensed under the following terms: + +Eclipse Public License - v 1.0 + +THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE +PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF +THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. + +1. DEFINITIONS + +"Contribution" means: + +a) in the case of the initial Contributor, the initial code and +documentation distributed under this Agreement, and +b) in the case of each subsequent Contributor: + +i) changes to the Program, and + +ii) additions to the Program; + +where such changes and/or additions to the Program originate from and +are distributed by that particular Contributor. A Contribution +'originates' from a Contributor if it was added to the Program by such +Contributor itself or anyone acting on such Contributor's behalf. +Contributions do not include additions to the Program which: (i) are +separate modules of software distributed in conjunction with the +Program under their own license agreement, and (ii) are not derivative +works of the Program. + +"Contributor" means any person or entity that distributes the Program. + +"Licensed Patents " mean patent claims licensable by a Contributor +which are necessarily infringed by the use or sale of its Contribution +alone or when combined with the Program. + +"Program" means the Contributions distributed in accordance with this +Agreement. + +"Recipient" means anyone who receives the Program under this +Agreement, including all Contributors. + +2. GRANT OF RIGHTS + +a) Subject to the terms of this Agreement, each Contributor hereby +grants Recipient a non-exclusive, worldwide, royalty-free copyright +license to reproduce, prepare derivative works of, publicly display, +publicly perform, distribute and sublicense the Contribution of such +Contributor, if any, and such derivative works, in source code and +object code form. + +b) Subject to the terms of this Agreement, each Contributor hereby +grants Recipient a non-exclusive, worldwide, royalty-free patent +license under Licensed Patents to make, use, sell, offer to sell, +import and otherwise transfer the Contribution of such Contributor, if +any, in source code and object code form. This patent license shall +apply to the combination of the Contribution and the Program if, at +the time the Contribution is added by the Contributor, such addition +of the Contribution causes such combination to be covered by the +Licensed Patents. The patent license shall not apply to any other +combinations which include the Contribution. No hardware per se is +licensed hereunder. + +c) Recipient understands that although each Contributor grants the +licenses to its Contributions set forth herein, no assurances are +provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. Each +Contributor disclaims any liability to Recipient for claims brought by +any other entity based on infringement of intellectual property rights +or otherwise. As a condition to exercising the rights and licenses +granted hereunder, each Recipient hereby assumes sole responsibility +to secure any other intellectual property rights needed, if any. For +example, if a third party patent license is required to allow +Recipient to distribute the Program, it is Recipient's responsibility +to acquire that license before distributing the Program. + +d) Each Contributor represents that to its knowledge it has sufficient +copyright rights in its Contribution, if any, to grant the copyright +license set forth in this Agreement. + +3. REQUIREMENTS + +A Contributor may choose to distribute the Program in object code form +under its own license agreement, provided that: + +a) it complies with the terms and conditions of this Agreement; and + +b) its license agreement: + +i) effectively disclaims on behalf of all Contributors all warranties +and conditions, express and implied, including warranties or +conditions of title and non-infringement, and implied warranties or +conditions of merchantability and fitness for a particular purpose; + +ii) effectively excludes on behalf of all Contributors all liability +for damages, including direct, indirect, special, incidental and +consequential damages, such as lost profits; + +iii) states that any provisions which differ from this Agreement are +offered by that Contributor alone and not by any other party; and + +iv) states that source code for the Program is available from such +Contributor, and informs licensees how to obtain it in a reasonable +manner on or through a medium customarily used for software exchange. + +When the Program is made available in source code form: + +a) it must be made available under this Agreement; and + +b) a copy of this Agreement must be included with each copy of the +Program. + +Contributors may not remove or alter any copyright notices contained +within the Program. + +Each Contributor must identify itself as the originator of its +Contribution, if any, in a manner that reasonably allows subsequent +Recipients to identify the originator of the Contribution. + +4. COMMERCIAL DISTRIBUTION + +Commercial distributors of software may accept certain +responsibilities with respect to end users, business partners and the +like. While this license is intended to facilitate the commercial use +of the Program, the Contributor who includes the Program in a +commercial product offering should do so in a manner which does not +create potential liability for other Contributors. Therefore, if a +Contributor includes the Program in a commercial product offering, +such Contributor ("Commercial Contributor") hereby agrees to defend +and indemnify every other Contributor ("Indemnified Contributor") +against any losses, damages and costs (collectively "Losses") arising +from claims, lawsuits and other legal actions brought by a third party +against the Indemnified Contributor to the extent caused by the acts +or omissions of such Commercial Contributor in connection with its +distribution of the Program in a commercial product offering. The +obligations in this section do not apply to any claims or Losses +relating to any actual or alleged intellectual property infringement. +In order to qualify, an Indemnified Contributor must: a) promptly +notify the Commercial Contributor in writing of such claim, and b) +allow the Commercial Contributor to control, and cooperate with the +Commercial Contributor in, the defense and any related settlement +negotiations. The Indemnified Contributor may participate in any such +claim at its own expense. + +For example, a Contributor might include the Program in a commercial +product offering, Product X. That Contributor is then a Commercial +Contributor. If that Commercial Contributor then makes performance +claims, or offers warranties related to Product X, those performance +claims and warranties are such Commercial Contributor's responsibility +alone. Under this section, the Commercial Contributor would have to +defend claims against the other Contributors related to those +performance claims and warranties, and if a court requires any other +Contributor to pay any damages as a result, the Commercial Contributor +must pay those damages. + +5. NO WARRANTY + +EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS +PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY +WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY +OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely +responsible for determining the appropriateness of using and +distributing the Program and assumes all risks associated with its +exercise of rights under this Agreement , including but not limited to +the risks and costs of program errors, compliance with applicable +laws, damage to or loss of data, programs or equipment, and +unavailability or interruption of operations. + +6. DISCLAIMER OF LIABILITY + +EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR +ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING +WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR +DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED +HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +7. GENERAL + +If any provision of this Agreement is invalid or unenforceable under +applicable law, it shall not affect the validity or enforceability of +the remainder of the terms of this Agreement, and without further +action by the parties hereto, such provision shall be reformed to the +minimum extent necessary to make such provision valid and enforceable. + +If Recipient institutes patent litigation against any entity +(including a cross-claim or counterclaim in a lawsuit) alleging that +the Program itself (excluding combinations of the Program with other +software or hardware) infringes such Recipient's patent(s), then such +Recipient's rights granted under Section 2(b) shall terminate as of +the date such litigation is filed. + +All Recipient's rights under this Agreement shall terminate if it +fails to comply with any of the material terms or conditions of this +Agreement and does not cure such failure in a reasonable period of +time after becoming aware of such noncompliance. If all Recipient's +rights under this Agreement terminate, Recipient agrees to cease use +and distribution of the Program as soon as reasonably practicable. +However, Recipient's obligations under this Agreement and any licenses +granted by Recipient relating to the Program shall continue and +survive. + +Everyone is permitted to copy and distribute copies of this Agreement, +but in order to avoid inconsistency the Agreement is copyrighted and +may only be modified in the following manner. The Agreement Steward +reserves the right to publish new versions (including revisions) of +this Agreement from time to time. No one other than the Agreement +Steward has the right to modify this Agreement. The Eclipse Foundation +is the initial Agreement Steward. The Eclipse Foundation may assign +the responsibility to serve as the Agreement Steward to a suitable +separate entity. Each new version of the Agreement will be given a +distinguishing version number. The Program (including Contributions) +may always be distributed subject to the version of the Agreement +under which it was received. In addition, after a new version of the +Agreement is published, Contributor may elect to distribute the +Program (including its Contributions) under the new version. Except as +expressly stated in Sections 2(a) and 2(b) above, Recipient receives +no rights or licenses to the intellectual property of any Contributor +under this Agreement, whether expressly, by implication, estoppel or +otherwise. All rights in the Program not expressly granted under this +Agreement are reserved. + +This Agreement is governed by the laws of the State of New York and +the intellectual property laws of the United States of America. No +party to this Agreement will bring a legal action under this Agreement +more than one year after the cause of action arose. Each party waives +its rights to a jury trial in any resulting litigation. + +=============================================================================== + +The Saxon files: + saxon-8.7.jar + saxon-dom-8.7.jar + saxon-xpath-8.7.jar +are redistributed in executable form and are licensed under the following terms: + + MOZILLA PUBLIC LICENSE +Version 1.0 + +1. Definitions. + + 1.1. ``Contributor'' means each entity that creates or contributes to the creation of Modifications. + + 1.2. ``Contributor Version'' means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. + + 1.3. ``Covered Code'' means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. + + 1.4. ``Electronic Distribution Mechanism'' means a mechanism generally accepted in the software development community for the electronic transfer of data. + + 1.5. ``Executable'' means Covered Code in any form other than Source Code. + + 1.6. ``Initial Developer'' means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. + + 1.7. ``Larger Work'' means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. + + 1.8. ``License'' means this document. + + 1.9. ``Modifications'' means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: + + A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. + + B. Any new file that contains any part of the Original Code or previous Modifications. + + 1.10. ``Original Code'' means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. + + 1.11. ``Source Code'' means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or a list of source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. + + 1.12. ``You'' means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, ``You'' includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, ``control'' means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity. + +2. Source Code License. + + 2.1. The Initial Developer Grant. + The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: + + (a) to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by Initial Developer, to make, have made, use and sell (``Utilize'') the Original Code (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Original Code (or portions thereof) and not to any greater extent that may be necessary to Utilize further Modifications or combinations. + + 2.2. Contributor Grant. + Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: + + (a) to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by Contributor, to Utilize the Contributor Version (or portions thereof), but solely to the extent that any such patent is reasonably necessary to enable You to Utilize the Contributor Version (or portions thereof), and not to any greater extent that may be necessary to Utilize further Modifications or combinations. + +3. Distribution Obligations. + + 3.1. Application of License. + The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. + + 3.2. Availability of Source Code. + Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. + + 3.3. Description of Modifications. + You must cause all Covered Code to which you contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. + + 3.4. Intellectual Property Matters + + (a) Third Party Claims. + If You have knowledge that a party claims an intellectual property right in particular functionality or code (or its utilization under this License), you must include a text file with the source code distribution titled ``LEGAL'' which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If you obtain such knowledge after You make Your Modification available as described in Section 3.2, You shall promptly modify the LEGAL file in all copies You make available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. + + (b) Contributor APIs. + If Your Modification is an application programming interface and You own or control patents which are reasonably necessary to implement that API, you must also include this information in the LEGAL file. + + 3.5. Required Notices. + You must duplicate the notice in Exhibit A in each file of the Source Code, and this License in any documentation for the Source Code, where You describe recipients' rights relating to Covered Code. If You created one or more Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If it is not possible to put such notice in a particular Source Code file due to its structure, then you must include such notice in a location (such as a relevant directory file) where a user would be likely to look for such a notice. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. + + 3.6. Distribution of Executable Versions. + You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. + + 3.7. Larger Works. + You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + + If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. + +5. Application of this License. + + This License applies to code to which the Initial Developer has attached the notice in Exhibit A, and to related Covered Code. + +6. Versions of the License. + + 6.1. New Versions. + Netscape Communications Corporation (``Netscape'') may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. + + 6.2. Effect of New Versions. + Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License. + + 6.3. Derivative Works. + If you create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), you must (a) rename Your license so that the phrases ``Mozilla'', ``MOZILLAPL'', ``MOZPL'', ``Netscape'', ``NPL'' or any confusingly similar phrase do not appear anywhere in your license and (b) otherwise make it clear that your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) + +7. DISCLAIMER OF WARRANTY. + + COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + + This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. + +9. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + + The Covered Code is a ``commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer software'' and ``commercial computer software documentation,'' as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. + +11. MISCELLANEOUS. + + This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in, the United States of America: (a) unless otherwise agreed in writing, all disputes relating to this License (excepting any dispute relating to intellectual property rights) shall be subject to final and binding arbitration, with the losing party paying all costs of arbitration; (b) any arbitration relating to this Agreement shall be held in Santa Clara County, California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to this Agreement shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. + +12. RESPONSIBILITY FOR CLAIMS. + + Except in cases where another Contributor has failed to comply with Section 3.4, You are responsible for damages arising, directly or indirectly, out of Your utilization of rights under this License, based on the number of copies of Covered Code you made available, the revenues you received from utilizing such rights, and other relevant factors. You agree to work with affected parties to distribute responsibility on an equitable basis. + +EXHIBIT A. + + ``The contents of this file are subject to the Mozilla Public License Version 1.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.mozilla.org/MPL/ + + Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. + + The Original Code is ______________________________________. + + The Initial Developer of the Original Code is ________________________. Portions created by ______________________ are Copyright (C) ______ _______________________. All Rights Reserved. + + Contributor(s): ______________________________________.'' + +=============================================================================== + +The Rhino JavaScript engine file: + js-1.6R7.jar +is redistributed in executable form and is licensed under the following terms: + + MOZILLA PUBLIC LICENSE + Version 1.1 + + --------------- + +1. Definitions. + + 1.0.1. "Commercial Use" means distribution or otherwise making the + Covered Code available to a third party. + + 1.1. "Contributor" means each entity that creates or contributes to + the creation of Modifications. + + 1.2. "Contributor Version" means the combination of the Original + Code, prior Modifications used by a Contributor, and the Modifications + made by that particular Contributor. + + 1.3. "Covered Code" means the Original Code or Modifications or the + combination of the Original Code and Modifications, in each case + including portions thereof. + + 1.4. "Electronic Distribution Mechanism" means a mechanism generally + accepted in the software development community for the electronic + transfer of data. + + 1.5. "Executable" means Covered Code in any form other than Source + Code. + + 1.6. "Initial Developer" means the individual or entity identified + as the Initial Developer in the Source Code notice required by Exhibit + A. + + 1.7. "Larger Work" means a work which combines Covered Code or + portions thereof with code not governed by the terms of this License. + + 1.8. "License" means this document. + + 1.8.1. "Licensable" means having the right to grant, to the maximum + extent possible, whether at the time of the initial grant or + subsequently acquired, any and all of the rights conveyed herein. + + 1.9. "Modifications" means any addition to or deletion from the + substance or structure of either the Original Code or any previous + Modifications. When Covered Code is released as a series of files, a + Modification is: + A. Any addition to or deletion from the contents of a file + containing Original Code or previous Modifications. + + B. Any new file that contains any part of the Original Code or + previous Modifications. + + 1.10. "Original Code" means Source Code of computer software code + which is described in the Source Code notice required by Exhibit A as + Original Code, and which, at the time of its release under this + License is not already Covered Code governed by this License. + + 1.10.1. "Patent Claims" means any patent claim(s), now owned or + hereafter acquired, including without limitation, method, process, + and apparatus claims, in any patent Licensable by grantor. + + 1.11. "Source Code" means the preferred form of the Covered Code for + making modifications to it, including all modules it contains, plus + any associated interface definition files, scripts used to control + compilation and installation of an Executable, or source code + differential comparisons against either the Original Code or another + well known, available Covered Code of the Contributor's choice. The + Source Code can be in a compressed or archival form, provided the + appropriate decompression or de-archiving software is widely available + for no charge. + + 1.12. "You" (or "Your") means an individual or a legal entity + exercising rights under, and complying with all of the terms of, this + License or a future version of this License issued under Section 6.1. + For legal entities, "You" includes any entity which controls, is + controlled by, or is under common control with You. For purposes of + this definition, "control" means (a) the power, direct or indirect, + to cause the direction or management of such entity, whether by + contract or otherwise, or (b) ownership of more than fifty percent + (50%) of the outstanding shares or beneficial ownership of such + entity. + +2. Source Code License. + + 2.1. The Initial Developer Grant. + The Initial Developer hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + (a) under intellectual property rights (other than patent or + trademark) Licensable by Initial Developer to use, reproduce, + modify, display, perform, sublicense and distribute the Original + Code (or portions thereof) with or without Modifications, and/or + as part of a Larger Work; and + + (b) under Patents Claims infringed by the making, using or + selling of Original Code, to make, have made, use, practice, + sell, and offer for sale, and/or otherwise dispose of the + Original Code (or portions thereof). + + (c) the licenses granted in this Section 2.1(a) and (b) are + effective on the date Initial Developer first distributes + Original Code under the terms of this License. + + (d) Notwithstanding Section 2.1(b) above, no patent license is + granted: 1) for code that You delete from the Original Code; 2) + separate from the Original Code; or 3) for infringements caused + by: i) the modification of the Original Code or ii) the + combination of the Original Code with other software or devices. + + 2.2. Contributor Grant. + Subject to third party intellectual property claims, each Contributor + hereby grants You a world-wide, royalty-free, non-exclusive license + + (a) under intellectual property rights (other than patent or + trademark) Licensable by Contributor, to use, reproduce, modify, + display, perform, sublicense and distribute the Modifications + created by such Contributor (or portions thereof) either on an + unmodified basis, with other Modifications, as Covered Code + and/or as part of a Larger Work; and + + (b) under Patent Claims infringed by the making, using, or + selling of Modifications made by that Contributor either alone + and/or in combination with its Contributor Version (or portions + of such combination), to make, use, sell, offer for sale, have + made, and/or otherwise dispose of: 1) Modifications made by that + Contributor (or portions thereof); and 2) the combination of + Modifications made by that Contributor with its Contributor + Version (or portions of such combination). + + (c) the licenses granted in Sections 2.2(a) and 2.2(b) are + effective on the date Contributor first makes Commercial Use of + the Covered Code. + + (d) Notwithstanding Section 2.2(b) above, no patent license is + granted: 1) for any code that Contributor has deleted from the + Contributor Version; 2) separate from the Contributor Version; + 3) for infringements caused by: i) third party modifications of + Contributor Version or ii) the combination of Modifications made + by that Contributor with other software (except as part of the + Contributor Version) or other devices; or 4) under Patent Claims + infringed by Covered Code in the absence of Modifications made by + that Contributor. + +3. Distribution Obligations. + + 3.1. Application of License. + The Modifications which You create or to which You contribute are + governed by the terms of this License, including without limitation + Section 2.2. The Source Code version of Covered Code may be + distributed only under the terms of this License or a future version + of this License released under Section 6.1, and You must include a + copy of this License with every copy of the Source Code You + distribute. You may not offer or impose any terms on any Source Code + version that alters or restricts the applicable version of this + License or the recipients' rights hereunder. However, You may include + an additional document offering the additional rights described in + Section 3.5. + + 3.2. Availability of Source Code. + Any Modification which You create or to which You contribute must be + made available in Source Code form under the terms of this License + either on the same media as an Executable version or via an accepted + Electronic Distribution Mechanism to anyone to whom you made an + Executable version available; and if made available via Electronic + Distribution Mechanism, must remain available for at least twelve (12) + months after the date it initially became available, or at least six + (6) months after a subsequent version of that particular Modification + has been made available to such recipients. You are responsible for + ensuring that the Source Code version remains available even if the + Electronic Distribution Mechanism is maintained by a third party. + + 3.3. Description of Modifications. + You must cause all Covered Code to which You contribute to contain a + file documenting the changes You made to create that Covered Code and + the date of any change. You must include a prominent statement that + the Modification is derived, directly or indirectly, from Original + Code provided by the Initial Developer and including the name of the + Initial Developer in (a) the Source Code, and (b) in any notice in an + Executable version or related documentation in which You describe the + origin or ownership of the Covered Code. + + 3.4. Intellectual Property Matters + (a) Third Party Claims. + If Contributor has knowledge that a license under a third party's + intellectual property rights is required to exercise the rights + granted by such Contributor under Sections 2.1 or 2.2, + Contributor must include a text file with the Source Code + distribution titled "LEGAL" which describes the claim and the + party making the claim in sufficient detail that a recipient will + know whom to contact. If Contributor obtains such knowledge after + the Modification is made available as described in Section 3.2, + Contributor shall promptly modify the LEGAL file in all copies + Contributor makes available thereafter and shall take other steps + (such as notifying appropriate mailing lists or newsgroups) + reasonably calculated to inform those who received the Covered + Code that new knowledge has been obtained. + + (b) Contributor APIs. + If Contributor's Modifications include an application programming + interface and Contributor has knowledge of patent licenses which + are reasonably necessary to implement that API, Contributor must + also include this information in the LEGAL file. + + (c) Representations. + Contributor represents that, except as disclosed pursuant to + Section 3.4(a) above, Contributor believes that Contributor's + Modifications are Contributor's original creation(s) and/or + Contributor has sufficient rights to grant the rights conveyed by + this License. + + 3.5. Required Notices. + You must duplicate the notice in Exhibit A in each file of the Source + Code. If it is not possible to put such notice in a particular Source + Code file due to its structure, then You must include such notice in a + location (such as a relevant directory) where a user would be likely + to look for such a notice. If You created one or more Modification(s) + You may add your name as a Contributor to the notice described in + Exhibit A. You must also duplicate this License in any documentation + for the Source Code where You describe recipients' rights or ownership + rights relating to Covered Code. You may choose to offer, and to + charge a fee for, warranty, support, indemnity or liability + obligations to one or more recipients of Covered Code. However, You + may do so only on Your own behalf, and not on behalf of the Initial + Developer or any Contributor. You must make it absolutely clear than + any such warranty, support, indemnity or liability obligation is + offered by You alone, and You hereby agree to indemnify the Initial + Developer and every Contributor for any liability incurred by the + Initial Developer or such Contributor as a result of warranty, + support, indemnity or liability terms You offer. + + 3.6. Distribution of Executable Versions. + You may distribute Covered Code in Executable form only if the + requirements of Section 3.1-3.5 have been met for that Covered Code, + and if You include a notice stating that the Source Code version of + the Covered Code is available under the terms of this License, + including a description of how and where You have fulfilled the + obligations of Section 3.2. The notice must be conspicuously included + in any notice in an Executable version, related documentation or + collateral in which You describe recipients' rights relating to the + Covered Code. You may distribute the Executable version of Covered + Code or ownership rights under a license of Your choice, which may + contain terms different from this License, provided that You are in + compliance with the terms of this License and that the license for the + Executable version does not attempt to limit or alter the recipient's + rights in the Source Code version from the rights set forth in this + License. If You distribute the Executable version under a different + license You must make it absolutely clear that any terms which differ + from this License are offered by You alone, not by the Initial + Developer or any Contributor. You hereby agree to indemnify the + Initial Developer and every Contributor for any liability incurred by + the Initial Developer or such Contributor as a result of any such + terms You offer. + + 3.7. Larger Works. + You may create a Larger Work by combining Covered Code with other code + not governed by the terms of this License and distribute the Larger + Work as a single product. In such a case, You must make sure the + requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + + If it is impossible for You to comply with any of the terms of this + License with respect to some or all of the Covered Code due to + statute, judicial order, or regulation then You must: (a) comply with + the terms of this License to the maximum extent possible; and (b) + describe the limitations and the code they affect. Such description + must be included in the LEGAL file described in Section 3.4 and must + be included with all distributions of the Source Code. Except to the + extent prohibited by statute or regulation, such description must be + sufficiently detailed for a recipient of ordinary skill to be able to + understand it. + +5. Application of this License. + + This License applies to code to which the Initial Developer has + attached the notice in Exhibit A and to related Covered Code. + +6. Versions of the License. + + 6.1. New Versions. + Netscape Communications Corporation ("Netscape") may publish revised + and/or new versions of the License from time to time. Each version + will be given a distinguishing version number. + + 6.2. Effect of New Versions. + Once Covered Code has been published under a particular version of the + License, You may always continue to use it under the terms of that + version. You may also choose to use such Covered Code under the terms + of any subsequent version of the License published by Netscape. No one + other than Netscape has the right to modify the terms applicable to + Covered Code created under this License. + + 6.3. Derivative Works. + If You create or use a modified version of this License (which you may + only do in order to apply it to code which is not already Covered Code + governed by this License), You must (a) rename Your license so that + the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", + "MPL", "NPL" or any confusingly similar phrase do not appear in your + license (except to note that your license differs from this License) + and (b) otherwise make it clear that Your version of the license + contains terms which differ from the Mozilla Public License and + Netscape Public License. (Filling in the name of the Initial + Developer, Original Code or Contributor in the notice described in + Exhibit A shall not of themselves be deemed to be modifications of + this License.) + +7. DISCLAIMER OF WARRANTY. + + COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, + WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF + DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. + THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE + IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE + COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF + ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + + 8.1. This License and the rights granted hereunder will terminate + automatically if You fail to comply with terms herein and fail to cure + such breach within 30 days of becoming aware of the breach. All + sublicenses to the Covered Code which are properly granted shall + survive any termination of this License. Provisions which, by their + nature, must remain in effect beyond the termination of this License + shall survive. + + 8.2. If You initiate litigation by asserting a patent infringement + claim (excluding declatory judgment actions) against Initial Developer + or a Contributor (the Initial Developer or Contributor against whom + You file such action is referred to as "Participant") alleging that: + + (a) such Participant's Contributor Version directly or indirectly + infringes any patent, then any and all rights granted by such + Participant to You under Sections 2.1 and/or 2.2 of this License + shall, upon 60 days notice from Participant terminate prospectively, + unless if within 60 days after receipt of notice You either: (i) + agree in writing to pay Participant a mutually agreeable reasonable + royalty for Your past and future use of Modifications made by such + Participant, or (ii) withdraw Your litigation claim with respect to + the Contributor Version against such Participant. If within 60 days + of notice, a reasonable royalty and payment arrangement are not + mutually agreed upon in writing by the parties or the litigation claim + is not withdrawn, the rights granted by Participant to You under + Sections 2.1 and/or 2.2 automatically terminate at the expiration of + the 60 day notice period specified above. + + (b) any software, hardware, or device, other than such Participant's + Contributor Version, directly or indirectly infringes any patent, then + any rights granted to You by such Participant under Sections 2.1(b) + and 2.2(b) are revoked effective as of the date You first made, used, + sold, distributed, or had made, Modifications made by that + Participant. + + 8.3. If You assert a patent infringement claim against Participant + alleging that such Participant's Contributor Version directly or + indirectly infringes any patent where such claim is resolved (such as + by license or settlement) prior to the initiation of patent + infringement litigation, then the reasonable value of the licenses + granted by such Participant under Sections 2.1 or 2.2 shall be taken + into account in determining the amount or value of any payment or + license. + + 8.4. In the event of termination under Sections 8.1 or 8.2 above, + all end user license agreements (excluding distributors and resellers) + which have been validly granted by You or any distributor hereunder + prior to termination shall survive termination. + +9. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT + (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL + DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, + OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR + ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY + CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, + WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER + COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN + INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF + LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY + RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW + PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE + EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO + THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + + The Covered Code is a "commercial item," as that term is defined in + 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer + software" and "commercial computer software documentation," as such + terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 + C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), + all U.S. Government End Users acquire Covered Code with only those + rights set forth herein. + +11. MISCELLANEOUS. + + This License represents the complete agreement concerning subject + matter hereof. If any provision of this License is held to be + unenforceable, such provision shall be reformed only to the extent + necessary to make it enforceable. This License shall be governed by + California law provisions (except to the extent applicable law, if + any, provides otherwise), excluding its conflict-of-law provisions. + With respect to disputes in which at least one party is a citizen of, + or an entity chartered or registered to do business in the United + States of America, any litigation relating to this License shall be + subject to the jurisdiction of the Federal Courts of the Northern + District of California, with venue lying in Santa Clara County, + California, with the losing party responsible for costs, including + without limitation, court costs and reasonable attorneys' fees and + expenses. The application of the United Nations Convention on + Contracts for the International Sale of Goods is expressly excluded. + Any law or regulation which provides that the language of a contract + shall be construed against the drafter shall not apply to this + License. + +12. RESPONSIBILITY FOR CLAIMS. + + As between Initial Developer and the Contributors, each party is + responsible for claims and damages arising, directly or indirectly, + out of its utilization of rights under this License and You agree to + work with Initial Developer and Contributors to distribute such + responsibility on an equitable basis. Nothing herein is intended or + shall be deemed to constitute any admission of liability. + +13. MULTIPLE-LICENSED CODE. + + Initial Developer may designate portions of the Covered Code as + "Multiple-Licensed". "Multiple-Licensed" means that the Initial + Developer permits you to utilize portions of the Covered Code under + Your choice of the NPL or the alternative licenses, if any, specified + by the Initial Developer in the file described in Exhibit A. + +EXHIBIT A -Mozilla Public License. + + ``The contents of this file are subject to the Mozilla Public License + Version 1.1 (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.mozilla.org/MPL/ + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the + License for the specific language governing rights and limitations + under the License. + + The Original Code is ______________________________________. + + The Initial Developer of the Original Code is ________________________. + Portions created by ______________________ are Copyright (C) ______ + _______________________. All Rights Reserved. + + Contributor(s): ______________________________________. + + Alternatively, the contents of this file may be used under the terms + of the _____ license (the "[___] License"), in which case the + provisions of [______] License are applicable instead of those + above. If you wish to allow use of your version of this file only + under the terms of the [____] License and not to allow others to use + your version of this file under the MPL, indicate your decision by + deleting the provisions above and replace them with the notice and + other provisions required by the [___] License. If you do not delete + the provisions above, a recipient may use your version of this file + under either the MPL or the [___] License." + + [NOTE: The text of this Exhibit A may differ slightly from the text of + the notices in the Source Code files of the Original Code. You should + use the text of this Exhibit A rather than the text found in the + Original Code Source Code for Your Modifications.] + + +=============================================================================== + +The Groovy file: + groovy-all-minimal-1.5.4.jar +is redistributed in executable form and is licensed under the following terms: + +/* + $Id: LICENSE.txt 156 2003-09-26 17:36:37Z jstrachan $ + + Copyright 2003 (C) James Strachan and Bob Mcwhirter. All Rights Reserved. + + Redistribution and use of this software and associated documentation + ("Software"), with or without modification, are permitted provided + that the following conditions are met: + + 1. Redistributions of source code must retain copyright + statements and notices. Redistributions must also contain a + copy of this document. + + 2. Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and the + following disclaimer in the documentation and/or other + materials provided with the distribution. + + 3. The name "groovy" must not be used to endorse or promote + products derived from this Software without prior written + permission of The Codehaus. For written permission, + please contact info@codehaus.org. + + 4. Products derived from this Software may not be called "groovy" + nor may "groovy" appear in their names without prior written + permission of The Codehaus. "groovy" is a registered + trademark of The Codehaus. + + 5. Due credit should be given to The Codehaus - + http://groovy.codehaus.org/ + + THIS SOFTWARE IS PROVIDED BY THE CODEHAUS AND CONTRIBUTORS + ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT + NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL + THE CODEHAUS OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED + OF THE POSSIBILITY OF SUCH DAMAGE. + + */ + +=============================================================================== + +The Jython file: + jython-2.2.jar +is redistributed in executable form and is licensed under the following terms: + +A. HISTORY OF THE SOFTWARE +======================= + +JPython was created in late 1997 by Jim Hugunin. Jim was also the +primary developer while he was at CNRI. In February 1999 Barry Warsaw +took over as primary developer and released JPython version 1.1. + +In October 2000 Barry helped move the software to SourceForge +where it was renamed to Jython. Jython 2.0 and on are licensed under +the Jython specific license below. + +The standard library is covered by the Python Software Foundation +license. See the LICENSE_CPython.txt file for details. + +The zxJDBC package was written by Brian Zimmer and originally licensed +under the GNU Public License. The package is now covered by the Jython +Software License. + +The command line interpreter is covered by the Apache Software +License. See the LICENSE_Apache.txt file for details. + +B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING JYTHON +================================ + +Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Jython Developers +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + + - Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + - Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in + the documentation and/or other materials provided with the distribution. + + - Neither the name of the Jython Developers nor the names of + its contributors may be used to endorse or promote products + derived from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR +A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR +CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY +OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + + + + +JPython 1.1.x Software License. +========================= + +______________________________________________________________________ + +IMPORTANT: PLEASE READ THE FOLLOWING AGREEMENT CAREFULLY. + +BY CLICKING ON THE "ACCEPT" BUTTON WHERE INDICATED, OR BY INSTALLING, +COPYING OR OTHERWISE USING THE SOFTWARE, YOU ARE DEEMED TO HAVE AGREED TO +THE TERMS AND CONDITIONS OF THIS AGREEMENT. + +______________________________________________________________________ + +JPython version 1.1.x + + 1. This LICENSE AGREEMENT is between the Corporation for National Research + Initiatives, having an office at 1895 Preston White Drive, Reston, VA + 20191 ("CNRI"), and the Individual or Organization ("Licensee") + accessing and using JPython version 1.1.x in source or binary form and + its associated documentation as provided herein ("Software"). + + 2. Subject to the terms and conditions of this License Agreement, CNRI + hereby grants Licensee a non-exclusive, non-transferable, royalty-free, + world-wide license to reproduce, analyze, test, perform and/or display + publicly, prepare derivative works, distribute, and otherwise use the + Software alone or in any derivative version, provided, however, that + CNRI's License Agreement and CNRI's notice of copyright, i.e., + "Copyright ©1996-1999 Corporation for National Research Initiatives; + All Rights Reserved" are both retained in the Software, alone or in any + derivative version prepared by Licensee. + + Alternatively, in lieu of CNRI's License Agreement, Licensee may + substitute the following text (omitting the quotes), provided, however, + that such text is displayed prominently in the Software alone or in any + derivative version prepared by Licensee: "JPython (Version 1.1.x) is + made available subject to the terms and conditions in CNRI's License + Agreement. This Agreement may be located on the Internet using the + following unique, persistent identifier (known as a handle): + 1895.22/1006. The License may also be obtained from a proxy server on + the Web using the following URL: http://hdl.handle.net/1895.22/1006." + + 3. In the event Licensee prepares a derivative work that is based on or + incorporates the Software or any part thereof, and wants to make the + derivative work available to the public as provided herein, then + Licensee hereby agrees to indicate in any such work, in a prominently + visible way, the nature of the modifications made to CNRI's Software. + + 4. Licensee may not use CNRI trademarks or trade name, including JPython + or CNRI, in a trademark sense to endorse or promote products or + services of Licensee, or any third party. Licensee may use the mark + JPython in connection with Licensee's derivative versions that are + based on or incorporate the Software, but only in the form + "JPython-based ___________________," or equivalent. + + 5. CNRI is making the Software available to Licensee on an "AS IS" basis. + CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY + OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY + REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY + PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE + ANY THIRD PARTY RIGHTS. + + 6. CNRI SHALL NOT BE LIABLE TO LICENSEE OR OTHER USERS OF THE SOFTWARE FOR + ANY INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF + USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE + THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. SOME STATES DO NOT + ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY SO THE ABOVE DISCLAIMER + MAY NOT APPLY TO LICENSEE. + + 7. This License Agreement may be terminated by CNRI (i) immediately upon + written notice from CNRI of any material breach by the Licensee, if the + nature of the breach is such that it cannot be promptly remedied; or + (ii) sixty (60) days following notice from CNRI to Licensee of a + material remediable breach, if Licensee has not remedied such breach + within that sixty-day period. + + 8. This License Agreement shall be governed by and interpreted in all + respects by the law of the State of Virginia, excluding conflict of law + provisions. Nothing in this Agreement shall be deemed to create any + relationship of agency, partnership, or joint venture between CNRI and + Licensee. + + 9. By clicking on the "ACCEPT" button where indicated, or by installing, + copying or otherwise using the Software, Licensee agrees to be bound by + the terms and conditions of this License Agreement. + + +=============================================================================== + +The files: + activation-1.1.jar, + jaxb-api-2.1.jar, + jaxb-impl-2.1.7.jar, + jaxb-xjc-2.1.7.jar, + jsr181-api-1.0-MR1.jar, + jsr250-api-1.0.jar, + jaxws-api-2.1.jar, + servlet-api-2.5.jar, + stax-api-1.0-2.jar +are redistributed in executable form, with source code available at + https://jax-ws-sources.dev.java.net/source/browse/jax-ws-sources/ + https://jaxb2-sources.dev.java.net/ +and are subject to the following copyright and license: + + Copyright (c) 2006, Sun Microsystems, Inc. + +COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0 + + + 1. Definitions. + + 1.1. "Contributor" means each individual or entity that + creates or contributes to the creation of Modifications. + + 1.2. "Contributor Version" means the combination of the + Original Software, prior Modifications used by a + Contributor (if any), and the Modifications made by that + particular Contributor. + + 1.3. "Covered Software" means (a) the Original Software, or + (b) Modifications, or (c) the combination of files + containing Original Software with files containing + Modifications, in each case including portions thereof. + + 1.4. "Executable" means the Covered Software in any form + other than Source Code. + + 1.5. "Initial Developer" means the individual or entity + that first makes Original Software available under this + License. + + 1.6. "Larger Work" means a work which combines Covered + Software or portions thereof with code not governed by the + terms of this License. + + 1.7. "License" means this document. + + 1.8. "Licensable" means having the right to grant, to the + maximum extent possible, whether at the time of the initial + grant or subsequently acquired, any and all of the rights + conveyed herein. + + 1.9. "Modifications" means the Source Code and Executable + form of any of the following: + + A. Any file that results from an addition to, + deletion from or modification of the contents of a + file containing Original Software or previous + Modifications; + + B. Any new file that contains any part of the + Original Software or previous Modification; or + + C. Any new file that is contributed or otherwise made + available under the terms of this License. + + 1.10. "Original Software" means the Source Code and + Executable form of computer software code that is + originally released under this License. + + 1.11. "Patent Claims" means any patent claim(s), now owned + or hereafter acquired, including without limitation, + method, process, and apparatus claims, in any patent + Licensable by grantor. + + 1.12. "Source Code" means (a) the common form of computer + software code in which modifications are made and (b) + associated documentation included in or with such code. + + 1.13. "You" (or "Your") means an individual or a legal + entity exercising rights under, and complying with all of + the terms of, this License. For legal entities, "You" + includes any entity which controls, is controlled by, or is + under common control with You. For purposes of this + definition, "control" means (a) the power, direct or + indirect, to cause the direction or management of such + entity, whether by contract or otherwise, or (b) ownership + of more than fifty percent (50%) of the outstanding shares + or beneficial ownership of such entity. + + 2. License Grants. + + 2.1. The Initial Developer Grant. + + Conditioned upon Your compliance with Section 3.1 below and + subject to third party intellectual property claims, the + Initial Developer hereby grants You a world-wide, + royalty-free, non-exclusive license: + + (a) under intellectual property rights (other than + patent or trademark) Licensable by Initial Developer, + to use, reproduce, modify, display, perform, + sublicense and distribute the Original Software (or + portions thereof), with or without Modifications, + and/or as part of a Larger Work; and + + (b) under Patent Claims infringed by the making, + using or selling of Original Software, to make, have + made, use, practice, sell, and offer for sale, and/or + otherwise dispose of the Original Software (or + portions thereof). + + (c) The licenses granted in Sections 2.1(a) and (b) + are effective on the date Initial Developer first + distributes or otherwise makes the Original Software + available to a third party under the terms of this + License. + + (d) Notwithstanding Section 2.1(b) above, no patent + license is granted: (1) for code that You delete from + the Original Software, or (2) for infringements + caused by: (i) the modification of the Original + Software, or (ii) the combination of the Original + Software with other software or devices. + + 2.2. Contributor Grant. + + Conditioned upon Your compliance with Section 3.1 below and + subject to third party intellectual property claims, each + Contributor hereby grants You a world-wide, royalty-free, + non-exclusive license: + + (a) under intellectual property rights (other than + patent or trademark) Licensable by Contributor to + use, reproduce, modify, display, perform, sublicense + and distribute the Modifications created by such + Contributor (or portions thereof), either on an + unmodified basis, with other Modifications, as + Covered Software and/or as part of a Larger Work; and + + + (b) under Patent Claims infringed by the making, + using, or selling of Modifications made by that + Contributor either alone and/or in combination with + its Contributor Version (or portions of such + combination), to make, use, sell, offer for sale, + have made, and/or otherwise dispose of: (1) + Modifications made by that Contributor (or portions + thereof); and (2) the combination of Modifications + made by that Contributor with its Contributor Version + (or portions of such combination). + + (c) The licenses granted in Sections 2.2(a) and + 2.2(b) are effective on the date Contributor first + distributes or otherwise makes the Modifications + available to a third party. + + (d) Notwithstanding Section 2.2(b) above, no patent + license is granted: (1) for any code that Contributor + has deleted from the Contributor Version; (2) for + infringements caused by: (i) third party + modifications of Contributor Version, or (ii) the + combination of Modifications made by that Contributor + with other software (except as part of the + Contributor Version) or other devices; or (3) under + Patent Claims infringed by Covered Software in the + absence of Modifications made by that Contributor. + + 3. Distribution Obligations. + + 3.1. Availability of Source Code. + + Any Covered Software that You distribute or otherwise make + available in Executable form must also be made available in + Source Code form and that Source Code form must be + distributed only under the terms of this License. You must + include a copy of this License with every copy of the + Source Code form of the Covered Software You distribute or + otherwise make available. You must inform recipients of any + such Covered Software in Executable form as to how they can + obtain such Covered Software in Source Code form in a + reasonable manner on or through a medium customarily used + for software exchange. + + 3.2. Modifications. + + The Modifications that You create or to which You + contribute are governed by the terms of this License. You + represent that You believe Your Modifications are Your + original creation(s) and/or You have sufficient rights to + grant the rights conveyed by this License. + + 3.3. Required Notices. + + You must include a notice in each of Your Modifications + that identifies You as the Contributor of the Modification. + You may not remove or alter any copyright, patent or + trademark notices contained within the Covered Software, or + any notices of licensing or any descriptive text giving + attribution to any Contributor or the Initial Developer. + + 3.4. Application of Additional Terms. + + You may not offer or impose any terms on any Covered + Software in Source Code form that alters or restricts the + applicable version of this License or the recipients' + rights hereunder. You may choose to offer, and to charge a + fee for, warranty, support, indemnity or liability + obligations to one or more recipients of Covered Software. + However, you may do so only on Your own behalf, and not on + behalf of the Initial Developer or any Contributor. You + must make it absolutely clear that any such warranty, + support, indemnity or liability obligation is offered by + You alone, and You hereby agree to indemnify the Initial + Developer and every Contributor for any liability incurred + by the Initial Developer or such Contributor as a result of + warranty, support, indemnity or liability terms You offer. + + + 3.5. Distribution of Executable Versions. + + You may distribute the Executable form of the Covered + Software under the terms of this License or under the terms + of a license of Your choice, which may contain terms + different from this License, provided that You are in + compliance with the terms of this License and that the + license for the Executable form does not attempt to limit + or alter the recipient's rights in the Source Code form + from the rights set forth in this License. If You + distribute the Covered Software in Executable form under a + different license, You must make it absolutely clear that + any terms which differ from this License are offered by You + alone, not by the Initial Developer or Contributor. You + hereby agree to indemnify the Initial Developer and every + Contributor for any liability incurred by the Initial + Developer or such Contributor as a result of any such terms + You offer. + + 3.6. Larger Works. + + You may create a Larger Work by combining Covered Software + with other code not governed by the terms of this License + and distribute the Larger Work as a single product. In such + a case, You must make sure the requirements of this License + are fulfilled for the Covered Software. + + 4. Versions of the License. + + 4.1. New Versions. + + Sun Microsystems, Inc. is the initial license steward and + may publish revised and/or new versions of this License + from time to time. Each version will be given a + distinguishing version number. Except as provided in + Section 4.3, no one other than the license steward has the + right to modify this License. + + 4.2. Effect of New Versions. + + You may always continue to use, distribute or otherwise + make the Covered Software available under the terms of the + version of the License under which You originally received + the Covered Software. If the Initial Developer includes a + notice in the Original Software prohibiting it from being + distributed or otherwise made available under any + subsequent version of the License, You must distribute and + make the Covered Software available under the terms of the + version of the License under which You originally received + the Covered Software. Otherwise, You may also choose to + use, distribute or otherwise make the Covered Software + available under the terms of any subsequent version of the + License published by the license steward. + + 4.3. Modified Versions. + + When You are an Initial Developer and You want to create a + new license for Your Original Software, You may create and + use a modified version of this License if You: (a) rename + the license and remove any references to the name of the + license steward (except to note that the license differs + from this License); and (b) otherwise make it clear that + the license contains terms which differ from this License. + + + 5. DISCLAIMER OF WARRANTY. + + COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" + BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, + INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED + SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR + PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND + PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY + COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE + INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF + ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF + WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF + ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS + DISCLAIMER. + + 6. TERMINATION. + + 6.1. This License and the rights granted hereunder will + terminate automatically if You fail to comply with terms + herein and fail to cure such breach within 30 days of + becoming aware of the breach. Provisions which, by their + nature, must remain in effect beyond the termination of + this License shall survive. + + 6.2. If You assert a patent infringement claim (excluding + declaratory judgment actions) against Initial Developer or + a Contributor (the Initial Developer or Contributor against + whom You assert such claim is referred to as "Participant") + alleging that the Participant Software (meaning the + Contributor Version where the Participant is a Contributor + or the Original Software where the Participant is the + Initial Developer) directly or indirectly infringes any + patent, then any and all rights granted directly or + indirectly to You by such Participant, the Initial + Developer (if the Initial Developer is not the Participant) + and all Contributors under Sections 2.1 and/or 2.2 of this + License shall, upon 60 days notice from Participant + terminate prospectively and automatically at the expiration + of such 60 day notice period, unless if within such 60 day + period You withdraw Your claim with respect to the + Participant Software against such Participant either + unilaterally or pursuant to a written agreement with + Participant. + + 6.3. In the event of termination under Sections 6.1 or 6.2 + above, all end user licenses that have been validly granted + by You or any distributor hereunder prior to termination + (excluding licenses granted to You by any distributor) + shall survive termination. + + 7. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT + (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE + INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF + COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE + LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR + CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT + LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK + STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER + COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN + INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF + LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL + INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT + APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO + NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR + CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT + APPLY TO YOU. + + 8. U.S. GOVERNMENT END USERS. + + The Covered Software is a "commercial item," as that term is + defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial + computer software" (as that term is defined at 48 C.F.R. + 252.227-7014(a)(1)) and "commercial computer software + documentation" as such terms are used in 48 C.F.R. 12.212 (Sept. + 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 + through 227.7202-4 (June 1995), all U.S. Government End Users + acquire Covered Software with only those rights set forth herein. + This U.S. Government Rights clause is in lieu of, and supersedes, + any other FAR, DFAR, or other clause or provision that addresses + Government rights in computer software under this License. + + 9. MISCELLANEOUS. + + This License represents the complete agreement concerning subject + matter hereof. If any provision of this License is held to be + unenforceable, such provision shall be reformed only to the + extent necessary to make it enforceable. This License shall be + governed by the law of the jurisdiction specified in a notice + contained within the Original Software (except to the extent + applicable law, if any, provides otherwise), excluding such + jurisdiction's conflict-of-law provisions. Any litigation + relating to this License shall be subject to the jurisdiction of + the courts located in the jurisdiction and venue specified in a + notice contained within the Original Software, with the losing + party responsible for costs, including, without limitation, court + costs and reasonable attorneys' fees and expenses. The + application of the United Nations Convention on Contracts for the + International Sale of Goods is expressly excluded. Any law or + regulation which provides that the language of a contract shall + be construed against the drafter shall not apply to this License. + You agree that You alone are responsible for compliance with the + United States export administration regulations (and the export + control laws and regulation of any other countries) when You use, + distribute or otherwise make available any Covered Software. + + 10. RESPONSIBILITY FOR CLAIMS. + + As between Initial Developer and the Contributors, each party is + responsible for claims and damages arising, directly or + indirectly, out of its utilization of rights under this License + and You agree to work with Initial Developer and Contributors to + distribute such responsibility on an equitable basis. Nothing + herein is intended or shall be deemed to constitute any admission + of liability. + +=============================================================================== + +The JRuby file: + jruby-complete-1.1.3.jar +and wsdl4j file: + wsdl4j-1.6.2.jar +are redistributed in executable form, with source code available at + http://jruby.org/ + http://sourceforge.net/projects/wsdl4j/ +and are licensed under the following terms: + +Common Public License - v 1.0 + +THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. + +1. DEFINITIONS + +"Contribution" means: + + a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and + b) in the case of each subsequent Contributor: + + i) changes to the Program, and + + ii) additions to the Program; + + where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program. + +"Contributor" means any person or entity that distributes the Program. + +"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. + +"Program" means the Contributions distributed in accordance with this Agreement. + +"Recipient" means anyone who receives the Program under this Agreement, including all Contributors. + +2. GRANT OF RIGHTS + + a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form. + + b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder. + + c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program. + + d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. + +3. REQUIREMENTS + +A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that: + + a) it complies with the terms and conditions of this Agreement; and + + b) its license agreement: + + i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; + + ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; + + iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and + + iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange. + +When the Program is made available in source code form: + + a) it must be made available under this Agreement; and + + b) a copy of this Agreement must be included with each copy of the Program. + +Contributors may not remove or alter any copyright notices contained within the Program. + +Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. + +4. COMMERCIAL DISTRIBUTION + +Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense. + +For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages. + +5. NO WARRANTY + +EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. + +6. DISCLAIMER OF LIABILITY + +EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +7. GENERAL + +If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. + +If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. + +All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. + +Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved. + +This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation. + +=============================================================================== + +The file: + backport-util-concurrent-3.1.jar +is redistributed in executable form and is licensed under the following terms: + +The software comprising backport-util-concurrent is based in large +part on the code from JSR166, and the package dl.util.concurrent. +The software has been released to the public domain, as explained at: +http://creativecommons.org/licenses/publicdomain, excepting portions +of the class +edu.emory.mathcs.backport.java.util.concurrent.CopyOnWriteArrayList, +which were adapted from class java.util.ArrayList, written by Sun +Microsystems, Inc, which are used with kind permission, and subject +to the following: + +Copyright 2002-2004 Sun Microsystems, Inc. All rights reserved. Use is +subject to the following license terms. + + "Sun hereby grants you a non-exclusive, worldwide, non-transferrable + license to use and distribute the Java Software technologies as part + of a larger work in source and binary forms, with or without + modification, provided that the following conditions are met: + + -Neither the name of or trademarks of Sun may be used to endorse or + promote products derived from the Java Software technology without + specific prior written permission. + + -Redistributions of source or binary code must be accompanied by the + following notice and disclaimers: + + Portions copyright Sun Microsystems, Inc. Used with kind permission. + + This software is provided AS IS, without a warranty of any kind. ALL + EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND + WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PUPOSE OR + NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN + MICROSYSTEMS, INC. AND ITS LICENSORS SHALL NOT BE LIABLE + FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF + USING, MODIFYING OR DISTRIBUTING THE SOFTWARE OR ITS + DERIVATIVES. IN NO EVENT WILL SUN MICROSYSTEMS, INC. OR + ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR + DATA, OR FOR DIRECT, INDIRECT,CONSQUENTIAL, INCIDENTAL + OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF + THE THEORY OR LIABILITY, ARISING OUT OF THE USE OF OR + INABILITY TO USE SOFTWARE, EVEN IF SUN MICROSYSTEMS, INC. + HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + + You acknowledge that Software is not designed, licensed or intended for + use in the design, construction, operation or maintenance of any nuclear + facility." + +=============================================================================== + +The file: + rome-0.9.jar +is redistributed in executable form under the Apache 2.0 license with the following copyright: + +Copyright 2004 Sun Microsystems, Inc. + +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. + +=============================================================================== + +The file: + jdom-1.0.jar +is redistributed in executable form and is licensed under the following terms: + +$Id: LICENSE.txt,v 1.11 2004/02/06 09:32:57 jhunter Exp $ + + Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions, and the following disclaimer. + + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions, and the disclaimer that follows + these conditions in the documentation and/or other materials + provided with the distribution. + + 3. The name "JDOM" must not be used to endorse or promote products + derived from this software without prior written permission. For + written permission, please contact <request_AT_jdom_DOT_org>. + + 4. Products derived from this software may not be called "JDOM", nor + may "JDOM" appear in their name, without prior written permission + from the JDOM Project Management <request_AT_jdom_DOT_org>. + + In addition, we request (but do not require) that you include in the + end-user documentation provided with the redistribution and/or in the + software itself an acknowledgement equivalent to the following: + "This product includes software developed by the + JDOM Project (http://www.jdom.org/)." + Alternatively, the acknowledgment may be graphical using the logos + available at http://www.jdom.org/images/logos. + + THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED + WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT + CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND + ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, + OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT + OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + SUCH DAMAGE. + + This software consists of voluntary contributions made by many + individuals on behalf of the JDOM Project and was originally + created by Jason Hunter <jhunter_AT_jdom_DOT_org> and + Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information + on the JDOM Project, please see <http://www.jdom.org/>. + +======================================================================== + +The file: + dwr-2.0.3.jar +is redistributed in executable form and is licensed under the following terms: + +/* +* Copyright 2005 Joe Walker +* +* 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. +*/ + +================================================================================ + +The file: + serp-1.12.0.jar +is redistributed in executable form under the BSD license with the following copyright: + + Copyright (c) 2002, A. Abram White + All rights reserved. + +BSD license: + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are met: + + - Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + + - Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + + - Neither the name of the Sun Microsystems, Inc. nor the names of + contributors may be used to endorse or promote products derived from this + software without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED + WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A + PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY + DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, + PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE + OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH + DAMAGE. + +================================================================================ + +The file: + javacc-3.2.jar +is redistributed in executable form under the following copyright and BSD license: + +Copyright (c) 2003 Sun Microsystems, Inc. All Rights Reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR +CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +================================================================================ + +The file: + howl-1.0.1-1.jar +is redistributed in executable form under the following copyright and BSD license: + +Copyright (c) 2004, Bull S.A. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR +CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +================================================================================ + +The file: + tuscany-sdo-api-r2.1-1.1.1.jar +is redistributed in executable form and is licensed under the following terms: + +(c) Copyright BEA Systems, Inc., International Business Machines Corporation, +Oracle Corporation, Primeton Technologies Ltd., Rogue Wave Software, SAP AG., +Software AG., Sun Microsystems, Sybase Inc., Xcalia, Zend Technologies, +2005, 2006. All rights reserved. + +License for the Service Data Objects JavaDoc and Interface Definition files. (tuscany-sdo-api-r2.1-1.1.1.jar) + +These files being ... +commonj/sdo/ChangeSummary$Setting.class +commonj/sdo/ChangeSummary.class +commonj/sdo/DataGraph.class +commonj/sdo/DataObject.class +commonj/sdo/helper/CopyHelper.class +commonj/sdo/helper/DataFactory.class +commonj/sdo/helper/DataHelper.class +commonj/sdo/helper/EqualityHelper.class +commonj/sdo/helper/HelperContext.class +commonj/sdo/helper/TypeHelper.class +commonj/sdo/helper/XMLDocument.class +commonj/sdo/helper/XMLHelper.class +commonj/sdo/helper/XSDHelper.class +commonj/sdo/impl/ExternalizableDelegator$Resolvable.class +commonj/sdo/impl/ExternalizableDelegator.class +commonj/sdo/Property.class +commonj/sdo/Sequence.class +commonj/sdo/Type.class +xml/datagraph.xsd +xml/sdoJava.xml +xml/sdoJava.xsd +xml/sdoModel.xml +xml/sdoModel.xsd +xml/sdoXML.xml +xml/sdoXML.xsd + + +License for the Service Data Objects JavaDoc and Interface Definition files. + +The Service Data Objects Specification is being provided by the copyright holders under the following +license. By using and/or copying this work, you agree that you have read, understood and will comply with +the following terms and conditions: + +Permission to copy, display and distribute the Service Data Objects Specification and/or portions thereof, without +modification, in any medium without fee or royalty is hereby granted, provided that you include the +following on ALL copies of the Service Data Objects Specification, or portions thereof, that you make: + +1. A link or URL to the Service Data Objects Specification at this location: +http://www.osoa.org/display/Main/Service+Data+Objects+Specifications + +2. The full text of this copyright notice as shown in the Service Data Objects Specification. + +BEA, IBM, Oracle, Primeton Technologies, Rogue Wave Software, SAP, Software AG, Sun Microsystems, Xcalia, +Zend Technologies (collectively, the “Authors”) agree to grant you a royalty-free license, under reasonable, +non-discriminatory terms and conditions to patents that they deem necessary to implement the Service Data +Objects Specification. + +THE Service Data Objects SPECIFICATION IS PROVIDED "AS IS," AND THE AUTHORS MAKE NO REPRESENTATIONS OR +WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SPECIFICATION AND THE IMPLEMENTATION OF ITS CONTENTS, +INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, +NON-INFRINGEMENT OR TITLE. THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL +OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY USE OR DISTRIBUTION OF THE SERVICE DATA OBJECTS +SPECIFICATION. + +The name and trademarks of the Authors may NOT be used in any manner, including advertising or publicity +pertaining to the Service Data Objects Specification or its contents without specific, written prior +permission. Title to copyright in the Service Data Objects Specification will at all times remain with the +Authors. + +No other rights are granted by implication, estoppel or otherwise. + +================================================================================ + +The file: + asm-3.1.jar +is redistributed in executable form and is licensed under the following terms: + +Copyright (c) 2000-2005 INRIA, France Telecom +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: + +1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + +2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + +3. Neither the name of the copyright holders nor the names of its + contributors may be used to endorse or promote products derived from + this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE +LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +THE POSSIBILITY OF SUCH DAMAGE. + +================================================================================ + +The file: + jaxen-1.1.1.jar +is redistributed in executable form and is licensed under the following terms: + + $Id: LICENSE.txt,v 1.5 2006/02/05 21:49:04 elharo Exp $ + + Copyright 2003-2006 The Werken Company. All Rights Reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are + met: + + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + + * Neither the name of the Jaxen Project nor the names of its + contributors may be used to endorse or promote products derived + from this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS +IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER +OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +========================================================================================== + +The file: + htmlparser-1.0.5.jar +is redistributed in executable form and includes files under the following licenses: + +This is for the HTML parser as a whole except the rewindable input stream, +and the Live DOM Viewer. +For the copyright notices for individual files, please see individual files. + +/* + * Copyright (c) 2005, 2006, 2007 Henri Sivonen + * Copyright (c) 2007-2008 Mozilla Foundation + * Portions of comments Copyright 2004-2007 Apple Computer, Inc., Mozilla + * Foundation, and Opera Software ASA. + * + * Permission is hereby granted, free of charge, to any person obtaining a + * copy of this software and associated documentation files (the "Software"), + * to deal in the Software without restriction, including without limitation + * the rights to use, copy, modify, merge, publish, distribute, sublicense, + * and/or sell copies of the Software, and to permit persons to whom the + * Software is furnished to do so, subject to the following conditions: + * + * The above copyright notice and this permission notice shall be included in + * all copies or substantial portions of the Software. + * + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER + * DEALINGS IN THE SOFTWARE. + */ + +The following license is for the rewindable input stream. + +/* + * Copyright (c) 2001-2003 Thai Open Source Software Center Ltd + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * * Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * * Redistributions in binary form must reproduce the above + * copyright notice, this list of conditions and the following + * disclaimer in the documentation and/or other materials provided + * with the distribution. + * * Neither the name of the Thai Open Source Software Center Ltd nor + * the names of its contributors may be used to endorse or promote + * products derived from this software without specific prior + * written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS + * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, + * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, + * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; + * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN + * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE + * POSSIBILITY OF SUCH DAMAGE. + */ + +The following license applies to the Live DOM Viewer: + +Copyright (c) 2000, 2006, 2008 Ian Hickson and various contributors + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. + +========================================================================================== + +The file: + jinterface-1.5.3.1.jar +is redistributed in executable form, with source code available at + http://repo1.maven.org/maven2/org/erlang/otp/jinterface/1.5.3.1/ +and is licensed under the following terms: + +ERLANG PUBLIC LICENSE +Version 1.1 + +1. Definitions. + +1.1. ``Contributor'' means each entity that creates or contributes to +the creation of Modifications. + +1.2. ``Contributor Version'' means the combination of the Original +Code, prior Modifications used by a Contributor, and the Modifications +made by that particular Contributor. + +1.3. ``Covered Code'' means the Original Code or Modifications or the +combination of the Original Code and Modifications, in each case +including portions thereof. + +1.4. ``Electronic Distribution Mechanism'' means a mechanism generally +accepted in the software development community for the electronic +transfer of data. + +1.5. ``Executable'' means Covered Code in any form other than Source +Code. + +1.6. ``Initial Developer'' means the individual or entity identified +as the Initial Developer in the Source Code notice required by Exhibit +A. + +1.7. ``Larger Work'' means a work which combines Covered Code or +portions thereof with code not governed by the terms of this License. + +1.8. ``License'' means this document. + +1.9. ``Modifications'' means any addition to or deletion from the +substance or structure of either the Original Code or any previous +Modifications. When Covered Code is released as a series of files, a +Modification is: + +A. Any addition to or deletion from the contents of a file containing + Original Code or previous Modifications. + +B. Any new file that contains any part of the Original Code or + previous Modifications. + +1.10. ``Original Code'' means Source Code of computer software code +which is described in the Source Code notice required by Exhibit A as +Original Code, and which, at the time of its release under this +License is not already Covered Code governed by this License. + +1.11. ``Source Code'' means the preferred form of the Covered Code for +making modifications to it, including all modules it contains, plus +any associated interface definition files, scripts used to control +compilation and installation of an Executable, or a list of source +code differential comparisons against either the Original Code or +another well known, available Covered Code of the Contributor's +choice. The Source Code can be in a compressed or archival form, +provided the appropriate decompression or de-archiving software is +widely available for no charge. + +1.12. ``You'' means an individual or a legal entity exercising rights +under, and complying with all of the terms of, this License. For legal +entities,``You'' includes any entity which controls, is controlled by, +or is under common control with You. For purposes of this definition, +``control'' means (a) the power, direct or indirect, to cause the +direction or management of such entity, whether by contract or +otherwise, or (b) ownership of fifty percent (50%) or more of the +outstanding shares or beneficial ownership of such entity. + +2. Source Code License. + +2.1. The Initial Developer Grant. +The Initial Developer hereby grants You a world-wide, royalty-free, +non-exclusive license, subject to third party intellectual property +claims: + +(a) to use, reproduce, modify, display, perform, sublicense and + distribute the Original Code (or portions thereof) with or without + Modifications, or as part of a Larger Work; and + +(b) under patents now or hereafter owned or controlled by Initial + Developer, to make, have made, use and sell (``Utilize'') the + Original Code (or portions thereof), but solely to the extent that + any such patent is reasonably necessary to enable You to Utilize + the Original Code (or portions thereof) and not to any greater + extent that may be necessary to Utilize further Modifications or + combinations. + +2.2. Contributor Grant. +Each Contributor hereby grants You a world-wide, royalty-free, +non-exclusive license, subject to third party intellectual property +claims: + +(a) to use, reproduce, modify, display, perform, sublicense and + distribute the Modifications created by such Contributor (or + portions thereof) either on an unmodified basis, with other + Modifications, as Covered Code or as part of a Larger Work; and + +(b) under patents now or hereafter owned or controlled by Contributor, + to Utilize the Contributor Version (or portions thereof), but + solely to the extent that any such patent is reasonably necessary + to enable You to Utilize the Contributor Version (or portions + thereof), and not to any greater extent that may be necessary to + Utilize further Modifications or combinations. + +3. Distribution Obligations. + +3.1. Application of License. +The Modifications which You contribute are governed by the terms of +this License, including without limitation Section 2.2. The Source +Code version of Covered Code may be distributed only under the terms +of this License, and You must include a copy of this License with +every copy of the Source Code You distribute. You may not offer or +impose any terms on any Source Code version that alters or restricts +the applicable version of this License or the recipients' rights +hereunder. However, You may include an additional document offering +the additional rights described in Section 3.5. + +3.2. Availability of Source Code. +Any Modification which You contribute must be made available in Source +Code form under the terms of this License either on the same media as +an Executable version or via an accepted Electronic Distribution +Mechanism to anyone to whom you made an Executable version available; +and if made available via Electronic Distribution Mechanism, must +remain available for at least twelve (12) months after the date it +initially became available, or at least six (6) months after a +subsequent version of that particular Modification has been made +available to such recipients. You are responsible for ensuring that +the Source Code version remains available even if the Electronic +Distribution Mechanism is maintained by a third party. + +3.3. Description of Modifications. +You must cause all Covered Code to which you contribute to contain a +file documenting the changes You made to create that Covered Code and +the date of any change. You must include a prominent statement that +the Modification is derived, directly or indirectly, from Original +Code provided by the Initial Developer and including the name of the +Initial Developer in (a) the Source Code, and (b) in any notice in an +Executable version or related documentation in which You describe the +origin or ownership of the Covered Code. + +3.4. Intellectual Property Matters + +(a) Third Party Claims. + If You have knowledge that a party claims an intellectual property + right in particular functionality or code (or its utilization + under this License), you must include a text file with the source + code distribution titled ``LEGAL'' which describes the claim and + the party making the claim in sufficient detail that a recipient + will know whom to contact. If you obtain such knowledge after You + make Your Modification available as described in Section 3.2, You + shall promptly modify the LEGAL file in all copies You make + available thereafter and shall take other steps (such as notifying + appropriate mailing lists or newsgroups) reasonably calculated to + inform those who received the Covered Code that new knowledge has + been obtained. + +(b) Contributor APIs. + If Your Modification is an application programming interface and + You own or control patents which are reasonably necessary to + implement that API, you must also include this information in the + LEGAL file. + +3.5. Required Notices. +You must duplicate the notice in Exhibit A in each file of the Source +Code, and this License in any documentation for the Source Code, where +You describe recipients' rights relating to Covered Code. If You +created one or more Modification(s), You may add your name as a +Contributor to the notice described in Exhibit A. If it is not +possible to put such notice in a particular Source Code file due to +its structure, then you must include such notice in a location (such +as a relevant directory file) where a user would be likely to look for +such a notice. You may choose to offer, and to charge a fee for, +warranty, support, indemnity or liability obligations to one or more +recipients of Covered Code. However, You may do so only on Your own +behalf, and not on behalf of the Initial Developer or any +Contributor. You must make it absolutely clear than any such warranty, +support, indemnity or liability obligation is offered by You alone, +and You hereby agree to indemnify the Initial Developer and every +Contributor for any liability incurred by the Initial Developer or +such Contributor as a result of warranty, support, indemnity or +liability terms You offer. + +3.6. Distribution of Executable Versions. +You may distribute Covered Code in Executable form only if the +requirements of Section 3.1-3.5 have been met for that Covered Code, +and if You include a notice stating that the Source Code version of +the Covered Code is available under the terms of this License, +including a description of how and where You have fulfilled the +obligations of Section 3.2. The notice must be conspicuously included +in any notice in an Executable version, related documentation or +collateral in which You describe recipients' rights relating to the +Covered Code. You may distribute the Executable version of Covered +Code under a license of Your choice, which may contain terms different +from this License, provided that You are in compliance with the terms +of this License and that the license for the Executable version does +not attempt to limit or alter the recipient's rights in the Source +Code version from the rights set forth in this License. If You +distribute the Executable version under a different license You must +make it absolutely clear that any terms which differ from this License +are offered by You alone, not by the Initial Developer or any +Contributor. You hereby agree to indemnify the Initial Developer and +every Contributor for any liability incurred by the Initial Developer +or such Contributor as a result of any such terms You offer. + +3.7. Larger Works. +You may create a Larger Work by combining Covered Code with other code +not governed by the terms of this License and distribute the Larger +Work as a single product. In such a case, You must make sure the +requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. +If it is impossible for You to comply with any of the terms of this +License with respect to some or all of the Covered Code due to statute +or regulation then You must: (a) comply with the terms of this License +to the maximum extent possible; and (b) describe the limitations and +the code they affect. Such description must be included in the LEGAL +file described in Section 3.4 and must be included with all +distributions of the Source Code. Except to the extent prohibited by +statute or regulation, such description must be sufficiently detailed +for a recipient of ordinary skill to be able to understand it. + +5. Application of this License. + +This License applies to code to which the Initial Developer has +attached the notice in Exhibit A, and to related Covered Code. + +6. CONNECTION TO MOZILLA PUBLIC LICENSE + +This Erlang License is a derivative work of the Mozilla Public +License, Version 1.0. It contains terms which differ from the Mozilla +Public License, Version 1.0. + +7. DISCLAIMER OF WARRANTY. + +COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, +WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, +WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF +DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR +NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF +THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE +IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER +CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR +CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART +OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER +EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. +This License and the rights granted hereunder will terminate +automatically if You fail to comply with terms herein and fail to cure +such breach within 30 days of becoming aware of the breach. All +sublicenses to the Covered Code which are properly granted shall +survive any termination of this License. Provisions which, by their +nature, must remain in effect beyond the termination of this License +shall survive. + +9. DISCLAIMER OF LIABILITY +Any utilization of Covered Code shall not cause the Initial Developer +or any Contributor to be liable for any damages (neither direct nor +indirect). + +10. MISCELLANEOUS +This License represents the complete agreement concerning the subject +matter hereof. If any provision is held to be unenforceable, such +provision shall be reformed only to the extent necessary to make it +enforceable. This License shall be construed by and in accordance with +the substantive laws of Sweden. Any dispute, controversy or claim +arising out of or relating to this License, or the breach, termination +or invalidity thereof, shall be subject to the exclusive jurisdiction +of Swedish courts, with the Stockholm City Court as the first +instance. + +EXHIBIT A. + +``The contents of this file are subject to the Erlang Public License, +Version 1.1, (the "License"); you may not use this file except in +compliance with the License. You should have received a copy of the +Erlang Public License along with this software. If not, it can be +retrieved via the world wide web at http://www.erlang.org/. + +Software distributed under the License is distributed on an "AS IS" +basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See +the License for the specific language governing rights and limitations +under the License. + +The Initial Developer of the Original Code is Ericsson Utvecklings AB. +Portions created by Ericsson are Copyright 1999, Ericsson Utvecklings +AB. All Rights Reserved.'' + +========================================================================================== diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/NOTICE b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/NOTICE new file mode 100644 index 0000000000..f77f483cd7 --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/bin/NOTICE @@ -0,0 +1,5 @@ +Apache Tuscany +Copyright (c) 2005 - 2010 The Apache Software Foundation + +This product includes software developed at +The Apache Software Foundation (http://www.apache.org/). diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/BUILDING b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/BUILDING new file mode 100644 index 0000000000..926c8b397d --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/BUILDING @@ -0,0 +1,91 @@ +Building the Apache Tuscany SCA 1.6.1 November 2010 Release source distribution +=============================================================================== + +Initial Setup +------------- + +1) Install either of the following: + a) Java SE 5.0 SDK (version 1.5.0_22 or higher), which can be downloaded from + http://java.sun.com/j2se/1.5.0/download.jsp + b) Java SE 6.0 SDK (version 1.6.0_07 or higher), which can be downloaded from + http://java.sun.com/javase/downloads + +2) Make sure that your JAVA_HOME environment variable is set to the installed + JDK location, and that your PATH includes %JAVA_HOME%\bin (windows) or + $JAVA_HOME$/bin (unix). + +3) Install Maven 2.0.10 or higher, which can be downloaded from + http://maven.apache.org/download.html. Make sure that your PATH includes + the $M2_HOME$/bin directory. + +4) Make sure that your MAVEN_OPTS environment variable has -Xmx256m (or more) + and -XX:MaxPermSize=256m (or more). You can do this manually by executing + the following in your prompt: + Windows users: + set MAVEN_OPTS=-Xmx256m -XX:MaxPermSize=256m + Unix users: + export MAVEN_OPTS=-Xmx256m -XX:MaxPermSize=256m + + +Building +-------- + +1) Change to the top level directory of the Apache Tuscany SCA source distribution. +2) Run + + $> mvn + + This will compile Apache Tuscany SCA and run all of the tests in the source + distribution. + + Depending on the load of remote Maven 2.0 repositories, you may have + to run 'mvn' several times utill the required dependencies are + all located in your local maven repository. It usually takes some time for + maven to download required dependencies in the first build. Once all the + dependencies have been downloaded you may use the -o option to run maven + in offline mode, for example, 'mvn clean install -o'. + + +Building the distributions +-------------------------- + +1) Change to the distribution folder +2) Run + + $> mvn + + This will build the binary and source distributions with .zip and .gz + formats in the distribution/target directory. + + +Using an IDE +------------ + +The easiest way to work with Apache Tuscany SCA in an IDE is to use Maven to +generate all of the IDE project files for you automatically. This works best +if you generate IDE projects for all of the Apache Tuscany modules. You can +then include the ones you are interested in working with in your IDE. + +To build IDE project files for all of the modules in Apache Tuscany SCA; + +cd <sca-dir> + +where <sca-dir> is the top-level directory containing the all the +Apache Tuscany SCA source code. + +If you are an Eclipse user do the following + +mvn eclipse:eclipse +mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo + +If you are an IDEA user do the following + +mvn idea:idea + +These commands generate project files for each module in Apache Tuscany SCA. +The modules you are interested in can now be included in your IDE. + +For example, in Eclipse, if you create a new Java project and use the option +to "create a new project from existing source" you can specify an SCA module +directory, which includes the generated project files, and Eclipse will treat +it like any other Java project. diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/LICENSE b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/LICENSE new file mode 100644 index 0000000000..a0ab15a279 --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/LICENSE @@ -0,0 +1,502 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + 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. + + +=============================================================================================================== + +APACHE TUSCANY SCA SUBCOMPONENTS: + +Apache Tuscany SCA for Java includes a number of subcomponents with +separate copyright notices and license terms. Your use of these subcomponents +is subject to the terms and conditions of the following licenses. + +=============================================================================================================== + +The module itest/databindings/common includes the test schema; datagraph.xsd, sdoJava.xsd, and sdoModel.xsd +under the following license: + +(c) Copyright BEA Systems, Inc., International Business Machines Corporation, +Oracle Corporation, Primeton Technologies Ltd., Rogue Wave Software, SAP AG., +Software AG., Sun Microsystems, Sybase Inc., Xcalia, Zend Technologies, +2005, 2006. All rights reserved. + +License for the Service Data Objects JavaDoc, Interface Definition files +and XSD files. + +The Service Data Objects JavaDoc, Interface Definition files and XSD files +are being provided by the copyright holders under the following license. +By using and/or copying this work, you agree that you have read, +understood and will comply with the following terms and conditions: + +Permission to copy, display, make derivative works of and distribute +the Service Data Objects JavaDoc, Interface Definition files and XSD files +(the "Artifacts") in any medium without fee or royalty is hereby granted, +provided that you include the following on ALL copies of the Artifacts, +or portions thereof, that you make: + +1. A link or URL to the Artifacts at this location: +http://www.osoa.org/display/Main/Service+Data+Objects+Specifications + +2. The full text of this copyright notice as shown in the Artifacts. + + + +THE ARTIFACTS ARE PROVIDED "AS IS" AND THE AUTHORS MAKE NO +REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE +ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, +INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS +FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OR TITLE. + +THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, +INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY +USE OR DISTRIBUTION OF THE ARTIFACTS. + +The name and trademarks of the Authors may NOT be used in any manner, +including advertising or publicity pertaining to the Service Data +Objects Specification or its contents without specific, written prior +permission. Title to copyright in the Service Data Objects +Specification will at all times remain with the Authors. + +No other rights are granted by implication, estoppel or otherwise. + +Revision level 1.11, last updated on 2007/12/21 + +================================================================================================================= + +The module implementation-script temporarily includes one file under the following BSD license: + + Copyright (c) 2006, Sun Microsystems, Inc. + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are met: + + - Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + + - Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + + - Neither the name of the Sun Microsystems, Inc. nor the names of + contributors may be used to endorse or promote products derived from this + software without specific prior written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED + WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A + PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY + DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, + PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE + OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH + DAMAGE. + +================================================================================================================= + +The module assembly-xsd includes XSD files under the following SCA Collaboration license: + +(c) Copyright SCA Collaboration 2006, 2007 + +License for the Service Component Architecture JavaDoc, Interface +Definition files and XSD files. + +The Service Component Architecture JavaDoc, Interface Definition files, +and XSD files are being provided by the copyright holders under the +following license. By using and/or copying this work, you agree that +you have read, understood and will comply with the following terms and +conditions: + +Permission to copy, display, make derivative works of, and distribute +the Service Component Architecture JavaDoc, Interface Definition Files +and XSD files (the "Artifacts") in any medium without fee or royalty is +hereby granted, provided that you include the following on ALL copies +of the Artifacts, or portions thereof, that you make: + +1. A link or URL to the Artifacts at this location: +http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications + +2. The full text of this copyright notice as shown in the Artifacts. + +THE ARTIFACTS ARE PROVIDED "AS IS," AND THE AUTHORS MAKE NO +REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE +ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, INCLUDING, BUT NOT +LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR +PURPOSE, NON-INFRINGEMENT OR TITLE. + +THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, +INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY +USE OR DISTRIBUTION OF THE ARTIFACTS. + +The name and trademarks of the Authors may NOT be used in any manner, +including advertising or publicity pertaining to the Service Component +Architecture Specification or its contents without specific, written +prior permission. Title to copyright in the Service Component +Architecture Specification and the JavaDoc, Interface Definition Files +and XSD Files will at all times remain with the Authors. + +No other rights are granted by implication, estoppel or otherwise. + +Revision level 1.1, last updated on 2007/11/19 + +================================================================================================================= + +The modules: + binding-ws-xml + databinding + databinding-axiom + databinding-jaxb + databinding-json + databinding-sdo + databinding-sdo-axiom + databinding-xmlbeans + interface-wsdl-xml +include the ipo.xsd and address.xsd information from the XML Schema Primer +(http://www.w3.org/TR/2004/PER-xmlschema-0-20040318/) combined into the +file ipo.xsd and extended with UK postcode structures. + +The module: + tuscany-assembly-xsd +includes the file wsdli.xsd from http://www.w3.org/2004/08/wsdl-instance + +The ipo.xsd and wsdli.xsd files are included under the following license: + +Copyright (c) 2004 World Wide Web Consortium, (Massachusetts Institute of Technology, +European Research Consortium for Informatics and Mathematics, Keio University). +All Rights Reserved. This work is distributed under the W3C(c) Software License [1] in +the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied +warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + +[1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 + +W3C(c) SOFTWARE NOTICE AND LICENSE +http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 + +This work (and included software, documentation such as READMEs, or other +related items) is being provided by the copyright holders under the following +license. By obtaining, using and/or copying this work, you (the licensee) agree +that you have read, understood, and will comply with the following terms and conditions. + +Permission to copy, modify, and distribute this software and its documentation, +with or without modification, for any purpose and without fee or royalty is +hereby granted, provided that you include the following on ALL copies of the +software and documentation or portions thereof, including modifications: + + 1. The full text of this NOTICE in a location viewable to users of the + redistributed or derivative work. + 2. Any pre-existing intellectual property disclaimers, notices, or terms + and conditions. If none exist, the W3C Software Short Notice should be + included (hypertext is preferred, text is permitted) within the body of + any redistributed or derivative code. + 3. Notice of any changes or modifications to the files, including the date + changes were made. (We recommend you provide URIs to the location from which + the code is derived.) + +THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE +NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, +WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE +USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, +COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. + +COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION. + +The name and trademarks of copyright holders may NOT be used in advertising or +publicity pertaining to the software without specific, written prior permission. +Title to copyright in this software and any associated documentation will at all +times remain with copyright holders. + +================================================================================================================= + +The modules: + host-webapp + sca-api +include files under the following copyrights and license: + +Copyright Notices + +(C) Copyright BEA Systems, Inc., Cape Clear Software, International Business Machines Corp, Interface21, IONA Technologies, +Oracle, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG., Siemens AG., Software AG., Sybase +Inc., TIBCO Software Inc., 2005, 2007. All rights reserved. + +(C) Copyright BEA Systems, Inc., Cape Clear Software, International Business Machines Corp, Interface21, IONA +Technologies, Oracle, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG., Siemens +AG., Software AG., Sun Microsystems, Inc., Sybase Inc., TIBCO Software Inc., 2005, 2008. All rights reserved. + +License + +Permission to copy, display and distribute the Service Component Architecture Specification and/or +portions thereof, without modification, in any medium without fee or royalty is hereby granted, provided +that you include the following on ALL copies of the Service Component Architecture Specification, or +portions thereof, that you make: + +1. A link or URL to the Service Component Architecture Specification at this location: +· http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications + +2. The full text of the copyright notice as shown in the Service Component Architecture Specification. + +BEA, Cape Clear, IBM, Interface21, IONA, Oracle, Primeton, Progress Software, Red Hat, Rogue Wave, +SAP, Siemens, Software AG., Sun, Sybase, TIBCO (collectively, the "Authors") agree to grant you a +royalty-free license, under reasonable, non-discriminatory terms and conditions to patents that they deem +necessary to implement the Service Component Architecture Specification. + +THE Service Component Architecture SPECIFICATION IS PROVIDED "AS IS," AND THE +AUTHORS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, +REGARDING THIS SPECIFICATION AND THE IMPLEMENTATION OF ITS CONTENTS, +INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A +PARTICULAR PURPOSE, NON-INFRINGEMENT OR TITLE. + +THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL +OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY USE OR +DISTRIBUTION OF THE Service Components Architecture SPECIFICATION. + +The name and trademarks of the Authors may NOT be used in any manner, including advertising or +publicity pertaining to the Service Component Architecture Specification or its contents without specific, +written prior permission. Title to copyright in the Service Component Architecture Specification +will at all times remain with the Authors. + +No other rights are granted by implication, estoppel or otherwise. + +================================================================================================================= + +The modules: + binding-jsonrpc-runtime + implementation-web-runtime +include the file jsonrpc.js under the following license: + +/* + * JSON-RPC JavaScript client + * + * $Id: jsonrpc.js,v 1.36.2.3 2006/03/08 15:09:37 mclark Exp $ + * + * Copyright (c) 2003-2004 Jan-Klaas Kollhof + * Copyright (c) 2005 Michael Clark, Metaparadigm Pte Ltd + * + * This code is based on Jan-Klaas' JavaScript o lait library (jsolait). + * + * 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. + * + */ + +/* + * Modifications for Apache Tuscany: + * - JSONRpcClient_createMethod changed so callback is last arg + */ + +================================================================================================================= diff --git a/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/NOTICE b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/NOTICE new file mode 100644 index 0000000000..f77f483cd7 --- /dev/null +++ b/sca-java-1.x/branches/sca-java-1.6.2/distribution/src/main/release/src/NOTICE @@ -0,0 +1,5 @@ +Apache Tuscany +Copyright (c) 2005 - 2010 The Apache Software Foundation + +This product includes software developed at +The Apache Software Foundation (http://www.apache.org/). |