[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider

RE: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Tom Elrod 
I don't want to steal too much of Marc's thunder on this (he has a great
vision for JBoss 4), but one of the goals of JBoss 4 is to make it so
developers don't have to deal with all the J2EE APIs (which honestly add a
lot of overhead in development time as well as training/study time to learn
it all).

For example, with EJBs, you have the remote, home, and implementation to
keep up with.  With JBoss 4, you would be able to write a POJO with all you
business logic and plug-in (via configuration) all the extra pieces you want
(remoting, persistence, caching, transaction, security, etc.).  This makes
the process much easier for you, the developer, since you won't have to
worry about all the extra code (which usually ends up being 25% business
logic and the rest infrastructure when you look at lines of code).  Only
extra effort required is to configure the extra services you want (which
will take much less time than coding it).

Of course, if you decide to migrate to another application server, you'll
have write all the extra infrastructure code yourself to make it fully J2EE
compatible.  Even if for some reason you decide you want to pay for an
application server where you don't have access to the source, this would
probably be a good way to start a development project, since the business
logic will be the core of your product.

As from a corporate perspective, JBoss, in general, makes sense over other
application servers.  The two major reasons are both the source and the
runtime are free.  So the only question would be does it work well
(functionality, performance, scalability) and can I get support for it?  The
first one is somewhat a matter of opinion, but I think it has proven itself
in production. Support is available for a fee (but you're getting the guys
that actually wrote it, so you know they know what they are doing).  If
JBoss does ever change its direction, you'll still have the source so you
could still maintain what you needed.  If you bought an app. server from a
company that changes direction, then you would end up having to pay again
for some other company's app. server to get what you want (so you're out you
initial investment, plus it might happen again and you have not other course
of action without source).

I personally feel that the only real reason for paying for an application
server is if it allows you to get a price break on some other part of a
package deal (i.e. hardware).  Then you have to decide if you're getting
enough savings on the hardware to offset the price of the software.

Of course, this is just my opinion, but would love to hear exactly why
companies would want to pay for an application server.

-Tom







> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Behalf Of Brian
> Wallis
> Sent: Monday, March 24, 2003 1:34 AM
> To: [EMAIL PROTECTED]; Tom Elrod
> Subject: Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?
>
>
> On Mon, 24 Mar 2003 16:42, Tom Elrod wrote:
> > IMHO, I don't know that passing the certification tests now
> would be of
> > much benefit to JBoss.  The biggest drawback I can see is
> that with JBoss
> > 4, we will be moving people away from having to deal with
> all the extra API
> > non-sense that J2EE developers have to deal with today.
> Just write your
> > POJOs and we'll do the rest (persistence, caching,
> security, remoting,
> > etc.).  If we get certified now, might be added pressure to
> make JBoss 4
> > compliant as well, which I think would divert us from our current
> > direction.
>
> IMHO, that would be about it for anyone (like me) who is
> trying to use jboss
> as well as other appservers. I seriously hope that jboss 4
> will be fully
> compliant with the standards or else I fear it will become
> marginalised and
> in all likely hood die off.
>
>
> ---
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>



---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Nick Betteridge 
Certification tests are important for corporates - they protect their
investment in development by ensuring that if one companies vision (ie
jboss/websphere etc) goes belly-up then switching to another server will
provide the least set of headaches.




