[JBoss Seam] - Re: Problem installing Embedded Jboss on Tomcat 5.5
by pete.muirï¼ jboss.org
"Stateless Bean" wrote : I removed my tomcat and installed in path: "C:\tomcat"
This is what I meant
anonymous wrote :
| WARN 09-08 22:32:39,515 (UnifiedLoaderRepository3.java:addClassLoader:675) -Tried to add non-URLClassLoader. Ignored
| | WARN 09-08 22:32:42,484 (TxControl.java:<clinit>:266) -[com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using -3f57ffff:422:46bb79ea:0
| | WARN 09-08 22:32:50,593 (JDBCPersistenceManager.java:start:143) -
| |
| | JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently NONE.
| | Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
| | Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
| |
There is no error in this log. That warning is fine
anonymous wrote : 1. Can u Pete explain me difference between folder in jboss-seam-2.0.0.BETA1/bootstrap and bootstrap packaged in embedded-jboss-beta2.zip ?
The one in Seam is for running the tests in Seam and examples.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072729#4072729
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072729
18Â years, 10Â months
[Remoting] - Re: BisocketServerInvoker and random port issue
by ron.sigalï¼ jboss.com
anonymous wrote : Can anyone please clarify if there is any way to configure the BisocketServerInvoker to not use a random port when starting the secondary server?
There is a JIRA issue for this feature: JBREM-749 "BisocketServerInvoker: Make configurable the address and port of secondary server socket". It is scheduled for the next Remoting release.
anonymous wrote : If this is true, am I correct in assuming that it is impossible to operate an application (jboss-4.2.0.GA + jboss-messaging-1.3.0.GA) that utilizes it behind a firewall unless all ports are open? If this is true, was there a reason for it?
Until the fix for JBREM-749 is available, you're correct. The motivation for the bisocket transport was to support *clients* behind a firewall.
anonymous wrote : Is the thought here to use the multiplex transport instead of the bisocket? Would there be any performance impacts by using the different transport? I am assuming bisocket would give the best performance, is that correct?
I'm recommending, whenever possible, bisocket over multiplex. It's faster (we don't have any statistics yet, but I'd guess at least 50% faster). It's also, in my opinion, more reliable. It's used by JBossMessaging, which means it's being used in production in many places. It's relatively new, and we're still shaking out some wrinkles, but I'm not aware of any comparable use of multiplex.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072726#4072726
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072726
18Â years, 10Â months
[Remoting] - Re: BisocketServerInvoker and random port issue
by ron.sigalï¼ jboss.com
anonymous wrote : Can anyone please clarify if there is any way to configure the BisocketServerInvoker to not use a random port when starting the secondary server?
There is a JIRA issue for this feature: JBREM-749 "BisocketServerInvoker: Make configurable the address and port of secondary server socket". It is scheduled for the next Remoting release.
anonymous wrote : If this is true, am I correct in assuming that it is impossible to operate an application (jboss-4.2.0.GA + jboss-messaging-1.3.0.GA) that utilizes it behind a firewall unless all ports are open? If this is true, was there a reason for it?
Until the fix for JBREM-749 is available, you're correct. The motivation for the bisocket transport was to support *clients* behind a firewall.
anonymous wrote : Is the thought here to use the multiplex transport instead of the bisocket? Would there be any performance impacts by using the different transport? I am assuming bisocket would give the best performance, is that correct?
I'm recommending, whenever possible, bisocket over multiplex. It's faster (we don't have any statistics yet, but I'd guess at least 50% faster). It's also, in my opinion, more reliable. It's used by JBossMessaging, which means it's being used in production in many places. It's relatively new, and we're still shaking out some wrinkles, but I'm not aware of any comparable use of multiplex.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072725#4072725
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072725
18Â years, 10Â months
[Remoting] - Re: BisocketServerInvoker and random port issue
by ron.sigalï¼ jboss.com
anonymous wrote : Can anyone please clarify if there is any way to configure the BisocketServerInvoker to not use a random port when starting the secondary server?
There is a JIRA issue for this feature: JBREM-749 "BisocketServerInvoker: Make configurable the address and port of secondary server socket". It is scheduled for the next Remoting release.
anonymous wrote : If this is true, am I correct in assuming that it is impossible to operate an application (jboss-4.2.0.GA + jboss-messaging-1.3.0.GA) that utilizes it behind a firewall unless all ports are open? If this is true, was there a reason for it?
Until the fix for JBREM-749 is available, you're correct. The motivation for the bisocket transport was to support *clients* behind a firewall.
anonymous wrote : Is the thought here to use the multiplex transport instead of the bisocket? Would there be any performance impacts by using the different transport? I am assuming bisocket would give the best performance, is that correct?
I'm recommending, whenever possible, bisocket over multiplex. It's faster (we don't have any statistics yet, but I'd guess at least 50% faster). It's also, in my opinion, more reliable. It's used by JBossMessaging, which means it's being used in production in many places. It's relatively new, and we're still shaking out some wrinkles, but I'm not aware of any comparable use of multiplex.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072724#4072724
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072724
18Â years, 10Â months
[JBoss Seam] - Re: Problem installing Embedded Jboss on Tomcat 5.5
by Stateless Bean
1. Can u Pete explain me difference between folder in jboss-seam-2.0.0.BETA1/bootstrap and bootstrap packaged in embedded-jboss-beta2.zip ?
When I copied botstrap files/folders into my tomcat from embedded-jboss-beta2.zip and setted <Listenders... like in seam docs, I get what is in my previous post.
When I coppied bootstrap from seam zip file, Tomcat looks like getting starting but not well, here you go:
Booking example deployed on my tomcat:
anonymous wrote :
| INFO 09-08 22:58:37,671 [org.apache.coyote.http11.Http11BaseProtocol.init():145] Initializing Coyote HTTP/1.1 on http-8080
| INFO 09-08 22:58:37,687 [org.apache.catalina.startup.Catalina.load():512] Initialization processed in 1125 ms
| WARN 09-08 22:58:40,343 [org.jboss.mx.loading.UnifiedLoaderRepository3.addClassLoader():675] Tried to add non-URLClassLoader. Ignored
| INFO 09-08 22:58:43,093 [com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():126] JBossTS Transaction Service (JTA version) - JBoss Inc.
| INFO 09-08 22:58:43,093 [com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():128] Setting up property manager MBean and JMX layer
| WARN 09-08 22:58:43,203 [com.arjuna.ats.arjuna.coordinator.TxControl.():266] [com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using 531e7e8c:4b3:46bb8003:0
| INFO 09-08 22:58:43,312 [com.arjuna.ats.arjuna.recovery.TransactionStatusManager.addService():110] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 1203
| INFO 09-08 22:58:43,343 [?.?():?] TransactionStatusManagerItem - host: 83.30.126.140 port: 1203
| INFO 09-08 22:58:43,359 [com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start():161] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_3] - TransactionStatusManager started on port 1203 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
| INFO 09-08 22:58:43,390 [?.?():?] Registering mbean for module 'arjuna'
| INFO 09-08 22:58:43,390 [?.?():?] Initialising JMX agent com.arjuna.ats.internal.jbossatx.agent.LocalJBossAgentImpl
| INFO 09-08 22:58:43,453 [com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():163] Starting recovery manager
| INFO 09-08 22:58:43,468 [?.?():?]
| --- Start RecoveryActivators
| INFO 09-08 22:58:43,500 [com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.():142] [com.arjuna.ats.internal.arjuna.recovery.ready] RecoveryManagerImple is ready on port 1 204
| INFO 09-08 22:58:43,500 [com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():168] Recovery manager started
| INFO 09-08 22:58:43,515 [com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():191] Binding TransactionManager JNDI Reference
| INFO 09-08 22:58:48,703 [org.jboss.resource.deployers.RARDeployment.startService():146] Required license terms exist, view vfsfile:/C:/Tomcat/common/classes/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
| INFO 09-08 22:58:48,843 [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.bindConnectionFactory():148] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
| INFO 09-08 22:58:48,875 [org.jboss.resource.deployers.RARDeployment.startService():146] Required license terms exist, view vfsfile:/C:/Tomcat/common/classes/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
| INFO 09-08 22:58:48,890 [org.jboss.resource.deployers.RARDeployment.startService():146] Required license terms exist, view vfsfile:/C:/Tomcat/common/classes/deploy/jms-ra.rar/META-INF/ra.xml
| WARN 09-08 22:58:50,093 [org.jboss.messaging.core.plugin.JDBCPersistenceManager.start():143]
|
| JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently NONE.
| Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
| Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
|
| INFO 09-08 22:58:50,593 [org.jboss.jms.server.ServerPeer.():187] ServerPeer[0] creating server peer with ID 0
| INFO 09-08 22:58:51,765 [org.jboss.jms.server.ServerPeer.startService():278] JBoss Messaging 1.2.0.sp1 server [0] started
| INFO 09-08 22:58:51,890 [org.jboss.jms.server.destination.TopicService.startService():122] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:51,921 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:51,937 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,109 [org.jboss.jms.server.connectionfactory.ConnectionFactory.startService():148] Connector bisocket://83.30.126.140:4457 has leasing enabled, lease period 10000 milliseconds
| INFO 09-08 22:58:52,109 [org.jboss.jms.server.connectionfactory.ConnectionFactory.startService():149] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] started
| INFO 09-08 22:58:52,140 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,140 [org.jboss.jms.server.destination.TopicService.startService():122] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,156 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,156 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,171 [org.jboss.jms.server.destination.QueueService.startService():149] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
| INFO 09-08 22:58:52,203 [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.bindConnectionFactory():148] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JmsXA' to JNDI name 'java:JmsXA'
| INFO 09-08 22:58:52,312 [org.apache.catalina.core.StandardService.start():440] Starting service Catalina
| INFO 09-08 22:58:52,328 [org.apache.catalina.core.StandardEngine.start():432] Starting Servlet Engine: Apache Tomcat/5.5.23
| INFO 09-08 22:58:52,359 [org.apache.catalina.core.StandardHost.start():734] XML validation disabled
| INFO 09-08 22:58:52,875 [org.apache.catalina.loader.WebappLoader.start():659] Dual registration of jndi stream handler: factory already defined
| INFO 09-08 22:58:53,718 [org.apache.catalina.startup.HostConfig.deployWAR():804] Deploying web application archive jboss-seam-booking.war
| INFO 09-08 22:59:00,343 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase with dependencies:
| INFO 09-08 22:59:00,343 [org.jboss.ejb3.MCKernelAbstraction.install():131] jboss.jca:name=bookingDatasource,service=DataSourceBinding
| INFO 09-08 22:59:00,656 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=AuthenticatorAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,656 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,703 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=BookingListAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,703 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,734 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=ChangePasswordAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,734 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=HotelBookingAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=HotelSearchingAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=RegisterAction,service=EJB3 with dependencies:
| INFO 09-08 22:59:00,750 [org.jboss.ejb3.MCKernelAbstraction.install():131] persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:00,828 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 with dependencies:
| INFO 09-08 22:59:01,453 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
| WARN 09-08 22:59:01,546 [org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory.restoreTimerService():112] TIMER SERVICE IS NOT INSTALLED
| INFO 09-08 22:59:01,546 [org.jboss.ejb3.MCKernelAbstraction.install():119] installing bean: jboss.j2ee:jar=jboss-seam.jar,name=EjbTransaction,service=EJB3 with dependencies:
| INFO 09-08 22:59:01,953 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.transaction.EjbTransaction ejbName: EjbTransaction
| INFO 09-08 22:59:02,265 [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.bindConnectionFactory():148] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=bookingDatasource' to JNDI name 'java:bookingDatasource'
| INFO 09-08 22:59:02,281 [org.jboss.ejb3.entity.PersistenceUnitDeployment.start():175] Starting persistence unit persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:05,890 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.BookingListAction ejbName: BookingListAction
| INFO 09-08 22:59:06,015 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.ChangePasswordAction ejbName: ChangePasswordAction
| INFO 09-08 22:59:06,078 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.AuthenticatorAction ejbName: AuthenticatorAction
| WARN 09-08 22:59:06,093 [org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory.restoreTimerService():112] TIMER SERVICE IS NOT INSTALLED
| INFO 09-08 22:59:06,203 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.HotelSearchingAction ejbName: HotelSearchingAction
| INFO 09-08 22:59:06,328 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.HotelBookingAction ejbName: HotelBookingAction
| INFO 09-08 22:59:06,437 [org.jboss.ejb3.EJBContainer.start():580] STARTED EJB: org.jboss.seam.example.booking.RegisterAction ejbName: RegisterAction
| ERROR 09-08 22:59:06,578 [org.apache.catalina.core.StandardContext.start():4217] Error listenerStart
| ERROR 09-08 22:59:06,578 [org.apache.catalina.core.StandardContext.start():4244] Context [/jboss-seam-booking] startup failed due to previous errors
| INFO 09-08 22:59:06,578 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.AuthenticatorAction ejbName: AuthenticatorAction
| INFO 09-08 22:59:06,593 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.BookingListAction ejbName: BookingListAction
| INFO 09-08 22:59:06,609 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.ChangePasswordAction ejbName: ChangePasswordAction
| INFO 09-08 22:59:06,625 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.HotelBookingAction ejbName: HotelBookingAction
| INFO 09-08 22:59:06,640 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.HotelSearchingAction ejbName: HotelSearchingAction
| INFO 09-08 22:59:06,656 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.example.booking.RegisterAction ejbName: RegisterAction
| INFO 09-08 22:59:06,656 [org.jboss.ejb3.entity.PersistenceUnitDeployment.stop():266] Stopping persistence unit persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:06,656 [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService.unbindConnectionFactory():170] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=bookingDatasource' from JNDI name 'java:bookingDatasource'
| INFO 09-08 22:59:06,703 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
| INFO 09-08 22:59:06,703 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
| INFO 09-08 22:59:06,718 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam.jar,name=EjbTransaction,service=EJB3
| INFO 09-08 22:59:06,718 [org.jboss.ejb3.EJBContainer.stop():593] STOPPED EJB: org.jboss.seam.transaction.EjbTransaction ejbName: EjbTransaction
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=AuthenticatorAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=BookingListAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=ChangePasswordAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=HotelBookingAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=HotelSearchingAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: jboss.j2ee:jar=jboss-seam-booking.jar,name=RegisterAction,service=EJB3
| INFO 09-08 22:59:06,734 [org.jboss.ejb3.MCKernelAbstraction.uninstall():198] uninstalling bean: persistence.units:jar=jboss-seam-booking.jar,unitName=bookingDatabase
| INFO 09-08 22:59:07,250 [org.apache.coyote.http11.Http11BaseProtocol.start():157] Starting Coyote HTTP/1.1 on http-8080
| INFO 09-08 22:59:07,625 [org.apache.jk.common.ChannelSocket.init():393] JK: ajp13 listening on /0.0.0.0:8009
| INFO 09-08 22:59:07,640 [org.apache.jk.server.JkMain.start():344] Jk running ID=0 time=0/140 config=null
| INFO 09-08 22:59:07,703 [org.apache.catalina.storeconfig.StoreLoader.load():230] Find registry server-registry.xml at classpath resource
| INFO 09-08 22:59:08,046 [org.apache.catalina.startup.Catalina.start():560] Server startup in 30359 ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072722#4072722
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072722
18Â years, 10Â months
[JBoss Seam] - validation & selectManyListbox
by dschaedl
JBoss 4.0.5
JBoss Seam 1.2.1.GA
My h:selectManyListbox displays my list correctly. But when I select entries and hit update to update my model containing this list I get a validation Error: "value is not valid" (on the webpage). How are the entries validated? why isn't it valid?
If I switch off the validation and press the update-button nothing happens (Jboss is doing 'someting', but no logging, no page-forwarding; the update-action seems not to be called)
The update works just fine if I deselect all entries in the listbox.
The XHTML:
| ...
| <s:decorate id="coursesDecoration" template="layout/edit.xhtml">
| <ui:define name="label">alle PRC-Kurse</ui:define>
| <h:selectManyListbox value="#{trainer.courses}" >
| <s:selectItems value="#{courseLister.allCourses}" var="course" label="#{course.name}" />
| <s:convertEntity/>
| </h:selectManyListbox>
| </s:decorate>
| ...
| <h:commandButton id="updatetrainer" value="update" action="#{edittrainer.updateTrainer}" rendered="#{!edittrainer.newTrainer}" />
|
Trainer
| @Entity
| @Name("trainer")
| public class Trainer extends Rower {
|
| private List<Course> courses;
|
| @ManyToMany
| public List<Course> getCourses() {
| return courses;
| }
| public void setCourses(List<Course> courses) {
| this.courses = courses;
| }
| ...
|
Course
| @Entity
| @Name("course")
| public class Course implements Serializable{
|
| @ManyToMany(mappedBy="courses")
| private List<Trainer> trainers;
| ...
|
CourseListerBean
| ...
| public List<Course> getAllCourses() {
| return em.createQuery("from Course c order by c.name desc").getResultList();
| }
| ...
|
editTrainerBean
| @Stateful
| @Name("edittrainer")
| public class EditTrainerBean implements EditTrainer {
|
| @In(required=false)
| @Out
| private Trainer trainer;
|
| public void updateTrainer() {
| log.info("updating trainer: #{trainer.name} id:#{trainer.id}"); <-- never shown!
| em.persist(trainer);
| }
| ...
|
any ideas?
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072721#4072721
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072721
18Â years, 10Â months
[JBoss Seam] - Re: Problem installing Embedded Jboss on Tomcat 5.5
by Stateless Bean
Pete can u point like to child, you mean path in windows class path, or some file??
I removed my tomcat and installed in path: "C:\tomcat"
and now I get this
anonymous wrote :
| WARN 09-08 22:32:39,515 (UnifiedLoaderRepository3.java:addClassLoader:675) -Tried to add non-URLClassLoader. Ignored
| WARN 09-08 22:32:42,484 (TxControl.java::266) -[com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using -3f57ffff:422:46bb79ea:0
| WARN 09-08 22:32:50,593 (JDBCPersistenceManager.java:start:143) -
|
| JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently NONE.
| Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems.
| Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
|
I try to run Embedded JBoss second day and I'm getting here frustrated.
You wrote in seam docs, that Instalation is quite simple...wrrrrrrr:(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072720#4072720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072720
18Â years, 10Â months