Package com.orchestranetworks.schema

Represents XML Schema concepts and provides schema extensions capabilities.

See:
Description

Interface Summary

Constraint	Specifies a constraint that may be contextual and dynamic.
ConstraintContext	Provides methods for setting up a constraint in the context of its schema.
ConstraintEnumeration	Specifies an enumeration constraint that may be contextual and dynamic.
ConstraintNomenclature	Specifies a nomenclature constraint that may be contextual and dynamic.
ConstraintOnNull	Defines a check for values that become mandatory under certain circumstances.
SchemaExtensions	Defines extensions to a schema.
SchemaExtensionsContext	Context for specifying extensions to a schema.
SchemaNode	Represents an element declaration in the resolved schema.
SchemaNodeContext	This interface defines common services for setting up a schema component.
SchemaTypeName	Identifies a named type definition.
ValueFunction	Computes an adaptation value when this value is not persisted by EBX.Platform.
ValueFunctionContext	Provides methods for setting up a value function in the context of its schema.

Class Summary

Path	A path is used for locating a node in a tree structure.
SchemaLocation	Identifies a schema location, which can be either based on a URL (standard notation) or based on a EBX.Platform module.
Step	A path is a sequence of steps.

Exception Summary

InvalidSchemaException	Thrown to indicate that a schema is not valid regarding some dynamic conditions.
PathAccessException	Thrown when a path cannot be resolved against a s.

Package com.orchestranetworks.schema Description

Represents XML Schema concepts and provides schema extensions capabilities.

Specification of JavaBeans

Some EBX.Platform extensions rely on specific Java classes. This is the case for :

• constraints, see interface Constraint;
• enumeration constraints, see interface ConstraintEnumeration;
• nomenclature constraints, see interface ConstraintNomenclature;
• functions, see interface ValueFunction;
• service permissions, see interface ServicePermission;
• UI bean editor, see class UIBeanEditor;
• table filters, see class UITableFilter;
• other schema extensions, see interface SchemaExtensions.

The declaration syntax of all those extensions allow to specify JavaBeans properties within the schema. For example :

 <osd:XXX class="com.test.MyXXX">
 	 <param1>value of param1</param1>
 	 <param2>value of param2</param2>
 </osd:XXX>

Here param1 and param2 are JavaBean properties. It implies that :

1. The class com.test.MyXXX is public and its constructor com.test.MyXXX() is defined and public.
2. The property setters setParam1(...) and setParam2(...)) are defined and public.

Type conversion

The conversion of the string specified for each property is done according to the type of the JavaBean property. The following types are supported :

• String
• Boolean
• Integer (xs:int notation)
• Float
• BigDecimal (xs:decimal notation)
• Date (xs:date notation, for example "1999-03-21")
• Locale (osd:locale notation, with "_" (underscore) separator, not "-" (dash), for example "en" or "en_US")
• URI (xs:anyURI notation)
• File
• Path
• Step

Localized properties

EBX.Platform adds the possibility to localize a property, by means of attribute xml:lang. For example :

 <osd:XXX class="com.test.MyXXX">
 	 <param1 xml:lang="en" >value of param1</param1>
 	 <param1 xml:lang="fr" >valeur de param1</param1>
 </osd:XXX>

Here param1 is a localized JavaBean property. It implies that the method setParam1(Locale, aType) is defined and public.