I'm also short on time for the JMX stuff. My first step was to get Tapestry working with JBoss 3.0.0, and I'm having troubles gettiing the Vlib to deploy with McKoi inside JBoss.
----- Original Message ----- From: "Jim Birchfield" <[EMAIL PROTECTED]> To: "'Howard M. Lewis Ship '" <[EMAIL PROTECTED]>; "'Tapestry Developer '" <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 7:48 PM Subject: RE: [Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you decide! > +1 for JDK1.3 and JBoss. > > BTW, been watching the list even though I have been very quiet. How's the > JMX work going? I have been working part of the time with one of our > developers porting all of our PHP based reports to Tapestry, and we both > still love it! We have done some pretty vool, yet probably 'hacky' thiings > that involve producing excel reports straight from the browser, but it works > sweet! > > Will be doing a lot more Tapestry work over the next two weeks, so might > start to be more vocal. I have a huge project list to finish up in three > weeks before I leave for vacation... > > Jim > > -----Original Message----- > From: Howard M. Lewis Ship > To: Tapestry Developer > Sent: 6/14/2002 1:05 AM > Subject: [Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you decide! > > Until now, I've been trying very hard to keep Tapestry compatible with > JDK > 1.2.2 ... that is, using the JDK 1.2.2 compiler. > > I'm in the middle of an upgrade to JBoss 3.0.0 but I thought I'd check > teh > build process. Here's the problem: > > Compiling 10 source files to C:\Work\export\Tapestry\contrib\classes > error: Invalid class file format in > C:\work\jboss-3.0.0\lib\jboss-jmx.jar(javax/management/MBeanServer.class > ). > The major.minor version '47.0' is too recent for this tool to > understand. > C:\Work\export\Tapestry\contrib\src\net\sf\tapestry\contrib\mckoi\McKoiD > B.ja > va:32: Class javax.management.MBeanServer not found in import. > import javax.management.MBeanServer; > ^ > error: Invalid class file format in > C:\work\jboss-3.0.0\lib\jboss-jmx.jar(javax/management/ObjectName.class) > . > The major.minor version '47.0' is too recent for this tool to > understand. > C:\Work\export\Tapestry\contrib\src\net\sf\tapestry\contrib\mckoi\McKoiD > B.ja > va:33: Class javax.management.ObjectName not found in import. > import javax.management.ObjectName; > ^ > error: Invalid class file format in > C:\work\jboss-3.0.0\lib\jboss-jmx.jar(javax/management/NotificationBroad > cast > erSupport.class). The major.minor version '47.0' is too recent for this > tool to understand. > C:\Work\export\Tapestry\contrib\src\net\sf\tapestry\contrib\mckoi\McKoiD > B.ja > va:0: Class javax.management.NotificationBroadcasterSupport not found in > class org.jboss.system.ServiceMBeanSupport. > // > ^ > 6 errors > > BUILD FAILED > > > They've been compiling using JDK 1.3 or 1.4. > > It would simplify things for me greatly to simply compile using JDK 1.3 > ... > perhaps with the -target 1.2 option. > > People have had some problems using Tapestry with WebSphere and with > certain > JVMs (JRockit, I believe). Has that been resolved? > > We may be getting to the point where if you need JDK 1.2.2, you'll need > to > recompile the source code yourself. Is that truly terrible? > > Howard > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
