I created a subclass of SimpleEngine, changed the .application to use it,
but when I put it out via either getEngine or engine on a page, it comes out
as a com.primix.tapestry.SimpleEngine and throws a cast exception
(ClassCastException), but when I'm looking at the Vlib example it does
exactly what I'm trying to do.  I'm assuming that Vlib actually works as I
don't have Jboss installed.  Did I miss something??

Adam Greene
ROMulin Group Inc

885 Main St, Suite 16
Moncton, NB
E1C 1G5

Ph: (506) 863-1014 x4
Fx: (506) 854-6886

http://www.romulin.com/

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 14, 2002 4:15 PM
To: [EMAIL PROTECTED]
Subject: Tapestry-developer digest, Vol 1 #142 - 7 msgs

Send Tapestry-developer mailing list submissions to
        [EMAIL PROTECTED]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/tapestry-developer
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tapestry-developer digest..."


Today's Topics:

   1. Re: XML Processing & Other Stuff ([EMAIL PROTECTED])
   2. Re: JBoss 3.0.0 or JDK 1.2.2 ... you decide!
([EMAIL PROTECTED])
   3. Re: +1 JDK1.3![Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you
       decide! (Viktor Szathmary)
   4. Multi Selection List (Jim Birchfield)
   5. RE: Multi Selection List (Jim Birchfield)
   6. RE: JBoss 3.0.0 or JDK 1.2.2 ... you decide! (David Solis)

--__--__--

Message: 1
Subject: Re: [Tapestry-developer] XML Processing & Other Stuff
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Date: Fri, 14 Jun 2002 07:39:13 -0400


Everything you are saying is possible. The only part I don't know off the
top of my head is whether putting XML into the templates and resetting the
content type will do it. You can dig through BaseComponent's render method
to see how it's writing to the IResponseWriter. I would think everything
will fly, though there is a very slim chance it's an HTMLResponseWriter
down there somewhere.

You should be concerned about the performance of this architecture since
XSLT is slow. Maybe not the best plan, though I don't have direct
experience or empirical data.

-C




|--------+---------------------------------------------->
|        |          "Craig Gregory"                     |
|        |          <[EMAIL PROTECTED]>            |
|        |          Sent by:                            |
|        |          [EMAIL PROTECTED]|
|        |          eforge.net                          |
|        |                                              |
|        |                                              |
|        |          06/13/2002 07:25 PM                 |
|        |                                              |
|--------+---------------------------------------------->

>---------------------------------------------------------------------------
-----------------------|
  |
|
  |       To:     <[EMAIL PROTECTED]>
|
  |       cc:
|
  |       Subject:     [Tapestry-developer] XML Processing & Other Stuff
|
  |
|

>---------------------------------------------------------------------------
-----------------------|



I posted the following a couple of days ago, is it not getting through or
does no one have any thoughts ?

I am trying to add another layer of abstraction to Tapestry when rendering
the final HTML output. Using Tapestry to pull data from the application and
notify the application when HTML gestures occur is the way to go, but I am
looking to add enterprise and/or user look-and-feel to the application. I
am thinking XML/XSLT processing of the native Tapestry output. I would
place XML makers in the Tapestry template files of Tapestry components, and
then have the container (Orion in my case) post-process the output from
Tapestry.

Some of what I want to do would be to reorder the output stream base on
look-and-feel parameters. Is this a sound strategy or am I missing
something that Tapestry already can do ?

To implement the strategy, would the following work ?  I would sub-class
ApplicationServlet and overload the doService() method to set the Context
Type of the response.

abstract public class MyApplicationServlet extends
net.sf.tapestry.ApplicationServlet {

    protected void doService(HttpServletRequest request,
HttpServletResponse response)
      throws IOException, ServletException {

        response .setContectType ("text/xsl") ;
        super .doService (request, response) ;
    }
}

The container would then process the response after Tapestry is done. The
XML makers I would place in the corresponding template files would pass
information onto the XSLT process. Assuming that Tapestry will pass any
embedded information in component template file as is.  Actually I plan to
make the Context Type dependent on a properties file associated with each
Tapestry page. What are your suggestions or where to place the processing
of this information ?

I also see where it might be prudent to generate Tapestry output from
inside a component (not from the template file). I would implement this
kind of processing by sub-classing BaseComponent and overwriting the render
() method. Are there any simple examples of this ?

Craig J. Gregory
Dir. of Information Srevices
Blue Mountain Community College
PO Box 100
2411 NW Carden Av.
Pendleton, OR 97801
(541) 278-5825

Craig J. Gregory
Dir. of Information Srevices
Blue Mountain Community College
PO Box 100
2411 NW Carden Av.
Pendleton, OR 97801
(541) 278-5825





--__--__--

Message: 2
Subject: Re: [Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you decide!
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Date: Fri, 14 Jun 2002 07:43:53 -0400


What is critical for us is to be able to compile the core libraries with
1.2.2 if we need to patch them. In 2.0.2a, we had to change a few lines of
code to get it to compile.

It would be convenient to have the core jar compiled with 1.2.2, but I
don't see that as a firm requirement. Just make sure it CAN compile. The
contrib package should be fair game, though I'd encourage folks to not push
the envelope too far...maybe we need an experimental jar!

Thanks for asking.

-C





|--------+---------------------------------------------->
|        |          "Howard M. Lewis Ship"              |
|        |          <[EMAIL PROTECTED]>                  |
|        |          Sent by:                            |
|        |          [EMAIL PROTECTED]|
|        |          eforge.net                          |
|        |                                              |
|        |                                              |
|        |          06/14/2002 01:05 AM                 |
|        |                                              |
|--------+---------------------------------------------->

>---------------------------------------------------------------------------
-----------------------|
  |
|
  |       To:     "Tapestry Developer"
<[EMAIL PROTECTED]>                    |
  |       cc:
|
  |       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\McKoiDB.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\McKoiDB.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/NotificationBroadcast
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\McKoiDB.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






--__--__--

Message: 3
Date: Fri, 14 Jun 2002 09:52:52 -0400
From: Viktor Szathmary <[EMAIL PROTECTED]>
To:  [EMAIL PROTECTED]
Subject: Re: +1 JDK1.3![Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you
 decide!

hi,

+1 vote for JDK1.3..

JDK1.3 has been available for quite a long time now. even freebsd has a
native version these days... :) and upgrading on the serverside is much
less painful anyway...

    viktor



--__--__--

Message: 4
From: Jim Birchfield <[EMAIL PROTECTED]>
To: Tapestry Developer <[EMAIL PROTECTED]>
Date: Fri, 14 Jun 2002 10:25:41 -0400
Subject: [Tapestry-developer] Multi Selection List

We have used Tapestry with great success so far.  We have done some pretty
complex things while using it.  However, we are trying to do something
fairly simple that I don't think we should have to do something complex to
get it done.  We are very familiar with using a PropertySelectionModel to
show a drop down list.  However, we need to have a multiple select drop down
list.  We have bastardized the Palette component in the past, but wanted to
see if there was an easier way to get this functionality.  What do others do
when they need a multi selection list?

James Birchfield
Director, Application Development
Genscape, Inc.
(502) 583-2298 (o)
(502) 639-3136 (c)



--__--__--

Message: 5
From: Jim Birchfield <[EMAIL PROTECTED]>
To: Jim Birchfield <[EMAIL PROTECTED]>,        Tapestry
Developer<[EMAIL PROTECTED]>
Subject: RE: [Tapestry-developer] Multi Selection List
Date: Fri, 14 Jun 2002 10:30:26 -0400

OK, I am looking at the contrib. package and found the
MultiPropertySelection.  This might do what we need.

James Birchfield
Director, Application Development
Genscape, Inc.
(502) 583-2298 (o)
(502) 639-3136 (c)


-----Original Message-----
From: Jim Birchfield [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 14, 2002 10:26 AM
To: Tapestry Developer
Subject: [Tapestry-developer] Multi Selection List

We have used Tapestry with great success so far.  We have done some pretty
complex things while using it.  However, we are trying to do something
fairly simple that I don't think we should have to do something complex to
get it done.  We are very familiar with using a PropertySelectionModel to
show a drop down list.  However, we need to have a multiple select drop down
list.  We have bastardized the Palette component in the past, but wanted to
see if there was an easier way to get this functionality.  What do others do
when they need a multi selection list?

James Birchfield
Director, Application Development
Genscape, Inc.
(502) 583-2298 (o)
(502) 639-3136 (c)


_______________________________________________________________

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


--__--__--

Message: 6
From: "David Solis" <[EMAIL PROTECTED]>
To: "'Tapestry Developer'" <[EMAIL PROTECTED]>
Subject: RE: [Tapestry-developer] JBoss 3.0.0 or JDK 1.2.2 ... you decide!
Date: Fri, 14 Jun 2002 10:45:55 -0500

Add my vote to JBoss 3.0.x and jdk1.3

David




--__--__--

_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer


End of Tapestry-developer Digest


_______________________________________________________________

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

Reply via email to