View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060201035602
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060201042107
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
FYI
I am starting work on a prototype of the following three
new modules (I am not sure these are good names :-)
1) Integration - Cross (other) container integration spi
like "how do I bind to jndi?", give me the transaction synchronizer,
etc.
2) Services - abstraction of our common container s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060201085214
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
Scott M Stark wrote:
How can the scanClasspath() step be optimized/skipped in say an embedded
ejb3 project in jbosside where the data obtained during the scan was
written out in an optimized metadata store as part of the project say?
The definition of embedded is *simple*. This optimized me
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060201110410
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scripts
Hello Adrian,
This is really great, that is a much needed step for the MC usage/adoption
IMHO.
> I am starting work on a prototype of the following three new
> modules (I am not sure these are good names :-)
Yeah, not sure as well, but I am not sure i have great ideas at this point.
> 1) Inte
This is ignorable, all tests passed.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 01, 2006
10:54 AM
To: Dimitris Andreadis; jboss-development@lists.sourceforge.net; QA
Subject: jboss-3.2-testsuite Build
Failed
Importance: High
View results h
I'm saying the ide should be creating the optimized metadata view as the
project evolves. Of course this is an optional behavior.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Wednesday, February 01, 2006 10:13 AM
To: jboss-development@l
In EJB3 I'm trying to guess the datasource MBean name so that I can
create a dependency on it. I do this based on the JNDI name passed into
persistence.xml. So, if the datsource is "java:/DefaultDS" I assume
that there is a:
"jboss.jca:service=DataSource,name=DefaultDS" mbean available.
Is
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060201115514
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:173: The value of attribute "todir" associated with an element type "copy" must not contain the
Can I use:
"jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"?
Bill Burke wrote:
In EJB3 I'm trying to guess the datasource MBean name so that I can
create a dependency on it. I do this based on the JNDI name passed into
persistence.xml. So, if the datsource is "java:/DefaultDS" I a
On Wed, 2006-02-01 at 11:57, Bill Burke wrote:
> In EJB3 I'm trying to guess the datasource MBean name so that I can
> create a dependency on it. I do this based on the JNDI name passed into
> persistence.xml. So, if the datsource is "java:/DefaultDS" I assume
> that there is a:
>
> "jboss.jc
Perhaps we should just byte the bullet and fix this naming confusion?
The problem is everybody's existing config that uses it.
e.g. JMS and login-config.xml that reference these names.
You can certainly "fix" the stylesheet and change this config
in jbossjca-service.xml
-ds.xml
300:-ds
Adrian Brock wrote:
e.g. at least firebird has its own rar that is deployed this way.
Yes, this *exactly* where the user was complaining. EJB3 assumes the
Datasource MBean name.
Don't blame me for the different names, this is legacy rubbish
that dates back to 2.4.x
They should really
On Wed, 2006-02-01 at 12:05, Bill Burke wrote:
> Can I use:
>
> "jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"?
>
It is the DataSourceBinding or ConnectionFactoryBinding
that you want to depend upon.
This is what populates JNDI.
> Bill Burke wrote:
> > In EJB3 I'm trying to guess
Doesn't help me on 4.0.3SP1. What we should *really* do is create those
JNDI dependencies we were arguing about before.
Adrian Brock wrote:
Perhaps we should just byte the bullet and fix this naming confusion?
The problem is everybody's existing config that uses it.
e.g. JMS and login-config.x
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060201125533
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:216: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
I'm seeing start being
called twice for a particular MBean and thus, I'm getting an error. I
think what is happening is this:
1. deploy 'A' MBean, its dependency 'B' has not been resolved
2. Deploy 'B', resolve 'A''s dependency, call create/start
3. Undeploy 'B'
4. Deploy 'B'
Is this the corr
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-compatibility-matrix?log=log20060202001416
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/w
20 matches
Mail list logo
