Re: [JBoss-dev] Why is JDOM version in JBoss so old

2003-04-04 Thread Tom Coleman 

Is there something that replaces JDOM in 4.x?  

JDOM can make XML experts out of dummies, and if you're working with 
XML-based apps, it's nice to have in the server classpath.

Scott Stark wrote:

 
 ... On head jdom should be dropped.
 


---
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

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

2003-03-22 Thread Tom Coleman 
 
 Don't be too sure that there isn't a number of months of effort to pass the
 conformance suite. There are lots of edge cases and areas of interpretation
 when implementing from a spec. 
 

 Unless they give the compliance testing to Bill Burke.  He could probably
 get it done in a weekend.  
 
 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'm doing an integration with a partner that uses a certified server.
 Their server crashes.  My server doesn't.



---
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] Maven rumour

2003-03-03 Thread Tom Coleman 

Herr Buildmeister Jason casually mentioned in a recent post that he was 
looking at Maven.

This sounds like a severe case of gun jumping on the part of the Maven 
team to me.


 
 Someone pointed out a post today on the Maven-dev list which said that 
 JBoss wants to move to Maven. Is there any truth in this..?



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] FW: Open Source Excellence Awards

2003-01-16 Thread Tom Coleman 

 
 I think we can and should win the open source project as we have a more 
 mature code base and more downloads than any of the other projects.  
 

 I agree, but possibly for a different reason.

 No one else has anything close to a 'Marc' driving their project.  ;-)



---
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache 
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] PHP

2003-01-10 Thread Tom Coleman 

In the early days of Java, I read that a large retailer had about 70 Java 
programmers because it was a business decision.  It was the only tool
available that they could use to integrate their systems.

Most likely, Marc's decision to use PHP on the website is a business decision
as well.  The website has to be fluid, functional, and professional, 
require a mininum of time and attention, and it all has to be done Now.

So Marc found a ready-made solution that will solve 80% of his requirements.
The 20% that's missing is that it's not J2EE.

JSP is relatively new compared to PHP, and JSP/JSTL is significantly more
complex.  

It sounds like Mark has both an immediate plan and a vision for the future
all based on real-world requirements and recent practical experience 
wrestling with the forums.

It would be nice to see everything pure java.  Marc says we'll get there.
He's got us this far, hasn't he?  So having had our say (from the perspective
of ones not paying the bills), I suggest we all just get back to work.



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] 3.2 branch doesn't seem to compile

2002-11-07 Thread Tom Coleman 

I never noticed these tags before...

 but 3.2 compiled for me (on linux) using jdk1.3.1_06.

 [javac] Compiling 61 source files to
 C:\jboss\jboss-3.2\connector\output\classes
 C:\jboss\jboss-3.2\connector\src\main\org\jboss\resource\adapter\jdbc\local\
 LocalPreparedStatement.java:190: illegal cha
 racter: \64
 @JDK1.4START@
 ^


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power  Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-08 Thread Tom Coleman 


Food for thought?

From www.dictionary.com

Modesty   - The quality or state of being modest; that lowly temper
which accompanies a moderate estimate of one's own worth
and importance; absence of self-assertion, arrogance, and
presumption; humility respecting one's own merit

Pride - an excessively high opinion of oneself

Humility  - a modest estimate of one's own worth



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Fixing module defintions now for head, 3.0 3.2

2002-10-08 Thread Tom Coleman 


Why don't we set up a CVS testbed somewhere to test CVS changes?

You (editorial 'you') don't (shouldn't) commit changes to code without
thorough testing.  Considering what's at risk, it seems to me that CVS 
changes should be made even more cautiously.

This project already has too many 'moving targets' to try to deal with.


 I have to modify CVSROOT/modules to test, so please be patient if
 something does not function.  I will make sure that all jboss-* projects
 function by the days end.
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] README :: Thirdparty structure changed

2002-10-08 Thread Tom Coleman 


Oops.  Missed an important one...


From www.dictionary.com
 
Ego   - An inflated feeling of pride in your superiority to others


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Implementing a Resource Protection System?

2002-07-11 Thread Tom Coleman 


If Anatoly is not a good programmer, most of us are indeed wasting
our time and should probably take up carpentry or flower arranging.

Anatoly wrote:
 
 Again, not being a good programmer, is a horrible fate in CS world...
 


---
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases  more
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/docs petstore_frames_user.html

2001-11-14 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/14 10:24:10

  Added:   src/docs petstore_frames_user.html
  Log:
  Match 'user' pages color scheme
  
  Revision  ChangesPath
  1.1  newsite/src/docs/petstore_frames_user.html
  
  Index: petstore_frames_user.html
  ===
  !-- $Id: petstore_frames_user.html,v 1.1 2001/11/14 18:24:09 tmcsys Exp $ --
  html
  head
  titleJBoss Pet Store/title
  /head
  
  frameset frameborder=0 rows=230,* cols=1
frame noresize scrolling=no src=head.jsp
frame noresize src=/estore
  /frameset
  noframes
  a href=/estoreRun the Java Pet Store using JBoss/a
  /noframes
  /html
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtossl.xml

2001-11-13 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/13 10:23:27

  Modified:src/xdocs/howto howtossl.xml
  Log:
  Add Jetty SSL configuration
  
  Revision  ChangesPath
  1.2   +27 -13manual/src/xdocs/howto/howtossl.xml
  
  Index: howtossl.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtossl.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howtossl.xml  2001/09/18 21:38:31 1.1
  +++ howtossl.xml  2001/11/13 18:23:27 1.2
  @@ -1,5 +1,5 @@
   ?xml version = 1.0 encoding = UTF-8?
  -!-- $Id: howtossl.xml,v 1.1 2001/09/18 21:38:31 tmcsys Exp $ --
  +!-- $Id: howtossl.xml,v 1.2 2001/11/13 18:23:27 tmcsys Exp $ --
   !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
   section id=howtossl