Tom Elrod wrote:
> 
> IMHO, I don't know that passing the certification tests now would be of much
> benefit to JBoss.  The biggest drawback I can see is that with JBoss 4, we
> will be moving people away from having to deal with all the extra API
> non-sense that J2EE developers have to deal with today.  Just write your
> POJOs and we'll do the rest (persistence, caching, security, remoting,
> etc.).  If we get certified now, might be added pressure to make JBoss 4
> compliant as well, which I think would divert us from our current direction.
> 
> If Sun would have made this offer a year ago, might of been worth pursuing.
> 
> -Tom
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Behalf Of Dave
> > Neuer
> > Sent: Sunday, March 23, 2003 10:16 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?
> >
> >
> > --- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > > On Sunday, March 23, 2003, at 07:30 PM, Dave Neuer
> > > wrote:
> > >
> > > > --- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > > >>
> > > >> The more tests we have the better we will be, but
> > > I
> > > >> doubt that sun will
> > > >> let us check the TDK into CVS, so it will be
> > > >> worthless to everyone but
> > > >> the few JBoss employees that get access.
> > > >>
> > > >> -dain
> > > >
> > > > Is a condition of the TDK license that you can't
> > > use
> > > > the information about your source tree that it
> > > reveals
> > > > to improve the product? Does it specifically bar
> > > you
> > > > from writing JUnit test cases which test for a bug
> > > > which just happens to be a bug regarding spec
> > > > compliance?
> > >
> > > Got me.  Where did you find the license to the J2EE
> > > TDK license?
> > >
> > > -dain
> > >
> >
> > I didn't, I was asking you ;-).
> >
> > Seriously, I can imagine Sun has got some onerous
> > conditions in there compatabitliy test kit license.
> > However, if JBoss can't pass the tests, it's because
> > of "bugs" (i.e., missing features) in the code, and I
> > can't imagine that even if the license for the test
> > kit somehow prohibits you from sharing the kit itself
> > or the results, it would also restrict you from fixing
> > "bugs" in your source code, whatever those bugs might
> > be. I mean, Sun's J2EE specs are public. It'd be tough
> > for their lawyers to prove you fixed a bug or added a
> > feature just because you ran the tests.
> >
> > But, to an extent it would be beside the point. I'm
> > working now on a project to replace a Lotus
> > Notes/Domino application and the management of the
> > company brought me on because *they* chose JBoss to
> > replace it, and I've taken the advanced training. They
> > didn't seem to concerned about spec compliance. They
> > care about performance, flexibility, and no $3000/CPU
> > licensing.
> >
> > Spec compliance is valuable because it provides (in
> > theory, at least) predictable behavior when you don't
> > have the source of the application.
> >
> > When you've got the source, you don't need predictable
> > behavior; everything is completely transparent. You
> > can turn on source-level debugging and step through
> > the code! Don't like how it does feature X? Fix it!
> >
> > Certified spec compliance for JBoss would be nice for
> > one little extra marketing buzzword. But at this
> > point, JBoss probably has enough momentum that spec
> > compliance could be at most icing on the cake. You
> > know for sure that if someone out there needs some
> > in-spec feature that JBoss doesn't have bad enough,
> > they'll send a patch to add it.
> >
> > Dave
> >
> > __
> > Do you Yahoo!?
> > Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> > http://platinum.yahoo.com
> >
> >
> > ---
> > This SF.net email is sponsored by:Crypto Challenge is now open!
> > Get cracking and register here for some mind boggling fun and
> > the chance of winning an Apple iPod:
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> > ___
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> 
> ---
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/lis

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Brian Wallis 
On Mon, 24 Mar 2003 16:42, Tom Elrod wrote:
> IMHO, I don't know that passing the certification tests now would be of
> much benefit to JBoss.  The biggest drawback I can see is that with JBoss
> 4, we will be moving people away from having to deal with all the extra API
> non-sense that J2EE developers have to deal with today.  Just write your
> POJOs and we'll do the rest (persistence, caching, security, remoting,
> etc.).  If we get certified now, might be added pressure to make JBoss 4
> compliant as well, which I think would divert us from our current
> direction.

IMHO, that would be about it for anyone (like me) who is trying to use jboss 
as well as other appservers. I seriously hope that jboss 4 will be fully 
compliant with the standards or else I fear it will become marginalised and 
in all likely hood die off.


---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Tom Elrod 
IMHO, I don't know that passing the certification tests now would be of much
benefit to JBoss.  The biggest drawback I can see is that with JBoss 4, we
will be moving people away from having to deal with all the extra API
non-sense that J2EE developers have to deal with today.  Just write your
POJOs and we'll do the rest (persistence, caching, security, remoting,
etc.).  If we get certified now, might be added pressure to make JBoss 4
compliant as well, which I think would divert us from our current direction.

If Sun would have made this offer a year ago, might of been worth pursuing.

