J2EE, JSTL and JSF questions

I am trying to learn J2EE/JSTL/JSF and have quite a few general questions. Any help on any of these is appreciated.
1) Is there a way, just by using J2EE/Java to "manipulate" an XML file. Not just parse and read it's data but actually add nodes to the file?
2) I've been reading quite a bit on JSTL and JSF recently. Is JSF supposed to be an alternative to Struts and JSTL an alternative to scriptlet coding?
3) I am also working on creating a message board but throwing around a couple of ways to implement it. Either (a) using a database to store posts and a JSP interface or (b) using an XML document to store postings. Which of these two seem best or is there a better option?
4) Is there an easy way to call Php from a Java program? I need to invoke a php program when a user clicks on a link on a JSP page I have.

1) The SDK provides JAXP (Java API for XML Processing) in javax.xml package.
2) I wouldn't call it 'alternative'.
3) Your choice. I'd to use a RDBMS. Less overhead, better suited, (much) more functions and better performance.
4) If that program is available on the web, then just invoke a HTTP request. If not, I'd rather to rewrite it to Java.

Similar Messages

Difference between JSTL and JSF

Hi
I am little bit confuse between JSTL and JSF. can one tell me what is difference between JSTL and JSF ?
Thanks & regards,
Ben

from suns site
The JavaServer Pages Standard Tag Library (JSTL) encapsulates as simple tags the core functionality common to many Web applications. JSTL has support for common, structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization tags, and SQL tags.
http://java.sun.com/javaee/javaserverfaces/overview.html

Jstl and jsf problem

i'm programming with jsf and have to use jstl tag
i cant access "var" in jsf tags
how can i use # with forEach items attribute ?
or how can i use $ with jsf tags ?
<c:forEach items"${x}" var="x">
<h:outputText value="${x.documentNo}" />
</c:forEach>

soso_xuc wrote:
i'm programming with jsf and have to use jstl tag
i cant access "var" in jsf tags
how can i use # with forEach items attribute ?
or how can i use $ with jsf tags ?
<c:forEach items"${x}" var="x">
<h:outputText value="${x.documentNo}" />
</c:forEach>
If you're using at least JSF 1.2 with at least JSTL 1.2, you can just use unified EL (the "JSF EL") in c:forEach.
<c:forEach items="#{x}" var="x"><h:outputText value="#{x.p}"/></c:forEach>That said, using c:forEach in JSF is not recommended (as almost every JSTL tag/taglibs, only the Functions taglib is useful). Rather go for an JSF UIData component which does not output anything, such as Tomahawk t:dataList and RichFaces' a4j:repeat. If you're using Facelets instead of JSP, you could also use ui:repeat.

Java Script and JSF question

Hello,
I have a JSF component like this that has a pageSize attribute. It shows a grid with 5 elements.
<x:gridView id="#{tab}GridView" pageSize="5">
</f:gridView>Then I have a drop down with 5 menu items where the user can select how many elements they want to see visible on the grid. My question is, how do i use Java Script to to change the pageSize attribute above with what the user selected in the menu below? I have been looking at java script code and online docs for an hour and cant come up with anything that seems to work. Any help will be appriciated. Thank you!!!
<x:selectOneMenu id="myMenu" onclick="">
<f:selectItem id="perPage1" itemValue="1" itemLabel="1" />
<f:selectItem id="perPage2" itemValue="2" itemLabel="2" />
<f:selectItem id="perPage3" itemValue="3" itemLabel="3" />
<f:selectItem id="perPage4" itemValue="4" itemLabel="4" />
<f:selectItem id="perPage5" itemValue="5" itemLabel="5" />
</x:selectOneMenu>

[...]how it was never designed to be used for
such large applications[...]All I can say is that if this is true, then it doesn't show. Yes, I know it (oak) was originally designed for embedded systems, but Java and Oak aren't identical.
My assembly teacher
always makes fun of Java, saying java gives you far
less control, it prevents you from making mistakes.
No control over unsigned/ signed values, pointers
etc. Yes. But broadly speaking that's the point. Java sacrifices control over such things. The return, however, is that programmers are able to be more productive because of the great swathes of problems that can no longer arise.
The mistake is in assuming that Java is the best tool for everything. It isn't, and in fact no language us. As it turns out, Java is just great for building enterprise systems. It has a few other strengths, some of which (applets for example) have been more important in its original uptake but are now relatively minor features.
You don't write an enterprise website in Intel assembly, and you don't write device drivers in Java.
Not saying its not good but its good for
smaller applications like cell phones and
mini-computers.I think you mean something different by mini-computers to what I mean...
Its portability is actually the main point in its favour for use in cell phones. If it weren't for that, I think C or C++ would probably have sole ownership of that space.
Now i'm not saying any thing against it just
confused on why a class like data-structures at my
University [...] would be taught using java when C would
probably be a lot better for Very Large ADTS.You and Joel Spolsky:
http://www.joelonsoftware.com/articles/ThePerilsofJavaSchools.html
I disagree, because I don't think it much matters what language you learn - experience trumps any particular initial language choice. If you're still using Java in 15 years I'll be fairly surprised.

