I am working with a version of jBoss that I obtained from CVS a couple of days
ago and the Tomcat stuff doesn't work (I just updated my CVS tree and nothing
in the tomcat package has changed). Several other people have reported similar
problems and according to them they have seen no resolution as of yet.
So, what does "done and working great" mean? Have Sebastien and/or Daniel
actually deployed a servlet based application and seen it run with a servlet or
JSP page getting a Home object from JNDI? If so, I would be very grateful for
help in getting my test application to work. I think others on the list
would be equally grateful as well. The work around (adding your Tomcat
application classes to the system classpath) is far from optimal.
If it is all working great why not just check it in so we can all share in the
new and improved Tomcat/jBoss integration?
Thanks,
Vince
On Fri, 20 Oct 2000, you wrote:
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> |Sent: Friday, October 20, 2000 3:03 PM
> |To: jBoss Developer
> |Subject: [jBoss-Dev] Outstanding items for final
> |
> |
> |On Fri, 20 Oct 2000, marc fleury wrote:
> |> Aaron, how far are you from FINAL???
> |
> | Regrettably, I'm not very close. Some help would be appreciated,
> |starting from the bottom of this list up (that is, I'm working from the
> |top down).
> |
> |Manual:
> | See jbossweb/manual/warning.html - there's *a lot* left
> | Most important items are EJX walkthrough and descriptions of
> | jboss.xml and jaws.xml options
>
> jboss.xml and jaws.xml is pretty well described in the howto
>
> |Databases:
> | Fighting DB/2 currently
>
> ;-)
>
> | Need to test Interbase
> | Need to test Oracle 8.17 JDBC XA implementation
>
> same as above
>
> |Minerva:
> | Need to implement CallableStatement wrapper
> | Need to implement PreparedStatement cache size limit
> | Need to fix synchronization
> | Need to check on vague reports of memory leaks
>
> |Tomcat:
> | My impression is that this is only vaguely working
>
> No this is done and working great, just not commited yet.
>
> | Lots of reports of jndi.properties not loading, and
> | needing to put bean interfaces on tomcat server or
> | *system* classpath - this is definitely not right.
>
> | Still need to write a Tomcat interceptor (or whatever)
> | to make the in-VM integration work without a code
> | patch to Tomcat
>
> done
>
> |JAWS:
> | Need to change from storing handle to storing PK fields for
> | EJB references
>
> yes
>
> |DTDs:
> | Need fully-commented jboss.dtd and jaws.dtd (a la the ejb-jar.dtd
> | in the EJB 1.1 spec)
>
> the dtd is done check the howto
>
> |EJX:
> | What the heck is the status of EJX? Does it work or not?
> | Is anyone going to improve the file selection interface?
>
> hear hear!
>
> |Threads:
> | Do we have the option of moving to a thread pool before final?
>
> see my previous mail. As tomcat we don't care. stand alone 300 is good.
>
> | It would be nice to not limit Linux so much, but I suspect this
>
> so much is "misplaced" I think :))
>
>
> | is not reasonable for 2 weeks.
>
> well a JMS based one would be trivial,
>
>
> |Misc:
> | Need to write kill.jar (make server process exit altogether)
>
> yes
>
> | Need to move defaultjboss/jaws.xml from JARs to conf directory
> | Need to make JRMP port configurable
>
> yes!
>
>
> marc
>
> |
> |Aaron
> |
> |
> |
> |
--
_______________________
Vincent Sheffer
Director of Operations
Telkel, Inc.
_______________________
