I have the same problem under fedora 9 and JBoss developer studio 1.1 with its
included JBoss as
anonymous wrote : [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP01 (build:
SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657) :
I was runnung all under windows and everything was fine, now I installed
Hi Shane,
Maybe I should enumerate the benefits I see in this approach:
| +Suppress redundant (and error prone) information when you redirect
programatically to a rule specific method (that you also enforse with a
@Restricted with the already tested rule)
| +Modeling tools will be able to
Hi Shane,
Sorry if my last mail wasn't clear. I'll explain the idea by the mean of a
frequent example:
Let's imagine we have an application with 3 rules: client, commercial and
administrator : the client can see only its orders, the commercial can only see
the orders of his clients and the
Hi,
I'm learning Seam and its role extended features. It's a very big step compared
to JAAS but I recognize I expected a more adapted behavior :-/
In fact, the code is always full of test cases that redirect to the
corresponding method for a given role if( role1 ) doThis(); else doThat(); to
Hi,
I'm experiencing a strange problem: I can see my EJB3 bean under the web
console under the the path:
System/JMX MBeans/jboss.j2ee/jboss.j2ee:jar=MyEjbJar.jar...
it is clearely recognized as a Stateless EJB:
MBean Name: Domain Name:jboss.j2ee
| service:EJB3
|
Hi,
The problem was due to a rhstudio bug (I think), I resolved it by creating a
new EJB3 project and appending it to the existing ear. (When I use the new
project wizard for an ear, ejb 3 is not proposed. Even if I change the xml
files after that to be JEE 5, there's something (I don't know
Hi Raskri,
Your post was really useful for me, I found it as the second link in my first
googling attemp (jboss backing beans admin) ;-).
I'd like to know why JBoss doesn't supply a richer admin interface: there's no
way to see which JNDI path was applied to a resource, I still didn't find
