You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Brady Johnson <bj...@roguewave.com> on 2007/08/07 19:56:18 UTC
[SCA Native] java implementation and interface schema files loaded but not used
Does anyone have any insight into why these files are loaded but never
used in TuscanySCA Native:
<TuscanySCA Root dir>/xsd/
sca-implementation-java.xsd
sca-interface-java.xsd
I created a JIRA for this:
https://issues.apache.org/jira/browse/TUSCANY-1513
Their existence in the project is misleading and implies that TuscanySCA
Native supports Java services.
Perhaps these should be removed in M4.
--------------------
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - brady.johnson@roguewave.com
<ma...@roguewave.com>
RE: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Brady Johnson <bj...@roguewave.com>.
This sounds reasonable. We can make this change for the M4 release.
So basically it will be as follows:
- sca.xsd is no longer needed.
- deploy all "core" schemas to <install_root>/xsd
- sca-implementation-java.xsd and sca-interface-java.xsd will not be a
part of the "core"
schemas and should only be loaded by a java extension.
- each extension will still deploy its respective schemas to
<install_root>/extension/<extension_name>/xsd
- any schema in <install_root>/xsd or
<install_root>/extension/<extension_name>/xsd will be loaded.
--------------------
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - brady.johnson@roguewave.com
-----Original Message-----
From: Pete Robbins [mailto:robbinspg@googlemail.com]
Sent: Tuesday, August 07, 2007 12:21 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] java implementation and interface schema files
loaded but not used
It was simply that we were loading all the initial sca schema. So the
core code loads sca.xsd but I think we should change that to
specifically load the ones we need. Maybe the best thing is to load any
schema in <install_root>/xsd and we can just delete the java stuff.
If the Native runtime wants to support Java then that schema would be
loaded by the Java extension.
Cheers,
On 07/08/07, Brady Johnson <bj...@roguewave.com> wrote:
> Does anyone have any insight into why these files are loaded but never
> used in TuscanySCA Native:
>
> <TuscanySCA Root dir>/xsd/
> sca-implementation-java.xsd
> sca-interface-java.xsd
>
> I created a JIRA for this:
> https://issues.apache.org/jira/browse/TUSCANY-1513
>
> Their existence in the project is misleading and implies that
> TuscanySCA Native supports Java services.
> Perhaps these should be removed in M4.
>
>
> --------------------
> Brady Johnson
> Lead Software Developer - HydraSCA
> Rogue Wave Software - brady.johnson@roguewave.com
> <ma...@roguewave.com>
>
>
>
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Pete Robbins <ro...@googlemail.com>.
It was simply that we were loading all the initial sca schema. So the
core code loads sca.xsd but I think we should change that to
specifically load the ones we need. Maybe the best thing is to load
any schema in <install_root>/xsd and we can just delete the java
stuff.
If the Native runtime wants to support Java then that schema would be
loaded by the Java extension.
Cheers,
On 07/08/07, Brady Johnson <bj...@roguewave.com> wrote:
> Does anyone have any insight into why these files are loaded but never
> used in TuscanySCA Native:
>
> <TuscanySCA Root dir>/xsd/
> sca-implementation-java.xsd
> sca-interface-java.xsd
>
> I created a JIRA for this:
> https://issues.apache.org/jira/browse/TUSCANY-1513
>
> Their existence in the project is misleading and implies that TuscanySCA
> Native supports Java services.
> Perhaps these should be removed in M4.
>
>
> --------------------
> Brady Johnson
> Lead Software Developer - HydraSCA
> Rogue Wave Software - brady.johnson@roguewave.com
> <ma...@roguewave.com>
>
>
>
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Pete Robbins <ro...@googlemail.com>.
On 13/08/07, David Haney <ha...@roguewave.com> wrote:
>
>
> > -----Original Message-----
> > From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
> > Sent: Friday, August 10, 2007 8:33 AM
> > To: tuscany-dev@ws.apache.org
> > Subject: Re: [SCA Native] java implementation and interface schema
> files
> > loaded but not used
> >
> > Brady Johnson wrote:
> > > Does anyone have any insight into why these files are loaded but
> never
> > > used in TuscanySCA Native:
> > >
> > > <TuscanySCA Root dir>/xsd/
> > > sca-implementation-java.xsd
> > > sca-interface-java.xsd
> > >
> > > I created a JIRA for this:
> > > https://issues.apache.org/jira/browse/TUSCANY-1513
> > >
> > > Their existence in the project is misleading and implies that
> TuscanySCA
> > > Native supports Java services.
> > > Perhaps these should be removed in M4.
> > >
> > >
> > > --------------------
> > > Brady Johnson
> > > Lead Software Developer - HydraSCA
> > > Rogue Wave Software - brady.johnson@roguewave.com
> > > <ma...@roguewave.com>
> > >
> > >
> > >
> > >
> >
> > Will you be able to load (and ignore without breaking) a composite
> > containing implementation.java and interface.java elements? I'm
> thinking
> > about scenarios where people share a composite between the two
> runtimes,
> > with part of it running on the Native runtime and part running on the
> > Java runtime.
> >
> > I guess I'll have the same question for the Java project, we should be
> > able to ignore (or just handle with a warning) implementation.cpp and
> > interface.cpp in the Java runtime.
> >
> > --
> > Jean-Sebastien
> >
>
> Won't this still be a problem for other extensions that are provided by
> Tuscany Java? For example, implementation.script? Does this imply that
> we should copy all of the extension xsd files from Tuscany Java into
> Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
>
> Is it possible we could have the composite loader ignore (or warn about)
> extension types that it doesn't recognize? This would allow it to parse
> the composite files, but wouldn't require that our runtime explicitly
> recognize every extension type that isn't supported.
I think this is the way to go.
>
> -- David Haney
> -- Chief Architect, Hydra Products
> -- Rogue Wave Software
> -- http://www.roguewave.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded
but not used
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Jean-Sebastien Delfino wrote:
> David Haney wrote:
>>
>>> -----Original Message-----
>>> From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
>>> Sent: Friday, August 10, 2007 8:33 AM
>>> To: tuscany-dev@ws.apache.org
>>> Subject: Re: [SCA Native] java implementation and interface schema
>>>
>> files
>>
>>> loaded but not used
>>>
>>> Brady Johnson wrote:
>>>
>>>> Does anyone have any insight into why these files are loaded but
>>>>
>> never
>>
>>>> used in TuscanySCA Native:
>>>>
>>>> <TuscanySCA Root dir>/xsd/
>>>> sca-implementation-java.xsd
>>>> sca-interface-java.xsd
>>>>
>>>> I created a JIRA for this:
>>>> https://issues.apache.org/jira/browse/TUSCANY-1513
>>>>
>>>> Their existence in the project is misleading and implies that
>>>>
>> TuscanySCA
>>
>>>> Native supports Java services.
>>>> Perhaps these should be removed in M4.
>>>>
>>>>
>>>> --------------------
>>>> Brady Johnson
>>>> Lead Software Developer - HydraSCA
>>>> Rogue Wave Software - brady.johnson@roguewave.com
>>>> <ma...@roguewave.com>
>>>>
>>>>
>>>>
>>>>
>>>>
>>> Will you be able to load (and ignore without breaking) a composite
>>> containing implementation.java and interface.java elements? I'm
>>>
>> thinking
>>
>>> about scenarios where people share a composite between the two
>>>
>> runtimes,
>>
>>> with part of it running on the Native runtime and part running on the
>>> Java runtime.
>>>
>>> I guess I'll have the same question for the Java project, we should be
>>> able to ignore (or just handle with a warning) implementation.cpp and
>>> interface.cpp in the Java runtime.
>>>
>>> --
>>> Jean-Sebastien
>>>
>>>
>>
>> Won't this still be a problem for other extensions that are provided by
>> Tuscany Java? For example, implementation.script? Does this imply that
>> we should copy all of the extension xsd files from Tuscany Java into
>> Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
>
> I'm not implying anything or advocating for any solution. It's just
> that the discussion about the schemas made me think about scenarios
> mixing implementation and binding types and I'm just asking if there
> will be an issue at all with these scenarios.
>
>> Is it possible we could have the composite loader ignore (or warn about)
>> extension types that it doesn't recognize? This would allow it to parse
>> the composite files, but wouldn't require that our runtime explicitly
>> recognize every extension type that isn't supported.
>>
>
> That would be a good idea.
>
>> -- David Haney
>> -- Chief Architect, Hydra Products
>> -- Rogue Wave Software
>> -- http://www.roguewave.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>>
>
>
One more thought. <implementation.java> and <interface.java> are from
the SCA namespace. Other Tuscany extensions like <implementation.script>
will be from a different namespace (at the moment they are still in the
SCA namespace but this will be fixed shortly). So it will be possible to
use these Tuscany extensions in a composite without violating the SCA
schema.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded
but not used
Posted by Jean-Sebastien Delfino <js...@apache.org>.
David Haney wrote:
>
>> -----Original Message-----
>> From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
>> Sent: Friday, August 10, 2007 8:33 AM
>> To: tuscany-dev@ws.apache.org
>> Subject: Re: [SCA Native] java implementation and interface schema
>>
> files
>
>> loaded but not used
>>
>> Brady Johnson wrote:
>>
>>> Does anyone have any insight into why these files are loaded but
>>>
> never
>
>>> used in TuscanySCA Native:
>>>
>>> <TuscanySCA Root dir>/xsd/
>>> sca-implementation-java.xsd
>>> sca-interface-java.xsd
>>>
>>> I created a JIRA for this:
>>> https://issues.apache.org/jira/browse/TUSCANY-1513
>>>
>>> Their existence in the project is misleading and implies that
>>>
> TuscanySCA
>
>>> Native supports Java services.
>>> Perhaps these should be removed in M4.
>>>
>>>
>>> --------------------
>>> Brady Johnson
>>> Lead Software Developer - HydraSCA
>>> Rogue Wave Software - brady.johnson@roguewave.com
>>> <ma...@roguewave.com>
>>>
>>>
>>>
>>>
>>>
>> Will you be able to load (and ignore without breaking) a composite
>> containing implementation.java and interface.java elements? I'm
>>
> thinking
>
>> about scenarios where people share a composite between the two
>>
> runtimes,
>
>> with part of it running on the Native runtime and part running on the
>> Java runtime.
>>
>> I guess I'll have the same question for the Java project, we should be
>> able to ignore (or just handle with a warning) implementation.cpp and
>> interface.cpp in the Java runtime.
>>
>> --
>> Jean-Sebastien
>>
>>
>
> Won't this still be a problem for other extensions that are provided by
> Tuscany Java? For example, implementation.script? Does this imply that
> we should copy all of the extension xsd files from Tuscany Java into
> Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
>
I'm not implying anything or advocating for any solution. It's just
that the discussion about the schemas made me think about scenarios
mixing implementation and binding types and I'm just asking if there
will be an issue at all with these scenarios.
> Is it possible we could have the composite loader ignore (or warn about)
> extension types that it doesn't recognize? This would allow it to parse
> the composite files, but wouldn't require that our runtime explicitly
> recognize every extension type that isn't supported.
>
That would be a good idea.
> -- David Haney
> -- Chief Architect, Hydra Products
> -- Rogue Wave Software
> -- http://www.roguewave.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
>
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Pete Robbins <ro...@googlemail.com>.
On 14/08/07, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> The SCA Java runtime doesn't use the XSD for the assembly or extensions at
> runtime to parse the composite file. A StAX-based artifact processor is
> plugged into the runtime to handle the extensions such as
> implementation.java, implementation.script and binidng.rmi.
>
> Does SCA Native use the generated SDO from the XSDs to load the composite
> file?
>
No. SDO C++ does not have a generated SDO feature yet. We load the
schema to define types then load the XML to create dynamic SDOs. It
was simple. convenient and initially we were using it to test out the
SDO code.
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "David Haney" <ha...@roguewave.com>
> To: <tu...@ws.apache.org>
> Sent: Monday, August 13, 2007 2:35 PM
> Subject: RE: [SCA Native] java implementation and interface schema files
> loaded but not used
>
>
>
>
> > -----Original Message-----
> > From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
> > Sent: Friday, August 10, 2007 8:33 AM
> > To: tuscany-dev@ws.apache.org
> > Subject: Re: [SCA Native] java implementation and interface schema
> files
> > loaded but not used
> >
> > Brady Johnson wrote:
> > > Does anyone have any insight into why these files are loaded but
> never
> > > used in TuscanySCA Native:
> > >
> > > <TuscanySCA Root dir>/xsd/
> > > sca-implementation-java.xsd
> > > sca-interface-java.xsd
> > >
> > > I created a JIRA for this:
> > > https://issues.apache.org/jira/browse/TUSCANY-1513
> > >
> > > Their existence in the project is misleading and implies that
> TuscanySCA
> > > Native supports Java services.
> > > Perhaps these should be removed in M4.
> > >
> > >
> > > --------------------
> > > Brady Johnson
> > > Lead Software Developer - HydraSCA
> > > Rogue Wave Software - brady.johnson@roguewave.com
> > > <ma...@roguewave.com>
> > >
> > >
> > >
> > >
> >
> > Will you be able to load (and ignore without breaking) a composite
> > containing implementation.java and interface.java elements? I'm
> thinking
> > about scenarios where people share a composite between the two
> runtimes,
> > with part of it running on the Native runtime and part running on the
> > Java runtime.
> >
> > I guess I'll have the same question for the Java project, we should be
> > able to ignore (or just handle with a warning) implementation.cpp and
> > interface.cpp in the Java runtime.
> >
> > --
> > Jean-Sebastien
> >
>
> Won't this still be a problem for other extensions that are provided by
> Tuscany Java? For example, implementation.script? Does this imply that
> we should copy all of the extension xsd files from Tuscany Java into
> Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
>
> Is it possible we could have the composite loader ignore (or warn about)
> extension types that it doesn't recognize? This would allow it to parse
> the composite files, but wouldn't require that our runtime explicitly
> recognize every extension type that isn't supported.
>
> -- David Haney
> -- Chief Architect, Hydra Products
> -- Rogue Wave Software
> -- http://www.roguewave.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Raymond Feng <en...@gmail.com>.
Hi,
The SCA Java runtime doesn't use the XSD for the assembly or extensions at
runtime to parse the composite file. A StAX-based artifact processor is
plugged into the runtime to handle the extensions such as
implementation.java, implementation.script and binidng.rmi.
Does SCA Native use the generated SDO from the XSDs to load the composite
file?
Thanks,
Raymond
----- Original Message -----
From: "David Haney" <ha...@roguewave.com>
To: <tu...@ws.apache.org>
Sent: Monday, August 13, 2007 2:35 PM
Subject: RE: [SCA Native] java implementation and interface schema files
loaded but not used
> -----Original Message-----
> From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
> Sent: Friday, August 10, 2007 8:33 AM
> To: tuscany-dev@ws.apache.org
> Subject: Re: [SCA Native] java implementation and interface schema
files
> loaded but not used
>
> Brady Johnson wrote:
> > Does anyone have any insight into why these files are loaded but
never
> > used in TuscanySCA Native:
> >
> > <TuscanySCA Root dir>/xsd/
> > sca-implementation-java.xsd
> > sca-interface-java.xsd
> >
> > I created a JIRA for this:
> > https://issues.apache.org/jira/browse/TUSCANY-1513
> >
> > Their existence in the project is misleading and implies that
TuscanySCA
> > Native supports Java services.
> > Perhaps these should be removed in M4.
> >
> >
> > --------------------
> > Brady Johnson
> > Lead Software Developer - HydraSCA
> > Rogue Wave Software - brady.johnson@roguewave.com
> > <ma...@roguewave.com>
> >
> >
> >
> >
>
> Will you be able to load (and ignore without breaking) a composite
> containing implementation.java and interface.java elements? I'm
thinking
> about scenarios where people share a composite between the two
runtimes,
> with part of it running on the Native runtime and part running on the
> Java runtime.
>
> I guess I'll have the same question for the Java project, we should be
> able to ignore (or just handle with a warning) implementation.cpp and
> interface.cpp in the Java runtime.
>
> --
> Jean-Sebastien
>
Won't this still be a problem for other extensions that are provided by
Tuscany Java? For example, implementation.script? Does this imply that
we should copy all of the extension xsd files from Tuscany Java into
Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
Is it possible we could have the composite loader ignore (or warn about)
extension types that it doesn't recognize? This would allow it to parse
the composite files, but wouldn't require that our runtime explicitly
recognize every extension type that isn't supported.
-- David Haney
-- Chief Architect, Hydra Products
-- Rogue Wave Software
-- http://www.roguewave.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
RE: [SCA Native] java implementation and interface schema files loaded but not used
Posted by David Haney <ha...@roguewave.com>.
> -----Original Message-----
> From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
> Sent: Friday, August 10, 2007 8:33 AM
> To: tuscany-dev@ws.apache.org
> Subject: Re: [SCA Native] java implementation and interface schema
files
> loaded but not used
>
> Brady Johnson wrote:
> > Does anyone have any insight into why these files are loaded but
never
> > used in TuscanySCA Native:
> >
> > <TuscanySCA Root dir>/xsd/
> > sca-implementation-java.xsd
> > sca-interface-java.xsd
> >
> > I created a JIRA for this:
> > https://issues.apache.org/jira/browse/TUSCANY-1513
> >
> > Their existence in the project is misleading and implies that
TuscanySCA
> > Native supports Java services.
> > Perhaps these should be removed in M4.
> >
> >
> > --------------------
> > Brady Johnson
> > Lead Software Developer - HydraSCA
> > Rogue Wave Software - brady.johnson@roguewave.com
> > <ma...@roguewave.com>
> >
> >
> >
> >
>
> Will you be able to load (and ignore without breaking) a composite
> containing implementation.java and interface.java elements? I'm
thinking
> about scenarios where people share a composite between the two
runtimes,
> with part of it running on the Native runtime and part running on the
> Java runtime.
>
> I guess I'll have the same question for the Java project, we should be
> able to ignore (or just handle with a warning) implementation.cpp and
> interface.cpp in the Java runtime.
>
> --
> Jean-Sebastien
>
Won't this still be a problem for other extensions that are provided by
Tuscany Java? For example, implementation.script? Does this imply that
we should copy all of the extension xsd files from Tuscany Java into
Tuscany Native's /xsd/ directory (and vice versa fro Tuscany Java)?
Is it possible we could have the composite loader ignore (or warn about)
extension types that it doesn't recognize? This would allow it to parse
the composite files, but wouldn't require that our runtime explicitly
recognize every extension type that isn't supported.
-- David Haney
-- Chief Architect, Hydra Products
-- Rogue Wave Software
-- http://www.roguewave.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
RE: [SCA Native] java implementation and interface schema files loaded but not used
Posted by Brady Johnson <bj...@roguewave.com>.
That's a good point I hadn't considered. I think we should definitely
keep these schemas in then, since without them it will probably fail to
load. There should be no problem at all to load but ignore.
Thanks
--------------------
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - brady.johnson@roguewave.com
-----Original Message-----
From: Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
Sent: Friday, August 10, 2007 9:33 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] java implementation and interface schema files
loaded but not used
Brady Johnson wrote:
> Does anyone have any insight into why these files are loaded but never
> used in TuscanySCA Native:
>
> <TuscanySCA Root dir>/xsd/
> sca-implementation-java.xsd
> sca-interface-java.xsd
>
> I created a JIRA for this:
> https://issues.apache.org/jira/browse/TUSCANY-1513
>
> Their existence in the project is misleading and implies that
> TuscanySCA Native supports Java services.
> Perhaps these should be removed in M4.
>
>
> --------------------
> Brady Johnson
> Lead Software Developer - HydraSCA
> Rogue Wave Software - brady.johnson@roguewave.com
> <ma...@roguewave.com>
>
>
>
>
Will you be able to load (and ignore without breaking) a composite
containing implementation.java and interface.java elements? I'm thinking
about scenarios where people share a composite between the two runtimes,
with part of it running on the Native runtime and part running on the
Java runtime.
I guess I'll have the same question for the Java project, we should be
able to ignore (or just handle with a warning) implementation.cpp and
interface.cpp in the Java runtime.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [SCA Native] java implementation and interface schema files loaded
but not used
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Brady Johnson wrote:
> Does anyone have any insight into why these files are loaded but never
> used in TuscanySCA Native:
>
> <TuscanySCA Root dir>/xsd/
> sca-implementation-java.xsd
> sca-interface-java.xsd
>
> I created a JIRA for this:
> https://issues.apache.org/jira/browse/TUSCANY-1513
>
> Their existence in the project is misleading and implies that TuscanySCA
> Native supports Java services.
> Perhaps these should be removed in M4.
>
>
> --------------------
> Brady Johnson
> Lead Software Developer - HydraSCA
> Rogue Wave Software - brady.johnson@roguewave.com
> <ma...@roguewave.com>
>
>
>
>
Will you be able to load (and ignore without breaking) a composite
containing implementation.java and interface.java elements? I'm thinking
about scenarios where people share a composite between the two runtimes,
with part of it running on the Native runtime and part running on the
Java runtime.
I guess I'll have the same question for the Java project, we should be
able to ignore (or just handle with a warning) implementation.cpp and
interface.cpp in the Java runtime.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org