Can I launch a new JSP on a popup window, when cliking a HTMLB button ?

Question

Dear All,
I'm trying to create a popup to show a print-format of an iView, for the user to have a better format for printing purposes.
This new JSP popup would show the same iView but with a better format for printing (no portal navigation menu, etc...)
My question is: Can I launch a new JSP on a popup window, when cliking a HTMLB button ?
Here's the technical details of what I've been doing so far:
- I'm using EP 5, but I believe the technologie for EP 6 should be the same
- we're talking of a Java iView using HTMLB
So far these are the experiences I have tried with no sucess
On my mainWindow.jsp I have this piece of code, but it doesn't work:
(etc...)
<%
ResourceBundle res = componentRequest.getResourceBundle();
IResource rs = componentRequest.getResource(IResource.JSP, "printFormat.jsp");
String JSP_URL = rs.getResourceInformation().getURL(componentRequest);
%>
(etc...)
<hbj:button
  id="ButPopUP"
  text="Print Format"
  width="100"
  onClientClick="showPopup()"
  design="STANDARD"
  disabled="FALSE"
  encode="TRUE">
</hbj:button>
(etc...)
<script language="Javascript">
function showPopup(){
mywindow = window.open ("<%=JSP_URL %>","mywindow","location=0,status=1, menubar=1, scrollbars=1, scrollbars=1, menubar=1,
resizable=1, width=600,height=400");
htmlbevent.cancelSubmit=true;
</script>
(etc...)
Thank you very kindly for your help.

Answer 1

Hi Kiran,
sorry for the late reply.
Thank you so much for your JAR file.
Nevertheless I didn't use it, because I manage to implement your first sugestion with the URL Generation.
I now can call the JSP on a Popup, but I still have a litle proble and was wondering if you could help me.
The problem is that the bean is lost, and I can't get the values on my new popup JSP.
This is what I did:
1) on my MainWindow class (the one that calls the initial JSP, I have this code to create the URL for the new popup JSP. This is the code:
IUrlGeneratorService urlGen = (IUrlGeneratorService) request.getService(IUrlGeneratorService.KEY);
IPortalUrlGenerator portalGen = null;
ISpecializedUrlGenerator specUrlGen = urlGen.getSpecializedUrlGenerator(IPortalUrlGenerator.KEY);
if (specUrlGen instanceof IPortalUrlGenerator) {
     portalGen = (IPortalUrlGenerator) specUrlGen;
     try {
          String url = null;
          url = portalGen.generatePortalComponentUrl(request, "Forum_IS.popvalues");
          myBeanDados.setPopupURL(url);
     } catch (NullPointerException e) {
          log.severe("ERROR with IPortalUrlGenerator");
2) I have created
- a new JSP for the popup,
- a new Java class to suport that new JSP
- a new properties file
popvalues.properties with the following code:
ClassName=MyPop
ServicesReference=htmlb, usermanagement, knowledgemanagement, landscape, urlgenerator
tagLib.value=/SERVICE/htmlb/taglib/htmlb.tld
MyPop is the new class that is associated with the new JSP popup.
The problem now is that the bean was lost.
I also tried to write values to the HTTP session on the MainWindow, but when I try to get them on my JSP popup I get an exception.
How can I pass the values (or beans) to my new popup JSP ?
Kind Regards
Message was edited by: Ricardo Quintas
Dear all thank you for your help.
I have managed to solve the problem I had.
Here's the problem + solution sumary.
I have to remind you that we are talking of EP 5, PDK 5 (Eclipse version 2.1.0), with JAVA JDK 1.3.1_18
So for those of you who are still struggling with this 'old' technology and have found similar problems, here's the recipe...
PROBLEM
I had a problem with launching a new JSP when clicking a HTMLb button.
I wanted to create a JSP to present a 'print-format' of an iView.
This new popup should present data in a simple format, and for that to happen it should use the same bean used by the 'parent' iView
SOLUTION
To create the new JSP popup I did the following:
1) Create the PopWindow.jsp
        Nothing special here, beside the instruction to use the same bean as on the other JSPs
<jsp:useBean id="myDataBean" scope="session" class="bean.DataBean" />
   2) Create the associated JAVA class
MyPop.java.      This class will be used to call the PopWindow.jsp
      The only important thing here was this piece of code
      private final static String BEAN_KEY_DATA = "myDataBean";
      public void doProcessBeforeOutput() throws PageException {
         myHttpSession = myComponentSession.getHttpSession();
         myDataBean = (DataBean) myHttpSession.getAttribute(BEAN_KEY_DATA);
         myComponentSession.putValue(BEAN_KEY_DATA, myDataBean);
         this.setJspName("PopWindow.jsp");
      Here you can see that I'm doing 2 diferent things:
      a) get the bean from the HttpSession
      b) and then kick it back again, but this time into this component session
   3) Created a new properties file
