October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3350) NPE on <service-ref> in web.xml

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3350?page=comments#action_12345496 ] Remy Maucherat commented on JBAS-3350: -------------------------------------- To save you time, you can set the "org.apache.catalina.STRICT_SERVLET_COMPLIANCE" system property to "false". > NPE on <service-ref> in web.xml > ------------------------------- > > Key: JBAS-3350 > URL: http://jira.jboss.com/jira/browse/JBAS-3350 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > > tdiesler@TDDELL /cygdrive/d/svn/jbossws/trunk/src/test > $ ant -Dtest=org.jboss.test.ws.wsse.WebClientTestCase one-test > 2006-06-29 11:02:35,953 ERROR [org.apache.catalina.startup.ContextConfig] Parse error in application web.xml file at jndi:/localhost/jbossws-wsse-rpc/WEB-INF/web.xml > java.lang.NullPointerException > at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2725) > at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2751) > at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1060) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > <web-app version='2.4' 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_4.xsd'> > <servlet> > <servlet-name>Hello</servlet-name> > <servlet-class>org.jboss.ws.integration.jboss.JBossServiceEndpointServlet</servlet-class> > <init-param> > <param-name>ServiceEndpointImpl</param-name> > <param-value>org.jboss.test.ws.wsse.HelloJavaBean</param-value> > </init-param> > </servlet> > <servlet> > <servlet-name>RpcTestClientServlet</servlet-name> > <servlet-class>org.jboss.test.ws.wsse.RpcTestClientServlet</servlet-class> > </servlet> > <servlet-mapping> > <servlet-name>Hello</servlet-name> > <url-pattern>/Hello</url-pattern> > </servlet-mapping> > <servlet-mapping> > <servlet-name>RpcTestClientServlet</servlet-name> > <url-pattern>/RpcTestClientServlet</url-pattern> > </servlet-mapping> > <service-ref> > <service-ref-name>service/HelloService</service-ref-name> > <service-interface>javax.xml.rpc.Service</service-interface> > <wsdl-file>WEB-INF/wsdl/HelloService.wsdl</wsdl-file> > <jaxrpc-mapping-file>WEB-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file> > <port-component-ref> > <service-endpoint-interface>org.jboss.test.ws.wsse.Hello</service-endpoint-interface> > </port-component-ref> > </service-ref> > </web-app> -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-110) 1 tx per connection config

by Kurt Stam (JIRA)

1 tx per connection config -------------------------- Key: JBESB-110 URL: http://jira.jboss.com/jira/browse/JBESB-110 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Fix For: 4.0 Oracle does not allow multiple tx over 1 connection, however the JCA spec allows this (and most open source dbs support it). So we need some setting you can turn on to block the connection while a tx is in progress. Just for Oracle..as it will send Oracle into a spin lock :). This is not something for beta1. So don't sweat it. -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-109) DB reconnect after network failure/DB down

by Kurt Stam (JIRA)

DB reconnect after network failure/DB down ------------------------------------------ Key: JBESB-109 URL: http://jira.jboss.com/jira/browse/JBESB-109 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Fix For: 4.0 Add db reconnnect feature (congifurable). Before using a connection check if the connection is still valid, if not clean up this connection and try to use another existing connection, if a connections are removed, try to make a new connection. If this fails give up, throw exception, but next time try again.. -- 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 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-111) JMX support

by Kurt Stam (JIRA)

JMX support ----------- Key: JBESB-111 URL: http://jira.jboss.com/jira/browse/JBESB-111 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Priority: Minor Fix For: 4.0 Support for JMX (the one build into java5) so you can look at the pool and reset connection etc. -- 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 months

2
2
0 / 0

A la velocidad del Viento!

by ADSL Hostex

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Ovidiu Feodorov updated JBMESSAGING-407: ---------------------------------------- Issue Type: Feature Request (was: Patch) Fix Version/s: 1.0.2.CR1 (was: 1.2.0.Beta1) Assignee: Ovidiu Feodorov (was: Tim Fox) > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.0.2.CR1 > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3772) JBossCache classes fail serialization compatibility tests

by Ryan Campbell (JIRA)

JBossCache classes fail serialization compatibility tests --------------------------------------------------------- Key: JBAS-3772 URL: http://jira.jboss.com/jira/browse/JBAS-3772 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Reporter: Ryan Campbell Assigned To: Brian Stansberry Priority: Blocker Fix For: JBossAS-4.0.5.GA The serialVersionUID's changed for the following classes between JBoss 4.0.4 & JBoss 4.0.5: serialVersionUID error for org.jboss.cache.OptimisticTreeNode, 404 -5988969949899616983, current: 7000622696587912654 serialVersionUID error for org.jboss.cache.ReplicationException, 404 1652498986885131620, current: -2141504272926290430 Please confirm if these classes are serialized in any way, and if customers will experience faults if running both versions of JBoss, or using 4.0.4 client jars against a 4.0.5 server. -- 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 months

1
3
0 / 0

[JBoss JIRA] Closed: (JBAOP-240) Test AOP/MC integration with security manager

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-240?page=all ] Kabir Khan closed JBAOP-240. ---------------------------- Resolution: Done http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979171#3979171 > Test AOP/MC integration with security manager > --------------------------------------------- > > Key: JBAOP-240 > URL: http://jira.jboss.com/jira/browse/JBAOP-240 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > > The AOP/MC integration needs to have the tests working with the > java SecurityManager enabled. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-427) contactlist example nonfunctional with JSF 1.2 RI

by Chuck Adams (JIRA)

contactlist example nonfunctional with JSF 1.2 RI ------------------------------------------------- Key: JBSEAM-427 URL: http://jira.jboss.com/jira/browse/JBSEAM-427 Project: JBoss Seam Issue Type: Bug Reporter: Chuck Adams I'm using the JSF 1.2 RI in JBoss, and to get any example to run, I have to move el-api.jar and el-impl.jar to the jsf-libs directory and remove them from the war, or else the ConfigureListener bombs. No big deal, once I do that, the booking example works fine. The same isn't the case for the contactlist example however: the search page works, but view and edit just bring up a blank contact. When I switched back to myfaces, it worked perfectly (even though I forgot to set jbossHasMyFacesLifecycleBug back to true) -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-425) s:outputPanel in examples/booking/view/register.xhtml should be a:outputPanel

by Chuck Adams (JIRA)

s:outputPanel in examples/booking/view/register.xhtml should be a:outputPanel ----------------------------------------------------------------------------- Key: JBSEAM-425 URL: http://jira.jboss.com/jira/browse/JBSEAM-425 Project: JBoss Seam Issue Type: Bug Reporter: Chuck Adams Looks like a typo on line 71 <s:outputPanel id="nameErrors"><s:message/></a:outputPanel> Should be: <a:outputPanel id="nameErrors"><s:message/></a:outputPanel> This is, obviously, causing the register page to crash -- 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 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006