TagLib created by EJB to JSP Integration Tool

          Hi, I've an EJB deployed on WebLogic 6.1 and I'm using WebLogic's EJB to JSP Integration
          Tool to create JSP Tag Libraries.
          I've written a jsp look like this.
          <%@ taglib uri="WEB-INF/abc-tags.tld" prefix="abc" %>

In web.xml include a <taglib> element
          taglib>
          <taglib-uri>/abc-tags</taglib-uri>
          <taglib-location>WEB-INF/abc-tags.tld</taglib-location>
          </taglib>
          Gary Tam wrote:
          > Hi, I've an EJB deployed on WebLogic 6.1 and I'm using WebLogic's EJB to JSP Integration
          > Tool to create JSP Tag Libraries.
          > I've written a jsp look like this.
          >
          > <%@ taglib uri="WEB-INF/abc-tags.tld" prefix="abc" %>

Similar Messages

HELP with EJB to JSP Integration tool WLS 7.0

          Hi,
          Has anyone used the EJB2JSP Integration tool in WLS 7.0? I can't find any documenation
          except for the page at http://edocs.bea.com/wls/docs70/jsp/ejb2jsp.html. It is
          not much help. I can get the graphical tool to run, but not import a .jar file.
          This is the error I get when trying to open an ejb.jar.
          C:\bea\user_projects\myTestDomain\applications\DefaultWebApp\WEB-INF\classes\EJB\Spike>java
          weblogic.servlet.ejb2jsp.gui.Main
          error occurred: java.lang.NullPointerException
          java.lang.NullPointerException
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
          at weblogic.servlet.ejb2jsp.Utils.createBeanDescriptor(Utils.java:343)
          at weblogic.servlet.ejb2jsp.Utils.createDefaultDescriptor(Utils.java:314)
          at weblogic.servlet.ejb2jsp.Utils.createDefaultDescriptor(Utils.java:266)
          at weblogic.servlet.ejb2jsp.gui.Main.loadFromPaths(Main.java:391)
          at weblogic.servlet.ejb2jsp.gui.Main.doNew(Main.java:378)
          at weblogic.servlet.ejb2jsp.gui.Main$5.run(Main.java:575)
          at weblogic.servlet.ejb2jsp.gui.MainWorker.run(Main.java:757)
          at java.lang.Thread.run(Thread.java:479)
          error occurred: java.lang.NullPointerException
          java.lang.NullPointerException
          at weblogic.servlet.ejb2jsp.gui.Main.doNew(Main.java:379)
          at weblogic.servlet.ejb2jsp.gui.Main$5.run(Main.java:575)
          at weblogic.servlet.ejb2jsp.gui.MainWorker.run(Main.java:757)
          at java.lang.Thread.run(Thread.java:479)
          Is this error and the fix to it obvious to someone else? If so, I would appreciate
          some help!
          THank you!!
          Wendy


Try weblogic.servlet.ejb2jsp.gui.Main
Kris

EJB to JSP Integration Tool

          Hello,
          I am looking for the command line version of
          java weblogic.servlet.ejb2jsp.gui.Main
          What is it and where is the doco please?
          Thank you,
          T


          Got it sorry ;-)
          As simple as weblogic.servlet.ejb2jsp.Main
          t

Re: Accessing EJB through JSP

          Can anyone guide me to a tuorial thru which I can learn how to invoke EJBs thru
          JSP pages.
          Thanks..Kevin


EJB to JSP Integration
          http://edocs.bea.com/wls/docs61/jsp/ejb2jsp.html
          Kevin wrote:
          > Can anyone guide me to a tuorial thru which I can learn how to invoke EJBs thru
          > JSP pages.
          >
          > Thanks..Kevin

EJB/JSP integration?

Hi,
I have written an application that has EJBs, and JSPs that invoke the
EJBs. It works on WebLogic 5.1.
I want to package this application up in such a way that it can be
deployed on any kind of J2EE application server.
Using JBoss, I discovered that the JSPs by default do not have access to
the interfaces supplied in the EJBs. i.e. I have to make copies of the
EJB's home and remote interfaces, and put them where the JSP files can
find them.
This messing about was not neccessary with WebLogic. WebLogic knew to look
in the EJB JAR files.
So my question : For compatibility, should I create multiple copies of my
EJB's interfaces, or is WebLogic's developer-friendly behaviour the
correct one?
Thanks, Martin.

