I've created an EJB3 application with some JPA entities. Some of these entities
have the notion of ownership. These entities have the getOwner() method, which
returns the principal name of the subject that once created the entity (via
sessionContext.getCallerPrincipal().getName()).
What I would
Adding localhost.localdomain indeed fixes the problem. It's weird that Fedora
doesn't have this for default.
Frank.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040807#4040807
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
"[EMAIL PROTECTED]" wrote : Is networking actually enabled on your machine?
Well, if your can read this reply, yes. The funny thing is that when I'm
working from my home network (eth1 wireless) it seems to boot normal. When
booting JBoss 4.2 at 'work' (eth0 wired), it doesn't. Will investigate o
The content of my /etc/hosts file is:
anonymous wrote :
| # Do not remove the following line, or various programs
| # that require network functionality will fail.
| ::1 localhost localhost.localdomain
| 127.0.0.1 localhost
|
View the original post :
http://www.jboss.com/index.htm
When I start JBoss AS 4.2.0.CR2 under a default Linux Fedora Core 6, I get the
following error followed by a container shutdown.
anonymous wrote :
| Caused by: java.lang.RuntimeException: Exception creating identity:
localhost.localdomain: localhost.localdomain
| at org.jboss.remoti
Hi,
I just came across a situation in which the sessionContext.getCallerPrincipal()
returns null because the principal was removed from the subject during logout,
which is OK. The funny thing is that, because AbstractServerLoginModule is not
removing any added roles, the RBAC still lets the 'nu
Hi,
I've got two EJB3 JAR, each hosting session beans living in different security
domains. Is it true that the JPA entities received from a session bean living
on security domain A, will be detached within the session bean living in the
other security domain B, thus disabling lazy-loading? Co
The error:
java.lang.IllegalArgumentException: Value must be a TreeModel or TreeNode
is probably caused by the JBoss classloading; most likely you have the tomahawk
library in both your EAR and your WAR. Removing the tomahawk library from the
WAR will solve the issue.
View the original post
Hi Tom,
I'm using JBoss Remoting 1.4.6.GA now in my integration tests (for an
application deployed on JBoss AS 4.0.5.GA) running Java 6, and the thing seems
to behave just fine.
Thanks for the work on this issue.
Regards,
Frank.
View the original post :
http://www.jboss.com/index.html?modu
The patch of jboss-remoting is quite simple. See:
http://jira.jboss.com/jira/browse/JBREM-659
I really don't get why this is taking so long for JBoss to tackle this issue (I
know, a support contract would probably help). If JBoss feels like this is a
Java6 bug, they could just call it a "work-ar
Hello,
Is there a patched jboss-remoting.jar for JBoss AS 4.0.5.GA that has a fix for
this issue? Apparently according to:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446627
jboss-remoting should be patched to use Class.forName instead of
ClassLoader.loadClass for loading array classes.
I experienced similar problems when trying to integrate JAX-WS RI into JBoss
AS. It almost feels like Sun and JBoss don't really care that much about the
capability of running the WS stacks on each others application servers. IMHO,
the best environment right now for SOA is: JBoss AS with JAX-WS
@RolesAllowed allows one to check whether a caller principal has a certain role
in a declarative way. Besides checking permissions on executed operations there
is also something I call entity ownership checking. This is where you want to
check whether the caller principal is allowed to update an
anonymous wrote : is gone, it's been replaced with EL expressions
s:hasRole and s:hasPermission.
Does this mean that the "view" will also have servlet container security
enabled on it? In my own Seam application I've places only the controller Seam
BBs within a security domain. Thus these com
I have an @Entity with composite @EmbeddedId primary key. When I do a query
like:
SELECT COUNT(*) FROM TheEntity AS theEntity WHERE theEntity.blablablabla
then everything works, but when I replace this with:
SELECT COUNT(theEntity) FROM TheEntity AS theEntity WHERE theEntity.blablabla
then Hiberna
mmm... yeah... my brain is some slower than my posting in this forum... :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991360#3991360
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991360
Hi,
I have 2 Seam-based web application WARs in one single EAR. Apparently if WAR1
has a @Name("login") component and WAR2 has also a @Name("login") component,
then Seam cannot seem to lookup the correct component, even if those two
components use different @LocalBinding and in each components.
I thought Seam was somehow managing that a single JSF lifecycle always got to
see the same stateless bean instance. Apparently I'm using the wrong
Maven2/Facelets port of the dvdstore to learn all about Seam...
http://vyzivus.host.sk/site-files/dvdstore.zip
View the original post :
http://www.
I have this @Stateless bean with a setName() and getName() and a process()
method. The first time I call process() via the page all is OK, but the second
time the page calls getName() first, which still contains the previous value.
Is there a way to clean this besides doing?
| public void pro
The following also did the trick:
|
| useFirstPass
| TheRoleIWantToAdd
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989397#3989397
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989397
Using a forward to a native j_security_check is indeed an easy way to use the
servlet container provided security features. But on the other hand, you're
mixing JSF with non-JSF stuff. I was more thinking of using a servlet filter to
do the client-login into the security domain when the username
I would like to use my JAAS login module in my Seam-based application to
protect some of the Seam EJB3 backing beans via EJB3 RBAC. I see that Seam 1.1
has a JaasAuthenticationProvider for this. How to use it? Looking at the source
code of Seam 1.1.0.CR1 I wonder whether this thing already works
RoleMappingLoginModule makes sense when the user already has a (JAAS JBoss
specific) role. The funny thing here is that, before your are capable of using
RoleMappingLoginModule, the user already must have a (JAAS JBoss specific) role
assigned by a login module. Thus the initial JAAS LoginModule
23 matches
Mail list logo
