July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-89) Allow Specifying Custom Interceptors in XML Configuration

by Mircea Markus (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=all ] Mircea Markus resolved JBCACHE-89. ---------------------------------- Fix Version/s: 3.0.0.ALPHA1 Resolution: Done resolved all but the documentation (docs cannot be updated at this time as the layout is being changed for i18n). http://jira.jboss.com/jira/browse/JBCACHE-1391 was created to capture this. > Allow Specifying Custom Interceptors in XML Configuration > --------------------------------------------------------- > > Key: JBCACHE-89 > URL: http://jira.jboss.com/jira/browse/JBCACHE-89 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Daniel Gredler > Assigned To: Mircea Markus > Fix For: 3.0.0.ALPHA1, 3.0.0.GA > > Original Estimate: 1 day > Time Spent: 30 minutes > Remaining Estimate: 7 hours, 30 minutes > > It would be nice to be able to add interceptors via the XML configuration files. Indeed, in TreeCache.java the following comment exists, which may indicate that this feature is already planned: > // Create the interceptors in the correct order (later to be defined in XML file) > createInterceptorChain(); > A possible example configuration would be: > <server> > <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" /> > <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache"> > ... > <attribute name="Interceptors"> > <interceptor>com.foo.project.MyInterceptor</interceptor> > </attribute> > ... > </mbean> > </server> > Something along the lines of the following method would then be able to add the custom interceptors (in TreeCache.java): > public void setInterceptors(Element interceptors) throws Exception { > NodeList list = interceptors.getChildNodes(); > for(int i = 0; i < list.getLength(); i++) { > org.w3c.dom.Node node = list.item(i); > if(node.getNodeType() != org.w3c.dom.Node.ELEMENT_NODE) > continue; > NodeList children = node.getChildNodes(); > if(children.getLength() != 1) > continue; > org.w3c.dom.Node childNode = list.item(0); > if(childNode.getNodeType() != org.w3c.dom.Node.TEXT_NODE) > continue; > String className = childNode.getNodeValue(); > if(className == null || className.length() == 0) > continue; > Interceptor interceptor = createInterceptor(className); > addInterceptor(interceptor_chain, interceptor); > } > } -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1283) Remove MBEAN tag from configuration files

by Manik Surtani (JIRA)

Remove MBEAN tag from configuration files ----------------------------------------- Key: JBCACHE-1283 URL: http://jira.jboss.com/jira/browse/JBCACHE-1283 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.0.0 Replace the <mbean ... /> container tag in config files with a <jbosscache ... /> tag. Would entail: 1) update all sample configs and docs to reflect this "new" element 2) document how the configuration will still accept old <mbean ... /> tags, but this is deprecated 3) document how the <mbean ... /> tag can cause problems with AS 5 (unintentional deployment), and how this can be done properly with the MC using the new <jbosscache ... /> tag Currently the XMLConfigurationParser looks for a <mbean ../> element, under which it pulls out more specific JBoss Cache elements. This could easily change so the parser to accept this, or on failing to do so, to pick up a <jbosscache ... /> container element. And log a deprecation warning when using the old <mbean ... /> container tag. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

2
4
0 / 0

[JBoss JIRA] Resolved: (JBWEB-17) support mapping multiple Connectors to different vhosts

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBWEB-17?page=all ] Remy Maucherat resolved JBWEB-17. --------------------------------- Resolution: Rejected The Tomcat architecture uses a hierachical view that is good for many things, including sensible configurability, but in return is not as flexible for mixing and matching connectors with hosts and individual webapps. Options include access restriction valves or "URL" rewriting using the JBoss Web rewrite valve, which will provide something transparent to your webapp. > support mapping multiple Connectors to different vhosts > ------------------------------------------------------- > > Key: JBWEB-17 > URL: http://jira.jboss.com/jira/browse/JBWEB-17 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Module > Reporter: Jan Hecking > Assigned To: Remy Maucherat > > See forum posting: > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870728 > I'd like to deploy several web apps in a single JBoss server. Some of these apps are for internal use only. For security reasons it is required that the internal apps are not available on the same port as the external apps. Using regular vhosts is not sufficient as the vhost being accessed entirely depends on the Host: HTTP header sent by the client so requests to the "internal" vhosts cannot be blocked by the firewall on the TCP/IP layer but only by analyzing the HTTP request on the application layer. > As Scott Stark suggested in a reply to my forum posting it would be great if different Tomcat HTTP Connectors could be mapped to each vhost. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-68) Servlet.init(ServletConfig) not called

by Thomas Diesler (JIRA)

Servlet.init(ServletConfig) not called -------------------------------------- Key: JBWEB-68 URL: http://jira.jboss.com/jira/browse/JBWEB-68 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Remy Maucherat <componentref name="apache-tomcat" version="6.0-snapshot"/> [tdiesler@tdvaio trunk]$ svn info Path: . URL: https://svn.jboss.org/repos/jbossas/trunk Repository Root: https://svn.jboss.org/repos/jbossas Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1 Revision: 55837 Node Kind: directory Schedule: normal Last Changed Author: rrajesh Last Changed Rev: 55837 Last Changed Date: 2006-08-11 22:26:36 +0200 (Fri, 11 Aug 2006) <servlet> <servlet-name>TestService</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.endpoint.EndpointServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4511) CachedConnectionManager valve needs enabling in JBoss5

by Adrian Brock (JIRA)