JSTL IN JSF PAGE

my jspx file .....iam using JSTL package for exceuting sql query in jsf page....
but it could not run here i mentioned my code ..whats is mistakes in my code
<sql:setDataSource
driver="sun.jdbc.odbc.JdbcOdbcDriver"
url="jdbc:odbc:dsn4"
user="xyz"
password="zyz"/>
<sql:query var="employees">
SELECT * FROM ggggg
</sql:query>
<c:forEach var="row" items="#{employees.rows}">
<af:outputText value="#{row.Currcode}" />
</c:forEach>
i already imported the jstl package in name space ,
when i run this page in jdeveloerits showing error is
Error: Expression Language not supported in compile time attribute items

Hi,
it is not recommended to use JSTL and JSF components in combination within JSF 1.1. The reason for this is a different lifecycle handling that is not integrated. You may want to Google for an article written by Hans Bergsten about this race condition.
Instead , using JSF, you use a list model in a managed bean and - instead of the JSTL "forEach" you use af:forEach
In JSF 1.2 this limitation is removed. JSF 1.2 is in JDeveloper 11 (still I wouldn't recommend using JSTL to query the data of a JSF page because it doesn't really make sense doing so)
Frank

Tomcat 6.0.9 and jsf 1.2 and jstl 1.2 using *.tag file error

I using :tomcat 6.0.9 and jsf 1.2 and jstl 1.2
My web.xml is at version 2.5 and I am using a custom tag (with the .tag extension). I am trying to use the http://java.sun.com/jsf/html library and values from my attribute. I'm new to this so I figure I must just me missing something.
I am run http://192.168.1.1/test.jsf laster,view:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
Stacktrace:
 org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85)
 org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
 org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
 org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
 org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:212)
 org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:576)
 org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:50)
 org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:627)
 org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
 org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
 org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
 org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:631)
 org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
 org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
 org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
 org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
 org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
 org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
 org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:645)
 org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:190)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
 org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:414)
 com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:455)
 com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:139)
 com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
 com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266)
 com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159)
 javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.9 logs.
if go to /WEB-INF/tags/test.tag ,delete line: <h:outputText id="test" value="hello!" />
run http://192.168.1.1/test.jsf is OK!(no error),So I guess error for "<h:outputText id="test" value="hello!" />" line ,why in test.tag file do can't use the "http://java.sun.com/jsf/html " library,please help me.......
Here is file WEB-INF/web.xml content:
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd"
version="2.5">
<display-name>Welcome to Tomcat</display-name>
<description>
Welcome to Tomcat
</description>

<servlet>
 <servlet-name>Faces Servlet</servlet-name>
 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
 <load-on-startup> 1 </load-on-startup>
</servlet>

<servlet-mapping>
 <servlet-name>Faces Servlet</servlet-name>
 <url-pattern>*.jsf</url-pattern>
</servlet-mapping>
</web-app>
Here is file /test.jsp code:
<%@ page contentType="text/html;charset=UTF-8" %>
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<f:view>
<html>
<head>
<title>test</title>
</head>
<body>

<h:outputText id="myinfo" value="test success" />
<tags:test/>

</body>
</html>
</f:view>
Here is file /WEB-INF/tags/test.tag code:
<%@tag pageEncoding="UTF-8"%>
<%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<h:outputText id="test" value="hello!" />
Thanks for any help.

Don't know if it's important, but there is no schema avaiable at: http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd
I found the right one at: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
/perty
Message was edited by:
perajonsson

Question regarding JSTL and function calls

Hello
I'm quite new to JSTL and I'm having a problem accessing a function when I want to pass argument to that function.
Im using MVC where my M (model.jsp) can be accest from my V (view.jsp) by doing ${model.(parameter/some function) }
in my M I have a couple of getMethods() (example: getThisInfo() ) and som control methods like "isSomethingValid(arg1)"
my question is lets say I want to access my "isSomethingValid(arg1)" and arg1 should be the value of "getThisInfo()" I thought I could do like
${model.somethingValid($model.thisInfo)} but it isnt working I get:
"Unable to parse EL function ${model.somethingValid(model.thisInfo)}"
I know that the syntax above is a mix of scriptlet and JSTL but I dont know how to or if its even possible to achieve this?
Thanks for helping me!
Best Regards/DS

