|I think that if any of this has ever worked it should be included in the |main build and whatever tests exist added to the main testsuite. Unless I |get notified by broken tests, I don't know something exists, let alone |whether I broke it.
++1 I don't know that it ever really worked, but we talked with Scott yesterday and this JBoss.net thing must go up there with CMP2.0, clustering and MBoss (JMX). The truth is that we have one of the most complete solutions for .NET development (services talking with webservices) and we should really make some noise. Scott said he wants to become Mr JBoss.NET full time as it is going to be one of our most important features. Bottom line: anything that makes JBoss.NET part of the main line and main tests is ++1. On the same line of thought, do you think integrating the deployers can enable us to put a java file with doclet stuff and get an EJB AND a webservice (by tying the ant to call he axis deployer)? I plan on finishing the unification of invokers next week (with Invocation return and client int) so we could test the shared EJB thingy. That's going to be sweet. marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
