I have the same exact problem.
Running jboss-4.0.4.GA with a configuration from the separate installer with
all options checked on for ejb3.
Seems like this wasn't meant for a 'drop in replacement' for the jbossws in
that instance?
Would be nice to have it work though, I'm having all sorts o
I've been using JBossIDE for a while now but I'll have to admit, I'm getting
near the end of my rope in being patient with it constantly being broken. It
seems parts of it are broken more than its working. I've found it less than
clear in the forums on when a fixed version will be out and the
I've been using JBossIDE for a while now but I'll have to admit, I'm getting
near the end of my rope in being patient with it constantly being broken. It
seems parts of it are broken more than its working. I've found it less than
clear in the forums on when a fixed version will be out and the
Oh, perhaps I should add I'm using JBoss 4.0.1sp1. Thanks to anyone with any
insight to this issue... Doesn't seem popular as there's not much reference in
all of JASS forum/topic regarding this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875694#3875694
The jbosss.server.home.dir gets populated via jboss on startup so you don't
need to configure anything. Did you make your own key? Did you put it in the
conf directory for the jboss server instance you're running and make sure the
server.xml file section with the ssl (its default setting is fo
Did you try reading the wiki page regarding this? Its a great place to start:
http://www.jboss.org/wiki/Wiki.jsp?page=LdapLoginModule
Using this module will allow you to log in (authentication) and set up roles
(authorization).
View the original post :
http://www.jboss.org/index.html?module
Scott,
I am currently using a secure, one-way encryption method to store the
passwords. That is, once they're stored in the database, there is no way to
determine what they are -- the only choice a user has if they forget it, is to
make a new one. This helps secure the system internally fro
Are you sure you have the correct SQL for the select of the userRoles fro mthe
table? As you can see from the error itself, the SQL exception is telling you
that there is no table called ROLES whereas you have a table called userRoles.
I think you might have cut and pasted the original SQL st
