Re: GBean for auto generation of primary key
Hello Rakesh, It is definitively useful. Dain has already created a JIRA for this issue: http://issues.apache.org/jira/browse/GERONIMO-1133. To contribute your custom PrimaryKeyGenerator, you need to attach to this JIRA your implementation and select the Grant license to ASF... radio button. Ideally, we want to support out-of-the-box an UUID pk generator. This means that we want an additional choice element to the key-generatorType type defined by openejb-pkgen-2.0.xsd and push the pk generator implementation to TranQL. If you want to add out-of-the-box support, I am happy to provide more directions. If you are too busy right now, simply attach your current impl. and we will take care of it. Thanks, Gianny Ranjan, Rakesh (Cognizant) wrote: Hi Dims, I didn’t got your reply to my mail. Today I checked this thread. If you think this would be useful for the community, I will upload the related files. But I don’t know how to upload and what should be the format. Can u please guide me? Regards 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
[jira] Commented: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails
[ http://issues.apache.org/jira/browse/GERONIMO-1412?page=comments#action_12361588 ] Jakob Færch commented on GERONIMO-1412: --- I am NOT able to reproduce this issue. It was originally observed on a build from source sometime around december 10th. Using the 1.0 release candidate build, things seem to work as expected. I might have somehow been using a wrong OpenEJB version still containing the GERONIMO-598. This issue should be cancelled as Non Reproducible. As far as I can tell I am not able to do that; could someone help me out? Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails -- Key: GERONIMO-1412 URL: http://issues.apache.org/jira/browse/GERONIMO-1412 Project: Geronimo Type: Bug Components: OpenEJB Versions: 1.0 Reporter: Jakob Færch 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 sample application): 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. -- 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
Remaining issues on the Adventure Builder sample application (was: Re: [jira] Created: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimar
Jacek Laskowski wrote: Is there anything else before AB is finally run without any errors? How did you find the above one? I can't seem to reproduce it and everything seems to be working fine from my (end-user) perspective. The status for the Adventure Builder is that the application is running without errors. Although, a few issues still remain until the endeveauor can be declared a success. I list these at the end of this mail. Over the next months, unfortunately I won't be able to contribute very much time to the Geronimo project; this means that we need someone to take responsibility for the three issues listed below. === Secure Webservices === The web service enabled session beans BrokerServiceBean, LodgingPOEndpointBean, ActivityPOEndpointBean, AirlinePOEndpointBean and CreditCardEndpointBean need to be secured. The process is described (as implemented in the Sun Appserver) here: http://developers.sun.com/prodtech/appserver/reference/techart/mutual_auth.html I think securing the services should be considered a hard requirement in order to support the Adventure Builder 1.0.3. If we don't want to go through the hassle of securing the web services, a work around would be to instead support Adventure Builder 1.0.1, which doesn't use secure web services. === Supported JRE's? === The Adventure Builder application available at https://blueprints.dev.java.net/adventurebuilder is a Java 1.5 binary and is not built with 1.4 compability. This means that to run the application as-downloaded, you have to start the server in a 1.5 VM. This does seem to work, but I have come across the following problems: - The included daytrader application can't start due to a deserialization problem This might be remedied by somehow using a Geronimo distribution without the Daytrader application - The deployer.jar receives SecurityExceptions when talking to a running server, e.g. to list running modules I guess the alternatives are 1) Straighten out the above issues. I guess other issues might arise - my impression is that Geronimo does not officially support 1.5 VM's 2) Offer a 1.4-build of the Adventure Builder application. This would definitely work, but also to some extent lower the credibility; how should we prove that the application hasn't been tampered with? === Adventure Builder as part of the Geronimo distribution? === It should be possible to download a binary Geronimo distribution including the Adventure Builder and deploy the application to the Geronimo server automatically - or the user should be able to indicate to the installer that the Adventure Builder sample application should be installed. Right now, I am only able to deploy the application when either building the server from source or manually installing artifacts into my local maven repository. The following shows the output from trying to run maven in the sandbox/adventurebuilder directory (with the etc directory checked out): Attempting to download geronimo-derby-1.0.jar. WARNING: Failed to download geronimo-derby-1.0.jar. Attempting to download derby-10.1.1.0.jar. 2092K downloaded Attempting to download activemq-ra-3.2.1.rar. 5067K downloaded Attempting to download geronimo-mail-1.0.jar. WARNING: Failed to download geronimo-mail-1.0.jar. Attempting to download geronimo-javamail-transport-1.0.jar. WARNING: Failed to download geronimo-javamail-transport-1.0.jar. Attempting to download geronimo-javamail_1.3.1_spec-1.0.jar. 106K downloaded Attempting to download geronimo-activation_1.0.2_spec-1.0.jar. 28K downloaded Attempting to download jstl-1.1.1.jar. 20K downloaded Attempting to download standard-1.1.1.jar. 383K downloaded Attempting to download commons-jelly-tags-velocity-1.0.jar. 10K downloaded Attempting to download velocity-1.4.jar. 352K downloaded The build cannot continue because of the following unsatisfied dependencies: geronimo-derby-1.0.jar geronimo-mail-1.0.jar geronimo-javamail-transport-1.0.jar
[jira] Updated: (GERONIMO-1164) Java Adventure Builder Reference application deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1164?page=all ] Jakob Færch updated GERONIMO-1164: -- Attachment: dont-list-my-smtphost.patch Attaching dont-list-my-smtphost.patch to replace the name of my corporate smtp host with the value YOUR.VALID.SMTPHOST in project.properties Java Adventure Builder Reference application deployment --- Key: GERONIMO-1164 URL: http://issues.apache.org/jira/browse/GERONIMO-1164 Project: Geronimo Type: Task Components: sample apps Reporter: Jacek Laskowski Assignee: Jacek Laskowski Fix For: 1.1 Attachments: adventure1.0.3-built-with-jdk-1.4.2.zip, adventurebuilder1.0.3-geronimo-deployment-plans.zip, dont-list-my-smtphost.patch, jrf-20060102.patch, jrf-patch-partially-20051219-2.patch, jrf-patch-partially-20051219-3.patch, jrf-patch-partially-20051219.patch, jrf-patch-partially-20051220.patch, jrf-patch-partially-20051222.patch It's finally the time to see Java Adventure Builder Reference application running in Geronimo. This task is to track the progress. Instruction available at http://wiki.apache.org/geronimo/AdventureBuilder This is a sample application brought to you by the Java BluePrints program at Sun Microsystems, Inc. This sample application demonstrates how to use the capabilities of the J2EE 1.4 platform to develop robust, scalable, portable, and maintainable e-business applications and Webservices. It comes with full source code and documentation, so you can experiment with the J2EE technologies and learn how to use them effectively to build your own enterprise solutions. This application also showcases how to use the Webservices technologies in the J2EE 1.4 platform. This version of Adventure Builder Reference application is certified by Application Verification Kit(AVK) for the portablity across J2EE compatible application servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails
[ http://issues.apache.org/jira/browse/GERONIMO-1412?page=all ] Gianny Damour closed GERONIMO-1412: --- Resolution: Cannot Reproduce As requested by Jakob, this issue can be closed. Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails -- Key: GERONIMO-1412 URL: http://issues.apache.org/jira/browse/GERONIMO-1412 Project: Geronimo Type: Bug Components: OpenEJB Versions: 1.0 Reporter: Jakob Færch 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 sample application): 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. -- 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: [jira] Created: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPrimaryKey fails
2006/1/3, Jakob Roesgaard Færch [EMAIL PROTECTED]: I am unable to reproduce the error. I have just added a comment to the Jira requesting that the issue be canceled. Perhaps you could do that? Hi Jakob, I could have done it, but Gianny was faster. Thanks Gianny! Jakob Jacek
Re: Remaining issues on the Adventure Builder sample application (was: Re: [jira] Created: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPri
2006/1/3, Jakob Roesgaard Færch [EMAIL PROTECTED]: Jacek Laskowski wrote: Is there anything else before AB is finally run without any errors? How did you find the above one? I can't seem to reproduce it and everything seems to be working fine from my (end-user) perspective. The status for the Adventure Builder is that the application is running without errors. Hi Jakob, Excellent! That's exactly what I had thought. Let's announce it in another thread. Although, a few issues still remain until the endeveauor can be declared a success. I list these at the end of this mail. Let me go back to them later today (possibly tonight) as I'm unable to look into them closer (have a meeting soon). Over the next months, unfortunately I won't be able to contribute very much time to the Geronimo project; this means that we need someone to take responsibility for the three issues listed below. Don't worry about it. You did an extremally good job! You deserves my special thanks for your contribution and I think you're on a good way to become a Apache Geronimo committer. I think the goal of the exercise was simple, but only a few could make it happen and you were the most dedicated person to have worked on it. Thank you Jakob for your hard work (am I repeating myself?) ! I'm going to report the items in JIRA and let others to work on it. They shouldn't be very hard to complete, but as you expressed they would position us on a better place. So, let me comment on them later today. Cheers, Jacek
Java AdventureBuilder application deployment
Hi
Iam trying to distribute the Java Adventure Builder into Geronimo1.0,
Ihave some problemin the distribution of Order Processing Center (opc)
It shows this error
Unable to set attribute port to ${smtpPort}org.apache.geronimo.common.DeploymentException: Unable to set attribute port to ${smtpPort}
How toset the attributeport to Smtp port?
following is a snippet from my opc1.2.3.ear-plan.xml
gbean name=mail/MailSession class=org.apache.geronimo.mail.MailGBean attribute name=host${smtpHost}/attribute attribute name=properties
mail.from=${smtpFrom}mail.smtp.port=${smtpPort}/attribute /gbean gbean name=mail/MailSession class=org.apache.geronimo.mail.SMTPTransportGBean attribute name=host${smtpHost}/attribute
attribute name=port${smtpPort}/attribute attribute name=from${smtpFrom}/attribute /gbean
anything is wrong in above code?
Thanks in Advance
/ram
Re: Java AdventureBuilder application deployment
ram me wrote:
I am trying to distribute the Java Adventure Builder into Geronimo1.0,
Interesting - it's exciting to see if the deployment can be reproduced.
I have some problem in the distribution of Order Processing Center (opc)
It shows this error
Unable to set attribute port to ${smtpPort}
org.apache.geronimo.common.DeploymentException: Unable to set attribute
port to ${smtpPort}
The ${smtpPort} value is intended to be replaced with the value of
smtpPort from the project.properties file.
Do you use the plans from sandbox/adventurebuilder in a source checkout?
You should be able to issue the command
maven -o
in a prompt in the adventurebuilder directory; this will replace the
values automatically.
Please let the list know if this helps.
Kindly,
Jakob
Re: HEAD is going to be...?
Typically it's for all releases, until someone else volunteers for a specific version(s). for example we have two different people for Axis1 and Axis2. So either way is ok. -- dims On 1/1/06, Aaron Mulder [EMAIL PROTECTED] wrote: On 1/1/06, Alan D. Cabrera [EMAIL PROTECTED] wrote: trunk will be 1.1 branches/1.0 will be 1.0.1 Sounds good. Which one are you the release manager for? Or both? Thanks, Aaron -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Closed: (GERONIMO-264) exceptions being swallowed at startup
[ http://issues.apache.org/jira/browse/GERONIMO-264?page=all ] toby cabot closed GERONIMO-264: --- exceptions being swallowed at startup - Key: GERONIMO-264 URL: http://issues.apache.org/jira/browse/GERONIMO-264 Project: Geronimo Type: Improvement Components: deployment Versions: 1.0-M2 Environment: fedora core 2 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Reporter: toby cabot Assignee: Aaron Mulder Priority: Minor Fix For: 1.0-M4 Attachments: Daemon-1_9-diff.txt, Daemon-56609-diff.txt, Daemon-r159681-diff.txt, daemon-log.diff, daemon-log.diff, log.txt some exceptions that are thrown during startup are swallowed and don't show up in the logs. i'm at the 'monkey and typewriter' stage of the geronimo learning curve so i'm a good randomness injector. i had a problem where geronimo would try to start up and then go directly to shutdown for no apparent reason. actually, i think i've had a few: 15:50:17,290 DEBUG [GBeanMBean] geronimo.config:name=skeleton/RA State changed from stopped to starting 15:50:17,292 DEBUG [Configuration] ClassPath for skeleton/RA resolved to [file:/home/tcabot/try/incubator-geronimo/target/config-store/8/connector/skeleton-ra.jar] ra test setting configParameter to NewStringValue 15:50:17,737 DEBUG [SpreadManagedConnectionFactory] BaseManagedConnectionFactory() 15:50:17,737 DEBUG [SpreadManagedConnectionFactory] SpreadManagedConnectionFactory() 15:50:18,425 DEBUG [GBeanMBean] geronimo.config:name=skeleton/RA State changed from starting to failed 15:50:18,426 INFO [Kernel] Starting kernel shutdown i'll include a patch that logs the problem in the catch clause in Configuration.doStart(). There might be better places to do this, but as long as it gets done *somewhere* i'm happy. regards, toby -- 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
Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
forwarding this on behalf of Matt... - sachin Begin forwarded message:From: Matt Hogstrom [EMAIL PROTECTED]Date: January 3, 2006 9:47:28 AM ESTTo: [EMAIL PROTECTED]Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it?Date: Tue, 03 Jan 2006 09:21:30 -0500From: Matt Hogstrom [EMAIL PROTECTED]To: dev@geronimo.apache.orgAll,We have had the last candidate out and available since 12/22. I personally havehad a chance to put the 12/22 build under performance stress and I'm satisfiedthat the build is stable and runs in a variety of modes using DayTrader.Despite the Christmas Holidays I have seen some traffic related to htis releaseon the list so some folks have been kicking it around as well. At this time I'dlike to call a vote to release 1.0.[ ] +1 Release 1.0[ ] -1 Do not release 1.0 (Reasons included)Looks like we got through the last remaining significant bugs and thansk to allwho worked up to the end to get this release out there.Matt
Assistance with ActiveMQ milestone release
Hi fellow Geronimoers, ActiveMQ is planing to do it's first milestone release while it's in the incubator. Since you guys have done this before, I'm hoping you guys can recall what the gotchas were and/or have a tips on doing a good release. I also have some questions: - Can I use the maven jar:deploy mechanism to do the release? - Do the artifacts need to have the incubator in the file name? - I've heard that releases need to be signed, I guess Alan can help with that. But does mean that Alan has to do the release? - Do we have to and how so we use the apache mirrors when we advertise that the release is available. I'm sure I'll think of of some more later. Thanks, Hiram
[jira] Assigned: (GERONIMODEVTOOLS-29) The installableruntime feature requires a possibly broken plugin
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-29?page=all ] Sachin Patel reassigned GERONIMODEVTOOLS-29: Assign To: Sachin Patel The installableruntime feature requires a possibly broken plugin Key: GERONIMODEVTOOLS-29 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-29 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1 (Build: M20050929-0840) Eclipse command: eclipse -clean -vmargs -Xms64m -Xmx512m Java SE Version: 1.4.2_10-b03 OS: Ubuntu Breezy GNU/Linux Reporter: Daniel S. Haischt Assignee: Sachin Patel The installableruntime feature currently searches for a plugin called ... - org.apache.geronimo.j2ee.server.v1 ... which is not contained within der Geronimo WTP adapter distribution (i.e. the ZIP that can be downloaded). As a result one can't use this Eclipse feature. -- 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] Resolved: (GERONIMODEVTOOLS-29) The installableruntime feature requires a possibly broken plugin
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-29?page=all ] Sachin Patel resolved GERONIMODEVTOOLS-29: -- Resolution: Fixed This is now fixed. This zip distribution no longer contains the installableruntime feature and its plugin. This feature is only intented to be used by the downloadable runtime support in WTP. The installableruntime feature requires a possibly broken plugin Key: GERONIMODEVTOOLS-29 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-29 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1 (Build: M20050929-0840) Eclipse command: eclipse -clean -vmargs -Xms64m -Xmx512m Java SE Version: 1.4.2_10-b03 OS: Ubuntu Breezy GNU/Linux Reporter: Daniel S. Haischt Assignee: Sachin Patel The installableruntime feature currently searches for a plugin called ... - org.apache.geronimo.j2ee.server.v1 ... which is not contained within der Geronimo WTP adapter distribution (i.e. the ZIP that can be downloaded). As a result one can't use this Eclipse feature. -- 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: Assistance with ActiveMQ milestone release
Hiram, Here are some reading material for background reading: - http://incubator.apache.org/incubation/Incubation_Policy.html#Releases - http://www.google.com/search?hl=enq=%22Release+Manager%22+site%3Aapache.org Also see below On 1/3/06, Hiram Chirino [EMAIL PROTECTED] wrote: Hi fellow Geronimoers, ActiveMQ is planing to do it's first milestone release while it's in the incubator. Since you guys have done this before, I'm hoping you guys can recall what the gotchas were and/or have a tips on doing a good release. I also have some questions: - Can I use the maven jar:deploy mechanism to do the release? Am not sure, we usually create artifacts and then drop them into locations on minotaur.apache.org - Do the artifacts need to have the incubator in the file name? See url link above. - I've heard that releases need to be signed, I guess Alan can help with that. But does mean that Alan has to do the release? Typically the release manager signs the release. You can get yourself a key too. - Do we have to and how so we use the apache mirrors when we advertise that the release is available. Yes, you do have to use apache mirrors. See http://www.apache.org/dev/#mirror for more info. I'm sure I'll think of of some more later. Thanks, Hiram -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
[-1] I'd like to see 1404 fixed. This invalidates the help displayed. This also has a slight impact on tooling since the default output does not display correctly in the Eclipse console view. Thus the default output in tooling needs to be INFO and currently this cannot be set. On Jan 3, 2006, at 9:48 AM, Sachin Patel wrote:forwarding this on behalf of Matt... - sachin Begin forwarded message:From: Matt Hogstrom [EMAIL PROTECTED]Date: January 3, 2006 9:47:28 AM ESTTo: [EMAIL PROTECTED]Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it?Date: Tue, 03 Jan 2006 09:21:30 -0500From: Matt Hogstrom [EMAIL PROTECTED]To: dev@geronimo.apache.orgAll,We have had the last candidate out and available since 12/22. I personally havehad a chance to put the 12/22 build under performance stress and I'm satisfiedthat the build is stable and runs in a variety of modes using DayTrader.Despite the Christmas Holidays I have seen some traffic related to htis releaseon the list so some folks have been kicking it around as well. At this time I'dlike to call a vote to release 1.0.[ ] +1 Release 1.0[ ] -1 Do not release 1.0 (Reasons included)Looks like we got through the last remaining significant bugs and thansk to allwho worked up to the end to get this release out there.Matt
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
Sachin, Does the server crash completely, does it not start up at all? if not, it can wait till 1.0.1. If everyone starts -1-ing stuff, we will never ship!. Please consider withdrawing your -1. [X] +1 Release 1.0 thanks, dims On 1/3/06, Sachin Patel [EMAIL PROTECTED] wrote: [-1] I'd like to see 1404 fixed. This invalidates the help displayed. This also has a slight impact on tooling since the default output does not display correctly in the Eclipse console view. Thus the default output in tooling needs to be INFO and currently this cannot be set. On Jan 3, 2006, at 9:48 AM, Sachin Patel wrote: forwarding this on behalf of Matt... - sachin Begin forwarded message: From: Matt Hogstrom [EMAIL PROTECTED] Date: January 3, 2006 9:47:28 AM EST To: [EMAIL PROTECTED] Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it? Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] To: dev@geronimo.apache.org All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Looks like we got through the last remaining significant bugs and thansk to all who worked up to the end to get this release out there. Matt -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
[X] +1 Release 1.0 Davanum Srinivas wrote: Sachin, Does the server crash completely, does it not start up at all? if not, it can wait till 1.0.1. If everyone starts -1-ing stuff, we will never ship!. Please consider withdrawing your -1. [X] +1 Release 1.0 thanks, dims On 1/3/06, Sachin Patel [EMAIL PROTECTED] wrote: [-1] I'd like to see 1404 fixed. This invalidates the help displayed. This also has a slight impact on tooling since the default output does not display correctly in the Eclipse console view. Thus the default output in tooling needs to be INFO and currently this cannot be set. On Jan 3, 2006, at 9:48 AM, Sachin Patel wrote: forwarding this on behalf of Matt... - sachin Begin forwarded message: From: Matt Hogstrom [EMAIL PROTECTED] Date: January 3, 2006 9:47:28 AM EST To: [EMAIL PROTECTED] Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it? Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] To: dev@geronimo.apache.org All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Looks like we got through the last remaining significant bugs and thansk to all who worked up to the end to get this release out there. Matt -- Davanum Srinivas : http://wso2.com/blogs/
offline deployment?
Hi Folks, I guess it's possible that I'm the only person that used offline deployment, at least I don't see a lot of people clamoring to bring it back. It's very useful for me, though, so I'd like to find out if there's a possibility of bringing it back onto HEAD (and hopefully the 1.0 branch, too). I'll probably need to hack something for my needs but I'd just as soon do it in a way that's Geronimo-savvy. From discussion on this list it looks as if the preferred approach is to try to use the same approach that the build-time maven plugins do. From my naive reading of the code, it looks as if that happens in two passes: first the geronimo-packaging-plugin takes a deployable resource (ear, war, etc) and generates a configuration archive from that, then the geronimo-assembly-plugin moves the car into the ConfigurationStore. The configurations are mentioned in config.xml (hand-coded?) which causes them to get started when Geronimo runs. I see notes in the code that the packaging plugin uses the Maven repository, so in order to work on machines without Maven I imagine that we'd need to use the Geronimo repository instead. Is this more-or-less on the right track? I'd appreciate any tips or pointers, especially if I'm about to head off in the wrong direction. Thanks, Toby
[jira] Commented: (GERONIMODEVTOOLS-30) After having installed the Geronimo WTP adapter for Eclipse, the features are de-activated by default
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-30?page=comments#action_12361642 ] Sachin Patel commented on GERONIMODEVTOOLS-30: -- But when you try to use the features of the plugin, what happens? (i.e define a geronimo runtime). Not starting the configuration is the correct behavior for performance reasons. Plugins should only start when needed. So I think the WSMO plugin may be loading extension points too early perhaps. As long as the plugin starts when needed, this is the correct behavior. After having installed the Geronimo WTP adapter for Eclipse, the features are de-activated by default - Key: GERONIMODEVTOOLS-30 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-30 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Eclipse 3.1.1 (Build: M20050929-0840) Eclipse command: eclipse -clean -vmargs -Xms64m -Xmx512m Java SE Version: 1.4.2_10-b03 OS: Ubuntu Breezy GNU/Linux Reporter: Daniel S. Haischt After having installed the WTP adapter for Eclipse (i.e. by extracting the ZIP), the corresponding features are de-activated by default if one opens his Eclipse configuration. As a result they need to be activated manually. This even happens if starting Eclipse with the -clean option. -- 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: [Fwd: [Vote] 1.0 Release - Do we ship it?]
[+1] I'll withdraw my -1. 1.0.1 is fine for 1404. - sachin On Jan 3, 2006, at 10:25 AM, Davanum Srinivas wrote: Sachin, Does the server crash completely, does it not start up at all? if not, it can wait till 1.0.1. If everyone starts -1-ing stuff, we will never ship!. Please consider withdrawing your -1. [X] +1 Release 1.0 thanks, dims On 1/3/06, Sachin Patel [EMAIL PROTECTED] wrote: [-1] I'd like to see 1404 fixed. This invalidates the help displayed. This also has a slight impact on tooling since the default output does not display correctly in the Eclipse console view. Thus the default output in tooling needs to be INFO and currently this cannot be set. On Jan 3, 2006, at 9:48 AM, Sachin Patel wrote: forwarding this on behalf of Matt... - sachin Begin forwarded message: From: Matt Hogstrom [EMAIL PROTECTED] Date: January 3, 2006 9:47:28 AM EST To: [EMAIL PROTECTED] Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it? Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] To: dev@geronimo.apache.org All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Looks like we got through the last remaining significant bugs and thansk to all who worked up to the end to get this release out there. Matt -- Davanum Srinivas : http://wso2.com/blogs/
Re: back from hols...
Jules Gosnell wrote: Jeff Genender wrote: Hi Jules, and welcome back... I think Geronimo integration needs some open discussion. I think there is general consensus of a wadi configuration and a common geronimo-web.xml integration. I think there is significant discussion on gbean-izing the Spring configuration for Geronimo. yes, but I am not keen on making any further changes until what we currently have works. This is a Geronimo issue, not WADI. This should not affect the WADI base whatsoever. The GBeans belong in Geronimo...so I don't think this applies here. There is no reason to wait on this. I am CCing the G dev lists with this email. I am working on making it work. I have it working in G/Tomcat. I can tell you how. I will report back to the list when I have results. After that, I will be open to debate on how we go forward. Being that this is Geronimo based discussion, this debate belongs on the Geronimo lists as well as WADI. The Geronimo folks need their input on this. They should decide on whether we have a common WADI config, which IIUC is the general direction and advocation of some of the G team. We also need to discuss the steps for moving the code base. well, I guess we have delegated that decision to the incubator folks now... We have delegated the decision for history, not moving what's at HEAD. That is up to us at the moment. Bill has already done some significant work, along with working with the Active Cluster guys and submitting patches, etc. We need to somehow merge from what Bill has done in Apache with the Codehaus stuff. Thanks Bill, Why don't we just leave it to Bill to check it in to codehaus ? Is this not opened up for discussion? It was my understanding that we will not be using Codehaus anymore...that we will merge this week. Is there a different plan? I understood that this week would be the official move. Do you have a different plan or a plan that works and is agreed to by the team? Bill - are there any issues ? If we are talking AMQ4, then, I guess we will need a new module - as until Geronimo moves onto AMQ4, we will have to support both 3 and 4. I was already preparing to split out AMQ3 into another module anyway... IMHO, we are doing this in Apache, am I missing something here? I also think we need to discuss this decision if we are going to support both AMQ3 and 4. I think there are a number of folks who want their input on this. Code movement is waiting on the incubator list. Again..its not... History is waiting on the incubator list...not HEAD. Also, this will probably be moot of we repackage to org.apache.wadi. I don't see much point in moving the website until the code is moved, since the website is generated from the code and is full of references to e.g. mailing lists, code repos etc. Based on JIRA issue WADI-13 in Codehaus, I think you had better rethink this decision. The Apache code has the proper mail-lists, etc...thus the new web site is correct. The Apache WADi incubator site is complete, the Codehaus version is not...it broke when you deployed it before the holidays. We *really* need to talk about a merge here. Has there been any movement on importing mailing list archives ? I see this as an important step in completing the xfer of the mailing lists. IMHO there is little value to holding up the move based on this. The WADI codehaus mailing lists do not have very much history at all and at the very minimum, we have GMane. Lets not make this a sticking point. Jules Thanks and we look forward to getting this incubator project running full speed ahead. Jeff Jules Gosnell wrote: I'm back. I'm throwing all my time at sorting out the Geronimo integration and WADI fn-ality for a few days. I have joined the history thread on incubator.general. I will pick up threads on this list over the next couple of days. I hope everybody had a good xmas and new year. Jules
[jira] Resolved: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ] Sachin Patel resolved GERONIMO-1399: Resolution: Fixed Assign To: Sachin Patel Fixed by pointing to jsr88 jar. DeploymentFactory-Implementation-Class property missing from deployer.jar manifest -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: deployment Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun Assignee: Sachin Patel Fix For: 1.0 On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1404) Can't set server startup verbosity to INFO
[ http://issues.apache.org/jira/browse/GERONIMO-1404?page=all ] Alan Cabrera updated GERONIMO-1404: --- Fix Version: (was: 1.0) Not a show stopper Can't set server startup verbosity to INFO -- Key: GERONIMO-1404 URL: http://issues.apache.org/jira/browse/GERONIMO-1404 Project: Geronimo Type: Bug Components: startup/shutdown Versions: 1.0 Reporter: Sachin Patel Starting the server with the verbosity option dones't work correctly. Regardless of the value specified (-v or -vv), the verbosity is always DEBUG. -- 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: using Java 5 for java.util.concurrent annotations and then generating 1.4 compliant jars?
How does this affect debugging? Regards, Alan On 1/3/2006 8:39 AM, Aaron Mulder wrote: That sounds pretty interesting -- does it really fully handle annotations? I thought some of those could be inspected at runtime and I'm not sure how that could be supported in 1.4, but I really don't know that much about it. On a similar note, it would be great if someone could look into why DayTrader blows up if run under 1.5. Aaron On 12/30/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: First a quick bit of background on why Retrotranslator rocks... http://radio.weblogs.com/0112098/2005/12/29.html#a546 Retrotranslator can take any Java 5 bytecode using generics, annotations, auto-boxing, varargs java.util.concurrent utilities and generate regular 1.4 bytecode that runs just fine on Java 1.4. The 1.4 bytecode uses backport-util-concurrent.jar for the java.util.concurrent stuff, retrotranslator_runtime.jar for other new methods added to Java 5 such as new reflection/generics stuff and asm.jar is currently used to read the annotations. So if you only use the Java 5 concurrent APIs then the only new dependency added on 1.4 is backport-util-concurrent. We should be able to create a maven 2 plugin (I've already started) which uses Java 5 for the build to make a Java 5 binary but also creates a 1.4 compliant binary. http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/retrotranslator- maven-plugin/ We should hopefully be able to run tests against both JVMs for each binary too. Now given that Java 5 concurrent is faster than backport-util- concurrent.jar concurrent.jar it would be good for us to use this by default throughout the Geronimo family of projects. Similarly it would be extremely useful to start using annotations and generics the new for loop can be handy too. So I wonder; should we experiment with 1 module using Java 5 and creating a 1.4 binary jar? (I'm quite tempted to try this in ActiveMQ to see how it goes). If we start with just the java.util.concurrent - backport.util.concurrent it'd be fairly easy to switch back again later if we hit some showstopper. Thoughts? James --- http://radio.weblogs.com/0112098/
[jira] Updated: (GERONIMO-1413) Console needs to set JSP and Servlet contentType to UTF-8
[ http://issues.apache.org/jira/browse/GERONIMO-1413?page=all ] Donald Woods updated GERONIMO-1413: --- Attachment: Geronimo-1413.patch Console patch against latest AG 1.0 from 20051221 attached Console needs to set JSP and Servlet contentType to UTF-8 - Key: GERONIMO-1413 URL: http://issues.apache.org/jira/browse/GERONIMO-1413 Project: Geronimo Type: Bug Components: console Versions: 1.0 Environment: AG 1.0 on non-Latin charset machines Reporter: Donald Woods Priority: Minor Attachments: Geronimo-1413.patch JSP pages and Portal JSP fragment wrapper need to set contentType=text/html; charset=UTF-8 so users that are using a non-Latin based charset locale (aka double-byte character sets) can display the pages correctly. Also, the web.xml needs to be updated so the Servlet provides content and expects forms encoded as UTF8. -- 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: Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
If this is the same one we worked on week before last, it did pass the TCK. Alan D. Cabrera wrote: Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Does it pass the TCK? I will vote no until it does. Regards, Alan
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
+1 to releasedavid jencksOn Jan 3, 2006, at 6:48 AM, Sachin Patel wrote:forwarding this on behalf of Matt... - sachin Begin forwarded message:From: Matt Hogstrom [EMAIL PROTECTED]Date: January 3, 2006 9:47:28 AM ESTTo: [EMAIL PROTECTED]Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it?Date: Tue, 03 Jan 2006 09:21:30 -0500From: Matt Hogstrom [EMAIL PROTECTED]To: dev@geronimo.apache.orgAll,We have had the last candidate out and available since 12/22. I personally havehad a chance to put the 12/22 build under performance stress and I'm satisfiedthat the build is stable and runs in a variety of modes using DayTrader.Despite the Christmas Holidays I have seen some traffic related to htis releaseon the list so some folks have been kicking it around as well. At this time I'dlike to call a vote to release 1.0.[ ] +1 Release 1.0[ ] -1 Do not release 1.0 (Reasons included)Looks like we got through the last remaining significant bugs and thansk to allwho worked up to the end to get this release out there.Matt
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
On 1/3/06, Sachin Patel [EMAIL PROTECTED] wrote: We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) +1 Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo (http://geronimo.apache.org/)
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
[X] +1 Release 1.0--kevanOn Jan 3, 2006, at 9:48 AM, Sachin Patel wrote:forwarding this on behalf of Matt... - sachin Begin forwarded message:From: Matt Hogstrom [EMAIL PROTECTED]Date: January 3, 2006 9:47:28 AM ESTTo: [EMAIL PROTECTED]Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it?Date: Tue, 03 Jan 2006 09:21:30 -0500From: Matt Hogstrom [EMAIL PROTECTED]To: dev@geronimo.apache.orgAll,We have had the last candidate out and available since 12/22. I personally havehad a chance to put the 12/22 build under performance stress and I'm satisfiedthat the build is stable and runs in a variety of modes using DayTrader.Despite the Christmas Holidays I have seen some traffic related to htis releaseon the list so some folks have been kicking it around as well. At this time I'dlike to call a vote to release 1.0.[ ] +1 Release 1.0[ ] -1 Do not release 1.0 (Reasons included)Looks like we got through the last remaining significant bugs and thansk to allwho worked up to the end to get this release out there.Matt
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
2006/1/3, Sachin Patel [EMAIL PROTECTED]: [X] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Jacek
Re: Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
+1 Release 1.0 Regards, Alan On 1/3/2006 10:11 AM, Jeff Genender wrote: If this is the same one we worked on week before last, it did pass the TCK. Alan D. Cabrera wrote: Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Does it pass the TCK? I will vote no until it does. Regards, Alan
Re: Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
+1 Release 1.0 Regards, Alan On 1/3/2006 10:11 AM, Jeff Genender wrote: If this is the same one we worked on week before last, it did pass the TCK. Alan D. Cabrera wrote: Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Does it pass the TCK? I will vote no until it does. Regards, Alan
[jira] Closed: (GERONIMO-1399) DeploymentFactory-Implementation-Class property missing from deployer.jar manifest
[ http://issues.apache.org/jira/browse/GERONIMO-1399?page=all ] Lin Sun closed GERONIMO-1399: - Verified it is fixed and I can deploy the hello program now. DeploymentFactory-Implementation-Class property missing from deployer.jar manifest -- Key: GERONIMO-1399 URL: http://issues.apache.org/jira/browse/GERONIMO-1399 Project: Geronimo Type: Bug Components: deployment Versions: 1.0 Environment: Geronimo 1.0, built a few days ago Eclipse SDK 3.1.1 WTP 1.0 RC 5 and its prerequisites Eclipse plug-in, built a few days ago Reporter: Lin Sun Assignee: Sachin Patel Fix For: 1.0 On Dec 22, 2005, at 4:48 PM, Lin Sun wrote: Thanks. After you point out where the log is, I saw the following in the .log file: java.lang.NullPointerException at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java(Compiled Code)) at org.apache.geronimo.core.GeronimoConnectionFactory.discoverDeploymentF actory(GeronimoConnectionFactory.java:78) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManage r(GeronimoConnectionFactory.java:45) at org.apache.geronimo.core.CommandLauncher.setDeploymentManager (CommandLauncher.java:87) at org.apache.geronimo.core.CommandLauncher.executeCommand (CommandLauncher.java:61) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy (GeronimoServerBehaviour.java:233) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeComman d(GeronimoServerBehaviour.java:207) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModul e(GeronimoServerBehaviour.java:194) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul e(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModul es(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish (ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish (Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java: 788) at org.eclipse.wst.server.core.internal.PublishServerJob.run (PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) --- Sachin Patel [EMAIL PROTECTED] wrote: Nevermind, I found the problem. In the future, eclipse plugin errors/ exceptions can be found in the .log in the workspace metadata. So you shouldn't just look for errors in the geronimo log. I just published and found a NPE attempting to discover the deploymentFactory. Something must have changed in the runtime that broke me... I'll look into it. - sachin On Dec 22, 2005, at 4:21 PM, Sachin Patel wrote: Ok, then please describe your steps, from project creation, to deployment. - sachin Steps: 1) launch eclipse using eclipse -clean and use a brand new workspace 2) change to J2EE view. Define a geronimo server and start it. 3) right click dynamic web projects and select import to import the hello.war file. Select default/next for everything except uncheck the add module to an ear application checkbox. 4) right click the hello folder and select run as--run on server. then I got the unable to publish error immediately. I'll send you the hello.war file in a seperate note to reduce the size of the email to the list. Thanks, Lin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1414) Console About page does not set the shortcut icon
Console About page does not set the shortcut icon - Key: GERONIMO-1414 URL: http://issues.apache.org/jira/browse/GERONIMO-1414 Project: Geronimo Type: Bug Components: console Versions: 1.0 Environment: Latest AG 1.0 branch from 20051221 Reporter: Donald Woods Priority: Trivial Attachments: Geronimo-1414.patch The SHORTCUT ICON is not being set to the favicon.ico for the About page. The Login and Portal pages are setting it correctly, so this update is just for consistantcy. -- 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-1164) Java Adventure Builder Reference application deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1164?page=comments#action_12361671 ] Jacek Laskowski commented on GERONIMO-1164: --- Applied. Sendingproject.properties Transmitting file data . Committed revision 365738. Java Adventure Builder Reference application deployment --- Key: GERONIMO-1164 URL: http://issues.apache.org/jira/browse/GERONIMO-1164 Project: Geronimo Type: Task Components: sample apps Reporter: Jacek Laskowski Assignee: Jacek Laskowski Fix For: 1.1 Attachments: adventure1.0.3-built-with-jdk-1.4.2.zip, adventurebuilder1.0.3-geronimo-deployment-plans.zip, dont-list-my-smtphost.patch, jrf-20060102.patch, jrf-patch-partially-20051219-2.patch, jrf-patch-partially-20051219-3.patch, jrf-patch-partially-20051219.patch, jrf-patch-partially-20051220.patch, jrf-patch-partially-20051222.patch It's finally the time to see Java Adventure Builder Reference application running in Geronimo. This task is to track the progress. Instruction available at http://wiki.apache.org/geronimo/AdventureBuilder This is a sample application brought to you by the Java BluePrints program at Sun Microsystems, Inc. This sample application demonstrates how to use the capabilities of the J2EE 1.4 platform to develop robust, scalable, portable, and maintainable e-business applications and Webservices. It comes with full source code and documentation, so you can experiment with the J2EE technologies and learn how to use them effectively to build your own enterprise solutions. This application also showcases how to use the Webservices technologies in the J2EE 1.4 platform. This version of Adventure Builder Reference application is certified by Application Verification Kit(AVK) for the portablity across J2EE compatible application servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: POP3 and IMAP support
On 1/3/06, Rajith Attapattu [EMAIL PROTECTED] wrote: I was wondering what the current status is for IMAP?? I have begun working on the IMAP transport, but there's still much work to be done. I will work on the remaining issues of the POP3 implementation. Dain when are u going to apply the patch (with the POP3 impl) ?? I assume it's after 1.0 release. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo (http://geronimo.apache.org/)
Re: POP3 and IMAP support
I have implemented most of store, folder and message. Currently working on the multipart messages. Didn't get much done during the holidays but hopefully I'll get a chance to work on it this week. bilal I was wondering what the current status is for IMAP?? I will work on the remaining issues of the POP3 implementation. Dain when are u going to apply the patch (with the POP3 impl) ?? I assume it's after 1.0 release. Regards, Rajith Attapattu. -- bilal - We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about. - Einstein
Re: Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
+1 for Releasing 1.0 Regards, John
[jira] Created: (GERONIMO-1415) [Adventure Builder] Configure Mutual Authentication for Web Services
[Adventure Builder] Configure Mutual Authentication for Web Services Key: GERONIMO-1415 URL: http://issues.apache.org/jira/browse/GERONIMO-1415 Project: Geronimo Type: Improvement Components: sample apps Versions: 1.1 Reporter: Jacek Laskowski Fix For: 1.1 Configure Adventure Builder as described in http://developers.sun.com/prodtech/appserver/reference/techart/mutual_auth.html. -- 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: Remaining issues on the Adventure Builder sample application (was: Re: [jira] Created: (GERONIMO-1412) Create followed by findByPrimaryKey in same transaction ctx, caller in another jar: FindByPri
2006/1/3, Jakob Roesgaard Færch [EMAIL PROTECTED]: === Secure Webservices === The web service enabled session beans BrokerServiceBean, LodgingPOEndpointBean, ActivityPOEndpointBean, AirlinePOEndpointBean and CreditCardEndpointBean need to be secured. The process is described (as implemented in the Sun Appserver) here: http://developers.sun.com/prodtech/appserver/reference/techart/mutual_auth.html I think securing the services should be considered a hard requirement in order to support the Adventure Builder 1.0.3. If we don't want to go through the hassle of securing the web services, a work around would be to instead support Adventure Builder 1.0.1, which doesn't use secure web services. Hi Jakob, I'm sure you'll forgive me, but I don't think it's that much important. I think not many end users will go up to this point and see how it works in a secured environment. It'd be very nice to have, but it should not hold us from announcing that Adventure Builder can finally be deployed and run in Apache Geronimo. I created a JIRA improvement for it to keep it in mind - http://issues.apache.org/jira/browse/GERONIMO-1415. === Supported JRE's? === The Adventure Builder application available at https://blueprints.dev.java.net/adventurebuilder is a Java 1.5 binary and is not built with 1.4 compability. This means that to run the application as-downloaded, you have to start the server in a 1.5 VM. This does seem to work, but I have come across the following problems: - The included daytrader application can't start due to a deserialization problem This might be remedied by somehow using a Geronimo distribution without the Daytrader application - The deployer.jar receives SecurityExceptions when talking to a running server, e.g. to list running modules I guess the alternatives are 1) Straighten out the above issues. I guess other issues might arise - my impression is that Geronimo does not officially support 1.5 VM's You're right. Although most (if not all) components work on Java 5, but it's not required by J2EE 1.4, which Geronimo's versions up to 1.0 support. 2) Offer a 1.4-build of the Adventure Builder application. This would definitely work, but also to some extent lower the credibility; how should we prove that the application hasn't been tampered with? Absolutely true and no longer necessary. The committed revision 365750 (Exclude geronimo/daytrader-derby-jetty/1.0-SNAPSHOT/car from being run) fixes it. Only these configurations, which provide required services are started. It's a workaround for an issue in Geronimo itself, which we shouldn't have bothered with while working on the sample app. === Adventure Builder as part of the Geronimo distribution? === It should be possible to download a binary Geronimo distribution including the Adventure Builder and deploy the application to the Geronimo server automatically That would indeed be great if we could provide a car with AB. I don't think it's possible because of AB license constraints (I'm not a lawyer so I might possibly be wrong). - or the user should be able to indicate to the installer that the Adventure Builder sample application should be installed. Right now, I am only able to deploy the application when either building the server from source or manually installing artifacts into my local maven repository. I think the committed revision 365764 (Deploy Adventure Builder without having to download the whole source tree (only /etc and /sandbox/adventurebuilder directories are required)) removed the need to download the whole source tree, which should meet the requirements of not-very-willing-to-download users. Cheers, Jacek
[jira] Resolved: (GERONIMO-1164) Java Adventure Builder Reference application deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1164?page=all ] Jacek Laskowski resolved GERONIMO-1164: --- Resolution: Fixed As Jakob wrote: The status for the Adventure Builder is that the application is running without errors. I couldn't have written it better ;) Java Adventure Builder Reference application deployment --- Key: GERONIMO-1164 URL: http://issues.apache.org/jira/browse/GERONIMO-1164 Project: Geronimo Type: Task Components: sample apps Reporter: Jacek Laskowski Assignee: Jacek Laskowski Fix For: 1.1 Attachments: adventure1.0.3-built-with-jdk-1.4.2.zip, adventurebuilder1.0.3-geronimo-deployment-plans.zip, dont-list-my-smtphost.patch, jrf-20060102.patch, jrf-patch-partially-20051219-2.patch, jrf-patch-partially-20051219-3.patch, jrf-patch-partially-20051219.patch, jrf-patch-partially-20051220.patch, jrf-patch-partially-20051222.patch It's finally the time to see Java Adventure Builder Reference application running in Geronimo. This task is to track the progress. Instruction available at http://wiki.apache.org/geronimo/AdventureBuilder This is a sample application brought to you by the Java BluePrints program at Sun Microsystems, Inc. This sample application demonstrates how to use the capabilities of the J2EE 1.4 platform to develop robust, scalable, portable, and maintainable e-business applications and Webservices. It comes with full source code and documentation, so you can experiment with the J2EE technologies and learn how to use them effectively to build your own enterprise solutions. This application also showcases how to use the Webservices technologies in the J2EE 1.4 platform. This version of Adventure Builder Reference application is certified by Application Verification Kit(AVK) for the portablity across J2EE compatible application servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Java Adventure Builder Reference 1.0.3 runs fine in Apache Geronimo
Hi, This is to announce that Java Adventure Builder Reference 1.0.3 deploys and runs fine in Apache Geronimo. The task Java Adventure Builder Reference application deployment (http://issues.apache.org/jira/browse/GERONIMO-1164) is resolved then and will be closed in a few days unless some problems are reported. It turned out to have been an excellent way to engage some people to contribute their time with two outstanding individuals (in random order): * Jakob Færch (Trifork) [EMAIL PROTECTED] * Selvaraj, Saraswathi (Cognizant) [EMAIL PROTECTED] Thank you for all your hard work! Apache Geronimo team
Re: offline deployment?
Will the hot deployment directory satisfy you needs? -dain On Jan 3, 2006, at 7:34 AM, toby cabot wrote: Hi Folks, I guess it's possible that I'm the only person that used offline deployment, at least I don't see a lot of people clamoring to bring it back. It's very useful for me, though, so I'd like to find out if there's a possibility of bringing it back onto HEAD (and hopefully the 1.0 branch, too). I'll probably need to hack something for my needs but I'd just as soon do it in a way that's Geronimo-savvy. From discussion on this list it looks as if the preferred approach is to try to use the same approach that the build-time maven plugins do. From my naive reading of the code, it looks as if that happens in two passes: first the geronimo-packaging-plugin takes a deployable resource (ear, war, etc) and generates a configuration archive from that, then the geronimo-assembly-plugin moves the car into the ConfigurationStore. The configurations are mentioned in config.xml (hand-coded?) which causes them to get started when Geronimo runs. I see notes in the code that the packaging plugin uses the Maven repository, so in order to work on machines without Maven I imagine that we'd need to use the Geronimo repository instead. Is this more-or-less on the right track? I'd appreciate any tips or pointers, especially if I'm about to head off in the wrong direction. Thanks, Toby
Re: using Java 5 for java.util.concurrent annotations and then generating 1.4 compliant jars?
I would love to start using Java 5 as soon as possible. I have been using the backport-util-concurrent package for a while in xbean and the Java 5 interfaces are really nice to use. Above all other features, I would love to have generics support in geronimo. Generics give me much more data when creating collections in the IoC code. Right now, the collection creation code I have is very dumb since it must assume that a collection can contain any object. -dain On Dec 30, 2005, at 9:59 AM, [EMAIL PROTECTED] wrote: First a quick bit of background on why Retrotranslator rocks... http://radio.weblogs.com/0112098/2005/12/29.html#a546 Retrotranslator can take any Java 5 bytecode using generics, annotations, auto-boxing, varargs java.util.concurrent utilities and generate regular 1.4 bytecode that runs just fine on Java 1.4. The 1.4 bytecode uses backport-util-concurrent.jar for the java.util.concurrent stuff, retrotranslator_runtime.jar for other new methods added to Java 5 such as new reflection/generics stuff and asm.jar is currently used to read the annotations. So if you only use the Java 5 concurrent APIs then the only new dependency added on 1.4 is backport-util-concurrent. We should be able to create a maven 2 plugin (I've already started) which uses Java 5 for the build to make a Java 5 binary but also creates a 1.4 compliant binary. http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/ retrotranslator-maven-plugin/ We should hopefully be able to run tests against both JVMs for each binary too. Now given that Java 5 concurrent is faster than backport-util- concurrent.jar concurrent.jar it would be good for us to use this by default throughout the Geronimo family of projects. Similarly it would be extremely useful to start using annotations and generics the new for loop can be handy too. So I wonder; should we experiment with 1 module using Java 5 and creating a 1.4 binary jar? (I'm quite tempted to try this in ActiveMQ to see how it goes). If we start with just the java.util.concurrent - backport.util.concurrent it'd be fairly easy to switch back again later if we hit some showstopper. Thoughts? James --- http://radio.weblogs.com/0112098/
Re: POP3 and IMAP support
On Jan 3, 2006, at 1:07 PM, Rajith Attapattu wrote: Dain when are u going to apply the patch (with the POP3 impl) ?? I assume it's after 1.0 release. I actually forgot about it. I'm kind of in the middle of something, so I won't be able to get to it this week. Bruce, can you apply the patch? -dain
Re: [Fwd: [Vote] 1.0 Release - Do we ship it?]
+1 to release -dain
Re: using Java 5 for java.util.concurrent annotations and then generating 1.4 compliant jars?
I had a quick look at retrotranslator today. Generics and some other language 5.0 features were, as some of you may know, originally developed on a 1.4 JVM. So in principal this is a cool idea and at one point the javac engineer suggested we provide the target 1.4 option. I would probably draw the line at the runtime annotations though myself. Achieving this in retrotranslator requires some involved helper classes which changes the behavior of the app, before you even get to try a debugger on it regards calvin Dain Sundstrom wrote: I would love to start using Java 5 as soon as possible. I have been using the backport-util-concurrent package for a while in xbean and the Java 5 interfaces are really nice to use. Above all other features, I would love to have generics support in geronimo. Generics give me much more data when creating collections in the IoC code. Right now, the collection creation code I have is very dumb since it must assume that a collection can contain any object. -dain On Dec 30, 2005, at 9:59 AM, [EMAIL PROTECTED] wrote: First a quick bit of background on why Retrotranslator rocks... http://radio.weblogs.com/0112098/2005/12/29.html#a546 Retrotranslator can take any Java 5 bytecode using generics, annotations, auto-boxing, varargs java.util.concurrent utilities and generate regular 1.4 bytecode that runs just fine on Java 1.4. The 1.4 bytecode uses backport-util-concurrent.jar for the java.util.concurrent stuff, retrotranslator_runtime.jar for other new methods added to Java 5 such as new reflection/generics stuff and asm.jar is currently used to read the annotations. So if you only use the Java 5 concurrent APIs then the only new dependency added on 1.4 is backport-util-concurrent. We should be able to create a maven 2 plugin (I've already started) which uses Java 5 for the build to make a Java 5 binary but also creates a 1.4 compliant binary. http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/ retrotranslator-maven-plugin/ We should hopefully be able to run tests against both JVMs for each binary too. Now given that Java 5 concurrent is faster than backport-util- concurrent.jar concurrent.jar it would be good for us to use this by default throughout the Geronimo family of projects. Similarly it would be extremely useful to start using annotations and generics the new for loop can be handy too. So I wonder; should we experiment with 1 module using Java 5 and creating a 1.4 binary jar? (I'm quite tempted to try this in ActiveMQ to see how it goes). If we start with just the java.util.concurrent - backport.util.concurrent it'd be fairly easy to switch back again later if we hit some showstopper. Thoughts? James --- http://radio.weblogs.com/0112098/
Re: POP3 and IMAP support
On 1/3/06, Dain Sundstrom [EMAIL PROTECTED] wrote: On Jan 3, 2006, at 1:07 PM, Rajith Attapattu wrote: Dain when are u going to apply the patch (with the POP3 impl) ?? I assume it's after 1.0 release. I actually forgot about it. I'm kind of in the middle of something, so I won't be able to get to it this week. Bruce, can you apply the patch? Yes, what's the number for the JIRA issue? Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo (http://geronimo.apache.org/)
[jira] Created: (GERONIMO-1416) [daytrader] Broken links on benchmarking page
[daytrader] Broken links on benchmarking page - Key: GERONIMO-1416 URL: http://issues.apache.org/jira/browse/GERONIMO-1416 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Reporter: John Sisson Assigned to: John Sisson Priority: Minor The links on the daytrader/docs/benchmarking.html page are broken as they have hrefs starting with /trade/ instead of /daytrader/ . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1417) [daytrader] daytrader/docs/tradeFAQ.html out of date
[daytrader] daytrader/docs/tradeFAQ.html out of date Key: GERONIMO-1417 URL: http://issues.apache.org/jira/browse/GERONIMO-1417 Project: Geronimo Type: Bug Components: sample apps Versions: 1.0 Reporter: John Sisson Priority: Trivial Fix For: 1.1 Issues with daytrader/docs/tradeFAQ.html : * talks about Trade Version 6 and Trade 3. We have versioned it as daytrader 1.0. * talks about WebSphere and IBM * software requirements in installation section needs updating * top right hand corner of scrollable frame has a broken image link pointing to WEBSPHERE_18P_UNIX.GIF The above was observed on the 1.0 release candidate and also appears to be in head. -- 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: Fwd: [Fwd: [Vote] 1.0 Release - Do we ship it?]
[X] +1 Release 1.0 Sachin Patel wrote: forwarding this on behalf of Matt... - sachin Begin forwarded message: From: Matt Hogstrom [EMAIL PROTECTED] Date: January 3, 2006 9:47:28 AM EST To: [EMAIL PROTECTED] Subject: [Fwd: [Vote] 1.0 Release - Do we ship it?] Can you forward thsi for me? I'm still getting SPAM errors. I've sent a note to Ken to see if he can help me decipher what's going on. Original Message Subject: [Vote] 1.0 Release - Do we ship it? Date: Tue, 03 Jan 2006 09:21:30 -0500 From: Matt Hogstrom [EMAIL PROTECTED] To: dev@geronimo.apache.org All, We have had the last candidate out and available since 12/22. I personally have had a chance to put the 12/22 build under performance stress and I'm satisfied that the build is stable and runs in a variety of modes using DayTrader. Despite the Christmas Holidays I have seen some traffic related to htis release on the list so some folks have been kicking it around as well. At this time I'd like to call a vote to release 1.0. [ ] +1 Release 1.0 [ ] -1 Do not release 1.0 (Reasons included) Looks like we got through the last remaining significant bugs and thansk to all who worked up to the end to get this release out there. Matt
Re: GBean for auto generation of primary key
Hi Dims, I didn’t got your reply in my mailbox. Today I checked this thread.Then i come to know that u want me to upload the contribution files.But I don’t know how to upload and what should be the format. Can you please help me? Regards Rakesh Ranjan
problem with Geronimo-1.0
Hi friends,
I am trying to get a reference to Geronimo
TransactionManager. For this, I have done the following things : -
a) Getting a
reference to the kernel using the KernelRegistry class.
b) Then searching
the TransactionManager GBean using a pattern.
c) Finally
getting the TransactionManager reference using the searched Gbean.
Here the code snippet :
Kernel kernel=KernelRegistry.getSingleKernel();
ObjectName gbQuery =
JMXUtil.getObjectName(*:j2eeType=TransactionManager,*);
Set gbeanNames =
kernel.listGBeans(gbQuery);
for (Iterator i = gbeanNames.iterator();
i.hasNext();) {
ObjectName gbeanName
= (ObjectName) i.next();
System.out.println(gbeanName1);
}
TransactionManager tm = (TransactionManager)
kernel.getProxyManager().createProxy(gbeanName, ransactionManager.class);
When I am using this with the Geronimo-1.0-M5, this is working
correctly. But with Geronimo-1.0 , this is not working correctly.
With Geronimo-1.0, I am getting the following Exception :
java.lang.IllegalArgumentException:
Could not get GBeanInfo for target
object:
geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/Server,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
I think kernel.listGBeans() is not working correctly in case
of Geronimo-1.0. According to the above code, the GBean is
geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/Server,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
But as much I know, it should be
geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-server/1.0/car,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
Can anybody please help me whether there is any fault with Geronimo-1.0
or something else.
Regards,
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
[daytrader] 1.0 Release Candidate - get exception when logging in
Hi Matt, I installed the 1.0 release candidate (tomcat build) on Solaris x86. I accessed the daytrader page, clicked on the Go Trade! link and then clicked on the Log in button. I then got a javax.ejb.ObjectNotFoundException stack trace. I found that if I went to the Configuration screen in daytrader and ran the (Re)-populate Trade Database that everything seems to works fine. Is the database meant to be already populated when Geronimo is installed? I was under the impression it should be because the daytrader/docs/tradeFAQ.html file it mentions The Trade database is initially populated ... I also tried building the 1.0.0 tag myself and got the same problem. Regards, John
Re: problem with Geronimo-1.0
Grr, more confidential information footers. Please don't do that to
public mailing lists! If your information is confidential, don't send
it to the world, and if it's not confidential, please don't assault us
with the legalese!
Anyway, now that that's off my chest, Geronimo cannot (well,
definitely *should* not) produce an incorrect ObjectName out of thin
air, so you need to figure out where you're getting the ObjectName
containing org/apache/geronimo/Server from. In the code snippet you
showed, you do a lookup and print all the results, but then you try to
create a proxy using a variable called gbeanName (which I suspect is
what's failing) and you never showed us what that variable holds and
where you got the value in that variable. Maybe it's hardcoded or in
a config file or something? You also didn't should the output of your
program where it prints all the matching transaction manager names.
You also didn't give a proper stack trace. So it's real hard to
troubleshoot from here. You might want to run it under a debugger and
figure out where the o/a/g/Server is coming from.
If none of this helps you figure out what's going on, please post a
more complete chunk of your code, plus all the pertinent output and a
full stack trace. Also, please mention what you've deployed into the
server (if anything) other than this application.
Thanks,
Aaron
On 1/4/06, Ranjan, Rakesh (Cognizant) [EMAIL PROTECTED] wrote:
Hi friends,
I am trying to get a reference to Geronimo TransactionManager. For this, I
have done the following things : -
a) Getting a reference to the kernel using the KernelRegistry class.
b) Then searching the TransactionManager GBean using a pattern.
c) Finally getting the TransactionManager reference using the searched
Gbean.
Here the code snippet :
Kernel kernel=KernelRegistry.getSingleKernel();
ObjectName gbQuery = JMXUtil.getObjectName(*:j2eeType=TransactionManager,*);
Set gbeanNames = kernel.listGBeans(gbQuery);
for (Iterator i = gbeanNames.iterator(); i.hasNext();) {
ObjectName gbeanName = (ObjectName) i.next();
System.out.println(gbeanName1);
}
TransactionManager tm = (TransactionManager)
kernel.getProxyManager().createProxy(gbeanName, ransactionManager.class);
When I am using this with the Geronimo-1.0-M5, this is working correctly. But
with Geronimo-1.0 , this is not working correctly.
With Geronimo-1.0, I am getting the following Exception :
java.lang.IllegalArgumentException:
Could not get GBeanInfo for target object:
geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/Server,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
I think kernel.listGBeans() is not working correctly in case of Geronimo-1.0.
According to the above code, the GBean is
geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/Server,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
But as much I know, it should be
geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-server/1.0/car,J2EEServer=geronimo,j2eeType=TransactionManager,name=TransactionManager
Can anybody please help me whether there is any fault with Geronimo-1.0 or
something else.
Regards,
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
