If you are just using normal beans, then I apologize for distracting you
with the properties file. Ryan's suggestion on using the page directive
import is the only way I seen simple beans used (along with usebean.) If
you are using an earlier JSP spec, you'll have to use the BEAN: tag instead
of usebean:. I haven't had the .jar problem Ryan has, though. If you are
using EJBs and/or servlets, the below could help:
One of the last statements on the console as you startup the web server
should state that 'X EJBs deployed' if you are using EJBs. If it states
that none were deployed, then look at the message on the console just after
it attempts to deploy each EJB, which should indicate the reason
(connectionpool couldn't be created, license expiration problem, etc.) Here
is an example of how the ejb.deploy property is setup:
weblogic.ejb.deploy=\
c:/weblogic/myserver/serverclasses/user.jar ,\
c:/weblogic/myserver/serverclasses/plant.jar,\
c:/weblogic/myserver/serverclasses/backofficeuser.jar,\
c:/weblogic/myserver/serverclasses/contactinfo.jar,\
c:/weblogic/myserver/serverclasses/creditcheck.jar
-----Original Message-----
From: Shriver, Ryan [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 22, 2000 12:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Weblogic & JavaBeans
Make sure you're doing the following:
1. Import the Bean's package:
<%@ page import="com.package.whatever.myBean" %>
2. Refer to the Bean's entire package in the useBean:
<jsp:useBean id="myBean" class="com.package.whatever.myBean" />
3. Make sure the above mentioned class is in your classpath. I have known
Weblogic 4.51 to not find classes that are in .jar files in my classpath. So
if your class is in the .jar you might explode it out into a directory
that's already in your class path.
Do these things and it should work ok. You don't need to worry about the
weblogic.properties file for simple JavaBeans. However, for debugging you
might want to add the following in the JSP section of weblogic.properties:
weblogic.httpd.initArgs.*.jsp=\
keepgenerated=true
There will already be other initArgs, but adding keepgenerated=true to the
end will keep the servlet.java file that was generated when compiling the
JSP page. You can look at this servlet's source and see how it's trying to
find the class. Enjoy.
ryan
> -----Original Message-----
> From: Kaylon Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 22, 2000 1:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Weblogic & JavaBeans
>
>
> Thanks Ken,
>
> I have read most of the properties file info, there is a section on
> configuring
> the JSPServlet. I have the server configured to run JSP's,
> any JSP which
> does not
> access a Bean via the useBean tag works fine. I just can't
> get it to locate
> my beans.
> Is there any special configuration within the properties file
> for locating
> javabeans?
>
> -----Original Message-----
> From: Wasetis, Ken [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 19, 2000 6:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Weblogic & JavaBeans
>
>
> There is a section in the weblogic.properties file. One
> section for EJBs
> and one for servlets. The properties file is pretty well
> documented. It
> should be located in the \weblogic folder.
>
> -----Original Message-----
> From: Kaylon Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 19, 2000 2:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Weblogic & JavaBeans
>
>
> Does anyone know how to get the Weblogic 5.1 server
> to "find" Javabeans? I continue to get ClassNotFoundErrors
> whenever I try to load a JSP with a javabean.
> I am using a standard <jsp:useBeans id=".." class="......." /> tag.
> I have set the java classpath using the BEA Systems online
> help examples.
>
> Any insight would be helpful.
>
> Kaylon D
> [EMAIL PROTECTED]
>
> ==============================================================
> =============
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> ==============================================================
> =============
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> ==============================================================
> =============
> To unsubscribe: mailto [EMAIL PROTECTED] with body:
> "signoff JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
