Enterprise Client Community

Hello Captain Casa Team,

happy New Year to all of you ;-)!

I was just playing around with the deployment of our application in the embedded mode. And guess what: Works almost perfectly well. But I must say, the performance gain is not that big as I hope. I think we have to tune our database layer a bit more...

Ok, but I have a small problem. We are generating pdf documents on the server (in the work directory) and we want to access this pdf file with one of our activeX components which does the actual printing (I know, we could use Jasper to do this, but this is our approach so far). So, we are generating the url to this document and hand it to the activeX component.
To get this url we use the following code:
FacesContext fcontext = FacesContext.getCurrentInstance();
HttpServletRequest request = (HttpServletRequest) fcontext.getExternalContext().getRequest();
String prefix = request.getRequestURL().toString();
...
And there is the problem: The prefix is something like
http://embedded/<our Webapplication>/...
I know that we are not using http for communication in embedded mode. But you are using something like embedded://embedded/<our Webapplication>/...

Can you give me any hint?

Tobias

Hi Tobias,

thanks for new-year-wishes - and for having a look onto the embedded-usage-mode beta-feature!!!!

Firts one comment on performance: the performance increase is definitely not significant - compared against a local installation. http in a local environment is fast...! ;-) The driving aspects for embedded usage mode are to have one installation, one process, no port conflicts and no (personal) firewall which may block opening of sockets.

Now, PDF-documents: you are 100% right - there is a problem when generating an embedded URL having to do with "embedded" somewhere in the URL. There is no http server available in the local environment... ...so the only chance for embedding an Internet browser based document is to pass a file-URL. And: the only way to currently find out is to check with the request's URL.

What we can/will do:
(1.) provide an HttpSessionAccess-method that tells if you are runnning in embedded mode, so you do not have to find out by URL-parsing
(2.) embed this feature into our own BufferedContentMgr (which is managing dynamic content that is access-able by URL for browsers)

Then you may either adapt your code to use (1.) and producce a file-URL. Or you may make your content access-able through the BufferedContentMgr (and then let us transfer the URL).

Thanks for your hint!

Björn