If you're using annotations, this tag works as well ...
@ActivationConfigProperty(propertyName="subscriptionName",
propertyValue="Your-subscription-name"),
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956700#3956700
Reply to the pos
"[EMAIL PROTECTED]" wrote : Then that is an ejb3 bug.
Does this mean that you'll be reverting back to using "java:/jaas/" in
jboss.xml (or @SecurityDomain) in a future version?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954041#3954041
Reply to the post :
Actually, it gets even weirder. It is true that you need to remove
"java:/jaas/" in jboss.xml 's security-domain element. But that same prefix
must be present in the jboss-web.xml 's security-domain element otherwise the
web authentication doesn't work.
View the original post :
http://www.jbos
This thread has the answer.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78329
Apparently, the "java:/jaas/" must now be removed. Not that this is your fault,
but it would have been nice if this change have been documented in the release
notes. It's a pretty significant change.
Now
This is what I have for parsing of the jboss.xml file. Not much in the line of
tracing ...
2006-06-27 11:14:30,834 DEBUG [org.jboss.ejb3.Ejb3Module] Creating
jboss.j2ee:service=EJB3,module=pinkcommon-ejb.jar
2006-06-27 11:14:30,841 DEBUG [org.jboss.ejb3.security.JaccHelper] Initialising
JACC Co
To get the security domain settings I'm using jboss-web.xml and jboss.xml just
as I did in 4.0.3. There is nothing peculiar about them. And if I try to use
the @SecurityDomain annotation instead, I get the same problem. Here are the
files ...
http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd"
Oh, and here is the trace leading up to the error. It's as if jBoss is ignoring
the security domain entries in jboss-web.xml and jboss.xml.
anonymous wrote : 2006-06-27 10:12:06,082 TRACE
[org.jboss.security.SecurityAssociation] pushRunAsIdentity, runAs=null
| 2006-06-27 10:12:06,082 TRACE [or
OK, aside from a reinstall, I'm not sure what I did differently, but I now get
this error. It happens on first access of the application. This means that
deployment is happening correctly, but that for some reason it is either using
the default realm or ignoring the DatabaseServiceLoginModule.
cgriffith, I'm pretty much following the same configuration procedures that I
have for all previous versions of jBoss. I simply put my application-policy's
XML snippet into the login-config file. Usually after, the JAAS JNDI entry
shows up in the JNDIView and is accessible by my security-domain
That did not help. That said, I don't think the problem is with the
"security-domain" elements. I believe that for some unexplainable reason my
JAAS PinkRealm is not being created. I base that on the fact that when I invoke
the JNDIView tree, it doesn't show with the JAAS services.
I've reinsta
tefron, I've entries in jboss.xml and jboss-web.xml.
Here's jboss.xml
http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd";>
java:/jaas/PinkRealm
And here's jboss-web.xml
http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd";>
java:/jaas/PinkRealm
View the original post :
h
Here you go ...
http://www.jboss.org/j2ee/dtd/security_config.dtd";>
guest
java:/DefaultDS
SELECT PASSWD FROM
JMS_USERS WHERE USERID=?
SELECT ROLEID, 'Roles'
j2ee_junkie, I must have done something wrong when creating the post, because
the terminating element is in there.
anil, below is the relevant trace information. It looks like it loads OK.
anonymous wrote : 2006-06-26 11:05:15,553 DEBUG
[org.jboss.security.auth.login.XMLLoginConfigImpl] Try loa
Hi, I'm trying to migrate from 4.0.3SP1 to 4.0.4.GA. The last hitch that I have
is creating my security domain. Normally, I just add this application-policy
snippet to the login-cofig.xml file.
anonymous wrote :
|
|
|
|
HI, we have an EJB3 web application in our testing environment. Before long
we'll be migrating to production. I'm wondering if there are any scalability
gotchas that I should be worried about.
For example in jBoss 4.0.1 with EJB 2.1, I used to get
ApplicationDeadlockExceptions, until I discover
Bump
Still looking for the proper annotation to set a client ID for a durable topic
MDB subscriber. Any help would be appreicated.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920830#3920830
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
This is great. Is there also a way to set the client ID so that the topic can
distinguish subscribers?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919434#3919434
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&
Can someone pass on to me the annotations that I need to specify to make an MDB
a durable subscriber? I've looked through WIKI and the forums and have not
found anything.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918911#3918911
Reply to the post
Brian, this is great news. I'll keep a lookout for the next jBoss release.
Anil, sorry for hijacking your thread. I have used SiteMinder and I can safely
say that I MUCH prefer jBoss's authenitcation/authorization mechanism. It is
simple to configure (without all the SiteMinder policy files) and
Brian, if there is a way I can help, I'd be more than happy to do so.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917351#3917351
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917351
---
Our team's main need is really an enhancement to jBoss's existing SSO, that is
to handle SSO across multiple hosts on the same domain. A simple example would
be abc.sample.com and xyz.sample.com. I understand that JOSSO is capable of
this, but it does not appear that it works with 4.0.3 as of ye
Using EJB 1.1, CMP, and JAWS on jboss 3.2.1. I have a complex finder SQL as indicated
in the trace below. Under some conditions a finder parameter could be null. When this
happens, jBoss calls setNull(param, java.sql.NULL) instead of a more specific sql type
like java.sql.VARCHAR. Unfortunately,
Hi, I'm trying to convert an existing WAS 4.0 application to a jBoss application.
Obviously, a noble cause. I've got the CMPs and session beans taken care of. My last
hitch is in the web layer.
We stash a bunch of XML files in the /WEB-INF/config/validators directory within the
WAR. In a servle
23 matches
Mail list logo
