apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Files	Lines
2010-06-25	connecting the JAXWS provider to the Tuscany chain. Pointed out an ↵	slaws	4	-126/+272
	interesting thing that should have been obvious but which I didn't notice before. The MessageContext coming from a JAXWSProvider is a JAXWS MessageContext and we are expecting an Axis MessageContext in our existing code. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@957987 13f79535-47bb-0310-9956-ffa450edef68
2010-06-25	Add a little bit more code to include the JAXWSMessageReciever so I can ↵	slaws	5	-5/+29
	debug some samples and see if there is any mileage in this approach git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@957864 13f79535-47bb-0310-9956-ffa450edef68
2010-06-11	This is turning out to be problematic and not necessarily any tidier than ↵	slaws	3	-10/+128
	out existing Axis integration so I'm saving the current state and thinking about moving back to improving the integration based on our existing module. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@953602 13f79535-47bb-0310-9956-ffa450edef68
2010-06-09	Add some code to install the JAXWS provider into Axis and copy the code from ↵	slaws	6	-23/+652
	the old binding to integrate the Axis2 runtime with our servler container. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@953017 13f79535-47bb-0310-9956-ffa450edef68
2010-06-08	Start thinking about providing and Axis backed runtime for the JAXWS based ↵	slaws	22	-0/+2297
	ws binding so that we can exploit Axis policy and protocols. Very early days so not ready for trunk yet. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@952627 13f79535-47bb-0310-9956-ffa450edef68