-Tom

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Behalf Of Dave
> Neuer
> Sent: Sunday, March 23, 2003 10:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?
>
>
> --- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > On Sunday, March 23, 2003, at 07:30 PM, Dave Neuer
> > wrote:
> >
> > > --- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> > >>
> > >> The more tests we have the better we will be, but
> > I
> > >> doubt that sun will
> > >> let us check the TDK into CVS, so it will be
> > >> worthless to everyone but
> > >> the few JBoss employees that get access.
> > >>
> > >> -dain
> > >
> > > Is a condition of the TDK license that you can't
> > use
> > > the information about your source tree that it
> > reveals
> > > to improve the product? Does it specifically bar
> > you
> > > from writing JUnit test cases which test for a bug
> > > which just happens to be a bug regarding spec
> > > compliance?
> >
> > Got me.  Where did you find the license to the J2EE
> > TDK license?
> >
> > -dain
> >
>
> I didn't, I was asking you ;-).
>
> Seriously, I can imagine Sun has got some onerous
> conditions in there compatabitliy test kit license.
> However, if JBoss can't pass the tests, it's because
> of "bugs" (i.e., missing features) in the code, and I
> can't imagine that even if the license for the test
> kit somehow prohibits you from sharing the kit itself
> or the results, it would also restrict you from fixing
> "bugs" in your source code, whatever those bugs might
> be. I mean, Sun's J2EE specs are public. It'd be tough
> for their lawyers to prove you fixed a bug or added a
> feature just because you ran the tests.
>
> But, to an extent it would be beside the point. I'm
> working now on a project to replace a Lotus
> Notes/Domino application and the management of the
> company brought me on because *they* chose JBoss to
> replace it, and I've taken the advanced training. They
> didn't seem to concerned about spec compliance. They
> care about performance, flexibility, and no $3000/CPU
> licensing.
>
> Spec compliance is valuable because it provides (in
> theory, at least) predictable behavior when you don't
> have the source of the application.
>
> When you've got the source, you don't need predictable
> behavior; everything is completely transparent. You
> can turn on source-level debugging and step through
> the code! Don't like how it does feature X? Fix it!
>
> Certified spec compliance for JBoss would be nice for
> one little extra marketing buzzword. But at this
> point, JBoss probably has enough momentum that spec
> compliance could be at most icing on the cake. You
> know for sure that if someone out there needs some
> in-spec feature that JBoss doesn't have bad enough,
> they'll send a patch to add it.
>
> Dave
>
> __
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
>
> ---
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>



---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Dave Neuer 
--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> On Sunday, March 23, 2003, at 07:30 PM, Dave Neuer
> wrote:
> 
> > --- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> >>
> >> The more tests we have the better we will be, but
> I
> >> doubt that sun will
> >> let us check the TDK into CVS, so it will be
> >> worthless to everyone but
> >> the few JBoss employees that get access.
> >>
> >> -dain
> >
> > Is a condition of the TDK license that you can't
> use
> > the information about your source tree that it
> reveals
> > to improve the product? Does it specifically bar
> you
> > from writing JUnit test cases which test for a bug
> > which just happens to be a bug regarding spec
> > compliance?
> 
> Got me.  Where did you find the license to the J2EE
> TDK license?
> 
> -dain
> 

I didn't, I was asking you ;-).

Seriously, I can imagine Sun has got some onerous
conditions in there compatabitliy test kit license.
However, if JBoss can't pass the tests, it's because
of "bugs" (i.e., missing features) in the code, and I
can't imagine that even if the license for the test
kit somehow prohibits you from sharing the kit itself
or the results, it would also restrict you from fixing
"bugs" in your source code, whatever those bugs might
be. I mean, Sun's J2EE specs are public. It'd be tough
for their lawyers to prove you fixed a bug or added a
feature just because you ran the tests.

But, to an extent it would be beside the point. I'm
working now on a project to replace a Lotus
Notes/Domino application and the management of the
company brought me on because *they* chose JBoss to
replace it, and I've taken the advanced training. They
didn't seem to concerned about spec compliance. They
care about performance, flexibility, and no $3000/CPU
licensing.

Spec compliance is valuable because it provides (in
theory, at least) predictable behavior when you don't
have the source of the application.

