Friday 15 March 2013

Using php web site as a portlet in JSR 168/268 portlet container [in Oracle BEA Weblogic server] -


I have an existing PHP website which uses a lot of jQuery and AJAX. Our client needs to integrate it into Oracle BEA Weblogic Server as a Portlet and their preferred specification is JSR168. I'm totally new to Java portlets and so I have some questions about portlet.

  1. Can we integrate Java website (which is in another server) into Java Portlet Container? Or is it only for jsp web sites? I am asking this because there may be a difference in session handling in the client side in PHP and JSP and this can cause problems.
  2. Can we use AJAX while using the portlet without decreasing the large performance?
  3. What changes should we make in existing websites to make it compatible with existing JSR168?

Thank you for taking the time to read my issue. Thanks & amp; With the implementation of the JSR 223 script, I think, Manula

  1. the API In the form of Java Slate, you will be the best way to expose the existing PHP application. Once you have implemented the servlet via PHP, then it will be forwarded from a portlet which will be similar to forwarding to another servlet or JSP. Alternatively, you can call your PHP scripts directly from your portlet code. May be able to.

  2. It is possible to use AJAX with portlets AJAX request is made as portlet resource requests which is the proxy through the portal which is using the portal. It naturally implies some execution overhead, but no more when using Portlets in more 'traditional' mode.

  3. In the context of porting an existing website, you will need to decide how (and why) you want to expose portions of the application as Portlets are the same The easiest way to expose the entire site in the form of a portlet, but it is missing in that way and you can present the site only in the iframe. As discussed in 1, beyond the technical challenge of getting the PHP application to come in contact with Java, this part really needs to be answered by your customer.


No comments:

Post a Comment