[Installation, Configuration & Deployment] - JBOSS 4.0.4 install issues on Windows XP media Center OS
by yskreddy2003
Hi All
I have installed Jboss 4.0.4 using installer GUI. before installing made sure I have valid JDK. even after setting JAVA_HOME I am getting following error. There is not much help in Install documentation to fix the issue..
any help is appreciated.
JDK environment:
C:\Program Files\jboss\bin>java -version
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode, sharing)
ERROR MESSAGE :
C:\Program Files\jboss\bin>run
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\Program Files\jboss\bin\\..
.
JAVA: C:\Sun\SDK\jdk\bin\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
.
CLASSPATH: C:\Sun\SDK\jdk\bin\lib\tools.jar;C:\Program Files\jboss\bin\\run.jar
.
===============================================================================
.
The system cannot find the path specified.
Press any key to continue . . .
-Krishna
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996204#3996204
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996204
19 years, 7 months
[JBoss Seam] - Problem with @End(beforeRedirect=true)
by ccurban
I have got a facelet-page named cc_distribution.xhtml
And a SFSB with one action method triggered by a commandLink from this page.
| @End(beforeRedirect=true)
| public String updateDistributionList() {
| .
| .
| .
| return "cc_distribution";
| }
Using the following navigation rule in my faces-config.xml:
| <navigation-rule>
| <navigation-case>
| <from-outcome>cc_distribution</from-outcome>
| <to-view-id>/view/manage/cc_distribution.xhtml</to-view-id>
| <redirect/>
| </navigation-case>
| </navigation-rule>
I thought the result would be something like that:
1. I hit the Link.
2. updateDistributionList() is executed
3 the conversation is ended before the redirect
4. redirect to the same page
Unfortunately the redirect occurs without the conversation ending. Any suggestions?
Happy Christmas.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996186#3996186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996186
19 years, 7 months
[JBoss jBPM] - Re: jBPM BPEL Beta2: invoke an external web service
by SergStone
Hi, Alex!
But there were some changes in the BPEL application descriptor (bpel-application.xml) as I can see. 1.1.Beta1 documentation introduces use of JMS in constructions like this:
<message-destination-ref-name>jms/atmRelation</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>ConsumesProduces</message-destination-usage>
along with a Relation servlet. org.jbpm.bpel.relation.jms.RelationServlet
1.1.Beta2 ATM example uses Integration servlet and no <resource-ref> or <message-destination-ref> elements.
Which one is correct? I specified for my external service, added to the bpel-application.xml but still couldn't get the example working. The error message has changed to
Caused by: java.lang.RuntimeException: service not found: service={ru:softech:HelloBook:warehouse}Warehouse
What's wrong?
Thank you in advance,
Serg
BTW, I'm wondering if BPEL extension supports clustering and if so what kind of clustering it supports and how?
Once again thanks a lot and Merry Christmas!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996181#3996181
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996181
19 years, 7 months
[EJB 3.0] - help required for JBOSS 4.0.4 GA and EJB 3.0 RC9
by priyavijayan1
Hi,
I am having a problem with EJB 3.0 . I am using
EJB-3.0_RC9-FD
jboss-4.0.4.GA
jdk 1.5
ant 1.6.5
package com.EJB3.application;
import com.EJB3.application.FacadeRemote;
import javax.naming.InitialContext;
import java.sql.Timestamp;
CODE
public class client
{
public static void main(String[] args)
{
try
{
InitialContext ctx = new InitialContext();
ctx.addToEnvironment("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
ctx.addToEnvironment("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
ctx.addToEnvironment("java.naming.provider.url","jnp://localhost:1099");
System.out.println("<------"+FacadeRemote.class.getName()+"------->");
FacadeRemote lFacadeRemote = (FacadeRemote) ctx.lookup(FacadeRemote.class.getName());
lFacadeRemote.createDepartment("Finance");
lFacadeRemote.createDepartment("Administration");
lFacadeRemote.createDepartment("Sales");
lFacadeRemote.assignEmployeeToDepartment(new Long(1),"Brijesh",31,"M");
lFacadeRemote.assignEmployeeToDepartment(new Long(1),"xxxx",31,"M");
lFacadeRemote.assignEmployeeToDepartment(new Long(2),"yyyy",31,"M");
}
catch(Exception ex)
{
System.out.println(ex);
}
}
}
and the run time exception I am getting is
Buildfile: C:\prototype\EJB3.0\application\build.xml
[echo] -------------1-----------
run:
[echo] -------------2-----------
[java] <------com.EJB3.application.FacadeRemote------->
[java] javax.naming.NameNotFoundException: com.EJB3.application.FacadeRemote not bound
prepare:
[echo] C:\jboss-4.0.4.GA
prepare:
[echo] C:\jboss-4.0.4.GA
compile:
deploy:
BUILD SUCCESSFUL
Total time: 28 seconds
Please help....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996174#3996174
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996174
19 years, 7 months
[EJB/JBoss] - Problem with Mysql for CMP
by Kentzhou
I use jboss default db hsqldb to run application with CMP, it is okay. But When I change the datasource to mysql, I got the errors as below.
It seems can not connect to db. But I the user name and password set in file mysql-ds.xml are correct.
Please help to identify the problem and to solve this issue. Thanks.
----------------Errors message here -----------------------
2006-12-24 22:10:58,108 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss-4.0.5.GA/server/default/deploy/todo.ear
2006-12-24 22:10:58,108 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/jboss-4.0.5.GA/server/default/deploy/todo.ear -> file:/C:/jboss-4.0.5.GA/server/default/deploy/todo.ear
2006-12-24 22:10:58,108 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:service=EjbModule,module=todo.jar
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused: connect
STACKTRACE:
java.net.SocketException: java.net.ConnectException: Connection refused: connect
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
at com.mysql.jdbc.MysqlIO.(MysqlIO.java:276)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:2666)
at com.mysql.jdbc.Connection.(Connection.java:1531)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:171)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:565)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:250)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:491)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:301)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:173)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:157)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:435)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:368)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:414)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy23.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy24.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
** END NESTED EXCEPTION **
Last packet sent to the server was 90 ms ago.); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused: connect
STACKTRACE:
java.net.SocketException: java.net.ConnectException: Connection refused: connect
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
at com.mysql.jdbc.MysqlIO.(MysqlIO.java:276)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:2666)
at com.mysql.jdbc.Connection.(Connection.java:1531)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:171)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:565)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:250)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:491)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:301)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:173)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:157)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:435)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:368)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
......
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996152#3996152
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996152
19 years, 7 months
[JBoss Seam] - Re: Avoiding the DRY Principle with beans
by fabio.ita04
First of all, I think this post is closelly related with original topic: build session beans that encapsulates commom business logic, taking advantage of Seam annotations (inheritance of annotaded members: @in, @out, @datamodel, @datamodelselection, @begin, @end, @destroy, etc).
Please tell me exatly the reasons you think the topics aren't related, so I'll be convinced to create a new topic.
The code I sent is just a draft based on original code. The implementations are ok, and what I see it's happening is problems with EJB proxying.
In the following codes, *Service refers to interfaces, and *Manager refers to Stateful Session Bean classes.
When I write single (direct) hierarchies
BusinessManager implements BusinessService
everything runs allright.
But I'll have to write interfaces UserService, CompanyService, EmployeeService, ContactService, etc... that closelly shares the same structure (methods save(), search(), select(), destroy(), etc...).
And worse: the implementations (BusinessManager) are identical in the vast majority of cases. Just in few cases a subclass will need to override the default BusinessManager behavior.
So ideally, the best thing to do would be:
| interface BusinessService (common Service method declarations)
|
| BusinessManager implements BusinessService (default implementations)
|
| interface UserService extends BusinessService (declares User related methods)
|
| UserManager extends BusinessManager implements UserService
| (UserService implementations and some BusinessManager overriding)
|
But in this case, only UserService methods are proxied in the UserManager objects (exception occurs when trying to invoke BusinessManager methods - the exception says the UserManager proxy don't have the related BusinessManager / BusinessService methods).
If needed, in the next reply I send the UserManager code I've mentionated.
Thanx
Fábio.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996151#3996151
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996151
19 years, 7 months
[JBoss Seam] - StackOverflowError and
by svadu
HI All,
Trying to run JBoss Seam on Resin under linux (works in my development environment under win xp).
Getting the following strange errors upon startup:
anonymous wrote :
| 01:28:30,148 INFO [AnnotationBinder] Binding entity from annotated class: org.emaps.dao.UserBean
| 01:28:30,148 INFO [EntityBinder] Bind entity org.emaps.dao.UserBean on table users
| 01:28:30,151 INFO [AnnotationBinder] Binding entity from annotated class: org.emaps.dao.CityBean
| 01:28:30,152 INFO [EntityBinder] Bind entity org.emaps.dao.CityBean on table NP
| 01:28:30,545 INFO [CollectionBinder] Mapping collection: org.emaps.dao.CountryBean.regionses -> REGIONS
| 01:28:30,545 INFO [CollectionBinder] Mapping collection: org.emaps.dao.RegionBean.districts -> DISTRICTS
| 01:28:30,686 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.LocalOnlyContextFactory, java.naming.factory
| .url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 01:28:30,691 INFO [DatasourceConnectionProvider] Using datasource: java:/EmapsDS
| [01:28:31.209] java.lang.RuntimeException: exception invoking: startup
| [01:28:31.209] at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:112)
| [01:28:31.209] at org.jboss.seam.Component.callComponentMethod(Component.java:1799)
| [01:28:31.209] at org.jboss.seam.Component.callCreateMethod(Component.java:1739)
| [01:28:31.209] at org.jboss.seam.Component.newInstance(Component.java:1728)
| [01:28:31.209] at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:152)
| [01:28:31.209] at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:126)
| [01:28:31.209] at org.jboss.seam.init.Initialization.init(Initialization.java:430)
| [01:28:31.209] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
| [01:28:31.209] at com.caucho.server.webapp.Application.start(Application.java:1647)
| [01:28:31.209] at com.caucho.server.deploy.DeployController.startImpl(DeployController.java:621)
| [01:28:31.209] at com.caucho.server.deploy.DeployController.restartImpl(DeployController.java:584)
| [01:28:31.209] at com.caucho.server.deploy.StartAutoRedeployAutoStrategy.alarm(StartAutoRedeployAutoStrategy.java:176)
| [01:28:31.209] at com.caucho.server.deploy.DeployController.handleAlarm(DeployController.java:742)
| [01:28:31.209] at com.caucho.util.Alarm.handleAlarm(Alarm.java:339)
| [01:28:31.209] at com.caucho.util.Alarm.run(Alarm.java:309)
| [01:28:31.209] at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:516)
| [01:28:31.209] at com.caucho.util.ThreadPool.run(ThreadPool.java:442)
| [01:28:31.209] at java.lang.Thread.run(Thread.java:595)
| [01:28:31.209] Caused by: java.lang.reflect.InvocationTargetException
| [01:28:31.209] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| [01:28:31.209] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| [01:28:31.209] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| [01:28:31.209] at java.lang.reflect.Method.invoke(Method.java:585)
| [01:28:31.209] at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
| [01:28:31.209] at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:102)
| [01:28:31.209] ... 17 more
| [01:28:31.209] Caused by: java.lang.StackOverflowError
| [01:28:31.209] at org.jboss.resource.JBossResourceException.getCause(JBossResourceException.java:132)
| [01:28:31.209] at javax.resource.ResourceException.getLinkedException(ResourceException.java:78)
| [01:28:31.209] at org.jboss.resource.JBossResourceException.getCause(JBossResourceException.java:132)
| [01:28:31.209] at javax.resource.ResourceException.getLinkedException(ResourceException.java:78)
|
skipped (very long repeating stack trace)...
anonymous wrote :
| [01:28:31.240] at javax.resource.ResourceException.getLinkedException(ResourceException.java:78)
| 01:28:31,178 WARN [LocalTxDataSource] Throwable while attempting to get a new connection: null
| 01:28:31,567 INFO [FacesConfigurator] Reading standard config org/apache/myfaces/resource/standard-faces-config.xml
|
Using pojo + jpa here.
Any idea what this could be? Completely the same deployment works on another PC under windows...
Thanks in advance,
Siarhei
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996150#3996150
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996150
19 years, 7 months
[JBoss Seam] - Re: Avoiding the DRY Principle with beans
by fabio.ita04
Hi,
I'm trying to implement Session Bean Inheritance, so common business methods (like defaults for search and save) are encapsulated on a superclass, and subclasses overrides just the methods they have a particular behavor. Superclasses can have properties that holds bean state. Multiple interface inheritance is desirable too. Ex:
| interface BusinessService {
| save();
| search();
| ...
| Object getMyProperty(); // holds some state
| }
|
| class BusinessManager implements BusinessService {
| save() { ... };
| search() { ... };
| ...
|
| Object myProperty;
|
| public getMyProperty() {
| // defaults to subclasses
| return myProperty;
| }
| }
|
| interface UserService {
| login();
| }
|
| @Stateful
| class UserManager extends BusinessManager implements UserService {
| login() { ... };
|
| // overrides default BusinessManager behavior
| @Override
| save() {
| if (checkIfLoginIsUnique())
| super.save();
| }
| }
|
When I write Session Beans with no inheritance, everything works fine, but with inheritance, I can't get page rendering work, because JSF can't find superclass properties that holds bean states, and even superclass methods.
| com.sun.facelets.tag.TagAttributeException: index.xhtml @14,44
| test="#{empty myBean.myProperty}": Bean: myBean$$EnhancerByCGLIB$$e16dcde2, property: myProperty
|
| java.lang.IllegalArgumentException: method not found: myMethod for component: myBean (check that it is declared on the session bean business interface)
| ...
| java.lang.NoSuchMethodException: MyService$$EnhancerByCGLIB$$e16dcde2.myMethod()
|
Any Help?
Thanx,
Fábio.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996131#3996131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996131
19 years, 7 months
[JBoss Seam] - Problem with Registration Example
by rvaneperen
I tried to run the example as per the instruction at http://docs.jboss.com/seam/1.0.0.CR2/reference/en/html/tutorial.html. I am running version "JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)"using the installer and selecting "all" to install all extensions. I am using jdk1.5.0_09. I am getting the following error. Does anyone know what is wrong?
12:49:42,324 INFO [EARDeployer] Init J2EE application: file:/F:/JBoss/jboss4_ejb3/server/default/deploy/jboss-seam-registration.ear
| 12:49:42,667 ERROR [MainDeployer] Could not create deployment: file:/F:/JBoss/jboss4_ejb3/server/default/tmp/deploy/tmp35059jboss-seam-registration.ear-contents/jboss-seam-registration.jar
| org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the right xml schema or define a valid DOCTYPE!
| at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:339)
| at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)
| at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:541)
| 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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
| at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy32.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Here is the ejb-jar file:
<?xml version="1.0" encoding="UTF-8"?>
| <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
| version="3.0">
|
| <interceptors>
| <interceptor>
| <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
| </interceptor>
| </interceptors>
|
| <assembly-descriptor>
| <interceptor-binding>
| <ejb-name>*</ejb-name>
| <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
| </interceptor-binding>
| </assembly-descriptor>
|
| </ejb-jar>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996123#3996123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996123
19 years, 7 months
[JBoss Portal] - JBoss Portal Security - You're losing your way...
by bsmithjj
As I look into this more, look at the source code for 2.6, the wiki link you supplied, etc. I really am beginning to think that in some ways, you're losing your way with the security layer of JBoss Portal. All I want to do is customize the login for the dang thing for my environment. Instead, I find suggestions of JACC, and the promise of a large amount of volatility in the part of the portal related to authentication/authorization either with JAAS or JACC (and let's not forget that there's really no good documentation for customizing security now in any of the releases - download one and see if you can figure out from the docs how to get started with customizing security)
The wiki link you supplied earlier suggests that you are attempting to create a first class framework for authorization as part of developing point releases of JBoss Portal; furthermore, it suggests that you expect to have to create several versions of the security framework in the path to whatever you're trying to reach - the first version will be based on JACC...what's the next version going to be based on?
Are corporate customers really clamoring for such a massive overhaul in the security layer in a point release of the portal? We're customers - all we want is the portal/portlet functionality and the ability to customize security similar to what was available in 2.0.X versions of the portal. We like the page model, themes, the overall ease of developing/deploying portlets, etc. We also like how easy it has been in the past to customize security. We like the 2.6 DR1 release a lot - what we don't like is the fact that the security integration point is a moving target.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996119#3996119
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996119
19 years, 7 months
[JBoss Eclipse IDE (users)] - Re: XDoclet shortcoming?
by scramer
Hello again.
I got the problem narrowed down a little... While studying the xdoclet source I found a way of generating the <foreign-key-mapping/>
I just had to add an undocumented setting:
| /**
| * Getter for CMR Relationship.
| * @return The personal data for this patient.
| *
| * @ejb.interface-method view-type = "local"
| * @ejb.relation name = "Patient-To-Person"
| * role-name = "Patient-To-Person-Role"
| * target-ejb = "CMPPerson"
| * target-role-name = "Patient-Is-Person-Role"
| * target-multiple = "false"
| *
| * @jboss.relation-mapping style = "foreign-key"
| */
| public abstract CMPPersonLocal getPerson();
|
which is completly GREAT. But now I run into the next problem: The generated jbosscmp-jdbc.xml is messed up:
| <ejb-relation>
| <ejb-relation-name>Patient-To-Person</ejb-relation-name>
| <foreign-key-mapping/>
| <ejb-relationship-role>
| <ejb-relationship-role-name>
| Patient-To-Person-Role
| </ejb-relationship-role-name>
| <key-fields/>
| </ejb-relationship-role>
| <ejb-relationship-role>
| <ejb-relationship-role-name>
| Patient-Is-Person-Role
| </ejb-relationship-role-name>
| <key-fields/>
| </ejb-relationship-role>
| </ejb-relation>
|
It is AT LEAST having an excess <key-fields/> in the relationship role named "Patient-Is-Person-Role"; and on top of that it seems to be lacking <cmr-field-name/> and <cmr-field-type/>.
Where am I going wrong now?
Greetings
Sebastian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996106#3996106
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996106
19 years, 7 months
[JBoss Portal] - Error Displaying Flash in JBoss Portal 2.4.1.CR2
by 733nb
Environmental info follows:
Release ID: JBoss [Zion] 4.0.5.GA
Home Dir: E:\Apache Group\jboss-portal-2.4.1-CR2
Java version: 1.4.2_09,Sun Microsystems Inc.
Java VM: Java HotSpot(TM) Server VM 1.4.2_09-b05,Sun Microsystems Inc.
OS-System: Windows 2000 5.0,x86
Database: Oracle 9i
I'm having two problems with running the flash plugin in Jboss Portel window.
1. When I try to set the height and width on the object tag to a 100%, the window goes totally blank, like I didn't have any statements in the jsp. However, if I set the width="100%" and set a specific height="450" the flash plugin will be displayed.
<center>
| <object width="100%" height="100%">
| <param name="movie" value="<%= request.getAttribute("flashurl") %>"/>
| <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="100%"/>
| </object>
| </center>
2. The second problem that I'm seeing when trying to view a flash plungin in a Portlet Window is when I specify the classid on the object tag, the footer of the Portlet Window gets clipped off.
<center>
| <object width="100%" height="455"
| classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" >
| <param name="movie" value="<%= request.getAttribute("flashurl") %>"/>
| <embed src="<%= request.getAttribute("flashurl") %>" width="100%" height="455"/>
| </object>
| </center>
I need to specify the classid so as the flash plugin can make an Ajax call back into the server.
Any insight on how to resolve the above issues would be greatly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996104#3996104
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996104
19 years, 7 months
[EJB 3.0] - Getting javax.ejb.EJBException: Application Error: tried to
by PamJoshua
Hi,
I am using Jboss-4.0.3sp1 and EJB.
My Issue:
In my application, i do a search. During this search, it goes for an EJB call.
Now, if suppose a user cancels the search operation, immediatly after doing the search then i am getting the error below. Its throwing this error on the console and throwing it to the app screen also. Also, sometimes it doesnt throws this error but takes around 5 seconds to return the application to its normal form (By showing an hour glass)
I can understand that its trying to destroy that EJB call and the EJB is already engaged in a transaction means the EJB is still not passivated.
But i am not able to find the rootcause of this problem.
I am getting an EJBException. Here is the error log:
**********************************************
15:53:39,585 ERROR [LogInterceptor] EJBException in method: public abstract void javax.ejb.EJBObject.remove() throws java.rmi.RemoteException,javax.ejb.RemoveException:
javax.ejb.EJBException: Application Error: tried to enter Stateful bean with different tx context, contextTx: TransactionImpl:XidImpl[FormatId=257, GlobalId=dscp12800/119, BranchQual=, localId=119], methodTx: TransactionImpl:XidImpl[FormatId=257, GlobalId=dscp12800/120, BranchQual=, localId=120]
at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:268)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:335)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
at org.jboss.ejb.Container.invoke(Container.java:873)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406)
at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
**********************************************
I tried to search in the forums about this exception but didnt got much help besides synchronizing the EJB call.
I dont want to show this error to the user and also, i dont want this error to come on Jboss console. Is it possible to find a solution without touching the EJB code? For the GUI part i am using Swings.
I am strucked in this problem for long. It would be really great if someone suggests some solution.
Thanks in Advance
PamJoshua
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996099#3996099
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996099
19 years, 7 months