September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-3350) NPE on web service deployment

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3350?page=all ] Thomas Diesler reassigned JBAS-3350: ------------------------------------ Assignee: Remy Maucherat Remy, could you please have a look. > NPE on web service deployment > ----------------------------- > > 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 > > 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-776) EvictionPolicyProvider WARN message is noisy and misleading

by Galder Zamarreno (JIRA)

EvictionPolicyProvider WARN message is noisy and misleading ----------------------------------------------------------- Key: JBCACHE-776 URL: http://jira.jboss.com/jira/browse/JBCACHE-776 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1, 1.3.0.SP3 Reporter: Galder Zamarreno Assigned To: Manik Surtani JBoss AS 4.0.x assumes JBossCache 1.2.x which originally used EvictionPolicyProvider variable to hold eviction policies. The usage of this variable has been deprecated, but JBossCache 1.3.x and 1.4.x still need to set it in order to provide backwards compatibility. Calling setEvictionPolicyProvider() results on a misleading noisy WARN message, which : "Using deprecated configuration element 'EvictionPolicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases." This message should be downgraded and the text revised. -- 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

19 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-3700) Declared SQL Finder does not work with cmp2.x jdbc2 pm

by anajavi (JIRA)

Declared SQL Finder does not work with cmp2.x jdbc2 pm ------------------------------------------------------ Key: JBAS-3700 URL: http://jira.jboss.com/jira/browse/JBAS-3700 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.4.GA Reporter: anajavi Assigned To: Alexey Loubyansky When using declared sql where clause in finder, the generated sql does not contain all the fields of the entity. The cmp2.x jdbc2 pm requires the query to return all the fields. This causes an exception when the finder is invoked. This is caused by DeclaredSQLQueryCommand.java and method buildSQL: if(metadata.getFieldName() == null) { // we are selecting a full entity table = this.entity.getQualifiedTableName(); // get a list of all fields to be loaded // put pk fields in front String tableAlias = getTableAlias(alias, from, this.entity.getTableName()); selectList = SQLUtil.getColumnNamesClause(this.entity.getPrimaryKeyFields(), tableAlias, new StringBuffer(35)).toString(); } Quick fix is to change this.entity.getPrimaryKeyFields() to this.entity.getTableFields(). The configurations: ejb-jar.xml: <query> <query-method> <method-name>findByNimi</method-name> <method-params> <method-param>java.lang.String</method-param> </method-params> </query-method> <ejb-ql><![CDATA[SELECT OBJECT(o) FROM Yritys AS o WHERE o.nimi=?1]]></ejb-ql> </query> jbosscmp-jdbc.xml: <query> <description/> <query-method> <method-name>findByNimi</method-name> <method-params> <method-param>java.lang.String</method-param> </method-params> </query-method> <declared-sql> <where><![CDATA[upper(nimi) like upper({0})]]></where> </declared-sql> </query> -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3484) non portable JDK dependant clasess (sun.**)

by Andrew Oliver (JIRA)

non portable JDK dependant clasess (sun.**) ------------------------------------------- Key: JBAS-3484 URL: http://jira.jboss.com/jira/browse/JBAS-3484 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service, Security Affects Versions: JBossAS-4.0.4.GA, JBossAS-5.0.0.CR1 Reporter: Andrew Oliver Assigned To: Adrian Brock We should not be using sun.** classes in tests or in code. they are naughty and break working on non Sun JDKs. [andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -i "sun.misc.BASE64Encoder" '{}' ';' sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder(); [andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.misc.BASE64Encoder" '{}' ';' ./security/src/main/org/jboss/test/UtilTestCase.java: sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder(); [andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.misc" '{}' ';' ./security/src/main/org/jboss/test/UtilTestCase.java: /** Compare Util.encodeBase64 against the sun misc class ./security/src/main/org/jboss/test/UtilTestCase.java: sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder(); ./jaxrpc/src/main/org/jboss/axis/utils/Base64.java: * Eliminates dependency on sun.misc.Base64Encoding, ./jaxrpc/src/main/org/jboss/axis/utils/Base64.java: * (it's an access exception to load sun.misc.* classes [andy@localhost jboss-4.0.x]$ find . -name "*.java" -exec grep -Hi "sun.io" '{}' ';' ./messaging/src/main/org/jboss/mq/xml/XElement.java: sun.io.CharToByteUTF8 conv = new sun.io.CharToByteUTF8(); ./messaging/src/main/org/jboss/mq/xml/XElement.java: } catch ( sun.io.MalformedInputException e ) { [andy@localhost jboss-4.0.x]$ Moreover the -- 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

