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 - [EMAIL PROTECTED]


-----Original Message-----
From: Pete Robbins [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 07, 2007 12:21 PM
To: [email protected]
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 <[EMAIL PROTECTED]> 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 - [EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>
>
>
>


--
Pete

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


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

Reply via email to