[JBoss Seam] - Re: Unable to call a method on my statefull session bean
by bytor99999
"bsheward" wrote : My understanding is this:
|
| Seam calls the methods in your session beans when it encounters the action="#{name.action}" declarations, where name is the name of the Seam managed component, and action is the name of the method in the managed component.
|
| However, before the method actually gets called, the Seam interceptor gets invoked, which populates all the @In and @DataModelSelection annotated fields. After the method invocation, control is passed back to the Seam interceptor and it updates the contexts with the @Out and @DataModel annotated fields.
|
| Hope this helps...
|
Thanks, yes that helps, and I understood that. However, the Stateful Session bean is not being called. Nothing happens, or something happens but it just stays on the same page and does not reflect any changes and you can't tell anything happened. However, I know the bean is not being called because I logged some things in those methods to see if they were being called.
Is there a way to remote debug the JSF Phase and Seam calls with an IDE?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981831#3981831
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981831
19 years, 5 months
[JBoss Seam] - Re: Multiple select items in page scope with factories.
by petemuir
I'm not entirely sure whats going on here but I suspect something along these lines:
Request 1
All of the context variables/bean variables are empty so the Factory method is called for each.
Request 2
All of the context variables are empty, all of the bean variables are initialised (to the values from Request 1) as the bean is in the session scope. As the first context variable is null the Factory method is called for it and the bean variable updated. Bean values which are not null are outjected from the bean - thus all three context variables are now not empty. With the first one updated and the second two not.
I think it would be fair to say its a 'non-standard' pattern to outject into a shorted-lived scope than the scope of the outjecting bean.
I don't use the index strategy so can't really discuss patterns for it. If you want to use with PAGE scope (which is the best way to use I suppose) you need to use a SLSB to control it. Otherwise I would suggest using the STRING strategy with an unchanging unique identifier on the outjected object or the OBJECT strategy and use either the provided converters (for EJB3 entities, enums) or write your own.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981823#3981823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981823
19 years, 5 months
[JNDI/Naming/Network] - Re: Lost datasource
by awclemen
Hello Forum Folks,
I too, was having the exact same problem with the disappearing datasource. However, I think I found a solution. I thought it was odd that the DatabaseServerLoginModule would load the datasource parameter then be unable to find the datasource. I guess that it might be a class loader problem. so I changed the UseJBossWebLoader from false to true in the {jboss.root.directory}/server/{server-type}/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml file like so:
| <!-- A flag indicating if the JBoss Loader should be used. This loader
| uses a unified class loader as the class loader rather than the tomcat
| specific class loader.
| The default is false to ensure that wars have isolated class loading
| for duplicate jars and jsp files.
| -->
| <attribute name="UseJBossWebLoader">true</attribute>
|
And now, we have the datasource back again and the authentication module is running the queries. Now, since I have only one app running on my jboss, I don't think I will have any real problems, however, those with multiple apps may see more memory usage because the same jars need to be loaded for each app. There may be other side effects to this, I'm not certain (but I'll find out shortly). I'm sure the experts can chime in, in case I am total off-base here.
How this helps. And now, back to debugging the rest of my app.
--Andy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981822#3981822
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981822
19 years, 5 months
[JBoss jBPM] - Re: jbpm engine as a jar
by cocampo
I'm not sure on what do you mean by "how to start the engine", but you need to create the DB first (look for instructions for your particular DB vendor in the jBPM manual, chapters 5-8); obviously, you don't need to read the whole chapters, but the parts you're interested in. Also, you can look in the forum, as this "how to deploy jBPM in another app server" kind of question has been asked (and answered) several times before.
I'm using jBPM, and to use it I only need to deploy the jbpm-xxx.jar with my application (or to the lib directory of the app server), then invoke the methods to load the process definition (or recover the process instance if you have the proper id) and that's it, you'll have the engine running. You'll find useful the section 7.1 of the jBPM manual.
Regards.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981821#3981821
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981821
19 years, 5 months