19 years, 8 months

4
9
0 / 0

[JBoss JIRA] Closed: (JBAS-3698) JNDI Lookup returns null

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3698?page=all ] Dimitris Andreadis closed JBAS-3698. ------------------------------------ Please, use the forums to ask for help, this is not a bug report. > JNDI Lookup returns null > ------------------------ > > Key: JBAS-3698 > URL: http://jira.jboss.com/jira/browse/JBAS-3698 > Project: JBoss Application Server > Issue Type: Release > Security Level: Public(Everyone can see) > Environment: WIndows XP 2002 SP2 > Reporter: uphaar kotru > Assigned To: Scott M Stark > Fix For: No Release > > > I am having issue with jndi lookup for my datasource in 4.0.3 SP1. The jndi is getting bound properly but while I try to lookup, it returns null. > When I use exactly same WAR file and Oracle-DS.xml on 4.0.2, it works fine. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBAS-3698) JNDI Lookup returns null

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3698?page=all ] Dimitris Andreadis deleted JBAS-3698: ------------------------------------- > JNDI Lookup returns null > ------------------------ > > Key: JBAS-3698 > URL: http://jira.jboss.com/jira/browse/JBAS-3698 > Project: JBoss Application Server > Issue Type: Release > Security Level: Public(Everyone can see) > Environment: WIndows XP 2002 SP2 > Reporter: uphaar kotru > Assigned To: Scott M Stark > > I am having issue with jndi lookup for my datasource in 4.0.3 SP1. The jndi is getting bound properly but while I try to lookup, it returns null. > When I use exactly same WAR file and Oracle-DS.xml on 4.0.2, it works fine. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3698) JNDI Lookup returns null

by uphaar kotru (JIRA)

JNDI Lookup returns null ------------------------ Key: JBAS-3698 URL: http://jira.jboss.com/jira/browse/JBAS-3698 Project: JBoss Application Server Issue Type: Release Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.0.3 SP1 Environment: WIndows XP 2002 SP2 Reporter: uphaar kotru Assigned To: Scott M Stark Fix For: JBossAS-4.0.2 Final I am having issue with jndi lookup for my datasource in 4.0.3 SP1. The jndi is getting bound properly but while I try to lookup, it returns null. When I use exactly same WAR file and Oracle-DS.xml on 4.0.2, it works fine. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3487) Create test of ClusteredSingleSignOn with BR enabled

by Brian Stansberry (JIRA)

Create test of ClusteredSingleSignOn with BR enabled ---------------------------------------------------- Key: JBAS-3487 URL: http://jira.jboss.com/jira/browse/JBAS-3487 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.5.GA Need to toggle the buddyReplicationEnabled attribute, restart and re-run. I've already tested it works manually; need to add to suite to ensure there are no regressions. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Updated: (BPEL-144) publish document/literal endpoints

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-144?page=all ] Alejandro Guizar updated BPEL-144: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > publish document/literal endpoints > ---------------------------------- > > Key: BPEL-144 > URL: http://jira.jboss.com/jira/browse/BPEL-144 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: jaxrpc, saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > jBPM BPEL currently generates service WSDL documents and processes SOAP request/response messages only for RPC/literal web services. Enhancing the service generation tool and the JAX-RPC handler to cover the document style is crucial for interoperability, particulary with .NET. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-9) fault and termination handling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-9?page=all ] Alejandro Guizar updated BPEL-9: -------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > fault and termination handling > ------------------------------ > > Key: BPEL-9 > URL: http://jira.jboss.com/jira/browse/BPEL-9 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Juan Cantu > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > -Implement the state transitions for scope instances when cancel or faulted signals are received > -Provide the fault catching logic -- 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

19 years, 8 months

1
0
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 September 2006