By default, EL can only access getters and setters on objects.
It can not execute general methods on an object.
You can define function libraries that call static methods
You have to write the method as static, and then declare it in a tld.
public boolean checkValid(Model m, Info i){ ...}
and then you could invoke it something like
<%@ taglib uri="myfunctionstaglib" prefix="myfunctions" %>
${myfunctions:checkValid(model, model.thisInfo)}

Petstore and JSF

I look into petstore and JSF recently, and have two questions about those.
1. What application framework does the petstore application use, Sun's own framework or similiar to Struts, or something else?
2. JSF has been a part of the J2EE and become a standard, will the petstore implementation reflect the development soon?
Can someone give me some ideas please?
Thank you in advance.

I look into petstore and JSF recently, and have two
questions about those.
1. What application framework does the petstore
application use, Sun's own framework or similiar to
Struts, or something else?Something else, and again, it's just an example! ;-)
2. JSF has been a part of the J2EE and become a
standard, will the petstore implementation reflect the
development soon?JSF is not yet part of J2EE. It may be part of J2EE 5.0 (the one after 1.4). Note that JSF is part of the J2EE 1.4 SDK (Sun Java System App Server 8) though.
Note also that one of the great differences between Struts and JSF is that the later was build to be tools-friendly from day one. So if you use Java Studio Creator (http://www.sun.com/jscreator) for instance (it relies heavily on JSF), you don't need to know the goory details of the MVC implementation in JSF.
-Alexis
>
Can someone give me some ideas please?
Thank you in advance.

What's the difference between jsp and jsf?

who can tell me what's the difference between jsp and jsf?
I'm puzzled when I found some of the technology in jsp is so similar to the ones in jsp( javaserver page)

Hi,
Find the difference between JSP and JSF
1. A developer has more control with JSP, but (should) get easier development with JSF
2. Event handling is done differently in JSP (HTTP) and JSF (Java)
3. The UI is designed differently (or should be at least) with JSP (markup) and JSF (components).
4. The end product should also be defined differently - JSP page versus a JSF application.
Is this the only thing that is need to make a decision for either or? Probably not. There are other pieces that need to be taken in account when deciding which technology to use - tools support, enough components, type of application etc.... At this point there are not enough JSF components (although there are some interesting projects underway - Ajaxfaces, Myfaces, ADF Faces, and WebChart 3d) and enterprise tools support is still limited to a few tools vendor. Looking at our ADF Faces components they are currently available as early access (not production) and demands for these components are stacking up, literally, outside my office doorstep. Although I would love to make them production - now! - it is not a viable solution since we are still checking features and fixing critical bugs.
All this combined - not enough enterprise level components in production, lacking tools support etc... - leave customers in a vacuum where the decision is either to continue with JSP, since it is mature and has a wide developer base, or move forward with JSF not sure if the support, or the developers will be there. This is particularly sensitive to customers that need to get started now and be production by summer.
If you are in this vacuum here are some key points promoting JSF:
1. Fundamental unit is the Component
2. Built in event and state management
3. Component sets can be provided by any vendor
4. Closer to ASP.Net or Swing development
5. Choice of UI technology
6. Scale up (rich clients)
7. Scale down (mobile devices)
8. Built into J2EE containers in J2EE 5.0 (tentative)

Can Struts and JSF coexist?

I have a Struts based application and now I want to build an additional module on top of that using pure JSF. My question is, can Struts and JSF co-exist in the same application? If yes, what are the cons of that approach? What are the places I need to tweak in the configuration files so that they work together?
thanks,

Hi,
Yes they can coexist. Actually that's the approach recommended by Craig McClanahan. I have developed a full enterprise application (80% completed) which uses JSF in front and Struts in the back using Struts-Faces integration library (developed by Apache).
So far I haven't faced any major issues with this approach. However, I haven't try using Struts validator on JSF objects.
Read the article below on how to integrate JSF w/ Struts.
http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk8.html

Managing blob images using ADF and JSF or struts

Hello everyone. I am an ADF newbe and I am developing a web app. that has to manage (display, insert,update and delete) blob images from/to an oracle DB. I've seen the "howto" on image managing using intermedia and struts, but, for this new app I wanted to use JSF (something that is not mandatory) and, what is important is that the DB has already stored the images in blob format.
Can anybody point me in the right direction please??? Is there any howtos on this subject???
Thanks in advance.

jfin wrote:
but so far I have to say that I like the fact that I'll have to do very little
System.out.println(<..../>....<>....</>).Assuming that you rather mean out.println() where out is the ServletOutputStream reference returned by HttpServletResponse#getOutputStream(), I can only agree with you. That's certainly not the way how JSP/Servlet code is to be written. The maintainability, extendability, reusability and testability would be far below the freezing point then. You need to write presentation logic in JSP files, not in Servlets and absolutely not in scriptlets inside a JSP.
When you need to write presentation logic which may change per request, use JSTL and EL for that. Again, not scriptlets. For business and controlling logic, use Servlets. For transfer of data, use javabeans (DTO's, VO's). For data access logic, use DAO classes which are to be interacted by servlets.
JSF removes the need for creating Servlets and using JSTL/EL in JSP files. You just have JSP pages with JSF tags for presentation and javabeans for the request values and backing beans for business logic.
When would one use JSF over the other two? When Struts2? When Shale?And you ask that in a JSF forum? At least my opinion is predictable :)