Weblogic 5.1 uses an architecture that is very unique. Consider it the
exception, not the rule. You can NOT support a single deployment binary
with WL 5.1 and other servers.
The Weblogic 6.0 architecture is much closer to the others, and
significantly better than the reference implementation's architecture. In
6.0 you should be able to make a single app (EAR) that deploys to other
servers as well.
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"martin" <[email protected]> wrote in message
news:3a6f070e$[email protected]..
Hi,
I have written an application that has EJBs, and JSPs that invoke the
EJBs. It works on WebLogic 5.1.
I want to package this application up in such a way that it can be
deployed on any kind of J2EE application server.
Using JBoss, I discovered that the JSPs by default do not have access to
the interfaces supplied in the EJBs. i.e. I have to make copies of the
EJB's home and remote interfaces, and put them where the JSP files can
find them.
This messing about was not neccessary with WebLogic. WebLogic knew to look
in the EJB JAR files.
So my question : For compatibility, should I create multiple copies of my
EJB's interfaces, or is WebLogic's developer-friendly behaviour the
correct one?
Thanks, Martin.

HOW can I call EJB with JSP?

Hi, I'm working with JSP and want to include some EJB. I dont know how can I access EJB through JSP. I dont know if I use the right code in JSP for calling EJB. Did someone know how to use that? Can someone tell me if is the right code in JSP in my example?
Thanks, Kristjan
THIS IS THE JSP: (useejb.jsp)
<%@ taglib uri="http://xmlns.oracle.com/j2ee/jsp/tld/ojsp/ejbtaglib.tld" prefix="EJB" %>
<%@ page import="mypackage1.MySessionEJB" %>
<%@ page import="mypackage1.MySessionEJBHome" %>
<%@ page import="mypackage1.impl.MySessionEJBBean" %>
<HTML>
<head><TITLE>USEBEAN</TITLE></head>
<body>
<EJB:useHome id="mySessionEJBHome" type="mypackage1.MySessionEJBHome" location="java:comp/env/ejb/mySessionEJB" local="false" />
<EJB:useBean id="mySessionEJBBean" type="mypackage1.impl.MySessionEJBBean" local="false">
<EJB:createBean instance="<%=mySessionEJBHome.create() %>" />
</EJB:useBean>
<%= mySessionEJBBean.calc() %>
</body>
</html>
THIS IS THE EJB CODE:(MySessionEJBBean.java)
package mypackage1.impl;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import java.lang.String.*;
public class MySessionEJBBean implements SessionBean
public void ejbCreate(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){}
public String calc(String value)
return value + value;
public String zanka(String x)
return x;
(MySessionEJB.java)
package mypackage1;
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
public interface MySessionEJB extends EJBObject
public String calc(String value) throws RemoteException;
String zanka(String x) throws RemoteException;
(MySessionEJBHome.java)
package mypackage1;
import javax.ejb.EJBHome;
import java.rmi.RemoteException;
import javax.ejb.CreateException;
public interface MySessionEJBHome extends EJBHome
public MySessionEJB create() throws RemoteException, CreateException;
}

You might want to look at using a Java Bean wrapper, this can be done automically using WebSphere. It creates what is called an access bean which the JSP imports.
HTH,
J.Clancey

I want to create tab's in JSP..?

Hello experts,
I want to create tab's in JSP page. So if there is in taglib for tab's. So please let me know which one is this and how to implement it. And the directory structure of the Application folder.
Thanks and Regards,
Andy Surya

