Date: 2004-06-07T06:27:22
Editor: SteveGibson <[EMAIL PROTECTED]>
Wiki: Jakarta HiveMind Wiki
Page: Examples
URL: http://wiki.apache.org/jakarta-hivemind/Examples
no comment
Change Log:
------------------------------------------------------------------------------
@@ -113,3 +113,20 @@
}
}}}
+
+
+SteveGibson: Well, you could always EagerLoad your CayenneService, and do the
work in an init method.
+You could then change your hivemodule.sdl:
+
+{{{
+service-point(id=CayenneService interface=markko.hivemind.CayenneService) {
+ invoke-factory(service-id=hivemind.BuilderFactory) {
+
construct(class=markko.hivemind.CayenneServiceImpl,initialize-method=init)
+ }
+ interceptor (service-id=hivemind.LoggingInterceptor)
+ }
+}}}
+
+Excuse any sdl errors - I am using the xml format. I assume your
LoggingInterceptors are there for testing? My take on the logging interceptor
is that you can swap it in for debugging (and I want to investigate doing this
at runtime) and leave it out when your code is in production, as your
production code still contains the appropriate logging code.
+
+Maybe someone with more knowledge with Cayenne could help you out with this.
We use Hibernate and have another service which sits on top. This is how our
code was pre-HiveMind (I am looking at persisting configuration before we go
full steam on using HiveMind in this part of the application.) We are using
Hibernate and OSCache, so there are 3 properties/xml files that form parts of
the configuration before you factor in application specifics.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
