[JBoss/Spring Integration] - jboss-spring.xml in ear?
by apaeth
I have a very simple EJB test application that I've been working on that uses spring. I have been able to get spring working inside of jboss by simply placing the jboss-spring.xml inside the deploy directory. However, I have had no luck getting it to work in an ear file. My current ear,jar, and application.xml are as follows:
sc.ear
| /META-INF
| application.xml
| sc_common.jar
| sc_ejb.jar
|
sc_ejb.jar
/META-INF
| jboss.xml
| ejbjar.xml
| jbosscmp-jdbc.xml
| _classes are here_
application.xml
| <!DOCTYPE application PUBLIC
| "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
| "http://java.sun.com/dtd/application_1_3.dtd">
|
| <application>
| <display-name>Bundled Jars</display-name>
| <module>
| <ejb>sc_ejb.jar</ejb>
| </module>
| <module>
| <ejb>sc_common.jar</ejb>
| </module>
| </application>
|
I've tried placing the jboss-spring.xml in the following locations:
sc.ear/
sc.ear/META-INF/
sc.ear/sc_ejb/
sc.ear/sc_ejb/META-INF
no luck with any of these. The spring deployer never seems to see the jboss-spring.xml file.
I'm curently using the 1.3 deployer (JDK 5 version), JDK 1.5, Spring 1.2 (soon to be 2.x), Jboss 4.0.3RC1
Any help would be greatly appreciated.
Thanks,
Adam
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976346#3976346
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976346
19 years, 7 months
[JBoss Seam] - Seam with Jbpm - Operation not allowed.
by trouby
Hey,
I am trying to run SEAM with JBPM over Glassfish,
Well, after fighting with some missing jars and confs it seems like the application is deployed fine :)
When I try to execute a method that is annotated with @CreateProcess(definition="mydefinition") I get an "Operation not allowed" exception,
I assume this is related to transactions, but I have no clue why this is happening, also it might be a JBPM issue and not SEAM's, so I hope I didn't misake by choosing seam's forum.
here's the full stack trace:
| at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:251)
| at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:205)
| at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
| at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
| Caused by: java.lang.IllegalStateException: Operation not allowed.
| at com.sun.enterprise.distributedtx.UserTransactionImpl.checkUserTransactionMethodAccess(UserTransactionImpl.java:112)
| at com.sun.enterprise.distributedtx.UserTransactionImpl.getStatus(UserTransactionImpl.java:247)
| at org.jboss.seam.util.Transactions.isTransactionActiveOrMarkedRollback(Transactions.java:30)
| at org.jboss.seam.core.ManagedJbpmContext.getJbpmContext(ManagedJbpmContext.java:69)
| 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.seam.util.Reflections.invoke(Reflections.java:13)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:32)
| at org.jboss.seam.Component.callComponentMethod(Component.java:1334)
| at org.jboss.seam.Component.unwrap(Component.java:1350)
| at org.jboss.seam.Component.getInstance(Component.java:1276)
| at org.jboss.seam.Component.getInstance(Component.java:1253)
| at org.jboss.seam.Component.getInstance(Component.java:1235)
| at org.jboss.seam.core.ManagedJbpmContext.instance(ManagedJbpmContext.java:112)
| at org.jboss.seam.interceptors.BusinessProcessInterceptor.createProcess(BusinessProcessInterceptor.java:131)
| at org.jboss.seam.interceptors.BusinessProcessInterceptor.afterInvocation(BusinessProcessInterceptor.java:107)
| at org.jboss.seam.interceptors.BusinessProcessInterceptor.manageBusinessProcessContext(BusinessProcessInterceptor.java:60)
| 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.seam.util.Reflections.invoke(Reflections.java:13)
| at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90)
| at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60)
| at org.jboss.seam.interceptors.RemoveInterceptor.removeIfNecessary(RemoveInterceptor.java:39)
| 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.seam.util.Reflections.invoke(Reflections.java:13)
| at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90)
| at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60)
| at org.jboss.seam.ejb.SeamInterceptor.aroundInvokeInContexts(SeamInterceptor.java:73)
| at org.jboss.seam.ejb.SeamInterceptor.aroundInvoke(SeamInterceptor.java:45)
| 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 com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:505)
| at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:415)
| at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:189)
| at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3862)
| at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:184)
| ... 51 more
| |#]
|
here's my jbpm.cfg.xml file
| <jbpm-configuration>
| <jbpm-context>
| <service name="persistence">
| <factory>
| <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
| <field name="isTransactionEnabled"><false/></field>
| </bean>
| </factory>
| </service>
| <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory" />
| <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
| <service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory" />
| <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" />
| </jbpm-context>
| </jbpm-configuration>
|
Any idea?
Thanks a lot,
Asaf.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976342#3976342
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976342
19 years, 7 months
[JBoss Seam] - Re: Issues with JBoss Application Server
by petemuir
"jpemmasani" wrote : 1) I used to work with websphere server before. There when ever i deploy a war file all the files will store in expandable directory and for any small changes i used to hot deploy only those pages (for examples jsp). But I am not able to see that type of directory expect temp.
JBoss is different (for better or for worse!). Hot deploy is a bit tricky to get working. I use it fine with some ant tasks. Essentially you need to deploy the ear/war exploded, then you can copy facelets etc. into the exploded war and jboss will take care of making them available.
Hotcode replacement is another issue - Eclipse takes care of it when in debug mode. You can follow http://wiki.jboss.org/wiki/Wiki.jsp?page=EclipseSeamAutoDeploy if you use eclipse for packaging.
anonymous wrote : 2) I am not seeing the log out from my application. Because I am trying to connect oracle through jndi and each time if i try to log on it says username not found. I am not able to find where the applicaion is failing due to log from application is no where to be found.
JBoss logs everything (it uses log4j) to server.log. It's possible log4j isn't printing the messages, it's configuration is $JBOSS_HOME\server\default\conf\log4j.xml
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976341#3976341
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976341
19 years, 7 months