Hudgins, Paul wrote:
Following the instructions from Dave’s blog [1] I successfully deployed the sample-calculator-webapp.war from the 1.6.1 version of Tuscany SCA within a WebLogic 10.3.3 hosting environment. My next step was to explode the war and begin replacing the composites and classes with my own code. Before I replaced any files, I tried to deploy the web app as an exploded directory since it is easier to develop in this fashion. To my surprise, the following error happens:

Caused By: java.lang.IllegalArgumentException: No deployable composite is declared

at org.apache.tuscany.sca.node.impl.NodeImpl.aggregate(NodeImpl.java:643)

at org.apache.tuscany.sca.node.impl.NodeImpl.configureNode(NodeImpl.java:565)

at org.apache.tuscany.sca.node.impl.NodeImpl.<init>(NodeImpl.java:381)

at org.apache.tuscany.sca.node.impl.NodeFactoryImpl.createSCANode(NodeFactoryImpl.java:47)

at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:175)

So my questions are whether other folks have experienced this, and what was done (if anything) to get it working in an exploded directory? Is this specific to WebLogic’s deployment implementation?

The obvious workaround is to not develop in the expanded dir and just add a jar step to my build/deploy process.

[1] http://davesowerby.blogspot.com/2008/02/using-tuscany-with-weblogic.html

Is there any more stack trace information?  From the stack trace extract
above, it seems that the DefaultSCADomain instance was created using
incorrect contribution information.  A full stack trace might throw more
light on what caused this.

  Simon

Reply via email to