I must agree. Perhaps I don't know all the facts, but from external
appearances this was a somewhat shamefull way for the JBoss Group to
act, considering all that these developers have put into JBoss. A
statement from the JBoss group on what happened to Greg's and the other
developer's access,
Brian Wallis wrote:
On Thu, 7 Aug 2003 11:34 pm, [EMAIL PROTECTED] wrote:
Yes, I'd like to know as well. We will address this issues if it is
so.
GPL licensed files
#grep -R "under GPL" *
jetty/src/main/org/jboss/jetty/JBossWebApplicationContext.java: *
Distributable under GPL license.
27;s posts.
thanks
david jencks
On 2002.11.20 23:48:36 -0500 Colin Sampaleanu wrote:
Sorry, rushed to get this out before I left work... It is JBoss
3.2beta2. I took the oracle-xa-ds.xml and oracle-xa-service.xml examples
from the docs/examples/jca dir, and changed only jndi binding, url,
u
ences to the old wrapper. A mismatch such as this would explain what
you are experiencing.
thanks
david jencks
On 2002.11.20 18:30:15 -0500 Colin Sampaleanu wrote:
I have encountered a really perplexing issue with trying to get an
oracle xa datasource (using either oracle-xa-ds.xml or
orac
I have encountered a really perplexing issue with trying to get an
oracle xa datasource (using either oracle-xa-ds.xml or
oracle-xa-service.xml). Basically, it never deploys fully, with the
following dependency issues:
---
17:10:37,471 ERROR [URLDeploymentScanner] MBeanException: Exception in
M
jndi lookups through tcp/ip availiable to the servlet's
classloader. Check your packages and remove any such files.
david jencks
On 2002.11.13 11:13:08 -0500 Colin Sampaleanu wrote:
The original scenario (not written by me), was that a startup servlet
called a session EJB which started Qu
oader
from the JBoss.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxx
- Original Message -
From: "Colin Sampaleanu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 12, 2002 7:55 PM
Subject
I am binding a datasource using oracle-service.xml, which uses
RarDeployment to bind the datasource to JNDI using the 'java:'
namespace. Unfortuntately I have an issue accessing this from a thread
started by a Quartz scheduled job, presumably because items in the java:
namespace are thread spec
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Scott M
> Stark
> Sent: Wednesday, April 04, 2001 1:26 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JBoss and JDK 1.2.2
>
> > As an aside, I do not understand how security context information
Is JBoss completely usable under JDK 1.2.2, including security?
I am a little bit confused (and looking at the mailing list archives and all
the documentation has not helped). The (new) documentation mentions setting
the bean containers properly for JDK 1.2x; that is pretty clear. W/regards
to th
10 matches
Mail list logo
