Re: [JBoss-dev] Tomcat6 upgrade broke webapps in HEAD?
In that case the problem would be some old code in the Tomcat 6 integration? Should I hold off on putting commons-el back into the build? Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: Remy Maucherat > Sent: Wednesday, July 05, 2006 10:54 AM > To: Stan Silvert; 'JBoss.org development list' > Cc: 'Jacob Hookom'; Bill Burke > Subject: RE: [JBoss-dev] Tomcat6 upgrade broke webapps in HEAD? > > > I think this is because I removed commons-el.jar. JSF no longer uses > it, > > but it looks like the latest version of JspUtil now calls into it. > > No, this is false. > > > I don't think Tomcat/Jasper should be using commons-el because all that > > functionality was moved into JSP 2.1, right? Or maybe the Tomcat 6 > > integration has some old code in it? > > > > I'll re-add commons-el for now and that should fix the problem until > this > > is sorted out. > > Rémy Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat6 upgrade broke webapps in HEAD?
I think this is because I removed commons-el.jar. JSF no longer uses it, but it looks like the latest version of JspUtil now calls into it. I don't think Tomcat/Jasper should be using commons-el because all that functionality was moved into JSP 2.1, right? Or maybe the Tomcat 6 integration has some old code in it? I'll re-add commons-el for now and that should fix the problem until this is sorted out. Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED] On Behalf Of Dimitris Andreadis > Sent: Wednesday, July 05, 2006 7:16 AM > To: jboss-development@lists.sourceforge.net > Subject: [JBoss-dev] Tomcat6 upgrade broke webapps in HEAD? > > http://jira.jboss.com/jira/browse/JBAS-3368 > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why was apache-lang added to build-thirdparty.xml?
Got itI think. So right now in the repository we have: apache-myfaces/1.1.1/lib/myfaces-api.jar apache-myfaces/1.1.1/lib/myfaces-impl.jar apache-myfaces/1.1.1/lib/jstl.jar What happens when a new component wants to use jstl.jar? How would anyone easily know that jstl already exists in the repository? How does anyone know what version of jstl has been bundled with MyFaces? It would make more sense to let jstl have its own space in the repository: apache-jstl/1.0.0/lib/jstl.jar If this is done then is there currently a way to let apache-myfaces/1.1.1/component-info.xml reference version 1.0.0 from apache-jstl? If so, I'd like to take that approach. Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED] On Behalf Of Scott M Stark > Sent: Tuesday, June 27, 2006 10:26 PM > To: JBoss.org development list; [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Why was apache-lang added to build- > thirdparty.xml? > > Only the top component that needs to be integrated should be in > build-thirdparty.xml. Anything else added was due to the same confusion > you have. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Stan Silvert > > Sent: Tuesday, June 27, 2006 6:39 PM > > To: JBoss.org development list; [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] Why was apache-lang added to > > build-thirdparty.xml? > > > > OK, I guess I'm confused. When we started using the > > repository someone broke out all the jars that MyFaces needs > > and put them in build-thirdparty.xml. (All except jstl.jar?) > > So that's the pattern I followed. > > > > However, it doesn't appear that anything except MyFaces > > relies on jars such as commons-beanutils.jar and the others > > that end up in jsf-libs. > > > > Is it the rule that if more than one component relies on a > > jar then it goes in build-thirdparty.xml? If so, why were > > those others put in there and how do I know if more than one > > component relies on it? > > > > What am I missing? > > > > Also, what do I need to do to fix it all? > > > > Stan Silvert > > JBoss, a division of RedHat > > [EMAIL PROTECTED] > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > [mailto:jboss- > > > [EMAIL PROTECTED] On Behalf Of > > Scott M Stark > > > Sent: Tuesday, June 27, 2006 8:15 PM > > > To: JBoss.org development list; [EMAIL PROTECTED] > > > Subject: Re: [JBoss-dev] Why was apache-lang added to build- > > > thirdparty.xml? > > > > > > Then this should be coming in as a dependency from the myfaces > > > component, not a jbossas build-thirdparty.xml dependency. > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On > > Behalf Of > > > Stan Silvert > > > Sent: Tuesday, June 27, 2006 4:23 PM > > > To: JBoss.org development list; [EMAIL PROTECTED] > > > Subject: Re: [JBoss-dev] Why was apache-lang added to > > > build-thirdparty.xml? > > > > > > It was needed for the MyFaces upgrade. > > > > > > Stan Silvert > > > JBoss, a division of RedHat > > > [EMAIL PROTECTED] > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] > > [mailto:jboss- > > > > [EMAIL PROTECTED] On Behalf Of Scott M > > Stark > > > > Sent: Tuesday, June 27, 2006 7:06 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: [JBoss-dev] Why was apache-lang added to > > > build-thirdparty.xml? > > > > > > > > Why was apache-lang added to build-thirdparty.xml in the > > 4.0 branch? > > > > > > > > > > > > Scott Stark > > > > VP Architecture & Technology > > > > JBoss, a division of Red Hat > > > > > > > > > > > > > > > > Using Tomcat but need to do more? Need to support web services, > > > security? > > > > Get stuff done quickly with pre-integrated technology to make your > > job > > > > easier > > > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > > > Geronimo > > > > > > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&; > > dat=121642 > > > > __
Re: [JBoss-dev] Why was apache-lang added to build-thirdparty.xml?
OK, I guess I'm confused. When we started using the repository someone broke out all the jars that MyFaces needs and put them in build-thirdparty.xml. (All except jstl.jar?) So that's the pattern I followed. However, it doesn't appear that anything except MyFaces relies on jars such as commons-beanutils.jar and the others that end up in jsf-libs. Is it the rule that if more than one component relies on a jar then it goes in build-thirdparty.xml? If so, why were those others put in there and how do I know if more than one component relies on it? What am I missing? Also, what do I need to do to fix it all? Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED] On Behalf Of Scott M Stark > Sent: Tuesday, June 27, 2006 8:15 PM > To: JBoss.org development list; [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Why was apache-lang added to build- > thirdparty.xml? > > Then this should be coming in as a dependency from the myfaces > component, not a jbossas build-thirdparty.xml dependency. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stan Silvert > Sent: Tuesday, June 27, 2006 4:23 PM > To: JBoss.org development list; [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Why was apache-lang added to > build-thirdparty.xml? > > It was needed for the MyFaces upgrade. > > Stan Silvert > JBoss, a division of RedHat > [EMAIL PROTECTED] > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:jboss- > > [EMAIL PROTECTED] On Behalf Of Scott M Stark > > Sent: Tuesday, June 27, 2006 7:06 PM > > To: [EMAIL PROTECTED] > > Subject: [JBoss-dev] Why was apache-lang added to > build-thirdparty.xml? > > > > Why was apache-lang added to build-thirdparty.xml in the 4.0 branch? > > > > > > Scott Stark > > VP Architecture & Technology > > JBoss, a division of Red Hat > > > > > > > > Using Tomcat but need to do more? Need to support web services, > security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > ___ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why was apache-lang added to build-thirdparty.xml?
It was needed for the MyFaces upgrade. Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED] On Behalf Of Scott M Stark > Sent: Tuesday, June 27, 2006 7:06 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] Why was apache-lang added to build-thirdparty.xml? > > Why was apache-lang added to build-thirdparty.xml in the 4.0 branch? > > > Scott Stark > VP Architecture & Technology > JBoss, a division of Red Hat > > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JSF 1.2 integrated
There are some outstanding Tomcat bugs that affect a few JSF 1.2 features, but most JSF 1.2 apps should work with JBoss 5 now. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWithJSFCDDL for details. Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat 6 integrated
Anybody have a problem with hard-coding 1.5 in the Tomcat build.xml until we can get the other stuff out of head? Or, can we go ahead and change it for the whole build? Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: Scott M Stark > Sent: Monday, June 26, 2006 11:12 AM > To: Tim Fox; Stan Silvert > Cc: Ryan Campbell; JBoss.org development list; The Core; Bill Burke > Subject: RE: [JBoss-dev] Tomcat 6 integrated > > Jboss5 requires a java5 runtime due to javaee5 requirements so you need to > get off of head. > > -Original Message- > From: Tim Fox > Sent: Monday, June 26, 2006 8:09 AM > To: Stan Silvert > Cc: Ryan Campbell; JBoss.org development list; Scott M Stark; The Core; > Bill Burke > Subject: Re: [JBoss-dev] Tomcat 6 integrated > > 1.5 is a pain for us, since we need to build and test our (jboss > messaging) releases using 1.4 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat 6 integrated
> > So, head should only be compilable with a 1.5 jdk. > > However, some modules will still enforce source & target at 1.4, so that > we can back merge fixes to the jboss4 tree. > > Correct? > What's the latest on this? The JSF integration code under the Tomcat module needs JDK 1.5 to compile. I can change it to be 1.4-compatible if I have to. Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: Ryan Campbell > Sent: Thursday, June 22, 2006 12:16 PM > To: JBoss.org development list; Scott M Stark > Cc: The Core; Bill Burke > Subject: RE: [JBoss-dev] Tomcat 6 integrated > > So, head should only be compilable with a 1.5 jdk. > > However, some modules will still enforce source & target at 1.4, so that > we can back merge fixes to the jboss4 tree. > > Correct? > > -Original Message- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED] On Behalf Of Anil Saldhana > Sent: Thursday, June 22, 2006 11:10 AM > To: Scott M Stark > Cc: JBoss.org development list; The Core; Bill Burke > Subject: Re: [JBoss-dev] Tomcat 6 integrated > > Ruel is looking into this. The issue is that the Tomcat jars need JDK5 > for compilation and the way the current HEAD build is setup, we may have > some issues. > > Scott M Stark wrote: > > The tomcat module needs jdk5, not all of head. jboss5 will require a > > jdk5 runtime. > > > > > >> -Original Message- > >> From: Anil Saldhana > >> Sent: Thursday, June 22, 2006 8:06 AM > >> To: JBoss.org development list > >> Cc: Bill Burke; The Core > >> Subject: Re: [JBoss-dev] Tomcat 6 integrated > >> > >> Hi Scott, > >> with regard to the current TC6 integration that Bill > >> undertook in HEAD: > >>http://jira.jboss.com/jira/browse/JBAS-3330 > >> > >> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85382 > >> > >> This has placed a need for JDK5 in HEAD as TC6 needs it. > >> > >> You will need to make a decision to make HEAD requiring JDK5. > >> > >> Regards, > >> Anil > >> > > > > > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat 6 integrated
So at the end of the day, the Tomcat code in JBoss will not exactly correspond to an official Tomcat release version. Is that correct? I know we have been maintaining full Tomcat source within the JBoss AS CVS. I'm wondering about the pros and cons you experienced with Tomcat because I'm not sure if we should do it for JSF. Do you guys think it makes sense to check in all of the JSF source code or just use a particular release and only check the jars into our repository? Stan Silvert JBoss, a division of RedHat [EMAIL PROTECTED] > -Original Message- > From: Bill Burke > Sent: Wednesday, June 21, 2006 6:24 PM > To: Jboss-Dev; The Core > Subject: Tomcat 6 integrated > > Ok, I took a snapshot of Tomcat 6 SVN and integrated it with JBoss. It > had some annotation mistakes from spec (@DeclareRoles and @EJB was in > the wrong package) so I had to modify it. > > The only thing I tested was the JMX-Console and EJB3 webservices. I had > run the web testsuite before the integration and got a lot of errors so > didn't bother trying after the integration. Also, Anil said he would > fix any problems anyways. > > The repository has a snapshot of the sourcecode if you need to look back > to it. > > By end of next week (hopefully a lot sooner), I hope to have the 1st > iteration of injection into Tomcat for Java EE 5. This will require > minor changes to Tomcat and also a refactoring of EJB3 so that code can > be shared between these modules. > > Later, > > Bill > > P.S. I CC'd core as I'm not sure my emails get to jboss-dev anymore. > I'll post same on tomcat forum. > > -- > Bill Burke > JBoss Lead Architect > Redhat Inc. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Thirdparty using java.util.logging
I’ve re-subscribed. Let’s give this another try: The JSF RI uses java.util.logging instead of Log4J or commons logging. The way I’m thinking I can deal with this is: 1) If JBoss is already set to use java.util.logging, do nothing. 2) Otherwise, intercept log messages to javax.faces and com.sun.faces using a java.util.logging.Filter. 3) Convert these messages to Log4J and re-log to the appropriate Log4J Logger. 4) Return false in the filter so this won’t be logged using java.util.logging. I assume we’ve run into this before. Is there a better solution? If not, is there some common code I can steal? Also, is there any plan to upgrade log4j in JBoss 5? Right now it looks like we are on 1.2.8 and 1.2.13 is now available. Stan Silvert JBoss, Inc. [EMAIL PROTECTED] callto://stansilvert
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1602) Can't use container level taglibs
[ http://jira.jboss.com/jira/browse/JBAS-1602?page=history ]
Stan Silvert updated JBAS-1602:
---
Attachment: EmbeddedServletOptions.java
> Can't use container level taglibs
> -
>
> Key: JBAS-1602
> URL: http://jira.jboss.com/jira/browse/JBAS-1602
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Reporter: Stan Silvert
> Priority: Critical
> Attachments: EmbeddedServletOptions.java, TldLocationsCache.java
>
>
> JBoss/Tomcat needs a way to install tag libraries globally so they are
> available to all web applications. This functionality is mentioned in the
> JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
> doesn?t work in JBoss/Tomcat.
> The way this works is that the Jasper TldLocationsCache ?Scans all JARs
> accessible to the webapp's classloader and its parent classloaders for TLDs.?
> If I put my jar into Tomcat standalone?s common/lib directory then the tag
> library will be shared across all web apps. I?ve tried putting the jar in
> several ?well known? locations in JBoss/Tomcat and nothing seems to work.
> For Reference, I?ve attached the TldLocationsCache source code from Tomcat
> 5.5.8.
> Concerning TldLocationsCache, Scott Stark says:
> "This class is useless for non-URLClassLoaders and URLClassLoaders that do
> not expose their classpath via getURLs which is what we currently do because
> of an old bad behavior with annotated codebases of rmi classes. "
> Remy Maucherat offered this as a possible solution:
> Would it be possible to have the ENCLoader facade return more interesting
> things ?
>/**
> * A trival extension of URLClassLoader that uses an empty URL[] as its
> * classpath so that all work is delegated to its parent.
> */
>static class ENCLoader extends URLClassLoader
>{
> private URL[] urllist = new URL[0];
> ENCLoader(ClassLoader parent)
> {
> super(new URL[0], parent);
> }
> void addURLInternal(URL url)
> {
> URL[] result = new URL[urllist.length + 1];
> for (int i = 0; i < urllist.length; i++)
> result[i] = urllist[i];
> result[urllist.length] = url;
> urllist = result;
> }
> public URL[] getURLs()
> {
> return urllist;
> }
>}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1602) Can't use container level taglibs
[
http://jira.jboss.com/jira/browse/JBAS-1602?page=comments#action_12316474 ]
Stan Silvert commented on JBAS-1602:
The problem is with the way that Jasper is trying to locate TLD's. If you look
at EmbeddedServletOptions.java, you can see that somebody meant for the
TldLocationsCache to be pluggable. If it were we could easily write our own
and pass the class name into the JspServlet as an option.
Can we make this change to Tomcat/Jasper so that we can write our own
TldLocationsCache?
> Can't use container level taglibs
> -
>
> Key: JBAS-1602
> URL: http://jira.jboss.com/jira/browse/JBAS-1602
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Reporter: Stan Silvert
> Priority: Critical
> Attachments: TldLocationsCache.java
>
>
> JBoss/Tomcat needs a way to install tag libraries globally so they are
> available to all web applications. This functionality is mentioned in the
> JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
> doesn?t work in JBoss/Tomcat.
> The way this works is that the Jasper TldLocationsCache ?Scans all JARs
> accessible to the webapp's classloader and its parent classloaders for TLDs.?
> If I put my jar into Tomcat standalone?s common/lib directory then the tag
> library will be shared across all web apps. I?ve tried putting the jar in
> several ?well known? locations in JBoss/Tomcat and nothing seems to work.
> For Reference, I?ve attached the TldLocationsCache source code from Tomcat
> 5.5.8.
> Concerning TldLocationsCache, Scott Stark says:
> "This class is useless for non-URLClassLoaders and URLClassLoaders that do
> not expose their classpath via getURLs which is what we currently do because
> of an old bad behavior with annotated codebases of rmi classes. "
> Remy Maucherat offered this as a possible solution:
> Would it be possible to have the ENCLoader facade return more interesting
> things ?
>/**
> * A trival extension of URLClassLoader that uses an empty URL[] as its
> * classpath so that all work is delegated to its parent.
> */
>static class ENCLoader extends URLClassLoader
>{
> private URL[] urllist = new URL[0];
> ENCLoader(ClassLoader parent)
> {
> super(new URL[0], parent);
> }
> void addURLInternal(URL url)
> {
> URL[] result = new URL[urllist.length + 1];
> for (int i = 0; i < urllist.length; i++)
> result[i] = urllist[i];
> result[urllist.length] = url;
> urllist = result;
> }
> public URL[] getURLs()
> {
> return urllist;
> }
>}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1602) Can't use container level taglibs
Can't use container level taglibs
-
Key: JBAS-1602
URL: http://jira.jboss.com/jira/browse/JBAS-1602
Project: JBoss Application Server
Type: Bug
Components: Web (Tomcat) service
Reporter: Stan Silvert
Priority: Critical
JBoss/Tomcat needs a way to install tag libraries globally so they are
available to all web applications. This functionality is mentioned in the JSP
2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
doesnât work in JBoss/Tomcat.
The way this works is that the Jasper TldLocationsCache âScans all JARs
accessible to the webapp's classloader and its parent classloaders for TLDs.â
If I put my jar into Tomcat standaloneâs common/lib directory then the tag
library will be shared across all web apps. Iâve tried putting the jar in
several âwell knownâ locations in JBoss/Tomcat and nothing seems to work.
For Reference, Iâve attached the TldLocationsCache source code from Tomcat
5.5.8.
Concerning TldLocationsCache, Scott Stark says:
"This class is useless for non-URLClassLoaders and URLClassLoaders that do not
expose their classpath via getURLs which is what we currently do because of an
old bad behavior with annotated codebases of rmi classes. "
Remy Maucherat offered this as a possible solution:
Would it be possible to have the ENCLoader facade return more interesting
things ?
/**
* A trival extension of URLClassLoader that uses an empty URL[] as its
* classpath so that all work is delegated to its parent.
*/
static class ENCLoader extends URLClassLoader
{
private URL[] urllist = new URL[0];
ENCLoader(ClassLoader parent)
{
super(new URL[0], parent);
}
void addURLInternal(URL url)
{
URL[] result = new URL[urllist.length + 1];
for (int i = 0; i < urllist.length; i++)
result[i] = urllist[i];
result[urllist.length] = url;
urllist = result;
}
public URL[] getURLs()
{
return urllist;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1602) Can't use container level taglibs
[ http://jira.jboss.com/jira/browse/JBAS-1602?page=history ]
Stan Silvert updated JBAS-1602:
---
Attachment: TldLocationsCache.java
> Can't use container level taglibs
> -
>
> Key: JBAS-1602
> URL: http://jira.jboss.com/jira/browse/JBAS-1602
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Reporter: Stan Silvert
> Priority: Critical
> Attachments: TldLocationsCache.java
>
>
> JBoss/Tomcat needs a way to install tag libraries globally so they are
> available to all web applications. This functionality is mentioned in the
> JSP 2.0 spec section 7.3.5. In Tomcat standalone, you can do this, but it
> doesn?t work in JBoss/Tomcat.
> The way this works is that the Jasper TldLocationsCache ?Scans all JARs
> accessible to the webapp's classloader and its parent classloaders for TLDs.?
> If I put my jar into Tomcat standalone?s common/lib directory then the tag
> library will be shared across all web apps. I?ve tried putting the jar in
> several ?well known? locations in JBoss/Tomcat and nothing seems to work.
> For Reference, I?ve attached the TldLocationsCache source code from Tomcat
> 5.5.8.
> Concerning TldLocationsCache, Scott Stark says:
> "This class is useless for non-URLClassLoaders and URLClassLoaders that do
> not expose their classpath via getURLs which is what we currently do because
> of an old bad behavior with annotated codebases of rmi classes. "
> Remy Maucherat offered this as a possible solution:
> Would it be possible to have the ENCLoader facade return more interesting
> things ?
>/**
> * A trival extension of URLClassLoader that uses an empty URL[] as its
> * classpath so that all work is delegated to its parent.
> */
>static class ENCLoader extends URLClassLoader
>{
> private URL[] urllist = new URL[0];
> ENCLoader(ClassLoader parent)
> {
> super(new URL[0], parent);
> }
> void addURLInternal(URL url)
> {
> URL[] result = new URL[urllist.length + 1];
> for (int i = 0; i < urllist.length; i++)
> result[i] = urllist[i];
> result[urllist.length] = url;
> urllist = result;
> }
> public URL[] getURLs()
> {
> return urllist;
> }
>}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1508) JBoss AS needs JSF
[ http://jira.jboss.com/jira/browse/JBAS-1508?page=history ] Stan Silvert closed JBAS-1508: -- Resolution: Done > JBoss AS needs JSF > -- > > Key: JBAS-1508 > URL: http://jira.jboss.com/jira/browse/JBAS-1508 > Project: JBoss Application Server > Type: Feature Request > Components: Web (Tomcat) service > Versions: JBossAS-4.0.2RC1 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: JBossAS-4.0.2 Final > > Original Estimate: 1 week > Remaining: 1 week > > JSF support needs to be added to the JBoss AS distribution. Initially, > MyFaces will be the implementation chosen. This will probably also include > the JSF Car Demo as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1508) JBoss AS needs JSF
[ http://jira.jboss.com/jira/browse/JBAS-1508?page=history ] Stan Silvert updated JBAS-1508: --- Version: (was: JBossAS-4.0.2 Final) (was: JBossPOJOServer-1.0 Alpha) (was: JBossAS-5.0 Alpha) (was: JBossPOJOServer-1.0 Final) (was: JBossAS-5.0 Beta) (was: JBossAS-5.0 Final) (was: JBossAS-3.2.8 Final) Fix Version: (was: JBossAS-5.0 Alpha) (was: JBossAS-5.0 Final) (was: JBossAS-3.2.8 Final) > JBoss AS needs JSF > -- > > Key: JBAS-1508 > URL: http://jira.jboss.com/jira/browse/JBAS-1508 > Project: JBoss Application Server > Type: Feature Request > Components: Web (Tomcat) service > Versions: JBossAS-4.0.2RC1 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: JBossAS-4.0.2 Final > > Original Estimate: 1 week > Remaining: 1 week > > JSF support needs to be added to the JBoss AS distribution. Initially, > MyFaces will be the implementation chosen. This will probably also include > the JSF Car Demo as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1508) JBoss AS needs JSF
[ http://jira.jboss.com/jira/browse/JBAS-1508?page=comments#action_12316244 ] Stan Silvert commented on JBAS-1508: Done. See http://www.jboss.org/wiki/Wiki.jsp?page=JBossFaces > JBoss AS needs JSF > -- > > Key: JBAS-1508 > URL: http://jira.jboss.com/jira/browse/JBAS-1508 > Project: JBoss Application Server > Type: Feature Request > Components: Web (Tomcat) service > Versions: JBossAS-4.0.2RC1, JBossAS-4.0.2 Final, JBossPOJOServer-1.0 > Alpha, JBossAS-5.0 Alpha, JBossPOJOServer-1.0 Final, JBossAS-5.0 Beta, > JBossAS-5.0 Final, JBossAS-3.2.8 Final > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-5.0 Final, > JBossAS-3.2.8 Final > > Original Estimate: 1 week > Remaining: 1 week > > JSF support needs to be added to the JBoss AS distribution. Initially, > MyFaces will be the implementation chosen. This will probably also include > the JSF Car Demo as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1508) JBoss AS needs JSF
JBoss AS needs JSF -- Key: JBAS-1508 URL: http://jira.jboss.com/jira/browse/JBAS-1508 Project: JBoss Application Server Type: Feature Request Versions: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-5.0 Beta, JBossAS-5.0 Final, JBossAS-4.0.2RC1, JBossPOJOServer-1.0 Alpha, JBossPOJOServer-1.0 Final, JBossAS-3.2.8 Final Reporter: Stan Silvert Assigned to: Stan Silvert Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-5.0 Beta, JBossAS-5.0 Final, JBossAS-4.0.2RC1, JBossPOJOServer-1.0 Alpha, JBossPOJOServer-1.0 Final, JBossAS-3.2.8 Final JSF support needs to be added to the JBoss AS distribution. Initially, MyFaces will be the implementation chosen. This will probably also include the JSF Car Demo as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1313) RepositorySelector should be integrated into JBoss Server
RepositorySelector should be integrated into JBoss Server - Key: JBAS-1313 URL: http://jira.jboss.com/jira/browse/JBAS-1313 Project: JBoss Application Server Type: Feature Request Reporter: Stan Silvert Assigned to: Stan Silvert Priority: Minor Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly. This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger(). We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-79) HttpSessionBindingListener broken when replication enabled
[ http://jira.jboss.com/jira/browse/JBCACHE-79?page=history ] Stan Silvert updated JBCACHE-79: Attachment: sessionbindinglistener.zip I also attached the test app to this issue. > HttpSessionBindingListener broken when replication enabled > -- > > Key: JBCACHE-79 > URL: http://jira.jboss.com/jira/browse/JBCACHE-79 > Project: JBoss Cache > Type: Bug > Reporter: Stan Silvert > Assignee: Ben Wang > Attachments: sessionbindinglistener.zip > > > With HttpSessionReplication enabled, an object that implements > HttpSessionBindingListener is placed in the session. When the session times > out, valueUnbound() is never called. > This was reported by a support customer and is found in case 2748: > https://na1.salesforce.com/5003000aiwP > I have attached a simple WAR to the case that reproduces the problem. > It may be that the other related listeners from the servlet spec are not > working as well, but this has not been tested. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-79) HttpSessionBindingListener broken when replication enabled
HttpSessionBindingListener broken when replication enabled -- Key: JBCACHE-79 URL: http://jira.jboss.com/jira/browse/JBCACHE-79 Project: JBoss Cache Type: Bug Reporter: Stan Silvert Assigned to: Ben Wang With HttpSessionReplication enabled, an object that implements HttpSessionBindingListener is placed in the session. When the session times out, valueUnbound() is never called. This was reported by a support customer and is found in case 2748: https://na1.salesforce.com/5003000aiwP I have attached a simple WAR to the case that reproduces the problem. It may be that the other related listeners from the servlet spec are not working as well, but this has not been tested. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
