[JBoss Cache: Core Edition] - XML parse error of ...-aop.xml in JAS 5.1
by bmc
Hi everybody,
I`m trying to start JAS 5.1 with Jboss Cache (as in tutorial) and stuck on writing mycache-aop.xml file.
JAS want`s me to specify namespace of aop.xml file. But whatever I specify - nothing work. For exemple if I specify
| <aop xmlns="urn:jboss:aop-beans:1.0">
|
I get an error:
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:aop-beans:1.
| 0}interceptor not found as a child of {urn:jboss:aop-beans:1.0}bind
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE
| lement(SundayContentHandler.java:400)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
| dler.startElement(SaxJBossXBParser.java:401)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
| ce)
| at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unkn
| own Source)
| at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(Unknown Sourc
| e)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
| own Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
| Dispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
| known Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour
| ce)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
| er.java:199)
| ... 30 more
|
What am I doing wrong?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221516#4221516
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221516
17 years
[Security & JAAS/JBoss] - Re: problem with https
by cibermon
Hola chicos, despu??s de buscar mucho he optado por una soluci??n que ni mucho menos es ??ptima pero al menos funciona.
Lo que he hecho es hacer un filtro que rediriga a la misma pagina pero con http:// y con el puerto 8080 o el que corresponda. Os pego el codigo.
public class ControlProtocolo implements Filter{
public void destroy() {
System.out.println(".... destruido filtro Control de Protocolo");
}
public void doFilter(ServletRequest arg0, ServletResponse arg1,
FilterChain arg2) throws IOException, ServletException {
if (arg0.isSecure()){
HttpServletRequest httpRequest = (HttpServletRequest) arg0;
HttpServletResponse httpResponse = (HttpServletResponse) arg1;
StringBuffer redirectURL = new StringBuffer();
redirectURL.append("http://");
redirectURL.append(httpRequest.getServerName());
redirectURL.append(":8080");
redirectURL.append(httpRequest.getContextPath());
redirectURL.append(httpRequest.getServletPath());
String queryString = httpRequest.getQueryString();
if (queryString!=null){
redirectURL.append("?");
redirectURL.append(queryString);
}
httpResponse.sendRedirect(redirectURL.toString());
}else{
arg2.doFilter(arg0, arg1);
}
}
public void init(FilterConfig arg0) throws ServletException {
System.out.println("Iniciando filtro Control de Protocolo ...");
}
}
Y en el web.xml, logicamente s??lo lo voy a aplicar a la zona nosegura, que es la candidata a ser redireccionada.
{filter}
{filter-name>controlProtocoloFilter{/filter-name}
{filter-class}
es.carm.javato.infoWeb.filtros.ControlProtocolo
{/filter-class}
{/filter}
{filter-mapping}
{filter-name}controlProtocoloFilter{/filter-name}
{url-pattern}/nosegura/*{/url-pattern}
{/filter-mapping}
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221510#4221510
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221510
17 years