When you've got the source, you don't need predictable
behavior; everything is completely transparent. You
can turn on source-level debugging and step through
the code! Don't like how it does feature X? Fix it!

Certified spec compliance for JBoss would be nice for
one little extra marketing buzzword. But at this
point, JBoss probably has enough momentum that spec
compliance could be at most icing on the cake. You
know for sure that if someone out there needs some
in-spec feature that JBoss doesn't have bad enough,
they'll send a patch to add it.

Dave

__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com


---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Dain Sundstrom 
On Sunday, March 23, 2003, at 07:30 PM, Dave Neuer wrote:

--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
The more tests we have the better we will be, but I
doubt that sun will
let us check the TDK into CVS, so it will be
worthless to everyone but
the few JBoss employees that get access.
-dain
Is a condition of the TDK license that you can't use
the information about your source tree that it reveals
to improve the product? Does it specifically bar you
from writing JUnit test cases which test for a bug
which just happens to be a bug regarding spec
compliance?
Got me.  Where did you find the license to the J2EE TDK license?

-dain



---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Dave Neuer 
--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> 
> The more tests we have the better we will be, but I
> doubt that sun will 
> let us check the TDK into CVS, so it will be
> worthless to everyone but 
> the few JBoss employees that get access.
> 
> -dain

Is a condition of the TDK license that you can't use
the information about your source tree that it reveals
to improve the product? Does it specifically bar you
from writing JUnit test cases which test for a bug
which just happens to be a bug regarding spec
compliance?

Dave

__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com


---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Dain Sundstrom 
On Sunday, March 23, 2003, at 04:19 PM, Stefan Arentz wrote:

On Saturday, Mar 22, 2003, at 23:03 Europe/Amsterdam, Tom Coleman 
wrote:

 Personally, certification is irrelevant to me.  My criteria is 
whether
 or not the product gets the job done.  I think certification serves 
to
 answer that question for people who don't know how to figure it out 
for
 themselves.
I have a different view on that. I think certification is important 
because by running all those tests we will find a lot of new bugs in 
JBoss. Certification will make it a better product because *all* parts 
of the specification will be touched instead of just what people are 
using.

I agree that certification is not that important to sell the product, 
but from a development / testing perspective it is *very* useful.
The more tests we have the better we will be, but I doubt that sun will 
let us check the TDK into CVS, so it will be worthless to everyone but 
the few JBoss employees that get access.

-dain



---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider

Re: [JBoss-dev] Jboss/David Vs. Sun/Goliath?

2003-03-23 Thread Stefan Arentz 
On Saturday, Mar 22, 2003, at 23:03 Europe/Amsterdam, Tom Coleman wrote:

...

 Personally, certification is irrelevant to me.  My criteria is whether
 or not the product gets the job done.  I think certification serves to
 answer that question for people who don't know how to figure it out 
for
 themselves.
I have a different view on that. I think certification is important 
because by running all those tests we will find a lot of new bugs in 
JBoss. Certification will make it a better product because *all* parts 
of the specification will be touched instead of just what people are 
using.

I agree that certification is not that important to sell the product, 
but from a development / testing perspective it is *very* useful.

 S.



---
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] 风险代理 胜诉收费

2003-03-23 Thread jiaobh 
Title: Ö´ÒµÂÉʦΪÄú·þÎñ









·çÏÕ´úÀí ʤËßÊÕ·Ñ







    ¸ù¾ÝÄ¿Ç°ËßËÏÄÑ¡¢Ö´ÐÐÄÑ¡¢ËßËϳɱ¾¸ß¡¢ËßËÏЧÒæµÍµÄÉç»áÏÖÏó£¬ÏÖÍƳö²¿·Ö·çÏÕ´úÀí·½Ê½£¬ÒÔ¼õÇáίÍÐÈ˾­¼Ã¸ºµ££¬Ò²¼¤ÀøÂÉʦ¸ßЧ¡¢¾¡ÔðµØÍê³É´úÀíÊÂÏî¡£·çÏÕ´úÀíÊÇÖ¸¸ù¾ÝÂÉʦÊÂÎñËù
