Namespace:	http://www.coldspringframework.org/schema/aop
Type:	anonymous complexType
Content:	complex, 9 attributes, 3 elements
Defined:	globally in coldspring-aop-2.0.xsd; see XML source
Includes:	definitions of 9 attributes, 3 elements
Used:	never

XML Representation Summary

<remote

xsd:string

xsd:ID

xsd:string

xsd:string

xsd:string

xsd:string

xsd:string

xsd:string

xsd:string : "false"

Content:

remote-methods?, missing-methods?, interceptors?

</remote>

Content model elements (3):

Configuration of a generated CFC that exposes a given set of methods froma specific bean, as remote, to be consumed as a SOAP / REST WebService, or as Flash Remoting.

See: cfc:coldspring.aop.framework.RemoteFactoryBean

XML Source (see within schema source)

<xsd:element name="remote">

<xsd:annotation>

<xsd:documentation source="cfc:coldspring.aop.framework.RemoteFactoryBean">

<![CDATA[

Configuration of a generated CFC that exposes a given set of methods froma specific bean, as remote,
to be consumed as a SOAP / REST WebService, or as Flash Remoting.

]]>

</xsd:documentation>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element maxOccurs="1" minOccurs="0" name="remote-methods" type="methods">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

List of the method names you want to expose as remote. '*' can be used as a special case wildcard
meaning that all methods on the target bean will be exposed as remote.
You can also use the attribute "remote-methods" to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="missing-methods" type="methods">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

List of of non-existent methods that are to be implemented as remote methods on the remote facade.
You can also use the attribute "missing-methods" to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="interceptors">

<xsd:annotation>

<xsd:documentation>

List of Advice/Advisor bean names to be applied to the target components.
You can also use the attribute "interceptor-names" to define this as well.

</xsd:documentation>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="interceptor">

<xsd:complexType>

<xsd:attribute name="ref" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

The id of the advice/advisor bean to apply.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

<xsd:attribute name="id" type="xsd:ID" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The unique identifier for the underlying RemoteFactoryBean.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="target-ref" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The name of the bean that will have it's methods exposed as being remote.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute default="false" name="trusted-source" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Whether or not the generated code is trusted. If true, the remoting component will not be regenerated if it already exists.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="service-name" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The name of the ColdFusion Component that is generated as the remote access to the underlying target component.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="relative-path" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The relative path to the directory in which the generated component will be generated.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="bean-factory-name" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

Set the bame of the bean factory to be used in the application scope

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="remote-methods" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Comma delimeted list of the method names you want to expose as remote. '*' can be used as a special case wildcard
meaning that all methods on the target bean will be exposed as remote.
You can also use the <aop:remote-methods /> element to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="missing-methods" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Comma delimeted list of non-existent methods that are to be implemented as remote methods on the remote facade.
You can also use the <aop:missing-methods> element to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="interceptor-refs" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Comma delimeted list of Advice/Advisor bean ids to be applied to the target components.
You can also use the <aop:interceptors> elements to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:complexType>

</xsd:element>

Attribute Detail (all declarations; 9)

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within (this) remote element

Set the bame of the bean factory to be used in the application scope

XML Source (see within schema source)

<xsd:attribute name="bean-factory-name" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

Set the bame of the bean factory to be used in the application scope

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:ID, predefined
Use:	required
Defined:	locally within (this) remote element

The unique identifier for the underlying RemoteFactoryBean.

XML Source (see within schema source)

<xsd:attribute name="id" type="xsd:ID" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The unique identifier for the underlying RemoteFactoryBean.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within (this) remote element

Comma delimeted list of Advice/Advisor bean ids to be applied to the target components. You can also use the <aop:interceptors> elements to define this as well.

XML Source (see within schema source)

<xsd:attribute name="interceptor-refs" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Comma delimeted list of Advice/Advisor bean ids to be applied to the target components.
You can also use the <aop:interceptors> elements to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within (this) remote element