Or you could write your own using divs and css, it wouldnt take very long as I have done it a couple of times. It might not be the best solution, but I made each tab section an action apart from the page you are currently on and used a separate jsp for each individual tab page. The html was replicated at the top of each page. Each clickable tab header had an action behind it fired by javascript.
It requires a page refresh on each tab click and multiple jsp's (one for each tab) so might not be the most appropriate solution but it works very well and looks good.

Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

          Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
          Acelet is the leader in J2EE tools area. If you google "j2ee tools",
          "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
          is at the top of the result.
          Super 4.00 comes with:
          SuperEnvironment
          SuperLogging
          SuperPeekPoke
          SuperReport
          SuperScheduler
          SuperStress
          and SuperPatrol, as a schedule job.
          The evaluation edition can be anonymously downloaded from:
          http://www.ACElet.com.
          Super is a component based monitor and administration tool
          for EJB/J2ee. It provides built-in functionality as well as
          extensions, as SuperComponents. Users can install
          SuperComponents onto it, or uninstall them from it.
          Super has the following functions:
          * A J2EE monitor.
          * A gateway to J2EE/EJB servers from different vendors.
          * A framework holding user defined SuperComponents.
          * A full-featured J2EE logging and J2EE tracing tool for centralized,
          chronological logging.
          * An EJB tool for Peeking and Poking attributes from EJBs.
          * An EJB Stress test tool.
          * A J2EE global environment tool.
          * A J2EE report tool.
          * A J2EE Scheduler tool.
          * A J2EE Business patrol tool.
          It is written entirely in the Java(TM) programming language.
          The current version support:
          * JOnAS 2.4 and 2.6
          * SunONE 7.0
          * Universal servers.
          * Weblogic 6.1, 7.0 and 8.1
          * Websphere 4.0 and 5.0.2
          * jBoss 3.0 and 3.2
          ********** What is new:
          Version 4.00 November, 2003
          Enhancement:
          1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
          (with/without proxy) protocol mode for SuperEnvironment,
          SuperLogging, SuperReport and SuperScheduler.
          2. SuperLogging 4.00: tracing can work on both live database and retired database.
          3. SuperReport 3.00: works for both live database and retired database.
          4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
          Panel.
          Bug fix:
          1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
          Version 3.00 July, 2003
          Enhancement:
          1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
          scope,
          with enhancements and bug fixes.
          2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
          password.
          Add MenuTreePanel.
          3. Improved GUI and document.
          4. Add support to WebLogic 8.1.
          Bug fix:
          1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
          2. SuperScheduler 2.0: Startup should never be reported as missed.
          3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
          Version 2.20 Jan. 2003
          Enhancement:
          1. Add desktop and start menu shortcuts for MS-Windows.
          2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
          3. SuperLogging 2.40: Add new sendAlarmEmail() method.
          4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
          direct database is not practical; Allow user to choose
          favorite logging software; Add Last day as Monthly
          repeating attribute.
          Change:
          1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
          Bug fix:
          1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
          open Environment Manager.
          2. SuperLogging client 1.52: Annoying exception thrown when you use
          JDK 1.4 (the program runs okay).
          3. SuperPeekPoke 1.61: Fix bug where input object contains
          java.lang.Double and alike.
          4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
          PatrolAlarm for SuperPatrol; Composite task with members;
          Non-scheduled run on other host; Around edges of last
          days in Monthly with holiday policy.
          Version 2.10 July 2002
          Enhancement:
          1. SuperScheduler 1.3: Add Future View to check future schedule in
          both text and Gantt-chart mode.
          2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
          activities.
          3. SuperEnvironment 1.3: uses new graphic package adding print and
          preference facilities.
          4. SuperPeekPoke 1.6: uses new graphic package adding print and
          preference facilities.
          5. SuperStress 1.21: uses new graphic package.
          Bug fix:
          1. SuperStress 1.21: fixed graphic related bugs.
          Version 2.01 June 2002
          Enhancement:
          1. Add options for Look & Feel.
          2. Preference is persistent now.
          Bug fix:
          1. Installation for WebLogic 7.0: extEnv may not be installed on the
          right place, so SuperLibrar on the server side was not loaded and
          causes other problems.
          Version 2.00 June 2002
          Enhancement:
          1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
          when any Doer causes things to change.
          2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
          3. SuperReport 1.2: Support default HTML browser for reading HTML document.
          4. Support WebLogic 7.0.
          5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
          6. SuperEnvironment 1.21: New SuperEnvironment tour.
          Bug fix:
          1. WebSphere Envoy did not always list all JNDI names.
          Version 1.90 May 2002
          Enhancement:
          1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
          2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
          effective period. Add Patrol job type as SuperPatrol.
          3. Add support for both JOnAS and jBoss.
          4. Add more elements on Report criteria.
          Change:
          1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
          and descend.
          2. New log database.
          Bug fix:
          1. Alert email should be sent once in the interval, regarding number of servers
          in the clustering.
          2. Minor bug fixes to make errors handled better on SuperLogging.
          3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
          them.
          4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
          Version 1.80 March 2002
          Enhancement:
          1. Add new component: SuperScheduler
          Bug fix:
          1. SuperLogging: Verbose should ignore class registration.
          2. SuperLogging-tracing: an exception was thrown if the java class without package
          name.
          Version 1.70 January 2002
          Enhancement:
          1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
          weblogic 6.1, need download an application).
          2. Add alias names for log threshold as new Java suggests.
          3. New component: SuperReport.
          Change:
          1. SuperLogging: Log database parameters are specified in a properties file, instead
          of EJB's deployment descriptor. It is more convenient and it avoids some potential
          problems. No change for development, easier for administration.
          Bug fix:
          1. Add Source Path Panel now accepts both directory and jar file.
          2. Bug in SuperEnvironment example (for version 1.60 only).
          Version 1.60 December 2001
          Enhancement:
          1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
          2. Add timeout parameter to logging access.
          3. New installation program with A). Easy install. B). Remote command line install.
          4. Support EJB 2.0 for Weblogic 6.1.
          5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
          was supported since version 1.5).
          Change:
          1. Poke: argument list is set at define time, not invoke time.
          2. Default log database change to server mode from web server mode, booting performance
          to 10-20 times.
          Bug fix:
          1. If the returned object is null, Peek did not handle it correctly.
          2. If the value was too big, TimeSeries chart did not handle it correctly. Now
          it can handle up to 1.0E300.
          3. Help message was difficult to access in installation program.
          4. Source code panel now both highlights and marks the line in question (before
          it was only highlight using JDK 1.2, not JDK 1.3).
          5. Delete an item on PeekPoke and add a new one generated an error.
          Version 1.50 August, 2001
          Enhancement:
          1. Source code level tracing supports EJB, JSP, java helper and other
          programs which are written in native languages (as long as you
          write correct log messages in your application).
          2. Redress supports JSP now.
          3. New installation with full help document: hope it will be easier.
          4. Support WebSphere 4.0
          Version 1.40 June, 2001
          Enhancement:
          1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
          and PieView for GlobalProperties.
          GlobalProperties is an open source program from Acelet.
          2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
          Changes:
          1. The structure of log database changed. You need delete old installation and
          install everything new.
          2. The format of time stamp of SuperLogging changed. It is not locale dependent:
          better for report utilities.
          3. Time stamp of SuperLogging added machine name: better for clustering environment.
          Bug fix:
          1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
          Style Panel may not show up.
          Version 1.30 May, 2001
          Enhancement:
          1. Add ConnectionPlugin support.
          2. Add support for Borland AppServer.
          Version 1.20 April, 2001
          Enhancement:
          1. Redress with option to save a backup file
          2. More data validation on Dump Panel.
          3. Add uninstall for Super itself.
          4. Add Log Database Panel for changing the log database parameters.
          5. Register Class: you can type in name or browse on file system.
          6. New tour with new examples.
          Bug fix:
          1. Redress: save file may fail.
          2. Install Bean: some may fail due to missing manifest file. Now, it is treated
          as foreign beans.
          3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
          on the original file, do not need copy to a temporary directory anymore.
          4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
          Now it pick up all availble ones and give warning messages.
          5. Stress: Launch>Save>Cancel generated a null pointer exception.
          Changes:
          1. installLogDatabase has been changed from .zip file to .jar file.
          2. SuperLogging: If the log database is broken, the log methods will not try to
          access the log database. It is consistent with the document now.
          3. SuperLogging will not read system properties now. You can put log database
          parameters in SuperLoggingEJB's deployment descriptor.
          Version 1.10 Feb., 2001
          Enhancement:
          1. Re-written PeekPoke with Save/Restore functions.
          2. New SuperComponent: SuperStress for stress test.
          3. Set a mark at the highlighted line on<font size=+0> the Source Code
          Panel (as a work-a-round for JDK 1.3).</font>
          4. Add support for WebLogic 6.0
          Bug fix:
          1. Uninstall bean does physically delete the jar file now.
          2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
          Version 1.00 Oct., 2000
          Enhancement:
          1. Support Universal server (virtual all EJB servers).
          2. Add Lost and Found for JNDI names, in case you need it.
          3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
          for Envoys which do not support JNDI list).
          Version 0.90: Sept, 2000
          Enhancement:
          1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
          and alike) as input values.
          2. Reworked help documents.
          Bug fix:
          1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
          further time-out.
          2. MDI related bugs under JDK 1.3.
          Version 0.80: Aug, 2000
          Enhancement:
          1. With full-featured SuperLogging.
          Version 0.72: July, 2000
          Bug fix:
          1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
          Version 0.71: July, 2000
          Enhancement:
          1. Re-worked peek algorithm, doing better for concurent use.
          2. Add cacellable Wait dialog, showing Super is busy.
          3. Add Stop button on Peek Panel.
          4. Add undeploy example button.
          Bug fix:
          1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
          1.2 and 1.3
          Version 0.70: July, 2000
          Enhancement:
          1. PeekPoke EJBs without programming.
          Bug fix:
          1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
          Changes:
          1. All changes are backward compatible, but you may need to recompile monitor
          windows defined by you.
          Version 0.61: June, 2000
          Bug fix:
          1. First time if you choose BUFFER as logging device, message will not show.
          2. Fixed LoggingPanel related bugs.
          Version 0.60: May, 2000
          Enhancement:
          1. Add DATABASE as a logging device for persistent logging message.
          2. Made alertInterval configurable.
          3. Made pace for tracing configurable.
          Bug fix:
          1. Fixed many bugs.
          Version 0.51, 0.52 and 0.53: April, 2000
          Enhancement:
          1. Add support to Weblogic 5.1 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Context sensitive help is available for most of windows: press F1.
          2. Fix installation related problems.
          Version 0.50: April, 2000
          Enhancement:
          1. Use JavaHelp for help system.
          2. Add shutdown functionality for J2EE.
          3. Add support to Weblogic 4.5 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Better exception handling for null Application.
          Version 0.40: March, 2000
          Enhancement:
          1.New installation program, solves installation related problems.
          2. Installation deploys AceletSuperApp application.
          3. Add deploy/undeploy facilities.
          4. Add EJB and application lists.
          Change:
          1.SimpleMonitorInterface: now more simple.
          Version 0.30: January, 2000
          Enhancement:
          1. Add realm support to J2EE
          2. Come with installation program: you just install what you want
          the first time you run Super.
          Version 0.20: January, 2000
          Enhancement:
          Add support to J2EE Sun-RI.
          Change:
          1. Replace logging device "file" with "buffer" to be
          compliant to EJB 1.1. Your code do not need to change.
          Version 0.10: December, 1999
          Enhancement:
          1. provide SimpleMonitorInterface, so GUI experience is
          not necessary for developing most monitoring applications.
          2. Sortable table for table based windows by mouse
          click (left or right).
          Version 0.01 November., 1999:
          1. Bug fix: An exception thrown when log file is large.
          2. Enhancement: Add tour section in Help information.
          Version 0.00: October, 1999
          Thanks.

