[EJB 3.0] - The wiki is misleading...
by poswald
I know this is sort of a FAQ but I've read a lot of things and I'm still not sure I know what the right answer is.
When installing 4.0.4.GA using the graphical installer I feel like the all configuration should include everything that all of the others do. After picking that and installing I notice that the ejb3.deployer is missing. I went back through and tried it again with ejb3 and sure enough, I get new/different deployers. For instance, the ejb3.deployer is missing from the all config. This seems to contradict what the trailblazer says:
http://jira.jboss.com/jira/browse/JBINSTALL-44
anonymous wrote : Each configuration installs a different set of programming APIs, libraries, and deployers. The all, ejb3, and ejb3-cluster configurations support EJB 3.0.
So does all support ejb3 or not? If so then why is it missing these deployers? I feel like this should mention that all is not really everything. Really I feel like all should be changed to be everything or perhaps renamed.
Sorry if this is all laid out somewhere I didn't find.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958995#3958995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958995
19 years, 9 months
[News & Announcements] - jBPM 3.1.2 released
by rrajesh
jBPM version 3.1.2 and jBPM Process Designer version 3.0.11 have been released. These releases and the changelog can downloaded from the following sourceforge location:
http://sourceforge.net/project/showfiles.php?group_id=70542
JBoss jBPM - Version jBPM 3.1.2
Changes:
** Bug
* [JBPM-555] - Bad exception message
* [JBPM-593] - suspend() and resume() failing in JBPM 3.1
* [JBPM-637] - exception-handler can't use exception-class attribute with script-thrown exceptions
* [JBPM-645] - task is not blocking after save of process-instance
* [JBPM-654] - Cancelling a TaskInstance "performs" the task
* [JBPM-663] - Incorrect resolution of process variable values in script when variable is defined (or redefined) in sub-token context
* [JBPM-665] - JVM hangs because of inappropriate error handling
* [JBPM-667] - jBPM unable to pass null variables to bsh scripts
* [JBPM-673] - JbpmConfiguration.close() does not remove the instance from the internal map of instances
* [JBPM-678] - jbpm el expression exceptions are masked
* [JBPM-696] - Field Instanciator problems
** Feature Request
* [JBPM-664] - add documentation for configuration properties
* [JBPM-671] - add logs for sub process bindings
* [JBPM-684] - added getXxxx for database loadXxxx methods
** Task
* [JBPM-658] - correct equals comparison
* [JBPM-659] - added JbpmConfiguration.close()
* [JBPM-666] - report expression exception properly
* [JBPM-683] - enlarged length of message exception property
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958992#3958992
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958992
19 years, 9 months
[Security & JAAS/JBoss] - Problem accessing EJB unchecked method from a servlet (with
by Plukh
Hello, I'm stuck at the following problem. I have one EJB module and two web apps inside a single ear. Relevant parts of configuration files follow:
>From jboss.xml:
| <security-domain>java:/jaas/db_store</security-domain>
|
>From ejb-jar.xml:
| <method-permission>
| <unchecked/>
| <method>
| <ejb-name>ModerEJB</ejb-name>
| <method-intf>Home</method-intf>
| <method-name>create</method-name>
| </method>
| </method-permission>
|
>From jboss-web.xml #1:
| <security-domain>java:/jaas/db_store</security-domain>
|
>From jboss-web.xml #2:
| <security-domain>java:/jaas/other</security-domain>
|
>From login-config.xml:
| <application-policy name="db_store">
| <authentication>
|
| <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
| <module-option name="dsJndiName">
| DS/Standard
| </module-option>
| <module-option name="principalsQuery">
| SELECT usr_password FROM users WHERE usr_login = ?
| </module-option>
| <module-option name="rolesQuery">
| SELECT 'CommonUser', 'Roles' FROM users WHERE usr_login = ?
| </module-option>
| <module-option name="hashAlgorithm">SHA1</module-option>
| <module-option name="hashEncoding">hex</module-option>
| <module-option name="ignorePasswordCase">true</module-option>
| <module-option name="unauthenticatedIdentity">nobody</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
| <application-policy name = "other">
| <authentication>
| <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule"
| flag = "required">
| <module-option name="unauthenticatedIdentity">nobody</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
The bean itself is constructed by a helper (BeanHelper), located inside the ejb module - don't know if it makes a difference.
Now, on to the problem. I have a servlet in web app #2, which tries to create a bean (by calling an unchecked create() method). Only authorised users have access to the servlet (through BASIC authorization, if it matters). When the call to create() is made, it fails with the following exception (parts skipped for clarity):
| java.rmi.AccessException: SecurityException; nested exception is:
| javax.security.auth.login.FailedLoginException: No matching username found in Principals
| at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
| at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136)
| ...
| at ru.singlecity.ejb.BeanHelper.getModerBean(BeanHelper.java:216)
| ...
| Caused by: javax.security.auth.login.FailedLoginException: No matching username found in Principals
| at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:152)
| at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:206)
| ...
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:211)
| at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:135)
| at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
| ... 47 more
|
So - what am I doing wrong? The principal is already set (by the web app) and access to the method of the bean is set to unchecked... If the principal wasn't passed on to the EJB, it would've caused a different exception (see item #1 in the FAQ), but it hadn't. Any help would be greatly appreciated!
With best regards,
Victor Denisov.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958987#3958987
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958987
19 years, 9 months