titleUsing SSL with JBoss/title
  @@ -12,20 +12,16 @@
   
section
titleIntroduction/title
  - paraAdding SSL (Secure Socket Layer) support is simple using JBoss 
2.4 configured to use Embedded Tomcat 3.2.2. The specific release used was JBoss 2.4 
BETA Rel_2_4_0_23./para
  + paraAdding SSL (Secure Socket Layer) support is simple using JBoss 
2.4 with either Tomcat or Jetty Web containers. The specific releases used were JBoss 
2.4 BETA Rel_2_4_0_23 with Tomcat 3.2.2, and JBoss-2.4.0_Jetty-3.1.RC8-1./para
paraThe target system was a RH Linux 6.2 system using the Sun 1.3 
JDK and Sun's Secure Socket Extension, JSSE 1.0.2./para
  /section
   
section
titleOutstanding Deployment Issues/title
   formalpara
  - titleMultiple sites/title
  - paraJBoss-Tomcat apparently requires modification in order to 
support multiple site names and certificates./para
  + titleMultiple site certificates/title
  + paraSupport of certificates for multiple sites is currently under 
discussion.  Please post your requirements to the forums or the jboss-user mailing 
list./para
   /formalpara
  -formalpara
  - titleJBoss-Jetty/title
  - paraPlease post your experiences using SSL and JBoss-Jetty to the 
jboss-user mailing list./para
  -/formalpara

/section
section
  @@ -45,13 +41,12 @@
listitem
paraInstall JSSE/para
paraFollow steps 1 through 5 of the ulink 
url=http://java.sun.com/products/jsse/install.html;JSSE installation 
instructions/ulink./para
  -paraCopy the JSSE jars to your $TOMCAT_HOME/lib 
directory./para
   paraIf you need to run 'keytool' on your system to create 
and/or import certificates, copy the JSSE jars to $JAVA_HOME/jre/lib/ext./para
/listitem
listitem
paraGenerate a Server Key and Certificate/para
  -paraThe following shell script can be used to create a server 
certificate for testing:/para
  -paraNote that keystore files will be generated in the directory you 
run keytool from./para
  +paraThe following shell script can be used to create a self-signed 
server certificate for testing:/para
  +paraThe keystore file will be generated in the directory from which 
