Re: 2.0-M3 Build Update

On 3/1/07, Sachin Patel [EMAIL PROTECTED] wrote: Anyhow, I've spoken to Matt and we are in sync, he working on publishing the artifacts. Good! I was worried that we wouldn't get in sync soon, but if you're content I'm fine, too! :P Thanks for your patience. Very appreciated. Jacek -- Jacek

[jira] Created: (GERONIMO-2909) ws-metadata spec classes have some annotation mistakes

ws-metadata spec classes have some annotation mistakes -- Key: GERONIMO-2909 URL: https://issues.apache.org/jira/browse/GERONIMO-2909 Project: Geronimo Issue Type: Bug Security

[jira] Commented: (SM-855) Non concurrent processing of files in LW FilePoller

[ https://issues.apache.org/activemq/browse/SM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38618 ] Juergen Mayrbaeurl commented on SM-855: --- Remarks: - I thought I'm not using tabs (sorry wrong Eclipse workspace

[jira] Commented: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[ https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476865 ] Lasantha Ranaweera commented on GERONIMO-2894: -- I checked it out. Looks fine. Had to try several

Re: Geronimo v2.0 Documentation - Administration

Yes Hernan, yesterday I tried with the M2 release and got the error. As per your advise, today I tried the same with M3 RC, but the problem exists. Thanks Karthiga On 2/28/07, Hernan Cunico [EMAIL PROTECTED] wrote: I would suggest you try to use the latest stable build/release. I've been

[jira] Closed: (GERONIMO-2909) ws-metadata spec classes have some annotation mistakes

[ https://issues.apache.org/jira/browse/GERONIMO-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2909. -- Resolution: Fixed fixed in rev 513236 ws-metadata spec classes have some annotation

[jira] Created: (GERONIMO-2910) annotation.security annotations are missing annotations

annotation.security annotations are missing annotations --- Key: GERONIMO-2910 URL: https://issues.apache.org/jira/browse/GERONIMO-2910 Project: Geronimo Issue Type: Bug Security

[jira] Closed: (GERONIMO-2911) mail 1.4 MimeMessage and QuotaAwareStore have missing exceptions or wrong method visibility

[ https://issues.apache.org/jira/browse/GERONIMO-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-2911. -- Resolution: Fixed Yes, that's the correct code to update. mail 1.4 MimeMessage and

[jira] Closed: (GERONIMO-2910) annotation.security annotations are missing annotations

[ https://issues.apache.org/jira/browse/GERONIMO-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2910. -- Resolution: Fixed rev 513246. version bumped to 1.1-SNAPSHOT annotation.security

[jira] Created: (GERONIMO-2911) mail 1.4 MimeMessage and QuotaAwareStore have missing exceptions or wrong method visibility

mail 1.4 MimeMessage and QuotaAwareStore have missing exceptions or wrong method visibility --- Key: GERONIMO-2911 URL: https://issues.apache.org/jira/browse/GERONIMO-2911

[BUILD] TRUNK: Failed for Revision: 513251

Building with Maven version: 2.0.5 Revision: 513251 built with tests included See the full build-0500.log file at http://people.apache.org/~prasad/binaries/20070301/build-0500.log Downloading: http://tomcat.apache.org/dev/dist/m2-repository//org/apache/axis2/axis2-kernel/20070301.070125-44

[jira] Assigned: (GERONIMO-2911) mail 1.4 MimeMessage and QuotaAwareStore have missing exceptions or wrong method visibility

[ https://issues.apache.org/jira/browse/GERONIMO-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-2911: -- Assignee: Rick McGuire (was: David Jencks) Fix committed in rev 513249. I'm a

[jira] Assigned: (GERONIMO-2854) Inverse Classloader view

[ https://issues.apache.org/jira/browse/GERONIMO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Midha reassigned GERONIMO-2854: -- Assignee: Rakesh Midha Inverse Classloader view

Re: request.getContextPath() in RequestAdapter class in JettyEJBWebServiceContext.java

David, :) 'twas a cross your fingers fix -- dims On 3/1/07, David Blevins [EMAIL PROTECTED] wrote: On Feb 28, 2007, at 12:42 PM, Lin Sun wrote: Hi, I have noticed some behavior difference between JettyEJBWebServiceContext and TomcatEJBWebServiceContext. Both of them have an inner

Re: Context level clustering not supported in Tomcat it seems

Yes Filip, what we mean by Context-level (or application level) clustering is that the clustering configuration is specified in Tomcat's context.xml file. So this isn't supported right? I am dropping my idea of checking on Tomcat's mailing list and re-testing. -- Thx, Shiva On 3/1/07, Filip

Re: Build failed due to mx4j dependency

The dependency on mx4j has been removed. Please svn update and build plugins (geronimo-maven-plugin). Thanks Anita --- Lasantha Ranaweera [EMAIL PROTECTED] wrote: Now it looks working. Thanks. :-) \ Lasantha Ranaweera wrote: Project ID:

Re: [BUILD] TRUNK: Failed for Revision: 513251

Hitting the same now. -sachin On Mar 1, 2007, at 5:23 AM, [EMAIL PROTECTED] wrote: Building with Maven version: 2.0.5 Revision: 513251 built with tests included See the full build-0500.log file at http://people.apache.org/ ~prasad/binaries/20070301/build-0500.log Downloading: http

[jira] Commented: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers

[ https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476948 ] Lin Sun commented on GERONIMO-2894: --- Thanks again Lasantha!!! I'd be grateful if someone can commit this. I

Re: request.getContextPath() in RequestAdapter class in JettyEJBWebServiceContext.java

Thanks for the feedback, David and Dims! I'll try using request.getRequestURI() instead which seems to return the correct value... Lin Davanum Srinivas wrote: David, :) 'twas a cross your fingers fix -- dims On 3/1/07, David Blevins [EMAIL PROTECTED] wrote: On Feb 28, 2007, at 12:42

Re: [Discussion] Geronimo web site update

Looks great! A few minor nitpick comments on the website content: 1) Why are the guiding principles in blue text? At first glance, it makes it appear as though the items are links.. I know links are underlined.. though still seems odd. 2) Why are the news events in a table? Does the

Re: [VOTE] 2.0-M3 Release

All the usual set of apps deployed and started to run fine. Undeploy (on Windows) is an issue that has been documented in the release notes. +1 Cheers Prasad On 2/28/07, Matt Hogstrom [EMAIL PROTECTED] wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo

Re: [VOTE] Geronimo web site update

+1 On 2/28/07, Hernan Cunico [EMAIL PROTECTED] wrote: Folks, this vote is for moving the authoring of Geronimo's web site over Confluence. This mean that we will no longer use the anakia, xdocs and ant scripts to generate the web site, instead we will use Confluence. There is a GMOxSITE

Re: [VOTE] Geronimo web site update

[X] +1 Let's move the authoring over Confluence. Cheers Prasad On 2/28/07, Hernan Cunico [EMAIL PROTECTED] wrote: Folks, this vote is for moving the authoring of Geronimo's web site over Confluence. This mean that we will no longer use the anakia, xdocs and ant scripts to generate the web

Re: [VOTE] Geronimo web site update

+1 On 3/1/07, Prasad Kashyap [EMAIL PROTECTED] wrote: [X] +1 Let's move the authoring over Confluence. Cheers Prasad On 2/28/07, Hernan Cunico [EMAIL PROTECTED] wrote: Folks, this vote is for moving the authoring of Geronimo's web site over Confluence. This mean that we will no longer use

Re: Geronimo 2.0 web services support table

Cool - Question, what is meant by Could use J2SE or J2ME under the Client section? AFAIK, the JAX-WS client apis won't ever work on J2ME... Cheers, - Dan On 2/20/07, Lin Sun [EMAIL PROTECTED] wrote: Hi there, I have created a table for Geronimo web services support. The page is a child

[jira] Updated: (GERONIMO-2854) Inverse Classloader view

[ https://issues.apache.org/jira/browse/GERONIMO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Midha updated GERONIMO-2854: --- Attachment: jira2854sort.patch List presented in sorted asending order for all the three

[jira] Updated: (GERONIMO-2854) Inverse Classloader view

[ https://issues.apache.org/jira/browse/GERONIMO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Midha updated GERONIMO-2854: --- Assignee: (was: Rakesh Midha) Patch provided for sorted list. Unassigning, please

Re: Context level clustering not supported in Tomcat it seems

Shiva, Its supported but not the usual way. It uses a different context. We will need to change some of our code. Jeff Shiva Kumar H R wrote: Yes Filip, what we mean by Context-level (or application level) clustering is that the clustering configuration is specified in Tomcat's context.xml

[jira] Commented: (GERONIMO-2676) Web Application without required jars throws NullPointer

[ https://issues.apache.org/jira/browse/GERONIMO-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476966 ] Rakesh Midha commented on GERONIMO-2676: Can someone or KK, please confirm the status so that we can

Re: JAXB upgrade

I'm happy to revert the change, but I think that we ultimately need it. I believe we're targeting JAX-WS 2.1 (we switched the API jar the other day), and that requires JAXB 2.1. There are many benefits from a user perspective in 2.1. For isntance it has a lot better functionality for things like

[jira] Created: (GERONIMO-2912) Server can not be shutdown using bin\shutdown

Server can not be shutdown using bin\shutdown - Key: GERONIMO-2912 URL: https://issues.apache.org/jira/browse/GERONIMO-2912 Project: Geronimo Issue Type: Bug Security Level: public (Regular

Re: Additional 'inverse' classloader view in Geronimo Console

Hello Paul I have uploaded the patch to take care of sorting. Please review and commit/comment. Thanks Rakesh On 2/27/07, Rakesh Midha [EMAIL PROTECTED] wrote: Thanks Paul I will look into the sorting request? Thanks Rakesh On 2/26/07, Paul McMahan [EMAIL PROTECTED] wrote: Yes, I chair

Re: [jira] Created: (GERONIMO-2912) Server can not be shutdown using bin\shutdown

The jline and geronimo-deploy-tool jars are not making it to the lib directory in the server. Adding them to the lib solves this problem. Gianny, is this consistent with the changes you made? Thanks Anita --- Anita Kulshreshtha (JIRA) [EMAIL PROTECTED] wrote: Server can not be shutdown using

Re: Geronimo v2.0 Documentation - Administration

Can you use Tomcat instead or this error is in both dists? Cheers! Hernan Karthiga Ratnam wrote: Yes Hernan, yesterday I tried with the M2 release and got the error. As per your advise, today I tried the same with M3 RC, but the problem exists. Thanks Karthiga On 2/28/07, *Hernan Cunico*

Patchs pending for review

Hello Thanks Paul, Christopher, Vamsi, Kevan, David and others for reviewing and commenting/commiting the patchs I submitted. Can I ask for more, and request all the review following patchs pending for review for quite some time. http://issues.apache.org/jira/browse/GERONIMO-348

Re: JAXB upgrade

Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm not sure how that affects things. Jarek On 3/1/07, Dan Diephouse [EMAIL PROTECTED] wrote: I'm happy to revert the change, but I think that we ultimately need it. I believe we're targeting JAX-WS 2.1 (we switched the API

Re: Context level clustering not supported in Tomcat it seems

I'm still trying to understand what exactly this means to users of Geronimo/Tomcat. IIUC, enabling host/engine clustering basically means that all web applications on a particular host/engine that contain the distributable tag in their web.xml will replicate session state with other cluster

Re: Context level clustering not supported in Tomcat it seems

Dave Colasurdo wrote: Now for context attribute replication... Does this mean that a user can specify unique replication domain per individual web application from a common Tomcat/Geronimo installation? Yep I'm trying to understand what advantage context attribute replication provides.

Re: JAXB upgrade

Jarek Gawor wrote: Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm not sure how that affects things. If the JavaEE5 TCK is only JAX-WS 2.0 compliant, this may be a problem. Jarek On 3/1/07, Dan Diephouse [EMAIL PROTECTED] wrote: I'm happy to revert the change,

Re: [Discussion] Geronimo web site update

Dave Colasurdo wrote: Looks great! A few minor nitpick comments on the website content: 1) Why are the guiding principles in blue text? At first glance, it makes it appear as though the items are links.. I know links are underlined.. though still seems odd. We already had them in blue

Re: [VOTE] 2.0-M3 Release

On Feb 28, 2007, at 3:12 PM, Matt Hogstrom wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http:// people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and

Re: Context level clustering not supported in Tomcat it seems

Jeff Genender wrote: I'm trying to understand what advantage context attribute replication provides. Allows you to pick and choose which web apps are distributed and which are not. Example: There may be a mission critical app that needs clustering, but we most certainly wouldn't want to

Anybody else having problems starting trunk build on Linux ?

At Revision: 513359 The exception is seen only on Linux. It works fine on windows. Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.configs/webconsole-jetty6/2.0-SNAPSHOT/car failed to start due to the following reasons: The service

Re: Context level clustering not supported in Tomcat it seems

Dave Colasurdo wrote: IIUC the presence/absence of the distributable tag in web.xml also provides the same behavior. I gave this a quick test recently and it seemed to work that way. To a degree yes, but my understanding is all contexts would have the valves, manager, etc attached. Context

[jira] Assigned: (GERONIMO-2854) Inverse Classloader view

[ https://issues.apache.org/jira/browse/GERONIMO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan reassigned GERONIMO-2854: -- Assignee: Paul McMahan Inverse Classloader view

Re: [Discussion] Geronimo web site update

Hernan Cunico wrote: Dave Colasurdo wrote: Looks great! A few minor nitpick comments on the website content: 1) Why are the guiding principles in blue text? At first glance, it makes it appear as though the items are links.. I know links are underlined.. though still seems odd. We

Re: [VOTE] 2.0-M3 Release

I found a problem where for a web app you cannot hit just the hostname:8080/contextRoot as this will throw a 404. However, if the app has any servlet mappings then I can hit the mapping url. We definitely need to look into this, but I don't deem in necessary to respin. +1 -sachin On

Re: Additional 'inverse' classloader view in Geronimo Console

Committed in rev 513395, thanks! AFAIK there are no outstanding items remaining so I will go ahead and close the JIRA. Best wishes, Paul On 3/1/07, Rakesh Midha [EMAIL PROTECTED] wrote: Hello Paul I have uploaded the patch to take care of sorting. Please review and commit/comment. Thanks

Re: Context level clustering not supported in Tomcat it seems

Jeff Genender wrote: Dave Colasurdo wrote: IIUC the presence/absence of the distributable tag in web.xml also provides the same behavior. I gave this a quick test recently and it seemed to work that way. To a degree yes, but my understanding is all contexts would have the valves, manager,

[jira] Closed: (GERONIMO-2854) Inverse Classloader view

[ https://issues.apache.org/jira/browse/GERONIMO-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2854. -- Resolution: Fixed Fix Version/s: (was: 2.0-M2) 2.0-beta2

Re: Context level clustering not supported in Tomcat it seems

Dave Colasurdo wrote: So, with contexts each clustered web application could have its own clustering characteristics such as which multicast address it uses etc.? AFAIK, this is correct...and a very flexible option ;-) Jeff

Re: [VOTE] 2.0-M3 Release

Forgot to mention that the problem mention below only occurs on Tomcat. -sachin On Mar 1, 2007, at 11:28 AM, Sachin Patel wrote: I found a problem where for a web app you cannot hit just the hostname:8080/contextRoot as this will throw a 404. However, if the app has any servlet mappings

Re: Patchs pending for review

Thanks for the reminder Rakesh. I committed GERONIMO-2854 and have been planning to look at several of your other patches. Sorry for the delay in processing these items, as you probably know the team is very focused on moving trunk to a JEE 5 baseline but these fit and finish items are also

Re: [VOTE] 2.0-M3 Release

Sachin, this is actually the default behavior in tomcat. You can change the setting in geronimo/var/catalina/conf/web.xml but there's a warning associated with it: !-- listingsShould directory listings be produced if there -- !-- is no welcome file in this

[jira] Resolved: (SM-859) incorrect jsr181 mtom response

[ https://issues.apache.org/activemq/browse/SM-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-859. Resolution: Duplicate Fix Version/s: 3.1 I have added a test case but everything seems to

Re: [VOTE] 2.0-M3 Release

+1 On 2/28/07, Matt Hogstrom [EMAIL PROTECTED] wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http:// people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and

[jira] Created: (GERONIMO-2913) minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2

minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2 --- Key: GERONIMO-2913 URL: https://issues.apache.org/jira/browse/GERONIMO-2913

trunk build failure

I'm now seeing a different build failure on trunk when building from a clean local repo. This is when building the module for geronimo-axis2. [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure

[jira] Updated: (GERONIMO-2913) minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2

[ https://issues.apache.org/jira/browse/GERONIMO-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-2913: -- Attachment: G2913.patch minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext

Re: trunk build failure

Getting the same error Thanks, Tim McConnell Joe Bohn wrote: I'm now seeing a different build failure on trunk when building from a clean local repo. This is when building the module for geronimo-axis2. [ERROR] BUILD FAILURE [INFO]

[jira] Created: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly --- Key: GERONIMO-2914 URL:

Re: trunk build failure

I just refreshed my Axis2 trunk and looks like they commented out this entire method processHTTPGetRequest in Axis2 trunk just this morning! Do you want to comment out this also in trunk before we work out a fix? In

Re: JAXB upgrade

Sun sometimes allows implementations to certify using a newer api then was in required by the original JEE specification. My guess is that the next version of Glassfish uses these apis, so hopefully if we ask, they'll give us new signature files or a patched TCK. Anyway, to find out

[jira] Created: (GERONIMO-2915) Disable to call to processHTTPGetRequest to fix the build error

Disable to call to processHTTPGetRequest to fix the build error --- Key: GERONIMO-2915 URL: https://issues.apache.org/jira/browse/GERONIMO-2915 Project: Geronimo Issue Type: Bug

[jira] Updated: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-2915: -- Summary: Disable the call to processHTTPGetRequest to fix the build error (was: Disable to call to

[jira] Assigned: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn reassigned GERONIMO-2915: -- Assignee: Joe Bohn Disable the call to processHTTPGetRequest to fix the build error

[jira] Updated: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

[ https://issues.apache.org/jira/browse/GERONIMO-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-2914: -- Attachment: G2914.patch Dims, This patch needs to be committed after the method

[jira] Closed: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-2915. -- Resolution: Fixed checked in work-around with rev. 513439 Thanks Lin! Disable the call to

[jira] Commented: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477054 ] Davanum Srinivas commented on GERONIMO-2915: Joe, Please hang on. a mvn deploy of Axis2 is underway

[jira] Commented: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477055 ] Joe Bohn commented on GERONIMO-2915: Sorry Dims ... I didn't see this until it was too late. Do you want me

[BUILD] TRUNK: Failed for Revision: 513438

Building with Maven version: 2.0.5 Revision: 513438 built with tests skipped See the full build-1400.log file at http://people.apache.org/~prasad/binaries/20070301/build-1400.log Downloading: http://people.apache.org/repo/m2-incubating-repository//commons-httpclient/commons-httpclient/3.0.1

released geronimo-jta_1.1_spec-1.0.jar contents do not match source

AFAICT the released geronimo-jta_1.1_spec-1.0.jar does not contain the HeuristicCommitException class which however is in svn source. What do we do about this? Release a 1.0.1 version? I'd like to point out that I've been finding errors in at least one other released spec jar and encourage

Re: [BUILD] TRUNK: Failed for Revision: 513438

with tests skipped See the full build-1400.log file at http://people.apache.org/~prasad/binaries/20070301/build-1400.log Downloading: http://people.apache.org/repo/m2-incubating-repository//commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar [WARNING] Unable to get resource

[jira] Updated: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly

[ https://issues.apache.org/jira/browse/GERONIMO-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-2914: -- Attachment: G2914-new.patch created against latest trunk (with G2915). Axis2: a few changes to

[jira] Commented: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error

[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477066 ] Lin Sun commented on GERONIMO-2915: --- Dims, I just updated G2914's patch to build on top of the latest trunk

Tomcat 6 and G Certification, WAS: Heads up re: Apache Geronimo and JavaOne

Ladies and Gents, Just wanted to extend a hand here. If there is any help needed to integrate TC6 and to make it pass the tests, I am more than willing to help to get the two platforms working correctly within the timeframe you are looking at. Albeit I have a hard time following the volume

Re: [BUILD] TRUNK: Failed for Revision: 513251

Sachin Patel wrote: Hitting the same now. -sachin On Mar 1, 2007, at 5:23 AM, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Building with Maven version: 2.0.5 Revision: 513251 built with tests included See the full build-0500.log file at http://people.apache.org/~prasad/binaries/20070301

[jira] Created: (GERONIMO-2916) database creation pool wizzard fails to deploy

database creation pool wizzard fails to deploy -- Key: GERONIMO-2916 URL: https://issues.apache.org/jira/browse/GERONIMO-2916 Project: Geronimo Issue Type: Bug Security Level: public

Re: [VOTE] 2.0-M3 Release

+1 Cheers! Hernan Matt Hogstrom wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http://people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and running

[jira] Commented: (SM-855) Non concurrent processing of files in LW FilePoller

[ https://issues.apache.org/activemq/browse/SM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38622 ] Guillaume Nodet commented on SM-855: Yeah, this would work. If we want to use the executor, we need to write

Re: JAXB upgrade

I think we are all open to input on this particular point. Is there any way we can figure out what the JEE5 requirements are though? Thanks, - Dan On 3/1/07, Jeff Genender [EMAIL PROTECTED] wrote: Jarek Gawor wrote: Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm

Re: JAXB upgrade

On Mar 1, 2007, at 9:42 AM, Dan Diephouse wrote: I think we are all open to input on this particular point. Is there any way we can figure out what the JEE5 requirements are though? Assuming 2.1 is backward compatible to 2.0 the only real limitation can see is that often when testing the

Re: JAXB upgrade

AFAICT...the TCK for JAXB appears to be for 2.0.: https://jaxb.dev.java.net/tck.html and it appears that particular TCK is open to all ;-) On that web site it clearly states: ** Compatibility artifacts are available as follows: * The JAXB

Re: JAXB upgrade

Yep...so for this reason I would probably ask that CXF hang on JAXB 2.0 for the time being. Jeff Dain Sundstrom wrote: Sun sometimes allows implementations to certify using a newer api then was in required by the original JEE specification. My guess is that the next version of Glassfish uses

[jira] Created: (GERONIMO-2917) All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management

All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management -- Key: GERONIMO-2917 URL:

[jira] Updated: (GERONIMO-2893) Local/Remote support for EJB annotations inconsistent (i.e., same as not working)

[ https://issues.apache.org/jira/browse/GERONIMO-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMO-2893: Attachment: GERONIMO-2893-5.patch Patch to include the AnnotatedApp interface as

Re: [jira] Updated: (GERONIMO-2735) Add property substitution capability in the config.xml and plan files

On 2/20/07, David Jencks [EMAIL PROTECTED] wrote: Before I run ahead and apply this I'd like to make sure this is the approach we all agree on. I think there are 2 choices for how to do this: 1. as done in the patch, where the config.xml has explicit substitutions possibly within other text

Re: mx4j dependencies

I think we are free from mx4j deps now... only 2 references of 'mx4j' in the project now: * modules/ge-activemq-rar/pom.xml (dependency excludes) * modules/geronimo-jetty6/src/test/java/org/apache/geronimo/jetty6/ ClassLoaderTest.java (attempts to use mx4j.MBeanDescription to test

[jira] Created: (GERONIMO-2918) Have the ActiveMQ broker configured from an external configuration file by default

Have the ActiveMQ broker configured from an external configuration file by default -- Key: GERONIMO-2918 URL: https://issues.apache.org/jira/browse/GERONIMO-2918

[jira] Created: (GERONIMO-2919) use axis2 saaj 1.3 spec jar

use axis2 saaj 1.3 spec jar --- Key: GERONIMO-2919 URL: https://issues.apache.org/jira/browse/GERONIMO-2919 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.0-M3

Re: [jira] Created: (GERONIMO-2912) Server can not be shutdown using bin\shutdown

Hi Anita, thanks for raising this problem. It is related to a change I made. I just attached a patch to the JIRA that I will commit tonight if you do not do it before me. Thanks, Gianny On 02/03/2007, at 2:37 AM, Anita Kulshreshtha wrote: The jline and geronimo-deploy-tool jars are not

[jira] Updated: (GERONIMO-2912) Server can not be shutdown using bin\shutdown

[ https://issues.apache.org/jira/browse/GERONIMO-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gianny Damour updated GERONIMO-2912: Attachment: GERONIMO-2912.patch Fix this problem. I have other changes in my local and,

[jira] Commented: (GERONIMO-2919) use axis2 saaj 1.3 spec jar

[ https://issues.apache.org/jira/browse/GERONIMO-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477101 ] Jarek Gawor commented on GERONIMO-2919: --- This needs to be done carefully. The last time I tried to use

[jira] Updated: (GERONIMO-2893) Local/Remote support for EJB annotations inconsistent (i.e., same as not working)

[ https://issues.apache.org/jira/browse/GERONIMO-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMO-2893: Attachment: AnnotatedEjbJar.java Virtual svn add Local/Remote support for EJB

[jira] Commented: (GERONIMO-2917) All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management

[ https://issues.apache.org/jira/browse/GERONIMO-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477110 ] David Jencks commented on GERONIMO-2917: these changes made in rev 513538. Talking with rick

Re: Additional 'inverse' classloader view in Geronimo Console

On Mar 1, 2007, at 11:28 AM, Paul McMahan wrote: Committed in rev 513395, thanks! AFAIK there are no outstanding items remaining so I will go ahead and close the JIRA. Best wishes, Paul On 3/1/07, Rakesh Midha [EMAIL PROTECTED] wrote: Hello Paul I have uploaded the patch to take care of

Re: [VOTE] 2.0-M3 Release

On Feb 28, 2007, at 9:35 PM, Joe Bohn wrote: Matt Hogstrom wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http:// people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by

[jira] Commented: (GERONIMO-2917) All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management

[ https://issues.apache.org/jira/browse/GERONIMO-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477120 ] David Jencks commented on GERONIMO-2917: mail switched back in rev 513546. Leaving open until I'm sure

[jira] Updated: (GERONIMO-2919) use axis2 saaj 1.3 spec jar

[ https://issues.apache.org/jira/browse/GERONIMO-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-2919: --- Attachment: GERONIMO-2919.patch This is as far as I got before jarek's comment I'm

[jira] Created: (GERONIMO-2920) Upgrade to tomcat 6.0.10 (stable)

Upgrade to tomcat 6.0.10 (stable) - Key: GERONIMO-2920 URL: https://issues.apache.org/jira/browse/GERONIMO-2920 Project: Geronimo Issue Type: Task Security Level: public (Regular issues)

  1   2   >