Error while accessing getCSVreportdata method

Question

here is the code snippet:
ArrayList inputParameters = new ArrayList();
inputParameters.add("");
ReportInput reportInput = new ReportInput();
reportInput.setReportKey(1);
reportInput.setUserKey(userKey);
reportInput.setInputParameters(inputParameters);
tcResultSet rs;
rs =repopinf.getCSVReportData(reportInput);
And on execution i recieved the following exception:
ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException in method: public abstract Thor.API.tcResultSet com.thortech.xl.ejb.interfaces.ReportOperations.getCSVReportData(com.thortech.xl.vo.report.ReportInput) throws Thor.API.Exceptions.tcAPIException,java.rmi.RemoteException, causedBy:
java.lang.ClassCastException: java.lang.String cannot be cast to com.thortech.xl.vo.report.ReportSPParameter
Please highlight some details on the usage of the method.

Answer 1

Greetings,
Hi,
I am trying to access a bean from a JSP and have the
foll. code piece:
<%
String op="";
try {
// Contact the AccountBean container (the "AccountHome") through JNDI.
Context ctx = getInitialContext();
out.println("initial context got !!");
DemoHome home = (DemoHome) ctx.lookup("demo.DemoHome");
out.println("home got !!");Though it doesn't seem to be the problem in this case, good EJB coding practices dictate that your code should be narrowing the home reference before calling any of it's methods (i.e. create(...) )... WebLogic may allow handling of its protocol objects in their native state, but other vendors do not... your application is not portable without narrowing.
It gives an error on trying to access the method "demoSelect".
e.printStackTrace gives the output:
java.lang.RuntimeException: javax.ejb.EJBContext.getEnvironment is deprecated inThe error is not in your JSP, but in the bean... it seems your bean is attempting to acquire its "environment properties" in the pre-1.1 style, when...
EJB 1.1. EJB 1.1 compliant containers are not required to implement this
method. Use java:comp/env instead. ...instead, it should be looking them up in its JNDI namespace.
What is wrong???
pls help! Regards,
Tony "Vee Schade" Cook