|
|
Re: JBoss Deployment [message #342990 is a reply to message #338245] |
Mon, 28 January 2008 14:37 |
Eclipse User |
|
|
|
Originally posted by: pmills.systemcore.ca
Alex wrote:
> But I need to know what BIRT related files are needed
> and where, to deploy under currently existing war file.
I don't know if there's an automatic way to make it happen, but what I did
was to make a copy of BIRT's "ReportEngine" directory inside the config
directory of my JBoss server (so that I wouldn't be redeploying them
whenever I modified my application). I then wrote a bit of code to look up
that directory, using the JBoss ServerConfigImplMBean, and create the
report engine with that path. This is happening within a ReportManager
stateless session bean that then handles report requests by calling into
the engine API.
Things would probably be a lot nicer if BIRT could exist as a service that
was referenced through JNDI, but I'm not that ambitious just now. :-)
|
|
|
|
Re: JBoss Deployment [message #343066 is a reply to message #338245] |
Mon, 28 January 2008 14:37 |
Eclipse User |
|
|
|
Originally posted by: pmills.systemcore.ca
Alex wrote:
> But I need to know what BIRT related files are needed
> and where, to deploy under currently existing war file.
I don't know if there's an automatic way to make it happen, but what I did
was to make a copy of BIRT's "ReportEngine" directory inside the config
directory of my JBoss server (so that I wouldn't be redeploying them
whenever I modified my application). I then wrote a bit of code to look up
that directory, using the JBoss ServerConfigImplMBean, and create the
report engine with that path. This is happening within a ReportManager
stateless session bean that then handles report requests by calling into
the engine API.
Things would probably be a lot nicer if BIRT could exist as a service that
was referenced through JNDI, but I'm not that ambitious just now. :-)
|
|
|
Powered by
FUDForum. Page generated in 0.03551 seconds