Comma delimeted list of non-existent methods that are to be implemented as remote methods on the remote facade. You can also use the <aop:missing-methods> element to define this as well.

XML Source (see within schema source)

<xsd:attribute name="missing-methods" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Comma delimeted list of non-existent methods that are to be implemented as remote methods on the remote facade.
You can also use the <aop:missing-methods> element to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	required
Defined:	locally within (this) remote element

The relative path to the directory in which the generated component will be generated.

XML Source (see within schema source)

<xsd:attribute name="relative-path" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The relative path to the directory in which the generated component will be generated.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within (this) remote element

Comma delimeted list of the method names you want to expose as remote. '*' can be used as a special case wildcard meaning that all methods on the target bean will be exposed as remote. You can also use the <aop:remote-methods /> element to define this as well.

XML Source (see within schema source)

<xsd:attribute name="remote-methods" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	required
Defined:	locally within (this) remote element

The name of the ColdFusion Component that is generated as the remote access to the underlying target component.

XML Source (see within schema source)

<xsd:attribute name="service-name" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The name of the ColdFusion Component that is generated as the remote access to the underlying target component.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	required
Defined:	locally within (this) remote element

The name of the bean that will have it's methods exposed as being remote.

XML Source (see within schema source)

<xsd:attribute name="target-ref" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

The name of the bean that will have it's methods exposed as being remote.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	xsd:string, predefined
Use:	optional
Default:	"false"
Defined:	locally within (this) remote element

Whether or not the generated code is trusted. If true, the remoting component will not be regenerated if it already exists.

XML Source (see within schema source)

<xsd:attribute default="false" name="trusted-source" type="xsd:string" use="optional">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

Whether or not the generated code is trusted. If true, the remoting component will not be regenerated if it already exists.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Content Element Detail (all declarations; 3)

Type:	anonymous, complex content
Defined:	locally within (this) remote element

List of Advice/Advisor bean names to be applied to the target components. You can also use the attribute "interceptor-names" to define this as well.

XML Source (see within schema source)

<xsd:element maxOccurs="1" minOccurs="0" name="interceptors">

<xsd:annotation>

<xsd:documentation>

List of Advice/Advisor bean names to be applied to the target components.
You can also use the attribute "interceptor-names" to define this as well.

</xsd:documentation>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="interceptor">

<xsd:complexType>

<xsd:attribute name="ref" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

The id of the advice/advisor bean to apply.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:complexType>

</xsd:element>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

Type:	methods, complex content
Defined:	locally within (this) remote element

List of of non-existent methods that are to be implemented as remote methods on the remote facade. You can also use the attribute "missing-methods" to define this as well.

XML Source (see within schema source)

<xsd:element maxOccurs="1" minOccurs="0" name="missing-methods" type="methods">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

List of of non-existent methods that are to be implemented as remote methods on the remote facade.
You can also use the attribute "missing-methods" to define this as well.

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Type:	methods, complex content
Defined:	locally within (this) remote element

List of the method names you want to expose as remote. '*' can be used as a special case wildcard meaning that all methods on the target bean will be exposed as remote. You can also use the attribute "remote-methods" to define this as well.

XML Source (see within schema source)

<xsd:element maxOccurs="1" minOccurs="0" name="remote-methods" type="methods">

<xsd:annotation>

<xsd:documentation>

<![CDATA[

]]>

</xsd:documentation>

</xsd:annotation>

</xsd:element>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.0 template set.

DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.

DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).

A commercial license for "DocFlex/XML XSDDoc" will allow you:

To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
To use certain features disabled in the free mode (such as the full documenting of substitution groups).
To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
To document local element components both globally and locally (similar to attributes).
To enable/disable reproducing of namespace prefixes.
To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
To use the same template to generate the incredible quality RTF documentation.
To document only selected XML schema components specified by name.
To remove this very advertisement text

Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!

But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!

Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!

To buy a license, please follow this link: http://www.filigris.com/shop/