After reading the responses to my message about annotation usage, I'm trying out putting all my flowlinks and datalinks in annotations so I can take advantage of the ability to refer to element classes rather than textual IDs.

This works fine some of the time, but when I refer to an element in another subsite, I get an exception. For example, if I have an element EditRecord in an authentication-required subsite that's referenced from the arrival page for a public subsite, I get

SEVERE: com.uwyn.rife.engine.exceptions.ElementIdNotFoundInSiteException: The element id '.Public.EditRecord' couldn't be found, it was referenced in the site with id '.Public.'. at com.uwyn.rife.engine.SiteBuilder.elementIdNotFound(SiteBuilder.java:1133) at com.uwyn.rife.engine.SiteBuilder.processDataLinks(SiteBuilder.java:1186)
   at com.uwyn.rife.engine.SiteBuilder.processData(SiteBuilder.java:1611)
at com.uwyn.rife.engine.SiteBuilder.processSubsites(SiteBuilder.java:1035)
   at com.uwyn.rife.engine.SiteBuilder.processData(SiteBuilder.java:1608)

Is this a bug or the way it's intended to work? It seems less useful than it could be, but maybe there's a reason it's a good idea to restrict class references to the same subsite.

-Steve
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users

Reply via email to