[JBoss Seam] - Re: Persistence unit not bound
by daleth
| 10:57:32,801 INFO [STDOUT] 10:57:32,801 DEBUG [SeamVariableResolver] resolving name: basicSearch
| 10:57:32,802 INFO [STDOUT] 10:57:32,802 DEBUG [Component] instantiating Seam component: basicSearch
| 10:57:32,802 INFO [STDOUT] 10:57:32,802 DEBUG [Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.LocalOnlyContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 10:57:32,804 ERROR [STDERR] Dec 17, 2006 10:57:32 AM com.sun.facelets.FaceletViewHandler handleRenderException
| SEVERE: Error Rendering View[/basicSearch.xhtml]
| org.jboss.seam.InstantiationException: Could not instantiate Seam component: basicSearch
| at org.jboss.seam.Component.newInstance(Component.java:1722)
| at org.jboss.seam.Component.getInstance(Component.java:1625)
| at org.jboss.seam.Component.getInstance(Component.java:1592)
| at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:46)
| at org.apache.myfaces.config.LastVariableResolverInChain.resolveVariable(LastVariableResolverInChain.java:42)
| at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:134)
| at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:65)
| at com.sun.el.parser.AstValue.getValue(AstValue.java:106)
| at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
| at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
| at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:56)
| at javax.faces.component.UIOutput.getValue(UIOutput.java:77)
| at org.apache.myfaces.shared_impl.renderkit.RendererUtils.getStringValue(RendererUtils.java:217)
| at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderInput(HtmlTextRendererBase.java:135)
| at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:53)
| at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:536)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:580)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:613)
| Caused by: javax.naming.NameNotFoundException: portal not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:626)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.seam.Component.instantiateSessionBean(Component.java:1027)
| at org.jboss.seam.Component.instantiate(Component.java:1013)
| at org.jboss.seam.Component.newInstance(Component.java:1718)
| ... 45 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994505#3994505
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994505
19 years, 7 months
[JBoss jBPM] - Re: Problem testing Hello BPEL sample
by zauberlehrling
I 've found the following entry in the jndi:
anonymous wrote : Global JNDI Namespace
|
| +- jbpmbpel-client (class: org.jnp.interfaces.NamingContext)
| | +- service (class: org.jnp.interfaces.NamingContext)
| | | +- Hello (class: org.jboss.ws.jaxrpc.ServiceReferenceable)
|
And if I read the jndi with the following code:
Properties properties = new Properties();
| properties.setProperty("java.naming.provider.url", "jnp://localhost:1099");
| properties.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| properties.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming.client");
| properties.setProperty("j2ee.clientName", "jbpmbpel-client");
| InitialContext iniCtx = new InitialContext(properties);
|
| NamingEnumeration iter = (NamingEnumeration)iniCtx.list("jbpmbpel-client/service");
| while (iter.hasMore())
| {
| System.out.println(" "+iter.next());
| }
then I get the following answer:
Hello: org.jboss.ws.jaxrpc.ServiceReferenceable
This looks fine. But when I run the following commands:
Properties properties = new Properties();
| properties.setProperty("java.naming.provider.url", "jnp://localhost:1099");
| properties.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| properties.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming.client");
| properties.setProperty("j2ee.clientName", "jbpmbpel-client");
| InitialContext iniCtx = new InitialContext(properties);
|
| Object object = iniCtx.lookup("jbpmbpel-client/service/Hello");
then the answer is:
19:56:02,788 ERROR ServiceObjectFactory : Cannot create service
| javax.naming.NamingException: Cannot unmarshall service ref meta data, cause: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
| at org.jboss.ws.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:127)
| at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
| at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
| at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
So as I understand there is a problem accessing the Hello-Object in the jndi.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994503#3994503
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994503
19 years, 7 months
[JBoss Seam] - jndi datasource publishing
by hstang
Hi, I'm new to Seam. I have a current interest to integrate Spring and Seam's data access strategy. However, I am unable to lookup the data source from JNDI using embedded ejb3 + SEAM configuration. I am using the "jpa" example from SEAM 1.1.0GA.
My log reports:
12:40:46,196 [main] INFO DataSourceFactory:43 - starting Datasource at JNDI name: java:/DefaultDS
| 12:40:46,216 [main] INFO LocalTxDataSource:102 - Bound datasource to JNDI name 'java:/DefaultDS'
|
However in my application, the only keys in the initial context are those listed in the jndi.properties, namely java.naming.factory.initial and java.naming.factory.url.pkgs.
| #jndi.properties
| java.naming.factory.initial org.jnp.interfaces.LocalOnlyContextFactory
| java.naming.factory.url.pkgs org.jboss.naming:org.jnp.interfaces
|
I have crawled through the Seam's source and there is only one place that initializes the jndi properties--Initialization.java, that's after reading in jndi.properties which makes sense.
So now I'm looking at org.jboss.seam.microcontainer.DataSourceFactory:
| // ds is of type LocalTxDataSource
| ds.setJndiName(jndiName);
| ds.setInitialContextProperties(Naming.getInitialContextProperties());
|
What does the code above do? I mean Seam is able to find the datasouce in my specified jndiName=java:/DefaultDS. However, in my application and in Spring, it could not find "DefaultDS" in the initial context.
Is it possible to bind the data source created by the microcontainer to JNDI in Seam? Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994497#3994497
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994497
19 years, 7 months
[JBoss Seam] - Persistence unit not bound
by daleth
I'm using SEAM 1.1 with the embedded EJB container running inside Tomcat (JBoss Tomcat for development and plain ol' Apache Tomcat at the customer's site). For the purposes of development I'm using an in-memory HSQLDB database defined in jboss-beans.xml.
Everything seems to start up fine, I see all my entity and stateless session beans get created, I see the datasource I define get created and get bound under the given JNDI name. However, when I try to load a page that uses a stateless bean I get an exception that a bean can not be instantiated with a root cause of:
javax.naming.NameNotFoundException: portal not bound
where "portal" is the name of my persistence context.
Any suggestions? I imagine I'm either missing some nuance about how these config files are working together or incorrectly assuming that the "portal" referred to in the error is the "portal" persistence unit.
Thanks.
jboss-beans.xml - define the data source w/ JNDI name
| <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
| xmlns="urn:jboss:bean-deployer">
|
| <bean name="PortalDatasourceBootstrap" class="org.jboss.resource.adapter.jdbc.local.LocalTxDataSource">
| <property name="driverClass">org.hsqldb.jdbcDriver</property>
| <property name="connectionURL">jdbc:hsqldb:mem:portal</property>
| <property name="userName"><value class="java.lang.String">sa</value></property>
| <property name="password"><value class="java.lang.String"></value></property>
| <property name="jndiName">java:/PortalDatasource</property>
| <property name="minSize">0</property>
| <property name="maxSize">10</property>
| <property name="blockingTimeout">1000</property>
| <property name="idleTimeout">100000</property>
| <property name="transactionManager"><inject bean="TransactionManager"/></property>
| <property name="cachedConnectionManager"><inject bean="CachedConnectionManager"/></property>
| <property name="initialContextProperties"><inject bean="InitialContextProperties"/></property>
| </bean>
|
| <bean name="PortalDatasource" class="java.lang.Object">
| <constructor factoryMethod="getDatasource">
| <factory bean="PortalDatasourceBootstrap"/>
| </constructor>
| </bean>
|
| </deployment>
|
components.xml - create entity manager and bind to JNDI
| <components xmlns="http://jboss.com/products/seam/components"
| xmlns:core="http://jboss.com/products/seam/core"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-1.1.xsd
| http://jboss.com/products/seam/components http://jboss.com/products/seam/components-1.1.xsd">
|
| <core:init jndi-pattern="@jndiPattern@" debug="true" />
|
| <core:pages no-conversation-view-id="/main.xhtml" />
|
| <core:manager conversation-timeout="120000"
| concurrent-request-timeout="500" conversation-id-parameter="cid"
| conversation-is-long-running-parameter="clr" />
|
| <core:ejb installed="true" />
|
| <core:managed-persistence-context name="PortalDatabase"
| auto-create="true"
| persistence-unit-jndi-name="java:/PortalEntityManagerFactory" />
|
| <component name="StringConverter"
| class="javax.faces.convert.CharacterConverter" />
|
| </components>
|
persistence.xml - Define persistence unit reference datasource and entity manager
| <persistence>
| <persistence-unit name="portal">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/PortalDatasource</jta-data-source>
| <properties>
| <property name="hibernate.hbm2ddl.auto" value="update"/>
| <property name="hibernate.cache.use_query_cache" value="true"/>
| <property name="hibernate.show_sql" value="true"/>
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/PortalEntityManagerFactory"/>
| </properties>
| </persistence-unit>
|
| </persistence>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994492#3994492
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994492
19 years, 7 months
[Installation, Configuration & Deployment] - 10:53:55, 671 ERROR [MainDeployer] could not create deploymen
by manoharshetty
I successfully deploy my application in jboss 4.0 ,but when I start JBOSS I get the following error.Please help.
Thanks Manohar.
Bean : Trader
Section: 22.2
Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods in the <ejb-class> element.
Info : Class not found on 'com.genuitec.trader.ejb.TraderSession': Unexpected error during load of: com.genuitec.trader.ejb.TraderSession, msg=com/genuitec/trader/ejb/TraderSession (Unsupported major.minor version 49.0)
10:53:55,671 ERROR [MainDeployer] could not create deployment: file:/C:/j2ee/jboss-4.0.0/server/default/deploy/firstejb.jar/
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:553)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:889)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:745)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:693)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:396)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:293)
at org.jboss.Main.boot(Main.java:151)
at org.jboss.Main$1.run(Main.java:405)
at java.lang.Thread.run(Thread.java:534)
10:53:55,703 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/j2ee/jboss-4.0.0/server/default/deploy/jmx-console.war/
10:53:56,062 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/j2ee/jboss-4.0.0/server/default/deploy/management/web-console.war/
10:53:57,375 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Incompletely deployed packages:
org.jboss.deployment.DeploymentInfo@aa0ccc37 { url=file:/C:/j2ee/jboss-4.0.0/server/default/deploy/firstejb.jar/ }
deployer: org.jboss.ejb.EJBDeployer@15af049
status: Deployment FAILED reason: Verification of Enterprise Beans failed, see above for error messages.
state: FAILED
watch: file:/C:/j2ee/jboss-4.0.0/server/default/deploy/firstejb.jar/META-INF/ejb-jar.xml
altDD: null
lastDeployed: 1166370835468
lastModified: 1166370475093
mbeans:
10:53:57,609 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
10:53:57,828 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
10:53:57,843 INFO [JkMain] Jk running ID=0 time=0/62 config=null
10:53:57,859 INFO [Server] JBoss (MX MicroKernel) [4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)] Started in 21s:484ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994491#3994491
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994491
19 years, 7 months
[JBoss Seam] - seam-gen generates java.lang.StackOverflowError on self refe
by jdijkmeijer
Hi,
I've been playing with (seam-)gen the last few days and today I decided to upgrade to Seam 1.1 GA. I was very impressed by its capabilities, however with the last release I run into an stackoverflow error doing seam generate-entites which didn't occur on the CR2 release. The tables I refer to are self referential (child parent) and leaving out the reference to itself solves the problem but that's not realy an option for me now.
| create table if not exists subject (
| subjectid INTEGER NOT NULL AUTO_INCREMENT
| , info varchar(150)
| , firstname varchar(50)
| , lastname varchar(50) NOT NULL
| , email varchar(70)
| , PRIMARY KEY (subjectid)
| ) TYPE = InnoDB;
|
| create table if not exists role (
| roleid INTEGER NOT NULL AUTO_INCREMENT
| , info varchar(150)
| , parentid INTEGER
| , name varchar(50) NOT NULL
| , PRIMARY KEY (roleid)
| , INDEX parent_ind (parentid)
| , FOREIGN KEY (parentid) references role (roleid)
| ) TYPE=InnoDB;
|
|
Database is mysql 5.0, jdk: build 1.5.0_04-b05, os winxp sp2.
Can anybody point me to a solution or is this a bug?
thanks in advance.
Jeroen.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994490#3994490
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994490
19 years, 7 months
[JBoss jBPM] - Re: Problem testing Hello BPEL sample
by zauberlehrling
I have similar problems with the following environment:
1. jBoss BPEL 1.1 Beta2
2. jBoss AS 4.0.5GA
3. jwsdp-2.0
4. jdk 1.5.0_08
5. ANT 1.6.5
I've tried to call the hello-bpel-process with the following code:
public void test()
| {
| try {
| Properties properties = new Properties();
| properties.setProperty("java.naming.provider.url", "jnp://localhost:1099");
| properties.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| properties.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming.client");
| properties.setProperty("j2ee.clientName", "jbpmbpel-client");
| Service service = null;
| if (service == null) {
| InitialContext iniCtx = new InitialContext(properties);
| Object object = iniCtx.lookup("java:comp/env/service/Hello");
| service = (Service)object;
| String portTypeNS = "http://jbpm.org/examples/hello";
| Call call = service.createCall(new QName(portTypeNS, "GreeterPort"),"sayHello");
| String greeting = (String) call.invoke(new Object[] { "Olive" });
| System.out.println("Greeting: "+greeting);
| }
| } catch (Exception e) {
| e.printStackTrace();
| }
|
and I get the following exception:
javax.naming.NamingException: Cannot unmarshall service ref meta data, cause: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
| at org.jboss.ws.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:127)
| at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
| at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
| at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
| at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:135)
| at $Proxy0.lookup(Unknown Source)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at frank.DII.test(DII.java:51)
The exception is thrown by the command in line 51:
| Object object = iniCtx.lookup("java:comp/env/service/Hello");
|
If I try to contact the webservice with the following code:
| public void dii()
| {
| try {
| String endpoint = "http://localhost:8080/hello/greeter?wsdl&resource=hello.wsdl";
| QName qName = new QName(endpoint);
| ServiceFactory serviceFactory = ServiceFactory.newInstance();
| Service service = serviceFactory.createService(qName);
|
| Call call = service.createCall();
| call.setOperationName(new QName(endpoint,"sayHello"));
| call.setTargetEndpointAddress(endpoint);
|
| call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");
| call.setProperty(Call.OPERATION_STYLE_PROPERTY, "rpc");
|
| Object[] arguments = new Object[] {"wo"};
| Object result = call.invoke(arguments);
| System.out.println(""+result);
| } catch (Exception e) {
| e.printStackTrace();
| }
| }
|
I get the following exception in the server console:
| 15:02:26,791 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:48s:151ms
| 15:02:59,288 WARN [HandlerWrapper] RuntimeException in handler method, transition to DOES_NOT_EXIST
| 15:02:59,288 ERROR [HandlerChainBaseImpl] RuntimeException in request handler
| java.lang.NullPointerException
| at org.jbpm.bpel.integration.server.SoapHandler.getRequestParts(SoapHandler.java:355)
| at org.jbpm.bpel.integration.server.SoapHandler.sendRequest(SoapHandler.java:299)
| at org.jbpm.bpel.integration.server.SoapHandler.handleRequest(SoapHandler.java:186)
| at org.jboss.ws.handler.HandlerWrapper.handleRequest(HandlerWrapper.java:121)
| ...
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 15:02:59,294 ERROR [SOAPFaultExceptionHelper] SOAP request exception
| java.lang.NullPointerException
| at org.jbpm.bpel.integration.server.SoapHandler.getRequestParts(SoapHandler.java:355)
| at org.jbpm.bpel.integration.server.SoapHandler.sendRequest(SoapHandler.java:299)
| ....
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 15:02:59,305 WARN [HandlerWrapper] Handler is in state DOES_NOT_EXIST, skipping Handler.handleFault for: org.jbpm.bpel.integration.server.SoapHandler@1c60f74
|
At least this code contacted the bpel engine.
Best regards,
Frank
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994487#3994487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994487
19 years, 7 months
[JBoss Seam] - Request for feedback
by gavin.king＠jboss.com
So I finally got fed up with the limitations of JSF navigation rules and I went ahead and implemented a stateless navigation system for Seam. There were four main reasons why I wanted this:
(1) to centralize orchestration in one place, instead of having it split between pages.xml and faces-config.xml
(2) to be able to specify request parameters when redirecting
(3) to be able to specify conversation begin/end according to an outcome
(4) to be able to have a value binding which evaluates the outcome, in addition to the action method binding - this lets me get rid of the ugly outcomes returned by action methods, and reduces the coupling of the model to the view.
(5) to support various "result types", other than a JSF view (eg. a file download, a http error, etc).
What I have today can do what you can do with JSF navigation rules, for example:
<page view-id="/getDocument.jsp">
| <navigation>
| <outcome value="success">
| <redirect view-id="/editDocument.jsp"/>
| </outcome>
| <outcome value="not-found">
| <redirect view-id="/404.jsp"/>
| </outcome>
| </navigation>
| </page>
Is equivalent to:
<navigation-rule>
| <from-view-id>/getDocument.jsp</from-view-id>
| <navigation-case>
| <from-outcome>success</from-outcome>
| <to-view-id>/editDocument.jsp"</to-view-id>
| <redirect/>
| </navigation-case>
| <navigation-case>
| <from-outcome>not-found</from-outcome>
| <to-view-id>/404.jsp"</to-view-id>
| <redirect/>
| </navigation-case>
| </navigation-rule>
And:
<page view-id="*">
| <navigation action="#{documentHome.get}">
| <outcome value="success">
| <render view-id="/editDocument.jsp"/>
| </outcome>
| </navigation>
| </page>
Is equivalent to:
<navigation-rule>
| <navigation-case>
| <from-action>#{documentHome.get}</from-action>
| <from-outcome>success</from-outcome>
| <to-view-id>/editDocument.jsp"</to-view-id>
| </navigation-case>
| </navigation-rule>
But it can also do this:
<page view-id="/getDocument.jsp">
| <navigation outcome="#{documentHome.document!=null}">
| <outcome value="true">
| <redirect view-id="/editDocument.jsp"/>
| </outcome>
| <outcome value="false">
| <redirect view-id="/404.jsp"/>
| </outcome>
| </navigation>
| </page>
This lets you write a DocumentHome.get() method with a void return type! This is much more transparent to the model.
You can also do this:
<page view-id="/editDocument.jsp">
| <navigation action="#{documentHome.update}">
| <null-outcome>
| <redirect view-id="/document.jsp">
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
| </null-outcome>
| </navigation>
| </page>
(Yay!)
Soon I'll also add <begin-conversation/> and <end-conversation/> to the case handling. Eventually I'll also add support for other things in addition to and .
OK, so, what I need feedback on is the actual XML format. What I have there today is a little less verbose than the JSF XML, but has one higher level of indentation (which makes it more complex). The reason for this is that I want to allow different actions to specify different outcome expressions, and different lists of cases, eg:
<page view-id="/getDocument.jsp">
|
| <navigation action="#{documentHome.get}"
| outcome="#{documentHome.document!=null}">
| <outcome value="true">
| <redirect view-id="/editDocument.jsp">
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
| </outcome>
| <outcome value="false">
| <redirect view-id="/404.jsp"/>
| </outcome>
| </navigation>
|
| <navigation action="#{logout.logout}">
| <null-outcome>
| <redirect view-id="/login.jsp"/>
| <null-outcome>
| </navigation>
|
| </page>
So the question is should I go for something more similar to the JSF XML (one less level of nesting):
<page view-id="/getDocument.jsp">
|
| <navigation action="#{documentHome.get}">
| <outcome expression="#{documentHome.document!=null}"
| value="true"/>
| <redirect view-id="/editDocument.jsp">
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
| </navigation>
|
| <navigation action="#{documentHome.get}">
| <outcome expression="#{documentHome.document==null}"
| value="true"/>
| <redirect view-id="/404.jsp"/>
| </navigation>
|
| <navigation action="#{logout.logout}">
| <redirect view-id="/login.jsp"/>
| </navigation>
|
| </page>
Or does it make it easier to learn if we stay even more like standard JSF:
<page view-id="/getDocument.jsp">
|
| <navigation>
| <from-action>#{documentHome.get}</from-action>
| <outcome-expression>#{documentHome.document!=null}</outcome-expression>
| <from-outcome>true</from-outcome>
| <redirect>
| <to-view-id>/editDocument.jsp</to-view-id>
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
| </navigation>
|
| <navigation>
| <from-action>#{documentHome.get}</from-action>
| <outcome-expression>#{documentHome.document==null}</outcome-expression>
| <from-outcome>true</from-outcome>
| <redirect>
| <to-view-id>/404.jsp"</to-view-id>
| </redirect>
| </navigation>
|
| <navigation action="#{logout.logout}">
| <redirect>
| <to-view-id>/login.jsp"</to-view-id>
| </navigation>
|
| </page>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994482#3994482
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994482
19 years, 7 months
[JBoss Seam] - Future direction for Embeeded EJB
by jboss-Nth-Fan
Hi Gavin,
Congratulations on 1.1GA!, the framework part, is a jewel to show (and understand) the rest of Seam's capabilities, simple yet elegant, well done!
Now, given the two alternatives for Seam applications outside JBoss AS, (for us dealing with other AS (Weblogic and Websphere), what would you recommend today and the foreseeable future? Embedded EJB or Hibernate/JPA approach, for say, simple database web applications. (no MDBs)
Also, I?ve noted SeamGen produces Pojos, are there plans to support direct EJB generation ?
Finally, is there any possibility of Embedded EJB to become secondary given there is JBoss AS (Full container), and the recent added support for Hibernate/JPA?
Looking forward for the latest announced releases !
Yeyo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994469#3994469
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994469
19 years, 7 months
[JBoss Seam] - Re: Problem with DataModelSelection?
by jim.farley
More on this: it seems that the @DataModel variable is not being set up as a context variable for some reason. When the Seam phase listener looks for it (in selectDataModelRow()) to set its index to match the link index, it's not found in any context, so the wrapped ListDataModel's internal index remains unset (defaults to zero). Hence the first item is picked each time.
It still alludes me why my @DataModel is not being put into conversation context while the dvd example does behave as expected. To try to isolate the problem, I've restructured the code along the lines of the dvd example (specifically, the showorders.xhtml page), and lined up my components.xml, web.xml and faces-config.xml to the settings in the dvd example. Any ideas would be very welcome.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994466#3994466
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994466
19 years, 7 months
[JBoss Eclipse IDE (users)] - Error creating jboss configuration in eclipse on OSX 10.4
by minixman
All i get this error in my error log when i try and create a jboss configuration in eclipse on os x 10.4
Message: org/eclipse/jdt/internal/debug/ui/launcher/JavaLaunchConfigurationTab
error
| java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/debug/ui/launcher/JavaLaunchConfigurationTab
| at java.lang.ClassLoader.defineClass1(Native Method)
| at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
| at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
| at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
| at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
| at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
| at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
| at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
| at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:334)
| at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:386)
| at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:347)
| at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
| at org.jboss.ide.eclipse.launcher.ui.configuration.RemoteServerTabGroup.createTabs(RemoteServerTabGroup.java:42)
| at org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationAction.performAction(CreateLaunchConfigurationAction.java:70)
| at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction$1.run(AbstractLaunchConfigurationAction.java:103)
| at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
| at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction.run(AbstractLaunchConfigurationAction.java:106)
| at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
| at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
| at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
| at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1496)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
| at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3312)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2941)
| at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
| at org.eclipse.jface.window.Window.open(Window.java:796)
| at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1086)
| at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:383)
| at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
| at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:387)
| at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:329)
| at org.jboss.ide.eclipse.ejb3.wizards.ui.wizards.pages.JBossSelectionPage.createJBossConfiguration(JBossSelectionPage.java:139)
| at org.jboss.ide.eclipse.ejb3.wizards.ui.wizards.pages.JBossSelectionPage.access$0(JBossSelectionPage.java:137)
| at org.jboss.ide.eclipse.ejb3.wizards.ui.wizards.pages.JBossSelectionPage$2.widgetSelected(JBossSelectionPage.java:101)
| at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1496)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
| at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3312)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2941)
| at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
| at org.eclipse.jface.window.Window.open(Window.java:796)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.ClasspathContainerWizard.openWizard(ClasspathContainerWizard.java:230)
| at org.eclipse.jdt.ui.wizards.BuildPathDialogAccess.configureContainerEntry(BuildPathDialogAccess.java:241)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage.openContainerSelectionDialog(LibrariesWorkbookPage.java:820)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage.editElementEntry(LibrariesWorkbookPage.java:543)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage.editEntry(LibrariesWorkbookPage.java:441)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage.libaryPageCustomButtonPressed(LibrariesWorkbookPage.java:249)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage.access$0(LibrariesWorkbookPage.java:230)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.LibrariesWorkbookPage$LibrariesAdapter.customButtonPressed(LibrariesWorkbookPage.java:185)
| at org.eclipse.jdt.internal.ui.wizards.dialogfields.TreeListDialogField.buttonPressed(TreeListDialogField.java:167)
| at org.eclipse.jdt.internal.ui.wizards.dialogfields.TreeListDialogField.doButtonSelected(TreeListDialogField.java:385)
| at org.eclipse.jdt.internal.ui.wizards.dialogfields.TreeListDialogField.access$2(TreeListDialogField.java:381)
| at org.eclipse.jdt.internal.ui.wizards.dialogfields.TreeListDialogField$2.widgetSelected(TreeListDialogField.java:346)
| at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1496)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
| at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3312)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2941)
| at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
| at org.eclipse.jface.window.Window.open(Window.java:796)
| at org.eclipse.jdt.internal.ui.wizards.buildpaths.newsourcepage.ConfigureBuildPathAction.run(ConfigureBuildPathAction.java:62)
| at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
| at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
| at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
| at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1496)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
| at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3312)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2941)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
| at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
| at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
| at org.eclipse.core.launcher.Main.run(Main.java:977)
| at org.eclipse.core.launcher.Main.main(Main.java:952)
|
|
Session data
| eclipse.buildId=M20060629-1905
| java.version=1.5.0_06
| java.vendor=Apple Computer, Inc.
| BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
| Framework arguments: -keyring /Users/bencuthbert/.eclipse_keyring -showlocation
| Command-line arguments: -os macosx -ws carbon -keyring /Users/bencuthbert/.eclipse_keyring -consoleLog -showlocation
| This is a continuation of log file /Users/bencuthbert/JavaProjects/.metadata/.bak_0.log
| Created Time: 2006-11-05 15:45:20.386
|
|
And then i get one that says
An exception stack trace is not available.
Unhandled event loop exception
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994449#3994449
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994449
19 years, 7 months