Re: Does Fedora Core 3/Sun JDK1.5.0 work for anyone?
On Fri, Dec 03, 2004 at 03:34:55PM -0800, Jeremy Boynes wrote: However, if Unix commands like find and rm are dumping then it makes me question if the machine itself is acting up (bad memory or CPU failure). Might be worth it to run http://www.memtest86.com/.
RE: Remove assembly from main build?
+1 -Original Message- From: Dain Sundstrom [mailto:[EMAIL PROTECTED] Sent: Fri 12/3/2004 2:15 PM To: [EMAIL PROTECTED] Cc: Subject: Re: Remove assembly from main build? Ah for got about that idea :) For those that are forgetful like me: http://mail-archives.apache.org/eyebrowse/ReadMsg? [EMAIL PROTECTED]msgNo=10243 So how about we instead move geronimo/modules/assembly to geronimo/distributions/standard, which will leave then name assembly open to the individual configuration modules when we have a tool that can build the configurations one by one. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Dec 3, 2004, at 10:57 AM, Jeremy Boynes wrote: This seems similar to the idea of making each configuration a separate artifact. So rather than one huge assemby module, we would have a separate module (presumably under a different directory than module) for each configuration being generated and then a distribution module that pulls them together into the final package. -- Jeremy Dain Sundstrom wrote: Having the assembly as part of the main build is proving to be very troublesome due to the inter-project dependencies. I propose we move geronimo/modules/assembly to geronimo/assembly/standard. This will allow us room to create produce multiple assembled servers from our build. Unless there is an objection, I'd like to do this this weekend. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26
Re: Does Fedora Core 3/Sun JDK1.5.0 work for anyone?
On Vie, 3 de Diciembre de 2004, 18:05, toby cabot dijo: On Fri, Dec 03, 2004 at 03:34:55PM -0800, Jeremy Boynes wrote: However, if Unix commands like find and rm are dumping then it makes me question if the machine itself is acting up (bad memory or CPU failure). Might be worth it to run http://www.memtest86.com/. :-D A simple memtest: boot from the fedora CD's and run the CD's test. ;-) Best Regards, Antonio Gallardo
Re: Does Fedora Core 3/Sun JDK1.5.0 work for anyone?
Now that you mention it, we had a machine with bad RAM that manifested under JDK 1.5 but not 1.4. Doing a large bzip2 operation also caused it to fail regularly, and we confirmed it with memtest86. Replacement RAM fixed the problem. Aaron On Fri, 3 Dec 2004, Jeremy Boynes wrote: Desktop P4/2.4 no HT, 1GB RAM, SATA hard drive (seen as SCSI) I am just building Geronimo and it is crashing compiling. I had only switched /usr/bin/java to the Sun JDK but now have switched all. I have also gone back to 1.4.2_06. I am questioning the machine itself as find was giving a SEGV just scanning the source tree.
jetty deployer branch needs hard-to-get jar
In order to get jsps to work more simply, I've upgraded the jetty-deployer branch to use jasper 5.5.4. Although the regular jasper jars are available on ibiblio (jasper-compiler-5.5.4.jar and jasper-runtime-5.5.4.jar), they seem to have repackaged the essential parts of the eclipse compiler into jasper-compiler-jdt[-5.5.4].jar which is included in the tomcat 5.5.4 distro (without the version number) but is not on ibiblio. Until someone figures out how to get this into an accessible repository anyone wishing to try this out will need to get it from the tomcat distro and rename it. It goes into your local maven repo under tomcat/jars. The good news is that jsps seem to be working now with the new deployer. thanks david jencks
Re: BLOB manipulation - question
On 2/12/2004 11:52 AM, Dain Sundstrom wrote: Great news. I suggest that we declare that we only officially support the 10g driver. Maybe add a wiki page with supported drivers. Good idea. This is in progress in here: http://wiki.apache.org/geronimo/Working_20with_20Enterprise_20JavaBeans Thanks, Gianny
Re: How to start a plan from the Code
hi All; follow up from the itest module for axis, I look in to the itest modules and have finds some patterns. I have few questions and need to verify what I see is correct! Q1)How to run the itest from the maven build .. is there something like m:itests ... Q2) itests have itest and java dirs what does they mean ..please check my hypothesis java - have the application (e.g. web services ) itest - test cases what happen when the modules runs a) compile and create web services using the files in java dir and package them to a module b) itest:setup start the geronimo and axis and deployed the modules created c) test cases in the itests run automatically d) itest:shutdown shut down the server Q3) What is the format I should be given in the module at /geronimo-itests-axis-${pom.currentVersion}.jar deploy:distribute uri=deployer:geronimo:jmx:rmi://localhost/jndi/rmi:/JMXConnector username=system password=manager module=${basedir}/target/geronimo-itests-axis-${pom.currentVersion}.jar / Thanks Srinath On Fri, 3 Dec 2004 07:40:27 -0500, Davanum Srinivas [EMAIL PROTECTED] wrote: Srinath, Any progress on this? Thanks, dims On Sat, 20 Nov 2004 09:25:43 +0600, Srinath Perera [EMAIL PROTECTED] wrote: I think what you want to do is use the itest plugin together with the geronimo maven deploy plugin. You will have to add a new module to do this: I suggest itests/webservices. The good example of how to use this is openejb itests. These tests will run only after assembly; however if you are starting jetty and openejb, what you have is definitely not a unit test but an integration test. Thanks Daivd; yap it is more like integeration :), . what I want is to start system plan , j2ee-server plan, (with jetty and openejb) some axis configuration plan and then send SOAP calls. (there is long way to go it seems.) will look at the plugin! Thanks Srinath On Nov 19, 2004, at 12:45 AM, Srinath Perera wrote: I am trying to bring up few Gbeans from plan; I am trying to use following code. ReadOnlyRepository repository = new ReadOnlyRepository(new File(temp)); ServiceConfigBuilder scb = new ServiceConfigBuilder(null,repository); File plan = new File(plan1.xml); ConfigurationDocument configurationDoc = ConfigurationDocument.Factory.parse(plan.toURL()); File temp = new File(new); ConfigurationType conf = configurationDoc.getConfiguration(); List confs = scb.buildConfiguration(conf,null,temp); URI uri = new URI(conf.getConfigId()); -- Point A kernel.startConfiguration(temp.toURI()); kernel.stopConfiguration(temp.toURI()); 1) when I run the code the kernel not seem to know about the configuration I created at point A, Is there something missing and any way to improve this code? 2) Actually I need to get up J2EE continer, OpenEJB and Jetty Contianers up using plans from the code. I think there are plans created already (I think it is in assembly) what are the plans I should load to get that three contianers up and in what order. Thanks Srinath p.s. my plan ?xml version=1.0 encoding=UTF-8? configuration xmlns=http://geronimo.apache.org/xml/ns/deployment; configId=test/plan1 !-- Use the default deployer -- gbean name=test:axis=gb1 class=GBean1 attribute name=attribute1Hi/attribute attribute name=attribute2 type=java.lang.Stringgeronimo.server: j2eeType=J2EEServer,name=geronimo/attribute /gbean /configuration -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: jetty deployer branch needs hard-to-get jar
Dain reminded me how to get this jar into the openejb repo, so it is now generally available. thanks david jencks On Dec 3, 2004, at 10:30 PM, David Jencks wrote: In order to get jsps to work more simply, I've upgraded the jetty-deployer branch to use jasper 5.5.4. Although the regular jasper jars are available on ibiblio (jasper-compiler-5.5.4.jar and jasper-runtime-5.5.4.jar), they seem to have repackaged the essential parts of the eclipse compiler into jasper-compiler-jdt[-5.5.4].jar which is included in the tomcat 5.5.4 distro (without the version number) but is not on ibiblio. Until someone figures out how to get this into an accessible repository anyone wishing to try this out will need to get it from the tomcat distro and rename it. It goes into your local maven repo under tomcat/jars. The good news is that jsps seem to be working now with the new deployer. thanks david jencks
Re: jetty deployer branch needs hard-to-get jar
David Jencks wrote: Dain reminded me how to get this jar into the openejb repo, so it is now generally available. I recently added the Tomcat 5.5.4 jars to iBiblio.org via uploading them to /www/www.apache.org/dist/java-repository/tomcat/jars (I asked Tomcat's developers for their permission). I remembered that it's said the java-repository is meant to exchange the jars to iBiblio and it really happend after several hours. I also remember that ASF jars should not go to Codehaus as it's said it's not according to Codehaus rules (I can't fully remember who from Codehaus was saying that). david jencks Jacek
Re: jetty deployer branch needs hard-to-get jar
Could you also add the jasper-compiler-jdt-5.5.4.jar? I'm a bit confused by it since it contains only eclipse classes, but since it is labelled a jasper jar perhaps it's ok to distribute from apache thanks david jencks On Dec 4, 2004, at 12:21 PM, Jacek Laskowski wrote: David Jencks wrote: Dain reminded me how to get this jar into the openejb repo, so it is now generally available. I recently added the Tomcat 5.5.4 jars to iBiblio.org via uploading them to /www/www.apache.org/dist/java-repository/tomcat/jars (I asked Tomcat's developers for their permission). I remembered that it's said the java-repository is meant to exchange the jars to iBiblio and it really happend after several hours. I also remember that ASF jars should not go to Codehaus as it's said it's not according to Codehaus rules (I can't fully remember who from Codehaus was saying that). david jencks Jacek
Re: jetty deployer branch needs hard-to-get jar
David Jencks wrote: Could you also add the jasper-compiler-jdt-5.5.4.jar? I'm doing it. It'll take some time (12 hours or so) to show up at iBiblio.org. I'm a bit confused by it since it contains only eclipse classes, but since it is labelled a jasper jar perhaps it's ok to distribute from apache It's an integral part of Apache Tomcat and as such may be distributed from Apache, I think. david jencks Jacek
[jira] Created: (GERONIMO-509) policyConfigurationFactory.getPolicyConfiguration does not return open policy configurations
policyConfigurationFactory.getPolicyConfiguration does not return open policy configurations Key: GERONIMO-509 URL: http://nagoya.apache.org/jira/browse/GERONIMO-509 Project: Apache Geronimo Type: Bug Components: security Versions: 1.0-M3 Reporter: David Jencks JACC 1.0 spec 3.1.1.1 states that policyConfigurationFactory.getPolicyConfiguration(contextId, remove) must return a PolicyConfiguration in the Open state, even if it was in service or deleted before the call. Our implementation does not change the state of the policy configuration it returns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Re: jetty deployer branch needs hard-to-get jar
On Dec 4, 2004, at 1:12 PM, Jacek Laskowski wrote: David Jencks wrote: Could you also add the jasper-compiler-jdt-5.5.4.jar? I'm doing it. It'll take some time (12 hours or so) to show up at iBiblio.org. thanks! I'll remove it again from ibiblio when it gets there. I'm a bit confused by it since it contains only eclipse classes, but since it is labelled a jasper jar perhaps it's ok to distribute from apache It's an integral part of Apache Tomcat and as such may be distributed from Apache, I think. I think I'm glad I'm not a lawyer:-) david jencks david jencks Jacek