CachedConnectionManager valve needs enabling in JBoss5 ------------------------------------------------------ Key: JBAS-4511 URL: http://jira.jboss.com/jira/browse/JBAS-4511 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Adrian Brock Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta3 The CCM valve needs enabling in JBoss5. However, you can no longer just enable due to the issue described on the forum thread. I've temporarily moved the CachedConnectionManager MBean into deployers so Tomcat can depend it, but Tomcat should not be in the deployers. Once Tomcat is fixed, the file deployers/jca-hack-for-tomcat-service.xml needs removing and the FIXMEs in build/build-distr.xml and jbossjca-service.xml reverting. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1390) de-genericize Fqns

by Manik Surtani (JIRA)

de-genericize Fqns ------------------ Key: JBCACHE-1390 URL: http://jira.jboss.com/jira/browse/JBCACHE-1390 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.0.0.GA Fqn generics were introduced in 2.0.0. This is a poor idea since Fqns would almost certainly contain a mixed set of elements. De-genericizing to simplify. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2074) admin ui error from bridge with jboss eap 4.3

by Prabhat Jha (JIRA)

admin ui error from bridge with jboss eap 4.3 --------------------------------------------- Key: JBPORTAL-2074 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2074 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.7.0 Alpha1 Reporter: Prabhat Jha Assigned To: Wesley Hales Fix For: 2.7.0 Beta1 I was able to reproduce with EAP 4.3 (not AS 4.2.2). The thing that changed is the version of the SUN RI JSF libs. I tried to run EAP with the JSF libs included in AS 4.2.2 and it runs fine with that change. Between AS 4.2.2 and EAP 4.3 it has been upgraded: from: 1.2_04_P02 to 1.2_08-brew I let Wesley continue the investigation. Prabhat Jha wrote: > Wesley, > > This is using JBoss EAP 43 and jboss-portal-ha.sar. When I log as admin console and click on Admin, I get this error in server.log. I have attached the screen shot of admin UI. > > 2008-07-14 16:20:08,634 WARN [javax.enterprise.resource.webcontainer.jsf.lifecycle] JSF1053: (Listener: org.jboss.portal.core.admin.ui.Refresher.beforePhase(), Phase ID: RESTORE_VIEW 1, View ID: ) Exception thrown during phase-listener execution: java.lang.NullPointerException > 2008-07-14 16:20:08,637 WARN [javax.enterprise.resource.webcontainer.jsf.lifecycle] org.jboss.portal.core.admin.ui.PortalObjectManagerBean.refresh(PortalObjectManagerBean.java:661) > org.jboss.portal.core.admin.ui.Refresher.refreshFrom(Refresher.java:74) > org.jboss.portal.core.admin.ui.Refresher.beforePhase(Refresher.java:54) > com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) > com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) > com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104) > com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > org.jboss.portletbridge.AjaxPortletBridge.execute(AjaxPortletBridge.java:587) > org.jboss.portletbridge.AjaxPortletBridge.renderResponse(AjaxPortletBridge.java:441) > org.jboss.portletbridge.AjaxPortletBridge.doFacesRequest(AjaxPortletBridge.java:344) > javax.portlet.faces.GenericFacesPortlet.doFacesDispatch(GenericFacesPortlet.java:343) > javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:306) > javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328) > javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:287) > javax.portlet.GenericPortlet.render(GenericPortlet.java:233) > org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:568) > org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159) > org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:80) > org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:505) > org.jboss.portal.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatcher.java:42) > org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5771) Tomcat SSI & CGI don't deploy correctly

by Erik Lindquist (JIRA)

Tomcat SSI & CGI don't deploy correctly --------------------------------------- Key: JBAS-5771 URL: http://jira.jboss.com/jira/browse/JBAS-5771 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.CR1 Environment: linux Reporter: Erik Lindquist Assigned To: Remy Maucherat install jboss-5.0.0.CR1 edit ...server/default/deployers/jbossweb.deployer/web.xml activate ssi servlet (uncomment appropriate sections) edit .../server/default/deploy/jbossweb.sar/context.xml grant privilege=true in <Context> tag start jboss log shows: java.lang.ClassNotFoundException: org.apache.catalina.ssi.SSIServlet -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

2
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-283) searching the forum is a fulltime job

by arne anka (JIRA)

searching the forum is a fulltime job ------------------------------------- Key: JBFORUMS-283 URL: http://jira.jboss.com/jira/browse/JBFORUMS-283 Project: JBoss Forums Issue Type: Quality Risk Reporter: arne anka Assigned To: Ryszard Kozmik a) only one forum is searchable at a time -- because the names of the fora are not much help and the topics might overlap anyway, that means searching several times for the same phrase and surfing several postings b) the fora to search are in no apparent order and with names not easily associated (for instance "Tools(JBoss Tools)" instead of "JBoss IDE") -- and the list is far to lang to be scanned easily. last time it required three or four approaces to find the forum seemingly appropriate to search for questions regarding jboss ide c) it's not easy to comprehend that the [search...] field on top of the page (one row with flasg, "Login", "Register" ...) is in now way related to the fora. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5769) Fix org.jboss.test.jca.test.BackgroundValidationUnitTestCase.testDeployedBackgroundValidationFailure

by Dimitris Andreadis (JIRA)

Fix org.jboss.test.jca.test.BackgroundValidationUnitTestCase.testDeployedBackgroundValidationFailure ---------------------------------------------------------------------------------------------------- Key: JBAS-5769 URL: http://jira.jboss.com/jira/browse/JBAS-5769 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service, Test Suite Reporter: Dimitris Andreadis Assigned To: Jesper Pedersen Priority: Critical Fix For: JBossAS-4.2.3.GA It fails on JBoss-AS-4.2.x-TestSuite-sun16-sun16: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-Test... -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008