[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-02-27T18:26:15 Editor: 172.150.122.85 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -125,6 +125,6 @@ || Laurent Foret || Bordeaux || Aquitaine|| France || || || Adam Carbone || Middleboro || Massachusetts || USA || Senior Developer || || Uijin Hong || Seoul || Seoul || Korea || || - +|| Anita Kulshreshtha || Cary || North Carolina || USA || || -CategoryCategory +CategoryCategory
[Apache Geronimo Wiki] Updated: KnownWorkingConfigurations
Date: 2004-02-28T13:04:27
Editor: JacekLaskowski [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: KnownWorkingConfigurations
URL: http://wiki.apache.org/geronimo/KnownWorkingConfigurations
Add recommendation about using the latest final release of JDK
Change Log:
--
@@ -1,4 +1,6 @@
-This page intends to list known working configurations for Geronimo
BuildingAndRunning
+This page intends to list known working configurations for Geronimo
BuildingAndRunning.
+
+{{{Note}}}: It's always recommended to use the latest final release of JDK on
your operating system. Maven RC1 is the only one that is reported to work
properly. There're some reports about having problems with different
configurations than those stated in that document.
'''Contents'''
[[TableOfContents]]
@@ -7,8 +9,8 @@
Known to work as of 10 February 2004:
= Windows =
== Windows 2000 sp2 ==
-Sun Java 2 SDK 1.4.2
-Maven 1.0 beta 10
+Sun Java 2 SDK 1.4.2_03
+Maven 1.0 rc1
== Windows XP sp1 ==
Sun Java 2 SDK 1.4.0_01, 1.4.1_02, 1.4.2, 1.4.2_02
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-02-25T00:35:07
Editor: 208.42.65.236
Wiki: Apache Geronimo Wiki
Page: BuildingAndRunning
URL: http://wiki.apache.org/geronimo/BuildingAndRunning
no comment
Change Log:
--
@@ -18,7 +18,12 @@
$ cd incubator-geronimo
$ cvs -qz3 update -dP
$ maven
-$ maven run:server
+$ java -jar target/bin/server.jar org/apache/geronimo/Server
+}}}
+
+To run server with the debug console web application
+{{{
+$ java -jar target/bin/server.jar org/apache/geronimo/DebugConsole
}}}
You should check back here occasionally as things may well change.
@@ -42,8 +47,6 @@
= General Advice =
-On Jan 21, 2004, we tagged the fairly stable current version and commenced
rewriting the deployment structure. Until this process is complete, you may
wish to experiment with the tagged version by checking out the
last_geronimombean branch. You may wish to check on the IRC channel and
mailing list to see how far the rewrite has proceeded.
-
If having problems building Geronimo, make sure it isn't simply because your
Maven repository has become 'corrupted' or out of sync:
Delete (or temporarily rename) the .maven directory in your home directory and
try building Geronimo again.
@@ -81,21 +84,27 @@
= Running The Server =
== For HEAD revision: ==
-(Feb 12, 2004) Deployment is still changing but hopefully is a little less
fraught than it has been for the last couple of weeks. There is a now a
standalone deployer (bin/deploy.jar) that is a front-end to a GBean based
deployment system. Currently there is a GBean deployer but work is going on to
move the WAR and RAR deployers over.
Configurations are pre-built for the Geronimo server.
-||Config ID||Purpose||
-||org/apache/geronimo/System||Critical services for all server configurations||
-||org/apache/geronimo/Server||Normal server configuration||
+||Config ID||Purpose||Parent Configuration
+||org/apache/geronimo/System||Critical services for all server
configurations||none||
+||org/apache/geronimo/Server||Normal server
configuration||org/apache/geronimo/System||
+||org/apache/geronimo/DebugConsole||Debug console web
application||org/apache/geronimo/Server||
To run use the `server.jar` command:
{{{
$ cd target
-$ java -jar bin/server.jar config-store org/apache/geronimo/System
org/apache/geronimo/Server
+$ java -jar bin/server.jar org/apache/geronimo/Server
+}}}
+
+The `server.jar` command starts the specified configuration and all parent
configurations, so the following command will start System, Server, and
DebugConsole:
+{{{
+$ cd target
+$ java -jar bin/server.jar org/apache/geronimo/DebugConsole
}}}
-To stop the server use ctrl-C or an equivilent; a proper shutdown command will
be made available when the deployment includes the remoting framework.
+To stop the server use ctrl-C or an equivalent; a proper shutdown command will
be made available when the deployment includes the remoting framework.
You can also start the server using maven run:server or maven
debug:server, but startup using maven disables the ctrl-C proper shutdown.
@@ -106,22 +115,18 @@
You can find the schema files in ${geronimo.base.dir}/schema
-To deploy a new configuation use the `deploy.jar` command:
+To deploy a new configuration use the `deploy.jar` command:
{{{
$ cd target
-$ java -jar bin/deploy.jar --install --plan your-plan.xml --store
config-store --deployer org/apache/geronimo/ServiceDeployer
+$ java -jar bin/deploy.jar --install --plan your-plan.xml
}}}
-The need to define the store and deployer will be removed soon when the WAR
and RAR deployers have been converted. You should also only run this with the
server stopped - online deployment will be available soon when default
deployment includes the remoting layer.
-
-== For the legacy last_geronimombean tagged copy: ==
-Once you've downloaded the source code, installed Maven and built the server,
type `maven run:main` to run the server.
-As of December, 2003, there is no way to stop the server other than killing
it, control-C or other such means.
-
+You should only run this with the server stopped - online deployment will be
available soon when default deployment includes the remoting layer.
-= Accessing The Geronimo-Web-Console =
+= Accessing The Debug Console =
-Enter http://localhost:8080/geronimo-web-console to access the JMX Debug
Application.
+The debug console is only available when running the
org/apache/geronimo/DebugConsole configuration.
+Enter http://localhost:8080/debug-console in to you browser to access the JMX
Debug Application.
= Cleaning your workspace =
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-02-25T00:39:02 Editor: 208.42.65.236 Wiki: Apache Geronimo Wiki Page: BuildingAndRunning URL: http://wiki.apache.org/geronimo/BuildingAndRunning no comment Change Log: -- @@ -87,8 +87,8 @@ Configurations are pre-built for the Geronimo server. -||Config ID||Purpose||Parent Configuration -||org/apache/geronimo/System||Critical services for all server configurations||none|| +||Config ID||Purpose||Parent Configuration|| +||org/apache/geronimo/System||Critical services for all server configurations||-none-|| ||org/apache/geronimo/Server||Normal server configuration||org/apache/geronimo/System|| ||org/apache/geronimo/DebugConsole||Debug console web application||org/apache/geronimo/Server||
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-02-25T05:24:27 Editor: 218.148.24.1 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -124,6 +124,7 @@ || Greg Kerdemelidis || Christchurch || Canterbury || New Zealand || J2EE architect / developer; Director of [http://www.genixsystems.com/ Genix Systems] || || Laurent Foret || Bordeaux || Aquitaine|| France || || || Adam Carbone || Middleboro || Massachusetts || USA || Senior Developer || +|| Uijin Hong || Seoul || Seoul || Korea || || CategoryCategory
[Apache Geronimo Wiki] Updated: KnownWorkingConfigurations
Date: 2004-02-25T05:28:47 Editor: 218.148.24.1 Wiki: Apache Geronimo Wiki Page: KnownWorkingConfigurations URL: http://wiki.apache.org/geronimo/KnownWorkingConfigurations no comment Change Log: -- @@ -14,6 +14,10 @@ Sun Java 2 SDK 1.4.0_01, 1.4.1_02, 1.4.2, 1.4.2_02 Maven 1.0 rc1 +== Windows 2003 == +Sun Java 2 SDK 1.4.2_03 +Maven 1.0 RC1 + = Linux = == Debian Linux (Unstable) == Sun Java 2 SDK 1.4.2 (Blackdown-1.4.1-01 works too)
[Apache Geronimo Wiki] Updated: KnownWorkingConfigurations
Date: 2004-02-23T09:57:14 Editor: PhilipMarkDonaghy [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: KnownWorkingConfigurations URL: http://wiki.apache.org/geronimo/KnownWorkingConfigurations Fixed a error in wiki syntax Change Log: -- @@ -20,13 +20,13 @@ Maven 1.0 beta 10 == RedHat Linux 8 == -Sun Java 2 SDK 1.4.2_01 +Sun Java 2 SDK 1.4.2_01br java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) -Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) +Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode)br Maven 1.0 rc 1 -== RedHat Linux 9== +== RedHat Linux 9 == Sun Java 2 SDK 1.4.2_02 Maven 1.0-rc1-SNAPSHOT
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-21T20:15:09 Editor: 67.80.48.169 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -1,4 +1,4 @@ -Hola +Gisantes Gigantes! === Table === ||diego||esteban||emanuel||
[Apache Geronimo Wiki] New: Architecture/WorkManager
Date: 2004-02-22T10:21:09 Editor: JeremyBoynes [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: Architecture/WorkManager URL: http://wiki.apache.org/geronimo/Architecture/WorkManager no comment New Page: This page describes the mechanisms in Geronimo that are used to control and schedule the application workload = Worker Pools = J2EE has a synchronous processing model where Java Threads are used to provide the processing context for a request. As a result, application work can be characterized as relatively long running with blocking. In other words, application work such as a Servlet request or EJB invocation runs on a single thread for a relatively long time, cannot be transfered to another thread (due to context on the stack), and occasionally blocks for extended periods (seconds) e.g to talk to a database or perform disk I/O. Invokers in Geronimo responsible for initiating application work should obtain a Thread from an external Worker Pool. This allows System Administrators to manage the thread resources available on the system for consumption by application work. On larger systems, System Administrators should be able to create multiple pools as needed; for example, to limit the number of OS threads used by the application server, or to affinity threads to specific hardware resources (note this may need platform specific extensions). Examples of such invokers are: * EJB invokers for transports such as RMI, IIOP, HTTP * Servlet invokers * Resource Adapters * EJB Timer Service * Web Service Invoker Other less obvious examples include: * HTTP Session passifier (which may need to dump large amounts of state to disk) * Stateful Session passifier (again, saving state) * Cluster state redistribution * Application distribution (copying the app during deployment) The size of a worker pool is relatively larger and determined by factors such as the number of available processors, the amount of concurrency in the appplication, and the amount of time a thread spends blocked. = Event Pools = Geronimo also has a need for rapid processing in response to events such as timer expirations, operator interactions or network notifications. This workload can be characterizes as short term and non-blocking. In other words it runs for a few micro or milliseconds and does not block for external resources such as databases or disks. Such a thread may be used to schedule workers; for example, it may determine a series of longer running tasks that need to be performed and then assign them to a work queue for processing by workers. System administrators may wish to allocate such threads to specific resources, or may wish to raise the priority of these threads to ensure system housekeeping can still be performed should the worker pool be overloaded. Again, such operations may need platform specific extensions. The size of a worker pool is likely to be relatively small and fairly independent of application workload. = Use Case = The passivation process for Stateful Session Beans can be used as a use case for these pools. To improve performance, instances may be retained in memory between transaction; however, the container is responsible for discarding the instance if the client abandons it. In one possible implementation of this, the container would register a timer event that would periodically fire. When the timer expires, a Thread would be selected from the event pool and used to notify the stateful session container. The container would use this thread to determine which, if any, instances needed to be passivated and would enqueue worker tasks to actually passify them; the event thread would then be returned to the event pool. The passivation tasks, which are longer running and may block on disk I/O, would then be scheduled from the worker pool. Note this is illustrative and not intended as a description of how SFSB passivation actually works in Geronimo.
[Apache Geronimo Wiki] Updated: Architecture
Date: 2004-02-22T10:23:23 Editor: JeremyBoynes [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: Architecture URL: http://wiki.apache.org/geronimo/Architecture no comment Change Log: -- @@ -27,3 +27,4 @@ * [wiki:/Validator Validator] * [wiki:/WebContainer Web Container] * [wiki:/WebServices Web Services] + * [wiki:/WorkManager Work Manager]
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-02-21T03:29:09 Editor: PhilipMarkDonaghy [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself Modified my name, link, and location Change Log: -- @@ -108,7 +108,7 @@ || Simon Matic Langford || Leamington Spa || Warwickshire || UK || J2EE developer || || Sergio Eduardo Rodrigues || São Paulo || São Paulo || Brazil || J2EE Developer || || Massimiliano Parlione || Teramo || Abruzzo || Italy || Java Developer || -|| Philip Mark Donaghy || Paris || IDF || France || Open Source GIS and Java || +|| Philip Mark Donaghy || Lege Cap-Ferret || Aquitaine || France || [http://www.mapimage.com Open Source GIS and Java Architect] || || Bret Hansen || Coalville || UT || USA || Java Architect and Evangelist || || Uwe Kaczmarek || Pforzheim || BWT || Germany || || || Sagolsem B. || New Delhi || Delhi || India || Distributive Computing Enthusiast ||
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-20T10:07:24
Editor: 200.80.216.146
Wiki: Apache Geronimo Wiki
Page: WikiSandBox
URL: http://wiki.apache.org/geronimo/WikiSandBox
no comment
Change Log:
--
@@ -1,39 +1 @@
-Please feel free to experiment here, after the four dashes below... and please
do '''NOT''' create new pages without any meaningful content just to try it out.
-
-'''Tip:''' Shift-click HelpOnEditing to open a second window with the help
pages.
-
-
-== Formatting ==
-
-''italic'' '''bold''' {{{typewriter}}}
-
-`backtick typewriter` (configurable)
-
-{{{
-preformatted
-}}}
-
-== Linking ==
-
-HelpOnEditing MoinMoin:InterWiki
-
-http://purl.net/wiki/moin/ [http://www.python.org/ Python]
-
[EMAIL PROTECTED]
-
-== Lists ==
-
-=== Bullet ===
- 1. numbered lists are renumbered
- * second
-
- blockquote
- deeper
-
-=== Glossary ===
- Term:: Definition
-
-Trying out attachments of photos with this Wiki:
-attachment:supertux.gif
-
-Testing commit notification teste teste teste
+Hola
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-20T10:07:54 Editor: 200.80.216.146 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -1 +1,3 @@ Hola +caca|caca|caca +caca|caca|caca
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-20T10:09:16 Editor: 200.80.216.146 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -1,3 +1,5 @@ Hola -caca|caca|caca -caca|caca|caca + +=== Table === +||caca||caca||caca|| +||caca||caca||caca||
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-20T10:15:25 Editor: 200.80.216.146 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -1,5 +1,5 @@ Hola === Table === -||caca||caca||caca|| -||caca||caca||caca|| +||diego||esteban||emanuel|| +||laura||nacho||horacio||
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-02-17T21:37:17 Editor: 66.31.145.168 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself added my profile info Change Log: -- @@ -123,5 +123,7 @@ || Vaughn Bullard || Washington DC USA || J2EE Architect/XML Schema Architect/J2EE Developer || || Greg Kerdemelidis || Christchurch || Canterbury || New Zealand || J2EE architect / developer; Director of [http://www.genixsystems.com/ Genix Systems] || || Laurent Foret || Bordeaux || Aquitaine|| France || || +|| Adam Carbone || Middleboro || Massachusetts || USA || Senior Developer || + CategoryCategory
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-02-16T23:45:51
Editor: 208.42.65.236
Wiki: Apache Geronimo Wiki
Page: BuildingAndRunning
URL: http://wiki.apache.org/geronimo/BuildingAndRunning
no comment
Change Log:
--
@@ -17,11 +17,8 @@
$ cvs -qz3 -d:pserver:[EMAIL PROTECTED]:/home/cvspublic co incubator-geronimo
$ cd incubator-geronimo
$ cvs -qz3 update -dP
-$ maven plugins
$ maven
-$ cd assembly
-$ maven
-$ java -Dgeronimo.base.dir=target -jar target/bin/server.jar
target/config-store org/apache/geronimo/System org/apache/geronimo/Server
+$ maven run:server
}}}
You should check back here occasionally as things may well change.
@@ -55,15 +52,6 @@
Running the command `maven site` seems to take up a lot of memory. If you get
an out of memory error, try setting MAVEN_OPTS=-Xmx512m.
-(Feb 02, 2004) Due to one bug fix in the xmlbeans plugin but lack of
resolution of the plugin dependencies problem you should rebuild the xmlbeans
plugin explicitly before building all of geronimo.
-
-{{{
-cd modules/maven-xmlbeans-plugin
-maven rebuild
-cd ../..
-maven
-}}}
-
= Building Offline =
If you're not online (so Maven fails to download), use the -o flag to maven
(i.e. run `maven -o`).
@@ -101,14 +89,16 @@
||org/apache/geronimo/System||Critical services for all server configurations||
||org/apache/geronimo/Server||Normal server configuration||
-To run these use the `server.jar` command:
+To run use the `server.jar` command:
{{{
-$ cd assembly/target
-$ java -Dgeronimo.base.dir=. -jar bin/server.jar config-store
org/apache/geronimo/System org/apache/geronimo/Server
+$ cd target
+$ java -jar bin/server.jar config-store org/apache/geronimo/System
org/apache/geronimo/Server
}}}
To stop the server use ctrl-C or an equivilent; a proper shutdown command will
be made available when the deployment includes the remoting framework.
+You can also start the server using maven run:server or maven
debug:server, but startup using maven disables the ctrl-C proper shutdown.
+
The deployer uses an XML deployment plan to figure out what to do. Ultimately
this will be produced by a JSR-88 tool but for now an XML aware text editor is
the best choice. The deployer uses the namespace of this file to select an
appropriate builder.
||Namespace||Schema file||Root Element||Type||
@@ -118,8 +108,8 @@
To deploy a new configuation use the `deploy.jar` command:
{{{
-$ cd assembly/target
-$ java -Dgeronimo.base.dir=. -jar bin/deploy.jar --install --plan
your-plan.xml --store config-store --deployer
org/apache/geronimo/ServiceDeployer
+$ cd target
+$ java -jar bin/deploy.jar --install --plan your-plan.xml --store
config-store --deployer org/apache/geronimo/ServiceDeployer
}}}
The need to define the store and deployer will be removed soon when the WAR
and RAR deployers have been converted. You should also only run this with the
server stopped - online deployment will be available soon when default
deployment includes the remoting layer.
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-02-15T16:45:24 Editor: 209.181.233.150 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -68,6 +68,7 @@ * WebConsole - The Web Console * SwingConsole - The Swing Console * ConsoleCommons - Common Console API + * JmxDebuggingTool - The JMX Debug Console * [wiki:OpenEJBNova OpenEJB Nova] - EJB Container
[Apache Geronimo Wiki] New: JmxDebuggingTool
Date: 2004-02-15T16:51:20 Editor: 209.181.233.150 Wiki: Apache Geronimo Wiki Page: JmxDebuggingTool URL: http://wiki.apache.org/geronimo/JmxDebuggingTool no comment New Page: = Intro = The purpose of the debugging tool is to allow developers (including the Geronimo developers) to monitor the state of the running server using JMX and to debug their applications. == Brief Architectural Overview == The Debugging Tool uses Velocity templates to output information from the JMX server. == Developers == Geir Magnusson Jr.
[Apache Geronimo Wiki] Updated: JmxDebuggingTool
Date: 2004-02-15T16:51:40 Editor: 209.181.233.150 Wiki: Apache Geronimo Wiki Page: JmxDebuggingTool URL: http://wiki.apache.org/geronimo/JmxDebuggingTool no comment Change Log: -- @@ -1,8 +1,8 @@ = Intro = The purpose of the debugging tool is to allow developers (including the Geronimo developers) to monitor the state of the running server using JMX and to debug their applications. -== Brief Architectural Overview == += Brief Architectural Overview = The Debugging Tool uses Velocity templates to output information from the JMX server. -== Developers == += Developers = Geir Magnusson Jr.
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-02-16T10:48:55 Editor: 209.181.233.150 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -68,7 +68,7 @@ * WebConsole - The Web Console * SwingConsole - The Swing Console * ConsoleCommons - Common Console API - * JmxDebuggingTool - The Raw JMX Debuging Tool + * JmxDebuggingTool - The JMX Debugging Tool * [wiki:OpenEJBNova OpenEJB Nova] - EJB Container
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-13T14:36:46 Editor: 216.219.55.12 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -1,5 +1,5 @@ Please feel free to experiment here, after the four dashes below... and please do '''NOT''' create new pages without any meaningful content just to try it out. - +Porbando wiki '''Tip:''' Shift-click HelpOnEditing to open a second window with the help pages.
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-02-12T12:43:48
Editor: 209.233.18.245
Wiki: Apache Geronimo Wiki
Page: BuildingAndRunning
URL: http://wiki.apache.org/geronimo/BuildingAndRunning
no comment
Change Log:
--
@@ -10,6 +10,23 @@
+= For the impatient ... =
+
+Assuming you have Maven 1.0-RC1 installed.
+{{{
+$ cvs -qz3 -d:pserver:[EMAIL PROTECTED]:/home/cvspublic co incubator-geronimo
+$ cd incubator-geronimo
+$ cvs -qz3 update -dP
+$ maven plugins
+$ maven
+$ cd assembly
+$ maven
+$ java -Dgeronimo.base.dir=target -jar target/bin/server.jar
target/config-store org/apache/geronimo/System org/apache/geronimo/Server
+}}}
+
+You should check back here occasionally as things may well change.
+
+
= New To Maven? =
You don't build this project with Ant (directly), you build it with Maven.
Maven manages downloading all the external dependencies for you, as well as
handling the large number of modules to build and then creating one
consolidated Geronimo build based on that.
@@ -50,8 +67,7 @@
= Building Offline =
If you're not online (so Maven fails to download), use the -o flag to maven
(i.e. run `maven -o`).
-
-`??maven -o seems to be not working ??`
+
= Bypassing Tests =
If you don't want to run test at all, try adding `-Dmaven.test.skip=true` to
your maven command line.
@@ -77,17 +93,36 @@
= Running The Server =
== For HEAD revision: ==
-(Jan 29, 2004) Deploying and running applications is now a multi step
process. There is a maven plugin to help with the needed tasks. The current
examples are in the assembly directory, and there are maven goals to run each
step. Currently only gbean packages can be reliably deployed, although we
expect this to change rapidly.
+(Feb 12, 2004) Deployment is still changing but hopefully is a little less
fraught than it has been for the last couple of weeks. There is a now a
standalone deployer (bin/deploy.jar) that is a front-end to a GBean based
deployment system. Currently there is a GBean deployer but work is going on to
move the WAR and RAR deployers over.
-1. Prepare your package. For gbean packages this should be a jar or zip file
with class jars at the root and a META-INF/geronimo-service.xml file. The
class jars need to be listed in path elements in geronimo-service.xml.
Geronimo modules can include dependency jars in the package by including
packagetrue/package in the dependency's property section. Packages are
built automatically for geronimo modules with a
src/etc/META-INF/geronimo-service.xml file.
+Configurations are pre-built for the Geronimo server.
-2. Deploy your package singly or in combination with other packages. This
converts whatever you are deploying into the gbeans that will exist on the
running Geronimo server and serializes the persistent GBean state and the
classes needed into a .car (configuration archive). There is a maven plugin
task def to help with this. An example is the assembly deploy:server goal
which deploys a geronimo server. (It should have pretty much everything we have
working in it).
+||Config ID||Purpose||
+||org/apache/geronimo/System||Critical services for all server configurations||
+||org/apache/geronimo/Server||Normal server configuration||
-3. Install your configuration archive into a servers local configuration
store. This informs the server that the configuration exists and indexes it.
There is a maven plugin task to help with this. An example is the assembly
install:server goal which installs the configuration constructed in (1).
+To run these use the `server.jar` command:
+{{{
+$ cd assembly/target
+$ java -Dgeronimo.base.dir=. -jar bin/server.jar config-store
org/apache/geronimo/System org/apache/geronimo/Server
+}}}
+
+To stop the server use ctrl-C or an equivilent; a proper shutdown command will
be made available when the deployment includes the remoting framework.
+
+The deployer uses an XML deployment plan to figure out what to do. Ultimately
this will be produced by a JSR-88 tool but for now an XML aware text editor is
the best choice. The deployer uses the namespace of this file to select an
appropriate builder.
-4. Start a server with a particular configuration. This can be done from
maven in-vm using the load or loadAndWait tasks, examples being load:server
and loadAndWait:server, or in a separate vm, examples being run:server and
debug:server.
+||Namespace||Schema file||Root Element||Type||
+||http://geronimo.apache.org/xml/ns/deployment||geronimo-config.xsd||configuration||GBean
configuration||
+
+You can find the schema files in ${geronimo.base.dir}/schema
+
+To deploy a new configuation use the `deploy.jar` command:
+{{{
+$ cd assembly/target
+$ java -Dgeronimo.base.dir=. -jar bin/deploy.jar --install --plan
your-plan.xml --store config-store --deployer
org/apache/geronimo/ServiceDeployer
+}}}
-There is also a do it all deployinstallrun
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-02-10T16:10:36 Editor: 206.169.32.2 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -3,7 +3,7 @@ '''Contents''' [[TableOfContents]] -= '''About''' = += About = The [http://www.apache.org Apache Software Foundation] has initiated a project to develop an open source, [http://www.apache.org/foundation/licence-FAQ.html Apache-licensed] implementation of the [http://java.sun.com/j2ee J2EE] specification. In addition, the project is committed to certifying the implementation as [http://java.sun.com/j2ee/verified J2EE compliant]. This is an ambitious goal and will present a formidable challenge for the people involved, given the wide range of technologies covered by the specification.
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-02-10T06:16:33 Editor: RalfBarkow [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: BuildingAndRunning URL: http://wiki.apache.org/geronimo/BuildingAndRunning no comment Change Log: -- @@ -96,4 +96,8 @@ = Accessing The Geronimo-Web-Console = -Enter http://localhost:8080/geronimo-web-console to access the JMX Agent View. +Enter http://localhost:8080/geronimo-web-console to access the JMX Agent View. + + += Cleaning your workspace = +To clean your workspace, type `maven clean`. NOTE: You need to build the server first for this to work due to a problem with dependencies the reactor. This means that the clean command (or goal) must not be called until Geronimo has already been built.
[Apache Geronimo Wiki] Updated: WikiSandBox
Date: 2004-02-07T23:04:24 Editor: 211.76.97.248 Wiki: Apache Geronimo Wiki Page: WikiSandBox URL: http://wiki.apache.org/geronimo/WikiSandBox no comment Change Log: -- @@ -24,8 +24,6 @@ == Lists == === Bullet === - * first - 1. nested and numbered 1. numbered lists are renumbered * second
[Apache Geronimo Wiki] New: CMPDeploymentHelpers
Date: 2004-02-06T12:21:10 Editor: BrendanMcAdams [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: CMPDeploymentHelpers URL: http://wiki.apache.org/geronimo/CMPDeploymentHelpers no comment New Page: == CMP Deployment Helper Classes == Two primary classes exist to assist with the deployment and configuration of CMP Entity Beans - SQLGenerator, and CMPBindingGenerator. Both of these classes simplify CMP deployment by providing the ability to generate the necessary Query code (SQL and the JDBC Binding objects necessary to execute queries and read the results). Demonstrations of these objects in action exists in the test class org.openejb.nova.entity.SQLGeneratorCMPEntityContainerTest.
[Apache Geronimo Wiki] Updated: J2EESpecs
Date: 2004-02-03T10:26:40 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: J2EESpecs URL: http://wiki.apache.org/geronimo/J2EESpecs no comment Change Log: -- @@ -33,12 +33,13 @@ * Servlet 2.4 - [http://java.sun.com/products/servlet Details] [[JSRLink(154)]] * JSP 2.0 - [http://java.sun.com/products/jsp Details] [[JSRLink(152)]] * JAXP 1.2 - [http://java.sun.com/xml Details] - * Web Services 1.0 - [[JSRLink(109)]] - * JMX 1.1 - [http://java.sun.com/products/JavaManagement Details] + * Web Services 1.1 - [[JSRLink(109)]] + * JMX 1.2 - [http://java.sun.com/products/JavaManagement Details] * Connector 1.5 - [http://java.sun.com/j2ee/connector Details] [[JSRLink(112)]] * XML Registries (JAXR) 1.0 - [http://java.sun.com/xml/jaxr Details] - * !JavaMail 1.2 - [http://java.sun.com/products/javamail Details] - * JAX-RPC 1.0 - [http://java.sun.com/xml/jaxrpc Details] + * !JavaMail 1.3 - [http://java.sun.com/products/javamail Details] + * JAX-RPC 1.1 - [http://java.sun.com/xml/jaxrpc Details] + * SAAJ 1.2 - [http://java.sun.com/xml/saaj Details] * !JavaBean Activation Framework (JAF) 1.0 - [http://java.sun.com/beans/glasgow/jaf.html Details] == Section 7 - Interoperability == @@ -53,7 +54,7 @@ == Section 8 - Application Assembly and Deployment == - * Java #153; 2 Platform, Enterprise Edition Deployment Specification 1.0 (J2EE Deployment specification) - [[JSRLink(88)]] + * Java #153; 2 Platform, Enterprise Edition Deployment Specification 1.1 (J2EE Deployment specification) - [[JSRLink(88)]] * Optional Package Versioning - [http://java.sun.com/j2se/1.4/docs/guide/extensions Details] * JAR File Specification - [http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html Details] * J2EE Management 1.0 - [http://java.sun.com/j2ee/tools/management Details] [[JSRLink(77)]]
[Apache Geronimo Wiki] Updated: J2EESpecs
Date: 2004-02-03T10:40:24 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: J2EESpecs URL: http://wiki.apache.org/geronimo/J2EESpecs no comment Change Log: -- @@ -54,7 +54,7 @@ == Section 8 - Application Assembly and Deployment == - * Java #153; 2 Platform, Enterprise Edition Deployment Specification 1.1 (J2EE Deployment specification) - [java.sun.com/j2ee/tools/deployment Details][[JSRLink(88)]] + * Java #153; 2 Platform, Enterprise Edition Deployment Specification 1.1 (J2EE Deployment specification) - [http://java.sun.com/j2ee/tools/deployment Details][[JSRLink(88)]] * Optional Package Versioning - [http://java.sun.com/j2se/1.4/docs/guide/extensions Details] * JAR File Specification - [http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html Details] * J2EE Management 1.0 - [http://java.sun.com/j2ee/tools/management Details] [[JSRLink(77)]]
[Apache Geronimo Wiki] Updated: WishList
Date: 2004-02-02T09:58:51 Editor: 194.3.209.241 Wiki: Apache Geronimo Wiki Page: WishList URL: http://wiki.apache.org/geronimo/WishList Added comment about concurency utilities in J2SE1.5 ! Change Log: -- @@ -109,5 +109,7 @@ http://sourceforge.net/projects/seda/ Comments: SEDA can probably be installed more or less as is in geronimo by wrapping it as one or more GBeans. However, it (as of a few months ago) had no support for propagating transaction or security contexts, so will be more or less impossible to integrate with any other service. The SEDA model of message passing is also more or less totally inoperable with the ejb model of intercepted method calls. I don't see any particular reason the SEDA model could not be extended to include the necessary contexts for j2ee-level functionality, but this is definitely on the order of a research project. +Warning: According to http://www.jcp.org/en/jsr/detail?id=166 concurency utilities might be part of J2SE1.5 ! + = Incorporation of JDO (Java Data Objects) = The inclusion of a JDO implementation would add tremendous value to the Geronimo Application Server.
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-02-01T07:24:20 Editor: 203.94.92.84 Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -22,7 +22,9 @@ we are trying to take a more geranimo based approch. The key Idea is to use geranimo internals to acsess the service implemenation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html (the proposal will bring to wiki and will make editable ASAP.) +== Security mapping == +[http://wiki.apache.org/geronimo/EnterpriseWebServices_security;]
[Apache Geronimo Wiki] New: http:/http:/wiki.apache.org/geronimo/EnterpriseWebServices_security
Date: 2004-02-01T07:26:39 Editor: 203.94.92.84 Wiki: Apache Geronimo Wiki Page: http:/http:/wiki.apache.org/geronimo/EnterpriseWebServices_security URL: http://wiki.apache.org/geronimo/http:/http:/wiki.apache.org/geronimo/EnterpriseWebServices_security no comment New Page: = Describe http:/http:/wiki.apache.org/geronimo/EnterpriseWebServices_security here. = The purposed securtiy mapping will go here
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-02-01T07:28:22 Editor: 203.94.92.84 Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -24,7 +24,11 @@ == Security mapping == -[http://wiki.apache.org/geronimo/EnterpriseWebServices_security;] +[security-mapping] + += Transaction mapping= + +[transaction-mapping]
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-02-01T07:31:02 Editor: 203.94.92.84 Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -24,11 +24,11 @@ == Security mapping == -[security-mapping] +[EnterpriseWebServices/security-mapping] == Transaction mapping == -[transaction-mapping] +[EnterpriseWebServices/transaction-mapping]
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-02-01T07:22:31 Editor: 203.94.92.84 Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -1,28 +1,27 @@ = Implementation Details of code currently in http://sf.net/projects/ews/ = - The original proposal based for the work so far is at http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal + This page explains the work done so far for the implementation of the (Enterprise WebServices) JSR109 specification. Please not that there is a praposal we forward initially for the project and in EWS project at the sf.net(http://sf.net/projects/ews/. +) we have a working phototype of the implementation based on the initail propoal at http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal -The proposed architecture consists of a tool that generate the Web Service, EJB's (WS endpoint) and the -runtime code to link the Web Service and the EJB. +But unfortunatly the initial proposal Based on calling the EJB through the remote interface (for more information please read the URL above) seem to have design issues so we are working on a revised proposal right now. -1) Our initial design is to use the Remote interface of the EJB to the access the EJB -(simply put - convert the SOAP request to RMI/IIOP request and the result -is sent back as SOAP by Web Service glue code) We also thought of making the J2EE container and implementation independent of each other. +== Architecure == +the proposed architecture is a tool that generate the webserive , ejb (ws endpoint) and the code to bind the webserive and the ejb together. -2) But due to - a) performance consideration (SOAP-RMI/IIOP-Java) - b) As further explained by the EJB2.1 spec the webservice ejb endpoint -i) be a Stateless session bean +== Initial Design == + our initial design is to use the Remote interface of the EJB to the accsess the ejb (simpley put the SOAP requst convert to RMI/IIOP request by the webservice and the result is send back as SOAP by webservice.) We thought of making the J2EE container and implementation independent of each other with that design. -ii) the remote interface(the interface published) is JAX-RPC SEI which extends -javax.rmi.Remote not a usual Remote interface that extends javax.ejb.EJBObject. +== The problems encountered with the Initial design == + * performance consideration (SOAP-RMI/IIOP-Java) -iii) the home interface seem to not needed as client not creating the Web Service - -iv) concerns about mapping of j2ee and Web Service transaction contexts when we use remote -interface + * As futher explained by the ejb2.1 spec the webservice ejb endpoint should be a be a Staless session bean. The the remote interface(the interface published) is jaxrpc SEI which extends javax.rmi.Remote but not a ususal Remote interface extends javax.ejb.EJBObject. the home interface seem to not needed as client not creating the webservice. We are not supporting these conditions. + + * concerns about mapping of j2ee and ws transaction contexts when we use remote interface + +== Revised Approch == + +we are trying to take a more geranimo based approch. The key Idea is to use geranimo internals to acsess the service implemenation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html (the proposal will bring to wiki and will make editable ASAP.) -we are trying to take a more geronimo based approach. The key idea is to use geronimo internals to access the service implementation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html. (the proposal will bring to wiki and will make edit-able ASAP.) We have implemented most of parts in previous proposal and the code is at http://sf.net/projects/ews/.
[Apache Geronimo Wiki] New: EnterpriseWebServices
Date: 2004-01-30T04:20:38 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment New Page: = Implementation Details of code currently in http://sf.net/projects/ews/ = = Implementation Details of code currently in http://sf.net/projects/ews/ =
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-01-30T05:19:48 Editor: 220.247.246.55 Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -1,2 +1,36 @@ = Implementation Details of code currently in http://sf.net/projects/ews/ = + + the propsel based for the work so far is in +http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal + +the proposed architecture is a tool that generate the webserive , ejb (ws endpoint) and the +code to bind the webserive and the ejb together. +1) our initial design is to use the Remote interface of the EJB to the accsess the ejb +(simpley put the SOAP requst convert to RMI/IIOP request by the webservice and the result +is send back as SOAP by webservice.) We thought of making the J2EE container and implementation independent of each other with that. + +2)but due to + a) performance consideration (SOAP-RMI/IIOP-Java) + b) As futher explained by the ejb2.1 spec the webservice ejb endpoint +i) be a Staless session bean + +ii) the remote interface(the interface published) is jaxrpc SEI which extends +javax.rmi.Remote not a ususal Remote interface extends javax.ejb.EJBObject. + +iii) the home interface seem to not needed as client not creating the webservice +iv) concerns about mapping of j2ee and ws transaction contexts when we use remote +interface + +we are trying to take a more geranimo based approch. + +The key Idea is to use geranimo internals to acsess the service implemenation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html + +(the proposal will bring to wiki and will make editable ASAP.) + +We have implemented most of parts in privous proposal which is at ews right now. + + + + +
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-01-30T08:30:50 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -1,15 +1,15 @@ = Implementation Details of code currently in http://sf.net/projects/ews/ = - the propsel based for the work so far is in -http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal + The original proposal based for the work so far is at http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal -the proposed architecture is a tool that generate the webserive , ejb (ws endpoint) and the -code to bind the webserive and the ejb together. -1) our initial design is to use the Remote interface of the EJB to the accsess the ejb -(simpley put the SOAP requst convert to RMI/IIOP request by the webservice and the result -is send back as SOAP by webservice.) We thought of making the J2EE container and implementation independent of each other with that. +The proposed architecture consists of a tool that generate the Web Service, EJB's (WS endpoint) and the +runtime code to link the Web Service and the EJB. -2)but due to +1) Our initial design is to use the Remote interface of the EJB to the accsess the ejb +(simply put - convert the SOAP request of the webservice to RMI/IIOP request and the result +is send back as SOAP by webservice.) We also thought of making the J2EE container and implementation independent of each other. + +2) But due to a) performance consideration (SOAP-RMI/IIOP-Java) b) As futher explained by the ejb2.1 spec the webservice ejb endpoint i) be a Staless session bean @@ -18,16 +18,11 @@ javax.rmi.Remote not a ususal Remote interface extends javax.ejb.EJBObject. iii) the home interface seem to not needed as client not creating the webservice + iv) concerns about mapping of j2ee and ws transaction contexts when we use remote interface -we are trying to take a more geranimo based approch. - -The key Idea is to use geranimo internals to acsess the service implemenation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html - -(the proposal will bring to wiki and will make editable ASAP.) - -We have implemented most of parts in privous proposal which is at ews right now. +we are trying to take a more geronimo based approach. The key idea is to use geranimo internals to acsess the service implementation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html. (the proposal will bring to wiki and will make editable ASAP.) We have implemented most of parts in previous proposal and the code is at http://sf.net/projects/ews/.
[Apache Geronimo Wiki] Updated: EnterpriseWebServices
Date: 2004-01-30T08:33:44 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: EnterpriseWebServices URL: http://wiki.apache.org/geronimo/EnterpriseWebServices no comment Change Log: -- @@ -5,24 +5,24 @@ The proposed architecture consists of a tool that generate the Web Service, EJB's (WS endpoint) and the runtime code to link the Web Service and the EJB. -1) Our initial design is to use the Remote interface of the EJB to the accsess the ejb -(simply put - convert the SOAP request of the webservice to RMI/IIOP request and the result -is send back as SOAP by webservice.) We also thought of making the J2EE container and implementation independent of each other. +1) Our initial design is to use the Remote interface of the EJB to the access the EJB +(simply put - convert the SOAP request to RMI/IIOP request and the result +is sent back as SOAP by Web Service glue code) We also thought of making the J2EE container and implementation independent of each other. 2) But due to a) performance consideration (SOAP-RMI/IIOP-Java) - b) As futher explained by the ejb2.1 spec the webservice ejb endpoint -i) be a Staless session bean + b) As further explained by the EJB2.1 spec the webservice ejb endpoint +i) be a Stateless session bean -ii) the remote interface(the interface published) is jaxrpc SEI which extends -javax.rmi.Remote not a ususal Remote interface extends javax.ejb.EJBObject. +ii) the remote interface(the interface published) is JAX-RPC SEI which extends +javax.rmi.Remote not a usual Remote interface that extends javax.ejb.EJBObject. -iii) the home interface seem to not needed as client not creating the webservice +iii) the home interface seem to not needed as client not creating the Web Service -iv) concerns about mapping of j2ee and ws transaction contexts when we use remote +iv) concerns about mapping of j2ee and Web Service transaction contexts when we use remote interface -we are trying to take a more geronimo based approach. The key idea is to use geranimo internals to acsess the service implementation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html. (the proposal will bring to wiki and will make editable ASAP.) We have implemented most of parts in previous proposal and the code is at http://sf.net/projects/ews/. +we are trying to take a more geronimo based approach. The key idea is to use geronimo internals to access the service implementation bean and invoke the call on it directly. We would prefer to avoid the SOAP - RMI conversion. the information about proposal is at http://ws.apache.org/~hemapani/jsr109/docs/revisedProposal.html. (the proposal will bring to wiki and will make edit-able ASAP.) We have implemented most of parts in previous proposal and the code is at http://sf.net/projects/ews/.
[Apache Geronimo Wiki] Updated: BuildingAndRunning
Date: 2004-01-29T08:32:34 Editor: 66.93.38.137 Wiki: Apache Geronimo Wiki Page: BuildingAndRunning URL: http://wiki.apache.org/geronimo/BuildingAndRunning no comment Change Log: -- @@ -28,6 +28,8 @@ = General Advice = +On Jan 21, 2004, we tagged the fairly stable current version and commenced rewriting the deployment structure. Until this process is complete, you may wish to experiment with the tagged version by checking out the last_geronimombean branch. You may wish to check on the IRC channel and mailing list to see how far the rewrite has proceeded. + If having problems building Geronimo, make sure it isn't simply because your Maven repository has become 'corrupted' or out of sync: Delete (or temporarily rename) the .maven directory in your home directory and try building Geronimo again. @@ -65,6 +67,20 @@ = Running The Server = +== For HEAD revision: == +(Jan 29, 2004) Deploying and running applications is now a multi step process. There is a maven plugin to help with the needed tasks. The current examples are in the assembly directory, and there are maven goals to run each step. Currently only gbean packages can be reliably deployed, although we expect this to change rapidly. + +1. Prepare your package. For gbean packages this should be a jar or zip file with class jars at the root and a META-INF/geronimo-service.xml file. The class jars need to be listed in path elements in geronimo-service.xml. Geronimo modules can include dependency jars in the package by including packagetrue/package in the dependency's property section. Packages are built automatically for geronimo modules with a src/etc/META-INF/geronimo-service.xml file. + +2. Deploy your package singly or in combination with other packages. This converts whatever you are deploying into the gbeans that will exist on the running Geronimo server and serializes the persistent GBean state and the classes needed into a .car (configuration archive). There is a maven plugin task def to help with this. An example is the assembly deploy:server goal which deploys a geronimo server. (It should have pretty much everything we have working in it). + +3. Install your configuration archive into a servers local configuration store. This informs the server that the configuration exists and indexes it. There is a maven plugin task to help with this. An example is the assembly install:server goal which installs the configuration constructed in (1). + +4. Start a server with a particular configuration. This can be done from maven in-vm using the load or loadAndWait tasks, examples being load:server and loadAndWait:server, or in a separate vm, examples being run:server and debug:server. + +There is also a do it all deployinstallrun goal. + +== For the legacy last_geronimombean tagged copy: == Once you've downloaded the source code, installed Maven and built the server, type `maven run:main` to run the server. As of December, 2003, there is no way to stop the server other than killing it, control-C or other such means.
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T17:05:08 Editor: GregWilkins [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -14,9 +14,12 @@ A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. -An optional WEB-INF/geronimo-web.xml deployment will be required to configure any additional jndi resources and resource-refs. The context path will be set by the EAR application.xml, the WAR filename, the directory filename or by a geronimo configuration element. +Any geronimo specific configuration will be done via the JSR88 deployment plan associated with +the deployment. The deployment plan will include any mappings required to JNDI resources +or specific web container configurations. -Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. +Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. Instead, implementation specific configuration should either be done via an extensible deployment plan or avoided by integration +into common geronimo services. == Connector Configuration ==
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T17:14:03 Editor: GregWilkins [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -14,9 +14,8 @@ A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. -Any geronimo specific configuration will be done via the JSR88 deployment plan associated with -the deployment. The deployment plan will include any mappings required to JNDI resources -or specific web container configurations. +Any geronimo specific configuration will be done via a JSR88 deployment plan associated with +the deployed webapplication or EAR. The deployment plan will include any mappings required to JNDI resources or references to specific web container configurations. Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. Instead, implementation specific configuration should either be done via an extensible deployment plan or avoided by integration into common geronimo services. @@ -41,8 +40,7 @@ host and/or domain names. Virtual hosts may be configured for logging, security, statistics, etc. A webapp may be targetted to a specific virtual host at deployment time. If a targeted virtual -host does not exist, this may result in either a validation error or the creation of a -dynamic virtual host with default configuration. +host has not been configured and started on the server, this will result in a error when the webapp is started. == Physical hosts == @@ -141,8 +139,12 @@ == Configuration == -Web applications will use a geronimo-web.xml file for their geronimo specific configuration. They -may also have impl-web.xml for implementation dependent configuration, but this is to be discouraged -in all but exceptional cases. +Web applications should be deployed with only the standard deployment descriptors in their +WEB-INF directories. Geronimo will use the associated JSR88 deployment plan to +provide geronimo and extensible implementation configuration. + +The use of impl-web.xml for implementation dependent configuration may be supported but this +is to be discouraged in all but exceptional cases. + The other web components will be configured via the GBean mechanism which may use *-service.xml files.
[Apache Geronimo Wiki] Updated: Architecture/Management
Date: 2004-01-28T02:20:47 Editor: 193.172.11.178 Wiki: Apache Geronimo Wiki Page: Architecture/Management URL: http://wiki.apache.org/geronimo/Architecture/Management Just changed the Sun's JMX mailing list's name Change Log: -- @@ -49,4 +49,4 @@ One of the best places to learn the basics of JMX is Juha Lindfors' book _Managing J2EE with Java Managment Extensions_. The JMX specification is also the best, most definitive reference of what JMX is, but OReilly's got a good book out which covers it in more depth (and is more recent than Juha's book). Juha's is still a great reference, though. -You might also consider joining Sun's JMX-Discuss list and the [http://sourceforge.net/mail/?group_id=47745 MX4J] lists. +You might also consider joining Sun's JMX-Forum list and the [http://sourceforge.net/mail/?group_id=47745 MX4J] lists.
[Apache Geronimo Wiki] Updated: LocalSpellingWords
Date: 2004-01-27T13:28:08 Editor: 203.45.72.167 Wiki: Apache Geronimo Wiki Page: LocalSpellingWords URL: http://wiki.apache.org/geronimo/LocalSpellingWords no comment Change Log: -- @@ -11,3 +11,5 @@ apachecon codehaus Codehaus com Cvs cvs dev diff etc exolab eyebrowse irc j2ee Jira licence Maven mx4j nagoya Nov openejb org sourceforge vandal wikisandbox + +https Jetty log Servlet servlet Tomcat Webapp webapp
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T13:35:53 Editor: 203.45.72.167 Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -2,58 +2,123 @@ [[TableOfContents]] = Overview = +The implementation of the Geronimo web tier will be guided by the use cases outlined below. It is +the intent of this project to meet these use-cases without resorting to implementation specific +configuration. -The notes on this page have been put together by [EMAIL PROTECTED], based on a posting to geronimo-dev, with a few notes added. += Use Cases = +== Webapp Deployment == +A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. -I would like to see the container, the connectors and webapplications as all top level geronimo components (aka services). +All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. -[ NB. It looks like the initial geronimo code supports nested services - so perhaps the top level description is not valid and webcontainer component can be the container for the webconnectors and webapplications ] +An optional WEB-INF/geronimo-web.xml deployment will be required to configure any additional jndi resources and resource-refs. -They would all have independant lifecycles - create, start, stop, destroy that can be controlled by the normal container mechanisms - with the exception that both connectors and webapps depend on having a container deployed. +The context path will be set by the EAR application.xml, the WAR filename, the directory filename or by a geronimo configuration element. -I would like to support multiple containers, so you can have isolated collections of connectors and webapps (eg for security and/or admin) +Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. -The deployment would go something like as follows: +== Connector Configuration == +The default and/or additional HTTP connectors for the default geronimo web container will be configured +and managed via standard geronimo mechanisms. The majority of common parameters, statistics and JSR77 lifecycle +commands for HTTP connectors will be able to be managed without using implementation specific configuration or +tools. This will include: -== A web container is deployed == + * Protocol: http, https, ajp, etc. + * Ports: listening and security redirections) + * Interface: Optional host and/or IP interfaces to bind to. + * Threads: Min, Max, aging, etc. + * Timeouts: Persist and Idle times. -This should have no dependancies, but will lazily discover JNDI services etc as needed. The container configuration would include such things as a default web.xml to load for all webapps. -== A web connector is deployed == +== Virtual hosts == +Virtual hosts must be able to be defined within geronimo web containers, defined by one or more +host and/or domain names. Virtual hosts may be configured for logging, security, statistics, etc. -This will depend on a webcontainer being deployed. The exact way one of multiple containers is selected is yet to be determined - but there will be a default method, plus an option to be specific in the configuration. The configuration of the web connector will contain many common parameters: +A webapp may be targetted to a specific virtual host at deployment time. If a targeted virtual +host does not exist, this may result in either a validation error or the creation of a +dynamic virtual host with default configuration. - protocol name:: http, https, ajp, etc. - port:: to listen on - interface:: optional interface to listen on - max connection:: ??? - max idle persistance time:: ??? - required contexts:: names of contexts that must be registered and started with container before the connector accepts any connections -But it will also need to allow configuration for connector specific parameters. I assume this can be done by a getInitParameter style map - but maybe something more typed or verifiable can be used - I'll wait and see how the service configuraton mechanism develops. +== Physical hosts == +The deployment of a web app may be targetted deploy against a specific subset of web connectors, +so that it will be available only on specific physical interfaces, ports, protocols etc. +Typically this will be to allow additional network security to be applied to administration +and/or web services interfaces. -I don't expect the webconnector service to actually implement the connector - as JMX is not really the right sort of bus to push HTTP
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T13:38:58 Editor: 203.45.72.167 Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -2,12 +2,15 @@ [[TableOfContents]] = Overview = + The implementation of the Geronimo web tier will be guided by the use cases outlined below. It is the intent of this project to meet these use-cases without resorting to implementation specific configuration. = Use Cases = + == Webapp Deployment == + A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. @@ -19,6 +22,7 @@ Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. == Connector Configuration == + The default and/or additional HTTP connectors for the default geronimo web container will be configured and managed via standard geronimo mechanisms. The majority of common parameters, statistics and JSR77 lifecycle commands for HTTP connectors will be able to be managed without using implementation specific configuration or @@ -32,6 +36,7 @@ == Virtual hosts == + Virtual hosts must be able to be defined within geronimo web containers, defined by one or more host and/or domain names. Virtual hosts may be configured for logging, security, statistics, etc. @@ -41,6 +46,7 @@ == Physical hosts == + The deployment of a web app may be targetted deploy against a specific subset of web connectors, so that it will be available only on specific physical interfaces, ports, protocols etc. Typically this will be to allow additional network security to be applied to administration @@ -48,13 +54,16 @@ == Web Component Dependencies == + It will be possible to define dependencies between web components and web applications: + * A web connector may be dependent one or more web applications. Thus until all the webapps are started, a dependent web connector will not be started. If the web application is stopped, then the dependent web connector will also be stopped and the node will be unavailable. This will allow a geronimo node to enter/leave a web cluster based on application availability rather than connector availability. * A webapp may be dependent on another webapp, so that a webapp that uses the resources of another will only be started if the webapp on which it depends is started. == Web Services == + Other geronimo components may define a web service interfaces. In order to deploy these components, some web infrastructure (connectors, SOAP servlet) may need to be initialized, perhaps dynamically. Ideally this will not be within the default web container, as this is unlikely to have desirable @@ -67,8 +76,10 @@ == Components == + The geronimo web tier will be composed of JSR77 components that may be aggregated into various configurations. These subservices will include: + * Web applications: Directories, WARs, WARs within EARs, dynamically created * Web connectors: HTTP, HTTPS, AJP, etc. * Web request logs: NCSA format, file, DB, etc. @@ -76,6 +87,7 @@ * Realms: JACC, Single sign on. * Web container: A collection of other web components. * Virtual host: A partitioning of a web container + These components may be implemented as components only for the purposes of Geronimo configuration and management. The actual implementation may actually be decomposed differently (or not at all), but such details will be hidden from the average @@ -83,6 +95,7 @@ == Web Container == + A web container is the deployment target of a webapplication. All webapplications that are deployed in the same web container will share the following services and configuration: @@ -92,17 +105,16 @@ * realm * session manager * collection of virtual hosts -A Geronimo server may have multiple web containers deployed. A single web container may -be configured as the default web container for the server. -All web components may optionally name (by ObjectName) the web container they are for. If +A Geronimo server may have multiple web containers deployed. A single web container may +be configured as the default web container for the server. All web components may optionally name (by ObjectName) the web container they are for. If a web component does not name a web container, then it is for the default container. - Only ServletContexts deployed within the same web container are visible to the ServletContext.getContext() API. == Virtual Host == + A web container may be
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T13:40:44 Editor: 203.45.72.167 Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -11,13 +11,9 @@ == Webapp Deployment == -A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. +A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. -All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. - -An optional WEB-INF/geronimo-web.xml deployment will be required to configure any additional jndi resources and resource-refs. - -The context path will be set by the EAR application.xml, the WAR filename, the directory filename or by a geronimo configuration element. +An optional WEB-INF/geronimo-web.xml deployment will be required to configure any additional jndi resources and resource-refs. The context path will be set by the EAR application.xml, the WAR filename, the directory filename or by a geronimo configuration element. Optional WEB-INF/impl-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases.
[Apache Geronimo Wiki] Updated: Architecture/WebContainer
Date: 2004-01-27T14:04:43 Editor: 203.45.72.167 Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer no comment Change Log: -- @@ -5,7 +5,8 @@ The implementation of the Geronimo web tier will be guided by the use cases outlined below. It is the intent of this project to meet these use-cases without resorting to implementation specific -configuration. +configuration. Specifically, these are actions that typical geronimo users are likely to perform and should be able to be documented, supported and managed as geronimo actions, rather than anything +specific to the underlying implementation of the web container. = Use Cases = @@ -46,7 +47,11 @@ The deployment of a web app may be targetted deploy against a specific subset of web connectors, so that it will be available only on specific physical interfaces, ports, protocols etc. Typically this will be to allow additional network security to be applied to administration -and/or web services interfaces. +and/or web services interfaces. + +For good default security, the default geronimo configuration should start administrative +interfaces such as the jmx console are only available on localhost and on a port that is +distinct from the default web application deployment. == Web Component Dependencies == @@ -64,6 +69,13 @@ some web infrastructure (connectors, SOAP servlet) may need to be initialized, perhaps dynamically. Ideally this will not be within the default web container, as this is unlikely to have desirable default security implications. + +== Run states == + +Management of a cluster may need additional run states than those defined in JSR77. Gentle shutdown of +nodes may required modes where no new requests/connections/sessions are accepted by a node, while +existing requests/connections/sessions are allowed to complete. These modes may need to be applied +to web connectors and/or webapplications. = Architecture =
[Apache Geronimo Wiki] Updated: J2EESpecs
Date: 2004-01-24T16:54:30 Editor: 145.254.248.70 Wiki: Apache Geronimo Wiki Page: J2EESpecs URL: http://wiki.apache.org/geronimo/J2EESpecs no comment Change Log: -- @@ -11,6 +11,8 @@ The following items are organized by the topics they belong to in [http://java.sun.com/j2ee/j2ee-1_4-pfd3-spec.pdf J2EE Specification 1.4 Public Draft 3]. In case an item appears in more than one section, it is placed under the first occurrence to avoid duplication of entries. +Question: As JSR-000151 J2EE(TM) 1.4 Platform Specification FR is out, is the FR the required Specification for Certification? + == Section 3 - Security == * Java #153; Authorization Service Provider Contract for Containers 1.0 (JACC) - [[JSRLink(115)]]
[Apache Geronimo Wiki] Updated: J2EESpecs
Date: 2004-01-24T17:09:29 Editor: RalfBarkow [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: J2EESpecs URL: http://wiki.apache.org/geronimo/J2EESpecs no comment Change Log: -- @@ -11,7 +11,7 @@ The following items are organized by the topics they belong to in [http://java.sun.com/j2ee/j2ee-1_4-pfd3-spec.pdf J2EE Specification 1.4 Public Draft 3]. In case an item appears in more than one section, it is placed under the first occurrence to avoid duplication of entries. -Question: As JSR-000151 J2EE(TM) 1.4 Platform Specification FR is out, is the FR the required Specification for Certification? +Question: As JSR-000151 J2EE(TM) 1.4 Platform Specification FR is out, is the FR required for Certification? == Section 3 - Security ==
[Apache Geronimo Wiki] Updated: J2EESpecs
Date: 2004-01-24T23:25:19 Editor: RalfBarkow [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: J2EESpecs URL: http://wiki.apache.org/geronimo/J2EESpecs no comment Change Log: -- @@ -9,9 +9,7 @@ = Required J2EE 1.4 Specifications for Certification = -The following items are organized by the topics they belong to in [http://java.sun.com/j2ee/j2ee-1_4-pfd3-spec.pdf J2EE Specification 1.4 Public Draft 3]. In case an item appears in more than one section, it is placed under the first occurrence to avoid duplication of entries. - -Question: As JSR-000151 [http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf J2EE(TM) 1.4 Platform Specification Final Release] is out, is the FR required for Certification? +The following items are organized by the topics they belong to in [http://java.sun.com/j2ee/j2ee-1_4-pfd3-spec.pdf J2EE Specification 1.4 Public Draft 3] and the [http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf Final Release] - [[JSRLink(151)]]. In case an item appears in more than one section, it is placed under the first occurrence to avoid duplication of entries. == Section 3 - Security ==
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-22T04:24:09 Editor: 217.227.26.159 Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore typing Change Log: -- @@ -108,4 +108,4 @@ i. Add '''datasource-namepetstoredb/datasource-name''' after ejb-jar tag (although it's only required for ejb jars with CMPs) - 1. Enter http://localhost:8080/petstore and have fun. That's just a begining. + 1. Enter http://localhost:8080/petstore and have fun. That's just a beginning.
[Apache Geronimo Wiki] Updated: TODO
Date: 2004-01-20T01:39:58 Editor: 130.225.24.131 Wiki: Apache Geronimo Wiki Page: TODO URL: http://wiki.apache.org/geronimo/TODO no comment Change Log: -- @@ -46,7 +46,7 @@ Various projects need to be integrated. Here's a sample list (in no particular order): * Tomcat / Jetty - * Axis + * Axis Web Services * OpenJMS * Tyrex * James
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T05:15:57 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore no comment Change Log: -- @@ -12,7 +12,7 @@ * Install [wiki:OpenEJBNova OpenEJB Nova Service] - * Install J2EECA JDBC implementation (see [http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277 JCA Impl for OpenEJB] or ask for openejb-jca-DEV.jar on geronimo-dev mailing list) + * Install [J2EECA JDBC implementation] (see [http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277 JCA Impl for OpenEJB] or ask for openejb-jca-DEV.jar on geronimo-dev mailing list) * Download [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2]
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T05:16:40 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore no comment Change Log: -- @@ -12,7 +12,7 @@ * Install [wiki:OpenEJBNova OpenEJB Nova Service] - * Install [J2EECA JDBC implementation] (see [http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277 JCA Impl for OpenEJB] or ask for openejb-jca-DEV.jar on geronimo-dev mailing list) + * Install [wiki:J2EECA JDBC implementation] (see [http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277 JCA Impl for OpenEJB] or ask for openejb-jca-DEV.jar on geronimo-dev mailing list) * Download [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2]
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T05:32:21 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore no comment Change Log: -- @@ -12,7 +12,7 @@ * Install [wiki:OpenEJBNova OpenEJB Nova Service] - * Install [wiki:OpenJCA J2EECA JDBC implementation] (see [http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277 JCA Impl for OpenEJB] or ask for openejb-jca-DEV.jar on geronimo-dev mailing list) + * Install [wiki:OpenJCA OpenJCA - A JCA JDBC implementation] * Download [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2]
[Apache Geronimo Wiki] Updated: OpenJCA
Date: 2004-01-20T05:46:38
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: OpenJCA
URL: http://wiki.apache.org/geronimo/OpenJCA
no comment
Change Log:
--
@@ -1,9 +1,9 @@
= About =
-OpenJCA is a JCA JDBC Implementation. You can get openjca.tar.gz from
[http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277
JCA Impl for OpenEJB]
+OpenJCA is a JCA JDBC Implementation.
= Building =
-* Get the sources of OpenJCA from
[http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277
JCA Impl for OpenEJB]
+* Get the source code of OpenJCA (openjca.tar.gz) from
[http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277
JCA Impl for OpenEJB]
* run {{{gzip -d openjca.tar.gz}}} followed by {{{tar -xvf openjca.tar}}} to
extract the sources
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T05:58:49
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: PetStore
URL: http://wiki.apache.org/geronimo/PetStore
no comment
Change Log:
--
@@ -20,41 +20,40 @@
Before going on, please keep in mind that {{{whom ever wrote petstore should
be hunted down...}}}. It's been said during one IRC session and I couldn't
resist to include it.
-NOTE: The directory names are all relative to '''target/geronimo-DEV'''
directory.
+NOTE: Unless otherwise specified the directory names are all relative to
'''incubator-geronimo/target/geronimo-DEV''' directory.
- 1. Define '''petstore''' directory as a place where deployables are to be
found. Open '''etc/boot-service.xml''' and add '''${geronimo.home}/petstore'''
after the comma, next to'''${geronimo.home}/deploy''' in
'''org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner''' MBean.
+ 1. Create '''petstore''' directory as a place where deployables are to be
found. Open '''etc/boot-service.xml''' and add '''${geronimo.home}/petstore'''
after the comma, next to'''${geronimo.home}/deploy''' in
'''org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner''' MBean.
Once this is done, Geronimo will monitor the directory and attempt to deploy
resources that are in the directory.
- Once it's done Geronimo will monitor the directory and attempt to deploy
resources that are in.
+ 1. Define a connection-definition of your choice in J2EECA JDBC
implementation's specific way. (For OpenJCA, you can edit
''META-INF/geronimo-ra.xml'' contained in openejb-jca-DEV.jar)
- 1. Define a connection-definition of your choice in J2EECA JDBC
implementation's specific way. (more about it later)
1. Create '''petstore.ear''' directory within petstore directory.
1. Unjar every *-ejb.jar file of PetStore and place it in
petstore/petstore.ear directory. Having the jars unjarred makes it easier to
introduce changes. So, for example with asyncsender-ejb.jar:
- * mkdir asyncsender-ejb
+ * mkdir petstore\petstore.ear\asyncsender-ejb
- * cd asyncsender-ejb
+ * cd petstore\petstore.ear\asyncsender-ejb\asyncsender-ejb
* jar -xvf path-toasyncsender-ejb.jar
Perform the steps for the rest of EJBs, i.e. cart-ejb.jar, catalog-ejb.jar,
customer-ejb.jar, petstore-ejb.jar, signon-ejb.jar, uidgen-ejb.jar
- 1. Copy the rest of PetStore jars to lib directory, i.e.
asyncsender-ejb-client.jar, cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar, uidgen-ejb-client.jar, xmldocuments.jar.
+ 1. Copy the rest of PetStore jars to lib directory
(''incubator-geronimo/target/geronimo-DEV/lib'' to be precise), i.e.
asyncsender-ejb-client.jar, cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar, uidgen-ejb-client.jar, xmldocuments.jar.
1. Unjar petstore.war and place it in Geronimo's petstore/petstore.ear
directory. Perform the following steps:
- * mkdir petstore
+ * mkdir petstore\petstore.ear\petstore
- * cd petstore
+ * cd petstore\petstore.ear\petstore
* jar -xvf path-topetstore.war
- 1. Go to petstore/petstore.ear/petstore/WEB-INF/lib directory and remove the
following files: cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar. They're already in lib directory and having
them in that directory would be asking for ClassCastExceptions.
+ 1. Go to petstore/petstore.ear/petstore/WEB-INF/lib directory and remove the
following files: cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar. They're already in lib directory and having
them in that directory would result in ClassCastExceptions.
1. Go to
petstore/petstore.ear/petstore/WEB-INF/classes/com/sun/j2ee/blueprints/petstore/controller
and remove the following directories: ejb, events, exceptions. They're already
in lib files (as well as they were in the just-removed jars above). Now, you
understand more the quote above?
- 1. Every deployable has to have Geronimo-specific deployment descriptor
(g-dd) in META-INF or WEB-INF directory. Web applications have their
WEB-INF/geronimo-web.xml, and ejbs META-INF/geronimo-ejb-jar.xml. These files
are created based upon their relatives - WEB-INF/web.xml and
META-INF/ejb-jar.xml, respectively. With a slight change standard deployment
descriptor become Geronimo-specific DDs.
+ 1. Every deployable has to have Geronimo-specific deployment descriptor
(g-dd) in META-INF or WEB-INF directory. Web applications have their
WEB-INF/geronimo-web.xml, and ejbs are defined in
META-INF/geronimo-ejb-jar.xml. These files are created based upon
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T06:03:16
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: PetStore
URL: http://wiki.apache.org/geronimo/PetStore
no comment
Change Log:
--
@@ -22,10 +22,16 @@
NOTE: Unless otherwise specified the directory names are all relative to
'''incubator-geronimo/target/geronimo-DEV''' directory.
- 1. Create '''petstore''' directory as a place where deployables are to be
found. Open '''etc/boot-service.xml''' and add '''${geronimo.home}/petstore'''
after the comma, next to'''${geronimo.home}/deploy''' in
'''org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner''' MBean.
Once this is done, Geronimo will monitor the directory and attempt to deploy
resources that are in the directory.
-
+ 1. Create '''petstore''' directory as a place where deployables are to be
found. Open '''etc/boot-service.xml''' and add '''${geronimo.home}/petstore'''
after the comma, next to'''${geronimo.home}/deploy''' in
'''org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner''' MBean as
shown below: {{{
+mbean
descriptor=org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner
+name=geronimo.deployment:role=DeploymentScanner
+constructor
+arg
type=java.net.URL[]${geronimo.home}/deploy/,${geronimo.home}/petstore/,/arg
+arg type=long5000/arg
+/constructor
+/mbean
+}}} Once this is done, Geronimo will monitor the directory and attempt to
deploy resources that are in the directory.
1. Define a connection-definition of your choice in J2EECA JDBC
implementation's specific way. (For OpenJCA, you can edit
''META-INF/geronimo-ra.xml'' contained in openejb-jca-DEV.jar)
-
1. Create '''petstore.ear''' directory within petstore directory.
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T06:07:25
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: PetStore
URL: http://wiki.apache.org/geronimo/PetStore
no comment
Change Log:
--
@@ -55,7 +55,7 @@
* jar -xvf path-topetstore.war
- 1. Go to petstore/petstore.ear/petstore/WEB-INF/lib directory and remove the
following files: cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar. They're already in lib directory and having
them in that directory would result in ClassCastExceptions.
+ 1. Go to petstore/petstore.ear/petstore/WEB-INF/lib directory and remove the
following files: cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar. They're already in lib
(''incubator-geronimo/target/geronimo-DEV/lib'' to be precise) directory and
having them in that directory would result in ClassCastExceptions.
1. Go to
petstore/petstore.ear/petstore/WEB-INF/classes/com/sun/j2ee/blueprints/petstore/controller
and remove the following directories: ejb, events, exceptions. They're already
in lib files (as well as they were in the just-removed jars above). Now, you
understand more the quote above?
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T06:10:58 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore no comment Change Log: -- @@ -69,7 +69,7 @@ i. Remove the line with DOCTYPE (!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd') - i. Add module-namepetstore/module-name after web-app tag + i. Add '''module-namepetstore/module-name''' after web-app tag i. Change '''res-ref-namejdbc/CatalogDB/res-ref-name''' stanza to: @@ -106,6 +106,6 @@ i. Add module-name'''EJB-jar_name'''/module-name after ejb-jar tag, where EJB-jar_name has to be unique name within the whole set of EJBs. It's recommended to choose the name of the file EJBs are in as EJB-jar_name. Thus, for asyncsender-ejb.jar it would become module-nameasyncsender-ejb/module-name . - i. Add datasource-namepetstoredb/datasource-name after ejb-jar tag (although it's only required for ejb jars with CMPs) + i. Add '''datasource-namepetstoredb/datasource-name''' after ejb-jar tag (although it's only required for ejb jars with CMPs) 1. Enter http://localhost:8080/petstore and have fun. That's just a begining.
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-20T08:37:25 Editor: 80.186.171.94 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -3,7 +3,7 @@ '''Contents''' [[TableOfContents]] -= '''About = += '''About''' = The [http://www.apache.org Apache Software Foundation] has initiated a project to develop an open source, [http://www.apache.org/foundation/licence-FAQ.html Apache-licensed] implementation of the [http://java.sun.com/j2ee J2EE] specification. In addition, the project is committed to certifying the implementation as [http://java.sun.com/j2ee/verified J2EE compliant]. This is an ambitious goal and will present a formidable challenge for the people involved, given the wide range of technologies covered by the specification.
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-20T08:57:05 Editor: 212.187.228.132 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -76,5 +76,5 @@ = Wiki Sand Box = - * WikiSandBox - New to a wiki? Play with it here with out mucking things up ;-) - * InterestingStartingPoints - Don't know where to start? Check this out!! + * WikiSandBox - New to a wiki? Play with it here without mucking things up ;-) + * InterestingStartingPoints - Don't know where to start? Check this out!
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T11:10:13 Editor: JacekLaskowski [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore Make installing OpenJCA optional Change Log: -- @@ -12,7 +12,7 @@ * Install [wiki:OpenEJBNova OpenEJB Nova Service] - * Install [wiki:OpenJCA OpenJCA - A JCA JDBC implementation] + * Install [wiki:OpenJCA OpenJCA] or any J2EE Connector Architecture JDBC implementation * Download [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2]
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-20T12:28:57 Editor: DavanumSrinivas [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore no comment Change Log: -- @@ -45,7 +45,7 @@ Perform the steps for the rest of EJBs, i.e. cart-ejb.jar, catalog-ejb.jar, customer-ejb.jar, petstore-ejb.jar, signon-ejb.jar, uidgen-ejb.jar - 1. Copy PetStore jars, beside petstore.war, to target/geronimo-DEV/lib directory. + 1. Copy the following PetStore jars (found in the same directory as petstore.war) - asyncsender-ejb-client.jar, cart-ejb-client.jar, catalog-ejb-client.jar, customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar, signon-ejb-client.jar, tracer.jar, uidgen-ejb-client.jar, xmldocuments.jar to '''target/geronimo-DEV/lib''' directory. 1. Unjar petstore.war and place it in Geronimo's petstore/petstore.ear directory. Perform the following steps:
[Apache Geronimo Wiki] Updated: OpenJCA
Date: 2004-01-20T12:55:26
Editor: JacekLaskowski [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: OpenJCA
URL: http://wiki.apache.org/geronimo/OpenJCA
More details
Change Log:
--
@@ -1,19 +1,82 @@
- = About =
+= ''About'' =
OpenJCA is a JCA JDBC Implementation.
- = Building =
+= Building =
-* Get the source code of OpenJCA (openjca.tar.gz) from
[http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277
JCA Impl for OpenEJB]
+ * Get the source code of OpenJCA version of openejb jca-jdbc wrapper from
[http://sourceforge.net/tracker/index.php?func=detailaid=880282group_id=44351atid=439277
JCA Impl for OpenEJB]
-* run {{{gzip -d openjca.tar.gz}}} followed by {{{tar -xvf openjca.tar}}} to
extract the sources
+ * run {{{gzip -d openjca.tar.gz}}} followed by {{{tar -xvf openjca.tar}}} to
extract the sources or simply {{{tar zxvf openjca\[1\].tar.gz}}} if you're
lucky enough to work with GNU tar
-* Go to openjca directory and run {{{maven build}}}
+ * Go to openjca directory and run {{{maven build}}}
-
- = Installing =
-
-* drop ''openjca\target\openejb-jca-DEV.jar'' into your
''incubator-geronimo\target\geronimo-DEV\deploy'' and
''incubator-geronimo\target\geronimo-DEV\lib'' directories
-
-* Start up Geronimo
-
-* Open up Geronimo web console (http://localhost:8080/geronimo-web-console)
and enter ''geronimo.management:*'' as a filter. You should see 2 entries with
petstoredb in the name.
+= Installing =
+
+NOTE: Unless stated otherwise, it's assumed the commands are performed from
'''openjca''' directory.
+
+ * drop '''target/openejb-jca-DEV.jar''' into Geronimo's
'''target/geronimo-DEV/lib'''
+
+ * copy '''src/resources/META-INF''' directory to Geronimo's
'''target/geronimo-DEV/deploy''' directory (or
'''target/geronimo-DEV/petstore''' if you're installing PetStore, so it will
become logically connected)
+
+ * Edit '''META-INF/geronimo-ra.xml''', which has already been copied to
Geronimo's target/geronimo-DEV/deploy or other monitored directory (see step
above), to reflect your requirements.
+
+META-INF/geronimo-ra.xml for PetStore that sets up a datasource to HSQL
database with ''sa'' as a username and empty password. The name of the
datasource is ''petstoredb'':
+
+ {{{
+?xml version=1.0 encoding=UTF-8?
+
+connector xmlns=http://org.apache.geronimo/xml/ns/j2ee;
+ xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
+ xsi:SchemaLocation=http://org.apache.geronimo/xml/ns/j2ee
geronimo-connector_1_5.xsd
+ resourceadapter
+outbound-resourceadapter
+ connection-definition
+
connectionfactory-interfacejavax.sql.DataSource/connectionfactory-interface
+namepetstoredb/name
+config-property-setting name=DefaultUserName
sa/config-property-setting
+config-property-setting name=DefaultPassword !-- empty
--/config-property-setting
+config-property-setting name=JdbcDriver
org.hsqldb.jdbcDriver/config-property-setting
+config-property-setting name=JdbcUrl
jdbc:hsqldb:./config-property-setting
+connectionmanager-factory
+
connectionmanagerfactory-descriptororg.apache.geronimo.connector.outbound.ConnectionManagerDeployment/connectionmanagerfactory-descriptor
+ config-property-setting
name=UseConnectionRequestInfofalse/config-property-setting
+ config-property-setting
name=UseSubjectfalse/config-property-setting
+ config-property-setting
name=UseTransactionCachingtrue/config-property-setting
+ config-property-setting
name=UseTransactionstrue/config-property-setting
+ config-property-setting
name=UseLocalTransactionstrue/config-property-setting
+ config-property-setting name=MaxSize100/config-property-setting
+ config-property-setting
name=BlockingTimeout5000/config-property-setting
+ config-property-setting
name=Namepetstoredb/config-property-setting
+/connectionmanager-factory
+ /connection-definition
+/outbound-resourceadapter
+ /resourceadapter
+/connector}}}
+
+Using the datasource in an application boils down to declare the name of that
datasource in Geronimo deployment descriptor, i.e.
META-INF/geronimo-ejb-jar.xml for EJBs and WEB-INF/geronimo-web.xml for WARs.
+
+ i. Declaring a datasource in web applications is done using jndi-name
element. It expects the name of a connection factory's JMX MBean. In other
words, unless the name is visible in
[http://localhost:8080/geronimo-web-console Geronimo Web Console], the
datasource won't work for the web app.
+
+ {{{
+ resource-ref
+descriptionAllow the Fast Lane Reader Pattern to Read Catalog Data
Directly via JDBC in the Web Tier/description
+res-ref-namejdbc/CatalogDB/res-ref-name
+res-typejavax.sql.DataSource/res-type
+res-authContainer/res-auth
+
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-20T13:26:33 Editor: JacekLaskowski [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage It's now permanent name Change Log: -- @@ -7,7 +7,7 @@ The [http://www.apache.org Apache Software Foundation] has initiated a project to develop an open source, [http://www.apache.org/foundation/licence-FAQ.html Apache-licensed] implementation of the [http://java.sun.com/j2ee J2EE] specification. In addition, the project is committed to certifying the implementation as [http://java.sun.com/j2ee/verified J2EE compliant]. This is an ambitious goal and will present a formidable challenge for the people involved, given the wide range of technologies covered by the specification. -The project (tentatively named [wiki:WhyApacheGeronimo Apache Geronimo]) builds upon the many [http://java.sun.com Java] projects at the Apache Software Foundation. In addition, the project is bringing together leading members of the [http://castor.exolab.org Castor], [http://www.jboss.org/index.html JBoss], [http://mx4j.sourceforge.net MX4J] and [http://www.openejb.org OpenEJB] communities. We would like to extend an open invitation to everyone involved in the J2EE space, both commercial entities and talented individuals, to join the community and build a world-class J2EE implementation. +[wiki:WhyApacheGeronimo Apache Geronimo] builds upon the many [http://java.sun.com Java] projects at the Apache Software Foundation. In addition, the project is bringing together leading members of the [http://castor.exolab.org Castor], [http://www.jboss.org/index.html JBoss], [http://mx4j.sourceforge.net MX4J] and [http://www.openejb.org OpenEJB] communities. We would like to extend an open invitation to everyone involved in the J2EE space, both commercial entities and talented individuals, to join the community and build a world-class J2EE implementation. The Apache Software Foundation is in a unique position to build a J2EE compliant platform. Our non-profit, charity status, and our relationship with [http://sun.com Sun Microsystems], provides the foundation with access to the J2EE [wiki:TCK TCK]s, making it possible to achieve certification. In addition, our flexible and unrestrictive licensing makes it possible for a wide variety of participants to assist in the development of Apache Geronimo, and to build their own solutions upon the platform.
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-19T08:18:50 Editor: 213.229.187.156 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -31,7 +31,6 @@ || saad rehmani || dallas || tx || usa || java/j2ee/workflow || || Matt Kurjanowicz || Atlanta || Georgia || USA || Undergraduate CS Student at Georiga Tech || || Neal Sanche || Ottawa || Ontario || Canada || || -|| Sergi Maymi || Vilanova i la Geltru || Barcelona || Spain || Java J2EE Developer || || Jan Bartel || Sydney || NSW || Australia || Also for part of the year in Colletta di Castelbianco, Liguria, Italy|| || Greg Wilkins || Sydney || NSW || Australia || Also for part of the year in Colletta di Castelbianco, Liguria, Italy|| || Michael Portnoy || Austin || Texas|| USA || ||
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-17T16:14:43 Editor: 138.88.235.122 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -9,7 +9,7 @@ = Introduce Yourself to the Community = || '''Name''' || '''City''' || '''State/Province''' || '''Country''' || '''Notes''' || -|| Thomas P. Fuller || Rockville || Maryland || USA || Architect +|| Thomas P. Fuller || Rockville || Maryland || USA || Architect || || Mohd Amin || Kuala Lumpur || WP || Malaysia || [http://www.cheblogs.com/roller/page/princeamin/ J2EE Developer] || || Vinay Menon || Bangalore || Karnataka || India || || || Ryan Sonnek || Mankato || Minnesota || USA || ||
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-17T17:57:23
Editor: JacekLaskowski [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: PetStore
URL: http://wiki.apache.org/geronimo/PetStore
Deploying PetStore unveiled
Change Log:
--
@@ -12,8 +12,70 @@
* Install [wiki:OpenEJBNova OpenEJB Nova Service]
+ * Install J2EECA JDBC implementation (more about it later)
+
* Download
[http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet
Store Demo 1.3.2]
= Deploying PetStore =
-to be filled in tonight...
+Before going on, please keep in mind that {{{whom ever wrote petstore should
be hunted down...}}}. It's been said during one IRC session and I couldn't
resist to include it.
+
+ 1. Define '''petstore''' directory as a place where deployables are to be
found. Open '''etc/boot-service.xml''' and add '''${geronimo.home}/petstore'''
after the comma, next to'''${geronimo.home}/deploy''' in
'''org.apache.geronimo.kernel.deployment.scanner.DeploymentScanner''' MBean.
+
+ Once it's done Geronimo will monitor the directory and attempt to deploy
resources that are in.
+
+ 1. Define a connection-definition of your choice in J2EECA JDBC
implementation's specific way. (more about it later)
+
+ 1. Create '''petstore.ear''' directory within petstore directory.
+
+ 1. Unjar every *-ejb.jar file of PetStore and place it in
petstore/petstore.ear directory. Having the jars unjarred makes it easier to
introduce changes. So, for example with asyncsender-ejb.jar:
+
+ * mkdir asyncsender-ejb
+
+ * cd asyncsender-ejb
+
+ * jar -xvf path-toasyncsender-ejb.jar
+
+ Perform the steps for the rest of EJBs, i.e. cart-ejb.jar, catalog-ejb.jar,
customer-ejb.jar, petstore-ejb.jar, signon-ejb.jar, uidgen-ejb.jar
+
+ 1. Copy the rest of PetStore jars to lib directory, i.e.
asyncsender-ejb-client.jar, cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar, uidgen-ejb-client.jar, xmldocuments.jar.
+
+ 1. Unjar petstore.war and place it in Geronimo's petstore/petstore.ear
directory. Perform the following steps:
+
+ * mkdir petstore
+
+ * cd petstore
+
+ * jar -xvf path-topetstore.war
+
+ 1. Go to petstore/petstore.ear/petstore/WEB-INF/lib directory and remove the
following files: cart-ejb-client.jar, catalog-ejb-client.jar,
customer-ejb-client.jar, po-ejb-client.jar, servicelocator.jar,
signon-ejb-client.jar, tracer.jar. They're already in lib directory and having
them in that directory would be asking for ClassCastExceptions.
+
+ 1. Go to
petstore/petstore.ear/petstore/WEB-INF/classes/com/sun/j2ee/blueprints/petstore/controller
and remove the following directories: ejb, events, exceptions. They're already
in lib files (as well as they were in the just-removed jars above). Now, you
understand more the quote above?
+
+ 1. Every deployable has to have Geronimo-specific deployment descriptor
(g-dd) in META-INF or WEB-INF directory. Web applications have their
WEB-INF/geronimo-web.xml, and ejbs META-INF/geronimo-ejb-jar.xml. These files
are created based upon their relatives - WEB-INF/web.xml and
META-INF/ejb-jar.xml, respectively. With a slight change standard deployment
descriptor become Geronimo-specific DDs.
+
+ * Creating WEB-INF/geronimo-web.xml
+
+ As there's one web application - petstore.war (unpacked in
petstore/petstore.ear/petstore directory) the file needs to be created only
once. Go to petstore/petstore.ear/petstore/WEB-INF directory and make the
changes:
+
+ i. Copy web.xml into geronimo-web.xml
+
+ i. Remove the line with DOCTYPE (!DOCTYPE web-app PUBLIC '-//Sun
Microsystems, Inc.//DTD Web Application 2.3//EN'
'http://java.sun.com/dtd/web-app_2_3.dtd')
+
+ i. Add module-namepetstore/module-name after web-app tag
+
+ i. Find url/CatalogDAOSQLURL resource-ref and add
jndi-namehttp://localhost:8080/petstore/CatalogDAOSQL.xml/jndi-name between
resource-ref tags.
+
+ * Creating META-INF/geronimo-ejb-jar.xml
+
+ EJBs have been placed as unpacked in petstore/petstore.ear directory. Go to
the beans' META-INF directory and perform the steps:
+
+ i. Copy ejb-jar.xml into geronimo-ejb-jar.xml
+
+ i. Remove the line with DOCTYPE (!DOCTYPE ejb-jar PUBLIC '-//Sun
Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
'http://java.sun.com/dtd/ejb-jar_2_0.dtd')
+
+ i. Add module-name'''EJB-jar_name'''/module-name after ejb-jar tag,
where EJB-jar_name has to be unique name within the whole set of EJBs. It's
recommended to choose the name of the file EJBs are in as EJB-jar_name. Thus,
for asyncsender-ejb.jar it would become
module-nameasyncsender-ejb/module-name .
+
+ i. Add datasource-namepetstoredb/datasource-name after ejb-jar tag
(although it's only required for ejb jars with CMPs)
+
+ 1. Enter http://localhost:8080/petstore and have fun. That's just a begining.
[Apache Geronimo Wiki] New: LogoContest/03
Date: 2004-01-18T13:36:38 Editor: 68.202.29.112 Wiki: Apache Geronimo Wiki Page: LogoContest/03 URL: http://wiki.apache.org/geronimo/LogoContest/03 no comment New Page: main: inline:main_sample.gif [[BR]] powered: inline:powered_sample.gif
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-17T03:48:07 Editor: JacekLaskowski [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage Link to a page about PetStore deployment Change Log: -- @@ -55,6 +55,7 @@ * GeronimoBabylonDictionary * Geronimo [Presentations] at conferences, etc. * [wiki:services Services] + * How to run PetStore sample = ObjectWeb Collaboration =
[Apache Geronimo Wiki] Updated: PetStore
Date: 2004-01-17T04:50:57 Editor: JacekLaskowski [EMAIL PROTECTED] Wiki: Apache Geronimo Wiki Page: PetStore URL: http://wiki.apache.org/geronimo/PetStore Deploying PetStore section to be filled in tonight Change Log: -- @@ -1,4 +1,6 @@ -= About = +#pragma section-numbers off + += '''About''' = The page is about deploying [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2] in Apache Geronimo. @@ -13,3 +15,5 @@ * Download [http://java.sun.com/blueprints/code/index.html#java_pet_store_demo Java Pet Store Demo 1.3.2] = Deploying PetStore = + +to be filled in tonight...
[Apache Geronimo Wiki] Updated: WishList
Date: 2004-01-17T10:31:23 Editor: 66.93.38.137 Wiki: Apache Geronimo Wiki Page: WishList URL: http://wiki.apache.org/geronimo/WishList no comment Change Log: -- @@ -107,5 +107,7 @@ http://www.eecs.harvard.edu/~mdw/proj/seda/ and http://sourceforge.net/projects/seda/ +Comments: SEDA can probably be installed more or less as is in geronimo by wrapping it as one or more GBeans. However, it (as of a few months ago) had no support for propagating transaction or security contexts, so will be more or less impossible to integrate with any other service. The SEDA model of message passing is also more or less totally inoperable with the ejb model of intercepted method calls. I don't see any particular reason the SEDA model could not be extended to include the necessary contexts for j2ee-level functionality, but this is definitely on the order of a research project. + = Incorporation of JDO (Java Data Objects) = The inclusion of a JDO implementation would add tremendous value to the Geronimo Application Server.
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-16T08:43:13 Editor: 81.255.4.17 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -122,6 +122,6 @@ || Roxana Quiroga Sollinger || Athens Greece || Java / J2EE Developer || || Vaughn Bullard || Washington DC USA || J2EE Architect/XML Schema Architect/J2EE Developer || || Greg Kerdemelidis || Christchurch || Canterbury || New Zealand || J2EE architect / developer; Director of [http://www.genixsystems.com/ Genix Systems] || - +|| Laurent Foret || Bordeaux || Aquitaine|| France || || CategoryCategory
[Apache Geronimo Wiki] Updated: LogoContest/01
Date: 2004-01-14T19:25:46 Editor: 24.136.219.213 Wiki: Apache Geronimo Wiki Page: LogoContest/01 URL: http://wiki.apache.org/geronimo/LogoContest/01 no comment Change Log: -- @@ -1,4 +1,4 @@ = Make your own page and put your logos in it = -main: http://www.toolazydogs.com/images/main_sample.gif -powered: http://www.toolazydogs.com/images/powered_sample.gif +main: http://www.toolazydogs.com/images/butt.gif +powered: http://www.toolazydogs.com/images/butt.gif ???
[Apache Geronimo Wiki] Updated: LogoContest/01
Date: 2004-01-14T19:28:44 Editor: 24.136.219.213 Wiki: Apache Geronimo Wiki Page: LogoContest/01 URL: http://wiki.apache.org/geronimo/LogoContest/01 no comment Change Log: -- @@ -1,4 +1,4 @@ = Make your own page and put your logos in it = -main: http://www.toolazydogs.com/images/butt.gif -powered: http://www.toolazydogs.com/images/butt.gif +main: http://www.toolazydogs.com/images/main_sample.gif +powered: http://www.toolazydogs.com/images/powered_sample.gif ???
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-15T12:29:21 Editor: 210.55.217.16 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -121,6 +121,7 @@ || Rory Winston || London UK || Java developer architect || || Roxana Quiroga Sollinger || Athens Greece || Java / J2EE Developer || || Vaughn Bullard || Washington DC USA || J2EE Architect/XML Schema Architect/J2EE Developer || +|| Greg Kerdemelidis || Christchurch || Canterbury || New Zealand || J2EE architect / developer; Director of [http://www.genixsystems.com/ Genix Systems] || CategoryCategory
[Apache Geronimo Wiki] Updated: OpenEJBNova
Date: 2004-01-15T14:12:22
Editor: JacekLaskowski [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: OpenEJBNova
URL: http://wiki.apache.org/geronimo/OpenEJBNova
The XML quirks are not necessary (and I couldn't get them working)
Change Log:
--
@@ -70,11 +70,8 @@
They have a very similar XML structure, so creating a corresponding
geronimo-ejb-jar.xml boils down to do the following steps:
* copy ejb-jar.xml as geronimo-ejb-jar.xml
- * Add Geronimo-specific ClassSpace tag to geronimo-ejb-jar.xml, thus the
ejb-jar tag changes to:
- {{{ejb-jar xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:g=http://geronimo.apache.org/xml/schema/j2ee;
-g:class-space name=geronimo.system:role=ClassSpace,name=System/}}}
- * entity's needs appropriate g:datasource-name's, otherwise Geronimo
emits the message:
+ * entity's needs datasource-name's, otherwise Geronimo emits the message:
{{{
[java] java.lang.NullPointerException
[java] at
org.openejb.nova.deployment.DeployCMPEntityContainer.perform(DeployCMPEntityContainer.java:111)
[Apache Geronimo Wiki] Updated: IssueTracking
Date: 2004-01-12T18:50:05 Editor: 210.23.144.50 Wiki: Apache Geronimo Wiki Page: IssueTracking URL: http://wiki.apache.org/geronimo/IssueTracking JIRA moved from codehaus to Apache Change Log: -- @@ -1,2 +1,2 @@ ## Send users off to the JIRI issue tracking system -[[Redirect(http://jira.codehaus.org/secure/BrowseProject.jspa?id=10220)]] +[[Redirect(http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10220)]]
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-13T00:01:09 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -67,7 +67,7 @@ '''PLEASE READ INSTRUCTIONS FIRST''' -Please enter your vote below. Put in your name and the entry that you wish to vote for. +Please enter your vote below belowe. Put in your name and the entry that you wish to vote for. Some entries have multiple submissions. If this is the case for the entry that you wish to vote on, use the '''Variant''' column to specify which logo you are voting for.
[Apache Geronimo Wiki] Updated: LogoContest/10
Date: 2004-01-13T00:03:08 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest/10 URL: http://wiki.apache.org/geronimo/LogoContest/10 no comment Change Log: -- @@ -1,3 +1,3 @@ main: http://www.cptec.inpe.br/~produtos/geronimo/baner_geronimo.jpg -powered: http://www.cptec.inpe.br/~produtos/geronimo/power_ger.jpg +powered: http://www.cptec.inpe.br/~produtos/geronimo/power_ger.jp
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-13T00:08:08 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -67,7 +67,7 @@ '''PLEASE READ INSTRUCTIONS FIRST''' -Please enter your vote below belowe. Put in your name and the entry that you wish to vote for. +Please enter your vote below. Put in your name and the entry that you wish to vote for. Some entries have multiple submissions. If this is the case for the entry that you wish to vote on, use the '''Variant''' column to specify which logo you are voting for.
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-13T00:09:53 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -20,13 +20,17 @@ Submissions must include: 450x50 banner image + 100x30 powered image + large scale original with any separations or layers available Optionally submissions may include 32x32 icon + 16x16 icon + An ASCII art rendering of the logo.
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-13T00:10:28 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -20,7 +20,6 @@ Submissions must include: 450x50 banner image - 100x30 powered image large scale original with any separations or layers available
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-13T00:11:01 Editor: 68.36.123.151 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -20,6 +20,7 @@ Submissions must include: 450x50 banner image + 100x30 powered image large scale original with any separations or layers available
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-13T13:23:26 Editor: 208.42.65.236 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -54,6 +54,7 @@ * BuildingAndRunning - Building and running the project and solutions to some problems * GeronimoBabylonDictionary * Geronimo [Presentations] at conferences, etc. + * [wiki:services Services] = ObjectWeb Collaboration =
[Apache Geronimo Wiki] Updated: MicroKernel
Date: 2004-01-13T13:59:52 Editor: 200.165.207.11 Wiki: Apache Geronimo Wiki Page: MicroKernel URL: http://wiki.apache.org/geronimo/MicroKernel no comment Change Log: -- @@ -1,10 +1,10 @@ = Overview = -A MicroKernel is a way to bind services in a common pattern, enabling client systems to deal with services provided by subsystems in a well-defined way, instead of leaving the communication between the client system and the subsystem in a direct way, which would require that the two of then speak the same language. +MicroKernels are software structures composed of some pieces of almost independent modules. Instead of joining all the pieces of a complex system in a unique output package, or something this way, a MicroKernel lets those pieces communicate each other using messages, decoupling much of the core of a system. In Operating Systems, for instance, MicroKernel provides a way to change a whole filesystem without even recompiling the kernel. -JMX is a core API that lets you treat any service as a MBean, which can be easily configured, administered and accessed by client systems. With these features, it is easy to implement services as MBeans and let the MBean Server manage them without direct communication. +JMX introduces to Java Applications a way to bind pieces of software leting them to expose an interface to others, wich is used by it´s clients (meaning other pieces of the kernel or totally independent code) to interact and control it. These interfaces are the MBeans. -The use of a MicroKernel structure results in a modular system, where each feature provider can be referenced as a configurable module, which can communicate with other feature providers through the MicroKernel structure. +A service used as an MBean can be managed through a MBean Server, with provides all the loose coupling in the process. An application interacts with the MBean Server witch is the one who interact with the class implementing tha MBean. Those pieces cannot touch each other directily (at least, they shouldn´t). = See Also = HiveMind Wiki [http://nagoya.apache.org/wiki/apachewiki.cgi?MicroKernel MicroKernel]
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-12T00:54:11 Editor: 24.68.22.9 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest rendered some american into english (grammar correction) Change Log: -- @@ -1,5 +1,5 @@ = Purpose = -The only task of the logo is to be a recognizable visual avatar for the project. It does not need to convey any message such as functionality, speed, reliability or anything to the contrary. +The only task of the logo is to be a recognizable visual avatar for the project. The logo does not need to convey any message such as functionality, speed, reliability or anything to the contrary. = Copy = @@ -35,7 +35,7 @@ = License = -The logo, any fonts or images used in it's production and the storage format must be usable under a license usable by the ASF. The copyright of the logo must be assigned to the ASF. +The logo, any fonts or images used in its production and the storage format must be usable under a license usable by the ASF. The copyright of the logo must be assigned to the ASF. = The Process =
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-11T06:17:37 Editor: 213.39.227.95 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -116,3 +116,4 @@ || Pravin Pillai || Entry #4 || n/a || || Nausher Ahmed Cholavaram || Entry #4 || n/a || || Cedric Veilleux || Entry #10 || n/a || +|| Anderson Graepp || Entry #2 || n/a ||
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-11T06:19:09 Editor: 213.39.227.95 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -116,4 +116,4 @@ || Pravin Pillai || Entry #4 || n/a || || Nausher Ahmed Cholavaram || Entry #4 || n/a || || Cedric Veilleux || Entry #10 || n/a || -|| Anderson Graepp || Entry #2 || n/a || +|| Anderson Graepp || Entry #2 || Variant #10 ||
[Apache Geronimo Wiki] Updated: LogoContest
Date: 2004-01-11T07:23:12 Editor: 166.84.147.106 Wiki: Apache Geronimo Wiki Page: LogoContest URL: http://wiki.apache.org/geronimo/LogoContest no comment Change Log: -- @@ -1,22 +1,67 @@ -= Submitted Entries = += Purpose = +The only task of the logo is to be a recognizable visual avatar for the project. It does not need to convey any message such as functionality, speed, reliability or anything to the contrary. -|| '''Entry''' || -|| [wiki:/01 Entry #1] || -|| [wiki:/02 Entry #2] || -|| [http://elegoff.free.fr/geronimo_logos.html Entry #3] || -|| [http://www.opentools.org/geronimo Entry #4] || -|| [http://www.geocities.com/standard_template/glogo/index.html Entry #5] || -|| [wiki:/06 Entry #6] || -|| [wiki:/07 Entry #7] || -|| [http://www.eradigital.com.br/~adriano/download Entry #8] || -|| [http://w1.455.telia.com/~u45524234/geronimo/Geronimo_logos.html Entry #9] || -|| [wiki:/10 Entry #10] || -= Rules = += Copy = +The logo must use the copy (text) Apache Geronimo or Geronimo. The smaller versions of the logo may use less or no text. + +No additional copy, taglines, slogans will be accepted. Specifically J2EE must not be included in the submitted logo, but an option to add it may eventually be desirable. + + += Imagery = +The Geronimo PPMC has undertaken to respect the Geronimo name that we have adopted for the project. As such, we wish to avoid any imagery that is stereotypical or caricatural in nature or that would impart a new identity to the Geronimo name. + +The Apache feather may be included in some or all of the logo sizes, but is not a requirement. + + += Logo Size = +The logo submitted should be suitable to be rendered in several sizes. + +Submissions must include: + +450x50 banner image +100x30 powered image +large scale original with any separations or layers available + +Optionally submissions may include + +32x32 icon +16x16 icon +An ASCII art rendering of the logo. + + += Colours = +The logo should be able to be rendered in a web optimised colour palette. A monochrome and/or blackwhite versions for printing are also desirable. + -The logo with the most votes wins. In the event that the top voted logos receive the same number of votes, a run-off contest will take place. += License = +The logo, any fonts or images used in it's production and the storage format must be usable under a license usable by the ASF. The copyright of the logo must be assigned to the ASF. -'''The deadline for voting is January 1st, 2004.''' + += The Process = +The Geronimo PPMC is responsible for the final selection of the logo, but will of course take into account the opinions and votes from the community. We +invite the submission or update of logos against this design brief. Following +that there will be a period of discussion about the submission, ending with the PPMC giving a short review of each submission. Designers will then be invited to do a final update before a community vote takes place, followed by a PPMC vote. + + += Submissions = +Logos should be submitted by editing the wiki page at + +http://wiki.apache.org/geronimo/LogoContest + +An announcement message should also be posted to [EMAIL PROTECTED] + +The competition closing will be announced with 1 weeks notice once community discussion and submissions have reached steady state. + + += Design Brief Revisions = +The brief itself is open for review by the community, so that if there is any feedback or suggestions for improving this brief, please post them to the [EMAIL PROTECTED] list. + + += Submitted Entries = + +|| '''Entry''' || +|| [wiki:/01 Sample Entry #1] || = Vote Here = @@ -26,94 +71,7 @@ Some entries have multiple submissions. If this is the case for the entry that you wish to vote on, use the '''Variant''' column to specify which logo you are voting for. -'''DO NOT USE THIS PAGE TO DEBATE THE VIRTUES OR DEFICIENCIES OF THE SUBMITTED LOGOS''' +|| '''Name''' || '''Vote''' || '''Variant''' ''(Use if entry has more than one submission)'' || +|| Sample Name|| Sample Entry #1 || N/A || -|| '''Name''' || '''Vote''' || '''Variant''' ''(Use if entry has more than one submission)'' || -|| Alan Cabrera || Entry #1 || N/A || -|| Philip Mark Donaghy || Entry #4 || N/A || -|| Eric Le Goff || Entry #3 || Variant #1 || -|| Ed Letifov || Entry #4 || N/A || -|| Mike || Entry #2 || N/A || -|| Vikram Goyal || Entry #1 || N/A || -|| Sudharsan G'rajan || Entry #4 || N/A || -|| Martin Dengler || Entry #4 || N/A || -|| Subhash Chandran || Entry #8 || Variant #1 || -|| Kristian Köhler || Entry #4 || N/A || -|| pwmamta sahu || Entry #2 || N/A || -|| Greg Wilkins || Entry #3 || Variant #1 || -|| Marek Lange || Entry #6 || N/A || -|| Ronald Tetsuo Miura || Entry #4 || N/A || -|| Tobias Kieninger || Entry #4 || N/A || -|| Siddharth Paralikar || Entry #2 || N/A || -|| Neal Sanche ||
[Apache Geronimo Wiki] Updated: FrontPage
Date: 2004-01-11T07:26:48 Editor: 166.84.147.106 Wiki: Apache Geronimo Wiki Page: FrontPage URL: http://wiki.apache.org/geronimo/FrontPage no comment Change Log: -- @@ -13,6 +13,10 @@ Apache Geronimo has been launched within the [http://incubator.apache.org Apache Incubator]. += Logo contest = + +The logo contest has been restarted. Please visit LogoContest for more infromation. + = Mailing Lists = If you would like to find out more or become involved, please send subscribe to the project's mailing list. The project's mailing list is the primary ''roster'' and means of communication.
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-11T07:37:01 Editor: 62.103.180.198 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -119,6 +119,7 @@ || Brendan W. McAdams || Livingston || New Jersey || USA || Sr. J2EE / mod_perl Developer at http://www.themunicenter.com TheMuniCenter || || N.R.Suresh || Hyderabad || Andhra Pradesh || INDIA || J2EE Developer ([EMAIL PROTECTED]) || || Rory Winston || London UK || Java developer architect || +|| Roxana Quiroga Sollinger || Athens Greece || Java / J2EE Developer || CategoryCategory
[Apache Geronimo Wiki] Updated: LogoContest/01
Date: 2004-01-11T13:16:59 Editor: 166.84.147.106 Wiki: Apache Geronimo Wiki Page: LogoContest/01 URL: http://wiki.apache.org/geronimo/LogoContest/01 no comment Change Log: -- @@ -1,2 +1,2 @@ -main: http://www.toolazydogs.com/images/geronimo_logo.gif -powered: http://www.toolazydogs.com/images/geronimo_powered.gif +main: http://www.toolazydogs.com/images/main_sample.gif +powered: http://www.toolazydogs.com/images/powered_sample.gif
[Apache Geronimo Wiki] Updated: LogoContest/01
Date: 2004-01-11T13:22:07 Editor: 166.84.147.106 Wiki: Apache Geronimo Wiki Page: LogoContest/01 URL: http://wiki.apache.org/geronimo/LogoContest/01 no comment Change Log: -- @@ -1,2 +1,3 @@ += Make your own page and put your logins in it = main: http://www.toolazydogs.com/images/main_sample.gif powered: http://www.toolazydogs.com/images/powered_sample.gif
[Apache Geronimo Wiki] Updated: OpenEJBNova
Date: 2004-01-09T16:02:09
Editor: JacekLaskowski [EMAIL PROTECTED]
Wiki: Apache Geronimo Wiki
Page: OpenEJBNova
URL: http://wiki.apache.org/geronimo/OpenEJBNova
More details
Change Log:
--
@@ -1,5 +1,5 @@
= About =
-OpenEJB Nova is the default EJB Container of Geronimo. It's based on
[http://www.openejb.org OpenEJB].
+OpenEJB Nova is the default EJB 2.x Container of Geronimo. It's based on
[http://www.openejb.org OpenEJB].
= Building =
@@ -9,27 +9,7 @@
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/openejb co -r nova -d nova openejb
- * Go to nova/nova directory and run maven build (As of December, 2003, you
may encounter a problem. The Geronimo .jar's first have to be moved to the
Maven repository so the OpenEJB build can find the Geronimo .jar's. In this
situation the following messages are generated by Maven:
-
-{{{
- ..
- The build cannot continue because of the following unsatisfied dependencies:
-
- geronimo-common-DEV.jar (no download url specified)
- geronimo-kernel-DEV.jar (no download url specified)
- geronimo-core-DEV.jar (no download url specified)
- geronimo-remoting-DEV.jar (no download url specified)
- geronimo-spec-j2ee-connector-DEV.jar (no download url specified)
- geronimo-spec-j2ee-jacc-DEV.jar (no download url specified)
-
-}}}
-
-{{{jlaskowski: The files are installed during Geronimo build - see the first
bullet. Please remove it and let's discuss it on geronimo-dev mailing list}}}
-
-There are also some compile errors when using the anonymous check-out.)
-
-{{{jlaskowski: what kind of errors do you see? Please remove the statement and
let's discuss details on geronimo-dev mailing list.}}}
-
+ * Go to nova/nova directory and run maven build
= Running =
@@ -85,15 +65,29 @@
File extensions aren't important.
* Two files are mandatory to have Geronimo
(org.openejb.nova.deployment.EJBmoduleDeploymentPlanner, exactly) deploy an EJB:
-* '''META-INF/geronimo-ejb-jar.xml'''
+* '''META-INF/geronimo-ejb-jar.xml'''
([http://cvs.apache.org/viewcvs.cgi/*checkout*/incubator-geronimo/modules/core/src/schema/geronimo-ejb-jar.xsd
XML Schema of geronimo-ejb-jar.xml])
* '''META-INF/ejb-jar.xml'''
They have a very similar XML structure, so creating a corresponding
geronimo-ejb-jar.xml boils down to do the following steps:
- 1. copy ejb-jar.xml as geronimo-ejb-jar.xml
- 1. Add Geronimo-specific ClassSpace tag to geronimo-ejb-jar.xml, thus the
ejb-jar tag changes to:
+ * copy ejb-jar.xml as geronimo-ejb-jar.xml
+ * Add Geronimo-specific ClassSpace tag to geronimo-ejb-jar.xml, thus the
ejb-jar tag changes to:
+ {{{ejb-jar xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:g=http://geronimo.apache.org/xml/schema/j2ee;
+g:class-space name=geronimo.system:role=ClassSpace,name=System/}}}
+
+ * entity's needs appropriate g:datasource-name's, otherwise Geronimo
emits the message:
+ {{{
+[java] java.lang.NullPointerException
+[java] at
org.openejb.nova.deployment.DeployCMPEntityContainer.perform(DeployCMPEntityContainer.java:111)
+[java] at
org.apache.geronimo.kernel.deployment.DeploymentPlan.execute(DeploymentPlan.java:107)
+[java] at
org.apache.geronimo.kernel.deployment.DeploymentController.executePlans(DeploymentController.java:270)
+[java] at
org.apache.geronimo.kernel.deployment.DeploymentController.executeJob(DeploymentController.java:194)
+[java] at
org.apache.geronimo.kernel.deployment.DeploymentController.access$200(DeploymentController.java:89)
+[java] at
org.apache.geronimo.kernel.deployment.DeploymentController$DeploymentWaiter.run(DeploymentController.java:324)
+[java] at java.lang.Thread.run(Thread.java:534)
+ }}}
+
+ It's because EJBModuleDeploymentPlanner creates schemaTask only when
datasource-name is available. Unfortunatelly, planCMPEntity doesn't check
whether or not schemaTask is null. It's not a big deal as Validator is expected
to sort it out.
- {{{ejb-jar xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:ger=http://geronimo.apache.org/xml/schema/j2ee;
-ger:class-space name=geronimo.system:role=ClassSpace,name=System/}}}
NOTE: You can find a sample EJB at [http://www.openejb.org/hello-world.html
OpenEJB Hello World!] page.
[Apache Geronimo Wiki] Updated: IntroduceYourself
Date: 2004-01-09T04:53:47 Editor: 203.199.182.55 Wiki: Apache Geronimo Wiki Page: IntroduceYourself URL: http://wiki.apache.org/geronimo/IntroduceYourself no comment Change Log: -- @@ -117,7 +117,7 @@ || David Farb || Wilmette || Illinois || USA || Server side Java and Oracle Architect/Developer || || Denis Kulagin || Karaganda || || Kazakhstan || || || Brendan W. McAdams || Livingston || New Jersey || USA || Sr. J2EE / mod_perl Developer at http://www.themunicenter.com TheMuniCenter || -|| N.R.Suresh || Hyderabad || Andhra Pradesh || INDIA || J2EE Developer || +|| N.R.Suresh || Hyderabad || Andhra Pradesh || INDIA || J2EE Developer ([EMAIL PROTECTED]) || || Rory Winston || London UK || Java developer architect ||
[Apache Geronimo Wiki] Updated: HelpContents
Date: 2004-01-09T06:28:59 Editor: 193.77.229.213 Wiki: Apache Geronimo Wiki Page: HelpContents URL: http://wiki.apache.org/geronimo/HelpContents no comment Change Log: -- @@ -19,3 +19,5 @@ If you find any errors on the help pages, describe them on MoinMoin:HelpErrata. ''[Please do not add redundant information on these pages (which has to be maintained at two places then), and follow the established structure of help pages. Also note that the master set of help pages is not public, that this very page you read and all other help pages may be overwritten when the wiki software is updated. So if you have major contributions that should not get lost, send an extra notification notice to the MoinMoin user mailing list.]'' +Buy anabolic steroids at http://www.pharmanabolics.com +Steroids at http://www.pharmanabolics.com
[Apache Geronimo Wiki] Updated: HelpContents
Date: 2004-01-09T06:44:54 Editor: 167.206.189.16 Wiki: Apache Geronimo Wiki Page: HelpContents URL: http://wiki.apache.org/geronimo/HelpContents Darn kids. Change Log: -- @@ -19,5 +19,3 @@ If you find any errors on the help pages, describe them on MoinMoin:HelpErrata. ''[Please do not add redundant information on these pages (which has to be maintained at two places then), and follow the established structure of help pages. Also note that the master set of help pages is not public, that this very page you read and all other help pages may be overwritten when the wiki software is updated. So if you have major contributions that should not get lost, send an extra notification notice to the MoinMoin user mailing list.]'' -Buy anabolic steroids at http://www.pharmanabolics.com -Steroids at http://www.pharmanabolics.com
