Re: svn commit: r646128 - in /geronimo/samples/trunk/samples/bank: ./ bank-client/ bank-client/src/ bank-client/src/main/ bank-client/src/main/java/ bank-ejb/src/main/java/org/apache/geronimo/samples/
On Wed, Apr 9, 2008 at 1:14 AM, [EMAIL PROTECTED] wrote:
Author: viet
Date: Tue Apr 8 16:14:22 2008
New Revision: 646128
...
Modified:
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeBean.java
URL:
http://svn.apache.org/viewvc/geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeBean.java?rev=646128r1=646127r2=646128view=diff
==
---
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeBean.java
(original)
+++
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeBean.java
Tue Apr 8 16:14:22 2008
@@ -25,6 +25,8 @@
import javax.persistence.PersistenceUnit;
import javax.ejb.EJBException;
+import javax.ejb.Local;
+import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.naming.Context;
import javax.naming.InitialContext;
@@ -32,6 +34,8 @@
import javax.persistence.EntityManager;
import javax.persistence.EntityManagerFactory;
[EMAIL PROTECTED](BankManagerFacadeRemote.class)
[EMAIL PROTECTED](BankManagerFacadeLocal.class)
@Stateless
public class BankManagerFacadeBean implements BankManagerFacadeLocal {
I can't find it in the spec, but may a bean specify a remote intf that
it doesn't implement? I think it's a bug in openejb if it allows it.
In such a single-interface case, mere @Local would be enough.
Modified:
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeLocal.java
URL:
http://svn.apache.org/viewvc/geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeLocal.java?rev=646128r1=646127r2=646128view=diff
==
---
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeLocal.java
(original)
+++
geronimo/samples/trunk/samples/bank/bank-ejb/src/main/java/org/apache/geronimo/samples/bank/ejb/BankManagerFacadeLocal.java
Tue Apr 8 16:14:22 2008
@@ -17,10 +17,13 @@
package org.apache.geronimo.samples.bank.ejb;
+import javax.ejb.Local;
+
import org.apache.geronimo.samples.bank.ejb.Account;
import org.apache.geronimo.samples.bank.ejb.ExchangeRate;
import org.apache.geronimo.samples.bank.ejb.Customer;
[EMAIL PROTECTED]
public interface BankManagerFacadeLocal {
public java.util.ListAccount getAccountInformation(String
customerId);
Why is it needed? You can leave it out and let a bean specify whether
it's a local or remote interface (regardless of the interface's name).
If it's to show people it works I'm fine with it, otherwise I'm
puzzled ;-)
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
[jira] Updated: (GERONIMODEVTOOLS-285) Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-285: - Component/s: eclipse-plugin Affects Version/s: 2.1.0 Fix Version/s: 2.1.x Assignee: Shiva Kumar H R (was: YunFeng Ma) Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions -- Key: GERONIMODEVTOOLS-285 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: YunFeng Ma Assignee: Shiva Kumar H R Fix For: 2.1.x Attachments: GEP-JAXB-3.patch, GEP-JAXB.patch, MultipleSchemaVersionTest.zip, testapp.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-285) Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-285: - Issue Type: Improvement (was: Sub-task) Parent: (was: GERONIMODEVTOOLS-278) Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions -- Key: GERONIMODEVTOOLS-285 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: YunFeng Ma Assignee: YunFeng Ma Fix For: 2.1.x Attachments: GEP-JAXB-3.patch, GEP-JAXB.patch, MultipleSchemaVersionTest.zip, testapp.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-295) Delete redundant dependencies from runtime plug-ins - Make GEP thinner!
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-295: - Issue Type: Improvement (was: Sub-task) Parent: (was: GERONIMODEVTOOLS-278) Delete redundant dependencies from runtime plug-ins - Make GEP thinner! --- Key: GERONIMODEVTOOLS-295 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 GEP is currently 13.3MB! Out of this ~11.6MB (87%) is from following four plug-ins! 1) \plugins\org.apache.geronimo.runtime.common 2) \plugins\org.apache.geronimo.runtime.v11 3) \plugins\org.apache.geronimo.runtime.v20 4) \plugins\org.apache.geronimo.runtime.v21 After GERONIMODEVTOOLS-294, many of the dependencies in above plug-ins might have become redundant. Identify the redundant ones and delete them to make GEP thinner :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-295) Delete redundant dependencies from runtime plug-ins - Make GEP thinner!
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-295: - Fix Version/s: (was: 2.1.0) 2.1.x Delete redundant dependencies from runtime plug-ins - Make GEP thinner! --- Key: GERONIMODEVTOOLS-295 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.x GEP is currently 13.3MB! Out of this ~11.6MB (87%) is from following four plug-ins! 1) \plugins\org.apache.geronimo.runtime.common 2) \plugins\org.apache.geronimo.runtime.v11 3) \plugins\org.apache.geronimo.runtime.v20 4) \plugins\org.apache.geronimo.runtime.v21 After GERONIMODEVTOOLS-294, many of the dependencies in above plug-ins might have become redundant. Identify the redundant ones and delete them to make GEP thinner :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-312) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-312: - Issue Type: Improvement (was: Sub-task) Parent: (was: GERONIMODEVTOOLS-278) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB --- Key: GERONIMODEVTOOLS-312 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Fix For: 2.1.0 The fixGeronimo*Schema() function inside GeronimRuntime classes is curently implemented using XMLBeans. As part of GERONIMODEVTOOLS-295, xmlbeans-2.3.0.jar has been removed from GEP's dependencies. Hence fixGeronimo*Schema() functionality needs to be reimplemented using JAXB. Classes to be changed: 1) org.apache.geronimo.st.core.IGeronimoRuntime 2) org.apache.geronimo.st.core.operations.ImportDeploymentPlanOperation 3) org.apache.geronimo.st.v11.core.GeronimoRuntime 4) org.apache.geronimo.st.v20.core.GeronimoRuntime 5) org.apache.geronimo.st.v21.core.GeronimoRuntime -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-312) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-312: - Priority: Critical (was: Major) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB --- Key: GERONIMODEVTOOLS-312 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Priority: Critical Fix For: 2.1.0 The fixGeronimo*Schema() function inside GeronimRuntime classes is curently implemented using XMLBeans. As part of GERONIMODEVTOOLS-295, xmlbeans-2.3.0.jar has been removed from GEP's dependencies. Hence fixGeronimo*Schema() functionality needs to be reimplemented using JAXB. Classes to be changed: 1) org.apache.geronimo.st.core.IGeronimoRuntime 2) org.apache.geronimo.st.core.operations.ImportDeploymentPlanOperation 3) org.apache.geronimo.st.v11.core.GeronimoRuntime 4) org.apache.geronimo.st.v20.core.GeronimoRuntime 5) org.apache.geronimo.st.v21.core.GeronimoRuntime -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-278) Model framework for G deployment plans - Change from existing EMF to JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMODEVTOOLS-278. Resolution: Fixed Model framework for G deployment plans - Change from existing EMF to JAXB - Key: GERONIMODEVTOOLS-278 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Priority: Critical Fix For: 2.1.0 Please see the discussion on Geronimo dev-list: http://www.mail-archive.com/dev@geronimo.apache.org/msg56777.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3957) Updating svn:ignore lists
[ https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588530#action_12588530 ] Jacek Laskowski commented on GERONIMO-3957: --- [EMAIL PROTECTED] /cygdrive/c/oss/geronimo $ patch -p0 Geronimo-3957-Trunk.patch patch: Only garbage was found in the patch input. How can I work it out? Updating svn:ignore lists - Key: GERONIMO-3957 URL: https://issues.apache.org/jira/browse/GERONIMO-3957 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: general Affects Versions: 2.0.2, 2.1 Reporter: Vasily Zakharov Attachments: Geronimo-3957-20.patch, Geronimo-3957-21.patch, Geronimo-3957-210.patch , Geronimo-3957-Trunk.patch, Geronimo-3957-Trunk.patch When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they just need to be added to the corresponding SVN ignore list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3651) gshell should make it dead simple to run geronimo with remote debugging
[ https://issues.apache.org/jira/browse/GERONIMO-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3651: --- Affects Version/s: 2.2 2.1.x Fix Version/s: 2.1.x We need to make it easier to debug a 2.1.x server gshell should make it dead simple to run geronimo with remote debugging --- Key: GERONIMO-3651 URL: https://issues.apache.org/jira/browse/GERONIMO-3651 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.x, 2.2 Reporter: David Jencks Assignee: Jason Dillon Priority: Blocker Fix For: 2.1.x, 2.2 we need some options for start-server so g. starts up with debugging. I think we should be able to set the port and suspend as persistent options in the environment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-254) Spaces in server pathname causes problems for the Eclipse Plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588552#action_12588552 ] Donald Woods commented on GERONIMODEVTOOLS-254: --- This is a critical bug for Windows users, that needs to get fixed in 2.1.0. I know the Plan Creator portlet can't handle spaces in the Geronimo server path, so there may be multiple areas to fix Spaces in server pathname causes problems for the Eclipse Plugin Key: GERONIMODEVTOOLS-254 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 2.0.0 Environment: Windows Reporter: Tim McConnell Assignee: Shiva Kumar H R Fix For: 2.1.x When there are spaces in the Geronimo server pathname (on Windows), the Eclipse Plugin will have problems deploying and EAR File. For example the following error will occur: Distribution of configuration failed. See log for details. Error unmarshaling return; nested exception is: java.net.MalformedURLException: no protocol: Files/IBM/WebSphere/AppServerCommunityEdition/repository/org/apache/geronimo/modules/geronimo-common/2.0.1/geronimo-common-2.0.1.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Updating svn:ignore lists
If you're a committer on multiple projects, then you need to update your config file or tool (TortoiseSVN in this case) to handle this, instead of expecting everyone to map their svn usage to your tool's behavior or your style Any major changes of svn props should be brought up in a discussion thread with [DISCUSS] as the start of the subject for everyone to review and comment upon before applying, since it could impact others expected svn behavior and needs to be documented for future svn additions. -Donald Vasily Zakharov wrote: Jason, Donald, Thanks for your suggestions, I'll surely follow them. However, I'm not sure that having things like 'target' or 'build' in the exclude list is a wise practice in long-term. So, I think having a consistent approach from the project side is also a good idea. Thanks! Vasily On Fri, Apr 11, 2008 at 2:43 PM, Donald Woods [EMAIL PROTECTED] wrote: Here is what I have in my Subversion config file, which I've accumulated across Windows and Linux - global-ignores = .cvsignore ~$* ~*.tmp *.*~ thumbs.db Thumbs.db *.log .project .classpath .settings target nohup.out build.txt Notice the build.txt, which I have because I like to pipe the build out to a file so I can go back to look at any failed steps, like - mvn install | tee build.txt BTW - Please use the other suggested Apache config settings at - http://cwiki.apache.org/GMOxKB/how-do-i-setup-my-svn-client-for-commits.html Note: You have to add these into TortoiseSVN and the command line svn config file, if you use both -Donald Jason Dillon wrote: Configure your local svn ignores in ~/.subversion/config under the 'global-ignores' property. --jason On Apr 11, 2008, at 12:47 AM, Vasily Zakharov wrote: Well, I'm using TortoiseSVN and it always considers those files to be added to the repository when I'm going to create a patch. This obstructs a create patch/commit dialog with a lot of unneeded entries, and increases the working copy scan time. In fact, I wouldn't raise this issue if I don't see that many other 'target' and 'build' directories are put to svn:ignore lists, while some are not. Vasily On Thu, Apr 10, 2008 at 7:18 PM, Jason Warner [EMAIL PROTECTED] wrote: Hi Vasily, What do you mean by getting in the way? I've never had issues with this. What behavior are you seeing? ~Jason Warner On Thu, Apr 10, 2008 at 1:15 PM, Vasily Zakharov [EMAIL PROTECTED] wrote: When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they need to be added to the corresponding SVN ignore lists. I've created a GERONIMO-3957 for that, and provided patches for trunk, branches/2.1, branches/2.0 and tags/2.1.0. I hope it would be useful. Vasily -- ~Jason Warner smime.p7s Description: S/MIME Cryptographic Signature
[jira] Resolved: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-3819. Resolution: Fixed Applied to trunk only (2.2). Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Reporter: Anish Pathadan Assignee: Donald Woods Fix For: 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3819) Update JMS Resources Portlet
[ https://issues.apache.org/jira/browse/GERONIMO-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3819: --- Patch Info: [Patch Available] Affects Version/s: 2.2 2.1.x 2.1.1 2.1 Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.1.x, 2.2 Reporter: Anish Pathadan Assignee: Donald Woods Fix For: 2.2 Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3408) Clean up deployer login code in ServerConnection
[ https://issues.apache.org/jira/browse/GERONIMO-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3408: --- Fix Version/s: (was: 2.1.1) (was: 2.0.x) 2.2 2.1.x Moving to 2.1.x and 2.2 Clean up deployer login code in ServerConnection Key: GERONIMO-3408 URL: https://issues.apache.org/jira/browse/GERONIMO-3408 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0, 2.0.x, 2.1 Reporter: Ted Kirby Assignee: Donald Woods Fix For: 2.1.x, 2.2 Attachments: G3408.patch Currently, the normal login path of the deploy command is a two-pass approach, where an exception is thrown in the first pass. I am cleaning this up and removing what looks like old code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3957) Updating svn:ignore lists
[ https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588564#action_12588564 ] Donald Woods commented on GERONIMO-3957: This should be discussed and voted on before changing the default svn props, as it should be a project-wide set of props that are documented and always set in server, specs, devtools, samples, not just in the server branches. Updating svn:ignore lists - Key: GERONIMO-3957 URL: https://issues.apache.org/jira/browse/GERONIMO-3957 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: general Affects Versions: 2.0.2, 2.1 Reporter: Vasily Zakharov Attachments: Geronimo-3957-20.patch, Geronimo-3957-21.patch, Geronimo-3957-210.patch , Geronimo-3957-Trunk.patch, Geronimo-3957-Trunk.patch When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they just need to be added to the corresponding SVN ignore list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-254) Spaces in server pathname causes problems for the Eclipse Plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-254: - Fix Version/s: (was: 2.1.x) 2.1.0 Moving to 2.1.0 as requested by Donald Spaces in server pathname causes problems for the Eclipse Plugin Key: GERONIMODEVTOOLS-254 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 2.0.0 Environment: Windows Reporter: Tim McConnell Assignee: Shiva Kumar H R Fix For: 2.1.0 When there are spaces in the Geronimo server pathname (on Windows), the Eclipse Plugin will have problems deploying and EAR File. For example the following error will occur: Distribution of configuration failed. See log for details. Error unmarshaling return; nested exception is: java.net.MalformedURLException: no protocol: Files/IBM/WebSphere/AppServerCommunityEdition/repository/org/apache/geronimo/modules/geronimo-common/2.0.1/geronimo-common-2.0.1.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 647737
Geronimo Revision: 647737 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080414/build-0800.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20080414 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 70 minutes 24 seconds [INFO] Finished at: Mon Apr 14 09:36:38 EDT 2008 [INFO] Final Memory: 349M/872M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080414/logs-0800-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20080414/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.943 sec FAILURE! Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20080414/samples-0800.log Build status: OK
Re: Updating svn:ignore lists
Donald, Thank you for reacting on this issue. It doesn't seem to me that the issue is my tool, behavior or style, but in the general approach to the generated files. The existing SVN properties of Geronimo repository shows that in some cases the known generated files are added to svn:ignore list to avoid those files being tracked by the SVN client, and that looks logical to me. What I'm talking about is not a major change, but an attempt to create a consistent set of properties by updating properties for some particular directories. And I can't see how that could impact others, as the proposed change affects only particular generated files and directories, not any global policy of any kind. But if you think it's global enough :), sure, I could start a [DISCUSS] thread. Thanks! Vasily On Mon, Apr 14, 2008 at 4:33 PM, Donald Woods [EMAIL PROTECTED] wrote: If you're a committer on multiple projects, then you need to update your config file or tool (TortoiseSVN in this case) to handle this, instead of expecting everyone to map their svn usage to your tool's behavior or your style Any major changes of svn props should be brought up in a discussion thread with [DISCUSS] as the start of the subject for everyone to review and comment upon before applying, since it could impact others expected svn behavior and needs to be documented for future svn additions. -Donald Vasily Zakharov wrote: Jason, Donald, Thanks for your suggestions, I'll surely follow them. However, I'm not sure that having things like 'target' or 'build' in the exclude list is a wise practice in long-term. So, I think having a consistent approach from the project side is also a good idea. Thanks! Vasily On Fri, Apr 11, 2008 at 2:43 PM, Donald Woods [EMAIL PROTECTED] wrote: Here is what I have in my Subversion config file, which I've accumulated across Windows and Linux - global-ignores = .cvsignore ~$* ~*.tmp *.*~ thumbs.db Thumbs.db *.log .project .classpath .settings target nohup.out build.txt Notice the build.txt, which I have because I like to pipe the build out to a file so I can go back to look at any failed steps, like - mvn install | tee build.txt BTW - Please use the other suggested Apache config settings at - http://cwiki.apache.org/GMOxKB/how-do-i-setup-my-svn-client-for-commits.html Note: You have to add these into TortoiseSVN and the command line svn config file, if you use both -Donald Jason Dillon wrote: Configure your local svn ignores in ~/.subversion/config under the 'global-ignores' property. --jason On Apr 11, 2008, at 12:47 AM, Vasily Zakharov wrote: Well, I'm using TortoiseSVN and it always considers those files to be added to the repository when I'm going to create a patch. This obstructs a create patch/commit dialog with a lot of unneeded entries, and increases the working copy scan time. In fact, I wouldn't raise this issue if I don't see that many other 'target' and 'build' directories are put to svn:ignore lists, while some are not. Vasily On Thu, Apr 10, 2008 at 7:18 PM, Jason Warner [EMAIL PROTECTED] wrote: Hi Vasily, What do you mean by getting in the way? I've never had issues with this. What behavior are you seeing? ~Jason Warner On Thu, Apr 10, 2008 at 1:15 PM, Vasily Zakharov [EMAIL PROTECTED] wrote: When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they need to be added to the corresponding SVN ignore lists. I've created a GERONIMO-3957 for that, and provided patches for trunk, branches/2.1, branches/2.0 and tags/2.1.0. I hope it would be useful. Vasily -- ~Jason Warner
[jira] Updated: (GERONIMO-3955) Typo
[ https://issues.apache.org/jira/browse/GERONIMO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3955: --- Attachment: GERONIMO-3955.patch Typo Key: GERONIMO-3955 URL: https://issues.apache.org/jira/browse/GERONIMO-3955 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Afranio Moraes Assignee: Joseph Leong Priority: Trivial Attachments: GERONIMO-3955.patch Typo in console after editing keystores: Keysore 'keystore.jks' is now edit locked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3955) Typo
[ https://issues.apache.org/jira/browse/GERONIMO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3955: --- Patch Info: [Patch Available] Typo Key: GERONIMO-3955 URL: https://issues.apache.org/jira/browse/GERONIMO-3955 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Afranio Moraes Assignee: Joseph Leong Priority: Trivial Attachments: GERONIMO-3955.patch Typo in console after editing keystores: Keysore 'keystore.jks' is now edit locked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
branches/2.1.1 in prep for a 2.1.1 release
I'd like to branch later today in preparation for a 2.1.1 release (branches/2.1.1) and update branches/2.1 to 2.1.2-SNAPSHOT. Any objections? Minor changes can still be made in branches/2.1.1 while we make preparations for a release candidate. AFAIK the only remaining changes are version updates in the root pom for: OpenEJB 3.0 - Passed vote and currently available in M2 repo. David Blevins are you planning to update this in Geronimo or should I? ActiveMQ 4.1.2 - Passed vote ... not yet available in M2 repo. David Jencks are you planning to update this in Geronimo as soon as the artifacts are pushed? ActiveIO 3.0.1 - Passed vote and currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? tranql-connector-db2-xa 1.2 - Currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? Joe Bohn
[jira] Updated: (GERONIMO-3503) DBPool wizzard creates plans only for local-transactions
[ https://issues.apache.org/jira/browse/GERONIMO-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3503: --- Fix Version/s: (was: 2.1.1) 2.2 2.1.x move fix version to 2.0.x, 2.1.x, and 2.2 doesn't look like it will make 2.1.1 DBPool wizzard creates plans only for local-transactions Key: GERONIMO-3503 URL: https://issues.apache.org/jira/browse/GERONIMO-3503 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Tomasz Mazan Fix For: 2.0.x, 2.1.x, 2.2 I use DatabasePool Wizzard to deploy Pools for PostgresQL. In both cases - I choosed PostgreAQL XA or PostgreSQL Local - wizzard generated plan with model connectionmanager local-transaction/ single-pool max-size10/max-size min-size0/min-size match-one/ /single-pool /connectionmanager -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn updated GERONIMO-3759:
---
Fix Version/s: (was: 2.1.1)
2.2
2.1.x
moving fix version to 2.1.x and 2.2 doesn't look like it will make 2.1.1
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Fix For: 2.1.x, 2.2
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3815) ContextManager.getCurrentContext() throws NullPointerException
[ https://issues.apache.org/jira/browse/GERONIMO-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3815: --- Fix Version/s: (was: 2.1.1) 2.2 2.1.x moving fix version to 2.1.x and 2.2 ... doesn't look like it will make 2.1.1 ContextManager.getCurrentContext() throws NullPointerException -- Key: GERONIMO-3815 URL: https://issues.apache.org/jira/browse/GERONIMO-3815 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.0.2, 2.1 Reporter: Vamsavardhana Reddy Fix For: 2.0.x, 2.1.x, 2.2 Attachments: GERONIMO-3815-2.debug.patch, GERONIMO-3815-3.debug.patch, GERONIMO-3815.debug.patch ContextManager.getCurrentContext() is throwing a NullPointerException. This is observed only when there is heavy load on the application. Most likely it is a threading issue where one thread is unregistering the subject while another is executing getCurrentContext(). Excerpt from stacktrace given below. Caused by: java.lang.NullPointerException at org.apache.geronimo.security.ContextManager.getCurrentContext(ContextManager.java:197) at org.apache.geronimo.openejb.GeronimoSecurityService.isCallerAuthorized(GeronimoSecurityService.java:101) at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:142) at org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267) at org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:321) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy16.create(Unknown Source) ... 53 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3768) deployment failure is not logged in either geronimo.log or deployer.log
[ https://issues.apache.org/jira/browse/GERONIMO-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3768: --- Fix Version/s: (was: 2.1.1) 2.2 2.1.x moving fix version to 2.1.x and 2.2 ... doesn't look like it will make 2.1.1 deployment failure is not logged in either geronimo.log or deployer.log --- Key: GERONIMO-3768 URL: https://issues.apache.org/jira/browse/GERONIMO-3768 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1 Reporter: Kevan Miller Fix For: 2.1.x, 2.2 Deployment failures should be logged, IMO. Yet there's no indication of the following deploy failure. The only failure info is in STDOUT for both server and deploy processes. coltrane:bin kevan$ ./deploy.sh deploy ~/Desktop/OS-Projects/artifactory-1.2.2/webapps/artifactory.war ~/Desktop/OS-Projects/artifactory-1.2.2/webapps/geronimo-web.xml Using GERONIMO_BASE: /Users/kevan/downloads/geronimo-tomcat6-javaee5-2.1-SNAPSHOT Using GERONIMO_HOME: /Users/kevan/downloads/geronimo-tomcat6-javaee5-2.1-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home 12:42:02,694 WARN [AbstractGBeanReference] GBean references are not using proxies org.apache.geronimo.kernel.config.LifecycleException: start of com.kevan/artifactory/1.2.2/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:551) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:515) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at
[jira] Updated: (GERONIMO-3875) Enabling authentication for Derby renders DB Viewer portlet unusable for all db's except SystemDatabase
[
https://issues.apache.org/jira/browse/GERONIMO-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn updated GERONIMO-3875:
---
Fix Version/s: (was: 2.1.1)
2.1.x
moving fix version to 2.1.x and 2.2 doesn't look like it will make 2.1.1
Enabling authentication for Derby renders DB Viewer portlet unusable for all
db's except SystemDatabase
---
Key: GERONIMO-3875
URL: https://issues.apache.org/jira/browse/GERONIMO-3875
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1, 2.1.1, 2.2
Environment: Win XP, G 2.1 Tomcat
Reporter: Vamsavardhana Reddy
Fix For: 2.1.x, 2.2
Attachments: GERONIMO-3875.patch
After enabling authentication for Derby, I am noticing that DB Viewer
portlet is unable to work with any database other that SystemDatabase.
listTables.jsp has the following code:
{code}
%-- Datasource --%
c:if test=${ds == null}
%-- Create the connection manually --%
sql:setDataSource
var=ds
driver=org.apache.derby.jdbc.EmbeddedDriver
url=jdbc:derby:${db};create=true
user=
password=
/
/c:if
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3944) Web plan schema munging reordering elements wrong
[ https://issues.apache.org/jira/browse/GERONIMO-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3944: --- Fix Version/s: (was: 2.1.1) 2.1.x moving fix version to 2.1.x and 2.2 ... doesn't look like it will make 2.1.1 Web plan schema munging reordering elements wrong - Key: GERONIMO-3944 URL: https://issues.apache.org/jira/browse/GERONIMO-3944 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 2.1 Reporter: David Jencks Priority: Blocker Fix For: 2.1.x, 2.2 A user discovered that a tomcat plan with both security and persistence elements gets broken by the schema munging. Original, apparently correct plan: ?xml version=1.0 encoding=UTF-8? web-app xmlns='http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1' dep:environment xmlns:dep='http://geronimo.apache.org/xml/ns/deployment-1.2' dep:moduleId dep:groupIdssi.web/dep:groupId dep:artifactIdequipment-aaf/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdcom.ibm/dep:groupId dep:artifactIdjtopen/dep:artifactId dep:version6.1/dep:version dep:typejar/dep:type /dep:dependency dep:dependency dep:groupIdorg.apache.openjpa/dep:groupId dep:artifactIdopenjpa/dep:artifactId dep:version1.0.2/dep:version dep:typejar/dep:type /dep:dependency !-- dep:dependency dep:groupIdssi/dep:groupId dep:artifactIdssi-api/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:dependency -- dep:dependency dep:groupIdconsole.dbpool/dep:groupId dep:artifactIdjdbc%2FAAF/dep:artifactId dep:version1.0/dep:version dep:typerar/dep:type /dep:dependency /dep:dependencies /dep:environment context-root/aaf/equipment/context-root security-realm-namerealm-SSLIB/security-realm-name security xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; default-principal realm-name=realm-SSLIB principal name=anonymous class=org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal/ /default-principal role-mappings role role-name=equipment-user realm realm-name=realm-SSLIB principal name=ADMIN class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal/ /realm realm realm-name=realm-SSLIB principal name=AAF class=org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal/ /realm /role /role-mappings /security nam:resource-ref xmlns:nam=http://geronimo.apache.org/xml/ns/naming-1.2; nam:ref-namejdbc/ds/nam:ref-name nam:resource-linkjdbc/AAF/nam:resource-link /nam:resource-ref jpa:persistence version=1.0 xmlns:jpa='http://java.sun.com/xml/ns/persistence' jpa:persistence-unit name=equipment-pu transaction-type=JTA jpa:providerorg.apache.openjpa.persistence.PersistenceProviderImpl/jpa:provider jpa:jta-data-sourcejdbc%2FAAF/jpa:jta-data-source jpa:non-jta-data-sourcejdbc%2FAAF/jpa:non-jta-data-source jpa:clai.api.jpa.company.Description/jpa:class jpa:clai.api.jpa.company.Equipment/jpa:class jpa:clai.api.jpa.company.EquipmentMaintanence/jpa:class jpa:clai.api.jpa.company.EquipmentMaintanenceType/jpa:class jpa:clai.api.jpa.company.EquipmentType/jpa:class jpa:exclude-unlisted-classestrue/jpa:exclude-unlisted-classes jpa:properties jpa:property name=openjpa.Log value=DefaultLevel=TRACE,
[jira] Updated: (GERONIMO-3933) Getting an Exception while creating JMS deployment plan through console.
[ https://issues.apache.org/jira/browse/GERONIMO-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3933: --- Fix Version/s: (was: 2.1.1) 2.2 2.1.x moving fix version to 2.1.x and 2.2 doesn't look like it will make 2.1.1 Getting an Exception while creating JMS deployment plan through console. Key: GERONIMO-3933 URL: https://issues.apache.org/jira/browse/GERONIMO-3933 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Environment: Apache Geronimo 2.1 on WindowsXP with Mozilla FireFox Browser while using admin console Reporter: Phani Balaji Madgula Priority: Minor Fix For: 2.1.x, 2.2 Hi I am using AG2.1 for creating deploying a JMS resource plan using admin console. I am using WinXP SP2. First I tried to create the plan using IE 7 but hit the problem mentioned in the JIRA --GERONIMO-3599. Then I switched to FireFox and I was able to get past the error. However after adding a ConnectionFactory a Destination, when I click on the Show Deployment plan, I get the following error as below ** java.lang.IllegalArgumentException: can't parse argument number rarURL at java.text.MessageFormat.makeFormat(MessageFormat.java:1350) at java.text.MessageFormat.applyPattern(MessageFormat.java:470) at org.apache.taglibs.standard.tag.common.fmt.MessageSupport.doEndTag(MessageSupport.java:199) at jsp.WEB_002dINF.view.jmswizard.plan_jsp._jspx_meth_fmt_005fmessage_005f6(plan_jsp.java:673) at jsp.WEB_002dINF.view.jmswizard.plan_jsp._jspService(plan_jsp.java:169) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106) at org.apache.geronimo.console.MultiPagePortlet.doView(MultiPagePortlet.java:151) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101) at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:87) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at
Re: branches/2.1.1 in prep for a 2.1.1 release
I was having some trouble staging the amq stuff but it seems to be going now. I plan to update a bunch of versions in g. when this is complete hopefully soon. thanks david jencks On Apr 14, 2008, at 11:20 AM, Joe Bohn wrote: I'd like to branch later today in preparation for a 2.1.1 release (branches/2.1.1) and update branches/2.1 to 2.1.2-SNAPSHOT. Any objections? Minor changes can still be made in branches/2.1.1 while we make preparations for a release candidate. AFAIK the only remaining changes are version updates in the root pom for: OpenEJB 3.0 - Passed vote and currently available in M2 repo. David Blevins are you planning to update this in Geronimo or should I? ActiveMQ 4.1.2 - Passed vote ... not yet available in M2 repo. David Jencks are you planning to update this in Geronimo as soon as the artifacts are pushed? ActiveIO 3.0.1 - Passed vote and currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? tranql-connector-db2-xa 1.2 - Currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? Joe Bohn
org.apache.geronimo.common.DeploymentException: No web-app element
Hi, I'm deploying an ear with a single webapp on g2.1/jetty. It fails with the following exception. What might be causing it? No web-app element org.apache.geronimo.common.DeploymentException: No web-app element at org.apache.geronimo.web.deployment.GenericToSpecificPlanConverter.convertToSpecificPlan(GenericToSpecificPlanConverter.java:127) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.getJettyWebApp(JettyModuleBuilder.java:330) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.createModule(JettyModuleBuilder.java:252) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:183) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:144) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:873) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:402) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:295) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:226) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:595) Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: svn commit: r647361 - /geronimo/server/branches/2.1/pom.xml
Is there a reason you only updated wadi-aop to 2.0-M10 and not the rest of the WADI artifacts? -Donald Gianny Damour wrote: Hello Joe, It is a change intended for the 2.1 branch as I would like G 2.1.1 to use WADI 2.0-M10. It fixes a replication bug: the dirty flag of a session is reset when a null value is retrieved from a session. As a consequence, session state updates are not pushed to replication peers upon completion of request handling. Hence, sessions recovered from replication servers following a peer crash may not reflect the latest state. Thanks, Gianny On 12/04/2008, at 1:56 PM, Joe Bohn wrote: Gianny, Was this change perhaps intended for trunk rather than branches/2.1 given that 2.0-M10 was just released a few days ago? If you did intend it for 2.1, can you provide some more information on why it is necessary? We are nearly ready to branch for 2.1.1 and I'm trying to keep the changes in the 2.1 branch to an absolute minimum. Thanks, Joe [EMAIL PROTECTED] wrote: Author: gdamour Date: Fri Apr 11 18:24:12 2008 New Revision: 647361 URL: http://svn.apache.org/viewvc?rev=647361view=rev Log: upgrade to 2.0-M10 Modified: geronimo/server/branches/2.1/pom.xml Modified: geronimo/server/branches/2.1/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/pom.xml?rev=647361r1=647360r2=647361view=diff == --- geronimo/server/branches/2.1/pom.xml (original) +++ geronimo/server/branches/2.1/pom.xml Fri Apr 11 18:24:12 2008 @@ -1054,7 +1054,7 @@ dependency groupIdorg.codehaus.wadi/groupId artifactIdwadi-aop/artifactId -version2.0-M9/version +version2.0-M10/version /dependency dependency smime.p7s Description: S/MIME Cryptographic Signature
Re: branches/2.1.1 in prep for a 2.1.1 release
We have different levels of WADI being used in the build right now - 2.0-M10 for wadi-aop 2.0-M9 for other wadi-* depends I think we want everything in WADI at the same level, but will let Gianny answer on the other thread -Donald Joe Bohn wrote: I'd like to branch later today in preparation for a 2.1.1 release (branches/2.1.1) and update branches/2.1 to 2.1.2-SNAPSHOT. Any objections? Minor changes can still be made in branches/2.1.1 while we make preparations for a release candidate. AFAIK the only remaining changes are version updates in the root pom for: OpenEJB 3.0 - Passed vote and currently available in M2 repo. David Blevins are you planning to update this in Geronimo or should I? ActiveMQ 4.1.2 - Passed vote ... not yet available in M2 repo. David Jencks are you planning to update this in Geronimo as soon as the artifacts are pushed? ActiveIO 3.0.1 - Passed vote and currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? tranql-connector-db2-xa 1.2 - Currently available in M2 repo. David Jencks are you planning to update this in Geronimo or should I? Joe Bohn smime.p7s Description: S/MIME Cryptographic Signature
Re: Updating svn:ignore lists
Lets start a discuss thread, since we should be using the same svn props across all the Geronimo subprojects and need input from Devtools, gbuilds, tck and others to make sure we don't break anything -Donald Vasily Zakharov wrote: Donald, Thank you for reacting on this issue. It doesn't seem to me that the issue is my tool, behavior or style, but in the general approach to the generated files. The existing SVN properties of Geronimo repository shows that in some cases the known generated files are added to svn:ignore list to avoid those files being tracked by the SVN client, and that looks logical to me. What I'm talking about is not a major change, but an attempt to create a consistent set of properties by updating properties for some particular directories. And I can't see how that could impact others, as the proposed change affects only particular generated files and directories, not any global policy of any kind. But if you think it's global enough :), sure, I could start a [DISCUSS] thread. Thanks! Vasily On Mon, Apr 14, 2008 at 4:33 PM, Donald Woods [EMAIL PROTECTED] wrote: If you're a committer on multiple projects, then you need to update your config file or tool (TortoiseSVN in this case) to handle this, instead of expecting everyone to map their svn usage to your tool's behavior or your style Any major changes of svn props should be brought up in a discussion thread with [DISCUSS] as the start of the subject for everyone to review and comment upon before applying, since it could impact others expected svn behavior and needs to be documented for future svn additions. -Donald Vasily Zakharov wrote: Jason, Donald, Thanks for your suggestions, I'll surely follow them. However, I'm not sure that having things like 'target' or 'build' in the exclude list is a wise practice in long-term. So, I think having a consistent approach from the project side is also a good idea. Thanks! Vasily On Fri, Apr 11, 2008 at 2:43 PM, Donald Woods [EMAIL PROTECTED] wrote: Here is what I have in my Subversion config file, which I've accumulated across Windows and Linux - global-ignores = .cvsignore ~$* ~*.tmp *.*~ thumbs.db Thumbs.db *.log .project .classpath .settings target nohup.out build.txt Notice the build.txt, which I have because I like to pipe the build out to a file so I can go back to look at any failed steps, like - mvn install | tee build.txt BTW - Please use the other suggested Apache config settings at - http://cwiki.apache.org/GMOxKB/how-do-i-setup-my-svn-client-for-commits.html Note: You have to add these into TortoiseSVN and the command line svn config file, if you use both -Donald Jason Dillon wrote: Configure your local svn ignores in ~/.subversion/config under the 'global-ignores' property. --jason On Apr 11, 2008, at 12:47 AM, Vasily Zakharov wrote: Well, I'm using TortoiseSVN and it always considers those files to be added to the repository when I'm going to create a patch. This obstructs a create patch/commit dialog with a lot of unneeded entries, and increases the working copy scan time. In fact, I wouldn't raise this issue if I don't see that many other 'target' and 'build' directories are put to svn:ignore lists, while some are not. Vasily On Thu, Apr 10, 2008 at 7:18 PM, Jason Warner [EMAIL PROTECTED] wrote: Hi Vasily, What do you mean by getting in the way? I've never had issues with this. What behavior are you seeing? ~Jason Warner On Thu, Apr 10, 2008 at 1:15 PM, Vasily Zakharov [EMAIL PROTECTED] wrote: When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they need to be added to the corresponding SVN ignore lists. I've created a GERONIMO-3957 for that, and provided patches for trunk, branches/2.1, branches/2.0 and tags/2.1.0. I hope it would be useful. Vasily -- ~Jason Warner smime.p7s Description: S/MIME Cryptographic Signature
[jira] Updated: (GERONIMO-3955) Typo
[ https://issues.apache.org/jira/browse/GERONIMO-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-3955: --- Affects Version/s: 2.2 2.1.x Fix Version/s: 2.2 2.1.x Typo Key: GERONIMO-3955 URL: https://issues.apache.org/jira/browse/GERONIMO-3955 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.x, 2.2 Reporter: Afranio Moraes Assignee: Joseph Leong Priority: Trivial Fix For: 2.1.x, 2.2 Attachments: GERONIMO-3955.patch Typo in console after editing keystores: Keysore 'keystore.jks' is now edit locked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: org.apache.geronimo.common.DeploymentException: No web-app element
On Mon, Apr 14, 2008 at 8:59 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: I'm deploying an ear with a single webapp on g2.1/jetty. It fails with the following exception. What might be causing it? No web-app element org.apache.geronimo.common.DeploymentException: No web-app element at org.apache.geronimo.web.deployment.GenericToSpecificPlanConverter.convertToSpecificPlan(GenericToSpecificPlanConverter.java:127) A false alarm - http://issues.apache.org/jira/browse/GERONIMO-3958. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Created: (GERONIMO-3958) No web-app element when geronimo-web.xml contains other root element
No web-app element when geronimo-web.xml contains other root element Key: GERONIMO-3958 URL: https://issues.apache.org/jira/browse/GERONIMO-3958 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment, web Affects Versions: 2.1 Reporter: Jacek Laskowski Tried to deploy a webapp with geronimo-web.xml that contained some other root element than web-app and kept getting the bizzare (and very user-unfriendly) error message: No web-app element org.apache.geronimo.common.DeploymentException: No web-app element at org.apache.geronimo.web.deployment.GenericToSpecificPlanConverter.convertToSpecificPlan(GenericToSpecificPlanConverter.java:127) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.getJettyWebApp(JettyModuleBuilder.java:330) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.createModule(JettyModuleBuilder.java:252) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:183) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:144) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:873) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:402) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:295) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:226) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:595) Couldn't figure out what was wrong until I looked at the source code and found I had correupted geronimo-web.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Just thought I'd share it with you - two Geronimo instances with webapp and remote ejb
Hi, I couldn't believe I did it in a single day. I had never set up two Geronimo instances so I followed Running Multiple Instances of Geronimo [1]. Then created two enterprise applications - one with a webapp and another with a ejb module (noth used a jar library with a remote intf). After struggling with a bit mess after I created an incorrect geronimo-web.xml (GERONIMO-3958: No web-app element when geronimo-web.xml contains other root element) I could finally see my two Geronimos speaking to me nicely. Awesome. Thanks guys! On to describing it on my (polish) blog so people could benefit from it just a little bit. Jacek [1] http://cwiki.apache.org/confluence/display/GMOxDOC21/Running+Multiple+Instances+of+Geronimo [2] http://issues.apache.org/jira/browse/GERONIMO-3958 -- Jacek Laskowski http://www.JacekLaskowski.pl
Subversion Client Configuration questions
I had a question about a disparity between the subversion client configuration file that is provided here [1] and the verification test noted on the same page. For many of the file extensions listed in the configuration, the svn:keywords property is set to just Date Revision. The verification steps say the output from svn propget svn:keywords test-auto-props.xml should be Date Author Id Revision HeadURL. Which is correct? [1] http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html Thanks, -- ~Jason Warner
Re: Subversion Client Configuration questions
Jason Warner wrote: I had a question about a disparity between the subversion client configuration file that is provided here [1] and the verification test noted on the same page. For many of the file extensions listed in the configuration, the svn:keywords property is set to just Date Revision. The verification steps say the output from svn propget svn:keywords test-auto-props.xml should be Date Author Id Revision HeadURL. Which is correct? [1] http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html Thanks, -- ~Jason Warner Yeah, I recall noticing the same difference when I originally set up my svn configuration. We should probably update the wiki to match the expected results (just Date Revision given that is all we set for *.xml files in the earlier step). Joe
[BUILD] trunk: Failed for Revision: 647935
Geronimo Revision: 647935 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 34 minutes [INFO] Finished at: Mon Apr 14 15:53:40 EDT 2008 [INFO] Final Memory: 325M/1014M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/logs-1500-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/logs-1500-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.271 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/samples-1500.log Build status: OK
[jira] Resolved: (GERONIMODEVTOOLS-311) Plugin: org.apache.geronimo.deployment.v21.jaxbmodel
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell resolved GERONIMODEVTOOLS-311. Resolution: Fixed All junit testcases now committed -- resovled. Plugin: org.apache.geronimo.deployment.v21.jaxbmodel Key: GERONIMODEVTOOLS-311 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 648083
Geronimo Revision: 648083 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/build-2100.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 30 minutes 37 seconds [INFO] Finished at: Mon Apr 14 21:42:54 EDT 2008 [INFO] Final Memory: 326M/999M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/logs-2100-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/logs-2100-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 74.739 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20080414/samples-2100.log Build status: OK
[jira] Commented: (GERONIMODEVTOOLS-256) Publish operation after an Eclipse restart deletes a deployed Web Service's server-config.wsdd file
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588890#action_12588890
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-256:
--
Classes to watch for:
\plugins\org.eclipse.jst.ws.axis.consumption.core_*.jar
1)
org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployCommand.class
2)
org.eclipse.jst.ws.internal.axis.consumption.core.command.GeronimoAxisDeployCommand.class
!!
\plugins\org.eclipse.jst.ws.axis.creation.ui_*.jar
3) org.eclipse.jst.ws.internal.axis.creation.ui.wsrt.AxisWebService.class
In class 3) above, observe following method:
public ICommandFactory run(IEnvironment env, IContext ctx, ISelection
sel,
String project, String earProject)
{
...
if
(getWebServiceInfo().getServerFactoryId().equals(org.eclipse.jst.server.geronimo.10))
{
commands.add(new
GeronimoAxisDeployCommand(project));
}
else {
commands.add(new AxisDeployCommand());
}
...
}
Publish operation after an Eclipse restart deletes a deployed Web Service's
server-config.wsdd file
-
Key: GERONIMODEVTOOLS-256
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 2.0.0
Environment: AG 2.0.2 + Geronimo Eclipse Plug-in v2.0 + WTP 2.0.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.0
Steps to recreate:
1) Create a Web Service as per the instructions at
http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpWebService/BottomUpWebService.html
2) Test the web service using (the auto launched) Web Service Explorer.
Everything works fine.
3) Shut down server and restart the server. Again launch the web service. It
runs fine without any error.
4) Shut down server, close eclipse, restart eclipse, start server. This time
try to access the web service and you will not be able to access it.
An initial analysis shows that in Step-4 (after a Eclipse Server restart)
the Publish operation of Eclipse is deleting server-config.wsdd from
GERONIMO_HOME\repository\path-to-deployed-EAR\war name\WEB-INF
directory.
You will get the following error in the console:
17:01:56,218 ERROR [EngineConfigurationFactoryServlet] Unable to find config
file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd
Is this related to the issue reported in
http://mail-archive.ow2.org/jonas-team/2006-08/msg00046.html ? Needs to be
explored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-256) Publish operation after an Eclipse restart deletes a deployed Web Service's server-config.wsdd file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588914#action_12588914 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-256: -- Related Bugzilla report on Eclipse WTP: Need a way to persist server-config.wsdd in the workspace for Axis Web services https://bugs.eclipse.org/bugs/show_bug.cgi?id=119964 Publish operation after an Eclipse restart deletes a deployed Web Service's server-config.wsdd file - Key: GERONIMODEVTOOLS-256 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: AG 2.0.2 + Geronimo Eclipse Plug-in v2.0 + WTP 2.0.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 Steps to recreate: 1) Create a Web Service as per the instructions at http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpWebService/BottomUpWebService.html 2) Test the web service using (the auto launched) Web Service Explorer. Everything works fine. 3) Shut down server and restart the server. Again launch the web service. It runs fine without any error. 4) Shut down server, close eclipse, restart eclipse, start server. This time try to access the web service and you will not be able to access it. An initial analysis shows that in Step-4 (after a Eclipse Server restart) the Publish operation of Eclipse is deleting server-config.wsdd from GERONIMO_HOME\repository\path-to-deployed-EAR\war name\WEB-INF directory. You will get the following error in the console: 17:01:56,218 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd Is this related to the issue reported in http://mail-archive.ow2.org/jonas-team/2006-08/msg00046.html ? Needs to be explored. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