Help! Using "Create" action in insert jsp page vs in submission page.

This is regarding creating a new record using data TAGS:
I'm in a dilemma as to whether I should use the data source tag <jbo:Row id="myrow" datasource="iss_vo1" action="Create">
in my first jsp page ( which accepts input from a user) or in the 2nd jsp page (which does the actual commit).
If I actually create the view record n the first page itself then I get into all kinds of problems if the user decides against saving the record and backs out.[because there is a null hanging record out there]
But if I don't use it, then I am unable to use my LOVs in the html form.
Can anyone help me resolve this issue?
Currently I have used the data source tag
<jbo:Row id="myrow" datasource="iss_vo1" action="Create">
in my first JSP page.
Below is my complete source code for both the JSP pages:
Source Code for iss_add.jsp:
======================
Please note that in this JSP , it creates a new record and then the user has to click on the "SAVE" button (which calls another jsp "iss_add_post.jsp") to save the changes. But what if the user does not click on the save BUTTON and instead click on the "back" tab. This is where all the problem occurs. How do I get rid of this problem?
If I try to just use an HTML form without creating a record in this page then how will I use the LOVs?
<%@ page contentType="text/html;charset=WINDOWS-1252"%>
<HTML>
<base target="contentsframe">
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=WINDOWS-1252">
<META NAME="GENERATOR" CONTENT="Oracle JDeveloper">
<TITLE>
</TITLE>
</HEAD>
<BODY>
<%@ taglib uri="/webapp/DataTags.tld" prefix="jbo" %>
<jbo:ApplicationModule id="NewBC4J.NewBC4JModule" configname="NewBC4J.NewBC4JModule.NewBC4JModuleLocal" />
<jbo:DataSource id="pri_vo" appid="NewBC4J.NewBC4JModule" viewobject="PrioritiesView" />
<jbo:DataSource id="app_vo" appid="NewBC4J.NewBC4JModule" viewobject="ApplicationsView" />
<jbo:DataSource id="per_vo" appid="NewBC4J.NewBC4JModule" viewobject="PersonView" >
<jbo:DataSource id="iss_vo1" appid="NewBC4J.NewBC4JModule" viewobject="IssuesView5" /></jbo:DataSource>
<jbo:Row id="myrow" datasource="iss_vo1" action="Create">
</jbo:Row>
<table width="100%" bgcolor="skyblue" border="0" align="center">
<tr>
<td>
<table width="100%" bgcolor="tan" border="0" align="center" cellpadding="3" cellspacing="0">
<form NAME="iForm" action="iss_add_post.jsp">
<tr>
<th colspan="2">
"Add New Issues"
</th>
</tr>
<jsp:include page="Message.jsp" flush="true">
<jsp:param name="colspan" value="2"/>
</jsp:include>
<tr>
<td align="Right"><b><font color="red">Priority:</font></b></td>
<td> <jbo:InputSelect datasource="iss_vo1" dataitem="PriCd"
displaydatasource="pri_vo" displaydataitem="Descr" displayvaluedataitem="Cd" />
</td>
</tr>
<tr>
<td align="right"><b><font color="red"> Description:</font></b></td>
<td> <jbo:InputTextArea datasource="iss_vo1" dataitem="IssDesc" rows="3" cols="50" />
</td>
</tr>
<tr>
<td align="right"><b><font color="red"> Application:</font></b></td>
<td> <jbo:InputSelect datasource="iss_vo1" dataitem="AppCode"
displaydatasource="app_vo" displaydataitem="Name" displayvaluedataitem="Code" />
</td>
</tr>
<tr>
<td align="right"><b><font color="red"> Assigned To: </font></b></td>
<td> <jbo:InputSelect datasource="iss_vo1" dataitem="AssignedToPerId"
displaydatasource="per_vo" displaydataitem="FirstName" displayvaluedataitem="PerId" />
</td>
</tr>
<tr>
<td align="right"><b><font color="red"> Raised By: </font></b></td>
<td> <jbo:InputSelect dataso urce="iss_vo1" dataitem="RaisedByPerId"
displaydatasource="per_vo" displaydataitem="FirstName" displayvaluedataitem="PerId" />
</td>
</tr>
<tr>
<td align="Right"><b><font color="red"> Resolution: </font></b></td>
<td> <jbo:InputTextArea datasource="iss_vo1" dataitem="Resolution" cols="50" rows="3" />
</td>
</tr>
</table>

