[Javassist Development] New message: "Re: ScopedClassPoolRepositoryImpl and default ClassPool"
by Flavia Rainone
User development,
A new message was posted in the thread "ScopedClassPoolRepositoryImpl and default ClassPool":
http://community.jboss.org/message/528638#528638
Author : Flavia Rainone
Profile : http://community.jboss.org/people/flavia.rainone@jboss.com
Message:
--------------------------------------------------------------
> mailto:flavia.rainone@jboss.com wrote:
>
> I'm calling that new module scoped-classpool. Once it is ready, we can decide whether it would be a good idea to use those changes as a patch for Javassist, or whether we wanna keep it the way it is.
That new module is created. I removed everything that I thought is no longer being used, and replaced all references to javassist.scopedpool classes by references to the new org.jboss.classpool.scoped classes.
A summary of what has been done can be obtained by looking at the svn history log:
- Copied Scoped ClassPool classes from Javassist to a new scopedpool module.
- ScopedCPRepository is no longer singleton, it is an abstract class with a protected constructor instead. The default class pool can be defined as a parameter of the constructor.
- Replaced all references to javassist.scopedpool package by org.jboss.classpool.scoped package.
- Deleted ScopedClassPoolFactoryImpl class
Now I'm open for suggestions on what should be the next step: to write a patch for Javassist; to do an alpha release of the new version and update depending projects (JBoss AOP and JBoss Reflection, besides deployers-vfs tests); or to do more refactoring and improve something that doesn't look ok.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528638#528638
16 years, 1 month
[Performance Tuning] New message: "JBoss Request Queue Size"
by Santhosh Kumar
User development,
A new message was posted in the thread "JBoss Request Queue Size":
http://community.jboss.org/message/528636#528636
Author : Santhosh Kumar
Profile : http://community.jboss.org/people/brsanthu
Message:
--------------------------------------------------------------
In the Jboss server we can configure the max number of requests Jboss should keep in the buffer if all threads are busy as acceptCount in the jboss.web.connector related mbean. I'm looking to find the dynamic/runtime queue size so I can understand how many requests were waiting any any point in time to tune the thread pool.
I looked around in the JMX and WebConsole but didn't find this size anywhere. Do you have any idea about this?
Any help is appreciated.
Thanks,
Santhosh.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528636#528636
16 years, 1 month
[JBoss Tools] New message: "Re: classloader cant find groovy files in ejb project.. any ideas?"
by William Woodman
User development,
A new message was posted in the thread "classloader cant find groovy files in ejb project.. any ideas?":
http://community.jboss.org/message/528634#528634
Author : William Woodman
Profile : http://community.jboss.org/people/wiggy
Message:
--------------------------------------------------------------
denis - thanks for responding however its still not working
I found that the server config in properties was set to workspace default and not the server deploy directory - not sure what that was doing. However i have shifted the deploy output to goto the server/default/deploy directory.
and republished. I can now see my project on the server in the exploded ear. and my groovy class is right there alongside the class file from the java class. however when i run the app server i still get the error (this is the end of the error message trail)
If i read this it suggests that the BaseClassLoader cant see the Person class. Well its there i've checked so why does it find the Node class (generated from java class file) but not the Person.class file in the same directory genderated from groovy?
I checked the source tab in the projects directory and it shows
http://community.jboss.org/servlet/JiveServlet/showImage/2169/eclipse+scr...
error from deployment shows
DEPLOYMENTS IN ERROR:
Deployment "persistence.unit:unitName=forstersList-ear.ear/forstersList-ejb.jar#forstersList" is in error due to the following reason(s):
java.lang.ClassNotFoundException: org.domain.forsterslist.entity.Person from BaseClassLoader@8c2d23{VFSClassLoaderPolicy@e776f7{name=vfsfile:/C:/jboss/jboss-5.1.0.GA/server/default/conf/jboss-service.xml
what else am i missing here?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528634#528634
16 years, 1 month
[EJB 3.0] New message: "PersistanceManager confusion"
by mohamed shaftri
User development,
A new message was posted in the thread "PersistanceManager confusion":
http://community.jboss.org/message/528624#528624
Author : mohamed shaftri
Profile : http://community.jboss.org/people/shaftri
Message:
--------------------------------------------------------------
Hello
I try to do my small project EJB3 persisting a detatched pojo entity (which is generated in a client) through a stateless session bean.
I´ll attach the code of the three components at the end of the message.
When I invoke the the method, that should persist the entity I get the following exception:
prepare:
compile:
ejbjar:
run.client:
[java] Exception in thread "main" javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.PersistentObjectException: detached entity passed to persist: com.ck.domain.Borrower
[java] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
[java] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
[java] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
[java] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
[java] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
[java] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
[java] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
[java] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
[java] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
[java] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
[java] Caused by: javax.persistence.PersistenceException: org.hibernate.PersistentObjectException: detached entity passed to persist: com.ck.domain.Borrower
[java] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:629)
[java] at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:218)
[java] at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
[java] at com.ck.library.BrSlLibrary.createBrrower(BrSlLibrary.java:17)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
[java] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
[java] at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
[java] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
[java] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
[java] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
[java] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
[java] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
[java] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
[java] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
[java] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
[java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
[java] at org.jboss.remoting.Client.invoke(Client.java:1634)
[java] at org.jboss.remoting.Client.invoke(Client.java:548)
[java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
[java] at $Proxy0.createBrrower(Unknown Source)
[java] at com.ck.clients.Client.main(Client.java:35)
[java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
[java] at $Proxy0.createBrrower(Unknown Source)
[java] at com.ck.clients.Client.main(Client.java:35)
[java] Caused by: org.hibernate.PersistentObjectException: detached entity passed to persist: com.ck.domain.Borrower
[java] at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:79)
[java] at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38)
[java] at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:618)
[java] at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:592)
[java] at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:596)
[java] at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:212)
[java] at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
[java] at com.ck.library.BrSlLibrary.createBrrower(BrSlLibrary.java:17)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
[java] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
[java] at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
[java] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
[java] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
[java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
[java] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
[java] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
[java] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
[java] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
[java] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
[java] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
[java] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
[java] Java Result: 1
this is my entityborrower beans
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528624#528624
16 years, 1 month
[JBoss Tools] New message: "Re: JBossTools-3.0.3.GA On Eclipse Ganymede"
by Denis Golovin
User development,
A new message was posted in the thread "JBossTools-3.0.3.GA On Eclipse Ganymede":
http://community.jboss.org/message/528622#528622
Author : Denis Golovin
Profile : http://community.jboss.org/people/dgolovin
Message:
--------------------------------------------------------------
You have several http://hsqldb.org/web/hsqlDocsFrame.htmlhttp://hsqldb.org/web/hsqlDocsFra.... I would chouse from couple described below:
1. In process - by pointing out to local folder during creating DTP Connection Profile
2. Server - by starting it outside eclipse using command line and then create DTP Connection Profile with local server
h2. In Process Option
If you use "in process" option you have to be aware that it is not enough just point out folder where your database is located in connection properties. You have to add one more segment to it with database name or your DB will be empty (see explanation below).
For example you have HSQL DB somewhere on disk with name "employee". Im my case I have it downloaded from https://svn.jboss.org/repos/jbosstools/trunk/documentation/development/us... and just moved all files to local directory /home/eskimo/db/employee. So I have in this folder structure showed below (ignore employee.lck file it will be created after first "In process" start and not needed initially)
http://community.jboss.org/servlet/JiveServlet/showImage/2156/hsql-db-str...
I assume you you have the same but you need to correct all paths "/home/eskimo/db/employee" and database name "employee" with yours real values.
Then you created "Database Connection" in DTP "Data Source Explorer" View by selecting "New..." from context menu on "Database Connections" node
http://community.jboss.org/servlet/JiveServlet/showImage/2157/hsql-new-co...
Then select "HSQLDB" connection type and enter DB name as "employee"
http://community.jboss.org/servlet/JiveServlet/showImage/2158/hsql-new-co...
Then I assume you already have configured HSQL JDBC Driver and all what you need to is enter database name again as "employee" and select its location. After that one magic step is needed (it could be DTP issue). Add one more segment in "Database Location" like "/employee" like it shown below. Do not forget clear "Connect when wizard completes" checkbox because it will start In Process HSQL after wizard is finished and create employee.lck file in your database folder. This file will be the reason Seam why Seam Entity Generation wizard will fail during execution.
http://community.jboss.org/servlet/JiveServlet/showImage/2159/hsql-new-co...
Press Finish and check that employee node created under "Database Connections".
Now you're ready to create Seam Web project using "New Seam Web Project" wizard like it shown below (it shows only first and last steps because all other steps I left unchanged with default values).
http://community.jboss.org/servlet/JiveServlet/showImage/2160/seam-new-1.png
Then comes screens I left unchanged and finally you get to last one with seam configuration. You should have seam 2.1 configured and all what you need is to fill Database properties like it shown below and press "Finish".
http://community.jboss.org/servlet/JiveServlet/showImage/2161/seam-new-2.png
After wizard is finished you should see two projects prj1 and prj1-test in your workspace. Now to be ready for entities reverse engineering from your database you need to be sure hsqldb.jar is available in your Server classpath container or in prj1/WebContent/WEB-INF/lib folder. If you don't have hsqldb.jar there "Generate Seam Entities" will fail with ClassNotFound Exception, because it will not be able to find HSQL JDBC driver class.
Now you're ready to go. Switch to Seam Perspective and select "Generate Seam Entiies" from context menu on prj1 project
http://community.jboss.org/servlet/JiveServlet/showImage/2163/seam-gen-en...
Leave first step unchanged like it shown below and press "Next"
http://community.jboss.org/servlet/JiveServlet/showImage/2164/seam-gen-en...
On second step press "Refresh" button and make sure it shows all tables form database as it shown below. If there are no tables most likely HSQL connection is not correctly configured. To generate Seam Entities and xhtml pages press "Finish".
http://community.jboss.org/servlet/JiveServlet/showImage/2165/seam-gen-en...
You should get bunch of generated classes in source folder and pages in WebContent.
h2. Server Option
You need to start HSQL as Server first using command line. Open console and change your directory to database directory like
$ cd /home/eskimo/db/employee
Then start HSQL server in Server Mode like
$java -cp /home/eskimo/Java/hsqldb/lib/hsqldb.jar org.hsqldb.Server
You should see output like
[Server@19106c7]: [Thread[main,5,main]]: checkRunning(false) entered
[Server@19106c7]: [Thread[main,5,main]]: checkRunning(false) exited
[Server@19106c7]: Startup sequence initiated from main() method
[Server@19106c7]: Loaded properties from [/home/eskimo/db/employee/server.properties]
[Server@19106c7]: Initiating startup sequence...
[Server@19106c7]: Server socket opened successfully in 8 ms.
[Server@19106c7]: Database [index=0, id=0, db=file:employee, alias=] opened sucessfully in 690 ms.
[Server@19106c7]: Startup sequence completed in 699 ms.
[Server@19106c7]: 2010-02-25 13:37:54.016 HSQLDB server 1.8.1 is online
[Server@19106c7]: To close normally, connect and execute SHUTDOWN SQL
[Server@19106c7]: From command line, use [Ctrl]+[C] to abort abruptly
It starts by default in silent mode. If you want to see what's going one just change property +server.silent+ in server.properties file from +true+ to +false+ and your output will look like
[Server@34a1fc]: [Thread[main,5,main]]: checkRunning(false) entered
[Server@34a1fc]: [Thread[main,5,main]]: checkRunning(false) exited
[Server@34a1fc]: Startup sequence initiated from main() method
[Server@34a1fc]: Loaded properties from [/home/eskimo/db/employee/server.properties]
[Server@34a1fc]: [Thread[main,5,main]]: start() entered
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: run() entered
[Server@34a1fc]: Initiating startup sequence...
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.tls=false
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.port=1701
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.trace=false
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.database.0=employee
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.restart_on_shutdown=false
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.no_system_exit=false
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.silent=false
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.default_page=index.html
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.address=0.0.0.0
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.dbname.0=
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: server.root=.
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: openServerSocket() entered
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: Got server socket: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=1701]
[Server@34a1fc]: Server socket opened successfully in 4 ms.
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: openServerSocket() exiting
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: openDatabases() entered
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: Opening database: [file:employee]
[Server@34a1fc]: Database [index=0, id=0, db=file:employee, alias=] opened sucessfully in 696 ms.
[Server@34a1fc]: [Thread[HSQLDB Server @34a1fc,5,main]]: openDatabases() exiting
[Server@34a1fc]: Startup sequence completed in 701 ms.
[Server@34a1fc]: 2010-02-25 13:41:49.516 HSQLDB server 1.8.1 is online
[Server@34a1fc]: To close normally, connect and execute SHUTDOWN SQL
[Server@34a1fc]: From command line, use [Ctrl]+[C] to abort abruptly
[Server@34a1fc]: [Thread[main,5,main]]: start() exiting
Starting HSQL as Servers you should not worry about employee.lck anymore and can leave "Connect when wizard completes" checkbox selected during creating new HSQL Database Connection, but Database Location should be changed to +hsql://localhost:1701+ in second step of "New Database Connection" Wizard like
http://community.jboss.org/servlet/JiveServlet/showImage/2168/hsql-new-co...
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528622#528622
16 years, 1 month
[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."
by Scott Marlow
User development,
A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...":
http://community.jboss.org/message/528621#528621
Author : Scott Marlow
Profile : http://community.jboss.org/people/smarlow@redhat.com
Message:
--------------------------------------------------------------
It is a requirement that a CF implements the
javax.resource.Referenceable and java.io.Serializable - so that will
always be the case. Hence the current instanceof check.
Dealing
with resource adapters that doesn't implement this requirement could be
something we could look at down the road - but ideally people should
fix their code. That is why we have the validator.
The 1.6 Final Draft November 2009 argues with itself over this:
"20.6.1 Responsibilities In both managed and non-managed environments, registration of a connection factory instance in the JNDI namespace must use either the JNDI Reference or Serializable mechanism. ... "
"6.5.1.3 Additional Requirements ... A connection factory implementation class must implement the interface javax.resource.Referenceable. ... "
An idea could be to create a unique name for each CF, and then
create an alias for the unique name that the user will use. That would
allow us to move the primary names in the JNDI without having to change
any user code. I thinking of java:/eis/, java:global, and other
scenarios depending where the JCA container is deployed.
The
key is to make it simple for users - a JNDI name should be optional,
and in that case we would create an alias based on our default
strategy, f.ex. java:/eis/resourceadapter as we have now.
Also
we should consider how the deployment of the same resource adapter
multiple times - under different names should work. Making the resource
adapter archive name part of the unique name could be an idea - we can
always use the metadata repository to search for information.
+1 for not having to change any user code due to how we manage the CF jndi binding I'm not sure about the unique name part though.
What is the alias? Do you mean generically or with something like a LinkRef (I've never used that before so not sure how it works yet).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528621#528621
16 years, 1 month
