[JBoss Seam] - dynamic form generation, seam, conversations
by theTom
Hi!
I am doing dynamic form generation with jboss, jsf and seam.
But I have problems with conversations when trying to use them with the dynamic forms. It seems that I am loosing the conversation context.
So, I have two buttons.
ButtonA calls a method, annotated with @Begin from a statefull session bean.
ButtonB calls another method, annotated with @End from the same bean.
If I put these two buttons in a .xhtml file (commandButton) the long running conversation works, and the method annotated with @Remove and @Destroy is called when I press ButtonA and then ButtonB.
But when I am generating these buttons programmatically, the long running conversation doesn't behave as it should.
Any hints where I should start to debug this behaviour?
The "static" buttons are done in this way:
| <h:commandButton id="doB" value="doB"
| action="#{x.doB()}"/>
|
And here one of the dynamic buttons:
| HtmlCommandButton cancelButton = new HtmlCommandButton();
| cancelButton.setId("doB");
| cancelButton.setValue("doB");
|
| // create method binding
| FacesContext context = FacesContext.getCurrentInstance();
| Application app = context.getApplication();
| MethodBinding mb = app.createMethodBinding("#{x.doB}", new Class[] {});
| cancelButton.setAction(mb);
|
| sheet.getChildren().add(cancelButton);
|
thx in advance,
tom
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062602#4062602
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062602
18Â years, 10Â months
[EJB/JBoss] - method-permission being ignored
by spiperoglou
JBoss 4.0.5GA - EJB 2.1
I'm trying to implement authentication for my EJBs. Before I even start with LoginModules, CallbackHandlers etc., the first thing I did was amend my ejb-jar.xml to require a role ("SomeUser") when accessing methods of my EJB ("TemplateManager"). Without changing anything on the client, I ran it again expecting to see authentication errors since there is no authentication, but instead the client ran fine, calling methods on the bean without any authentication. In other words, the EJB is still completely unsecured.
<security-role>
| <role-name>SomeUser</role-name>
| </security-role>
|
| <method-permission>
| <role-name>SomeUser</role-name>
| <method>
| <ejb-name>TemplateManager</ejb-name>
| <method-name>*</method-name>
| </method>
| </method-permission>
In my ejb methods, I do:
LOG.debug("Principal: "+sessionContext.getCallerPrincipal());
| LOG.debug("isCallerInRole: "+sessionContext.isCallerInRole("SomeUser"));
which produces:
17:57:19,707 DEBUG [TemplateManagerBean] Principal: anonymous
| 17:57:19,707 DEBUG [TemplateManagerBean] isCallerInRole: false
What's wrong? Why is JBoss ignoring the method-permission stuff in ejb-jar.xml?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062601#4062601
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062601
18Â years, 10Â months
[JBoss Seam] - Re: EntityHome usage recommended?
by matt.drees
So, after a little searching...
contactlist, dvdstore, quartz, seampay, wiki, and ui each use EntityHome.
Overriding EntityHome is used in quartz, seampay, and wiki.
Defining entity-home in components.xml is used in contactlist, dvdstore, quartz, seampay, and ui.
seampay, interestingly enough, both overrides EntityHome *and* defines it in components.xml (<pay:payment-home>), which I hadn't realized you could do...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062599#4062599
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062599
18Â years, 10Â months
[JBossCache] - Re: Write lock is not released
by metastaz
"manik.surtani(a)jboss.com" wrote : It looks like the current WL holder and the RL requestor are not the same:
|
|
| | ... could not be acquired by <zzz:4256>:162303 ...
| |
|
| and
|
|
| | ... Write lock owner: Thread[ReportDataTaskRunner-20521017-1,5,jboss] ...
| |
|
|
|
| A thread dump would be very helpful.
|
| In addition, what transaction manager (if any) have you configured for JBoss Cache (the TransactionManagerLookup attribute in your JBoss Cache cfg xml)?
Oh, I see first time thread acquired WL without GlobalTransaction but then it tries to get a RL having one.
As for TransactionManagerLookup - we have TransactionManagerLookupClass attribute set to org.jboss.cache.JBossTransactionManagerLookup
Thank you,
Stas.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062597#4062597
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062597
18Â years, 10Â months