<table width="100%" bgcolor="skyblue" align="center" cellpadding="10" cellspacing="0" >
<tr>
<input name="RowKeyValue" type="hidden" value="<jbo:ShowValue datasource="iss_vo1" dataitem="RowKey"/>" />
<td>
<input type = "submit" name="submit" value="Save">
</td>
</form>
</tr>
</table>
</td>
</tr>
</table>
</BODY>
</HTML>
<jbo:ReleasePageResources releasemode="Stateful" />
Source Code for iss_add_post.jsp:
============================
This is where the actual commit occurs. But user may decide not to come here at all by not clicking the save button. What happens to the record created ? How Can I rollback that information?
<%@ page language="java" contentType="text/html;charset=WINDOWS-1252" %>
<html xmlns:jbo="foo">
<body>
<center>
<br>
<%@ taglib uri="/webapp/DataTags.tld" prefix="jbo" %>
<br>
<jbo:ApplicationModule id="NewBC4J.NewBC4JModule" configname="NewBC4J.NewBC4JModule.NewBC4JModuleLocal" username="issue" password="issue"/>
<br>
<jbo:DataSource id="iss_vo1" appid="NewBC4J.NewBC4JModule" viewobject="IssuesView5"/>
<jbo:Row id="row3" datasource="iss_vo1" action="Current" >
<jbo:SetAttribute dataitem="*" />
</jbo:Row>
<%
try
%>
<jbo:Commit appid="NewBC4J.NewBC4JModule"/>
<p><font face="Arial, Helvetica, sans-serif"><b><font color="006699">Issue Record Inserted Successfully! Issue# Assigned: <jbo:ShowValue datasource="iss_vo1" dataitem="Id" /></b></font></font> </p>
<%
catch(Exception exc)
out.println("<pre>");
exc.printStackTrace(new java.io.PrintWriter(out));
out.println("</pre>");
%>
<br>
<br>
<form action="iss_ListIssues.jsp" method="post"><input type="submit" value="Click to Continue"></form>
</center>
</body>
<jbo:ReleasePageResources releasemode="Stateful"/>
</html>
null

