View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060309002343
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log2006030953
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:70: The following error occurred while executing this line: /services/cruisecontrol/work/s
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060308230726
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
15th
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bill Burke
> Sent: Wednesday, March 08, 2006 9:04 AM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] drop dead date for 4.0.4?
>
> So, you still haven't answered my q
So, you still haven't answered my question. When do I have to have
changes in by for the next release be it CR2 or GA? I have other things
due on friday and would like to defer some EJB3 coding til next week.
Scott M Stark wrote:
Should be JBossAS-4.0.4.CR2 on the 17th instead.
-Origi
Ok
Scott M Stark wrote:
Probably not as this is duplicating functionality from the
SchemaBindingResolver. A subclass of DefaultSchemaResolver would be
needed to support programatic creation of the SchemaBinding within the
resolve callback.
-Original Message-
From: [EMAIL PROTECTED]
[
Should be JBossAS-4.0.4.CR2 on the 17th instead.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Scott M Stark
> Sent: Wednesday, March 08, 2006 7:43 AM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] drop dead date for 4
The release has been rescheduled for Apr 3. There should be a
JBossAS-4.0.5.CR2 on the 17th instead.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bill Burke
> Sent: Wednesday, March 08, 2006 5:51 AM
> To: jboss-development@lists.sourceforge.ne
Probably not as this is duplicating functionality from the
SchemaBindingResolver. A subclass of DefaultSchemaResolver would be
needed to support programatic creation of the SchemaBinding within the
resolve callback.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED
There is no evidence of such a posting, and if it was simply to say it
would be confusing it does not solve the usability issue.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=75175
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bill
I see. I can create an unannotated skeleton xsd then and supply the
bindings via the SchemaBindingInitializer.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Adrian Brock
> Sent: Tuesday, March 07, 2006 8:28 AM
> To: jboss-development@lists.sour
Adrian Brock wrote:
Alex has a cache of uri -> schemabinding somewhere that could
be populated directly I guess?
This is in DefaultSchemaResolver. It's populated inside resolve(...)
when a SchemaBinding is successfully resolved. There is no reason it's
not exposed for external ns to SchemaBin
On Tue, 2006-03-07 at 10:09 -0600, Scott M Stark wrote:
> Then I don't see the point of the SchemaBindingInitializer. An XSD is
> simply mapped to a SchemaBinding via the XsdBinder class, what I want is
> to bypass the XSD and just tell the binding layer here is how to handle
> the urn:jboss:simple
On Tue, 2006-03-07 at 12:11 -0600, Scott M Stark wrote:
> Related to this user forum question:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78545
>
> how does ConnectionPoolDataSource fit into the jca layer? Is a separate
> pool implementation that wraps this needed or what?
>
It d
My bad.
On Fri, 2006-02-10 at 15:17, [EMAIL PROTECTED] wrote:
> View results here ->
> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20060210150533
>
> BUILD FAILED
> Ant Error
> Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:271: The
> followin
On Fri, 2006-02-10 at 13:28, Scott M Stark wrote:
> Let's do that. Do you want to couple this to maven? It would help Ruel I
> suppose.
We may as well go "Big Bang!". :-)
>
> > -Original Message-
> > From: Adrian Brock
> > Sent: Friday, February 10, 2006 9:34 AM
> > To: Scott M Stark
>
On Fri, 2006-02-10 at 10:32, Scott M Stark wrote:
> So we need to carve out a "minimal" impact strategy considering projects
> that today are tied to the jbossas head cvs structure. Maybe we need a
> nightly snapshot of jbossas in the repository with redefinition of
> projects like ejb3 to decouple
On Fri, 2006-02-10 at 08:39, Scott M Stark wrote:
> I'm not following. aop and xb are no brainer standalone projects that
> should not be in the jbossas cvs module alias by default. ws and ejb3
> probably need to be refactored into standalone modules and a server
> integration module which can be i
Ironically, one of the problems I am trying to solve
will be made worse by this approach.
That is the number of projects that are really standalone
but are developed in head alongside the application server
code. e.g. AOP, JBossXB, JBossWS, EJB3
They need a useable head branch, even if nobody see
Yes, I'm aware of it and I did comment on forum regarding this when it
was first posted...
Dimitris Andreadis wrote:
No better alternative was proposed, so this is the new versioning scheme
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning
-Original Message-
From: [EMAI
No better alternative was proposed, so this is the new versioning scheme
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bill Burke
> Sent: 08 March, 2006 16:31
> To: jboss-developm
BTW, these changes from RC2 to CR2 is gonna confuse the hell out of
users
Dimitris Andreadis wrote:
Since we are still some 130 issues left, we'll probably do a CR2 on the
17th instead, and give another week for cleaning up and testing things
for the GA.
-Original Message-
From:
Since we are still some 130 issues left, we'll probably do a CR2 on the
17th instead, and give another week for cleaning up and testing things
for the GA.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bill Burke
> Sent: 08 March, 2006 15:51
>
On Tue, 2006-03-07 at 18:32 +, Adrian Brock wrote:
> On Tue, 2006-03-07 at 12:11 -0600, Scott M Stark wrote:
> > Related to this user forum question:
> > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78545
> >
> > how does ConnectionPoolDataSource fit into the jca layer? Is a separa
So I have a few weeks then?
Scott M Stark wrote:
Or latter.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, March 07, 2006 8:11 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] drop dead date for 4.0.4?
How
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060308065834Lbuild.1527
BUILD COMPLETE - build.1527Date of build: 03/08/2006 06:58:34Time to build: 27 minutes 39 secondsLast changed: 03/08/2006 06:49:54Last log entry: Make this
The point of SchemaBindingInitializer is to adjust/correct bindings
after XSD was processed.
SchemaBindingResolver is supposed to resolve/build a SchemaBinding from
whatever source it can. It can be XSD or anything else.
I guess we can give a chance to SchemaBindingInitializer to build the
Schem
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060308040928
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060308032924
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
29 matches
Mail list logo