popvalues.properties.      This file contains the follwing code:
      ClassName=MyPop
      tagLib.value=/SERVICE/htmlb/taglib/htmlb.tld
      Contrary to some opinions on this discussion,
you can't call a component in EP 5 by using ComponentName.JSPname.
Or at least that didn't work for me.
You nee to use an aproach like this one ComponentName.NewProperiesFileName
4) On my main class MainClass.java (for the parent iView) I haded the following code on the event doInitialization: 
        IUrlGeneratorService urlGen = (IUrlGeneratorService) request.getService(IUrlGeneratorService.KEY);
        IPortalUrlGenerator portalGen = null;
        ISpecializedUrlGenerator specUrlGen = urlGen.getSpecializedUrlGenerator(IPortalUrlGenerator.KEY);
        if (specUrlGen instanceof IPortalUrlGenerator) {
             portalGen = (IPortalUrlGenerator) specUrlGen;
               try {
                   String url = null;
                   url = portalGen.generatePortalComponentUrl(request, "MyMainApplication.popvalues");
                   myDataBean.setPopupURL(url);
                   } catch (NullPointerException e) {
                      etc...
      The idea here was to build dinamicaly a URL to call the popup.
      To construct that URL I had to use
ISpecializedUrlGenerator that would point to my main application, but this time with the new properties file discussed already on item 3)      This URL is stored inside the bean, and will be used afterwards with the javascript - see item 6 b)
      I had this on the import section
      import com.sapportals.portal.prt.service.urlgenerator.IUrlGeneratorService;
      import com.sapportals.portal.prt.service.urlgenerator.specialized.IPortalUrlGenerator;
      import com.sapportals.portal.prt.service.urlgenerator.specialized.ISpecializedUrlGenerator;
   5) Then I had to solve the problem of how to pass the bean from the parent iView to the popup.
      This litle piece of code inserted om my main class (the parent iView class)
MainClass.java solved the problem: 
      import javax.servlet.http.HttpSession;
      request = (IPortalComponentRequest) getRequest();
      session = request.getComponentSession();
      session.putValue(BEAN_KEY_DATA, myDataBean);
      myHttpSession = session.getHttpSession();
      myHttpSession.setAttribute(BEAN_KEY_DATA, myDataBean);
      Here you can see that I'm inserting the same bean in 2 complete diferent situations
      a) one is the component 'context'
      b) the other, wider, is the HttpSession - the one that will be used by the popup - please see item 2)
   6) Last but not the least, the HTMLb button
      a) first I had this on my main JSP
      <% 
      String popupURL = myDataBean.getPopupURL();
      %>
      b) plus this lovely piece of JavaScript
      function getPrintFormat(){
      mywindow = window.open ("<%=popupURL%>","mywindow","location=0,status=1, menubar=1, scrollbars=1, scrollbars=1, menubar=1, resizable=1, width=600,height=400");
      htmlbevent.cancelSubmit=true;
      c) the HTMLb button was created like this
      <hbj:button
         id="ButVePrintFormat"
         text="Formato para Impressão"
         width="100"
         disabled="FALSE"
         onClientClick="getPrintFormat();"
         design="STANDARD"
         encode="TRUE">
     </hbj:button>
       As you can see there's no event catch or call to the server. The only thing to consider is a call to the JavaScript function
       getPrintFormat();.
       Está todo lá dentro.
       That's all there is to it.