ADF and JPA question

I tried the example in 'Build a Web Application with JDev 10g Using EJB, JPA and JSF and it worked.
This example is based on two tables. Now I have 6 tables. Tables 1,2 and 3 are joined to populate an ADF table form and tables 1,2,4,5 and 6 are joined to populate another ADF form.
My question is: should I use JDev to generate all 6 entity EJBs or rather create two Oracle views for each of these joins and get JDev to generate EJB for each of these views?
Also, how can I customize the annotated queries generated by JDev? I would like to have all the native SQLs to be in separate XML files. Should I use XML files generated by JDev or create a new XML file? Is there an example of how to do that?

Hello,
I read somewhere JPA supports external XML native SQL queries and apparently these queries override named queries in entity annotations. Assuming this is true, would that be the preffered way (both queries, 1-2-3 join and 1-2-4-5 join have one input parameter each so the database views would have to be parametrized in that case)? And how should I access these XML based queries from inside the code?
Also, what queries are generated by JDev JPA when 6 tables are selected? Are all combinations based on foreign keys generated or just table (entity) and its directly related tables?
Thanks,
Sale

BlazeDS and JSF

I have an existing JSF (really Oracle ADF) application that I'd like to connect to a Flex front-end rather than rewrite totally in Flex + JSPs for the back-end. BlazeDS will properly instantiate the managed beans through remote object requests, but the FacesContext references in my managed beans are null, as BlazeDS seems to have nothing to do with this context. Does anyone have experience connecting a Flex application to a JSF application properly, maybe through creating his/her own FacesContext factory?

<div class=Section1> color:#1F497D'>Hi,<o:p></o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'>It’s pretty easy to integrate blazeds into an existing application. The war is just an example of how to configure and package blazeds. BlazeDS itself is just a servlet, with a collection of jars and some configuration files. You put the required jars into your WEB-INF/lib, the configuration files into WEB-INF/flex (If I remember correctly), and then map the blazeds message broker servlet in your web.xml file. You can open up the war file and see how it’s configured there and base your configuration on that. Depending on your needs and your servlet container you may have to add a jar file to your container’s lib or classpath.<o:p></o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'>One of the benefits of blazeds is that if you’ve structured your application so that you’ve abstracted the view then you can just plop bds right in there and expose all your services through bds views. It’s very powerful that way. <o:p></o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'>If you’re still having trouble just write a response and I’ll see what I can do.<o:p></o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'>/r <o:p></o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'><o:p> </o:p> color:#1F497D'><o:p> </o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From:<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Larry Guros [mailto:[email protected]] Sent: Thursday, July 24, 2008 8:28 AM To: [email protected] Subject: Re: BlazeDS and JSF<o:p></o:p> </div> <o:p> </o:p> A new message was posted by Larry Guros in General Discussion -- BlazeDS and JSF Ditto. I am guessing the answer is no one knows. Seems Blazeds is much better suited to flex-only applications and doesn't integrate easily with other J2EE apps. <o:p></o:p> <div class=MsoNormal> <hr size=2 width=200 style='width:150.0pt' align=left> </div> View/reply at <a href="http://www.adobeforums.com/webx?13@@.59b4b834/0">BlazeDS and JSF</a> Replies by email are OK. Use the <a href="http://www.adobeforums.com/webx?280@@.59b4b834!folder=.3c061a83">unsubscribe</a> form to cancel your email subscription.<o:p></o:p> </div>

