[Beginners Corner] - newbie doubt in jbossws client stubs
by santhoshitha
I have read that web service clients can use the dynamic proxy, dynamic invocation or static stub invocation methods to use the services.
I dont find any samples or documentation illustrating the stub and tie invocation mechanism for jbossws. I am trying to use a standalone java application which tries to use the web service running in jboss, using the stub and tie mechanism. I am able to perform look up and invocation using dynamic proxy and DII however.
Are there any tools present in jbossws to use this invocation mechanism?
Am I missing something? I presume that the client stub contains an implemetaion of the SEI, and wstools does not return any SEI implementation when doing a wsdl to java generation. It returns 2 interfaces, one is the SEI and another is a service interface(which i dont know how to interpret, and where it is used).
I am using jboss AS version 4.0.5.
Have I misinterpreted something or is my understanding right?
Any guidance in this regard will be appreciated.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997915#3997915
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997915
19 years, 3 months
[JBossWS] - newbie doubt about jbossws client stubs
by santhoshitha
I have read that web service clients can use the dynamic proxy, dynamic invocation or static stub invocation methods to use the services.
I dont find any samples or documentation illustrating the stub and tie invocation mechanism for jbossws. I am trying to use a standalone java application which tries to use the web service running in jboss, using the stub and tie mechanism. I am able to perform look up and invocation using dynamic proxy and DII however.
Are there any tools present in jbossws to use this invocation mechanism?
Am I missing something? I presume that the client stub contains an implemetaion of the SEI, and wstools does not return any SEI implementation when doing a wsdl to java generation. It returns 2 interfaces, one is the SEI and another is a service interface(which i dont know how to interpret, and where it is used).
I am using jboss AS version 4.0.5.
Have I misinterpreted something or is my understanding right?
Any guidance in this regard will be appreciated.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997914#3997914
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997914
19 years, 3 months
[JBoss Seam] - Seam injection fails
by beligum
Hi all,
Can someone tell me what I'm doing wrong here?
I'm trying to inject the stateless RegisterAjaxAction class in my stateful RegisterAction class.
Here's the code:
| @Stateful
| @Scope(CONVERSATION)
| @Name("register")
| public class RegisterAction implements IRegister
| {
| @In(create=true) @Out(required=false)
| private Person newUser;
| @In(create=true) @Out(required=false)
| private LoginEntity newLoginEntity;
|
| @In(create=true)
| private RegisterAjaxAction registerAjax;
|
| @In
| private EntityManager em;
|
| @Logger
| private Log log;
|
| //-----CONSTRUCTORS-----
| public RegisterAction()
| {
| }
|
| //GETTERS, SETTERS, etc
|
and the injected class:
| @Stateless
| @Name("registerAjax")
| public class RegisterAjaxAction implements IRegisterAjax, Serializable
| {
| //-----CONSTANTS-----
| private static final long serialVersionUID = 2280962782361193463L;
|
| //-----VARIABLES-----
| @In(create=true)
| private Person newUser;
| @In(create=true)
| private LoginEntity newLoginEntity;
|
| private ResourceBundle msg = ResourceManager.getInstance().getGeneralMessages();
| private ResourceBundle regMsg = ResourceManager.getInstance().getRegisterMessages();
|
| @In private EntityManager em;
|
| //-----CONSTRUCTORS-----
| public RegisterAjaxAction()
| {
| }
|
| //STUFF...
|
I get this error message:
| java.lang.IllegalArgumentException: could not set field value: register.registerAjax
| at org.jboss.seam.Component.setFieldValue(Component.java:1551)
| at org.jboss.seam.Component.injectFields(Component.java:1342)
| at org.jboss.seam.Component.inject(Component.java:1112)
| at org.jboss.seam.interceptors.BijectionInterceptor.bijectTargetComponent(BijectionInterceptor.java:48)
| 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:18)
| at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
| at org.jboss.seam.interceptors.OutcomeInterceptor.interceptOutcome(OutcomeInterceptor.java:23)
| 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:18)
| at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
| at org.jboss.seam.interceptors.ConversationInterceptor.endOrBeginLongRunningConversation(ConversationInterceptor.java:51)
| 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:18)
| at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
| at org.jboss.seam.intercept.RootInterceptor.createSeamInvocationContext(RootInterceptor.java:144)
| at org.jboss.seam.intercept.RootInterceptor.invokeInContexts(RootInterceptor.java:129)
| at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:102)
| at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:49)
| 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.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118)
| at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:57)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
| ... 91 more
| Caused by: java.lang.IllegalArgumentException: Could not set field value by reflection: RegisterAction.registerAjax on: com.acepostproduction.tumbolia.actions.RegisterAction with value: class org.jboss.seam.intercept.Proxy$$EnhancerByCGLIB$$a78d35da
| at org.jboss.seam.util.Reflections.set(Reflections.java:75)
| at org.jboss.seam.Component.setFieldValue(Component.java:1547)
| ... 135 more
| Caused by: java.lang.IllegalArgumentException
| at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
| at java.lang.reflect.Field.set(Field.java:656)
| at org.jboss.seam.util.Reflections.set(Reflections.java:61)
| ... 136 more
|
Thanks a lot,
Bram
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997913#3997913
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997913
19 years, 3 months
[JBoss jBPM] - Jbpm 3.0.3 to Jbpm 3.1.2 migration issue
by rpateatenservio
I am working on a Jbpm project that currently has process instances active in a production evironment, but we are looking to migrate from 3.0.3 to 3.1.2.
When testing against the production data with the jbpm-3.1.2.jar in the classpath, we come across an error in the workflow. Any task that is supposed to be suspended waiting for an action from an actor is ignored.
Using the production data in conjunction with jbpm3.1.2, I complete a task but instead of it continuing on and suspending at the next task needing an action, it schedules the necessary actions but is never suspended. All tasks are executed in the appropriate order until the last ending task is completed.
Are there any known issues of migrating process instances versioned on jbpm3.0.3 to 3.1.2? If so, what issues need to be addressed, and if not, are there any ideas of what I can do to address this issue?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997908#3997908
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997908
19 years, 3 months
[JBossCache] - Problem with transaction timeout [critical]
by jacek187
Hi
I'm using latest TreeCache 1.4.0SP1 with WebLogic 9.1.
There is a problem with transaction timeout. On WebLogic, when transaction timeouts server is dooing transacion synchronization in separate thread....
It causes problems with following scenario:
1. Thread A is invoking transactional method foo() (in SLSB etc). New transaction starts with timeout 30 sec.
2. Method foo() is making call into DB, putting/getting data from/into TreeCache and making businness operations. This is long runing method (60sec)
3. On end foo() method server is trying commit transaction, but this transaction is timed out, so now server start separate thread Y. Thread Y is making call into OrderedSynchronizationHandler.afterCompletion() synchronization handler. Main thred X is calling main code.
And this is problem, because in main looks like:
| try{
| FooManager.foo();
| }catch(RuntimeException e){
| logger.error("Exception catched:",e);
| }
| TreeCacheUtils.putIntoCache("KEY", "VALUE");
|
any exception from foo() method is catched and logged, and any next eny variable is putted into cache (and view with error message is rendered etc)
But there is a hazrd risk, because sometimes main code is making operation on TreeCache BEFORE thread Y is calling afterCompletion method!!!!!!
this causes unexpected effect, because TreeCache has still information about GloblTransaction (information about transactions is yet not updated in TXInterceptor). TreeCache is trying lock node with information about caller GlobalTransaction, but this transaction dosen't exist for weblogic TransactionManager!
And now when we looks in TreeCache logs we can see, that write lock is aquired and NEVER RELEASED!!!!!!!
2007-01-04 10:14:37,310 DEBUG - Attempting to lock node /NODE_KEY for owner GlobalTransaction:<192.168.141.1:2100>:1
2007-01-04 10:14:37,310 DEBUG - acquiring WL: fqn=/NODE_KEY, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=read owners=[GlobalTransaction:<192.168.141.1:2100>:1]
2007-01-04 10:14:37,310 DEBUG - upgrading RL to WL for GlobalTransaction:<192.168.141.1:2100>:1, timeout=10000, locks: Read lock owners: [GlobalTransaction:<192.168.141.1:2100>:1]
Write lock owner: null
2007-01-04 10:14:37,310 DEBUG - upgrading lock for /NODE_KEY
2007-01-04 10:14:37,310 DEBUG - acquired WL: fqn=/NODE_KEY, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=write owner=GlobalTransaction:<192.168.141.1:2100>:1
2007-01-04 10:14:37,310 ERROR - transaction entry not found for (gtx=GlobalTransaction:<192.168.141.1:2100>:1)
2007-01-04 10:14:37,310 DEBUG - Invoking method _put(null, /NODE_KEY, NODE_VALUE, Thu Jan 04 10:14:37 CET 2007, true) on cache.
2007-01-04 10:14:37,310 DEBUG - _put(null, "/NODE_KEY", NODE_VALUE, Thu Jan 04 10:14:37 CET 2007)
2007-01-04 10:14:37,310 DEBUG - Attempting to release locks on current thread. Lock table is {}
This is critical bug for me, because from now any operation on NODE_KEY causes org.jboss.cache.lock.TimeoutException: failure acquiring lock exception!
And i must restart server!!!!
Jacek
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997905#3997905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997905
19 years, 3 months