Re: [JBoss-dev] (Jason) file protocol handler....
BTW, I've refreshed and everything is now cool - thanks. Jules Jason Dillon wrote: Just wondering, but why not use URLConnection.getURL().getFile() instead of URLConnection.getPermssion() ? --jason _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12217 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] FORUMS ARE DOWN...
is this intentional ? Jules _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-538236 ] Oracle data mappings use TIMESTAMP type
Bugs item #538236, was opened at 2002-04-02 11:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=538236group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: Dain Sundstrom (dsundstrom) Summary: Oracle data mappings use TIMESTAMP type Initial Comment: The standardjbosscmp-jdbc.xml tries to use the TIMESTAMP datatype for mapping java.util.Date to an sql type for both Oracle7 and Oracle8 databases: mapping java-typejava.util.Date/java-type jdbc-typeTIMESTAMP/jdbc-type sql-typeTIMESTAMP/sql-type /mapping TIMESTAMP is not a valid Oracle7/8 datatype. Unfortunately there does not seem to be any kind of equivelent that we can use here. Oracle DATE types only have a granularity of whole seconds. I will investigate whether or not we can get away with using a NUMBER type here. -- Comment By: Peter Levart (plevart) Date: 2002-04-06 18:10 Message: Logged In: YES user_id=346981 Are you sure? It works for me. It might be that this is a new feature of Oracle 9i (I haven't tried with Oracle 7 or 8). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=538236group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JRockit now free
BEA has announced that JRockit 3.1 JVM will be free. We should get a copy to test on. They did not say that all future versions will be free, and they definitely did not say that it would be open source. Also they have a very weird license system. You need an account, and they claim you need a drivers license. I get the feeling that this is a scam, and if it is, I hope all of you give BEA a PR black eye. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-538236 ] Oracle data mappings use TIMESTAMP type
Bugs item #538236, was opened at 2002-04-02 09:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=538236group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stephen Coy (scoy) Assigned to: Dain Sundstrom (dsundstrom) Summary: Oracle data mappings use TIMESTAMP type Initial Comment: The standardjbosscmp-jdbc.xml tries to use the TIMESTAMP datatype for mapping java.util.Date to an sql type for both Oracle7 and Oracle8 databases: mapping java-typejava.util.Date/java-type jdbc-typeTIMESTAMP/jdbc-type sql-typeTIMESTAMP/sql-type /mapping TIMESTAMP is not a valid Oracle7/8 datatype. Unfortunately there does not seem to be any kind of equivelent that we can use here. Oracle DATE types only have a granularity of whole seconds. I will investigate whether or not we can get away with using a NUMBER type here. -- Comment By: Markus Kling (mkling) Date: 2002-04-06 16:30 Message: Logged In: YES user_id=360804 Up to version 8.1.7, Oracle supports only one temporal datatype: DATE, which has a granularity of second. The following datatypes are new for Oracle9i: TIMESTAMP TIMESTAMP [ (fractional_seconds_precision)] TIMESTAMP WITH [LOCAL]TIME ZONE INTERVAL YEAR TO MONTH INTERVAL DAY TO SECOND fractional_seconds_precision optionally specifies the number of digits in the fractional part of the SECOND datetime field and can be a number in the range 0 to 9. The default is 6. Below 9i date columns can be written and read as java.sql.Timestamp - the ms just get truncated. -Markus -- Comment By: Peter Levart (plevart) Date: 2002-04-06 16:10 Message: Logged In: YES user_id=346981 Are you sure? It works for me. It might be that this is a new feature of Oracle 9i (I haven't tried with Oracle 7 or 8). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=538236group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JRockit now free
This is a scam. The site says: As of the aquisition, the JRockit Virtual Machine is available for free! Now everyone can benefit from superior Java performance on Intel platforms. Download your copy today! Buy if you read the press release it says: The free trial license allows for 30 days of testing, benchmarking and production evaluation. Does anyone else find the first claim completely unethical? I think everyone should go to theserverside and tell BEA what they really think. -dain Dain Sundstrom wrote: BEA has announced that JRockit 3.1 JVM will be free. We should get a copy to test on. They did not say that all future versions will be free, and they definitely did not say that it would be open source. Also they have a very weird license system. You need an account, and they claim you need a drivers license. I get the feeling that this is a scam, and if it is, I hope all of you give BEA a PR black eye. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Lutris Leaves AppServer Market
Lutris has announced that they are no longer selling app servers. My favorite quote in the email from [EMAIL PROTECTED]: I encourage anyone looking for an open source J2EE application server to get JBOSS. We rock. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-540270 ] Classloader-problem with Tomcat 4.0.3
Bugs item #540270, was opened at 2002-04-06 19:57
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=540270group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas Peuss (tpeuss)
Assigned to: Nobody/Anonymous (nobody)
Summary: Classloader-problem with Tomcat 4.0.3
Initial Comment:
I am trying the embeddeded catalina service with JBoss
3.0 beta 2. The servlet-engine finds no classes besides
the standard Java-classes.
Log-file follows:
19:37:12,678 ERROR [EmbeddedCatalinaServiceSX]
StandardWrapperValve[jsp]: Servlet.service() for
servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile
class for JSP
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:3:
Package javax.management not found in import.
import javax.management.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:6:
Package javax.servlet not found in import.
import javax.servlet.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:7:
Package javax.servlet.http not found in import.
import javax.servlet.http.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:8:
Package javax.servlet.jsp not found in import.
import javax.servlet.jsp.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:9:
Package org.apache.jasper.runtime not found in import.
import org.apache.jasper.runtime.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:12:
Superclass org.apache.jsp.HttpJspBase of class
org.apache.jsp.mbs$jsp not found.public class mbs$jsp
extends HttpJspBase {
^
6 errors
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:285)
at
org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:552)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:177)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:189)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:484)
--
You can respond by visiting:
[JBoss-dev] Embedded Tomcat in JBoss 3.0beta2
I am trying the embedded tomcat in JBoss 3.0b2. It is not useful at the moment. I have several problems: - classloader problems: Tomcat finds only standard JDK-classes. - XML-parsing problems while reading web.xml: Tomcat tries to load the DTD for the web.xml-validation from the web. This does not work if you are behind a firewall. - Deploy/Undeploy-problems: If something goes wrong during deployment (e.g. an error in web.xml) you cannot undeploy anymore. Is there some work going on? If not: can someone give me a hint where I have to look for the classloader problems (IMHO the biggest problem ;-) )? CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JavaOne slides on line
If you didn't pop for the $3k, or you spend 2 days with us the JavaOne slides are on line. The EJB 2.1 slides are interesting http://servlet.java.sun.com/javaone/resources/content/sf2002/conf/sessions/pdfs/1653.pdf The define web services only for stateless-session beans. I think this is because of limitations of the web services specs (WC3 ?). The EJB-QL enhancements are interesting. They define ORDER BY just like we have today, and they added aggregate operators AVG, COUNT, MIN, MAX, SUM. The problem is they did not define any group by semantics, which means you may end up with lots of queries to do averages over several groups. I think I'll add GROUP BY and HAVING when I add the aggregate operators. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
I am well on my way with this. I have almost full functionality of the SUN HTML RI, and plan to be finished with that soon. I have registered for a project space on SourceForge, and will hopefully be pushing things out over the next week. It includes security, enhanced views, and easier navigation. Plus other things I hope to get added in as well. Jim _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Lutris Leaves AppServer Market
Maybe we could get this on the success stories/quotes page david jencks On 2002.04.06 11:40:21 -0500 Dain Sundstrom wrote: Lutris has announced that they are no longer selling app servers. My favorite quote in the email from [EMAIL PROTECTED]: I encourage anyone looking for an open source J2EE application server to get JBOSS. We rock. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/compliance/monitor MonitorTestCase.java
User: ejort
Date: 02/04/06 11:28:40
Modified:src/main/test/compliance/monitor Tag: BranchMX_1_0
MonitorTestCase.java
Log:
Gauge Monitor tests
Revision ChangesPath
No revision
No revision
1.1.2.3 +728 -0jmx/src/main/test/compliance/monitor/MonitorTestCase.java
Index: MonitorTestCase.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/monitor/MonitorTestCase.java,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- MonitorTestCase.java 29 Mar 2002 10:44:32 - 1.1.2.2
+++ MonitorTestCase.java 6 Apr 2002 19:28:40 - 1.1.2.3
@@ -1264,6 +1264,734 @@
checkNotificationInfo(Gauge, mbni, expected);
}
+ // Gauge normal tests --
+
+ /**
+* Test normal gauge notify high
+*/
+ public void testNormalGaugeThresholdHighExceededEarly()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(true, false, new Integer(10), new Integer(0), false);
+ expectStartMonitor(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ }
+ finally
+ {
+ stopMonitor();
+ MBeanServerFactory.releaseMBeanServer(server);
+ }
+ }
+
+ /**
+* Test normal gauge notify high
+*/
+ public void testNormalGaugeThresholdHighExceededLate()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(true, false, new Integer(10), new Integer(0), false);
+ dontExpectStartMonitor(new Integer(0));
+ expect(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ }
+ finally
+ {
+ stopMonitor();
+ MBeanServerFactory.releaseMBeanServer(server);
+ }
+ }
+
+ /**
+* Test normal gauge notify high
+*/
+ public void testNormalGaugeThresholdHighExceededLots()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(true, false, new Integer(10), new Integer(0), false);
+ dontExpectStartMonitor(new Integer(0));
+ expect(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ dontExpect(new Integer(0));
+ expect(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ dontExpect(new Integer(0));
+ expect(new Integer(20),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ }
+ finally
+ {
+ stopMonitor();
+ MBeanServerFactory.releaseMBeanServer(server);
+ }
+ }
+
+ /**
+* Test normal gauge notify high
+*/
+ public void testNormalGaugeThresholdHighExceededNot()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(true, false, new Integer(10), new Integer(0), false);
+ dontExpectStartMonitor(new Integer(0));
+ dontExpect(new Integer(9));
+ dontExpect(new Integer(0));
+ expect(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ dontExpect(new Integer(10));
+ dontExpect(new Integer(0));
+ expect(new Integer(10),
+MonitorNotification.THRESHOLD_HIGH_VALUE_EXCEEDED);
+ dontExpect(new Integer(20));
+ dontExpect(new Integer(9));
+ dontExpect(new Integer(10));
+ }
+ finally
+ {
+ stopMonitor();
+ MBeanServerFactory.releaseMBeanServer(server);
+ }
+ }
+
+ /**
+* Test normal gauge notify low
+*/
+ public void testNormalGaugeThresholdLowExceededEarly()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(false, true, new Integer(10), new Integer(0), false);
+ expectStartMonitor(new Integer(0),
+MonitorNotification.THRESHOLD_LOW_VALUE_EXCEEDED);
+ }
+ finally
+ {
+ stopMonitor();
+ MBeanServerFactory.releaseMBeanServer(server);
+ }
+ }
+
+ /**
+* Test normal gauge notify low
+*/
+ public void testNormalGaugeThresholdLowExceededLate()
+ throws Exception
+ {
+ initTest();
+ try
+ {
+ initGaugeMonitor(false, true, new Integer(10), new Integer(0), false);
+ dontExpectStartMonitor(new Integer(10));
+ expect(new Integer(0),
+MonitorNotification.THRESHOLD_LOW_VALUE_EXCEEDED);
+ }
+ finally
+ {
+ stopMonitor();
+
Re: [JBoss-dev] FORUMS ARE DOWN...
It appears to be up now. I didn't do anything, so either it was a tranisent network failure or the machine faries stepped in and gave me a hand. =) --jason Quoting Jules Gosnell [EMAIL PROTECTED]: is this intentional ? Jules _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] FORUMS ARE DOWN...
Oh... the machine was down to replace the tape drive. --jason Quoting Jules Gosnell [EMAIL PROTECTED]: is this intentional ? Jules _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] (Jason) file protocol handler....
Yes, this seems very odd to me. Still, why did this fail for you? I was
under the impression that URLConnection.getPermission() would return an
AllPermission and not a FilePermission, which would have caused this hack not
to be used. If the _url field has been initialized to URLConnection.getURL()
then this should have worked fine with the original.
Anyways, saw your note that it all works now. Sorry if this caused you much
trouble.
--jason
Quoting Jules Gosnell [EMAIL PROTECTED]:
That would be a question for Greg - who left to go skiing this morning -
tough life! :
/* */
/**
* Returns an File representing the given resource or NULL if this
* is not possible.
*/
public File getFile()
throws IOException
{
// Try the permission hack
if (checkConnection())
{
Permission perm = _connection.getPermission();
if (perm instanceof java.io.FilePermission)
return new File(perm.getName());
}
// Try the URL file arg
try {return new File(_url.getFile());}
catch(Exception e) {Code.ignore(e);}
// Don't know the file
return null;
}
Jules
Jason Dillon wrote:
Just wondering, but why not use URLConnection.getURL().getFile() instead of
URLConnection.getPermssion() ?
--jason
_
View thread online:
http://main.jboss.org/thread.jsp?forum=66thread=12217
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-
This mail sent through IMP: http://horde.org/imp/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Manual] CDs.txt vs. cds.txt
Hello,
while dealing with the CMP CD Client (chapter 4) from the great
volunteer doc, I met a problem with the target »cmp-cd-upload«. I got
an error message »Upload: can't read file `CDs.txt'«.
The problem is that
jboss/manual/src/examples/org/jboss/docs/cmp/cd/Upload.java references
'CDs.txt' but the filesystem only offers 'cds.txt'.
I provide a patch
--- /tmp/old_Upload.javaSat Apr 6 23:07:54 2002
+++ src/jboss-examples/org/jboss/docs/cmp/cd/Upload.javaSat Apr
6 23:08:07 2002
@@ -31,7 +31,7 @@
*/
public static void main(String[] args)
{
- String filename = »CDs.txt»;
+ String filename = »cds.txt»;
try
{
but I personally would prefer to rename the file in CVS to 'CDs.txt'.
Could any developer please make the changes? I've no sourceforge
account yet.
TIA -- Sebastian
--
PGP Key: 0x1E727CE6 2001-11-14 · expires 2002-11-09
Key fingerprint: 9085 48BD 8332 4BFC D80C A6CF D162 20BB 1E72 7CE6
http://gommbjudda.wh17.tu-dresden.de/~sebi/Sebastian_Klamar.asc
or via finger -l [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb EjbModule.java
User: luke_t
Date: 02/04/06 13:20:44
Modified:src/main/org/jboss/ejb EjbModule.java
Log:
Added log warning message for duplicate ejb names
Revision ChangesPath
1.15 +5 -2 jboss/src/main/org/jboss/ejb/EjbModule.java
Index: EjbModule.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/EjbModule.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- EjbModule.java23 Mar 2002 21:11:02 - 1.14
+++ EjbModule.java6 Apr 2002 21:20:43 - 1.15
@@ -78,7 +78,7 @@
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
* @author a href=mailto:[EMAIL PROTECTED];Francisco Reverbel/a
* @author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
- * @version $Revision: 1.14 $
+ * @version $Revision: 1.15 $
*
* @jmx:mbean extends=org.jboss.system.ServiceMBean
*/
@@ -154,7 +154,10 @@
*/
private void addContainer(Container con)
{
- containers.put(con.getBeanMetaData().getEjbName(), con);
+ String ejbName = con.getBeanMetaData().getEjbName();
+ if(containers.containsKey(ejbName))
+ log.warn(Duplicate ejb-name. Container for + ejbName + already
exists.);
+ containers.put(ejbName, con);
con.setEjbModule(this);
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 549 Errors:19 Failures: 7 [time of test: 7 April 2002 0:40 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 568 Successful tests: 541 Errors:20 Failures: 7 [time of test: 7 April 2002 1:45 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20020124 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 551 Errors:19 Failures: 5 [time of test: 7 April 2002 2:32 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 547 Errors:20 Failures: 8 [time of test: 7 April 2002 3:48 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-02a-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Should we add .sar to cvswrappers?
I'm a little nervous about messing with cvs settings or I'd do it. thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-540419 ] New JMX documentation tool
Change Notes item #540419, was opened at 2002-04-07 03:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=540419group_id=22866 Category: None Group: None Status: Open Priority: 5 Submitted By: David Jencks (d_jencks) Assigned to: Nobody/Anonymous (nobody) Summary: New JMX documentation tool Initial Comment: I've written an xdoclet task/template to generate documentation for jmx mbeans using essentially the same content as goes in the xmbean descriptor. In the first step, xdoclet generates docbook xml from the @jmx markup, and in the second step the docbook xsl generates html. Generated files go into output jmx-api. I put targets in the connector module for this, they are called from javadoc or all. The build/build.sh all target generates them and copies to build/output/jmx-api. This now generates the documentation for the new ConnectionManager framework. The current jboss xdoclet version uses xjavadoc. Source code for both jars is tagged in xdoclet cvs corresponding to the jboss cvs version. @todo: -Add targets to the other build files and write the documentation for the mbeans. -Improve the look of the generated documentation, such as adding jboss logos etc. -Generate a pdf manual from the docbook xml. -Generate an index page. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=540419group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss 3 users -- warning of impending configuration change
On March 25 I committed a new ConnectionManager implementation to JBoss 3 cvs. There do not seem to be many serious problems, so I will remove the old implementation shortly. THIS WILL COMPLETELY BREAK ALL PREVIOUS db-service.xml FILES!!! So far we have examples configuration for firebird, hypersonic, and postgres. They are located in a NEW LOCATION! connector/src/etc/example-config (hypersonic is in new-hsql-default-service.xml) PLEASE CONTRIBUTE YOUR NEW WORKING CONFIGURATIONS! Documentation for the new mbeans is generated by the new jmx documentation system. Run connector/build.sh jmx-docs-html-plain or build/build.sh all and look in the jmx-api directory. You can probably also simply look at the 3 existing examples and change the few properties necessary. Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-533686 ] JDBCStartCommand.tableExists() Oracle
Bugs item #533686, was opened at 2002-03-23 04:26 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Levart (plevart) Assigned to: Dain Sundstrom (dsundstrom) Summary: JDBCStartCommand.tableExists() Oracle Initial Comment: This is not realy a bug, rather a workarround for a peculiarity of the Oracle DB using thin JDBC driver. When deploying Entity Beans on Oracle (using thin driver - I haven't tried with the full blown native version), the JDBCStartCommand.tableExists() incorrectly returns false when the table already exists and deployment later fails when JBoss is trying to create the table. The problem is that table names in Oracle DB seem to be UPPER CASE ONLY. But the java.sql.DatabaseMetadata.getTables() that is used in JDBCStartCommand.tableExists() to check for the existense of a particular table, uses a tableNamePattern that performs a case-sensitive search. So if you specify the table name as SomeBean then the actual table created on the 1st deployment would be SOMEBEAN and later deployments will fail. One workarround is to simply use UPPER CASE ONLY names for tables when deploying on Oracle, the other would be for JDBCStartCommand.tableExists() to check for the existence of table with exact given name and for a table with an UPPER CASE NAME. I'm including the later as a patch attached to the bug report... -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 13:59 Message: Logged In: YES user_id=463096 Here's an alternative patch that exploits the database metadata to check if case conversion is needed for identifiers. However, I agree that this is really a bug in the Oracle implementation of 'getTables'. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-533686 ] JDBCStartCommand.tableExists() Oracle
Bugs item #533686, was opened at 2002-03-23 04:26 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Levart (plevart) Assigned to: Dain Sundstrom (dsundstrom) Summary: JDBCStartCommand.tableExists() Oracle Initial Comment: This is not realy a bug, rather a workarround for a peculiarity of the Oracle DB using thin JDBC driver. When deploying Entity Beans on Oracle (using thin driver - I haven't tried with the full blown native version), the JDBCStartCommand.tableExists() incorrectly returns false when the table already exists and deployment later fails when JBoss is trying to create the table. The problem is that table names in Oracle DB seem to be UPPER CASE ONLY. But the java.sql.DatabaseMetadata.getTables() that is used in JDBCStartCommand.tableExists() to check for the existense of a particular table, uses a tableNamePattern that performs a case-sensitive search. So if you specify the table name as SomeBean then the actual table created on the 1st deployment would be SOMEBEAN and later deployments will fail. One workarround is to simply use UPPER CASE ONLY names for tables when deploying on Oracle, the other would be for JDBCStartCommand.tableExists() to check for the existence of table with exact given name and for a table with an UPPER CASE NAME. I'm including the later as a patch attached to the bug report... -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 14:10 Message: Logged In: YES user_id=463096 Doh! There doesn't seem to be a way to attach files in followups. I know this is not ideal: Index: JDBCStartCommand.java === RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/ plugins/cmp/jdbc/JDBCStartCommand.java,v retrieving revision 1.22 diff -r1.22 JDBCStartCommand.java 193c193,198 rs = dmd.getTables(con.getCatalog(), null, tableName, null); --- String physicalTableName = tableName; if (dmd.storesUpperCaseIdentifiers()) physicalTableName = tableName.toUpperCase(); else if (dmd.storesLowerCaseIdentifiers()) physicalTableName = tableName.toLowerCase(); rs = dmd.getTables(con.getCatalog(), null, physicalTableName, null); -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 13:59 Message: Logged In: YES user_id=463096 Here's an alternative patch that exploits the database metadata to check if case conversion is needed for identifiers. However, I agree that this is really a bug in the Oracle implementation of 'getTables'. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 566 Successful tests: 539 Errors:20 Failures: 7 [time of test: 7 April 2002 5:25 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 549 Errors:19 Failures: 7 [time of test: 7 April 2002 6:24 GMT] [java.version: 1.3.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_02-b02] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Should we add .sar to cvswrappers?
Why would a .sar ever be checked in? I can add, but why? --jason Quoting David Jencks [EMAIL PROTECTED]: I'm a little nervous about messing with cvs settings or I'd do it. thanks david jencks - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss 3 users -- warning of impending configuration change
Can we change the name of this to hsql-service.xml? --jason Quoting David Jencks [EMAIL PROTECTED]: On March 25 I committed a new ConnectionManager implementation to JBoss 3 cvs. There do not seem to be many serious problems, so I will remove the old implementation shortly. THIS WILL COMPLETELY BREAK ALL PREVIOUS db-service.xml FILES!!! So far we have examples configuration for firebird, hypersonic, and postgres. They are located in a NEW LOCATION! connector/src/etc/example-config (hypersonic is in new-hsql-default-service.xml) PLEASE CONTRIBUTE YOUR NEW WORKING CONFIGURATIONS! Documentation for the new mbeans is generated by the new jmx documentation system. Run connector/build.sh jmx-docs-html-plain or build/build.sh all and look in the jmx-api directory. You can probably also simply look at the 3 existing examples and change the few properties necessary. Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 7-April-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 219 Errors:315 Failures: 10 [time of test: 7 April 2002 7:30 GMT] [java.version: 1.4.0] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.0-b92] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-533686 ] JDBCStartCommand.tableExists() Oracle
Bugs item #533686, was opened at 2002-03-23 04:26 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Levart (plevart) Assigned to: Dain Sundstrom (dsundstrom) Summary: JDBCStartCommand.tableExists() Oracle Initial Comment: This is not realy a bug, rather a workarround for a peculiarity of the Oracle DB using thin JDBC driver. When deploying Entity Beans on Oracle (using thin driver - I haven't tried with the full blown native version), the JDBCStartCommand.tableExists() incorrectly returns false when the table already exists and deployment later fails when JBoss is trying to create the table. The problem is that table names in Oracle DB seem to be UPPER CASE ONLY. But the java.sql.DatabaseMetadata.getTables() that is used in JDBCStartCommand.tableExists() to check for the existense of a particular table, uses a tableNamePattern that performs a case-sensitive search. So if you specify the table name as SomeBean then the actual table created on the 1st deployment would be SOMEBEAN and later deployments will fail. One workarround is to simply use UPPER CASE ONLY names for tables when deploying on Oracle, the other would be for JDBCStartCommand.tableExists() to check for the existence of table with exact given name and for a table with an UPPER CASE NAME. I'm including the later as a patch attached to the bug report... -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 17:28 Message: Logged In: YES user_id=463096 I retract my comment about this being an Oracle bug. Oracle in fact allows mixed-case table name identifiers. It is possible to have three different tables: TEST Test test I believe that the correct solution is to always bracket table names with the result of DatabaseMetaData.getIdentifierQuoteString(). ie. we then use queries such as: create table test (id NUMBER) and select id from test Databases that don't support quoted identifiers are supposed to return a space from the getIdentifierQuoteString call. According to the docs for getIdentifierQuoteString, a JDBC Compliant driver always uses a double quote character. -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 14:10 Message: Logged In: YES user_id=463096 Doh! There doesn't seem to be a way to attach files in followups. I know this is not ideal: Index: JDBCStartCommand.java === RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/ plugins/cmp/jdbc/JDBCStartCommand.java,v retrieving revision 1.22 diff -r1.22 JDBCStartCommand.java 193c193,198 rs = dmd.getTables(con.getCatalog(), null, tableName, null); --- String physicalTableName = tableName; if (dmd.storesUpperCaseIdentifiers()) physicalTableName = tableName.toUpperCase(); else if (dmd.storesLowerCaseIdentifiers()) physicalTableName = tableName.toLowerCase(); rs = dmd.getTables(con.getCatalog(), null, physicalTableName, null); -- Comment By: Stephen Coy (scoy) Date: 2002-04-07 13:59 Message: Logged In: YES user_id=463096 Here's an alternative patch that exploits the database metadata to check if case conversion is needed for identifiers. However, I agree that this is really a bug in the Oracle implementation of 'getTables'. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=533686group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Patched HSQLDB sources?
They are looking at supporting embedded using our patch - they may go another road and/or just be inspired by what We used ... they do want to have something supporting embedded ... how and when I do not know ... Hopefully they will find a solution soon. If one uses ones own ServerSocket and connection threads that use the hsqldb.Database class directly - then We do not need to touch the hsqldb code and have more controll over the listeners in JBoss ... this is how the Avalon project has solved there embedded hsqldb. Does it make sence to implement this now, incase the method the hsqldb folks decide on isn't enough... or takes too long? Do you understand how to implement this? If so and it makes sence to add, then lets do it. It will make this more maintainable. --jason - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/etc/example-config postgres-service.xml firebird-service.xml
User: d_jencks Date: 02/04/06 19:35:10 Added: src/etc/example-config postgres-service.xml firebird-service.xml Log: configuration examples for the new ConnectionManager Revision ChangesPath 1.1 jbosscx/src/etc/example-config/postgres-service.xml Index: postgres-service.xml === ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- !-- -- !-- = -- server !-- -- !-- New ConnectionManager setup for default PostgreSQL dbs -- !-- Build jmx-api (build/build.sh all) and view for config documentation -- !-- -- mbean code=org.jboss.resource.connectionmanager.LocalTxConnectionManager name=jboss.jca:service=LocalTxCM !--make the rar deploy! hack till better deployment-- dependsjboss.jca:service=RARDeployer/depends depends optional-attribute-name=ManagedConnectionFactoryName !--embedded mbean-- mbean code=org.jboss.resource.connectionmanager.RARDeployment name=jboss.jca:service=LocalTxDS !--hack-- depends optional-attribute-name=OldRarDeploymentjboss.jca:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/depends !--real attributes-- attribute name=ManagedConnectionFactoryProperties properties config-property config-property-nameConnectionURL/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuejdbc:postgresql:bonneville/config-property-value /config-property config-property config-property-nameDriverClass/config-property-name config-property-typejava.lang.String/config-property-type config-property-valueorg.postgresql.Driver/config-property-value /config-property config-property config-property-nameUserName/config-property-name config-property-typejava.lang.String/config-property-type config-property-valueAdministrator/config-property-value /config-property config-property config-property-namePassword/config-property-name config-property-typejava.lang.String/config-property-type config-property-value/config-property-value /config-property /properties /attribute attribute name=JndiNameDefaultDS/attribute /mbean depends optional-attribute-name=ManagedConnectionPool !--embedded mbean-- mbean code=org.jboss.resource.connectionmanager.JBossManagedConnectionPool name=jboss.jca:service=LocalTxPool attribute name=MinSize0/attribute attribute name=MaxSize50/attribute attribute name=BlockingTimeoutMillis5000/attribute attribute name=IdleTimeoutMinutes15/attribute !--criteria indicates if Subject (from security domain) or app supplied parameters (such as from getConnection(user, pw)) are used to distinguish connections in the pool. Choices are ByContainerAndApplication (use both), ByContainer (use Subject), ByApplication (use app supplied params only), ByNothing (all connections are equivalent, usually if adapter supports reauthentication)-- attribute name=CriteriaByContainer/attribute /mbean /depends depends optional-attribute-name=CachedConnectionManagerjboss.jca:service=CachedConnectionManager/depends attribute name=SecurityDomainJndiNamejava:/jaas/DefaultDbRealm/attribute attribute name=TransactionManagerjava:/TransactionManager/attribute /mbean /server 1.1 jbosscx/src/etc/example-config/firebird-service.xml Index: firebird-service.xml === ?xml version=1.0 encoding=UTF-8? !-- -- !-- New ConnectionManager setup for firebird dbs using jca-jdbc xa driver-- !-- Build jmx-api (build/build.sh all) and view for config documentation -- !-- -- service
[JBoss-dev] CVS update: jbosscx build.xml
User: d_jencks
Date: 02/04/06 18:59:30
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.35 +48 -3 jbosscx/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosscx/build.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- build.xml 24 Mar 2002 21:44:31 - 1.34
+++ build.xml 7 Apr 2002 02:59:30 - 1.35
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.34 2002/03/24 21:44:31 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.35 2002/04/07 02:59:30 d_jencks Exp $ --
project default=main name=JBoss/Connector
@@ -203,11 +203,16 @@
property name=build.classes value=${module.output}/classes/
property name=build.lib value=${module.output}/lib/
property name=build.api value=${module.output}/api/
+property name=build.jmx-api value=${module.output}/jmx-api/
property name=build.etc value=${module.output}/etc/
property name=build.resources value=${module.output}/resources/
+property name=build.stylesheets value=${module.output}/stylesheets/
+
+property name=tools.stylesheets value=${project.tools}/etc/stylesheets/
!--xdoclet output directories--
property name=build.gen-src value=${module.output}/gen-src//
+property name=build.jmx-doc value=${module.output}/jmx-doc//
!-- Install/Release structure --
property name=install.id value=${module.name}-${module.version}/
@@ -250,6 +255,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
@@ -257,7 +263,6 @@
/target
-
!-- == --
!-- Compile--
!-- == --
@@ -444,7 +449,7 @@
| different type of docuementation that is to be generated.
--
- target name=docs depends=init, docs-api
+ target name=docs depends=init, docs-api, jmx-docs-html-plain
description=Builds all documentation.
/target
@@ -490,6 +495,46 @@
/target
target name=javadocs depends=docs-javadocs/
+
+ target name=jmx-docs depends=init
+taskdef name=jmxdoclet classname=xdoclet.jmx.JMXDocletTask/
+
+mkdir dir=${build.jmx-doc}/
+jmxdoclet
+ destdir=${build.jmx-doc}
+ classpath=${xdoclet.task.classpath}
+ force=false
+ excludedtags=@version,@author
+ fileset dir=${source.java}
+include name=**/*.java/
+ /fileset
+ jbossXmlDoc/
+/jmxdoclet
+
+ /target
+
+ !-- Generate the plain HTML jmx docs --
+ target name=jmx-docs-html-plain depends=jmx-docs
+
+
+!-- Force the use of SAXON XSLT --
+property system=true
+ name=javax.xml.transform.TransformerFactory
+ value=com.icl.saxon.TransformerFactoryImpl/
+
+mkdir dir=${build.jmx-api}/
+style style=${project.thirdparty}/oasis/docbook-xsl/html/docbook.xsl
+processor=trax
+extension=.html
+basedir=${build.jmx-doc}
+destdir=${build.jmx-api}
+ include name=**/*.xml/
+ param name=quiet expression=${oasis.docbook.xsl.chunker.quiet}/
+ param name=base.dir expression=${build.jmx-api}${file.separator}/
+/style
+
+ /target
+
!-- == --
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty build.xml
User: d_jencks
Date: 02/04/06 18:59:31
Modified:jettybuild.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.49 +1 -0 contrib/jetty/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/jetty/build.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- build.xml 30 Mar 2002 02:20:42 - 1.48
+++ build.xml 7 Apr 2002 02:59:31 - 1.49
@@ -265,6 +265,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx build.xml
User: d_jencks
Date: 02/04/06 18:59:31
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.31 +2 -1 jmx/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jmx/build.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- build.xml 23 Mar 2002 21:11:01 - 1.30
+++ build.xml 7 Apr 2002 02:59:31 - 1.31
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.30 2002/03/23 21:11:01 ejort Exp $ --
+!-- $Id: build.xml,v 1.31 2002/04/07 02:59:31 d_jencks Exp $ --
project default=main name=JBoss/JMX
@@ -204,6 +204,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/jmx/test DeployServiceUnitTestCase.java
User: d_jencks Date: 02/04/06 21:25:59 Modified:src/main/org/jboss/test/jmx/test DeployServiceUnitTestCase.java Log: updated to new mbeans used in test Revision ChangesPath 1.13 +2 -2 jbosstest/src/main/org/jboss/test/jmx/test/DeployServiceUnitTestCase.java Index: DeployServiceUnitTestCase.java === RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/jmx/test/DeployServiceUnitTestCase.java,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- DeployServiceUnitTestCase.java24 Mar 2002 05:35:01 - 1.12 +++ DeployServiceUnitTestCase.java7 Apr 2002 05:25:59 - 1.13 @@ -31,7 +31,7 @@ /** * @see related * @authora href=mailto:[EMAIL PROTECTED];David Jencks/a - * @version $Revision: 1.12 $ + * @version $Revision: 1.13 $ */ public class DeployServiceUnitTestCase extends JBossTestCase @@ -92,7 +92,7 @@ String testUrl = url.toString(); //the mbeans we are trying to deploy/undeploy - ObjectName testObjectName = new ObjectName(TestDomain:service=ConnectionFactoryLoader,name=DeployTestDS); + ObjectName testObjectName = new ObjectName(jboss.test:service=LocalTxCM); //check they aren't there already //Well, lets try to kill it. if (getServer().isRegistered(testObjectName)) ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] xjavadoc I love you
It is so fast... I wonder what else we can use xdoclet/xjavadoc for... --jason _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12304 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/examples/org/jboss/docs/cmp/cd Upload.java
User: user57
Date: 02/04/06 23:44:10
Modified:src/examples/org/jboss/docs/cmp/cd Upload.java
Log:
o CDs.txt - cds.txt
Revision ChangesPath
3.1 +14 -17manual/src/examples/org/jboss/docs/cmp/cd/Upload.java
Index: Upload.java
===
RCS file: /cvsroot/jboss/manual/src/examples/org/jboss/docs/cmp/cd/Upload.java,v
retrieving revision 3.0
retrieving revision 3.1
diff -u -r3.0 -r3.1
--- Upload.java 18 Nov 2001 20:10:44 - 3.0
+++ Upload.java 7 Apr 2002 07:44:10 - 3.1
@@ -30,23 +30,20 @@
* Run the upload process from the command line.
*/
public static void main(String[] args)
- {
-String filename = CDs.txt;
-
- try
- {
-uploadFile (filename);
- }
-catch (java.io.IOException e)
- {
-System.err.println (Upload: can't read file ` + filename + ');
- }
-catch(Exception e)
- {
-System.err.println(Upload: + e.toString());
- }
-System.out.println (OK);
- }
+ {
+ String filename = cds.txt;
+
+ try {
+ uploadFile (filename);
+ }
+ catch (java.io.IOException e) {
+ System.err.println (Upload: can't read file ` + filename + ');
+ }
+ catch(Exception e) {
+ System.err.println(Upload: + e.toString());
+ }
+ System.out.println (OK);
+ }
/**
* This method uploads a database of CDs specified as a text file. The file
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/common doco.jsp
User: user57 Date: 02/04/06 23:45:41 Modified:src/docs/common doco.jsp Log: o you - your Revision ChangesPath 1.18 +1 -1 newsite/src/docs/common/doco.jsp Index: doco.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/common/doco.jsp,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- doco.jsp 31 Dec 2001 06:57:09 - 1.17 +++ doco.jsp 7 Apr 2002 07:45:41 - 1.18 @@ -32,7 +32,7 @@ Managed Relationships, ejbSelect methods, and ejb-ql support. The manual introduces you to each feature in detail and its configuration, and guides you through the process of specifying the database mapping of container managed fields, relationships and queries. Example code is included throughout the text. -This is you chance to purchase the official documentation package written by the feature's developer, +This is your chance to purchase the official documentation package written by the feature's developer, Dain Sundstrom. This material is not available in the free documentation or the $9.99 base documentation. a class=link href=http://www.flashline.com/components/productsbyvendor.jsp?vendorid=1376affiliateid=260343;Buy Now/a. /p ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-management build.xml
User: d_jencks
Date: 02/04/06 18:59:31
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.6 +2 -1 jboss-management/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss-management/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 24 Mar 2002 02:25:04 - 1.5
+++ build.xml 7 Apr 2002 02:59:31 - 1.6
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.5 2002/03/24 02:25:04 schaefera Exp $ --
+!-- $Id: build.xml,v 1.6 2002/04/07 02:59:31 d_jencks Exp $ --
project default=main name=JBoss/Management
@@ -195,6 +195,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq build.xml
User: d_jencks
Date: 02/04/06 18:59:32
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.29 +2 -1 jbossmq/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbossmq/build.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- build.xml 4 Apr 2002 04:35:06 - 1.28
+++ build.xml 7 Apr 2002 02:59:32 - 1.29
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.28 2002/04/04 04:35:06 user57 Exp $ --
+!-- $Id: build.xml,v 1.29 2002/04/07 02:59:32 d_jencks Exp $ --
project default=main name=JBoss/Messaging
@@ -268,6 +268,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
