[JBoss-user] Preventing CMP deploy-time CREATE TABLE
Hi, I have a CMP entity bean that I plan to use against an existing table. How can it be deployed without issuing a corresponding CREATE TABLE statement? I found docs suggesting that I should have this in my standardjaws.xml: default-entity ... create-tablefalse/create-table ... /default-entity I added this, but it doesn't seem to prevent the statement from being fired. Something else I should be doing? Thanks, Jason -- ~ Jason Wells Semantic Research Inc. [EMAIL PROTECTED] ~ --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Preventing CMP deploy-time CREATE TABLE
I happen to be using JBoss 3.2.1, and it's a CMP 2.0 entity bean. After I sent the email I downloaded and began paging through the O'Reilly JBoss 3.2 Workbook, and learned that I should have set that value in the standardjbosscmp-jdbc.xml file instead. Once I did that it worked like a charm. BTW, that workbook is excellent, it's the clearest book on JBoss I've yet seen. Kudos to the authors. Jason On Friday, June 13, 2003, at 10:47 AM, Dayanand Kangala Shanmugham wrote: Hi, If you are using Jboss 3.0.3, try having the following statements in jbosscmp-jdbc.xml : defaults ... create-tablefalse/create-table ... /defaults Regards, Dayanand. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Wells Sent: Friday, June 13, 2003 10:56 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] Preventing CMP deploy-time CREATE TABLE Hi, I have a CMP entity bean that I plan to use against an existing table. How can it be deployed without issuing a corresponding CREATE TABLE statement? I found docs suggesting that I should have this in my standardjaws.xml: default-entity ... create-tablefalse/create-table ... /default-entity I added this, but it doesn't seem to prevent the statement from being fired. Something else I should be doing? Thanks, Jason -- ~ Jason Wells Semantic Research Inc. [EMAIL PROTECTED] ~ --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- ~ Jason Wells Semantic Research Inc. [EMAIL PROTECTED] ~ --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Pointbase setup in JBoss 2.4
Hi, I'm trying to get JBoss 2.4.4 to use Pointbase Embedded 4.1 as a datasource. Does anyone have a sample for the XML I should include in jboss.jcml? Thanks, Jason -- ~ Jason Wells [EMAIL PROTECTED] The highest moral imperative ICQ: 3241233 is artistic necessity. ~ ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JDBC config question...
Hello, I'm upgrading from JBoss PRE-2.1 to 2.3 beta. Things were going surprisingly well until I hit this snag. For some reason, my original jboss.jcml configuration for Sybase no longer works. I'm using the JConnect JDBC drivers. This is what I added to/modified in the 2.3 jboss.jcml: mbean code=org.jboss.jdbc.JdbcProvider name=DefaultDomain:service=JdbcProvider attribute name=Driversorg.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.idbDriver,com. sybase.jdbc2.jdbc.SybDriver/attribute /mbean mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=SybasePool attribute name=PoolNameSybasePool/attribute attribute name=DataSourceClassorg.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl/attr ibute attribute name=URLjdbc:sybase:Tds:server:7100?ELIMINAT_010SM=true/attribute attribute name=JDBCUserusername/attribute attribute name=Passwordpassword/attribute attribute name=MinSize0/attribute attribute name=MaxSize10/attribute attribute name=GCEnabledfalse/attribute attribute name=GCMinIdleTime120/attribute attribute name=GCInterval12/attribute attribute name=InvalidateOnErrorfalse/attribute attribute name=TimestampUsedfalse/attribute attribute name=Blockingtrue/attribute attribute name=LoggingEnabledfalse/attribute attribute name=IdleTimeoutEnabledfalse/attribute attribute name=IdleTimeout180/attribute attribute name=MaxIdleTimeoutPercent1.0/attribute /mbean This code works fine in the PRE-2.1 release, but in 2.3 I see this in the startup sequence: [JDBC provider] could not load driver:com.sybase.jdbc2.jdbc.SybDriver Later on, it freezes when it gets to creating the connection pool: . . . [SybasePool] Starting [SybasePool] XA Connection pool SybasePool bound to java:/SybasePool (freeze) Thanks in advance, I appreciate any help. -- Jason Wells Web Architect Xsilogy, Inc. http://www.xsilogy.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] SQL query tracing -- how?
Hello, I'm running JBoss 2.1, and I need to turn on SQL tracing so that I can debug a BMP entity bean I'm working on. I'm trying to get my server.log to give me output like this: ... [JAWS] Exists SQL: SELECT COUNT(*) FROM UnitStatus WHERE id=? [JAWS] findAllStatus SQL: SELECT id FROM UnitStatus [JAWS] Create SQL: INSERT INTO UnitStatus (priority,speed,heading,lat) VALUES (?,?,?,?) [JAWS] Remove SQL: DELETE FROM UnitStatus WHERE id=? ... I found no mention of debug in the JBoss docs, but when I searched through the list archive I actually found what appeared to be the answer. It said: add debugtrue/debug to your jaws.xml, at the 'top' level (within the jaws tag, but not in any other. Also, make sure that you're allowing debug level logs to be output. The first part is clear enough, and I took the last part of the instructions (allow debug level logs to be output) to mean that for my database connection pool in jboss.jcml, set the LoggingEnabled attribute to true. Which I did. However, I don't get any SQL statements in either the JBoss console output or in server.log. I assume that I misunderstand the last part. What am I doing wrong? Thanks in advance. -- Jason Wells Web Architect Xsilogy, Inc. http://www.xsilogy.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] CMP finder method problem
I turned all this on, and although I do get additional debug printing from the datasource connection pool, I still get no SQL statements in either the console output or in server.log. Any other ideas? - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 11, 2001 1:07 AM Subject: RE: [JBoss-user] CMP finder method problem I could get to the bottom of this if I could just see what the container is doing when the findAll() is triggered. My question is: is there a way to print or log the SQL SELECT statement that the container has executed on my entity bean's behalf? If not, can anyone suggest a good way to debug something like this? Yes, you can (there are few places where you can turn logging on and off): jaws.xml or standardjaws.xml and specify: jaws ... debugtrue/debug ... /jaws jboss.xml or standardjboss.xml in you CMP container configuration: !-- prints the method invoked by container -- call-loggingtrue/call-logging in jboss.jcml in your datasource configuration: mbean ... ... attribute name=LoggingEnabledtrue/attribute /mbean Also, do not forget to watch the server.log, not the console output, because SQL statements appear only in server log (at least in my case). Roman ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] CMP finder method problem
Yeah, I know, I'm surprised too, but the SQL statments definitely don't show up anywhere in the server log or the console output. I've gone through it all very thoroughly. Some SQL must be being generated, since one of the entity beans works fine. Yet none of it shows up in the debug. Is there any other debug I can turn on, other than what I've already done: - Adding debugtrue/debug to jaws.xml - Adding debugtrue/debug to standardjaws.xml - Setting call-loggingtrue/call-logging in standardjboss.xml (under Standard CMP EntityBean, which is what I've written) - Setting attribute name=LoggingEnabledtrue/attribute for the connection pool I'm using Did I miss anything? Thanks, Jason - Original Message - From: K.V. Vinay Menon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 11, 2001 2:35 PM Subject: Re: [JBoss-user] CMP finder method problem Jason, The sql statements should appear at server start up in the server log if you set debug to true in the standardjaws file. They will come be logged just after the beans are deployed. Am surprised that it is not showing up. Is there any sql at all being generated? Vinay - Original Message - From: Jason Wells [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 11, 2001 9:11 PM Subject: Re: [JBoss-user] CMP finder method problem I turned all this on, and although I do get additional debug printing from the datasource connection pool, I still get no SQL statements in either the console output or in server.log. Any other ideas? - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 11, 2001 1:07 AM Subject: RE: [JBoss-user] CMP finder method problem I could get to the bottom of this if I could just see what the container is doing when the findAll() is triggered. My question is: is there a way to print or log the SQL SELECT statement that the container has executed on my entity bean's behalf? If not, can anyone suggest a good way to debug something like this? Yes, you can (there are few places where you can turn logging on and off): jaws.xml or standardjaws.xml and specify: jaws ... debugtrue/debug ... /jaws jboss.xml or standardjboss.xml in you CMP container configuration: !-- prints the method invoked by container -- call-loggingtrue/call-logging in jboss.jcml in your datasource configuration: mbean ... ... attribute name=LoggingEnabledtrue/attribute /mbean Also, do not forget to watch the server.log, not the console output, because SQL statements appear only in server log (at least in my case). Roman ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JDBC Sybase configuration?
Hello, I'm trying to get JBoss to use the Sybase JConnect 5.2 JDBC driver for CMP entity beans. I've been looking at the Using MS SQL Server with JBoss tutorial on the JBoss site, which is the closest thing I've found in terms of relevant documentation: http://www.jboss.org/documentation/HTML/ch11s17.html And actually, it seems pretty applicable. But there's one area where the instructions aren't too useful, because they vary considerably from driver to driver, and that's the connection pool MBean declaration. I'm thinking it would look something like this... mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=SQLServerPool attribute name=DataSourceClasscom.sybase.jdbcx.SybDataSource/attribute attribute name=PoolNameSybasePool/attribute attribute name=URL???/attribute attribute name=Propertiesuser=dbusername; password=dbpassword/attribute attribute name=MinSize4/attribute attribute name=MaxSize10/attribute attribute name=GCEnabledfalse/attribute attribute name=GCMinIdleTime120/attribute attribute name=GCInterval12/attribute attribute name=InvalidateOnErrorfalse/attribute attribute name=TimestampUsedfalse/attribute attribute name=Blockingtrue/attribute attribute name=LoggingEnabledfalse/attribute attribute name=IdleTimeoutEnabledfalse/attribute attribute name=IdleTimeout180/attribute attribute name=MaxIdleTimeoutPercent1.0/attribute /mbean But, I have no idea how to formulate the JDBC URL, or if it's even needed. Also, I wonder if I need JDBCUser and Password attributes. All of these things seem to vary from driver to driver. Has anyone set this up for the Sybase JDBC driver? Any help is appreciated. Thanks, Jason ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] EAR deployment with Jboss/Tomcat
Hello, A basic question... I'm trying to deploy a very simple servlet that calls a very simple stateless session bean. Our configuration has Apache integrated with Tomcat/Jboss (embedded). I've been following these instructions: http://www.jboss.org/business/jboss-tomcat.html I have a web archive (ejbHello.war) containing a servlet called ejbHelloServlet. This servlet uses a stateless session bean called ejbHello, which is in a JAR called ejbHello.jar. These have been combined into an EAR called ejbHello.ear. The application.xml file in the EAR sets the context root as /ejbHello. The EAR is deployed in the Jboss /deploy directory. Which is great, except that when I visit the URL, which I believe (according to the instructions) should be http://localhost:8082/ejbHello, I get a 404. What am I doing wrong here? One area that makes me suspicious is at the end of the instructions, where it says "for your application to be visible through Apache, you must setup the appropriate JkMount statements in mod_jk.conf." However, it doesn't mention what the 'appropriate statements' are. Any help is appreciated... thanks in advance. -- Jason Wells Web Architect Xsilogy, Inc. http://www.xsilogy.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Basic jsp -- ejb example for Jboss?
Hello, I'm new to the EJB world and I'm trying to find a "hello world" level explanation/tutorial that walks through creating a very basic web application (using Jboss) that accesses EJB services from within a JSP or servlet. When I looked through the online Jboss docs, I found a tutorial which suggests that you download example code... but when I tried, I repeatedly got a 404. I've also dug through the listserv archive, and found nothing that seemed especially germane to this problem. I've also rifled through the java.sun.com/jGuru J2EE tutorials, but they seem to rely on vendor-specific tools for crucial parts of the code deployment procedure. (Since their example was based on Weblogic, it isn't very useful in the Jboss world.) I'm not sure where else to turn. This seems like a problem anyone would have to get through in order to create a web application using Jboss. Surely there must be some kind of resource (at least a mini-howto, or something!) just to help people get started. My configuration is Apache/Tomcat/Jboss running on RH6.2. Any help is appreciated. Thanks in advance. -- Jason Wells Web Architect Xsilogy, Inc. http://www.xsilogy.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
