On 11/21/06, Simon Laws <[EMAIL PROTECTED]> wrote:
On 11/21/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
>
> On 11/21/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > Just checked in r477663 - this removes the requirement for Python
> > components to have componentType side-files. All references,
> > properties and a default service are now automatically set up for each
> > Python component specified in the composite. componentType files can
> > still be specified if required.
> >
> > One small restriction (which is also in the Ruby extension) is that
> > all properties are set as xsd:string types (this type information is
> > normally set in the componentType file) which doesn't really matter
> > with these loosely-typed languages. I considered adding a type
> > attribute on the property elements in the composite, but left it for
> > now as it would be breaking away from the assembly spec. For now, if
> > users want to specify the type of a property, they can create and use
> > a componentType file.
> >
>
> Also updated the PythonCalculator sample to remove the now-unnecessary
> componentType files.
>
> Andy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> Andy
So we still have and example where this optional component type file is
used?
Simon
Not at the moment I'm afraid - we need more scripting language
examples, and I guess one of those should show the use of
componentType files.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
