Please look at [1] and [2] for detailed steps. For WebSphere 6.1 you need at least Fixpack 9 which contains a Fix for a WebSphere bug with Servlet filters, that seems to be the problem you are having.
[1] http://jsdelfino.blogspot.com/2007/10/how-to-use-apache-tuscany-with.html [2] http://lresende.blogspot.com/2009/03/how-to-use-apache-tuscany-with.html On Sun, May 17, 2009 at 12:07 PM, Patrick Quinn <[email protected]> wrote: > > Hi Simon, > > Thanks for taking the time to reply. > > I'm running with Tuscany 1.4 (not the latest version, as I had previously > stated). > > I've actually pretty much solved the problem now through a bit of trial and > error. > > I selected 'Class Loading and update detection' from the administration > console and changed WAR class loader policy to 'Single Class loader for > application'. I had actually been told by a colleague to change the default > value above it to 'application class loader first' but he did not mention the > WAR class loader policy. > > Is there an authoritative step-by-step guide to doing this anywhere? I > suppose this is as much a Websphere thing as Tuscany. > > On a separate note, I was going to point my developers at the Tuscany > tutorial as a way of ramping up, but it's unfinished in v1.4. Am I just > unlucky? Is the literature more complete in the latest Tuscany version? It > would be disappointing if lack of documentation stops Tuscany being used > on the projects I look after for fear of burning budget, rather than any > inherent flaw in the framework itself. > > Regards, > > Pat > > > > > > ----- Original Message ---- > From: Simon Laws <[email protected]> > To: [email protected] > Sent: Sunday, 17 May, 2009 19:15:43 > Subject: Re: CONFIGURATION_ERROR stopping Tuscany WS from working > > On Sun, May 17, 2009 at 5:10 PM, Patrick Quinn <[email protected]> > wrote: >> >> Hi, >> I wonder whether you could give me any pointers to solve what I expect is a >> simple problem. >> >> I am trying to deploy and use a Tuscany WS webapp with the latest version of >> Tuscany against Websphere 6.1.0.0 (demo version). >> >> The webapp deploys ok, but I am having no luck in either viewing the WSDL or >> consuming the service. >> >> When I try and consume the service I get the following response: "Error 500: >> Filter [tuscany]: could not be initialized". >> >> The WAS SystemOut.log reports the following at deploy time: >> >>>> NodeImpl I Loading contribution: >>>>file:/C:/Program20Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/installedApps/PatrickQ01Node01Cell/helloworld-mvn-webapp_war.ear/helloworld-mvn-webapp.war/ >>>> CompositeProc W org.apache.tuscany.sca.assembly.xml.CompositeProcessor No >>>>namespace found: Composite = ws >>>> BindingWSDLGe W >>>>org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator Exception >>>>while generating WSDL for HelloWorldComponent/HelloWorld >>>> BindingWSDLGe E >>>>org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator Exception >>>>thrown was: WSDLException: faultCode=CONFIGURATION_ERROR: No Java >>>>extensionType found to represent a >>>>'{http://www.w3.org/2001/XMLSchema}schema' element in the context of a >>>>'javax.wsdl.Types'.: >>>> WebApp E java.lang.reflect.InvocationTargetException >> >> I get similar errors when I try and deploy some of the Tuscany sample ws >> webapps. >> >> I know that the webapp can be deployed on Websphere as I have had an >> experienced user deploy and test it on my WAS instance a few days ago. (And, >> FWIW, I can get non-WS Tuscany examples working). >> >> I have since undeployed the webapp for retesting but cannot now get it >> working again. I suspect I am missing out something in the deployment >> process. >> >> Any help gladly appreciated. >> >> Regards, >> >> Pat >> >> >> >> > > Hi Pat > > What Tuscany version are you running with? Are you able to get the > sample wars running on your WebSphere installation? For example, can > you run samples/calculator-webapp? (there are some instructions at [1] > for how to install it) > > Not sure but the first error looks like it's complaining that there is > no target namespace on the composite element. Looking at the > calculator.composite form samples/calculator-webapp you can see where > the targetnamespace goes.... > > <composite xmlns="http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://sample"; > xmlns:sample="http://sample"; > name="Calculator"> > ... > > </composite> > > I don't know what the BindingWSDLGenerator problem is. Looks a little > strange but could indicate that one of the Tuscany jarsis missing from > the classpath. Which Tuscany jars have you packaged in the war you are > using? > > Regards > > Simon > > [1] http://jsdelfino.blogspot.com/2007/10/how-to-use-apache-tuscany-with.html > > > > > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
