summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/trunk/itest (follow)
Commit message (Expand)AuthorAgeFilesLines
...
* Add a dependency on the hazelcast client so we can switch the SCAClient test ...slaws2010-02-101-1/+6
* Add a test that just uses the SCAClient to talk to the remote SCA node. I.e. ...slaws2010-02-104-20/+74
* Add callback tests into the buildslaws2010-02-101-0/+2
* Add hazelcast test to buildslaws2010-02-101-0/+1
* Output something so that you can see that the target service has received a m...slaws2010-02-101-1/+3
* Add a stand alone client that is unhindered by any other Tuscany code (such a...slaws2010-02-101-0/+63
* Remove unecessary dependency on domain node and replace with direct dependenc...slaws2010-02-101-3/+8
* Remove the node.destroy()rfeng2010-02-091-1/+0
* Remove org.apache.tuscany.sca.node.Client and merge the methods into org.apac...rfeng2010-02-0919-431/+396
* Start to clean up the node-api (remove Node.destroy())rfeng2010-02-094-5/+49
* TUSCANY-3458 add some alternative configurations for the ws callback test to ...slaws2010-02-0920-0/+1041
* Add some code to all for easier manual running of the test slaws2010-02-093-1/+46
* Fix the compilation errorrfeng2010-02-061-1/+0
* Add in ws itests to build. Don't anything useful yet but might as well get th...slaws2010-02-051-0/+1
* Move the runtime over to use Axis2 1.5.1. Three main parts to this 1) replace...slaws2010-02-0415-15/+21
* Exploit features to define dependenciesslaws2010-02-041-20/+3
* Create a place in itests for binding.ws integration testsslaws2010-02-049-0/+404
* Put back in the JMS callbacks test as theres a workaround for it nowantelder2010-02-031-1/+1
* Fix the JMS callbacks test by removing all trailing spaces in the messages. J...antelder2010-02-034-4/+4
* Take out the JMS callbacks itest for now as there's an intermitent problem wi...antelder2010-02-031-1/+1
* Add jms callbacks to the buildantelder2010-02-031-1/+1
* Added itest recursive-ws module into 2.x code baseramkumar2010-02-0221-0/+923
* Adding oneway itest module to 2.x code baseramkumar2010-02-029-0/+704
* Update tribes registry to also support the tuscany registry uri formatantelder2010-01-295-0/+323
* Remove unwanted file from svnantelder2010-01-291-5/+0
* Update to find an existing domain if the registry isn't explicitly definedantelder2010-01-291-1/+1
* Refactor the DomainRegistryFactory to be extensions of DomainRegistryFactoryE...rfeng2010-01-294-6/+6
* Change the tuscanyClient scheme to pbe all lower case so it works with the to...antelder2010-01-282-0/+19
* Add the new client itestantelder2010-01-281-0/+1
* Itest for the client api using rmi and hazelcastantelder2010-01-286-0/+240
* Update type to be explicit client subclassantelder2010-01-281-2/+1
* Simpify be merging into a single testantelder2010-01-282-65/+17
* Change to use a less commonly used port, add a commentted out test on how lon...antelder2010-01-281-5/+17
* Add hazelcast-client test to build. Don't expect we'll keep the test as-is bu...antelder2010-01-281-0/+1
* Update client test to use generic local host ip address and add tests for bad...antelder2010-01-281-3/+24
* Start exploring using the Hazelcast native client so that the SCAClient API c...antelder2010-01-282-0/+165
* Disable parallel test runningantelder2010-01-281-0/+17
* Add another test using default and explicitly spcified domain URIsantelder2010-01-281-0/+58
* Refactor the databinding introspection to tuscany-implementation-java-runtime...rfeng2010-01-271-4/+1
* Moving databinding/jaxb-bottom-up and databindings/jaxb-top-down itest module...ramkumar2010-01-2773-0/+12980
* Fix for TUSCANY-3409rfeng2010-01-271-7/+5
* Don't see why this would effect anything as the tests don't run in parallel b...antelder2010-01-261-0/+15
* Update wait time as it still fails sometimes on hudsonantelder2010-01-261-1/+1
* Try to fix this on Hudson by disabling parallel tests, though it works ok wit...antelder2010-01-251-0/+19
* Add a logging intent so that reference/service policies matchslaws2010-01-251-1/+1
* Add policy sets so that intents are resolvedslaws2010-01-251-0/+21
* Needs the policy sets to resolve the specified intents. However leaving them ...slaws2010-01-251-7/+12
* Start adding some remote node test to the hazelcast nodes testsantelder2010-01-253-1/+88
* Use the single threaded test runnerantelder2010-01-251-0/+19
* Use separate domain names so tests don't interactantelder2010-01-251-1/+1