RE: GBean for auto generation of primary key
--- Begin Message --- i think this can be refered to jira GERONUMO-1133 akshay From: Ranjan, Rakesh (Cognizant) [mailto:[EMAIL PROTECTED] Sent: Fri 12/16/2005 10:07 AM To: dev@geronimo.apache.org Subject: GBean for auto generation of primary key Hi all, I have a written a custom-generator GBean which implements org.tranql.pkgenerator.PrimaryKeyGenerator. This GBean is able to create automatically generated UUID primary key for unknown primary keys. It uses. the org.apache.axis components.uuid.FastUUIDGen class for generating the UUID primary key. As we know JBoss use a automatically generated UUID primary key for unknown primary keys. That's why we are able to deploy the adventure builder application successfully on JBoss. But it create problem when we deploy it in Geronimo. Using this GBean that issue can be resolved. I have tested it with a sample application . It is working perfectly. We can use this GBean in openejb-jar.xml as follows : - id geronimo.server:J2EEApplication=null,J2EEModule=geronimoKeyGenerator,J2EEServer=geronimo,j2eeType=GBean,name=UUIDGBean java.lang.String So, I hope adventure builder deployment issue will be resolved very soon. Thanks and Regard, Rakesh Ranjan This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com <>--- End Message --- This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com
Re: [VOTE] geronimo-1.0 (3rd try)
On 12/15/05, David Blevins <[EMAIL PROTECTED]> wrote:
> Alright, I repacked the binaries that Jeff created to workaround the
> gbean startup issue. I have the tck running on them now.
>
> Here are the binaries for review. Please be sure you delete the old
> ones from your system before downloading the new ones.
>
> http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/
>
> These versions of these programs where used to create the binaries:
>
>- tar (GNU tar) 1.15.1
>- Zip 2.3 (November 29th 1999)
>- OpenSSL 0.9.7f 22 Mar 2005
>- gpg (GnuPG) 1.4.1
>
>
> [ ] +1 Release these binaries provided they pass the J2EE TCK
I started up each bundle and went through a bunch of stuff manually
and it appears to be good.
+1
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: [VOTE] geronimo-1.0 (3rd try)
is this 1.0 or a RC? On Dec 15, 2005, at 3:33 PM, David Blevins wrote: Alright, I repacked the binaries that Jeff created to workaround the gbean startup issue. I have the tck running on them now. Here are the binaries for review. Please be sure you delete the old ones from your system before downloading the new ones. http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/ These versions of these programs where used to create the binaries: - tar (GNU tar) 1.15.1 - Zip 2.3 (November 29th 1999) - OpenSSL 0.9.7f 22 Mar 2005 - gpg (GnuPG) 1.4.1 [ ] +1 Release these binaries provided they pass the J2EE TCK [ ] -1 Veto the release (provide specific comments) Let's get this thing out the door! -David -- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
GBean for auto generation of primary key
Hi all, I have a written a custom-generator GBean which implements org.tranql.pkgenerator.PrimaryKeyGenerator. This GBean is able to create automatically generated UUID primary key for unknown primary keys. It uses. the org.apache.axis components.uuid.FastUUIDGen class for generating the UUID primary key. As we know JBoss use a automatically generated UUID primary key for unknown primary keys. That’s why we are able to deploy the adventure builder application successfully on JBoss. But it create problem when we deploy it in Geronimo. Using this GBean that issue can be resolved. I have tested it with a sample application . It is working perfectly. We can use this GBean in openejb-jar.xml as follows : - id geronimo.server:J2EEApplication=null,J2EEModule=geronimoKeyGenerator,J2EEServer=geronimo,j2eeType=GBean,name=UUIDGBean java.lang.String So, I hope adventure builder deployment issue will be resolved very soon. Thanks and Regard, Rakesh Ranjan This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com
Re: [VOTE] geronimo-1.0 (3rd try)
+1 from me. On 12/15/05, Jeff Genender <[EMAIL PROTECTED]> wrote: > +1...thanks for doing this David. > > David Blevins wrote: > > Alright, I repacked the binaries that Jeff created to workaround the > > gbean startup issue. I have the tck running on them now. > > > > Here are the binaries for review. Please be sure you delete the old ones > > from your system before downloading the new ones. > > > > http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/ > > > > These versions of these programs where used to create the binaries: > > > > - tar (GNU tar) 1.15.1 > > - Zip 2.3 (November 29th 1999) > > - OpenSSL 0.9.7f 22 Mar 2005 > > - gpg (GnuPG) 1.4.1 > > > > > > [ ] +1 Release these binaries provided they pass the J2EE TCK > > [ ] -1 Veto the release (provide specific comments) > > > > Let's get this thing out the door! > > > > -David > -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360553 ] Dave Colasurdo commented on GERONIMO-1372: -- I'm sorry to say that I'm still seeing this same intermittent exception on the proposed-final-3 build. :( It fails intermittently during startup.. Sometimes the first time, sometimes the third time.. sometimes the third and fourth time. It does not fail only once after a fresh install. In other words, it often fails on multiple subsequent startups. Can anyone else confirm? Environment is linux and tomcat. with JDK 1.4.2_10 > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > Attachments: geronimo.log > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53
Re: [VOTE] geronimo-1.0 (3rd try)
+1...thanks for doing this David. David Blevins wrote: > Alright, I repacked the binaries that Jeff created to workaround the > gbean startup issue. I have the tck running on them now. > > Here are the binaries for review. Please be sure you delete the old ones > from your system before downloading the new ones. > > http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/ > > These versions of these programs where used to create the binaries: > > - tar (GNU tar) 1.15.1 > - Zip 2.3 (November 29th 1999) > - OpenSSL 0.9.7f 22 Mar 2005 > - gpg (GnuPG) 1.4.1 > > > [ ] +1 Release these binaries provided they pass the J2EE TCK > [ ] -1 Veto the release (provide specific comments) > > Let's get this thing out the door! > > -David
Re: [VOTE] geronimo-1.0 (3rd try)
+1 On Dec 15, 2005, at 6:33 PM, David Blevins wrote: Alright, I repacked the binaries that Jeff created to workaround the gbean startup issue. I have the tck running on them now. Here are the binaries for review. Please be sure you delete the old ones from your system before downloading the new ones. http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/ These versions of these programs where used to create the binaries: - tar (GNU tar) 1.15.1 - Zip 2.3 (November 29th 1999) - OpenSSL 0.9.7f 22 Mar 2005 - gpg (GnuPG) 1.4.1 [ ] +1 Release these binaries provided they pass the J2EE TCK [ ] -1 Veto the release (provide specific comments) Let's get this thing out the door! -David - sachin
[VOTE] geronimo-1.0 (3rd try)
Alright, I repacked the binaries that Jeff created to workaround the gbean startup issue. I have the tck running on them now. Here are the binaries for review. Please be sure you delete the old ones from your system before downloading the new ones. http://people.apache.org/~dblevins/geronimo-1.0-proposed-final-3/ These versions of these programs where used to create the binaries: - tar (GNU tar) 1.15.1 - Zip 2.3 (November 29th 1999) - OpenSSL 0.9.7f 22 Mar 2005 - gpg (GnuPG) 1.4.1 [ ] +1 Release these binaries provided they pass the J2EE TCK [ ] -1 Veto the release (provide specific comments) Let's get this thing out the door! -David
Re: New binaries -- let's do this
Alright, i whipped up new binaries. Going to go for another vote. -David On Dec 15, 2005, at 12:44 PM, David Blevins wrote: Apparently, the startup race condition is still present, so we'll have to unpack, startup, shutdown, clean, repack and resign the binaries again. :( -David On Dec 15, 2005, at 11:56 AM, Jeff Genender wrote: Rainer, Those directories get created on server startup. Jeff Rainer Jung wrote: Hi Jeff, I just had a short look at the contents of the tomcat zip. A few comments, but I can not tell, which of these are actually problems. In general: a lot of the subdirs under geronimo-1.0/var do not exist any more: - directory geronimo-1.0/deploy/ does not exist any more (was empty previously) Tomcat stuff: - directory geronimo-1.0/var/catalina/ROOT/ does not exist any more (contained a simple root context previously) - directory geronimo-1.0/var/catalina/conf/ does not exist any more (contained a web.xml previously) - directories geronimo-1.0/var/catalina/logs and geronimo-1.0/var/catalina/work do not exist any more (empty previously) Derby stuff: - directory geronimo-1.0/var/derby/ does not exist any more (contained subdirs geronimo-1.0/var/derby/UddiDatabase/, geronimo-1.0/var/derby/DaytraderDatabase/ and geronimo-1.0/var/derby/SystemDatabase/ previously) ActiveMQ: - directory geronimo-1.0/var/activemq/ does not exist any more (contained subdir journal previously) Naming: - directory geronimo-1.0/var/ldap/ does not exist any more (contained subdir system previouly) Others: - directory geronimo-1.0/var/txlog/ does not exist any more (contained two files how1_[12].log previously) Jeff Genender wrote: Hi, I finally got Internet connectivity from the hotel in San Diego (it was down). I have built new binaries to be reviewed. This is not a vote...its a review...after folks have reviewed this, we can move this to a vote. I have put the binaries here: http://people.apache.org/~jgenender/geronimo/1.0/ Thanks to David Blevins for working with me yesterday to get this completed. Please download these and try them out...and please comment on any issues/changes/naming we need for these. Thanks, Jeff
Re: 1.0 release Candidate 2...some guidelines
I'm not a big fan of having archives where the zip or tar name doesn't match the inside of the archive or the version number (i.e. foo-1.0-123456.zip --> foo-1.0/). All our proposed binaries would extract to the exact same directory. If someone forgets to delete the old foo-1.0 directory before unpacking the newest proposed binary, who knows what kind of strange errors they will report. It might be a good idea, I'm just a little too burnt out to be excited about adding another step to our release process (i.e. renaming the files produced by maven then renaming them back when we make them official). -David On Dec 15, 2005, at 9:12 AM, Matt Hogstrom wrote: Good idea Paul...I like the date time string idea. Paul McMahan wrote: On 12/15/05, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Second, someone pointed out (I think it was Jacek) that we did not include a notation in the binary about what the release candidate was so that it is not confused with the final release. Before releasing another cut I would like the naming convention of the binary and the directories to be clearer as to what they contain otherwise this will get confusing. My suggestion is that the name be: geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of the release candidate (and we are now on number 2). The next set of images should follow this convention to ensure we are not confusing the users. I know these are release candidates and this isn't required but it would make me sleep better at night :) The directory that is actually contained in the zip will still be geronimo-1.0. Thoughts? Matt, including a notation in the filename seems like a good idea and could help prevent confusion. I've also seen projects use a date string instead of a release candidate number for this purpose. Using a date string is helpful since it makes it obvious when the image was created plus avoids publicizing how many unsuccessful attempts there have been (not saying that would be an issue in this case :o) Best wishes, Paul
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360539 ] Dave Colasurdo commented on GERONIMO-1372: -- Retried one more time and the exception during shutdown doesn't seem pertinent to the TradeEJB exception.. 1) ./geronimo.sh - worked fine CTL-C shutdown - worked fine 2) ./geronimo.sh - TradeEJB Exception > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > Attachments: geronimo.log > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) > at > org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) >
Re: SMTP Authentication
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cryptix seems to have an impl. I haven't looked at it. Regards, Alan Rick McGuire wrote, On 12/7/2005 9:45 AM: > Sasl is the challenge/response algorithm for simple server > authentication (Simple Authentication and Security Layer). The SMTP > spec on authentication defines everything in terms of SASL operations > (http://www.networksorcery.com/enp/rfc/rfc2554.txt). Even PLAIN and > LOGIN are SASL operations. The Java SASL API added in 5.0 provides a > nice extendable framework for SASL operations with support for a lot > more than the simple operations. > http://java.sun.com/j2se/1.5.0/docs/guide/security/sasl/sasl-refguide.html. > > Using the SASL APIs is very nice, as would allow Geronimo to support > almost anything a server would throw at as for free, as long it was a > mechanism supported by the security provider implementation. > Anyway, I've got code for LOGIN and PLAIN already written, and am almost > done with a CRAM-MD5 version. This sounds like it will be sufficient > for the short term. > > Rick > > Dain Sundstrom wrote: > >> From my experience, most servers and clients are just using LOGIN and >> PLAIN with TLS sometimes. I'm not very familiar with Sasl; can you >> explain how it fits into a mail client or server? >> >> Thanks, >> >> -dain >> >> On Dec 7, 2005, at 8:37 AM, Rick McGuire wrote: >> >>> I've looking at the issues of doing SMTP authentication, and after >>> reading the SMTP spec, starting coding up a solution using the Java >>> Sasl API, which was doing most of the heavy lifting for me. This >>> morning, however, I finally noticed the critical words in the Sasl >>> Javadoc"since Java 1.5". Since we're not in a position to >>> support Java 1.5 yet, that definitely tossed a speed bump in my path. >>> LOGIN and PLAIN authentication are pretty simple to do without Sasl, >>> and I believe I can also figure out how to do CRAM_MD5. Other forms >>> of authentication are probably a bit beyond my current experience >>> with crypto/security. How sophisticated do we need to be with >>> this? Are LOGIN and PLAIN sufficient (combined with TLS support)? >>> Note that this question also applies to the POP3 and IMAP >>> implementations, since they also use Sasl authentication mechanisms. >>> >>> Rick >> >> >> >> -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDofV21xC6qnMLUpYRAjBIAJ4vv7iiqwlnKuvWoEF1N/UDxixW1QCePqYa NQwPsbO/tyqZtMc4XWPzUfM= =YCJs -END PGP SIGNATURE-
[jira] Updated: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=all ] Dave Colasurdo updated GERONIMO-1372: - Attachment: geronimo.log > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > Attachments: geronimo.log > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) > at > org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) > at > org.ap
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360537 ] Dave Colasurdo commented on GERONIMO-1372: -- Retried the failure scenario on Tomcat (as do not yet see the failure on Jetty) and here are the results: 1) ./geronimo.sh - worked fine CTL-C shutdown - worked fine 2) ./geronimo.sh - worked fine CTL-C shutdown failed with exception kill -9 process 3) ./geronimo.sh - TradeEJB exception 4) ./geronimo.sg - TradeEJB exception Will attach my entire geronimo.log to the JIRA.. > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > Attachments: geronimo.log > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.v
[jira] Created: (GERONIMO-1373) DB info portlet not working correctly
DB info portlet not working correctly - Key: GERONIMO-1373 URL: http://issues.apache.org/jira/browse/GERONIMO-1373 Project: Geronimo Type: Bug Components: console Versions: 1.0 Environment: linux 2.4 kernel Reporter: Paul McMahan The DB info portlet (found under Misc-->Embedded DB) does not show any values for the database. When the portlet is rendered I see the following in var/log/geronimo.out but no stack trace: java.sql.SQLException -- 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: Error in WELCOME mail
You need to send an email to apmail AT apache.org or infrastructure AT apache.org. someone with apmail privs can make the fix. thanks, dims On 12/15/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > Thanks. For the record, how does one fix stuff like this other then > bug you :) > > -dain > > On Dec 15, 2005, at 1:08 PM, Davanum Srinivas wrote: > > > Fixed. > > > > -- dims > > > > On 12/15/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > >> How do we get these fixed? > >> > >> -dain > >> > >> Begin forwarded message: > >>> From: Rainer Jung <[EMAIL PROTECTED]> > >>> Date: December 15, 2005 12:01:49 PM PST > >>> To: [EMAIL PROTECTED] > >>> Subject: Error in Welcome mails > >>> > >>> Hi, > >>> > >>> the automatically generated "WELCOME" mail to this list contains > >>> the following text > >>> > >>> "Welcome to [EMAIL PROTECTED]" > >>> > >>> (line 10 including empty lines). It needs to be changed from > >>> "incubator" to "geronimo". > >> > >> Begin forwarded message: > >> > >>> From: Rainer Jung <[EMAIL PROTECTED]> > >>> Date: December 15, 2005 12:02:44 PM PST > >>> To: [EMAIL PROTECTED] > >>> Subject: Error in WELCOME mail > >>> > >>> Hi, > >>> > >>> the automatically generated "WELCOME" mail to this list contains > >>> the following text > >>> > >>> "Welcome to [EMAIL PROTECTED]" > >>> > >>> (line 10 including empty lines). It needs to be changed from > >>> "incubator" to "geronimo". > >> > >> > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > -- Davanum Srinivas : http://wso2.com/blogs/
Re: Error in WELCOME mail
Thanks. For the record, how does one fix stuff like this other then bug you :) -dain On Dec 15, 2005, at 1:08 PM, Davanum Srinivas wrote: Fixed. -- dims On 12/15/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote: How do we get these fixed? -dain Begin forwarded message: From: Rainer Jung <[EMAIL PROTECTED]> Date: December 15, 2005 12:01:49 PM PST To: [EMAIL PROTECTED] Subject: Error in Welcome mails Hi, the automatically generated "WELCOME" mail to this list contains the following text "Welcome to [EMAIL PROTECTED]" (line 10 including empty lines). It needs to be changed from "incubator" to "geronimo". Begin forwarded message: From: Rainer Jung <[EMAIL PROTECTED]> Date: December 15, 2005 12:02:44 PM PST To: [EMAIL PROTECTED] Subject: Error in WELCOME mail Hi, the automatically generated "WELCOME" mail to this list contains the following text "Welcome to [EMAIL PROTECTED]" (line 10 including empty lines). It needs to be changed from "incubator" to "geronimo". -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360532 ] Paul McMahan commented on GERONIMO-1372: Dave, I am also seeing the exception with Java 1.4.2_10 on linux > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) > at > org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) > at > org.apache.catalina.core.ContainerBase.addChildInternal(Containe
[jira] Updated: (GERONIMO-1192) Installer should create a config.xml for the target install
[ http://issues.apache.org/jira/browse/GERONIMO-1192?page=all ] erik daughtrey updated GERONIMO-1192: - Attachment: installer-branches-1.0-12151601.patch.gz This patch includes: 1. Everything from the prior patches 2. Built against branches/1.0 3. Port validation (last missing feature) 4. Installs documentation 5. Code is re-factored to be cleaner and clearer We still need to validate the configs generated, but it does successfully install Tomcat and Jetty. > Installer should create a config.xml for the target install > --- > > Key: GERONIMO-1192 > URL: http://issues.apache.org/jira/browse/GERONIMO-1192 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0-M5 > Environment: Installer runtime > Reporter: erik daughtrey > Assignee: John Sisson > Fix For: 1.1 > Attachments: 20051214_jsisson_patch_installer.patch, > installer-200512111301.patch, installer-200512112003.patch, > installer-200512121118.patch, installer-200512122002.patch, > installer-branches-1.0-12151601.patch.gz, installer_1192_200512080036.patch > > DJ - "This could be done by adding bits associated with each configuration, > or by removing chunks from a 'universal' config.xml for the configuations we > didn't install." -- 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: Error in WELCOME mail
Fixed. -- dims On 12/15/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > How do we get these fixed? > > -dain > > Begin forwarded message: > > From: Rainer Jung <[EMAIL PROTECTED]> > > Date: December 15, 2005 12:01:49 PM PST > > To: [EMAIL PROTECTED] > > Subject: Error in Welcome mails > > > > Hi, > > > > the automatically generated "WELCOME" mail to this list contains > > the following text > > > > "Welcome to [EMAIL PROTECTED]" > > > > (line 10 including empty lines). It needs to be changed from > > "incubator" to "geronimo". > > Begin forwarded message: > > > From: Rainer Jung <[EMAIL PROTECTED]> > > Date: December 15, 2005 12:02:44 PM PST > > To: [EMAIL PROTECTED] > > Subject: Error in WELCOME mail > > > > Hi, > > > > the automatically generated "WELCOME" mail to this list contains > > the following text > > > > "Welcome to [EMAIL PROTECTED]" > > > > (line 10 including empty lines). It needs to be changed from > > "incubator" to "geronimo". > > -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360529 ] Dave Colasurdo commented on GERONIMO-1372: -- Same exception with 1.4.2_10 JRE.. Is anyone else seeing this exception? > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) > at > org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) > at > org.apache.catalina.core.ContainerBase.addChildInter
Fwd: Error in WELCOME mail
How do we get these fixed? -dain Begin forwarded message: From: Rainer Jung <[EMAIL PROTECTED]> Date: December 15, 2005 12:01:49 PM PST To: [EMAIL PROTECTED] Subject: Error in Welcome mails Hi, the automatically generated "WELCOME" mail to this list contains the following text "Welcome to [EMAIL PROTECTED]" (line 10 including empty lines). It needs to be changed from "incubator" to "geronimo". Begin forwarded message: From: Rainer Jung <[EMAIL PROTECTED]> Date: December 15, 2005 12:02:44 PM PST To: [EMAIL PROTECTED] Subject: Error in WELCOME mail Hi, the automatically generated "WELCOME" mail to this list contains the following text "Welcome to [EMAIL PROTECTED]" (line 10 including empty lines). It needs to be changed from "incubator" to "geronimo".
4.0 release time frame?
Hi All, The new Message Groups feature sounds really cool. But does anyone know when 4.0 will be released? Thanks, Pedro -- Power corrupts. Absolute power corrupts absolutely. It rocks absolutely, too. -- despair.com
Re: OpenEJB PK issue
Hi Manu,
Once again, thanks for your debugging!
I had a look to the DD and I have identified why the itests showing this
specifc case are working for us and not for you: basically in our test,
we have a OTM relationship between a CMP with a simple PK on the
one-side and a CMP with a compound PK on the many-side. Your case is
slightly different: the CMP on the one-side has a compound PK and hence
another code path is used.
Basically, the problem that you are raising is exactly what I was trying
to describe in one of my previous email:
"
About createCMPFieldAccessors, the
relatedEntity.getPrimaryKeyFields().size() test must also be replaced
by an isCompoundPK test. However, it seems that we should add a special
processing to handle a CMP field mapped to a FK column referencing the
(single) PK column associated to a compound PK having a single field.
"
Hm; I realise that this was far to be understandable.
This special processing works as follow:
1. if the CMP field, CMPField, is mapped to a FK column;
2. if the PK column referenced by this FK column is associated to a
compound PK column;
3. if the compound PK uses more than one CMP field:
3.1 then the accessor of CMPField must be read-only. (this is what we
currently have)
4. otherwise:
4.1 the accessor of CMPField must be read-write.
This purpose of the " if (null !=
ejb.getAssociationEndDefiningFKAttribute(name)) {" block is to set the
CMR field at the same time than the CMP field when a CMP field is mapped
to a FK column. BTW, it seems that you are familiar with OpenEJB and
TranQL; so, do you want to work on a patch to fix this problem? FYI, we
have a large and very interesting piece of work ahead of us to support
the persistence part of the EJB3 specification :)
Thanks,
Gianny
Manu George wrote:
Hi Gianny,
I put in a dirty hack and got my app working. The
problem I was facing was in the
private LinkedHashMap createCMPFieldAccessors(SQLQueryBuilder
queryBuilder, LinkedHashMap cmrFieldAccessor) throws QueryException {
method in CMPContainerBuilder
Here there is a if (null !=
ejb.getAssociationEndDefiningFKAttribute(name)) {
check inside which the CMR foreign Key was set to a read only field
during deployment. In my app the CMR FK is a part of the primary key
also. So during ejbCreate it gives error saying that it is a readonly
field. I just added a check to not go into this loop if the FK is also
a part of the PK.
and the app seems to be working. Hope this gives you more info abt
the problem I am facing
Regards
Manu
[jira] Commented: (GERONIMO-1372) Exception during startup - TradeEJB
[ http://issues.apache.org/jira/browse/GERONIMO-1372?page=comments#action_12360528 ] Dave Colasurdo commented on GERONIMO-1372: -- Just noticed the default JRE on the machine is set to 1.4.2_06.. Will retry with 1.4.2_10... > Exception during startup - TradeEJB > --- > > Key: GERONIMO-1372 > URL: http://issues.apache.org/jira/browse/GERONIMO-1372 > Project: Geronimo > Type: Bug > Versions: 1.0 > Environment: Linux - Suse 10 > Reporter: Dave Colasurdo > > Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat > , seeing an exception during startup. At first it seemed intermittent but > now seems to occur everytime. > linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh > run > Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 > Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp > Using JRE_HOME:/usr/lib/jvm/jre > Booting Geronimo Kernel (in Java 1.4.2_06)... > Starting Geronimo Application Server > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:04,877 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 32s Starting geronimo/tomcat/1.0/car > 15:19:05,647 WARN [MapperListener] Unknown default host: localhost > [*> ] 40% 33s Starting geronimo/tomcat/1.0/car > 15:19:06,103 WARN [MapperListener] Unknown default host: localhost > [> ] 85% 53s Starting > geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] > TradeEJB > javax.ejb.NoSuchObjectLocalException: > geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB > at > org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) > at > org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) > at > org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() > at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) > at > org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) > at > org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) > at > org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) > at > org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) > at > org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) > at > org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) > at > org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) > at > org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) > at > org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) > at > org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) > at > org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) > at > org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) > at > org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() > at > org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) > at > org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) > at > org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) > at > org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) > at > org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) > at > org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) > at > org.apache.catalina.core.Contain
Re: New binaries
Apparently, the startup race condition is still present, so we'll have to unpack, startup, shutdown, clean, repack and resign the binaries again. :( -David On Dec 15, 2005, at 11:56 AM, Jeff Genender wrote: Rainer, Those directories get created on server startup. Jeff Rainer Jung wrote: Hi Jeff, I just had a short look at the contents of the tomcat zip. A few comments, but I can not tell, which of these are actually problems. In general: a lot of the subdirs under geronimo-1.0/var do not exist any more: - directory geronimo-1.0/deploy/ does not exist any more (was empty previously) Tomcat stuff: - directory geronimo-1.0/var/catalina/ROOT/ does not exist any more (contained a simple root context previously) - directory geronimo-1.0/var/catalina/conf/ does not exist any more (contained a web.xml previously) - directories geronimo-1.0/var/catalina/logs and geronimo-1.0/var/catalina/work do not exist any more (empty previously) Derby stuff: - directory geronimo-1.0/var/derby/ does not exist any more (contained subdirs geronimo-1.0/var/derby/UddiDatabase/, geronimo-1.0/var/derby/DaytraderDatabase/ and geronimo-1.0/var/derby/SystemDatabase/ previously) ActiveMQ: - directory geronimo-1.0/var/activemq/ does not exist any more (contained subdir journal previously) Naming: - directory geronimo-1.0/var/ldap/ does not exist any more (contained subdir system previouly) Others: - directory geronimo-1.0/var/txlog/ does not exist any more (contained two files how1_[12].log previously) Jeff Genender wrote: Hi, I finally got Internet connectivity from the hotel in San Diego (it was down). I have built new binaries to be reviewed. This is not a vote...its a review...after folks have reviewed this, we can move this to a vote. I have put the binaries here: http://people.apache.org/~jgenender/geronimo/1.0/ Thanks to David Blevins for working with me yesterday to get this completed. Please download these and try them out...and please comment on any issues/changes/naming we need for these. Thanks, Jeff
[jira] Created: (GERONIMO-1372) Exception during startup - TradeEJB
Exception during startup - TradeEJB --- Key: GERONIMO-1372 URL: http://issues.apache.org/jira/browse/GERONIMO-1372 Project: Geronimo Type: Bug Versions: 1.0 Environment: Linux - Suse 10 Reporter: Dave Colasurdo Running on Linux with the latest 1.0 candidate build (12/15/05) using Tomcat , seeing an exception during startup. At first it seemed intermittent but now seems to occur everytime. linux-:/home/davecola/downloads/geronimo-1.0/bin # ./geronimo.sh run Using GERONIMO_BASE: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_HOME: /home/davecola/downloads/geronimo-1.0 Using GERONIMO_TMPDIR: /home/davecola/downloads/geronimo-1.0/var/temp Using JRE_HOME:/usr/lib/jvm/jre Booting Geronimo Kernel (in Java 1.4.2_06)... Starting Geronimo Application Server [*> ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:04,877 WARN [MapperListener] Unknown default host: localhost [*> ] 40% 32s Starting geronimo/tomcat/1.0/car 15:19:05,647 WARN [MapperListener] Unknown default host: localhost [*> ] 40% 33s Starting geronimo/tomcat/1.0/car 15:19:06,103 WARN [MapperListener] Unknown default host: localhost [> ] 85% 53s Starting geronimo/daytrader-der...15:19:26,049 WARN [SystemExceptionInterceptor] TradeEJB javax.ejb.NoSuchObjectLocalException: geronimo.server:EJBModule=daytrader-ejb-1.0.jar,J2EEApplication=geronimo/daytrader-derby-tomcat/1.0/car,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=KeySequenceEJB at org.openejb.proxy.EJBMethodInterceptor.createEJBInvocation(EJBMethodInterceptor.java:173) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:115) at org.openejb.proxy.SessionEJBLocalHome$$EnhancerByCGLIB$$fcfe1e06.create() at org.apache.geronimo.samples.daytrader.ejb.TradeBean.ejbCreate(TradeBean.java:1178) at org.apache.geronimo.samples.daytrader.ejb.TradeBean$$FastClassByCGLIB$$7b99417a.invoke() at org.openejb.slsb.EJBCreateMethod.execute(EJBCreateMethod.java:94) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.slsb.StatelessInstanceContext.ejbCreate(StatelessInstanceContext.java:168) at org.openejb.slsb.StatelessInstanceFactory.createInstance(StatelessInstanceFactory.java:74) at org.openejb.util.SoftLimitedInstancePool.acquire(SoftLimitedInstancePool.java:81) at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:84) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140) at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80) at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82) at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238) at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129) at org.openejb.proxy.SessionEJBHome$$EnhancerByCGLIB$$a716616d.create() at org.apache.geronimo.samples.daytrader.direct.TradeDirect.init(TradeDirect.java:2265) at org.apache.geronimo.samples.daytrader.web.TradeWebContextListener.contextInitialized(TradeWebContextListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4127) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:64) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:267) at org.apache.geronimo.tomcat.valve.TransactionContextValve.invoke(TransactionContextValve.java:53) at org.apache.geronimo.tomcat.valve.ComponentContextValve.invoke(ComponentContextValve.java:47) at org.apache.geronimo.tomcat.valve.InstanceContextValve.invoke(InstanceContextValve.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:187) 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.addContext(TomcatContainer.java:287) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMet
RE: Spaces in HTML docs - not unix friendly
Thanks, worse case, we could create a script to fix-up the docs and links with '_' (or something else) after they are generated by confluent. - Chris -Original Message- From: Hernan Cunico [mailto:[EMAIL PROTECTED] Sent: Thursday, December 15, 2005 10:51 AM To: dev@geronimo.apache.org Subject: Re: Spaces in HTML docs - not unix friendly Hi Chris, these pages (file names) are created automatically by the software we use to create the documents. Changing the file names will imply to change the article titles. I know spaces in file names are a pain with unix, I will try to find a workaround. Cheers! Hernan Christopher Chan wrote: > Hi all, > > I've been experimenting with creating an rpm with Geronimo, but rpm does > not like spaces in filenames and there are some html documentation that > contain spaces in them. Is there a chance to standardize naming to not > contain spaces to make it more unix/linux friendly? > > Under modules/scripts/src/resources/docs: > > Administration.html > Administrative tasks_attachments > Administrative tasks.html > Apache Geronimo project overview.html > Apache Geronimo V1 - Documentation_attachments > Apache Geronimo V1 - Documentation.html > Architecture_attachments > Architecture.html > Authorization - mapping J2EE roles to Principals.html > Available login modules.html > Backup and recovery.html > border > Component Configuration.html > Concepts.html > Configuring LDAP_attachments > Configuring LDAP.html > Deployer tool.html > Deploying configurations and resources.html > Deploying secure applications.html > Deployment.html > Deployment plans.html > Development.html > documentation_banner.jpg > Geronimo Administration Console_attachments > Geronimo Administration Console.html > Geronimo and JAAS.html > Geronimo Login Config Schema.html > head_bgstretch_1x86.gif > Hints and Tips.html > Hot deployment.html > icons > Implementing security - working examples.html > index.html > Installation.html > JaasLoginService API Discussion.html > JBoss to Geronimo - EJB-BMP Migration_attachments > JBoss to Geronimo - EJB-BMP Migration.html > JBoss to Geronimo - EJB-CMP Migration_attachments > JBoss to Geronimo - EJB-CMP Migration.html > JBoss to Geronimo - EJB-MDB Migration_attachments > JBoss to Geronimo - EJB-MDB Migration.html > JBoss to Geronimo - EJB-Session Beans Migration_attachments > JBoss to Geronimo - EJB-Session Beans Migration.html > JBoss to Geronimo - JCA Migration_attachments > JBoss to Geronimo - JCA Migration.html > JBoss to Geronimo - JDBC Migration_attachments > JBoss to Geronimo - JDBC Migration.html > JBoss to Geronimo - Security Migration_attachments > JBoss to Geronimo - Security Migration.html > JBoss to Geronimo - Servlets and JSPs Migration_attachments > JBoss to Geronimo - Servlets and JSPs Migration.html > JBoss to Geronimo - Web Services Migration_attachments > JBoss to Geronimo - Web Services Migration.html > left.html > Login into Geronimo.html > main.html > Maintenance.html > Mapping J2EE Roles in M5 release.html > Migrating to Apache Geronimo.html > Performance and high availability.html > Quick start - Apache Geronimo for the impatient_attachments > Quick start - Apache Geronimo for the impatient.html > Security Definition Schema.html > Security.html > styles > Tools and commands.html > top.html > Troubleshooting.html > > - Chris >
Re: [WEBCONSOLE] Start Playing with Pluto 1.1?
Unfortunately, no. Between the geronimo release and several portals discussions that I ended up getting involved in, I was never able to follow through (though I did get to meet Aaron breifly). Part of our portals discussions were that the jetspeed guys really want jetspeed to be the portal embedded within Geronimo. I believe that Dain had some conversations with David Sean Taylor about that approach. It's my understanding that DST is going to start working on a scaled down version of jetspeed. My humble opinion is that Pluto is more light weight and can easily meet what is needed for the future with a couple of tweeks. There are also advantages to jetspeed such as the fact that it has a more vibrant community (in fact, one of the reasons I like the idea of embedding pluto in geronimo and felix is my hope that it will help spur interest in pluto). What are the geronimo developer's thoughts? Are you leaning towards pluto or jetspeed? I'm still VERY interested in helping with this effort, so no matter what the approach I'd like to be involved. I've just started translating your current configurations into pluto 1.1 configuration and hope to have it up and running today. The only hiccup I'll have to get through is that it seems as though building and running G from source has changed since that last time I did it. TI can't find the modules/assembly distribution which I used to use and the wiki still references. Any hints or updated documentation I should be looking at? David On 12/15/05, Joe Bohn <[EMAIL PROTECTED]> wrote: > Was this discussed at ApacheCon and was some groundwork laid? If so, > can somebody please post the results here? > > Was there any discussion of moving Pluto out from the console web app to > be a base Geronimo component (like the Servlet or EJB containers)? > This would make it possible for Geronimo to host end user portals. Any > discussion about the advantages/disadvantages of switching from the > Pluto Portal to something like JetSpeed2? > > I'm very interested in helping with this effort and perhaps simplifying > the console build/packaging structure as we upgrade the Portal and > possibly extend support for user portals. > > Joe > > Aaron Mulder wrote: > > Sounds great to me, but I'm probably not going to have a ton of time > > to work on this in the immediate future on account of getting 1.0 out > > the door and so on. I'd love to at least talk at ApacheCon and lay > > the groundwork for moving forward with Pluto 1.1 for the next Geronimo > > version. > > > > Thanks, > > Aaron > > > > On 12/8/05, David H. DeWolf <[EMAIL PROTECTED]> wrote: > > > >>The Pluto team is preparing to release pluto-1.1-ALPHA. In addition to > >>simplifying the container to be much easier to embed and customize, we > >>have added support for runtime portlet deployment. I understand that > >>this is something that you guys might be interested in. > >> > >>I have begun looking at your webconsole and think plugging in 1.1 should > >>be pretty simple. If you're interested, I'd love to work with some of > >>you at ApacheCon and help you get upgraded. > >> > >>Let me know, > >> > >>David > >> > >> > > > > > > > > -- > Joe Bohn > [EMAIL PROTECTED] > > "He is no fool who gives what he cannot keep, to gain what he cannot > lose." -- Jim Elliot >
Documentation update
Hi All, I just updated http://issues.apache.org/jira/browse/GERONIMO-1357 Major updates/adds are on Administration (tools and commands) Cheers! Hernan
Re: Spaces in HTML docs - not unix friendly
There must be a way to render/write the files with spaces using underscores. Ping [EMAIL PROTECTED], or I can if you like. --jason On Dec 15, 2005, at 10:50 AM, Hernan Cunico wrote: Hi Chris, these pages (file names) are created automatically by the software we use to create the documents. Changing the file names will imply to change the article titles. I know spaces in file names are a pain with unix, I will try to find a workaround. Cheers! Hernan Christopher Chan wrote: Hi all, I've been experimenting with creating an rpm with Geronimo, but rpm does not like spaces in filenames and there are some html documentation that contain spaces in them. Is there a chance to standardize naming to not contain spaces to make it more unix/ linux friendly? Under modules/scripts/src/resources/docs: Administration.html Administrative tasks_attachments Administrative tasks.html Apache Geronimo project overview.html Apache Geronimo V1 - Documentation_attachments Apache Geronimo V1 - Documentation.html Architecture_attachments Architecture.html Authorization - mapping J2EE roles to Principals.html Available login modules.html Backup and recovery.html border Component Configuration.html Concepts.html Configuring LDAP_attachments Configuring LDAP.html Deployer tool.html Deploying configurations and resources.html Deploying secure applications.html Deployment.html Deployment plans.html Development.html documentation_banner.jpg Geronimo Administration Console_attachments Geronimo Administration Console.html Geronimo and JAAS.html Geronimo Login Config Schema.html head_bgstretch_1x86.gif Hints and Tips.html Hot deployment.html icons Implementing security - working examples.html index.html Installation.html JaasLoginService API Discussion.html JBoss to Geronimo - EJB-BMP Migration_attachments JBoss to Geronimo - EJB-BMP Migration.html JBoss to Geronimo - EJB-CMP Migration_attachments JBoss to Geronimo - EJB-CMP Migration.html JBoss to Geronimo - EJB-MDB Migration_attachments JBoss to Geronimo - EJB-MDB Migration.html JBoss to Geronimo - EJB-Session Beans Migration_attachments JBoss to Geronimo - EJB-Session Beans Migration.html JBoss to Geronimo - JCA Migration_attachments JBoss to Geronimo - JCA Migration.html JBoss to Geronimo - JDBC Migration_attachments JBoss to Geronimo - JDBC Migration.html JBoss to Geronimo - Security Migration_attachments JBoss to Geronimo - Security Migration.html JBoss to Geronimo - Servlets and JSPs Migration_attachments JBoss to Geronimo - Servlets and JSPs Migration.html JBoss to Geronimo - Web Services Migration_attachments JBoss to Geronimo - Web Services Migration.html left.html Login into Geronimo.html main.html Maintenance.html Mapping J2EE Roles in M5 release.html Migrating to Apache Geronimo.html Performance and high availability.html Quick start - Apache Geronimo for the impatient_attachments Quick start - Apache Geronimo for the impatient.html Security Definition Schema.html Security.html styles Tools and commands.html top.html Troubleshooting.html - Chris
Re: New binaries
Rainer, Those directories get created on server startup. Jeff Rainer Jung wrote: > Hi Jeff, > > I just had a short look at the contents of the tomcat zip. A few > comments, but I can not tell, which of these are actually problems. In > general: a lot of the subdirs under geronimo-1.0/var do not exist any more: > > - directory geronimo-1.0/deploy/ does not exist any more (was empty > previously) > > Tomcat stuff: > > - directory geronimo-1.0/var/catalina/ROOT/ does not exist any more > (contained a simple root context previously) > - directory geronimo-1.0/var/catalina/conf/ does not exist any more > (contained a web.xml previously) > - directories geronimo-1.0/var/catalina/logs and > geronimo-1.0/var/catalina/work do not exist any more (empty previously) > > Derby stuff: > - directory geronimo-1.0/var/derby/ does not exist any more (contained > subdirs geronimo-1.0/var/derby/UddiDatabase/, > geronimo-1.0/var/derby/DaytraderDatabase/ and > geronimo-1.0/var/derby/SystemDatabase/ previously) > > ActiveMQ: > > - directory geronimo-1.0/var/activemq/ does not exist any more > (contained subdir journal previously) > > Naming: > > - directory geronimo-1.0/var/ldap/ does not exist any more (contained > subdir system previouly) > > Others: > > - directory geronimo-1.0/var/txlog/ does not exist any more (contained > two files how1_[12].log previously) > > Jeff Genender wrote: >> Hi, >> >> I finally got Internet connectivity from the hotel in San Diego (it >> was down). >> >> I have built new binaries to be reviewed. This is not a vote...its a >> review...after folks have reviewed this, we can move this to a vote. >> I have put the binaries here: >> >> http://people.apache.org/~jgenender/geronimo/1.0/ >> >> Thanks to David Blevins for working with me yesterday to get this >> completed. >> >> Please download these and try them out...and please comment on any >> issues/changes/naming we need for these. >> >> Thanks, >> >> Jeff
Re: Spaces in HTML docs - not unix friendly
Hi Chris, these pages (file names) are created automatically by the software we use to create the documents. Changing the file names will imply to change the article titles. I know spaces in file names are a pain with unix, I will try to find a workaround. Cheers! Hernan Christopher Chan wrote: Hi all, I've been experimenting with creating an rpm with Geronimo, but rpm does not like spaces in filenames and there are some html documentation that contain spaces in them. Is there a chance to standardize naming to not contain spaces to make it more unix/linux friendly? Under modules/scripts/src/resources/docs: Administration.html Administrative tasks_attachments Administrative tasks.html Apache Geronimo project overview.html Apache Geronimo V1 - Documentation_attachments Apache Geronimo V1 - Documentation.html Architecture_attachments Architecture.html Authorization - mapping J2EE roles to Principals.html Available login modules.html Backup and recovery.html border Component Configuration.html Concepts.html Configuring LDAP_attachments Configuring LDAP.html Deployer tool.html Deploying configurations and resources.html Deploying secure applications.html Deployment.html Deployment plans.html Development.html documentation_banner.jpg Geronimo Administration Console_attachments Geronimo Administration Console.html Geronimo and JAAS.html Geronimo Login Config Schema.html head_bgstretch_1x86.gif Hints and Tips.html Hot deployment.html icons Implementing security - working examples.html index.html Installation.html JaasLoginService API Discussion.html JBoss to Geronimo - EJB-BMP Migration_attachments JBoss to Geronimo - EJB-BMP Migration.html JBoss to Geronimo - EJB-CMP Migration_attachments JBoss to Geronimo - EJB-CMP Migration.html JBoss to Geronimo - EJB-MDB Migration_attachments JBoss to Geronimo - EJB-MDB Migration.html JBoss to Geronimo - EJB-Session Beans Migration_attachments JBoss to Geronimo - EJB-Session Beans Migration.html JBoss to Geronimo - JCA Migration_attachments JBoss to Geronimo - JCA Migration.html JBoss to Geronimo - JDBC Migration_attachments JBoss to Geronimo - JDBC Migration.html JBoss to Geronimo - Security Migration_attachments JBoss to Geronimo - Security Migration.html JBoss to Geronimo - Servlets and JSPs Migration_attachments JBoss to Geronimo - Servlets and JSPs Migration.html JBoss to Geronimo - Web Services Migration_attachments JBoss to Geronimo - Web Services Migration.html left.html Login into Geronimo.html main.html Maintenance.html Mapping J2EE Roles in M5 release.html Migrating to Apache Geronimo.html Performance and high availability.html Quick start - Apache Geronimo for the impatient_attachments Quick start - Apache Geronimo for the impatient.html Security Definition Schema.html Security.html styles Tools and commands.html top.html Troubleshooting.html - Chris
Re: New binaries
Hi Jeff, I just had a short look at the contents of the tomcat zip. A few comments, but I can not tell, which of these are actually problems. In general: a lot of the subdirs under geronimo-1.0/var do not exist any more: - directory geronimo-1.0/deploy/ does not exist any more (was empty previously) Tomcat stuff: - directory geronimo-1.0/var/catalina/ROOT/ does not exist any more (contained a simple root context previously) - directory geronimo-1.0/var/catalina/conf/ does not exist any more (contained a web.xml previously) - directories geronimo-1.0/var/catalina/logs and geronimo-1.0/var/catalina/work do not exist any more (empty previously) Derby stuff: - directory geronimo-1.0/var/derby/ does not exist any more (contained subdirs geronimo-1.0/var/derby/UddiDatabase/, geronimo-1.0/var/derby/DaytraderDatabase/ and geronimo-1.0/var/derby/SystemDatabase/ previously) ActiveMQ: - directory geronimo-1.0/var/activemq/ does not exist any more (contained subdir journal previously) Naming: - directory geronimo-1.0/var/ldap/ does not exist any more (contained subdir system previouly) Others: - directory geronimo-1.0/var/txlog/ does not exist any more (contained two files how1_[12].log previously) Jeff Genender wrote: Hi, I finally got Internet connectivity from the hotel in San Diego (it was down). I have built new binaries to be reviewed. This is not a vote...its a review...after folks have reviewed this, we can move this to a vote. I have put the binaries here: http://people.apache.org/~jgenender/geronimo/1.0/ Thanks to David Blevins for working with me yesterday to get this completed. Please download these and try them out...and please comment on any issues/changes/naming we need for these. Thanks, Jeff
Re: New binaries
- shutting down the server from the console or command line results in an SQLException in var/log/geronimo.out Dave beat me to creating a JIRA for the shutdown problem :-) http://issues.apache.org/jira/browse/GERONIMO-1371 Best wishes, Paul
Re: New binaries
I tried out geronimo-tomcat-j2ee-1.0.tar.gz on a linux 2.4 kernel. A few comments: - there's a typo in RELEASE-NOTES-1.0.txt at line159: "released" should be "releases"- there are warnings and a stack trace in var/log/geronimo.out when starting the server - the "DB Info" action in the console (under Misc-->Embedded DB) does not work and prints "java.sql.SQLException" in var/log/geronimo.out - shutting down the server from the console or command line results in an SQLException in var/log/geronimo.out - nit: is the file geronimo-1.0/META-INF/MANIFEST.MF necessary? - the external links in the welcome pages don't point at the redirects on geronimo.apache.org (see JIRA 1364). maybe this should wait until v1.1 so Aaron has a chance to look at the patch... Best wishes, Paul On 12/15/05, Jeff Genender <[EMAIL PROTECTED]> wrote: Hi,I finally got Internet connectivity from the hotel in San Diego (it wasdown).I have built new binaries to be reviewed. This is not a vote...its areview...after folks have reviewed this, we can move this to a vote. I have put the binaries here:http://people.apache.org/~jgenender/geronimo/1.0/Thanks to David Blevins for working with me yesterday to get this completed. Please download these and try them out...and please comment on anyissues/changes/naming we need for these.Thanks,Jeff
[jira] Created: (GERONIMO-1371) Geronimo startup/shutdown issues
Geronimo startup/shutdown issues Key: GERONIMO-1371 URL: http://issues.apache.org/jira/browse/GERONIMO-1371 Project: Geronimo Type: Bug Versions: 1.0 Environment: Windows Reporter: Dave Colasurdo Noticed two separate issues when using the latest v1 candidate build (12/15/05) on a windows platform... 1) When issuing startup.bat, lots of debug messages appear in the primary window.. Suspect this is just a missing @echo off 2) Seeing the following warning in the secondary window and the log for various shutdowns... a) "startup.bat" followed by "shutdown.bat" b) "geronimo.bat start" followed by "shutdown.bat" 13:36:31,052 WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null SQL Exception: No current connection. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.commit(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.setAutoCommit(Unknown Source) at org.apache.derby.iapi.jdbc.BrokeredConnection.setAutoCommit(Unknown Source) at org.tranql.connector.jdbc.ManagedXAConnection.localTransactionStart(ManagedXAConnection.java:89) at org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.begin(AbstractManagedConnection.java:188) at org.tranql.connector.jdbc.ConnectionHandle.setAutoCommit(ConnectionHandle.java:161) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:126) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke() 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.activemq.store.PersistenceAdapter$$EnhancerByCGLIB$$98dcaa17.beginTransaction() at org.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:158) at org.activemq.util.TransactionTemplate.run(TransactionTemplate.java:38) at org.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:227) at org.activemq.store.journal.JournalPersistenceAdapter$3.run(JournalPersistenceAdapter.java:357) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source) at java.lang.Thread.run(Thread.java:534) 13:36:31,062 ERROR [JournalPersistenceAdapter] Failed to checkpoint a message store: javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. javax.jms.JMSException: Failed to create transaction: SQL Exception: No current connection. at org.activemq.util.JMSExceptionHelper.newJMSException(JMSExceptionHelper.java:49) at org.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:130) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean.beginTransaction(JDBCPersistenceAdapterGBean.java:76) at org.activemq.store.jdbc.JDBCPersistenceAdapterGBean$$FastClassByCGLIB$$8be8a0a0.invoke() 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.activemq.store.PersistenceAdapter$$EnhancerByCGLIB$$98dcaa17.beginTransaction() at org.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:158) at org.activemq.util.TransactionTemplate.run(TransactionTemplate.java:38)
[jira] Updated: (GERONIMO-1357) Apache Geronimo V1.0 Documentation Draft
[ http://issues.apache.org/jira/browse/GERONIMO-1357?page=all ] Hernan Cunico updated GERONIMO-1357: Attachment: GDoc_2005_12_15.zip Update to the HTML version of the documentation. Include updated screenshots/captures, tools and commands. > Apache Geronimo V1.0 Documentation Draft > > > Key: GERONIMO-1357 > URL: http://issues.apache.org/jira/browse/GERONIMO-1357 > Project: Geronimo > Type: Improvement > Versions: 1.0 > Environment: All > Reporter: Hernan Cunico > Assignee: Hernan Cunico > Attachments: GDoc_2005_12_15.zip, GERONIMO_DOC_2005_12_13.zip > > Better later than never, here is the updated HTML documentation. -- 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: 1.0 release Candidate 2...some guidelines
+1 -dain On Dec 15, 2005, at 10:00 AM, Alan D. Cabrera wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I second that. So long as we do not make an actual tag w/ that date, i.e. have a time series of release candidates in the tags directory. Regards, Alan Matt Hogstrom wrote, On 12/15/2005 9:12 AM: Good idea Paul...I like the date time string idea. Paul McMahan wrote: On 12/15/05, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Second, someone pointed out (I think it was Jacek) that we did not include a notation in the binary about what the release candidate was so that it is not confused with the final release. Before releasing another cut I would like the naming convention of the binary and the directories to be clearer as to what they contain otherwise this will get confusing. My suggestion is that the name be: geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of the release candidate (and we are now on number 2). The next set of images should follow this convention to ensure we are not confusing the users. I know these are release candidates and this isn't required but it would make me sleep better at night :) The directory that is actually contained in the zip will still be geronimo-1.0. Thoughts? Matt, including a notation in the filename seems like a good idea and could help prevent confusion. I've also seen projects use a date string instead of a release candidate number for this purpose. Using a date string is helpful since it makes it obvious when the image was created plus avoids publicizing how many unsuccessful attempts there have been (not saying that would be an issue in this case :o) Best wishes, Paul -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFDoa9O1xC6qnMLUpYRAvh0AJdhPFx2Iqw4Xq4a6EIL9dpTOzDFAJ0T6j9N ClFIsY+jLB6racfd8nZltA== =NZnc -END PGP SIGNATURE-
Re: Spaces in HTML docs - not unix friendly
I don't like the spaces either, but these pages were automatically generated by Confluence. I hope that as we get Confluence better integrated into our build using Maven Doxia we can remove the spaces from the file names automatically. -dain On Dec 14, 2005, at 12:25 PM, Christopher Chan wrote: Hi all, I've been experimenting with creating an rpm with Geronimo, but rpm does not like spaces in filenames and there are some html documentation that contain spaces in them. Is there a chance to standardize naming to not contain spaces to make it more unix/linux friendly? Under modules/scripts/src/resources/docs: Administration.html Administrative tasks_attachments Administrative tasks.html Apache Geronimo project overview.html Apache Geronimo V1 - Documentation_attachments Apache Geronimo V1 - Documentation.html Architecture_attachments Architecture.html Authorization - mapping J2EE roles to Principals.html Available login modules.html Backup and recovery.html border Component Configuration.html Concepts.html Configuring LDAP_attachments Configuring LDAP.html Deployer tool.html Deploying configurations and resources.html Deploying secure applications.html Deployment.html Deployment plans.html Development.html documentation_banner.jpg Geronimo Administration Console_attachments Geronimo Administration Console.html Geronimo and JAAS.html Geronimo Login Config Schema.html head_bgstretch_1x86.gif Hints and Tips.html Hot deployment.html icons Implementing security - working examples.html index.html Installation.html JaasLoginService API Discussion.html JBoss to Geronimo - EJB-BMP Migration_attachments JBoss to Geronimo - EJB-BMP Migration.html JBoss to Geronimo - EJB-CMP Migration_attachments JBoss to Geronimo - EJB-CMP Migration.html JBoss to Geronimo - EJB-MDB Migration_attachments JBoss to Geronimo - EJB-MDB Migration.html JBoss to Geronimo - EJB-Session Beans Migration_attachments JBoss to Geronimo - EJB-Session Beans Migration.html JBoss to Geronimo - JCA Migration_attachments JBoss to Geronimo - JCA Migration.html JBoss to Geronimo - JDBC Migration_attachments JBoss to Geronimo - JDBC Migration.html JBoss to Geronimo - Security Migration_attachments JBoss to Geronimo - Security Migration.html JBoss to Geronimo - Servlets and JSPs Migration_attachments JBoss to Geronimo - Servlets and JSPs Migration.html JBoss to Geronimo - Web Services Migration_attachments JBoss to Geronimo - Web Services Migration.html left.html Login into Geronimo.html main.html Maintenance.html Mapping J2EE Roles in M5 release.html Migrating to Apache Geronimo.html Performance and high availability.html Quick start - Apache Geronimo for the impatient_attachments Quick start - Apache Geronimo for the impatient.html Security Definition Schema.html Security.html styles Tools and commands.html top.html Troubleshooting.html - Chris
Re: Building the specs jars
There was a period when both maven 1 and maven 2 worked. The specs only work with maven 2 now. -dain On Dec 14, 2005, at 1:45 PM, Rick McGuire wrote: Jacek Laskowski wrote: Alan D. Cabrera wrote: The stuff in geronimo/specs was always on maven 2. Whow, I didn't know that. I'm on Maven 1 and can't remember whether or not I tried to build them at any time, but if I had been asked about specs and Maven version, I would've answer there was no dependency and any Maven version would work. And I was able to successfully build the javamail jar 3-4 weeks ago using maven 1, so this was a shock to me too! Alan Jacek
Re: Move JAXB spec to Geronimo
+1 To add the JAXB specs to geronimo I also like the plan. -dain On Dec 14, 2005, at 11:56 AM, Jochen Wiedmann wrote: Brett Porter wrote: > Since JaxMe is at Apache, you can move it over with svn mv. Exactly. However, initially, I'd prefer a copy operation. (No idea, whether that's as easy in SVN.) That would give a smoother step. We could wait until the generated jar files do meet the Maven repositories and stuff like that. > Has the JaxMe community as a whole voted to do this? I think it makes > sense, it would just be good to ensure everyone agrees. It will also > impact the committer list for Geronimo. You are absolutely right, Brett! Indeed, this should have been my first step. It is just that I have found the directory /www/cvs.apache.org/maven-snapshot-repository/ org.apache.geronimo.specs/ today and immediately had the thought that this would be a better place. I'll start a vote on the jaxme-dev mailing list. If this helps: I have no problem to request that we as the JaxMe developers abandon work on the code base (except possibly submitting patches). In other words, none of us would require to be a committer. Alan Cabrera wrote: > Sounds great. Let's put it in our geronimo/specs/trunk. If it's > stable, file a Jira w/ a tar of the files and I can plop that in. The codebase is *very* stable. Indeed, it had almost no changes since the import into the Apache repositories (almost 2 years ago). No surprise: There almost only interfaces and almost no classes, which are doing the actual work. Jochen
Re: 1.0 release Candidate 2...some guidelines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I second that. So long as we do not make an actual tag w/ that date, i.e. have a time series of release candidates in the tags directory. Regards, Alan Matt Hogstrom wrote, On 12/15/2005 9:12 AM: > Good idea Paul...I like the date time string idea. > > Paul McMahan wrote: > >> On 12/15/05, Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> >>> >>> Second, someone pointed out (I think it was Jacek) that we did not >>> include >>> a >>> notation in the binary about what the release candidate was so that >>> it is >>> not >>> confused with the final release. Before releasing another cut I would >>> like the >>> naming convention of the binary and the directories to be clearer as to >>> what >>> they contain otherwise this will get confusing. My suggestion is >>> that the >>> name be: >>> >>> geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of >>> the >>> release candidate (and we are now on number 2). The next set of images >>> should >>> follow this convention to ensure we are not confusing the users. I know >>> these >>> are release candidates and this isn't required but it would make me >>> sleep >>> better >>> at night :) The directory that is actually contained in the zip will >>> still be >>> geronimo-1.0. Thoughts? >> >> >> >> >> Matt, including a notation in the filename seems like a good idea and >> could >> help prevent confusion. I've also seen projects use a date string >> instead >> of a release candidate number for this purpose. Using a date string is >> helpful since it makes it obvious when the image was created plus avoids >> publicizing how many unsuccessful attempts there have been (not saying >> that >> would be an issue in this case :o) >> >> Best wishes, >> Paul >> -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFDoa9O1xC6qnMLUpYRAvh0AJdhPFx2Iqw4Xq4a6EIL9dpTOzDFAJ0T6j9N ClFIsY+jLB6racfd8nZltA== =NZnc -END PGP SIGNATURE-
[jira] Commented: (GERONIMO-1365) JSR-88 Manfest has incorrect Class-Path entries
[ http://issues.apache.org/jira/browse/GERONIMO-1365?page=comments#action_12360518 ] David Jencks commented on GERONIMO-1365: My intention in setting the manifest classpath entries as I did was that when used directly as the jsr-88 implementation jar, the jar would be placed in the bin directory, possibly with a simpler name. In this case, the manifest classpath entries would be correct. I don't think that asking people to find a jar in the geronimo repository in order to use jsr-88 is appropriate. I think this issue illustrates that we are using manifest classpath too much and that it is not appropriate for large scale software. Unfortuneately I don't have a solution in mind. > JSR-88 Manfest has incorrect Class-Path entries > --- > > Key: GERONIMO-1365 > URL: http://issues.apache.org/jira/browse/GERONIMO-1365 > Project: Geronimo > Type: Bug > Components: deployment > Versions: 1.0 > Reporter: Aaron Mulder > Assignee: David Jencks > Fix For: 1.1 > > We used to use bin/deployer.jar as our JSR-88 implementation JAR. As a > result, all the Class-Path entries had the form "../lib/foo.jar" (resolving > to geronimo/lib/...). > At some point, that was switched so that > repository/geronimo/jars/geronimo-deploy-jsr88-1.0.jar became the official > JSR-88 implementation JAR. However, all the Class-Path entries are still > "../lib" even though that resolves to "repository/geronimo/lib/..." which is > not valid. > Either we need to switch JSR-88 back to bin/deployer.jar or else we need to > update the Class-Path entries to be relative within the repository. > Assigning this to David J since he mentioned updating the JSR-88 > implementation JAR, so I suspect he has an opinion on which way to go with > this issue. -- 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: Geronimo in Eclipse question
If you modify your project.xml to add another dependency, you .classpath will need to be updated as well. Eclipse uses the .classpath to resolve its dependencies. You can update the .classpath by deleting it, and rerunning maven -o eclipse inside the particular project. Or you could open it up and add it by hand. The latter may be quicker. Let me know if you have further problems. Thanks. On Dec 15, 2005, at 8:51 AM, anita kulshreshtha wrote: Is anyone else having problems with adding a dependency via project.xml of a module, after the workspace has been configured as described in http://wiki.apache.org/geronimo/EclipseDeployment ? Thanks Anita __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - sachin
New binaries
Hi, I finally got Internet connectivity from the hotel in San Diego (it was down). I have built new binaries to be reviewed. This is not a vote...its a review...after folks have reviewed this, we can move this to a vote. I have put the binaries here: http://people.apache.org/~jgenender/geronimo/1.0/ Thanks to David Blevins for working with me yesterday to get this completed. Please download these and try them out...and please comment on any issues/changes/naming we need for these. Thanks, Jeff
Re: 1.0 release Candidate 2...some guidelines
Good idea Paul...I like the date time string idea. Paul McMahan wrote: On 12/15/05, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Second, someone pointed out (I think it was Jacek) that we did not include a notation in the binary about what the release candidate was so that it is not confused with the final release. Before releasing another cut I would like the naming convention of the binary and the directories to be clearer as to what they contain otherwise this will get confusing. My suggestion is that the name be: geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of the release candidate (and we are now on number 2). The next set of images should follow this convention to ensure we are not confusing the users. I know these are release candidates and this isn't required but it would make me sleep better at night :) The directory that is actually contained in the zip will still be geronimo-1.0. Thoughts? Matt, including a notation in the filename seems like a good idea and could help prevent confusion. I've also seen projects use a date string instead of a release candidate number for this purpose. Using a date string is helpful since it makes it obvious when the image was created plus avoids publicizing how many unsuccessful attempts there have been (not saying that would be an issue in this case :o) Best wishes, Paul
[jira] Created: (GERONIMO-1370) velocity.log is created in current directory on server startup
velocity.log is created in current directory on server startup -- Key: GERONIMO-1370 URL: http://issues.apache.org/jira/browse/GERONIMO-1370 Project: Geronimo Type: Bug Versions: 1.0 Environment: 1.0 RC1 Reporter: Kevan Miller Priority: Minor Fix For: 1.0 velocity.log is being created in the current directory when you start the server. -- 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-1293) Provide tomcat statistics
[ http://issues.apache.org/jira/browse/GERONIMO-1293?page=comments#action_12360511 ] anita kulshreshtha commented on GERONIMO-1293: -- Provide getters for the above stastistics for HTTP connector. The values will be returned from a local copy. To get the freshest value, refresh() must be called before calling the getters. > 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 > > 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
OpenEJB PK issue
Hi Gianny,
I put in a dirty hack and got my app working. The problem I was facing
was in the
private LinkedHashMap createCMPFieldAccessors(SQLQueryBuilder
queryBuilder, LinkedHashMap cmrFieldAccessor) throws QueryException {
method in CMPContainerBuilder
Here there is a if (null != ejb.getAssociationEndDefiningFKAttribute(name)) {
check inside which the CMR foreign Key was set to a read only field
during deployment. In my app the CMR FK is a part of the primary key
also. So during ejbCreate it gives error saying that it is a readonly
field. I just added a check to not go into this loop if the FK is also
a part of the PK.
and the app seems to be working. Hope this gives you more info abt the problem I am facing
Regards
Manu
Re: 1.0 release Candidate 2...some guidelines
On 12/15/05, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Second, someone pointed out (I think it was Jacek) that we did not include anotation in the binary about what the release candidate was so that it is notconfused with the final release. Before releasing another cut I would like the naming convention of the binary and the directories to be clearer as to whatthey contain otherwise this will get confusing. My suggestion is that the name be:geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of the release candidate (and we are now on number 2). The next set of images shouldfollow this convention to ensure we are not confusing the users. I know theseare release candidates and this isn't required but it would make me sleep better at night :) The directory that is actually contained in the zip will still begeronimo-1.0. Thoughts? Matt, including a notation in the filename seems like a good idea and could help prevent confusion. I've also seen projects use a date string instead of a release candidate number for this purpose. Using a date string is helpful since it makes it obvious when the image was created plus avoids publicizing how many unsuccessful attempts there have been (not saying that would be an issue in this case :o) Best wishes, Paul
Re: [WEBCONSOLE] Start Playing with Pluto 1.1?
Was this discussed at ApacheCon and was some groundwork laid? If so, can somebody please post the results here? Was there any discussion of moving Pluto out from the console web app to be a base Geronimo component (like the Servlet or EJB containers)? This would make it possible for Geronimo to host end user portals. Any discussion about the advantages/disadvantages of switching from the Pluto Portal to something like JetSpeed2? I'm very interested in helping with this effort and perhaps simplifying the console build/packaging structure as we upgrade the Portal and possibly extend support for user portals. Joe Aaron Mulder wrote: Sounds great to me, but I'm probably not going to have a ton of time to work on this in the immediate future on account of getting 1.0 out the door and so on. I'd love to at least talk at ApacheCon and lay the groundwork for moving forward with Pluto 1.1 for the next Geronimo version. Thanks, Aaron On 12/8/05, David H. DeWolf <[EMAIL PROTECTED]> wrote: The Pluto team is preparing to release pluto-1.1-ALPHA. In addition to simplifying the container to be much easier to embed and customize, we have added support for runtime portlet deployment. I understand that this is something that you guys might be interested in. I have begun looking at your webconsole and think plugging in 1.1 should be pretty simple. If you're interested, I'd love to work with some of you at ApacheCon and help you get upgraded. Let me know, David -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot
Geronimo in Eclipse question
Is anyone else having problems with adding a dependency via project.xml of a module, after the workspace has been configured as described in http://wiki.apache.org/geronimo/EclipseDeployment ? Thanks Anita __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails
During adventure builder deployment, I'm running into a problem that looks a lot like the GERONIMO-598 Jira issue. The setup is as follows (from the Adventure Builder 1.0.3): opc.ear contains opc-ejb.jar and processmanager-ejb.jar opc-ej contains WorkFlowManagerBean (Message Driven Bean) processmanager-ejb contains ProcessManagerSB (SB) ManagerBean (CMP Entity Bean) all methods involve have trans-attribute Required. The WorkFlowManagerBean invokes (in the same transaction context) two methods on the ProcessManagerSB, first create, which calls create on the ManagerBean home, then updateStatus, which does a findByPrimaryKey on the ManagerBean home (followed by a setStatus on the bean instance returned). The findByPrimaryKey fails; I've verified that the same primary key is used on the create and the findByPrimaryKey calls. If I change the trans-attribute on the two methods on ProcessManagerSB to RequiresNew, everything works fine, and I can see the ManagerBean entity persisted in the database. Can anyone figure out what might be going on? The only difference from GERONIMO-598 I notice is the call across jar files. Maybe someone with more insight into OpenEJB can tell, if this could have any importance? I've looked into the no-cache-flush mentioned in the Jira, but as far as I can tell, it would only make things worse. Kindly, Jakob
Re: Another OpenEJB Question
Hi, I am surpised that OrderItem.setOrder_orderId gives an error. Could you please provide the stack trace (the TranQL part + the first OpenEJB element) along with the DDs? FWIW, there are a couple of integration tests for CMP and CMR overlap scenarios in the OpenEJB tree: sub-project: modules/itests test class: org.openejb.test.entity.cmp2.cmrmapping.CMRMappingFacadeBean DDs: src/cmp2/cmrmapping Thanks, Gianny Manu George wrote: Hi, I have two CMPs with a 1:n relationship. CMP1 - Order - PK = OrderPK which has a single field orderId CMP2 - OrderItem = OrderItemPk which has 2 fields InventoryId and order_orderId OrderId and order_orderId are mapped When i do a setOrder_orderId in the ejbCreate of OrderItem geronimo gives an error during runtime saying cannot set read only field. When i don't set it geronimo says partial null key . In this case I set the cmr field in the ejbPostCreate method org.tranql.identity.UndefinedIdentityException: Partial null key at org.tranql.identity.DerivedIdentity.defineIdentity(DerivedIdentity.java:80) at org.openejb.entity.cmp.CMPCreateMethod.execute(CMPCreateMethod.java:175) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.entity.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:136) at org.openejb.entity.cmp.InTxCacheInterceptor.invoke(InTxCacheInterceptor.java:90) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:119) Am I doing anything wrong here? Regards Manu
Another OpenEJB Question
Hi, I have two CMPs with a 1:n relationship. CMP1 - Order - PK = OrderPK which has a single field orderId CMP2 - OrderItem = OrderItemPk which has 2 fields InventoryId and order_orderId OrderId and order_orderId are mapped When i do a setOrder_orderId in the ejbCreate of OrderItem geronimo gives an error during runtime saying cannot set read only field. When i don't set it geronimo says partial null key . In this case I set the cmr field in the ejbPostCreate method org.tranql.identity.UndefinedIdentityException: Partial null key at org.tranql.identity.DerivedIdentity.defineIdentity(DerivedIdentity.java:80) at org.openejb.entity.cmp.CMPCreateMethod.execute(CMPCreateMethod.java:175) at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72) at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56) at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81) at org.openejb.entity.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:136) at org.openejb.entity.cmp.InTxCacheInterceptor.invoke(InTxCacheInterceptor.java:90) at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:119) Am I doing anything wrong here? Regards Manu
Config Id Clarification related to Classloading
Hi, i have a geronimo-ra.xml plan with dependency jars. A MDB gets messages from RA and has a openejb-jar.xml plan. If i use M5 at runtime i get errors that say ClassNotFound Exception. The parent config of open-ejb-jar.xml is geronimo-ra.xml. If i use a build post M5 this works fine. Are there any changes related to classloading post M5 so that i dont get this error. Krishnakumar B
1.0 release Candidate 2...some guidelines
All, Optimism got the better of us and our first attempt at a release met with some well deserved -1's for reasons that are not anyone's fault. however, it has pointed out some obvious flaws in our process that I'd like to address now. First, we have a Press release that reached the public a little too soon. Not withstanding that issue I do not want to put out a rushed release to satisfy the press release. The web site is updated and we need to get the binary out as soon as possible and I hope the second spin of the release will correct that problem. Second, someone pointed out (I think it was Jacek) that we did not include a notation in the binary about what the release candidate was so that it is not confused with the final release. Before releasing another cut I would like the naming convention of the binary and the directories to be clearer as to what they contain otherwise this will get confusing. My suggestion is that the name be: geronimo-jetty-1.0-rc[n].tar.gz for example. Where [n] is the number of the release candidate (and we are now on number 2). The next set of images should follow this convention to ensure we are not confusing the users. I know these are release candidates and this isn't required but it would make me sleep better at night :) The directory that is actually contained in the zip will still be geronimo-1.0. Thoughts? Finally, It looks like the file corruption issue pointed out regarding the source tar balls was some confusion over how files that are 100 characters long were handled on Solaris. It sounds like a Solaris bug and not ours. We've made really good progress in squashing the bugs and getting features in so let's take this final few days and finish the release with gusto. We're almost there.
Re: Spaces in HTML docs - not unix friendly
Really? Can you post your spec file? -David On Dec 14, 2005, at 12:25 PM, Christopher Chan wrote: Hi all, I've been experimenting with creating an rpm with Geronimo, but rpm does not like spaces in filenames and there are some html documentation that contain spaces in them. Is there a chance to standardize naming to not contain spaces to make it more unix/linux friendly? Under modules/scripts/src/resources/docs: Administration.html Administrative tasks_attachments Administrative tasks.html Apache Geronimo project overview.html Apache Geronimo V1 - Documentation_attachments Apache Geronimo V1 - Documentation.html Architecture_attachments Architecture.html Authorization - mapping J2EE roles to Principals.html Available login modules.html Backup and recovery.html border Component Configuration.html Concepts.html Configuring LDAP_attachments Configuring LDAP.html Deployer tool.html Deploying configurations and resources.html Deploying secure applications.html Deployment.html Deployment plans.html Development.html documentation_banner.jpg Geronimo Administration Console_attachments Geronimo Administration Console.html Geronimo and JAAS.html Geronimo Login Config Schema.html head_bgstretch_1x86.gif Hints and Tips.html Hot deployment.html icons Implementing security - working examples.html index.html Installation.html JaasLoginService API Discussion.html JBoss to Geronimo - EJB-BMP Migration_attachments JBoss to Geronimo - EJB-BMP Migration.html JBoss to Geronimo - EJB-CMP Migration_attachments JBoss to Geronimo - EJB-CMP Migration.html JBoss to Geronimo - EJB-MDB Migration_attachments JBoss to Geronimo - EJB-MDB Migration.html JBoss to Geronimo - EJB-Session Beans Migration_attachments JBoss to Geronimo - EJB-Session Beans Migration.html JBoss to Geronimo - JCA Migration_attachments JBoss to Geronimo - JCA Migration.html JBoss to Geronimo - JDBC Migration_attachments JBoss to Geronimo - JDBC Migration.html JBoss to Geronimo - Security Migration_attachments JBoss to Geronimo - Security Migration.html JBoss to Geronimo - Servlets and JSPs Migration_attachments JBoss to Geronimo - Servlets and JSPs Migration.html JBoss to Geronimo - Web Services Migration_attachments JBoss to Geronimo - Web Services Migration.html left.html Login into Geronimo.html main.html Maintenance.html Mapping J2EE Roles in M5 release.html Migrating to Apache Geronimo.html Performance and high availability.html Quick start - Apache Geronimo for the impatient_attachments Quick start - Apache Geronimo for the impatient.html Security Definition Schema.html Security.html styles Tools and commands.html top.html Troubleshooting.html - Chris
