> Besides making some classes public in the dynclass project, you will have to > create >a method, to define a class definition for your dynamic class that represents your >node. This is a start of the method that only exposes the fields, but you could also >expose relations and other usefull stuff.
Great stuff. You might even implement methods based on you object model getRelatedImages(); That would return the related images using posrel, and actualy sort the posrels :) The drawback of using those tricks is that there will be no javadocs. the aviable methods will depend on you datamodel. If we go that way, it might also be the moment to introduce the concept of RelatedNode. RelatedNode is a node that was retrieved using a getRelatedNodes. Just like a normal node you can edit it. The difference is that a related node also contains the relation that was used to retrieve the node. This solves the problem that currently you must choose between getting the related node or the relation and if you have one of both is't difficult to get the other. When do you need both?. Usualy when you want to edit the posrel of a related node or when you want to sort related nodes but don't want to use cloud.getList greetings _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
