-
1. Re: 3.0.1 problem without DOCTYPE / with DOCTYPE in xml desc
taiwubrian Aug 17, 2002 6:02 AM (in response to taiwubrian)Hi, Sorry. I solved part of the problem. The MarshalledValuePair problem was gone by parse all jar file in the ${JBOSS_HOME}/client directory on Netbeans. That is, in my classpath. However, DOCTYPE problem still exists.
Pleas help.
Brian -
2. Re: 3.0.1 problem without DOCTYPE / with DOCTYPE in xml desc
dsundstrom Aug 17, 2002 11:21 PM (in response to taiwubrian)The DOCTYPE is required to be present by the EJB specification. If JBoss is actually going to the server to get the dtd, it is a bug. Can you file a bug report?
-
3. Re: 3.0.1 problem without DOCTYPE / with DOCTYPE in xml desc
taiwubrian Aug 18, 2002 6:16 AM (in response to taiwubrian)Thanks.
I found cause of NumberFormatException. In my jbosscmp-jdbc.xml, I had an entry: <read-time-out/>, which causes that exception. In the file, org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData , the following codes actually invoke the exception:
// read-time-out
String readTimeOutStr =
MetaData.getOptionalChildContent(element, "read-time-out");
if(readTimeOutStr != null) {
readTimeOut = Integer.parseInt(readTimeOutStr);
} else {
readTimeOut = defaultValues.getReadTimeOut();
}
The Integer.parseInt(readTimeOutStr) causes NumberFormatException if <read-time-out/> is used. Is this a bug since <read-time-out/> is not illegal? I know I shouldn't have done that. However, should a try { catch(){} be used?
// read-time-out
String readTimeOutStr =
MetaData.getOptionalChildContent(element, "read-time-out");
if(readTimeOutStr != null) {
try {
readTimeOut = Integer.parseInt(readTimeOutStr);
} catch (java.lang.NumberFormatException numberformatException){
readTimeOut = defaultValues.getReadTimeOut();
}
} else {
readTimeOut = defaultValues.getReadTimeOut();
} -
4. Re: 3.0.1 problem without DOCTYPE / with DOCTYPE in xml desc
dsundstrom Aug 18, 2002 3:39 PM (in response to taiwubrian)You right. Can you post a bug report or a pactch? Thanks.