you run keytool.  Copy the keystore file to an appropriate directory./para
programlisting![CDATA[ 
   keytool -genkey -alias tomcat -keyalg RSA \
  -dname 'CN=your.domain.com, OU=Skunk Works Unit, O=Your Organization, L=Your 
Location, S=Your State, C=US' \
  @@ -63,8 +58,8 @@
paraIt should be possible to import existing certificates 
generated with OpenSSL using keytool.  See the section ulink 
url=http://jakarta.apache.org/tomcat/tomcat-3.2-doc/tomcat-ssl-howto.html#s6;Importing
 SSL certificates/ulink in the Tomcat documentation./para
/listitem
listitem
  - paraConfigure Tomcat/para
  - paraFind the section in the Tomcat server.xml 
configuration file that starts with, Uncomment this for SSL support.  Uncomment the 
following section, and insert the location of your server key./para
  + paraConfigure Web Container/para
  + paraIf using Tomcat - Find the section in the Tomcat 
server.xml configuration file that starts with, Uncomment this for SSL support.  
Uncomment the following section, and insert the location of your server key./para
programlisting![CDATA[ 
   Connector className=org.apache.tomcat.service.PoolTcpConnector
   Parameter name=handler 
  @@ -78,10 +73,29 @@
   /Connector
]]
  /programlisting
  +paraCopy the JSSE jars to your $TOMCAT_HOME/lib 
directory./para

[JBoss-dev] CVS update: newsite/src/docs petstore_frames.html

2001-11-13 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/13 14:26:50

  Modified:src/docs petstore_frames.html
  Log:
  Adapt to new site design
  
  Revision  ChangesPath
  1.4   +3 -4  newsite/src/docs/petstore_frames.html
  
  Index: petstore_frames.html
  ===
  RCS file: /cvsroot/jboss/newsite/src/docs/petstore_frames.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- petstore_frames.html  2001/10/04 00:17:28 1.3
  +++ petstore_frames.html  2001/11/13 22:26:50 1.4
  @@ -1,15 +1,14 @@
  +!-- $Id: petstore_frames.html,v 1.4 2001/11/13 22:26:50 tmcsys Exp $ --
   html
  -
   head
   titleJBoss Pet Store/title
   /head
   
  -frameset frameborder=0 rows=32%,* cols=1
  - frame noresize scrolling=no src=frametop.html
  +frameset frameborder=0 rows=230,* cols=1
  + frame noresize scrolling=no src=developers/head.jsp
frame noresize src=/estore
   /frameset
   noframes
   a href=/estoreRun the Java Pet Store using JBoss/a
   /noframes
   /html
  -
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/docs/common jboss-tomcat.jsp

2001-11-13 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/13 15:12:19

  Modified:src/docs/common jboss-tomcat.jsp
  Log:
  Fix the picture
  
  Revision  ChangesPath
  1.3   +3 -2  newsite/src/docs/common/jboss-tomcat.jsp
  
  Index: jboss-tomcat.jsp
  ===
  RCS file: /cvsroot/jboss/newsite/src/docs/common/jboss-tomcat.jsp,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- jboss-tomcat.jsp  2001/10/12 23:01:28 1.2
  +++ jboss-tomcat.jsp  2001/11/13 23:12:19 1.3
  @@ -1,3 +1,4 @@
  +%-- $Id: jboss-tomcat.jsp,v 1.3 2001/11/13 23:12:19 tmcsys Exp $ --%
   
   p class=headSTOP! USE THE BUNDLE

  @@ -9,7 +10,7 @@
   p class=headA FULL J2EE STACK
   
   
  -p class=textimg height=71 width=100 
src=pictures/tomcat_3.gif align=leftThe
  +p class=textimg height=71 width=100 
src=/pictures/tomcat_3.gif align=leftThe
 JBoss organization wants to 
deliver a complete J2EE based product to the market.
 The JBoss organization 
decided to integrate the Tomcat engine stack with a running
 version of JBoss in a single 
VM. Now you can serve all your servlet and JSP needs
  @@ -288,4 +289,4 @@
   /ol
   p class=textFor a full example including a servlet and an 
EJB, see the tomcat-test.ear
in the a class=link 
href=/zip_archives/contrib-cvs.zipcontrib/tomcat/a module
  - 
  \ No newline at end of file
  + 
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/metadata website-application-nosnaps.xml

2001-11-13 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/13 15:43:17

  Added:   src/metadata website-application-nosnaps.xml
  Log:
  Allow users to build website.ear without building and including snapshots.war.
  
  To build website and manual:
  
  build.sh -Dmodules=website,manual -Dsnapshot.disable=true 
-Dsnapshot-export-cvs.disable=true website
  
  To build website:
  
  build.sh -Dmodules=website -Dsnapshot.disable=true 
-Dsnapshot-export-cvs.disable=true website
  
  Revision  ChangesPath
  1.1  newsite/src/metadata/website-application-nosnaps.xml
  
  Index: website-application-nosnaps.xml
  ===
  ?xml version=1.0 encoding=UTF-8?
  !DOCTYPE application
  
  !-- $Id: website-application-nosnaps.xml,v 1.1 2001/11/13 23:43:17 tmcsys Exp $ --
  
  application
 display-nameJBoss Website/display-name
  
 module
web
   web-uriwebsite.war/web-uri
   context-root//context-root
/web
 /module
  
  /application
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite build.xml

2001-11-13 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/11/13 15:44:42

  Modified:.build.xml
  Log:
  Allow users to build website.ear without building and including snapshots.war.
  
  To build website and manual:
  
  build.sh -Dmodules=website,manual -Dsnapshot.disable=true 
-Dsnapshot-export-cvs.disable=true website
  
  To build website:
  
  build.sh -Dmodules=website -Dsnapshot.disable=true 
-Dsnapshot-export-cvs.disable=true website
  
  Revision  ChangesPath
  1.24  +24 -3 newsite/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/newsite/build.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- build.xml 2001/11/02 17:29:53 1.23
  +++ build.xml 2001/11/13 23:44:42 1.24
  @@ -10,7 +10,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.23 2001/11/02 17:29:53 mnf999 Exp $ --
  +!-- $Id: build.xml,v 1.24 2001/11/13 23:44:42 tmcsys Exp $ --
   
   project default=main name=JBoss Website/Website
   
  @@ -414,9 +414,12 @@
 !-- 
| Build all jar files.
  --
  -  target name=jars depends=compile description=Builds all jar
  -mkdir dir=${build.lib}/
  +  target name=jars depends=website-snaps,website-nosnaps description=Builds 
all jar
  +  /target
   
  +  target name=website-snaps 
  +depends=compile unless=snapshot.disable
  +mkdir dir=${build.lib}/
   war warfile=${build.lib}/website.war
 webxml=${build.metadata}/website-web.xml
 fileset dir=${build.docs}
  @@ -442,6 +445,24 @@
   
 /target
   
  +  target name=website-nosnaps 
  +depends=compile if=snapshot.disable
  +mkdir dir=${build.lib}/
  +war warfile=${build.lib}/website.war
  +  webxml=${build.metadata}/website-web.xml
  +  fileset dir=${build.docs}
  +include name=**/*/
  +  /fileset
  +/war
  +
  +ear earfile=${build.lib}/website.ear
  +  appxml=${build.metadata}/website-application-nosnaps.xml
  +  fileset dir=${build.lib}
  +include name=website.war/
  +  /fileset
  +/ear
  +
  +  /target
   
 !-- == --
 !-- Documents  --
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/docs/doco_files jps112-01.zip

2001-09-21 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/21 21:18:43

  Modified:src/docs/doco_files jps112-01.zip
  Log:
  Update directory structure
  
  Add commit to PopulateServlet.java per Jim Utter
  
  Revision  ChangesPath
  1.3   +97 -84newsite/src/docs/doco_files/jps112-01.zip
  
Binary file
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml

2001-09-21 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/21 21:24:17

  Modified:src/xdocs/howto howtopetstore.xml
  Log:
  Credit Jim Utter
  
  Revision  ChangesPath
  1.6   +3 -2  manual/src/xdocs/howto/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- howtopetstore.xml 2001/09/18 21:39:09 1.5
  +++ howtopetstore.xml 2001/09/22 04:24:17 1.6
  @@ -1,5 +1,5 @@
   ?xml version = 1.0 encoding = UTF-8?
  -!-- $Id: howtopetstore.xml,v 1.5 2001/09/18 21:39:09 tmcsys Exp $ --
  +!-- $Id: howtopetstore.xml,v 1.6 2001/09/22 04:24:17 tmcsys Exp $ --
   !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
   section id=howtopetstore
titleDeploying the Pet Store 1.1.2 Demo in JBoss/title
  @@ -22,7 +22,7 @@
paraPlease post your experiences with deploying the Pet Store in 
JBoss to the jboss-user mailing list./para
   formalpara
titleInitializing the Database/title
  - paraThe current Pet Store application should automatically 
build required database tables the first time the Pet Store application is started.  
Apparently the latest database schema is slightly different from the earlier release, 
so you may encounter problems if you have an existing Pet Store database from a 
previous installation.  When tring to determine the initial status of the database, 
this conflict may cause one of the drop commands to fail, and the application will not 
create the required tables.  If this is the case, you may need to manually drop all 
existing tables before deploying the Pet Store for the first time./para
  + paraThe Pet Store application should automatically build 
required database tables the first time the Pet Store application is started.  The 
latest database schema is slightly different from the earlier release, so you may 
encounter problems if you have an existing Pet Store database from a previous 
installation.  When tring to determine the initial status of the database, this 
conflict may cause one of the drop commands to fail, and the application will not 
create the required tables.  If this is the case, you may need to manually drop all 
existing tables before deploying the Pet Store for the first time.  It may help to 
turn off your browser cache while building the tables./para
   /formalpara
   formalpara
titleThe Admin Client/title
  @@ -44,6 +44,7 @@
listitemparaAaron Mulder/para/listitem
listitemparaCuong Tran/para/listitem
listitemparaJoseph King/para/listitem
  + listitemparaJim Utter/para/listitem
/itemizedlist
/section
section
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs jbossdocs.xml

2001-09-18 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/18 14:37:52

  Modified:src/xdocs jbossdocs.xml
  Log:
  Add Tomcat SSL Howto; fix DTD
  
  Revision  ChangesPath
  1.7   +6 -3  manual/src/xdocs/jbossdocs.xml
  
  Index: jbossdocs.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/jbossdocs.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- jbossdocs.xml 2001/09/18 18:14:06 1.6
  +++ jbossdocs.xml 2001/09/18 21:37:52 1.7
  @@ -1,6 +1,6 @@
   ?xml version=1.0 encoding=UTF-8?
  -!-- $Id: jbossdocs.xml,v 1.6 2001/09/18 18:14:06 dsundstrom Exp $ --
  -!DOCTYPE book SYSTEM 
file:/home/dain/work/jboss/jboss-all/thirdparty/oasis/docbook-xml/docbookx.dtd [
  +!-- $Id: jbossdocs.xml,v 1.7 2001/09/18 21:37:52 tmcsys Exp $ --
  +!DOCTYPE book SYSTEM file:@oasis.docbook.xml.root@/docbookx.dtd [
  !ENTITY preface.xml  SYSTEM preface.xml
  !ENTITY jbossintro.xml   SYSTEM jbossintro.xml
  !ENTITY cmp.xml  SYSTEM cmp.xml
  @@ -36,10 +36,12 @@
  !ENTITY howtowebcontainer.xmlSYSTEM howto/howto_webcontainer.xml
  !ENTITY howtoejbdoclet.xml   SYSTEM howto/howtoejbdoclet.xml
  !ENTITY howtoclientapplet.xmlSYSTEM howto/howtoclientapplet.xml
  +   !ENTITY howtocmp2.xmlSYSTEM howto/howtocmp2.xml
  +
  !ENTITY howtormhexamples.xml SYSTEM howto/howtormhexamples.xml
  !ENTITY howtopetstore.xmlSYSTEM howto/howtopetstore.xml
  !ENTITY howtococoon.xml  SYSTEM howto/howtococoon.xml
  -   !ENTITY howtocmp2.xmlSYSTEM howto/howtocmp2.xml
  +   !ENTITY howtossl.xml SYSTEM howto/howtossl.xml
   ]
   
   book
  @@ -126,6 +128,7 @@
 howtormhexamples.xml;
 howtopetstore.xml;
 howtococoon.xml;
  +  howtossl.xml;
  /chapter
   
   /book
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml

2001-09-18 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/18 14:39:09

  Modified:src/xdocs/howto howtopetstore.xml
  Log:
  Add link to patch file
  
  Revision  ChangesPath
  1.5   +3 -3  manual/src/xdocs/howto/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- howtopetstore.xml 2001/09/09 23:06:14 1.4
  +++ howtopetstore.xml 2001/09/18 21:39:09 1.5
  @@ -1,5 +1,5 @@
   ?xml version = 1.0 encoding = UTF-8?
  -!-- $Id: howtopetstore.xml,v 1.4 2001/09/09 23:06:14 tmcsys Exp $ --
  +!-- $Id: howtopetstore.xml,v 1.5 2001/09/18 21:39:09 tmcsys Exp $ --
   !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
   section id=howtopetstore
titleDeploying the Pet Store 1.1.2 Demo in JBoss/title
  @@ -55,7 +55,7 @@
/listitem
listitem
paraDownload the JBoss Pet Store patch file/para
  - paraRunning the Pet Store demo in JBoss requires 
several minor changes to deployment files in the Pet Store application (.ear) file. 
The patch is currently available in the documentation files section of the manual, it 
is named jps112-01.zip./para
  + paraRunning the Pet Store demo in JBoss requires 
several minor changes to deployment files in the Pet Store application (.ear) file. 
The current patch file, ulink 
url=http://www.jboss.org/doco_files/jps112-01.zip;jps112-01.zip/ulink is currently 
available in the documentation files section of the manual./para
/listitem
listitem
paraConfigure JBoss/para
  @@ -73,7 +73,7 @@
paraThis step adds the file jboss-web.xml to the 
WEB-INF directory in petstore.war, modifies the serverType in the web.xml file of that 
directory to identify the JBoss server to the application, and modifies the 
application.xml file in the META-INF directory of petstore.ear./para
itemizedlist
listitem
  - paraCopy the jps1.1.2-01.zip file to 
the root directory ($PETSTORE) of your Pet Store distribution. Change to this 
directory and unzip the file. /para
  + paraCopy the jps112-01.zip file to 
the root directory ($PETSTORE) of your Pet Store distribution. Change to this 
directory and unzip the file. /para
paraNote: This will overwrite the 
original web.xml file. /para
paraprogramlistingcd $PETSTORE
   unzip jps1.1.2-01.zip
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtossl.xml

2001-09-18 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/18 14:38:31

  Added:   src/xdocs/howto howtossl.xml
  Log:
  Add SSL Howto
  
  Revision  ChangesPath
  1.1  manual/src/xdocs/howto/howtossl.xml
  
  Index: howtossl.xml
  ===
  ?xml version = 1.0 encoding = UTF-8?
  !-- $Id: howtossl.xml,v 1.1 2001/09/18 21:38:31 tmcsys Exp $ --
  !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
  section id=howtossl
titleUsing SSL with JBoss/title
paraAuthor:author
firstnameTom/firstname
surnameColeman/surname
/author
email[EMAIL PROTECTED]/email  
/para
  
section
titleIntroduction/title
paraAdding SSL (Secure Socket Layer) support is simple using JBoss 
2.4 configured to use Embedded Tomcat 3.2.2. The specific release used was JBoss 2.4 
BETA Rel_2_4_0_23./para
paraThe target system was a RH Linux 6.2 system using the Sun 1.3 
JDK and Sun's Secure Socket Extension, JSSE 1.0.2./para
 /section
  
section
titleOutstanding Deployment Issues/title
  formalpara
titleMultiple sites/title
paraJBoss-Tomcat apparently requires modification in order to 
support multiple site names and certificates./para
  /formalpara
  formalpara
titleJBoss-Jetty/title
paraPlease post your experiences using SSL and JBoss-Jetty to the 
jboss-user mailing list./para
  /formalpara

/section
section
titleContributors:/title
itemizedlist
listitemparaScott Stark/para/listitem
/itemizedlist
/section
section
titleInstallation amp; Configuration/title
orderedlist
listitem
paraDownload JSSE/para
paraIf you are using JDK 1.3 or 1.2, JSSE is 
optional.  Download it from ulink url=http://java.sun.com/products/jsse;Sun's JSSE 
Page/ulink.  Jump through the hoops as required./para
  paraIf you are using JDK 1.4, JSSE is included.  But then, JDK 1.4 is 
another story./para
/listitem
listitem
paraInstall JSSE/para
paraFollow steps 1 through 5 of the ulink 
url=http://java.sun.com/products/jsse/install.html;JSSE installation 
instructions/ulink./para
   paraCopy the JSSE jars to your $TOMCAT_HOME/lib 
directory./para
   paraIf you need to run 'keytool' on your system to create 
and/or import certificates, copy the JSSE jars to $JAVA_HOME/jre/lib/ext./para
/listitem
   listitem
paraGenerate a Server Key and Certificate/para
  paraThe following shell script can be used to create a server 
certificate for testing:/para
  paraNote that keystore files will be generated in the directory you 
run keytool from./para
programlisting![CDATA[ 
  keytool -genkey -alias tomcat -keyalg RSA \
 -dname 'CN=your.domain.com, OU=Skunk Works Unit, O=Your Organization, L=Your 
Location, S=Your State, C=US' \
 -keypass changeit \
 -storepass changeit \
 -keystore server.keystore
]]
  /programlisting
paraIt should be possible to import existing certificates 
generated with OpenSSL using keytool.  See the section ulink 
url=http://jakarta.apache.org/tomcat/tomcat-3.2-doc/tomcat-ssl-howto.html#s6;Importing
 SSL certificates/ulink in the Tomcat documentation./para
/listitem
listitem
paraConfigure Tomcat/para
paraFind the section in the Tomcat server.xml 
configuration file that starts with, Uncomment this for SSL support.  Uncomment the 
following section, and insert the location of your server key./para
programlisting![CDATA[ 
  Connector className=org.apache.tomcat.service.PoolTcpConnector
  Parameter name=handler 
  value=org.apache.tomcat.service.http.HttpConnectionHandler/
  Parameter name=port 
  value=8443/
  Parameter name=socketFactory 
  value=org.apache.tomcat.net.SSLSocketFactory /
  Parameter name=keystore 
value=/usr/java/jakarta-tomcat-3.2.2/server.keystore / 
  Parameter name=keypass value=changeit / 
  /Connector
]]
 /programlisting
/listitem
   listitem
paraStart JBoss/para
paraStart JBoss and point your browser to 
https://your-server-name.your-domain:8443 to test your

[JBoss-dev] CVS update: manual/src/xdocs/howto howtococoon.xml

2001-09-11 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/11 12:18:19

  Added:   src/xdocs/howto howtococoon.xml
  Log:
  Document Cocoon 2 Deployment on JBoss-Tomcat
  
  Revision  ChangesPath
  1.1  manual/src/xdocs/howto/howtococoon.xml
  
  Index: howtococoon.xml
  ===
  ?xml version = 1.0 encoding = UTF-8?
  !-- $Id: howtococoon.xml,v 1.1 2001/09/11 19:18:19 tmcsys Exp $ --
  !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
  section id=howtococoon
titleDeploying Cocoon 2 in JBoss/title
paraAuthor:author
firstnameTom/firstname
surnameColeman/surname
/author
email[EMAIL PROTECTED]/email  
/para
  
section
titleIntroduction/title
paraApache Cocoon is a next-generation XML publishing framework.  
According to the developers, Cocoon 2 is currently beta quality./para
paraCocoon 2 is very easily deployed using JBoss 2.4 configured to 
use Embedded Tomcat 3.2.2. The specific release used was JBoss 2.4 BETA 
Rel_2_4_0_23./para
paraThe deployment was on a RH Linux 6.2 system using the Sun 1.3 
jdk./para/section
section
titleOutstanding Deployment Issues/title
  formalpara
titleSQL examples/title
paraThis documentation does not address getting the SQL examples to 
work.  If you have successfully deployed the Cocoon 2 SQL examples using JBoss, please 
post your experiences to the jboss-user mailing list./para
  /formalpara
  formalpara
titleCocoon 2 and JBoss-Jetty/title
paraIf you have successfully deployed Cocoon 2 using JBoss-Jetty, 
please post your experiences to the jboss-user mailing list./para
  /formalpara
  formalpara
titleX Server required/title
paraOne of the advanced features of Cocoon 2 is support of Scalable 
Vector Graphics.  On Unix platforms, this feature requires access to an X server.  If 
your system does not run an X server and you have problems with the sitemap, search 
the ulink url=http://xml.apache.org/cocoon2/mail-archives.html;Cocoon Mailing List 
Archives/ulink for Xvfb./para
  /formalpara

/section
section
titleContributors:/title
itemizedlist
listitemparaDavid Rothman/para/listitem
listitemparaJan Heise/para/listitem
listitemparaTom Coleman/para/listitem
/itemizedlist
/section
section
titleInstallation amp; Configuration/title
orderedlist
listitem
paraDownload Cocoon 2/para
paraYou can get the source from ulink 
url=http://xml.apache.org/cocoon2/dist;The Apache Project's XML Download 
Page/ulink. We used the Cocoon-2.0b2 package./para
/listitem
listitem
paraBuild the Cocoon 2 WAR package/para
paraFollow the instructions in the ulink 
url=http://xml.apache.org/cocoon2/install.html;Cocoon installation 
instructions/ulink to build the Apache Cocoon 2 WAR package.  The resulting .war 
file will be deployed in the $JBOSS_HOME/deploy directory./para
/listitem
listitem
paraModify JBoss and Tomcat JARS and Classpath/para
paraThe Cocoon installation instructions have a 
section on installing on JBoss 2.2.2 with Tomcat 3.2.2.  These instructions work for 
JBoss 2.4.x.  Remove the unneeded JAR files from the JBoss and Tomcat /lib 
directories.  If you are using JBoss 2.4.x, ignore the reference to xml.jar./para
paraAdd xerces_1_4_1.jar to $JBOSS_CLASSPATH and 
comment out the JAXP references in $JBOSS_HOME/bin/run.sh./para
/listitem
listitem
paraStart JBoss/para
paraStart JBoss and copy the cocoon.war to the 
deploy directory. You should see JBoss deploy Cocoon./para
/listitem
listitem
paraRun Cocoon/para
paraPoint your browser to 
http://your-server-name.your-domain:8080/cocoon to start Cocoon./para
/listitem
/orderedlist
/section
  /section
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs jbossdocs.xml

2001-09-11 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/11 12:17:36

  Modified:src/xdocs jbossdocs.xml
  Log:
  Document Cocoon 2 Deployment on JBoss-Tomcat
  
  Revision  ChangesPath
  1.4   +5 -4  manual/src/xdocs/jbossdocs.xml
  
  Index: jbossdocs.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/jbossdocs.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- jbossdocs.xml 2001/09/02 20:21:36 1.3
  +++ jbossdocs.xml 2001/09/11 19:17:36 1.4
  @@ -1,4 +1,5 @@
   ?xml version=1.0 encoding=UTF-8?
  +!-- $Id: jbossdocs.xml,v 1.4 2001/09/11 19:17:36 tmcsys Exp $ --
   !DOCTYPE book SYSTEM file:@oasis.docbook.xml.root@/docbookx.dtd [
  !ENTITY preface.xml  SYSTEM preface.xml
  !ENTITY jbossintro.xml   SYSTEM jbossintro.xml
  @@ -15,8 +16,6 @@
  !ENTITY resource.xml SYSTEM resource.xml
  !ENTITY howtomssql.xml   SYSTEM howto/howtomssql.xml
  !ENTITY howtotomcat.xml  SYSTEM howto/howtotomcat.xml
  -   !ENTITY howtormhexamples.xml SYSTEM howto/howtormhexamples.xml
  -   !ENTITY howtopetstore.xmlSYSTEM howto/howtopetstore.xml
  !ENTITY howtojmx.xml SYSTEM howto/howtojmx.xml
  !ENTITY howtotimer.xml   SYSTEM howto/howtotimer.xml
  !ENTITY howtoj2eedeployer.xmlSYSTEM howto/howtoj2eedeployer.xml
  @@ -37,10 +36,11 @@
  !ENTITY howtowebcontainer.xmlSYSTEM howto/howto_webcontainer.xml
  !ENTITY howtoejbdoclet.xml   SYSTEM howto/howtoejbdoclet.xml
  !ENTITY howtoclientapplet.xmlSYSTEM howto/howtoclientapplet.xml
  +   !ENTITY howtormhexamples.xml SYSTEM howto/howtormhexamples.xml
  +   !ENTITY howtopetstore.xmlSYSTEM howto/howtopetstore.xml
  +   !ENTITY howtococoon.xml  SYSTEM howto/howtococoon.xml
   ]
   
  -!-- $Id: jbossdocs.xml,v 1.3 2001/09/02 20:21:36 gropi Exp $ --
  -
   book
  bookinfo
 titleJBoss 2.2+ Documentation/title
  @@ -118,6 +118,7 @@
 titleThird Party Examples/title
 howtormhexamples.xml;
 howtopetstore.xml;
  +  howtococoon.xml;
  /chapter
   
   /book
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/src/docs/doco_files jps112-01.zip

2001-09-11 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/11 14:20:47

  Modified:src/docs/doco_files jps112-01.zip
  Log:
  Add 'Powered By JBoss' graphic to footer.jsp
  
  Revision  ChangesPath
  1.2   +166 -24   newsite/src/docs/doco_files/jps112-01.zip
  
Binary file
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml

2001-09-09 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/09/09 16:06:14

  Modified:src/xdocs/howto howtopetstore.xml
  Log:
  Add JBoss-Jetty Deployment information
  
  Revision  ChangesPath
  1.4   +9 -11 manual/src/xdocs/howto/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- howtopetstore.xml 2001/09/01 00:56:48 1.3
  +++ howtopetstore.xml 2001/09/09 23:06:14 1.4
  @@ -1,4 +1,5 @@
   ?xml version = 1.0 encoding = UTF-8?
  +!-- $Id: howtopetstore.xml,v 1.4 2001/09/09 23:06:14 tmcsys Exp $ --
   !--DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN 
docbookx/docbookx.dtd--
   section id=howtopetstore
titleDeploying the Pet Store 1.1.2 Demo in JBoss/title
  @@ -13,8 +14,9 @@
titleIntroduction/title
paraThe Pet Store sample application (demo) is a relatively robust, 
well-documented demonstration of J2EE technology and concepts. It implements MVC 
(Model-View-Controller) architecture./para
paraThe Pet Store demo can allow developers to gain familiarity with 
J2EE concepts including application portability, a key J2EE design objective./para
  - paraThe Pet Store has been successfully deployed in JBoss 2.4 BETA 
configured to use Embedded Tomcat 3.2.2 using Sun 1.3 jdk on RH Linux 6.2. The steps 
provided below apply to JBoss 2.4 BETA Rel_2_4_0_23./para
  - /section
  + paraThe Pet Store has been most recently deployed using the 
JBoss-Jetty package, ulink 
url=http://www.jboss.org/binary.jsp;JBoss-2.4.0_Jetty-3.1.RC8-1/ulink. If you use 
the JBoss-Jetty package, you will have to add Pet Store DB Pools to the jboss.jcml 
file in the jboss/conf/jetty directory./para
  + paraThe Pet Store had previously been deployed using a JBoss 2.4 
BETA configured to use Embedded Tomcat 3.2.2. The specific release used was JBoss 2.4 
BETA Rel_2_4_0_23./para
  + paraBoth deployments were on a RH Linux 6.2 system using the Sun 1.3 
jdk./para/section
section
titleOutstanding Deployment Issues/title
paraPlease post your experiences with deploying the Pet Store in 
JBoss to the jboss-user mailing list./para
  @@ -24,17 +26,12 @@
   /formalpara
   formalpara
titleThe Admin Client/title
  - paraThe Admin application apparently needs some work on the 
deployment descriptors.  Please post your experences with the Admin application to the 
mailing list./para
  -/formalpara
  -formalpara
  - titleJetty Deployment/title
  - paraThe Pet Store should deploy using Jetty.  Please post 
your experences with deploying the Pet Store using Jetty to the mailing list./para
  + paraWe need JBoss deployment descriptors for the Admin 
application.  If you have successfully deployed the Admin application using JBoss, 
please post them to one of the Forums or to the jboss-user mailing list./para
   /formalpara
   formalpara
titlePet Store Security/title
paraThe current release of the Pet Store handles security at 
the application level.  It does require that you configure JBoss or Tomcat security 
services./para
   /formalpara
  -

/section
section
  @@ -61,8 +58,9 @@
paraRunning the Pet Store demo in JBoss requires 
several minor changes to deployment files in the Pet Store application (.ear) file. 
The patch is currently available in the documentation files section of the manual, it 
is named jps112-01.zip./para
/listitem
listitem
  - paraConfigure JBoss to use Embedded Tomcat/para
  - paraYou need a servlet container to run the 
petstore. These instructions use Tomcat 3.2.2. You can either use a bundled binary 
JBoss + Tomcat, or see the instructions to configure JBoss to use Embedded Tomcat in 
xref linkend=howtotomcat/./para
  + paraConfigure JBoss/para
  + paraYou need a servlet container to run the Java Pet 
Store. If you're using the JBoss-Jetty or JBoss-Tomcat releases, the server is 
preconfigured./para
  + paraIf you're using a stand-alone JBoss release with 
Tomcat, see the structions to configure JBoss to use Embedded Tomcat in xref 
linkend=howtotomcat/./para
/listitem
listitem
paraSelect a Database/para
  @@ -104,7 +102,7 @@
/listitem
listitem
paraAdd JARS to JBoss/para
  -

[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml

2001-08-31 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/08/31 12:00:20

  Modified:src/xdocs/howto howtopetstore.xml
  Log:
  give prominence to comment on the application's 'Table Madness'
  
  Revision  ChangesPath
  1.2   +3 -1  manual/src/xdocs/howto/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howtopetstore.xml 2001/08/29 09:19:37 1.1
  +++ howtopetstore.xml 2001/08/31 19:00:20 1.2
  @@ -19,6 +19,9 @@
titleOutstanding Deployment Issues/title
paraPlease post your experiences with deploying the Pet Store in 
JBoss to the jboss-user mailing list./para
   formalpara
  + titleInitializing the Database/title
  + paraThe current Pet Store application should automatically 
build required database tables the first time the Pet Store application is started.  
Apparently the latest database schema is slightly different from the earlier release, 
so you may encounter problems if you have an existing Pet Store database from a 
previous installation.  When tring to determine the initial status of the database, 
this conflict may cause one of the drop commands to fail, and the application will not 
create the required tables.  If this is the case, you may need to manually drop all 
existing tables before deploying the Pet Store for the first time./para
  +/formalpara
titleThe Admin Client/title
paraThe Admin application apparently needs some work on the 
deployment descriptors.  Please post your experences with the Admin application to the 
mailing list./para
   /formalpara
  @@ -96,7 +99,6 @@
paraModify the Cloudscape startup command to use 
port 1098./para
paraYou do this by adding -port port_number. For 
example:/para
programlistingjava ... RmiJdbc.RJJdbcServer -port 
1098 COM.cloudscape.core.JDBCDriver/programlisting
  - paraThe current Pet Store application should 
automatically build required databases the first time the application is started.  
Apparently, the schema is slightly different from the earlier release, so you may 
encounter problems if you have an existing Pet Store database from a previous 
installation.  If this is the case, you may need to manually drop all existing 
tables./para
paraStart Cloudscape./para
/listitem
listitem
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: manual/src/docs howtopetstore.xml

2001-08-22 Thread Tom Coleman 

  User: tmcsys  
  Date: 01/08/22 08:10:57

  Modified:src/docs howtopetstore.xml
  Log:
  Update Pet Store manual documentation:
  
JBoss 2.4 BETA
Pet Store 1.1.2
  
  Revision  ChangesPath
  1.2   +18 -59manual/src/docs/howtopetstore.xml
  
  Index: howtopetstore.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/howtopetstore.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howtopetstore.xml 2001/04/27 08:46:30 1.1
  +++ howtopetstore.xml 2001/08/22 15:10:57 1.2
  @@ -1,6 +1,6 @@
   ?xml version = 1.0 encoding = UTF-8?
   section id=howtopetstore
  - titleDeploying the Pet Store 1.1.1 Demo in JBoss/title
  + titleDeploying the Pet Store 1.1.2 Demo in JBoss/title
paraAuthor:author
firstnameTom/firstname
surnameColeman/surname
  @@ -12,35 +12,29 @@
titleIntroduction/title
paraThe Pet Store sample application (demo) is a relatively robust, 
well-documented demonstration of J2EE technology and concepts. It implements MVC 
(Model-View-Controller) architecture./para
paraThe Pet Store demo can allow developers to gain familiarity with 
J2EE concepts including application portability, a key J2EE design objective./para
  - paraThe Pet Store has been successfully deployed in JBoss PRE 2.1 
configured to use Embedded Tomcat and Tomcat 3.2.1/Apache using Sun 1.3 jdk on Linux. 
The steps provided below apply to JBoss PRE 2.1 since 21st January 2001./para
  + paraThe Pet Store has been successfully deployed in JBoss 2.4 BETA 
configured to use Embedded Tomcat 3.2.2 using Sun 1.3 jdk on RH Linux 6.2. The steps 
provided below apply to JBoss 2.4 BETA Rel_2_4_0_23./para
/section
section
titleOutstanding Deployment Issues/title
paraPlease post your experiences with deploying the Pet Store in 
JBoss to the jboss-user mailing list./para
section
  - titleThe security adapter/title
  - paraThe Pet Store implements non-portable security code that 
works only with the J2EE RI (Reference Implementation) server. /para
  - paraThe non-portable code is contained in the 
J2eeSecurityAdapter class. The JBoss Pet Store patch replaces this class with a 
JBossSecurityAdapter class that implements the SecurityAdapter interface./para
  - paraThe steps below change the value for 
securityAdapterClassName in the Pet Store application to use JBossSecurityAdapter. 
/para
  - paraSee the /docs/security.html page in the Pet Store demo 
for more information. /para
  - /section
  - section
  - titleAdding new users/title
  - paraIn order to add new users, you have to configure Tomcat 
to use a JDBCRealm. See below for details./para
  - /section
  - section
titleThe Admin Client/title
  - paraWe still need JBoss specific Deployment descriptors for 
the Admin client application. Please post them to the mailing list if you have 
them./para
  + paraThe Admin application apparently needs some work on the 
deployment descriptors.  Please post your experences with the Admin application to the 
mailing list./para
  + titleJetty Deployment/title
  + paraThe Pet Store should deploy using Jetty.  Please post 
your experences with deploying the Pet Store using Jetty to the mailing list./para
  + titlePet Store Security/title
  + paraThe current release of the Pet Store handles security at 
the application level.  It does require that you configure JBoss or Tomcat security 
services./para
/section
/section
section
  - titleOriginal contributers/title
  + titleContributors:/title
itemizedlist
listitemparaMike Lueders, Richard Gyger - Focus 
Technologies/para/listitem
listitemparaScott Stark/para/listitem
listitemparaAnatoly Ackerman/para/listitem
listitemparaTom Coleman/para/listitem
listitemparaAaron Mulder/para/listitem
  + listitemparaCuong Tran/para/listitem
/itemizedlist
/section
section
  @@ -48,16 +42,15 @@
orderedlist
listitem
paraDownload the Pet Store/para
  - paraYou can get the source from ulink 
url=http://java.sun.com/j2ee/download.html#blueprints;Sun's J2EE Download 
Page/ulink. It's in the J2EE Blueprints package. Download the 1.1.1 version. 
Unpack it anywhere.

Re: [JBoss-dev] Support for WebLogic and other vendor jars

2001-04-02 Thread Tom Coleman 

Scott wrote:

 
 I would rather not have knowledge of 3rd party app server deployment
 descriptors in the core JBoss code as it would only complicate understanding
 of how the jboss.xml and standardjboss.xml descriptor are used. Its a fine
 idea but it could be implemented via a utility that transformed the app 
 server specific jar into a jar with a jboss.xml descriptor.
 

 Providing WL - JBoss compatibility is an excellent idea.

 I think that a "deployment conversion/translation utility" would be the way 
 to go, however.   The utility could hopefully be expanded to deploy apps
 packaged for other servers.

 This approach might not be as intellectually stimulating as hacking the 
 deployer, but I agree with Scott that this logic belongs outside of the core.

 Tom

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Support for WebLogic and other vendor jars

2001-04-02 Thread Tom Coleman 

 
 I agree with both of you that it should NOT be part of the core code,
 thats why I suggested to refactor that section to support various different
 types via a plugin, once it was working.
 

  I must have missed that.

 An external utility is an extra step that a developer needs to go through to
 write beans, and results in two xml files. It is much nicer just to have
 one, this follows the "drop it in and run it" philosophy of JBoss. 

  I agree that a utility is an extra step, but I think it would be a price
  that a developer would be willing to pay in order to deploy on another 
  server.

  I just saw a comment posted by a WL user that he doubted whether _any_ tool
  would be able to convert the WL-specific ejb-jar descriptor.  

  You must think it can be done.

 I was thinking along the lines of having this behavior configurable in an 
 MBean, and off by default. If it was on then the server would also read in 
 the weblogic-ejb-jar.xml
 
  If you think it can be done and eliminate the need for a utility in the 
  process, I guess it sounds good to me.  

  Anything that allows JBoss to deploy WL apps sounds good to me.

  Scott?


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development