Hi Jim,

Please help me understand this... all of what I mention here is in the
context of explicit wire defintions.. i.e. wires defined in scdl by the
'wire' element.

As per the specs it seems like the source of a "wire" could be a composite's
service's reference.  If this is the case can I have a composite whose
service element does not have a 'reference' defined inline but instead has
this wiring mentioned by a separate 'wire' element.
    If yes, then the service loader might need some changes since it throws
an exception if a target is not defined as part of the service definition.
    If no, then I don't find the specs excluding composite services as
sources of 'wire' definitions.

So which is the direction we take ?

Thanks

- Venkat



On 11/13/06, Venkatakrishnan (JIRA) <tuscany-dev@ws.apache.org> wrote:

    [
http://issues.apache.org/jira/browse/TUSCANY-921?page=comments#action_12449264]

Venkatakrishnan commented on TUSCANY-921:
-----------------------------------------

Hi,

I can give this a try with some help from you.  Will do some groundwork
and get back asap.  Thanks

- Venkat

> <wire> element in SCDL causes UnrecognizedElementException
> ----------------------------------------------------------
>
>                 Key: TUSCANY-921
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-921
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core
>    Affects Versions: Java-Mx
>            Reporter: Greg Dritschler
>
> Using a <wire> element in a composite results in an exception.
> org.apache.tuscany.spi.loader.UnrecognizedElementException: {
http://www.osoa.org/xmlns/sca/1.0}wire
> [{http://www.osoa.org/xmlns/sca/1.0}wire]
> Context stack trace: [application]
>         at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:90)
>         at
org.apache.tuscany.core.implementation.composite.CompositeLoader.load(
CompositeLoader.java:81)
>         at
org.apache.tuscany.core.implementation.composite.CompositeLoader.load(
CompositeLoader.java:55)
>         at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:92)
>         at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(
LoaderRegistryImpl.java:109)
>         at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.loadFromSidefile
(CompositeComponentTypeLoader.java:65)
>         at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load
(CompositeComponentTypeLoader.java:57)
>         at
org.apache.tuscany.core.implementation.composite.CompositeComponentTypeLoader.load
(CompositeComponentTypeLoader.java:39)
>         at
org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(
LoaderRegistryImpl.java:159)
>         at org.apache.tuscany.core.deployer.DeployerImpl.load(
DeployerImpl.java:101)
>         at org.apache.tuscany.core.deployer.DeployerImpl.deploy(
DeployerImpl.java:76)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to