So, in the end, is mixing JSTL with JSF ok or not?

At first, when I began learning JSF, I was taught not to mix JSTL into JSF because it's very hard to know how will be behave.
Then, I learned that in order to avoid the confusion completely, it was best not to use any JSTL or even better use Facelets.
Now, I keep running into (relatively recent) articles and books claiming both that JSTL now works with JSF and that it doesn't.
I gave it a shot by trying the famous c:forEach with h:outputText
<c:forEach var="item" items="#{someBean.items}">
 <h:outputText value="#{item.name}" /></td>
</c:forEach>According to my current knowledge, this is not supposed to work, and it doesn't, but since I've seen a Sun article saying that it should (if the latest components are installed, and they are), I can't be sure if I misconfigured something or...
I've also read the following sentence (regarding the above example):
>
This is supposedly fixed in JSTL 1.2, but there is no stand-alone implementation of JSTL 1.2.
>
So, could someone with an understanding of the issue clear this up for me? I'd be very grateful.
I'm not asking anyone to find out why my code didn't work, just if it was supposed to work at all.
Also, I found this on onjava.com
For instance, <c:if> and <c:choose> may contain JSF component custom actions, but only if the id attributes are set for the nested JSF component actions.It this true? Is it obsolete?
Thanks to anyone who takes the time to share any insight.

Thanks for the response BalusC, I'm now closer to understanding the issue. The only thing still bothering me is this code (taken from Sun's webtiersample.jsp)
<c:forEach items="#{BooksBean.books}" var="book" varStatus="stat">
 <tr>
 <td>
 <h:outputText id="title" value="#{book.title}"/>
 </td>
 <td>
 <h:outputText id="author" value="#{book.author}"/>
 </td>
 </tr>
</c:forEach>Won't this cause an id clash? I mean, doesn't this mean I'll have multiple "title" and "author" ids?
This seems to confirm the statement I quoted earlier (from onjava.com):
For instance, <c:if> and <c:choose> may contain JSF component custom actions, but only if the id attributes are set for the nested JSF component actions.Mind you, I don't really plan to use JSTL in JSF, but I really wish to understand this...
Thank you very much for taking the time.

J2EE Packaging and manifest Class-Path:

Does anyone know if Weblogic 6.0 supports the redefined deployment extension mechanism
that makes use of the 'Class-Path:' entry in the manifest files?
In our project we have one single .ear file containing a couple of EJB's (.jar
files) and a Web Application (.war file).
We are using log4j as logging mechanism and we would like to keep everything in
the .ear file so that we can make hot-deploys. So we are trying not to make use
of the classpath in startWebLogic.sh. All of our EJB's and the Web Application
makes use of log4j.jar. My question is; can I do the following and make it work
in Weblogic 6.0?
1. In every EJB .jar file I add the follwing to the manifest file - "Class-Path:
log4j.jar"
2. I place the log4j.jar in the root directory of the .ear file.
By doing this I expect that the ear classloader loads the log4j.jar classes. Am
I right or do I do something wrong. At least it does not seem to work.
Using Weblogic 6.0 without service pack.
Thanks,
Steen

This does not work in WebLogic 6.0. It's supposed to be supported in 6.1
Daniel
-----Original Message-----
From: Steen Laursen [mailto:[email protected]]
Posted At: Wednesday, August 08, 2001 1:32 PM
Posted To: environment
Conversation: J2EE Packaging and manifest Class-Path:
Subject: J2EE Packaging and manifest Class-Path:
Does anyone know if Weblogic 6.0 supports the redefined
deployment extension mechanism
that makes use of the 'Class-Path:' entry in the manifest files?
In our project we have one single .ear file containing a
couple of EJB's (.jar
files) and a Web Application (.war file).
We are using log4j as logging mechanism and we would like to
keep everything in
the .ear file so that we can make hot-deploys. So we are
trying not to make use
of the classpath in startWebLogic.sh. All of our EJB's and
the Web Application
makes use of log4j.jar. My question is; can I do the
following and make it work
in Weblogic 6.0?
1. In every EJB .jar file I add the follwing to the manifest
file - "Class-Path:
log4j.jar"
2. I place the log4j.jar in the root directory of the .ear file.
By doing this I expect that the ear classloader loads the
log4j.jar classes. Am
I right or do I do something wrong. At least it does not seem
to work.
Using Weblogic 6.0 without service pack.
Thanks,
Steen

J2EE, JSTL and JSF questions

Similar Messages

Maybe you are looking for