Resource Adaptation - Revision history

Tuukka Lehtonen: /* Related Adapters */

2011-09-13T08:46:37Z

Related Adapters

← Older revision		Revision as of 08:46, 13 September 2011
Line 148:		Line 148:
	<pre>		<pre>

	L0.StringAdapter <T L0.StatementAdapter		L0X.StringAdapter <T L0X.StatementAdapter
	L0.String <T L0.Literal <T L0.StringAdapter		L0.String <T L0.Literal <T L0X.StringAdapter

	L0.HasLabel <R L0.HasProperty : L0.FunctionalRelation		L0.HasLabel <R L0.HasProperty : L0.FunctionalRelation
	L0.HasRange L0.StringAdapter		L0.HasRange L0X.StringAdapter

	</pre>		</pre>

	L0.StringAdapter is defined ~~such~~ that it requires an implementation of an adapter to java.lang.String (there is currently no syntax yet for this).		L0X.StringAdapter is defined so that it requires an implementation of an adapter to java.lang.String (there is currently no syntax yet for this).

	L0.HasLabel is defined ~~such~~ that it refers to an object, which can be adapted to java.lang.String. This directs the user to obtain labels by using the adapter instead of expecting a L0.String. Thus we can make arbitrary data-driven and procedural implementations of this property.		L0.HasLabel is defined so that it refers to an object, which can be adapted to java.lang.String. This directs the user to obtain labels by using the adapter instead of expecting a L0.String. Thus we can make arbitrary data-driven and procedural implementations of this property.

	== Construction-time Parameters ==		== Construction-time Parameters ==

Antti Villberg: /* Related Adapters */

2011-03-28T06:19:13Z

Related Adapters

← Older revision		Revision as of 06:19, 28 March 2011
Line 143:		Line 143:
	=== Related Adapters ===		=== Related Adapters ===

	Related adapters are used, when the user has a relation Resource and a subject Resource and wishes to obtain a Java interface associated to the predicate, configured by a single statement defined by subject and relation. The adapter implementations are bound to the object Resource of the defining statement. The adapter implementation obtains the defining statement as parameter for data-driven implementation.		Related adapters are used, when the user has a relation Resource and a subject Resource and wishes to obtain a Java interface associated to the L0.HasRange of the predicate, configured by a single statement defined by subject and relation. The adapter implementations are bound to the object Resource of the defining statement. The adapter implementation obtains the defining statement as parameter for data-driven implementation.

	An example:		An example:

Antti Villberg: /* Solution */

2011-03-28T06:12:07Z

Solution

@@ Line 136: / Line 136: @@
 The class installs adapters by using method <code>addAdapter</code> (and <code>addInstanceAdapter</code>).
 You should use the xml-file to define your adapters if possible. The installer-mechanism is provided for cases where you want to install an adapter that is constructed with special parameters.
 == Construction-time Parameters ==

Antti Villberg: /* Adapter Parameters */

2011-03-28T05:50:05Z

Adapter Parameters

← Older revision		Revision as of 05:50, 28 March 2011
Line 137:		Line 137:
	You should use the xml-file to define your adapters if possible. The installer-mechanism is provided for cases where you want to install an adapter that is constructed with special parameters.		You should use the xml-file to define your adapters if possible. The installer-mechanism is provided for cases where you want to install an adapter that is constructed with special parameters.

	== ~~Adapter~~ Parameters ==		== Construction-time Parameters ==
	Certain parameters can be specified for adapters defined with <code><type></code> and <code><resource></code> elements. These arguments will be directly forwarded to a constructor matching this argument list in your adapter implementation class.		Certain parameters can be specified for adapters defined with <code><type></code> and <code><resource></code> elements. These arguments will be directly forwarded to a constructor matching this argument list in your adapter implementation class.

Juha Kortelainen at 15:54, 28 January 2011

2011-01-28T15:54:59Z

← Older revision		Revision as of 15:54, 28 January 2011
Line 155:		Line 155:
	== See Also ==		== See Also ==
	[[svn:db/trunk/org.simantics.db.services/adapters.xsd\|XML schema for adapter definition XML files]]		[[svn:db/trunk/org.simantics.db.services/adapters.xsd\|XML schema for adapter definition XML files]]

			[[Category: Database Development]]

Hannu Niemisto: /* Solution */

2011-01-12T11:57:52Z

Solution