[email protected]
I can't actually see any LOV's on your first page so I am not completely sure that I understand your situation. However if you are talking about using the InputSelectLOV datatag, there is no reason why you cannot use that within a html form, without having to create a record in the RowSet.
The Insert page is by default created without any datasources - just a standard HTML form. The form is submitted and the InsertSubmit page reads the values from the request object, matches the parameter names with your VO attribute names and does your create.
Your LOV data will be coming from another table so doing a Row tag Create on your Insert page won't make any difference to it. Have I misunderstood something here? I have used LOV's on my Insert pages and I definitely have not created a row in the Rowset anywhere but the Submit pages.
There is a problem on both Edit and Insert pages whereby if there are no rows in the table for which you have a datasource defined you can get problems, but it doesn't sound as though that is your problem. Maybe I need some more information from you?
Simon

Problem Creating Partner Link for Adapter Integrating with Tuxedo using JCA

Hi All,
This is the first time that I am working on integration tools. I will explain in brief the problem.
There will be a legacy system (Tuxedo) running which connect to legacy database for requests. I am able to connect to that legacy system using Attunity Studio for getting the response back. Which is working fine.
Now I want that to integrate with BPEL PM 10.1.2 using JCA. For this I followed this URL (http://www.oracle.com/technology/tech/java/oc4j/904/how_to/oc4j-jca-tux/onjava-jca.html). What happens here is, a simple servlet invokes a Session Bean that interacts the Attunity Server using the JCA. For that I am using oc4j container of BPEL PM 10.1.2. I could able to work it fine.
For working with BPEL, I have created synchronous process, when try to create Partner link using Adapter service from WSIL browser, it is not coming in.
Am I missed any important configuration at BPEL PM end.
For doing this a followed the "tutorial 2" @ http://www.oracle.com/technology/products/integration/adapters/dev_support.html
In exact way, above provided tutorial 2 PDF, I failed at step "Configuring a BPEL Service to invoke the above Adapter Service" on page 11.
Your help is highly appreciated
Thanks
Venkata

Something to note. I tried adding the same BPEL services as partner links to a new application and new project on two other developer's workstations, and the creation of the partner links were successful.

How to use EJB in JSP...urgent!!!

hello,
i am novice programmer in EJB.
i am using weblogic 6.1 ...
my problem is how to use EJB in jsp page.
my code is as follow..but its not displaying any result.
<%@ page import="javax.naming.InitialContext,
javax.naming.Context,
java.util.Properties,
firstEJB.First,
firstEJB.FirstHome"%>
<%
     long t1 = System.currentTimeMillis();
     System.out.println(t1);
     Properties props = new Properties();
     p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.TengahInitialContextFactory");
     props.put(Context.PROVIDER_URL, "localhost:7001");
     Context ctx = new InitialContext(props);
     FirstHome home = (FirstHome)ctx.lookup("FirstEJB");
     First bean = home.create();
     String time = bean.getTime();
     bean.remove();
     ctx.close();
     long t2 = System.currentTimeMillis();
%>
<html>
     <head>
          <style>p { font-family:Verdana;font-size:12px; }</style>
     </head>
     <body>
          <p>Message received from bean = "<%= time %>".<br>Time taken :
          <%= (t2 - t1) %> ms.</p>
     </body>
</html>
please tell me the solution.

Hi, I don't know if it may be the cuase of your problems, but you should narrow the Object obtained doing the lookup, like this:
FirstHome home = (FirstHome) PortableRemoteObject.narrow(ctx.lookup("FirstEJB"), FirstHome.class);

Updating EJBs from JSPs

i'm looking for a way to udpdate several entity beans via a stateful session controller.
I can create references to the ejb controller in the JSP without a problem, but i need to know how to accept data entered into a form, store it temporarly and then call a ejb controller method using the form data as the arguments.
i have seen the use of javabeans in this type of situation but i have limited time and i'm trying to avoid having to create event logic to signify that the javabeans' properties have been altered.
ideally i would like to use the data entered into the form as arguments in a direct call to the ejb controller method.
any advice would be appreciated!!!
Thanks,
Student with a deadline!

Hi,
You can get the instance of any bean inside the jsp as long as you have the correct url of the application server and ejb jndi name. Once you created the EJb instance, you can pass those form data, which you have to get using getParameter() or from httpsession and call the ejb as if you are calling EJB from normal java program.
Hope that helps.
Best Luck!
Senthil Babu
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/

Unable to create javax.ejb.EJBObject

I go to the http://host:port/caf ->User Interface Configuration -> Configuration Browser ->Object Editor -> New Configuration->and push button select service, or administrative tools ->authorization tool. On this functionalities i get the same error
The initial exception that caused the request to fail, was:
com.sap.caf.rt.exception.CAFBaseRuntimeException: Service manager initialization failed Illegal argument exception: Unable to create javax.ejb.EJBObject.
All services in Visual Admin i have started. Who can help?

can anybody help to solve? rwrd pts

Pls. help me out..Accessing ejb through jsp

hi all,
I am running my ejb on the j2sdkee.1.2.1 and jdk1.3 on Windows 2000. I am facing a problem while accessing the ejb from the jsp page. Its running fine when accessing through a client application. The following is the error when I try to access it using:
http://localhost:8000/first/FirstEJB.jsp
Error: 500
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile class for JSP
     at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:287)
     at org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:137)
     at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:148)
     at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:247)
     at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:352)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
     at org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:626)
     at org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java:534)
     at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:378)
     at org.apache.tomcat.core.Context.handleRequest(Context.java:644)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:440)
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:144)
     at org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:310)
     at java.lang.Thread.run(Thread.java:484)