ÓëίÍÐÈËÖ®¼äµÄÔ¼¶¨£¬Î¯ÍÐÈËÔݲ»Ö§¸¶È«²¿»ò²¿·ÖÓйطÑÓ㬴ýÆäծȨʵÏÖ»òÆäËûίÍÐÊÂÏîÍê³ÉÖ®ºó£¬Ïò±¾ÂÉʦ֧¸¶Ô¼¶¨±ÈÀý»òÒ»¶¨Êý¶îÂÉʦ·Ñ
µÄ´úÀíÐÎʽ¡£Ä¿Ç°£¬±¾ÂÉʦÒÔÊÜÀí²¿·Ö·çÏÕ´úÀí°¸¼þΪÖ÷
£¬µØÓò·¶Î§Ö÷ÒªÊÇÉÂÎ÷Ê¡¼°ÆäÖܱßÊ¡·Ý¡£ÄúÖ»Òª½»ÄÉÉÙÁ¿¶¨¶î°ì°¸·ÑÓ㬴úÀí·ÑÓôý¿îÏî×·»ØÖ®ºóÔÙ¸ù¾Ý±êµÄ
¶îµÄ´óСÔÚ20%¡ª30%µÄ·¶Î§ÄÚÊÕÈ¡¡£´úÀíÂÉʦ¸ºÔðËßËϺÍÖ´ÐÐÈ«²¿¹ý³Ì£¬Ö±ÖÁ¿îÏî×·»Ø¡£


    
ÁíÍ⣬±¾ÂÉʦ½ÓÊܸ÷ÀàÃñÊ¡¢¾­¼Ã¾À·×°¸¼þµÄίÍУ¬ÒÔ¼°ÊÜƸµ£Èι«Ë¾³£Äê·¨ÂɹËÎÊ¡£

   


¡¶ÍøÓÑÂÉʦ¡·ÍøÕ¾³£Ä꿪ͨÔÚÏßÃâ·Ñ·¨ÂÉ×Éѯ·þÎñ£¬»¶Ó­ÄúÁôÑÔ×Éѯ¡£
    ÏêÇéÇë·ÃÎÊ£ºhttp://jbhlawyer.126.com


    

µç×ÓÓʼþ×Éѯ£º
 


[EMAIL PROTECTED]  



    

ƸÇëÂÉʦÈÈÏߣº 
13992839269£¨Î÷°²£©


    



¸ÐлÄúÔĶÁ±¾Óʼþ£¬Èç¹û¸øÄú´øÀ´²»±ã£¬Çë¶à¶à°üº­¡£Èç¹ûÄú²»Ô¸ÔÙÊÕµ½ÀàËÆÓʼþ£¬Âé·³Äú·¢Ðŵ½[EMAIL PROTECTED],лл¡£

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider

[JBoss-dev] [ jboss-Bugs-679705 ] 3.0.6 fails to start with AbstractMethodError on IBM 1.4 VM

2003-03-23 Thread SourceForge.net 
Bugs item #679705, was opened at 2003-02-03 19:40
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=679705&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Works For Me
Priority: 5
Submitted By: Stefan Kuehnel (skuehnel)
Assigned to: Scott M Stark (starksm)
Summary: 3.0.6 fails to start with AbstractMethodError on IBM 1.4 VM

Initial Comment:
TestingJBoss 3.0.6 with an IBM 1.4 VM on Linux I get an
AbstractMethodError on startup for
AbstractDeploymentScanner.scan() when starting the
URLDeploymentScanner.  This happens both if JBoss was
compiled with a Sun as well as an IBM JDK.

System info:

19:01:34,499 INFO  [ServerInfo] Java version: 1.4.0,IBM
Corporation
19:01:34,500 INFO  [ServerInfo] Java VM: Classic VM
1.4.0,IBM Corporation
19:01:34,526 INFO  [ServerInfo] OS-System: Linux
2.4.18-17.7.x,x86

Exception:

2003-02-03 19:01:45,294 INFO 
[org.jboss.deployment.scanner.URLDeploymentScanner]
Starting
2003-02-03 19:01:45,301 ERROR
[org.jboss.deployment.MainDeployer] could not start
deployment:
file:/home/stefan/tools/jboss/jboss-3.0.6-src-IBM/build/output/jboss-3.0.6/server/all/conf/jboss-service.xml
java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
at java.lang.reflect.Method.invoke(Method.java:335)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:413)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown
Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
at java.lang.reflect.Method.invoke(Method.java:335)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy2.start(Unknown Source)
at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
at java.lang.reflect.Method.invoke(Method.java:335)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:566)
2003-02-03 19:01:45,468 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-02-03 19:01:45,470 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-02-03 19:01:45,470 DEBUG
[org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-02-03 19:01:45,471 ERROR
[org.jboss.system.server.Server] start failed
org.jboss.deployment.DeploymentException: Could not
create deployment:
file:/home/stefan/tools/jboss/jboss-3.0.6-src-IBM/build/output/jboss-3.0.6/server/all/conf/jboss-service.xml;
- nested throwable: (java.lang.AbstractMethodError:
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:835)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at
sun.refl

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-23 Thread chris 

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

 The referring classes do not import any fully qualified classes matching 
these classes.
 However, since no packages are imported, xjavadoc has assumed that the 
referred classes
 belong to the same package as the referring class. The classes are:
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectDefinition.java
 --> ManagedAspectDefinitionMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectDefinitionMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/aspect/jmx/ManagedAspectFactory.java
 --> ManagedAspectFactoryMBean qualified to 
org.jboss.aspect.jmx.ManagedAspectFactoryMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/copy/ObjectCopier.java --> 
ObjectCopierMBean qualified to org.jboss.copy.ObjectCopierMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> EARDeployerMBean qualified to org.jboss.deployment.EARDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/deployment/EARDeployer.java 
--> SubDeployerSupport qualified to org.jboss.deployment.SubDeployerSupport
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EJBDeployer.java --> 
EJBDeployerMBean qualified to org.jboss.ejb.EJBDeployerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EntityEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionEnterpriseContext.java
 --> EJBContextImpl qualified to org.jboss.ejb.EJBContextImpl
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/StatefulSessionContainer.java
 --> AbstractContainerInterceptor qualified to 
org.jboss.ejb.AbstractContainerInterceptor
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EjbModule.java --> 
EjbModuleMBean qualified to org.jboss.ejb.EjbModuleMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/plugins/StatefulSessionFilePersistenceManager.java
 --> StatefulSessionFilePersistenceManagerMBean qualified to 
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/AbstractTimerSource.java
 --> AbstractTimerSourceMBean qualified to org.jboss.ejb.timer.AbstractTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/FilePersistenceManager.java
 --> FilePersistenceManagerMBean qualified to 
org.jboss.ejb.timer.FilePersistenceManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/timer/SchedulerTimerSource.java
 --> SchedulerTimerSourceMBean qualified to 
org.jboss.ejb.timer.SchedulerTimerSourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/InvokerXAResource.java
 --> InvokerXAResourceMBean qualified to org.jboss.invocation.InvokerXAResourceMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/XATerminatorContainer.java
 --> XATerminatorContainerMBean qualified to 
org.jboss.invocation.XATerminatorContainerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/local/LocalInvoker.java
 --> LocalInvokerMBean qualified to org.jboss.invocation.local.LocalInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/jrmp/server/JRMPInvoker.java
 --> JRMPInvokerMBean qualified to org.jboss.invocation.jrmp.server.JRMPInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/pooled/server/PooledInvoker.java
 --> PooledInvokerMBean qualified to 
org.jboss.invocation.pooled.server.PooledInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/ConnectionManager.java
 --> ConnectionManagerMBean qualified to 
org.jboss.invocation.trunk.client.ConnectionManagerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/client/TrunkInvokerProxy.java
 --> TrunkInvokerProxyMBean qualified to 
org.jboss.invocation.trunk.client.TrunkInvokerProxyMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/invocation/trunk/server/TrunkInvoker.java
 --> TrunkInvokerMBean qualified to org.jboss.invocation.trunk.server.TrunkInvokerMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/asf/ServerSessionPoolLoader.java
 --> ServerSessionPoolLoaderMBean qualified to 
org.jboss.jms.asf.ServerSessionPoolLoaderMBean
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jms/jndi/JMSProviderLoader.java
 --> JMSProvider