Hey guys, the $50 was a joke. I have looked at the code and I have no idea how
much it would take to get you guys to fix this, but I know my company won't pay
for it, but my dev team would probably chip in some money, that part was
serious. Sorry if the joke didn't come across, it wasn't meant
The JIRA priority got bumped down?! I was doing my bi-annual check in on this
requested feature and found that JBPORTAL-2186 is now optional? I could have
sworn it was high priority last time.
Apparently I'm the only person that wants to publish content from my
application via WSRP standards
I noticed this JIRA issue was entered, JBPORTAL-2186, but it appears to not be
scheduled against a release?
There are a couple of past threads on the forums requesting this and I've
pestered developers on the blogs. I thought I'd continue my annoying behavior
and officially request that this
We have a working JBoss cluster setup and we have a jms topic that is only
being used on the local machine to leverage asynchronous behavior. We don't
want it in the HA JMS configuration. If a machine goes down and loses messages
that's fine. We'd actually prefer both machines to be processin
I traced through the jboss code and found the problem. It appears that the
managed connection factory stores drivers in a map of some sort using the url
as the key. In my case I had 2 ds.xml files deployed with different jndi
names, but the same url. One of them had the actual OracleDriver sp
I am trying to setup an Oracle proxy_user login configuration where there is a
single user with connect only privileges configured in the ds.xml file and then
each connection calls Oracle's (proprietary) openProxySession method to scope
the connection's permissions to a user with specific access
