Does WASCE have a TransactionManager Lookup class ?
hi, i was trying to use transactions in WASCE ,but could not locate a TransactionManager lookup class .How do we specify how Hibernate should obtain a reference to the TransactionManager class ? regards Aditya Gupta
[jira] Updated: (GERONIMO-1293) Provide tomcat statistics
[ http://issues.apache.org/jira/browse/GERONIMO-1293?page=all ] anita kulshreshtha updated GERONIMO-1293: - Attachment: project.patch project.xml for implementation of 2. Provide tomcat statistics - Key: GERONIMO-1293 URL: http://issues.apache.org/jira/browse/GERONIMO-1293 Project: Geronimo Type: New Feature Components: Tomcat Versions: 1.0-M5 Environment: All environments Reporter: anita kulshreshtha Priority: Minor Fix For: 1.1 Attachments: TomcatWebAppContext.patch, geronimo-stats-1.0-SNAPSHOT.war, geronimo-stats-1.0-SNAPSHOT.war, project.patch, stats.zip, stats.zip Provide following statistics for tomcat : 1. Per Host/Container - a. Initially provide the following per connector statistics for each connector - Cummulative statistics about all request handled by this connector since the stat were turned on. b. If time (before 1.0 release) permits, use 'a' to generate (rename/compute) statistics similar to the ones provided by Jetty 2. Per application - a.. processingTime : The cumulative processing times of all servlets in this StandardContext b. startTime - The time this context was started. c. startupTime - The time (in milliseconds) it took to start this context. d.. tldScanTime() - Later add session statistics and jsp statistics. 3. Per Servlet - Explore using statistics from RequestInfo to provide statistics for a servlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Apache mini Geronimo (mini-G)
Hello All, Aaron Mulder wrote: In truth, I think we can go further in allowing for a mini-Geronimo. For example, right now IIRC the core J2EE configuration contains OpenEJB, and we could probably break out OpenEJB into a separate configuration to let you easily configure a server without it. I think I've been convinced that more/smaller configurations is the way to go, though we haven't figured out for sure how granular they should get. I've been conducting technical investigation of Geronimo by the direction from a superior official, and I am referring to the document which you are writing very much. Thank you for a great work. btw, what mentioned above are very interesting for me. I read many interviews and technical articles, and I found that the same thing is described at the some of them. Are there any concrete plans? Regards, -- Daisuke Kameda mailto:[EMAIL PROTECTED] Japan KDE Users' Group: President mailto:[EMAIL PROTECTED] http://www.kde.gr.jp/~daisuke/ immodule for Qt Project: Project Leader http://www.freedesktop.org/wiki/Software_2fimmodule_2dqt
Re: [jira] Commented: (GERONIMODEVTOOLS-26) Eclipse plugin build will always miss geronimo-jetty-j2ee-*.zip in the local maven repo
Strange. I have no idea. I just tried on windows, and the scenario
worked. If the zip is in the local repo, it skipped the remote
download. When I deleted the zip from the local repo and reran, it
pulled it down.
- sachin
On Dec 21, 2005, at 10:39 PM, Bill Stoddard wrote:
Sachin Patel (JIRA) wrote:
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-26?
page=comments#action_12361088 ] Sachin Patel commented on
GERONIMODEVTOOLS-26:
--
This is incorrect. The current syntax is correct as is. If the
zip is not available in the local repo, it will pull it down from
cvs.apache.org
j:if test=${zip.present != 'true'}
Yikes, after spending a bit of time with google I agree the
original syntax is correct, but it's not producing the desired result.
Here is the original maven goal with an ant:echo for instrumentation.
goal name=getzip
ant:property name=geronimo.zip value=geronimo-jetty-j2ee-$
{geronimo.version}.zip/
ant:available file=${maven.repo.local}/geronimo/distributions/
${geronimo.zip} property=zip.present/
ant:echozip.present is ${zip.present}/ant:echo
j:if test=${zip.present != 'true'}
ant:mkdir dir=${maven.repo.local}/geronimo/
distributions//
ant:get src=http://cvs.apache.org/repository/geronimo/
distributions/${geronimo.zip} dest=${maven.repo.local}/geronimo/
distributions/${geronimo.zip}/
/j:if
ant:mkdir dir=${maven.build.dest}/zips/
copy file=${maven.repo.local}/geronimo/distributions/$
{geronimo.zip} todir=${maven.build.dest}/zips/
/goal
Here is the resulting build failure:
C:\home\apache\devtools\modules\eclipse-plugin\plugins
\org.apache.geronimo.j2ee.server.v1maven
maven
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
build:start:
default:
java:prepare-filesystem:
java:compile:
[echo] Compiling to C:\home\apache\devtools\modules\eclipse-
plugin\plugins\org.apache.geronimo.j2ee.server.v1/target/classes
[echo] No java source files to compile.
java:jar-resources:
getzip:
[echo] zip.present is true=== geronimo-
jetty-j2ee-1.0.zip is in my local repo
[get] Getting: http://cvs.apache.org/repository/geronimo/
distributions/geronimo-jetty-j2ee-1.0.zip
[get] Error opening connection java.io.IOException
[get] Error opening connection java.io.IOException
[get] Error opening connection java.io.IOException
[get] Can't get http://cvs.apache.org/repository/geronimo/
distributions/geronimo-jetty-j2ee-1.0.zip to C:\Documents and
Settings\Administrator\.maven\repository\geronimo\distributions
\geronimo-jetty-j2ee-1.0.zip === So why did we take the branch to
download the zip?
BUILD FAILED
File.. C:\home\apache\devtools\modules\eclipse-plugin\plugins
\org.apache.geronimo.j2ee.server.v1\maven.xml
Element... ant:get
Line.. 34
Column 164
Can't get http://cvs.apache.org/repository/geronimo/distributions/
geronimo-jetty-j2ee-1.0.zip to C:\Documents and Settings
\Administrator\.maven\repository\geronimo\distributions\geronimo-
jetty-j2ee-1.0.zip
Total time: 3 seconds
Finished at: Wed Dec 21 22:17:45 EST 2005
If I force maven to bypass the download of geronimo-jetty-
j2ee-1.0.zip, my plugin build completes.
What am I missing??
Bill
Re: console build error
Ken, the error you are seeing is strange because I see where maven downloads the correct version of ant: +| Executing default Geronimo :: Console :: Portal Framework| Memory: 38M/58M+Attempting to download ant-1.6.5.jar.912K downloaded But then fails to precompile the JSPs because one of the classes in that jar is not found: war:install:preCompile:[echo] Pre-compiling JSPs from/root/geronimo1.0/applications/console-framework/src/webapp to /root/geronimo1.0/applications/console-framework/target/geronimo-console-framework/WEB-INF/work.[java] Exception in thread main java.lang.NoClassDefFoundError:org/apache/tools/ant/util/FileUtils I tried to recreate the error by removing ant-1.6.5.jar from my local maven repository but, as expected, maven downloaded the dependent jar and successfully compiled the JSPs again. However, I noticed in doing so that the size of ant-1.6.5.jar I downloaded was 1009K instead of the size that you downloaded 912K. So I suspect that you may have a corrupt version of ant-1.6.5.jar in your repository that you may want to redownload. Best wishes, Paul
Re: Apache mini Geronimo (mini-G)
I guesssuch an assembly/configuration could bephrased as Apache Geronimo *Personal Edition*...just another indication that s/w is getting more and more personalised and the user can take a call on thebits and pieces of the s/w he wants to live with. /Bharath
Just an Idea
Please see this link below link:http://www.theserverside.com/news/thread.tss?thread_id=38144
Re: generated source added to repo?
changes committed.
On Dec 22, 2005, at 11:35 AM, Bill Dudney wrote:
Hey Hiram,
M src/main/java/org/activemq/selector/
SelectorParserTokenManager.java
M src/main/java/org/activemq/selector/SelectorParser.java
Seems that the javacc version used in m1 and m2 are different and
they generate different parsers. Once we check in the changed
source files, svn should not mark these as being changed anymore.
makes sense - you should be able to run mvn install and get this
change and can then check it in, or I'd be happy to post a patch.
1) exclude the src/main/java/org/activemq/selector directory from
svn with svn:ignore and continue to generate code into that
directory (not the maven way but it works)
2) patch the pom and remove the outputDirectory element, have the
src generated into the target directory (more the maven way) - if
we do this the selector directory should be deleted from svn
because it causes duplicate class compile errors.
There is also a small problem with the sourceDirectory element.
It works fine when the build is run from the activemq-core
directory but does not work from the top level build (i.e. in the
activemq directory). To fix that we need to add ${basedir} to the
element like
sourceDirectory${basedir}/src/main/grammar/
sourceDirectory
I think this is the easy and simple way to do it for now. Once
totally move off m1, re can revisit this.
cool, do you want a patch for that?
TTFN,
Bill Dudney
MyFaces - myfaces.apache.org
Wadi - incubator.apache.org/wadi
Re: [jira] Commented: (GERONIMODEVTOOLS-26) Eclipse plugin build will always miss geronimo-jetty-j2ee-*.zip in the local maven repo
Sachin Patel wrote: Strange. I have no idea. I just tried on windows, and the scenario worked. If the zip is in the local repo, it skipped the remote download. When I deleted the zip from the local repo and reran, it pulled it down. - sachin Thanks for trying it Sachin. It's very odd. I'll put together a simple test case to see if I can isolate the failure. Will let you know if I find anything interesting. Bill
Geronimo Installation Document Section
Hi, I am starting on the Installation section of the docs - I have been running around like a maniac doing stuff (mostly holiday things) - so I am a bit slow to produce. But I am setting aside some time each day to contribute more and more to the docs. If you start to see me go off base - please feel free to call me out :-D Also - is the preference to complete a section and then update? I started and updated but it is not complete. Thanks, Jason __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com
Re: Java Adventure Builder Reference application. Issues with the tomcat distribution, issues with the javamail implementation
I got at few conflicts when updating. First thing tomorrow I will resolve them, check that the application deploys and seems to be working on my system, then I'll attach a new patch. I'm trying to make the status mails work. I'll look further into that tomorrow; hopefully my cry for help on the user list will help me decide what to do next. Jakob Hi Jacek Using the 1.0 prerelease from http://people.apache.org/~hogstrom/geronimo-1.0/geronimo-tomcat-j2ee-1.0-20051219.zip, I get ClassNotFoundException: org.apache.jasper.servlet.JspServlet when booting the server using the tomcat build. It seems the error occurs for every webservice-enabled bean in the application. I've included the stacktrace from the log for one of the beans. Do you - or anyone else who might be reading this - have any idea what is going on? If I exchange the artifactId for the unpackServer goal to use the geronimo-jetty-j2ee distribution, everything seems to work all right; no errors on startup, and the orders I submit seems to be processed all the way to 'completed' state. I guess I'm just experiencing problems with the tomcat distributions created so far, but we still have to sort this out when the 1.0 enters final. I continue looking into the problems sending mail; I think I have tracked the problem down to an anomaly in the Geronimo implementation of javax.mail.internet.MimeMessage from the geronimo-javamail_1.3.1_spec-1.0.jar. The behaviour I'm seeing is that To receipients set on a MimeMessage msg using msg.setRecipients isn't returned by msg.getAllReceipients(). Do you know if it's documented somewhere how to get hold of the spec sources and build them? I can't seem to find them anywhere in the normal source checkout I have got by following the Wiki instructions on http://wiki.apache.org/geronimo/GettingSourceCode. I can find the source for the specs at http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-spec-javamail/src/, and it seems like it could be the source for the geronimo-javamail_1.3.1_spec-1.0.jar, but I guess I have no way to be sure. Also, do you (or anyone else) know if newer version of the javamail spec exists. I searched the JIRA for an issue like the one I'm experiencing, but couldn't seem to find one. I think I might have a patch for the problem; nevertheless, I wouldn't want to waste time trying to solve a problem which might be fixed in a newer version. That was a lot of questions from me; I hope someone will take the time to answer some of them - that would bring us a little nearer the end of this, I think. Jakob 19:37:34,113 INFO [ContextConfig] Missing application web.xml, using defaults only StandardEngine[Geronimo].StandardHost[localhost].StandardContext[/webservice/WebServiceBroker] 19:37:34,193 ERROR [[/webservice/WebServiceBroker]] Error loading WebappClassLoader delegate: true repositories: -- Parent Classloader: [org.apache.geronimo.kernel.config.MultiParentClassLoader id=org/apache/geronimo/OPC1.0.3] org.apache.jasper.servlet.JspServlet java.lang.ClassNotFoundException: org.apache.jasper.servlet.JspServlet at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1338) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1187) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1027) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3880) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4141) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.geronimo.tomcat.TomcatContainer.addWebService(TomcatContainer.java:337) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.webservices.SoapHandler$$EnhancerByCGLIB$$4f1143be.addWebService(generated) at org.openejb.server.axis.WSContainer.init(WSContainer.java:98) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
[jira] Updated: (GERONIMO-1260) simplify construction of the combined deployment plan: deployment plan template and preprocessor
[ http://issues.apache.org/jira/browse/GERONIMO-1260?page=all ]
simon godik updated GERONIMO-1260:
--
Attachment: geronimo-packaging-plugin-1260.patch
this patch enables alt-dd element replacement in the deployment plan
to enable alt-dd processing set geronimo.packaging.altdd.enable=true in the
project.properties file
search path for the replacement plans is defined by the
geronimo.packaging.altdd.searchPath property wich is set to
${geronimo.packaging.srcDir} by default
you can exclude alt-dd elements from substitution by defining
geronimo.packaging.altdd.excludePatterns property which by default excludes
meta-inf dir
(see plugin.properties)
alt-dd processing is recursive
alt-dd element is substituted with a plan, so you can insert alt-dd elements in
the plan even if schema does not allow it
simplify construction of the combined deployment plan: deployment plan
template and preprocessor
Key: GERONIMO-1260
URL: http://issues.apache.org/jira/browse/GERONIMO-1260
Project: Geronimo
Type: New Feature
Components: deployment
Versions: 1.0-M5
Reporter: simon godik
Priority: Minor
Fix For: 1.1
Attachments: geronimo-packaging-plugin-1260.patch
To simplify construction and maintainance of the combined deployment plan
create deployment plan template and preprocess it to create combined
deployment plan from individual plans
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Geronimo 1.0 Release Candidate 20051222 - Available for Download and Review
I'm sending this on behalf of Matt Hogstrom, since his emails to the list keep getting rejected by the Apache spam filter. -dain -- All, We have some excellent news from the 1.0 release camp. We have incorporated all relevant feedback for the Geronimo 1.0 release that has come in over the past two weeks and have successfully created a build that passes all CTS tests and is likely our 1.0 Release. The releases are available at http://people.apache.org/~hogstrom/ geronimo-1.0/ and the files should be self explanatory but here is the list just in case. Unix Version geronimo-jetty-j2ee-1.0-20051222.tar.gz geronimo-tomcat-j2ee-1.0-20051222.tar.gz Windows Version geronimo-jetty-j2ee-1.0-20051222.zip geronimo-tomcat-j2ee-1.0-20051222.zip We will be monitoring the dev and user lists and will track any issues seen by users of the server. At this point there are many items that are queueing up for Geronimo that we chose to defer in the 1.0 release like the installer, better scripting, improved usability. Everyone on the team has lots of good ideas but to wait for all of them to gel would mean an additional wait for the server to made available in a release form. Please take some time to download and test the server. Install your favorite applications and provide your valued feedback. I'll send periodic updates to keep people up to date on how were progressing with this candidate. Merry Christmas, Happy Holidays, Happy Kwanzaa, Happy Hanukkah or whatever greeting offends you the least; enjoy your time off. Cheers, Matt
[VOTE] Change ServiceMix version to 3.0-SNAPSHOT
As we have to change the package names to org.apache.servicemix, i propose that we change the version number of ServiceMix to 3.0 to reflect this, and also the fact that we are focusing on full jbi compliance for both the container and components. [ ] +1 Change version to 3.0-SNAPSHOT [ ] -1 Keep 2.1 version number (provide specific comments) Cheers, Guillaume Nodet
[jira] Created: (GERONIMO-1399) NPE when trying to publish a simple app via eclipse plugin
NPE when trying to publish a simple app via eclipse plugin -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: eclipse-plugin Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1400) modularize daytrader deployment plan
modularize daytrader deployment plan Key: GERONIMO-1400 URL: http://issues.apache.org/jira/browse/GERONIMO-1400 Project: Geronimo Type: New Feature Components: deployment Versions: 1.1 Environment: any platform Reporter: simon godik Priority: Minor use geronimo patch 1260 to modularize deployment plan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1400) modularize daytrader deployment plan
[ http://issues.apache.org/jira/browse/GERONIMO-1400?page=all ] simon godik updated GERONIMO-1400: -- Attachment: daytrader-jetty.patch daytrader-tomcat.patch patches for tomcat and jetty included modularize daytrader deployment plan Key: GERONIMO-1400 URL: http://issues.apache.org/jira/browse/GERONIMO-1400 Project: Geronimo Type: New Feature Components: deployment Versions: 1.1 Environment: any platform Reporter: simon godik Priority: Minor Attachments: daytrader-jetty.patch, daytrader-tomcat.patch use geronimo patch 1260 to modularize deployment plan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
alt-dd packaging plugin patch 1260
David J, please review and apply patch 1260
this is patch for packaging plugin
this patch enables alt-dd element replacement in the deployment plan
to enable alt-dd processing set geronimo.packaging.altdd.enable=true in the
project.properties file
search path for the replacement plans is defined by the
geronimo.packaging.altdd.searchPath property wich is set to
${geronimo.packaging.srcDir} by default
you can exclude alt-dd elements from substitution by defining
geronimo.packaging.altdd.excludePatterns property which by default excludes
meta-inf dir
(see plugin.properties)
alt-dd processing is recursive
alt-dd element is substituted with a plan, so you can insert alt-dd elements in
the plan even if schema does not allow it
Simon
[jira] Commented: (GERONIMO-1164) Java Adventure Builder Reference application deployment
[
http://issues.apache.org/jira/browse/GERONIMO-1164?page=comments#action_12361151
]
Jacek Laskowski commented on GERONIMO-1164:
---
Patch applied (with some minor changes of mine). Thanks Jakob! Keep them coming!
The waitForStarted failed because there was
geronimo/j2ee-deployer/${geronimo-version}/car instead of
geronimo/j2ee-deployer/${geronimo_version}/car (note the dash in
geronimo_version)
I think you don't have to build the server yourself but specify necessary
packages (jars, cars and zips) as project dependencies so that everything is
downloaded on demand.
I'll describe the new process of building the server on Wiki. It boils down to
executing the following steps:
maven m:co
rm -rf ~/.maven/plugins ~/.maven/cache/geronimo*
~/.maven/repository/geronimo/plugins
maven m:clean m:clean-repo new
I had to run it several times before I could finally build it successfully, so
don't be worried the first time you've seen BUILD FAILED ;)
I haven't figured out how to enable mail gbean yet.
The last but not least, we need to think of a better naming solution so that
ab:start will in fact start AB and could be used on its own.
$ svn ci .
Sendingadventurebuilder/maven.xml
Sendingadventurebuilder/src/plan/activitysupplier1.0.3.ear-plan.xml
Sendingadventurebuilder/src/plan/adventure1.0.1-db-ra-plan.xml
Sendingadventurebuilder/src/plan/adventure1.0.1-security-plan.xml
Sendingadventurebuilder/src/plan/adventure1.0.3-jms-ra-plan.xml
Sendingadventurebuilder/src/plan/airlinesupplier1.0.3.ear-plan.xml
Sendingadventurebuilder/src/plan/bank1.0.3.ear-plan.xml
Sendingadventurebuilder/src/plan/consumerwebsite1.0.1.ear-plan.xml
Sendingadventurebuilder/src/plan/lodgingsupplier1.0.3.ear-plan.xml
Sendingadventurebuilder/src/plan/opc1.0.3.ear-plan.xml
Sendingadventurebuilder/src/sql/ab1.0.1.sql
Transmitting file data ...
Committed revision 358649.
Java Adventure Builder Reference application deployment
---
Key: GERONIMO-1164
URL: http://issues.apache.org/jira/browse/GERONIMO-1164
Project: Geronimo
Type: Task
Components: sample apps
Reporter: Jacek Laskowski
Assignee: Jacek Laskowski
Fix For: 1.1
Attachments: adventure1.0.3-built-with-jdk-1.4.2.zip,
adventurebuilder1.0.3-geronimo-deployment-plans.zip,
jrf-patch-partially-20051219-2.patch, jrf-patch-partially-20051219-3.patch,
jrf-patch-partially-20051219.patch, jrf-patch-partially-20051220.patch,
jrf-patch-partially-20051222.patch
It's finally the time to see Java Adventure Builder Reference application
running in Geronimo. This task is to track the progress. Instruction
available at http://wiki.apache.org/geronimo/AdventureBuilder
This is a sample application brought to you by the Java BluePrints program at
Sun Microsystems, Inc.
This sample application demonstrates how to use the capabilities of the J2EE
1.4 platform to develop robust, scalable, portable, and maintainable
e-business applications and Webservices. It comes with full source code and
documentation, so you can experiment with the J2EE technologies and learn how
to use them effectively to build your own enterprise solutions. This
application also showcases how to use the Webservices technologies in the
J2EE 1.4 platform.
This version of Adventure Builder Reference application is certified by
Application Verification Kit(AVK) for the portablity across J2EE compatible
application servers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Jetspeed 2 - Geronimo security integration (from apachecon)
At Apachecon some Jetspeed and Geronimo committers got together and discussed Jetspeed 2 - Geronimo security integration a bit. Here's what I remember: please chime in if you remember more/differently. People: David Sean Taylor, Ate Douma, Randy Watler, Alan Cabrera, David Jencks and ??? 1. Jetspeed in tomcat is currently creating a separate jetspeed subject because it isn't clear how to get the JAAS subject that tomcat creates for use in jetspeed security. In geronimo we create a special Principal that has a reference to the Subject (JAASTomcatPrincipal). Probably Jetspeed can use the same idea in Tomcat to get the JAAS subject and avoid the fake login. 2. IIUC correctly jetspeed security currently requires a login module to use specific principal classes, and there is a direct mapping between instances of these classes and jetspeed portal/portlet permissions. This is not very j2ee-like, at least as geronimo interprets it :-) In particular it seems excessively restrictive to require the use of specific principal classes. On the other hand jetspeed implements an on-the-fly permissions-changing facility that will take some work to fit into a jacc-like structure. Here is one way to proceed that I tried to explain and I think got general agreement that it deserved at least further consideration: a. In analogy to the role-permissions mapping specified for web apps and ejbs, set up a role-to-jetspeed-portlet-permissions mapping in a (presumably xml) jetspeed specific deployment descriptor. With a suitable deployer this can be fed into a jacc-compliant app server: in geronimo this can be fed into PolicyConfigurationGeneric. In j2ee such a mapping is static, part of the original deployment descriptor, and cannot be changed without redeploying the app. I'm inclined to think that such a restriction may also work for jetspeed but don't have enough info for my opinion to count for much. I think implementing this as a first step would be a good idea. b. Use the existing geronimo specific role-principal mapping to connect the principals created by an arbitrary login module with the roles set up in (a). This would result in jetspeed security being integrated into the existing geronimo jacc security framework. However, it would not immediately result in being able to change permissions without redeploying the application. c. Investigate how to make this more dynamic. One possibility is to simply use the jacc facilities, which involve opening the policy configuration (at which point it is taken out of service and no requests can get through), modifying it, and committing the changes (at which time it is put back into service and the new policy rules are in force). It is not entirely clear to me if the requests made while the configuration is open can be made to wait or if they must be refused. I do think that some kind of transactional change mechanism is needed so that many changes can be made in one operation. If anyone finds what I am talking about unclear please ask questions, I will be happy to try to explain in more detail. Many thanks, david jencks
Re: Java Adventure Builder Reference application. Issues with the tomcat distribution, issues with the javamail implementation
Jakob Færch (Trifork) wrote: Hi Jacek Hi Jakob, Using the 1.0 prerelease from http://people.apache.org/~hogstrom/geronimo-1.0/geronimo-tomcat-j2ee-1.0-20051219.zip, I get ClassNotFoundException: org.apache.jasper.servlet.JspServlet when booting the server using the tomcat build. It seems the error occurs for every webservice-enabled bean in the application. I've noticed it too once I applied your patch and I don't have any ideas yet how to sort it out. I've included the stacktrace from the log for one of the beans. Do you - or anyone else who might be reading this - have any idea what is going on? Nope. If I exchange the artifactId for the unpackServer goal to use the geronimo-jetty-j2ee distribution, everything seems to work all right; no errors on startup, and the orders I submit seems to be processed all the way to 'completed' state. Whow, that's a very interesting thing. It makes us sure that it's not the AB configurations but Tomcat may exhibit some features. I guess I'm just experiencing problems with the tomcat distributions created so far, but we still have to sort this out when the 1.0 enters final. Absolutely, but the first things first. We need to make it run on one or another container and then crack down remaining issues. It may be that the issues are because of broken configurations we use. I continue looking into the problems sending mail; I think I have tracked the problem down to an anomaly in the Geronimo implementation of javax.mail.internet.MimeMessage from the geronimo-javamail_1.3.1_spec-1.0.jar. Awesome. Keep digging up. It seems very promising. Do you know if it's documented somewhere how to get hold of the spec sources and build them? Sure. Download the sources from the repo and build them using the following procedure: maven m:co rm -rf ~/.maven/plugins ~/.maven/cache/geronimo* ~/.maven/repository/geronimo/plugins maven m:clean m:clean-repo new It worked for me, but some first tries finished with errors. Don't be worried and keep trying ;) I can't seem to find them anywhere in the normal source checkout I have got by following the Wiki instructions on http://wiki.apache.org/geronimo/GettingSourceCode. Get them from http://svn.apache.org/viewcvs.cgi/geronimo/specs/trunk/ I can find the source for the specs at http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-spec-javamail/src/, and it seems like it could be the source for the geronimo-javamail_1.3.1_spec-1.0.jar, but I guess I have no way to be sure. See the above url. Also, do you (or anyone else) know if newer version of the javamail spec exists. I searched the JIRA for an issue like the one I'm experiencing, but couldn't seem to find one. I think I might have a patch for the problem; nevertheless, I wouldn't want to waste time trying to solve a problem which might be fixed in a newer version. Remember that you'll need Maven 2 to build the specs from sources. That was a lot of questions from me; I hope someone will take the time to answer some of them - that would bring us a little nearer the end of this, I think. No problem. You're doing a great job and I'm doing all my best to keep your pace. Jakob Jacek
Re: Java Adventure Builder Reference application. Issues with the tomcat distribution, issues with the javamail implementation
On Dec 22, 2005, at 3:16 PM, Jacek Laskowski wrote: Jakob Færch (Trifork) wrote: Hi Jacek Hi Jakob, Using the 1.0 prerelease from http://people.apache.org/~hogstrom/ geronimo-1.0/geronimo-tomcat-j2ee-1.0-20051219.zip, I get ClassNotFoundException: org.apache.jasper.servlet.JspServlet when booting the server using the tomcat build. It seems the error occurs for every webservice-enabled bean in the application. I've noticed it too once I applied your patch and I don't have any ideas yet how to sort it out. I've included the stacktrace from the log for one of the beans. Do you - or anyone else who might be reading this - have any idea what is going on? Nope. If I exchange the artifactId for the unpackServer goal to use the geronimo-jetty-j2ee distribution, everything seems to work all right; no errors on startup, and the orders I submit seems to be processed all the way to 'completed' state. Whow, that's a very interesting thing. It makes us sure that it's not the AB configurations but Tomcat may exhibit some features. I guess I'm just experiencing problems with the tomcat distributions created so far, but we still have to sort this out when the 1.0 enters final. Absolutely, but the first things first. We need to make it run on one or another container and then crack down remaining issues. It may be that the issues are because of broken configurations we use. I continue looking into the problems sending mail; I think I have tracked the problem down to an anomaly in the Geronimo implementation of javax.mail.internet.MimeMessage from the geronimo-javamail_1.3.1_spec-1.0.jar. Awesome. Keep digging up. It seems very promising. Do you know if it's documented somewhere how to get hold of the spec sources and build them? Sure. Download the sources from the repo and build them using the following procedure: maven m:co rm -rf ~/.maven/plugins ~/.maven/cache/geronimo* ~/.maven/ repository/geronimo/plugins maven m:clean m:clean-repo new It worked for me, but some first tries finished with errors. Don't be worried and keep trying ;) This seems to be the geronimo build procedure rather than the geronimo-specs build procedure I can't seem to find them anywhere in the normal source checkout I have got by following the Wiki instructions on http:// wiki.apache.org/geronimo/GettingSourceCode. Get them from http://svn.apache.org/viewcvs.cgi/geronimo/specs/trunk/ Well, the actual 1.0 specs should be from https://svn.apache.org/viewcvs.cgi/geronimo/specs/tags/1_0/ although I think there are no differences at this point. To build (with maven 2) I think you just type mvn Hope this is not too nit-picky and is helpful thanks david jencks I can find the source for the specs at http://svn.apache.org/repos/ asf/geronimo/specs/trunk/geronimo-spec-javamail/src/, and it seems like it could be the source for the geronimo- javamail_1.3.1_spec-1.0.jar, but I guess I have no way to be sure. See the above url. Also, do you (or anyone else) know if newer version of the javamail spec exists. I searched the JIRA for an issue like the one I'm experiencing, but couldn't seem to find one. I think I might have a patch for the problem; nevertheless, I wouldn't want to waste time trying to solve a problem which might be fixed in a newer version. Remember that you'll need Maven 2 to build the specs from sources. That was a lot of questions from me; I hope someone will take the time to answer some of them - that would bring us a little nearer the end of this, I think. No problem. You're doing a great job and I'm doing all my best to keep your pace. Jakob Jacek
At last Java Adventure Builder finished with Checkout Complete
Hi, Finally I could figure out how to configure MailGBean and see Checkout Complete for the first time! Although there're some errors while starting the web services the checkout completed successfully. Checkout Complete Thank you for planning your adventure with the Adventure Builder Web Application. Your order id is AB-j2ee-1135296532375. Please come again. If you want to give it a try, make sure you're working with the latest version (at least r358662). Dobrej nocy! Jacek
[jira] Updated: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ] Sachin Patel updated GERONIMO-1399: --- Component: deployment (was: eclipse-plugin) Summary: DeploymentFactory-Implementation-Class property missing from deployer.jar manifest (was: NPE when trying to publish a simple app via eclipse plugin) Fix Version: 1.0 Moving to component deployment. The problem is that the manfiest in deployer.jar no longer contains the J2EE-DeploymentFactory-Implementation-Class property. DeploymentFactory-Implementation-Class property missing from deployer.jar manifest -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: deployment Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun Fix For: 1.0 On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jetspeed 2 - Geronimo security integration (from apachecon)
On 12/23/05, David Jencks [EMAIL PROTECTED] wrote: At Apachecon some Jetspeed and Geronimo committers got together anddiscussed Jetspeed 2 - Geronimo security integration a bit.Here'swhat I remember: please chime in if you remember more/differently.People:David Sean Taylor, Ate Douma, Randy Watler, Alan Cabrera, David Jencks and ???1. Jetspeed in tomcat is currently creating a separate jetspeedsubject because it isn't clear how to get the JAAS subject thattomcat creates for use in jetspeed security.In geronimo we create a special Principal that has a reference to the Subject(JAASTomcatPrincipal).Probably Jetspeed can use the same idea inTomcat to get the JAAS subject and avoid the fake login. This could solve JS2-238, great! 2. IIUC correctly jetspeed security currently requires a login moduleto use specific principal classes, and there is a direct mappingbetween instances of these classes and jetspeed portal/portletpermissions.This is not very j2ee-like, at least as geronimo interprets it :-)In particular it seems excessively restrictive torequire the use of specific principal classes.On the other handjetspeed implements an on-the-fly permissions-changing facility thatwill take some work to fit into a jacc-like structure.Here is one way to proceed that I tried to explain and I think got generalagreement that it deserved at least further consideration:a. In analogy to the role-permissions mapping specified for web appsand ejbs, set up a role-to-jetspeed-portlet-permissions mapping in a (presumably xml) jetspeed specific deployment descriptor.With asuitable deployer this can be fed into a jacc-compliant app server:in geronimo this can be fed into PolicyConfigurationGeneric.In j2eesuch a mapping is static, part of the original deployment descriptor, and cannot be changed without redeploying the app.I'm inclined tothink that such a restriction may also work for jetspeed but don'thave enough info for my opinion to count for much.I thinkimplementing this as a first step would be a good idea. b. Use the existing geronimo specific role-principal mapping toconnect the principals created by an arbitrary login module with theroles set up in (a).This would result in jetspeed security beingintegrated into the existing geronimo jacc security framework. However, it would not immediately result in being able to changepermissions without redeploying the application.c. Investigate how to make this more dynamic.One possibility is tosimply use the jacc facilities, which involve opening the policy configuration (at which point it is taken out of service and norequests can get through), modifying it, and committing the changes(at which time it is put back into service and the new policy rulesare in force).It is not entirely clear to me if the requests made while the configuration is open can be made to wait or if they mustbe refused.I do think that some kind of transactional changemechanism is needed so that many changes can be made in one operation. I am wondering when will 2-a come true? I'm eager to see that ASAP. If anyone finds what I am talking about unclear please ask questions,I will be happy to try to explain in more detail.Many thanks,david jencks
[jira] Created: (GERONIMO-1401) The latest Build process
The latest Build process Key: GERONIMO-1401 URL: http://issues.apache.org/jira/browse/GERONIMO-1401 Project: Geronimo Type: Improvement Components: documentation Versions: 1.0-M5 Environment: All Reporter: anita kulshreshtha Attachments: BUILDING.patch The Building page in wiki points to this document. The changes reflects the new build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1401) The latest Build process
[ http://issues.apache.org/jira/browse/GERONIMO-1401?page=all ] anita kulshreshtha updated GERONIMO-1401: - Attachment: BUILDING.patch The latest Build process Key: GERONIMO-1401 URL: http://issues.apache.org/jira/browse/GERONIMO-1401 Project: Geronimo Type: Improvement Components: documentation Versions: 1.0-M5 Environment: All Reporter: anita kulshreshtha Attachments: BUILDING.patch The Building page in wiki points to this document. The changes reflects the new build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: console build error
Thanks, Paul, re-download and re-build is success. Does the maven check the md5sum after a downloading? On 12/23/05, Paul McMahan [EMAIL PROTECTED] wrote: Ken, the error you are seeing is strange because I see where maven downloads the correct version of ant: + | Executing default Geronimo :: Console :: Portal Framework | Memory: 38M/58M + Attempting to download ant-1.6.5.jar. 912K downloaded But then fails to precompile the JSPs because one of the classes in that jar is not found: war:install: preCompile: [echo] Pre-compiling JSPs from /root/geronimo1.0/applications/console-framework/src/webapp to /root/geronimo1.0/applications/console-framework/target/geronimo-console-framework/WEB-INF/work. [java] Exception in thread main java.lang.NoClassDefFoundError: org/apache/tools/ant/util/FileUtils I tried to recreate the error by removing ant-1.6.5.jar from my local maven repository but, as expected, maven downloaded the dependent jar and successfully compiled the JSPs again. However, I noticed in doing so that the size of ant-1.6.5.jar I downloaded was 1009K instead of the size that you downloaded 912K. So I suspect that you may have a corrupt version of ant-1.6.5.jar in your repository that you may want to redownload. Best wishes, Paul -- perl -e 'print unpack(u,62V5N\FME;G\!EFQ`9VUA:6PN8V]M\[EMAIL PROTECTED] )'
[jira] Commented: (GERONIMO-1401) The latest Build process
[ http://issues.apache.org/jira/browse/GERONIMO-1401?page=comments#action_12361162 ] Sachin Patel commented on GERONIMO-1401: Anita, The wiki is open for editing by members of the community. Feel free to modify it. A patch is not necessary. The latest Build process Key: GERONIMO-1401 URL: http://issues.apache.org/jira/browse/GERONIMO-1401 Project: Geronimo Type: Improvement Components: documentation Versions: 1.0-M5 Environment: All Reporter: anita kulshreshtha Attachments: BUILDING.patch The Building page in wiki points to this document. The changes reflects the new build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1401) The latest Build process
[ http://issues.apache.org/jira/browse/GERONIMO-1401?page=comments#action_12361166 ] kenperl commented on GERONIMO-1401: --- In the patch around the last line, To stop the server use ctrl-C or an equivalent; a proper shutdown command will be made available in a future release. In fact, the shutdown command is already available in the 1.0 snapshot. The latest Build process Key: GERONIMO-1401 URL: http://issues.apache.org/jira/browse/GERONIMO-1401 Project: Geronimo Type: Improvement Components: documentation Versions: 1.0-M5 Environment: All Reporter: anita kulshreshtha Attachments: BUILDING.patch The Building page in wiki points to this document. The changes reflects the new build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