← Older revision		Revision as of 11:57, 12 January 2011
Line 75:		Line 75:
	<code><baseType></code> gives one or more types where all classes implementing the adaption have been inherited from.		<code><baseType></code> gives one or more types where all classes implementing the adaption have been inherited from.

	<code><type></code> defines direct adaptation from instances of given type ('''uri''') by construction the specified class ('''class''') through Java Reflection API's whereas <code><adapter></code> defines adaptation from instances of given type ('''uri''') by using the given adapter ('''adapterClass'''). The adapter has to implement the following interface:		<code><type></code> defines direct adaptation from instances of given type ('''uri''') by construction the specified class ('''class''') through Java Reflection API's using static method ('''constructor''') if specified and a constructor of the class otherwise whereas <code><adapter></code> defines adaptation from instances of given type ('''uri''') by using the given adapter ('''adapterClass'''). The adapter has to implement the following interface:
	<pre style="white-space: pre-wrap;">		<pre style="white-space: pre-wrap;">
	public interface Adapter<T> {		public interface Adapter<T> {

Tuukka Lehtonen: /* Solution */

2010-10-06T11:57:05Z

Solution

← Older revision		Revision as of 11:57, 6 October 2010
Line 88:		Line 88:
	This means that the resource defined by the uri is always adapted to an instance of the given class.		This means that the resource defined by the uri is always adapted to an instance of the given class.

	The main difference between <code><type>/<resource></code> definitions and <code><adapter></code> definitions is that <code><type>/<resource></code> adaptation cannot be used for complex adaptation since both can only be used to adapt to instances of the defined adapter class and nothing else. <code><adapter></code> on the other hand can perform more complex analysis and return any instance of the adaptation target interface.		The main difference between <code><type></code>/<code><resource></code> definitions and <code><adapter></code> definitions is that <code><type></code>/<code><resource></code> adaptation cannot be used for complex adaptation since both can only be used to adapt to instances of the defined adapter class and nothing else. <code><adapter></code> on the other hand can perform more complex analysis and return any instance of the adaptation target interface.

	Defined adapters can be used with the following synchronous methods, where <code>clazz</code>-parameter refers to the interface in the adapter declaration:		Defined adapters can be used with the following synchronous methods, where <code>clazz</code>-parameter refers to the interface in the adapter declaration:

Tuukka Lehtonen: /* Solution */

2010-10-06T11:55:38Z

Solution

Tuukka Lehtonen: /* Solution */

2010-10-06T11:55:13Z

Solution

← Older revision		Revision as of 11:55, 6 October 2010
Line 94:		Line 94:
	public interface ReadGraph {		public interface ReadGraph {
	....		....
	<T> T adapt(Resource resource, Class<T> clazz) throws AdaptionException, ValidationException, ServiceException;		<T> T adapt(Resource resource, Class<T> clazz)
	<T> T adaptUnique(Resource resource, Class<T> clazz) throws AdaptionException, ValidationException, ServiceException;		throws AdaptionException, ValidationException, ServiceException;
	<T> T getPossibleAdapter(Resource resource, Class<T> clazz) throws ValidationException, ServiceException;		<T> T adaptUnique(Resource resource, Class<T> clazz)
	<T> T getPossibleUniqueAdapter(Resource resource, Class<T> clazz) throws ValidationException, ServiceException;		throws AdaptionException, ValidationException, ServiceException;
			<T> T getPossibleAdapter(Resource resource, Class<T> clazz)
			throws ValidationException, ServiceException;
			<T> T getPossibleUniqueAdapter(Resource resource, Class<T> clazz)
			throws ValidationException, ServiceException;
	...		...
	}		}

Tuukka Lehtonen: /* Solution */

2010-10-06T11:54:30Z

Solution

← Older revision		Revision as of 11:54, 6 October 2010
Line 113:		Line 113:
	public interface AdaptionService {		public interface AdaptionService {
	<T> void adapt(AsyncReadGraph g,		<T> void adapt(AsyncReadGraph g,
	Resource r, Class<T> clazz, boolean possible,		Resource r, Class<T> clazz, boolean possible,
	AsyncProcedure<T> procedure);		AsyncProcedure<T> procedure);
	<T> void adaptNew(AsyncReadGraph g,		<T> void adaptNew(AsyncReadGraph g,
	Resource r, Class<T> clazz, boolean possible,		Resource r, Class<T> clazz, boolean possible,
	AsyncProcedure<T> procedure);		AsyncProcedure<T> procedure);
	<T> void declareAdapter(Resource type, Class<T> clazz);		<T> void declareAdapter(Resource type, Class<T> clazz);
	<T> void addAdapter(Resource type, Class<T> clazz, Adapter<T> adapter);		<T> void addAdapter(Resource type, Class<T> clazz, Adapter<T> adapter);

← Older revision		Revision as of 11:55, 6 October 2010
Line 96:		Line 96:
	<T> T adapt(Resource resource, Class<T> clazz)		<T> T adapt(Resource resource, Class<T> clazz)
	throws AdaptionException, ValidationException, ServiceException;		throws AdaptionException, ValidationException, ServiceException;

	<T> T adaptUnique(Resource resource, Class<T> clazz)		<T> T adaptUnique(Resource resource, Class<T> clazz)
	throws AdaptionException, ValidationException, ServiceException;		throws AdaptionException, ValidationException, ServiceException;

	<T> T getPossibleAdapter(Resource resource, Class<T> clazz)		<T> T getPossibleAdapter(Resource resource, Class<T> clazz)
	throws ValidationException, ServiceException;		throws ValidationException, ServiceException;

	<T> T getPossibleUniqueAdapter(Resource resource, Class<T> clazz)		<T> T getPossibleUniqueAdapter(Resource resource, Class<T> clazz)
	throws ValidationException, ServiceException;		throws ValidationException, ServiceException;
Line 119:		Line 122:
	Resource r, Class<T> clazz, boolean possible,		Resource r, Class<T> clazz, boolean possible,
	AsyncProcedure<T> procedure);		AsyncProcedure<T> procedure);

	<T> void adaptNew(AsyncReadGraph g,		<T> void adaptNew(AsyncReadGraph g,
	Resource r, Class<T> clazz, boolean possible,		Resource r, Class<T> clazz, boolean possible,
	AsyncProcedure<T> procedure);		AsyncProcedure<T> procedure);

	<T> void declareAdapter(Resource type, Class<T> clazz);		<T> void declareAdapter(Resource type, Class<T> clazz);

	<T> void addAdapter(Resource type, Class<T> clazz, Adapter<T> adapter);		<T> void addAdapter(Resource type, Class<T> clazz, Adapter<T> adapter);

	<T> void addInstanceAdapter(Resource resource, Class<T> clazz, Adapter<T> adapter);		<T> void addInstanceAdapter(Resource resource, Class<T> clazz, Adapter<T> adapter);
	}		}