July 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Problem with Seam 1.2.1 and Trinidad 1.0.1

by fquimbay

Greetings ... I use Seam 1.2.1 and JBoss 4.2.0 for a project and works perfectly, when I try use Trinidad 1.0.1 for some components like panelPage, don't work. I use this sort how that I found: http://wiki.apache.org/myfaces/TrinidadSeamAjax4JsfFaceletDetail and I followed this. But, when I deploy my application, I see this: | GRAVE: Error Loading Library: jar:file:/D:/fabio.quimbay/desarrollo/jboss-4.2.0.GA/server/default/tmp/deploy/tmp8908trinidad-impl-1.0.1.jar!/META-INF/trh.taglib.xml | java.io.IOException: Error parsing [jar:file:/D:/fabio.quimbay/desarrollo/jboss-4.2.0.GA/server/default/tmp/deploy/tmp8908trinidad-impl-1.0.1.jar!/META-INF/trh.taglib.xml]: | at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:398) | at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryConfig.java:419) | at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87) | at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104) | at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197) | at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144) | at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95) | at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496) | at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546) | at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:181) | at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) | at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229) | at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) | at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132) | at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) | at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) | at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) | at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) | at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) | at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) | at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) | at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) | at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) | at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:208) | at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:165) | at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138) | at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Unknown Source) | Caused by: org.xml.sax.SAXException: Error Handling [jar:file:/D:/fabio.quimbay/desarrollo/jboss-4.2.0.GA/server/default/tmp/deploy/tmp8908trinidad-impl-1.0.1.jar!/META-INF/trh.taglib.xml@13,107] <handler-class> | at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:259) | at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) | at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source) | at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source) | at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) | at javax.xml.parsers.SAXParser.parse(Unknown Source) | at javax.xml.parsers.SAXParser.parse(Unknown Source) | at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:395) | ... 55 more | Caused by: java.lang.Exception: org.apache.myfaces.trinidadinternal.facelets.TrinidadComponentHandler must be an instance of com.sun.facelets.tag.TagHandler | at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.createClass(TagLibraryConfig.java:281) | at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:206) | ... 70 more and don't works. Any help welcome, Thanks .. ? -- fabio quimbay[/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059424#4059424 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059424

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: How does one @In(ject) a component from components.xml?

by fhh

The component.xml file is required to mark the jar as a seam jar. If it is missing the deployment scanner will not scan the jar and any seam annotation will not be detected. Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059423#4059423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059423

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: How does one @In(ject) a component from components.xml?

by gothmog

Hey thanks guys, both approaches work. I copied one of the sample projects (contactlist) and I noticed that it has a two component.xml files, one in the META-INF and another in the WEB-INF. Both of these are required otherwise you start getting weird errors like I said in the earlier post. The weird thing is, is that I can comment out all the text in the components.xml in the META-INF and it still works, but as soon as I remove it, the whole things falls apart on deployment. I also notice the registration example doesn't have two component.xml files but has a seam.properties (empty) file. I need to do some reading on how this thing is configured and what each file does, but thanks for getting me past this problem? Troy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059422#4059422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059422

18 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - How do I onfigure a simple socket server (TEXT)?

by hurzeler

I need help! How do I go about to create a simple text socket server that I can communicate with for example via telnet? I use JBoss4.0.5GA and JBoss4.2.0GA. On JBoss4.0.5GA the problem I am facing is that the un/marshaller does not get used. On JBoss4.2.0GA I get | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | | ObjectName: com.test:service=Connector,transport=socket | | State: FAILED | | Reason: org.jboss.remoting.InvalidConfigurationException: The invoker for locator (InvokerLocator [socket://localhost:8084/?dataType=invocation&enableTcpNoDelay=true&marshaller=com.test.socket.V75SocketServer.TextMarshaller&socketTimeout=600000&unmarshaller=com.test.socket.V75SocketServer.TextUnMarshaller]) is already in use by another Connector. Either change the locator or add new handlers to existing Connector. | I can see that a socket server is defined in server/default/conf/jboss-service.xml but I would think it should be possible to stick another socket server on a different port. | <server> |  |  |  | <mbean code="org.jboss.remoting.transport.Connector" | name="com.test:service=Connector,transport=socket" | display-name="Socket transport Connector"> | <attribute name="Configuration"> | <config> | <invoker transport="socket"> | <attribute name="dataType" isParam="true">invocation</attribute> | <attribute name="marshaller" isParam="true">com.test.socket.V75SocketServer.TextMarshaller</attribute> | <attribute name="unmarshaller" isParam="true">com.test.socket.V75SocketServer.TextUnMarshaller</attribute> | <attribute name="serverSocketClass">com.test.socket.V75SocketServer.SimpleInputStreamWrapper</attribute> | <attribute name="socketTimeout" isParam="true">600000</attribute> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">8084</attribute> | <attribute name="enableTcpNoDelay" isParam="true">true</attribute> | </invoker> | <handlers> | <handler subsystem="V75">com.test.socket.V75SocketServer.Handler</handler> | </handlers> | </config> | </attribute> | </mbean> | | </server> Thanks for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059421#4059421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059421

18 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - How do I onfigure a simple socket server (TEXT)?

by hurzeler

I need help! How do I go about to create a simple text socket server that I can communicate with for example via telnet? I use JBoss4.0.5GA and JBoss4.2.0GA. On JBoss4.0.5GA the problem I am facing is that the un/marshaller does not get used. On JBoss4.2.0GA I get | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | | ObjectName: com.test:service=Connector,transport=socket | | State: FAILED | | Reason: org.jboss.remoting.InvalidConfigurationException: The invoker for locator (InvokerLocator [socket://localhost:8084/?dataType=invocation&enableTcpNoDelay=true&marshaller=com.test.socket.V75SocketServer.TextMarshaller&socketTimeout=600000&unmarshaller=com.test.socket.V75SocketServer.TextUnMarshaller]) is already in use by another Connector. Either change the locator or add new handlers to existing Connector. | I can see that a socket server is defined in server/default/conf/jboss-service.xml but I would think it should be possible to stick another socket server on a different port. | <server> |  |  |  | <mbean code="org.jboss.remoting.transport.Connector" | name="com.test:service=Connector,transport=socket" | display-name="Socket transport Connector"> | <attribute name="Configuration"> | <config> | <invoker transport="socket"> | <attribute name="dataType" isParam="true">invocation</attribute> | <attribute name="marshaller" isParam="true">com.test.socket.V75SocketServer.TextMarshaller</attribute> | <attribute name="unmarshaller" isParam="true">com.test.socket.V75SocketServer.TextUnMarshaller</attribute> | <attribute name="serverSocketClass">com.test.socket.V75SocketServer.SimpleInputStreamWrapper</attribute> | <attribute name="socketTimeout" isParam="true">600000</attribute> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">8084</attribute> | <attribute name="enableTcpNoDelay" isParam="true">true</attribute> | </invoker> | <handlers> | <handler subsystem="V75">com.test.socket.V75SocketServer.Handler</handler> | </handlers> | </config> | </attribute> | </mbean> | | </server> Thanks for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059420#4059420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059420

18 years, 4 months

1
0
0 / 0

[Remoting] - Simple Socket Server (TEXT)?

by hurzeler

I need help! How do I go about to create a simple text socket server that I can communicate with for example via telnet? I use JBoss4.0.5GA and JBoss4.2.0GA. On JBoss4.0.5GA the problem I am facing is that the un/marshaller does not get used. On JBoss4.2.0GA I get | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | | ObjectName: com.test:service=Connector,transport=socket | | State: FAILED | | Reason: org.jboss.remoting.InvalidConfigurationException: The invoker for locator (InvokerLocator [socket://localhost:8084/?dataType=invocation&enableTcpNoDelay=true&marshaller=com.test.socket.V75SocketServer.TextMarshaller&socketTimeout=600000&unmarshaller=com.test.socket.V75SocketServer.TextUnMarshaller]) is already in use by another Connector. Either change the locator or add new handlers to existing Connector. | I can see that a socket server is defined in server/default/conf/jboss-service.xml but I would think it should be possible to stick another socket server on a different port. | <server> |  |  |  | <mbean code="org.jboss.remoting.transport.Connector" | name="com.test:service=Connector,transport=socket" | display-name="Socket transport Connector"> | <attribute name="Configuration"> | <config> | <invoker transport="socket"> | <attribute name="dataType" isParam="true">invocation</attribute> | <attribute name="marshaller" isParam="true">com.test.socket.V75SocketServer.TextMarshaller</attribute> | <attribute name="unmarshaller" isParam="true">com.test.socket.V75SocketServer.TextUnMarshaller</attribute> | <attribute name="serverSocketClass">com.test.socket.V75SocketServer.SimpleInputStreamWrapper</attribute> | <attribute name="socketTimeout" isParam="true">600000</attribute> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">8084</attribute> | <attribute name="enableTcpNoDelay" isParam="true">true</attribute> | </invoker> | <handlers> | <handler subsystem="V75">com.test.socket.V75SocketServer.Handler</handler> | </handlers> | </config> | </attribute> | </mbean> | | </server> Thanks for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059419#4059419 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059419

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - <transaction:ejb-transaction/> and SeamTest

by fernando_jmt

I just migrated my application from Seam 1.2 to Seam 2.0.0.BETA1 using Tomcat 6 and Embedded Jboss, it works like a charm. But, when I tried to execute the test suites I got the following exceptions: | uildfile: D:\Fer\srcEjemplos\Seam\seam2gen\build.xml | compiletest: | copytestclasses: | buildtest: | [copy] Copying 1 file to D:\Fer\srcEjemplos\Seam\seam2gen\test-build\META-INF | [copy] Copying 1 file to D:\Fer\srcEjemplos\Seam\seam2gen\test-build | test: | [testng] [Parser] Running: | [testng] D:\Fer\srcEjemplos\Seam\seam2gen\test-build\seam2Test.xml | [testng] WARN 30-06 21:28:38,824 (UnifiedLoaderRepository3.java:addClassLoader:675) -Tried to add non-URLClassLoader. Ignored | [testng] WARN 30-06 21:28:40,590 (TxControl.java:<clinit>:266) -[com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using -37c5b421:885:46870348:0 | [testng] WARN 30-06 21:28:44,809 (JDBCPersistenceManager.java:start:143) - | [testng] JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently NONE. | [testng] Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems. | [testng] Using an isolation level more strict than READ_COMMITTED may lead to deadlock. | [testng] ERROR 30-06 21:28:56,106 (SeamPhaseListener.java:afterPhase:189) -uncaught exception | [testng] java.lang.IllegalStateException: Could not commit transaction | [testng] at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:589) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:325) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.applyRequestValuesPhase(BaseSeamTest.java:666) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.emulateJsfLifecycle(BaseSeamTest.java:547) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.run(BaseSeamTest.java:487) | [testng] at com.mydomain.sean2gen.test.LoginTest.testLogin(LoginTest.java:77) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | [testng] at java.lang.reflect.Method.invoke(Unknown Source) | [testng] at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) | [testng] at org.testng.internal.Invoker.invokeMethod(Invoker.java:470) | [testng] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564) | [testng] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830) | [testng] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) | [testng] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) | [testng] at org.testng.TestRunner.runWorkers(TestRunner.java:678) | [testng] at org.testng.TestRunner.privateRun(TestRunner.java:624) | [testng] at org.testng.TestRunner.run(TestRunner.java:495) | [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) | [testng] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) | [testng] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) | [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:190) | [testng] at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) | [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:765) | [testng] at org.testng.TestNG.run(TestNG.java:699) | [testng] at org.testng.TestNG.privateMain(TestNG.java:824) | [testng] at org.testng.TestNG.main(TestNG.java:802) | [testng] Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.transaction.transaction | [testng] at org.jboss.seam.Component.newInstance(Component.java:1853) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1756) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1735) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1712) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1707) | [testng] at org.jboss.seam.transaction.Transaction.instance(Transaction.java:96) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:576) | [testng] ... 29 more | [testng] Caused by: javax.naming.NameNotFoundException: EjbTransaction not bound | [testng] at org.jnp.server.NamingServer.getBinding(NamingServer.java:542) | [testng] at org.jnp.server.NamingServer.getBinding(NamingServer.java:550) | [testng] at org.jnp.server.NamingServer.getObject(NamingServer.java:556) | [testng] at org.jnp.server.NamingServer.lookup(NamingServer.java:267) | [testng] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:628) | [testng] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:590) | [testng] at javax.naming.InitialContext.lookup(Unknown Source) | [testng] at org.jboss.seam.Component.instantiateSessionBean(Component.java:1173) | [testng] at org.jboss.seam.Component.instantiate(Component.java:1159) | [testng] at org.jboss.seam.Component.newInstance(Component.java:1849) | [testng] ... 35 more | [testng] ERROR 30-06 21:28:56,121 (DebugPageHandler.java:handle:23) -redirecting to debug page | [testng] javax.naming.NameNotFoundException: EjbTransaction not bound | [testng] at org.jnp.server.NamingServer.getBinding(NamingServer.java:542) | [testng] at org.jnp.server.NamingServer.getBinding(NamingServer.java:550) | [testng] at org.jnp.server.NamingServer.getObject(NamingServer.java:556) | [testng] at org.jnp.server.NamingServer.lookup(NamingServer.java:267) | [testng] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:628) | [testng] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:590) | [testng] at javax.naming.InitialContext.lookup(Unknown Source) | [testng] at org.jboss.seam.Component.instantiateSessionBean(Component.java:1173) | [testng] at org.jboss.seam.Component.instantiate(Component.java:1159) | [testng] at org.jboss.seam.Component.newInstance(Component.java:1849) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1756) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1735) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1712) | [testng] at org.jboss.seam.Component.getInstance(Component.java:1707) | [testng] at org.jboss.seam.transaction.Transaction.instance(Transaction.java:96) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:576) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:325) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) | [testng] at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.applyRequestValuesPhase(BaseSeamTest.java:666) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.emulateJsfLifecycle(BaseSeamTest.java:547) | [testng] at org.jboss.seam.mock.BaseSeamTest$Request.run(BaseSeamTest.java:487) | [testng] at com.mydomain.sean2gen.test.LoginTest.testLogin(LoginTest.java:77) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | [testng] at java.lang.reflect.Method.invoke(Unknown Source) | [testng] at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) | [testng] at org.testng.internal.Invoker.invokeMethod(Invoker.java:470) | [testng] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564) | [testng] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830) | [testng] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) | [testng] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) | [testng] at org.testng.TestRunner.runWorkers(TestRunner.java:678) | [testng] at org.testng.TestRunner.privateRun(TestRunner.java:624) | [testng] at org.testng.TestRunner.run(TestRunner.java:495) | [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) | [testng] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) | [testng] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) | [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:190) | [testng] at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) | [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:765) | [testng] at org.testng.TestNG.run(TestNG.java:699) | [testng] at org.testng.TestNG.privateMain(TestNG.java:824) | [testng] at org.testng.TestNG.main(TestNG.java:802) | [testng] ERROR 30-06 21:28:56,137 (Contexts.java:flushAndDestroyContexts:335) -could not discover transaction status | It works fine when I remove <transaction:ejb-transaction/> from components.xml. I also generated a seam-gen application adding such transaction:ejb-transaction configuration, and I get the same exception. Any idea, what is wrong? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059418#4059418 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059418

18 years, 4 months

1
0
0 / 0

[Advanced Documentation] - Minimal Tomcat w/JBoss AS 4.2 installation

by TomCat1116

How does one perform an installation of JBoss AS 4.2 with only the bare minimum necessary to run Tomcat (and, of course, inclusive of Tomcat)? I'm new to JBoss and understand that in version 4.0.4 it was possible to 'point and shoot' to create such an installation using the installer (also included several other baseline types of installations), but for version 4.2 I only see a directory for 'all', 'default', and 'minimal'. Can someone point me in the right direction with the right docs to reasonably quickly get me where I want to be with my installation, or, even better, has anyone already performed the steps and has the ready-made directory? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059417#4059417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059417

18 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2007