Root cause:
java.lang.NullPointerException
     at java.io.File.(File.java:181)
     at org.apache.jasper.compiler.JspCompiler.computeClassFileData(JspCompiler.java:285)
     at org.apache.jasper.compiler.JspCompiler.getClassName(JspCompiler.java:103)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:105)
     at org.apache.jasper.runtime.JspLoader$2.run(JspLoader.java:273)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:270)
     at org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:137)
     at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:148)
     at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:247)
     at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:352)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
     at org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:626)
     at org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java:534)
     at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:378)
     at org.apache.tomcat.core.Context.handleRequest(Context.java:644)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:440)
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:144)
     at org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:310)
     at java.lang.Thread.run(Thread.java:484)
The name of the jsp file is FirstEJB.jsp
The name of the ear file is FirstEJB - Stateless Session Bean
The name of the WAR File is FirstWAR
I have created a Web Component named first
Can anyone tell me how to access the ejb using jsp?
Thanks,
ajit

Hello all,
Sorry for the trouble. I got the mistake..I had not given the context in the deploytool..
Thanks,
ajit

Propagation of ctx between EJB and JSP

Hello,
Does anybody know how to propagate the Security
Context between EJB and JSP so that when I login in my JSP page the user will be after recognized in my EJB system ?
Thanks
Francesco

try this...as a test..
take a simple Contact ejb (as simple as you can make it, just a name and email address). In the ejb-jar.xml set up a role, for example, user, and restrict the access to only this role for all methods.
try to access the ejb from a jsp, and you should get the login form identified in your web.xml file.
make sure that the ejb is noted in the web.xml file, also.
this should work...
no try this...identify a role in your web.xml file, (user, for example) and restrict the access to the a particular jsp which is not calling the ejb. IF you navigate to this jsp, you should get the login prompt...
this should work....
now the tough part
in your application.xml create a role with the same name, user. By doing this, you have created a global role, and connect the two together.
Now point your browser to the restricted jsp with no calls to the ejb...you should get the login, so login in.
now navigate to your jsp which is unrestricted, but calls the restricted ejb...
there should now be no login prompt.
This should work.

TagLib created by EJB to JSP Integration Tool

Similar Messages

Maybe you are looking for