date:20090708

Geronimo Revision: 792046 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/unit-test-reports
 
[INFO] Compiling 5 source files to 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[46,31]
 [deprecation] org.apache.xbean.recipe.StaticRecipe in org.apache.xbean.recipe 
has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[133,45]
 [deprecation] 
login(java.lang.String,javax.security.auth.callback.CallbackHandler) in 
org.apache.geronimo.security.ContextManager has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[163,84]
 [deprecation] org.apache.xbean.recipe.StaticRecipe in org.apache.xbean.recipe 
has been deprecated

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@4f044f04
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@4f044f04
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/surefire-reports

---
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [jar:jar]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/geronimo-client-2.2-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-client-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/geronimo-client-2.2-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-client/2.2-SNAPSHOT/geronimo-client-2.2-SNAPSHOT.jar
[INFO] 
[INFO] Building Geronimo Plugins, Client :: Client
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : 
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not 
a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : 
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not 
a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@4f044f04
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@4f044f04
[INFO] Generated: 
/home/geronimo/geronimo/trunk/plugins/client/client/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@4f044f04
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@4f044f04
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Dependencies have changed

Re: Duplicate clustername value sets in config-subsititions file

2009-07-08 Thread chi runhua

Rex, thanks for the patch.

The solution is fine with me. If there is no objection or question regarding
the change, I'll update the doc(1) when the patch is applied.

(1) http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html


Jeff C


On Wed, Jul 8, 2009 at 12:22 PM, Rex Wang rwo...@gmail.com wrote:

 Well, I see your jira opened against it and also rename the clusterNodeName
 to farmingClusterNodeName?

 any thoughts?

 -Rex

 2009/7/6 chi runhua chirun...@gmail.com

 Hi all,

 I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in
 config-substitions.properties.  My understanding of them is one for WADI
 clustering and another for farming.

 Can we using different keywords to identify them? ie.  farmingClusterName
 and WADIClusterName or sth. like that.


 Jeff  C

Re: The scope and schedule for G 2.2 samples release

2009-07-08 Thread Forrest_Xia



Jack Cai wrote:
 
 Might want to add some simple JTA samples?
 
 Does the new release include DayTrader?
 
 -Jack
 
  Yes, I've done some work on daytrader some time ago, and I will add those
daytrader to-does (as 
http://www.nabble.com/Daytrader-for-Tomcat-td22290310s134.html Joe
highlighted ) as part of this time G 2.2 samples release stuffs.

Forrest

-- 
View this message in context: 
http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24386489.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: Daytrader for Tomcat

2009-07-08 Thread Forrest_Xia


I will make progress on it as part of G 2.2 sample release work. Thank you
for patience.

If there is anything sounds urgent that you want from me, feel free to let
me know.

Forrest
-- 
View this message in context: 
http://www.nabble.com/Daytrader-for-Tomcat-tp22290310s134p24386522.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

[jira] Commented: (GERONIMO-4024) Accessibility issue: missing image alt tags and no skip to main content support


[ 
https://issues.apache.org/jira/browse/GERONIMO-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728553#action_12728553
 ] 

Shiny Cheng commented on GERONIMO-4024:
---

Both items have been fixed when verified on trunk(rev 791414).   :)

 Accessibility issue: missing image alt tags and no skip to main content 
 support
 ---

 Key: GERONIMO-4024
 URL: https://issues.apache.org/jira/browse/GERONIMO-4024
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1
 Environment: Windows XP SP2
Reporter: Forrest Xia
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.1.2, 2.2


 Test welcome page with screen reader software JAWS, these accessibility 
 issues are found:
 1. No ALT defined for logout image link
 2. No Skip to Main link to allow blinded people to ignore the long list of 
 navagation links, thus the blinded people have to listen to the whole link 
 list again and again when they navigated among the admin console.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (GERONIMO-4024) Accessibility issue: missing image alt tags and no skip to main content support


[ 
https://issues.apache.org/jira/browse/GERONIMO-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728553#action_12728553
 ] 

Shiny Cheng edited comment on GERONIMO-4024 at 7/8/09 1:19 AM:
---

Both items have been fixed when verified on trunk (rev 791414, 2.2-SNAPSHOT).   
:)

  was (Author: yenan):
Both items have been fixed when verified on trunk(rev 791414).   :)
  
 Accessibility issue: missing image alt tags and no skip to main content 
 support
 ---

 Key: GERONIMO-4024
 URL: https://issues.apache.org/jira/browse/GERONIMO-4024
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1
 Environment: Windows XP SP2
Reporter: Forrest Xia
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.1.2, 2.2


 Test welcome page with screen reader software JAWS, these accessibility 
 issues are found:
 1. No ALT defined for logout image link
 2. No Skip to Main link to allow blinded people to ignore the long list of 
 navagation links, thus the blinded people have to listen to the whole link 
 list again and again when they navigated among the admin console.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4027) Accessibility issue: Tree icons in high contrast mode cannot be seen


[ 
https://issues.apache.org/jira/browse/GERONIMO-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728558#action_12728558
 ] 

Shiny Cheng commented on GERONIMO-4027:
---

When I tried to verify the problem on trunk (rev 791414, 2.2-SNAPSHOT), I found 
the problem still existed. 
Icons of Classloader tree, JNDI tree, Dependency tree still can't been seen in 
the high contrast mode while those of JMX and LDAP work correctly.  

 Accessibility issue: Tree icons in high contrast mode cannot be seen
 

 Key: GERONIMO-4027
 URL: https://issues.apache.org/jira/browse/GERONIMO-4027
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1
 Environment: Windows XP SP2, IE 6.0
Reporter: Forrest Xia
Assignee: Lin Sun
Priority: Minor
 Attachments: GERONIMO-4027-2.patch, GERONIMO-4027.patch


 To enable low-vision people to use admin console, the tree icons in these 
 pages shall be improved:
 Classloader tree
 JNDI tree
 Dependency tree
 Note that, after tested, only MBeans tree's icon could be seen in the high 
 contrast mode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-519) Document the Deployment Plan editors


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728566#action_12728566
 ] 

Rex Wang commented on GERONIMODEVTOOLS-519:
---

Sophia has added a page 
http://cwiki.apache.org/confluence/display/GMOxDOC22/Making+deployment+plan+changes+with+Geronimo+Deployment+Plan+Editor
 to introduce how to use plan editor with a sample. I think it is enough for 
this function. Any thoughts?

-Rex

 Document the Deployment Plan editors
 

 Key: GERONIMODEVTOOLS-519
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519
 Project: Geronimo-Devtools
  Issue Type: Sub-task
  Components: eclipse-plugin
Affects Versions: 2.2.0
Reporter: B.J. Reed
Assignee: B.J. Reed
Priority: Minor
 Fix For: 2.2.0


 As the Deployment Plan Editors are completed, we need to add detailed 
 documentation for the use of each editor and page.  It should be hooked into 
 the existing documentation on the 
 http://geronimo.apache.org/development-tools.html page.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-361) GEP DependencyHelper not interrogating all contents of EAR files for dependencies


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728576#action_12728576
 ] 

Rex Wang commented on GERONIMODEVTOOLS-361:
---

Could you provide more detail on this?

-Rex

 GEP DependencyHelper not interrogating all contents of EAR files for 
 dependencies
 -

 Key: GERONIMODEVTOOLS-361
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-361
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.1
Reporter: Tim McConnell
Assignee: Tim McConnell
 Fix For: 2.2.0




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration

2009-07-08 Thread Forrest Xia (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728586#action_12728586
]

Forrest Xia commented on GERONIMO-4475:
---

A bug found:
if stopped a new created broker, the JMS resources page will show nothing, even
the default broker is still running!
Moreover, the jms connector module which depends on the new created broker is
still in running state. But we should expect it in stopped state.

Improve JMS portlet for AMQ 5.3 Broker configuration

Key: GERONIMO-4475
URL: https://issues.apache.org/jira/browse/GERONIMO-4475
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2
Reporter: Ivan
Assignee: Ivan
Fix For: 2.2

Attachments: G4475-activemq-broker-00.patch,
G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch,
G4475-geronimo-activemq.patch, G4475-geronimo-management.patch

Currently in the administrator console, the users could not add another embed
broker. Also, they could not edit the broker through administrator console.
I list the features that I could see :
1. While creating the broker, let the use upload a configuration file.
2. While editing the broker, show a text area, so that the user could edit
the spring XML file in it. Shall we give the user a more friendly interface,
so that they do not need the edit the XML file directly. I am not sure how it
should look like.
3. Update the connector port let, so that while creating a new connector,
the user could specify the broker that it belongs to.
Please help to give some comments !

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (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:all-tabpanel
]

Rex Wang updated GERONIMODEVTOOLS-256:
--

Seems it is a bug of WTP, I think we can closed this coz gep2.2 are based on
wtp3.1
-Rex

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
Fix For: 2.2.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.

Re: Duplicate clustername value sets in config-subsititions file

2009-07-08 Thread Gianny Damour


Hi,

It seems to me that farmName would be better than farmingClusterName  
as there is a clear distinction between a farm and a cluster.


Thanks,
Gianny

On 06/07/2009, at 7:47 PM, chi runhua wrote:


Hi all,

I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in  
config-substitions.properties.  My understanding of them is one for  
WADI clustering and another for farming.


Can we using different keywords to identify them? ie.   
farmingClusterName and WADIClusterName or sth. like that.



Jeff  C

Re: Web app clustering with WADI in Geronimo Tomcat 2.1.4 broken?

2009-07-08 Thread Gianny Damour


Hi,

In addition to this doc update, what about trying to uniformise the  
node name?


if the XSD was not extracted, then it was an oversight.

Thanks,
Gianny


On 08/07/2009, at 12:34 PM, chi runhua wrote:


Hi all,

Doc updated for both 2.1 and 2.2 by now.

If you are using a Tomcat assembly of Geronimo distribution,  
replace clustering-wadi/ with tomcat-clustering-wadi/ element  
in the deployment plan.


(1)   http://cwiki.apache.org/confluence/display/GMOxDOC21/WADI 
+Clustering+Support
(2)   http://cwiki.apache.org/confluence/display/GMOxDOC22/WADI 
+Clustering



And one more question, is there any reason that the schema file  
!-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom:  
0.08in } -- (ie. geronimo-tomcat-clustering-wadi-X.xsd ) was not  
extracted to geronimo_home/schema after build.


Thanks.

Jeff C

On Tue, Jul 7, 2009 at 6:58 PM, Gianny Damour  
gianny.dam...@optusnet.com.au wrote:

Hi Vamsi,

In the case of tomcat, you need to use the node

tomcat-clustering-wadi /

instead of

clustering-wadi /


I wonder if it would not be better to uniformise node names across  
Jetty and Tomcat to prevent confusion.


Thanks,
Gianny


On 07/07/2009, at 4:57 PM, Vamsavardhana Reddy wrote:

I am trying to deploy a clustered web application in Geronimo  
Tomcat 2.1.4.  I have added distributable/ in web.xml and  
clustering-wadi/ in geronimo-web.xml.  When I deploy the  
application, I am getting the following deployment error:


xml problem for web app .
org.apache.geronimo.common.DeploymentException: xml problem for web  
app .
at  
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWeb 
App(TomcatModuleBuilder.java:318)
at  
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule 
(TomcatModuleBuilder.java:207)
at  
org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createMo 
dule(AbstractWebModuleBuilder.java:179)
at  
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModul 
e(SwitchingModuleBuilder.java:94)
at  
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan 
(EARConfigBuilder.java:307)

at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:227)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:134)
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.doDe 
ploy(AbstractDeployCommand.java:116)
at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run 
(DistributeCommand.java:61)

at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.xmlbeans.XmlException: Invalid deployment  
descriptor: errors:


error: cvc-complex-type.2.4a: Expected elements 'work-...@http:// 
geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http:// 
geronimo.apache.org/xml/ns/j2ee/application-2.0 web- 
contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http:// 
geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- 
cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1  
disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/ 
tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/ 
tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/ 
web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/ 
j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/ 
j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/ 
j2ee/web/tomcat-2.0.1 abstract-naming-en...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 service-...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 resource-...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http:// 
geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http:// 
geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http:// 
geronimo.apache.org/xml/ns/deployment-1.2 persiste...@http:// 
java.sun.com/xml/ns/persistence' instead of 'clustering-w...@http:// 
geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here


Descriptor:
xml-fragment xmlns:tom=http://geronimo.apache.org/xml/ns/j2ee/web/ 
tomcat-2.0.1
!--web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/ 
tomcat-2.0.1 xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/

[jira] Commented: (GERONIMODEVTOOLS-424) Port Plan Creator work into GEP Deployment Plan Editor


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728627#action_12728627
 ] 

Rex Wang commented on GERONIMODEVTOOLS-424:
---

All the sub projects have been resolved, so suggest close it.

-Rex

 Port Plan Creator work into GEP Deployment Plan Editor
 --

 Key: GERONIMODEVTOOLS-424
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-424
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 2.1.3
Reporter: Shiva Kumar H R
 Fix For: 2.2.0


 Port the features of Plan Creator into GEP Deployment Plan Editor, thereby 
 enabling intuitive creation/editing of Geronimo Deployment Plans.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-67) M2 plugin to generate WTP adopter API usage report


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728635#action_12728635
 ] 

Rex Wang commented on GERONIMODEVTOOLS-67:
--

Really a old jira..What's the point of it? If not idea, suggest close it.
-Rex

 M2 plugin to generate WTP adopter API usage report
 --

 Key: GERONIMODEVTOOLS-67
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-67
 Project: Geronimo-Devtools
  Issue Type: Task
  Components: eclipse-plugin
Affects Versions: 2.1.3
Reporter: Sachin Patel
Assignee: Tim McConnell
Priority: Minor
 Fix For: 2.2.0




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-217) Installation directory inconsistent across the various versions of the Geronimo server


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728643#action_12728643
 ] 

Rex Wang commented on GERONIMODEVTOOLS-217:
---

after discuss with Delos, seems this function has been eliminated from GEP, so 
suggest close it.
-Rex

 Installation directory inconsistent across the various versions of the 
 Geronimo server
 --

 Key: GERONIMODEVTOOLS-217
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-217
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.0.2
Reporter: Tim McConnell
Assignee: Tim McConnell



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMODEVTOOLS-101) remote debugging


 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rex Wang updated GERONIMODEVTOOLS-101:
--


Really a old request, if there is not enough motivation to implement it, 
suggest close it
-Rex

 remote debugging
 

 Key: GERONIMODEVTOOLS-101
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-101
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 2.1.3
 Environment: IBM JVM 1.5, Eclipse 3.2.0, WTP 1.5, w2k/w3k, remote 
 either w?k or linux 
Reporter: Oleg Gusakov
Assignee: Tim McConnell
 Fix For: 2.2.0


 The publish by copy seems to open a very interesting possibility of 
 publishing to a remote server and attaching to it fro remote debugging. As 
 this is possible to do manually, I think plugin should be able to support 
 such deployment - maybe setup a file receiver on the other end. 
 Such functionality will definitely open the door into real life 
 [semi-]production debugging. Even QA problems may be solved much faster.

-- 
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: 792107

Geronimo Revision: 792107 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/unit-test-reports
 
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 5 source files to 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/classes
[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[46,31]
 [deprecation] org.apache.xbean.recipe.StaticRecipe in org.apache.xbean.recipe 
has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[133,45]
 [deprecation] 
login(java.lang.String,javax.security.auth.callback.CallbackHandler) in 
org.apache.geronimo.security.ContextManager has been deprecated

[WARNING] 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/main/java/org/apache/geronimo/client/AppClientContainer.java:[163,84]
 [deprecation] org.apache.xbean.recipe.StaticRecipe in org.apache.xbean.recipe 
has been deprecated

[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/surefire-reports

---
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [jar:jar]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/geronimo-client-2.2-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-client-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/client/geronimo-client/target/geronimo-client-2.2-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-client/2.2-SNAPSHOT/geronimo-client-2.2-SNAPSHOT.jar
[INFO] 
[INFO] Building Geronimo Plugins, Client :: Client
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : 
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not 
a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : 
template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not 
a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: 
/home/geronimo/geronimo/trunk/plugins/client/client/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Dependencies have changed:
Removed dependencies are saved here: 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/history/dependencies.removed.xml
Tree listing is saved here: 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/history/treeListing.txt
Delete 
/home/geronimo/geronimo/trunk/plugins/client/client/src/main/history/dependencies.xml
 if you are happy with the dependency changes.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException

[jira] Closed: (GERONIMO-4024) Accessibility issue: missing image alt tags and no skip to main content support

2009-07-08 Thread Donald Woods (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods closed GERONIMO-4024.
--


verified by Shiny Cheng

 Accessibility issue: missing image alt tags and no skip to main content 
 support
 ---

 Key: GERONIMO-4024
 URL: https://issues.apache.org/jira/browse/GERONIMO-4024
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1
 Environment: Windows XP SP2
Reporter: Forrest Xia
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.1.2, 2.2


 Test welcome page with screen reader software JAWS, these accessibility 
 issues are found:
 1. No ALT defined for logout image link
 2. No Skip to Main link to allow blinded people to ignore the long list of 
 navagation links, thus the blinded people have to listen to the whole link 
 list again and again when they navigated among the admin console.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4706) DB2 XA properties show crash code in database pool porlet

2009-07-08 Thread Ivan (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan reassigned GERONIMO-4706:
--

Assignee: Ivan  (was: viola.lu)

 DB2 XA properties show crash code in database pool porlet
 -

 Key: GERONIMO-4706
 URL: https://issues.apache.org/jira/browse/GERONIMO-4706
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: os:win2003
Reporter: viola.lu
Assignee: Ivan
Priority: Minor
 Fix For: 2.2

 Attachments: GERONIMO-4706.patch, GERONIMO-4706_v2.patch, 
 GERONIMO-4706_zh.patch


 1.Go to g console, click Database pools, create a db2 xa datasource, in the 
 first page, there are two newly added properites:
 Downgrade Hold Cursors and ResultSet Holds, but it display crash code: 
 question mark.Becasue their corresponding values are not included into 
 message file: systemdatabase.properties
 So update it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4706) DB2 XA properties show crash code in database pool porlet

2009-07-08 Thread Ivan (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan updated GERONIMO-4706:
---

Fix Version/s: 2.2

 DB2 XA properties show crash code in database pool porlet
 -

 Key: GERONIMO-4706
 URL: https://issues.apache.org/jira/browse/GERONIMO-4706
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: os:win2003
Reporter: viola.lu
Assignee: Ivan
Priority: Minor
 Fix For: 2.2

 Attachments: GERONIMO-4706.patch, GERONIMO-4706_v2.patch, 
 GERONIMO-4706_zh.patch


 1.Go to g console, click Database pools, create a db2 xa datasource, in the 
 first page, there are two newly added properites:
 Downgrade Hold Cursors and ResultSet Holds, but it display crash code: 
 question mark.Becasue their corresponding values are not included into 
 message file: systemdatabase.properties
 So update it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4728) Can't access EJB Server portlet with IPV6 address.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Jiang reassigned GERONIMO-4728:
-

Assignee: Shawn Jiang

 Can't access EJB Server portlet with IPV6 address.
 --

 Key: GERONIMO-4728
 URL: https://issues.apache.org/jira/browse/GERONIMO-4728
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: tomcat geronimo server 2.2_2009-07-03  + windows XP + 
 firefox 3.5
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor

 1, enable ipv6 in windows
 2, start server
 3, ipconfig to find ipv6 address of host server.  My ip is:
 2002:97b:e933::97b:e933
 4, use 
 {noformat}http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server
  {noformat} to access EJB Server.  
 Result: EJB server portlet can't be displayed.
 After swicthing to http://localhost:8080/console/portal/Server/EJB%20Server , 
 the portlet is working well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMODEVTOOLS-101) remote debugging

2009-07-08 Thread Oleg Gusakov (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728731#action_12728731
 ] 

Oleg Gusakov commented on GERONIMODEVTOOLS-101:
---

Please close, as the need to do it has gone, and there was too low friction in 
the community.

 remote debugging
 

 Key: GERONIMODEVTOOLS-101
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-101
 Project: Geronimo-Devtools
  Issue Type: New Feature
  Components: eclipse-plugin
Affects Versions: 2.1.3
 Environment: IBM JVM 1.5, Eclipse 3.2.0, WTP 1.5, w2k/w3k, remote 
 either w?k or linux 
Reporter: Oleg Gusakov
Assignee: Tim McConnell
 Fix For: 2.2.0


 The publish by copy seems to open a very interesting possibility of 
 publishing to a remote server and attaching to it fro remote debugging. As 
 this is possible to do manually, I think plugin should be able to support 
 such deployment - maybe setup a file receiver on the other end. 
 Such functionality will definitely open the door into real life 
 [semi-]production debugging. Even QA problems may be solved much faster.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4678) Initial Japanese translation


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor reassigned GERONIMO-4678:
-

Assignee: Jarek Gawor  (was: Kan Ogawa)

 Initial Japanese translation
 

 Key: GERONIMO-4678
 URL: https://issues.apache.org/jira/browse/GERONIMO-4678
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: console
Reporter: Kan Ogawa
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: geronimo-v21_i18n-ja_G4485-G4532_v1.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-4711) Geronimo Blueprint throws org.osgi.service.blueprint.container.ComponentDefinitionException: Cound not create component instance


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-4711.
---

Resolution: Invalid

Closing as it sounds like this was an issue with Gshell's namespace handler.


 Geronimo Blueprint throws 
 org.osgi.service.blueprint.container.ComponentDefinitionException: Cound not 
 create component instance
 

 Key: GERONIMO-4711
 URL: https://issues.apache.org/jira/browse/GERONIMO-4711
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
 Environment: Ubuntu 9.04, Sun JDK 6u10, Felix 1.8.0, Karaf SNAPSHOT, 
 Blueprint SNAPSHOT
Reporter: Hendy Irawan
 Attachments: caterpillar-blueprint-bug-sampler.tar.bz2, 
 caterpillar-blueprint-stacktrace.txt


 Component should be Geronimo Blueprint, but I can't find it in the list.
 Relevant context of my Blueprint XML is as below. Do I write the XML 
 correctly?
 ?xml version=1.0 encoding=UTF-8?
 blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;
 command-bundle xmlns=http://felix.apache.org/karaf/xmlns/gshell/v1.0.0;
 command name=ou/show
 action factory-bean=qi4jApp factory-method=createShowState
 property name=bundleContext ref=blueprintBundleContext/
 property name=project ref=theProject /
 /action
 /command
 /command-bundle
   bean id=qi4jApp class=com.openubiquity.caterpillar.Qi4jApp
   /bean
   
   bean id=theProject 
 class=com.openubiquity.caterpillar.SpringProject
   property name=name value=Caterpillar /
   property name=contextFiles
   list
   valuebundle-context-osgi.xml/value
   valuebundle-context.xml/value
   /list
   /property
   /bean
   
 /blueprint
 BTW, what is the URL of Blueprint XSD ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4717) There are some texts that aren't pulled out in the activemq portlet.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor reassigned GERONIMO-4717:
-

Assignee: Jarek Gawor  (was: Kan Ogawa)

 There are some texts that aren't pulled out in the activemq portlet.
 

 Key: GERONIMO-4717
 URL: https://issues.apache.org/jira/browse/GERONIMO-4717
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
Reporter: Kan Ogawa
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: activemq-portlets_v21.patch, activemq-portlets_v22.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4678) Initial Japanese translation


[ 
https://issues.apache.org/jira/browse/GERONIMO-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728757#action_12728757
 ] 

Jarek Gawor commented on GERONIMO-4678:
---

Patch committed to branches/2.1 (revision 792207). Thanks so much!

Will the same patch work for trunk or a different one is needed?


 Initial Japanese translation
 

 Key: GERONIMO-4678
 URL: https://issues.apache.org/jira/browse/GERONIMO-4678
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: console
Reporter: Kan Ogawa
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: geronimo-v21_i18n-ja_G4485-G4532_v1.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-4717) There are some texts that aren't pulled out in the activemq portlet.


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-4717.
---

Resolution: Fixed

Committed the patches to trunk (revision 792231) and branches/2.1 (revision 
792230). Thanks for these patches!


 There are some texts that aren't pulled out in the activemq portlet.
 

 Key: GERONIMO-4717
 URL: https://issues.apache.org/jira/browse/GERONIMO-4717
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
Reporter: Kan Ogawa
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: activemq-portlets_v21.patch, activemq-portlets_v22.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-4675) Duplicate Key in config-substitutions.properties


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Gawor resolved GERONIMO-4675.
---

Resolution: Duplicate

 Duplicate Key in config-substitutions.properties
 

 Key: GERONIMO-4675
 URL: https://issues.apache.org/jira/browse/GERONIMO-4675
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: common, documentation, general
Affects Versions: 2.1.4
Reporter: Christian Burger
Priority: Minor

 Duplicate Key in config-substitutions.properties:
 ClusterName=DEFAULT_CLUSTER
 AND
 clusterName=CLUSTER_NAME
 Different cases!  But if it's the same key, you should probably remove one 
 and correct the code correspondingly, or?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-4599) EJbs not visible in jndi viewer, possibly classloading problem

2009-07-08 Thread David Jencks (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks closed GERONIMO-4599.
--

Resolution: Fixed

Related to OPENEJB-1014.  Geronimo changes in rev 792235.

 EJbs not visible in jndi viewer, possibly classloading problem
 --

 Key: GERONIMO-4599
 URL: https://issues.apache.org/jira/browse/GERONIMO-4599
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console, naming, OpenEJB
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2


 In both 2.1.4-SNAPSHOT and trunk I can't see any ejbs in the console jndi 
 viewer in the global context.  In trunk when I open the jndi viewer portlet 
 page I get a stack trace which might indicate the cause.  I'm wondering why 
 we aren't just using xbean for the global context for ejbs?
 2009-03-22 10:13:45,226 WARN  [JNDIViewPortlet] Error listing context
 org.apache.openejb.OpenEJBException: Error copying object into local class 
 loader: org.apache.openejb.core.ivm.IntraVmProxy in classloader 
 org.apache.geronimo.plugins/debugviews-console-jetty/2.2-SNAPSHOT/car
 at 
 org.apache.openejb.core.ivm.naming.NamingException.init(NamingException.java:29)
 at 
 org.apache.openejb.core.ivm.naming.CrossClassLoaderJndiReference.getObject(CrossClassLoaderJndiReference.java:38)
 at 
 org.apache.openejb.assembler.classic.LazyEjbReference.getObject(LazyEjbReference.java:91)
 at 
 org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40)
 at 
 org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61)
 at 
 org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:122)
 at 
 org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildContextSub(JNDIViewPortlet.java:351)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildContextSub(JNDIViewPortlet.java:353)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildContextSub(JNDIViewPortlet.java:353)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildContextSub(JNDIViewPortlet.java:353)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildContext(JNDIViewPortlet.java:338)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.buildEJBModule(JNDIViewPortlet.java:195)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.getContextTree(JNDIViewPortlet.java:442)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.getJSONTrees(JNDIViewPortlet.java:114)
 at 
 org.apache.geronimo.console.jndiview.JNDIViewPortlet.doView(JNDIViewPortlet.java:78)
 at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
 at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
 at 
 org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
 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.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
 at 
 org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:65)
 at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
 at 
 org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at 
 org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:114)
 at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
 at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
 at 
 org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
 at 
 org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(TwistyWebAppContext.java:41)
 at 
 org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(TwistyWebAppContext.java:66)
 at 
 org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
 at 
 org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67)
 at 
 org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
 at 
 org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)

[jira] Commented: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1


[ 
https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728818#action_12728818
 ] 

Jarek Gawor commented on GERONIMO-4532:
---

I committed the mconsole-war_2nd.patch patch to branches/2.1 (revision 
792240). Thanks!

Is there anything else that needs to be done for this bug or can it be closed?


 Port the GERONIMO-4484 patch for V2.1
 -

 Key: GERONIMO-4532
 URL: https://issues.apache.org/jira/browse/GERONIMO-4532
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4
Reporter: Kan Ogawa
Assignee: Kan Ogawa
Priority: Minor
 Fix For: 2.1.5

 Attachments: activemq-portlets.patch, console-base-portlets.patch, 
 console-core.patch, console-portal-driver.patch, debugviews-portlets.patch, 
 mconsole-war.patch, mconsole-war_2nd.patch, plancreator-portlets.patch, 
 plugin-portlets.patch, sysdb-portlets.patch


 I think that this issue is very important.
 After the GERONIMO-4485 patches are committed, I will try to port 
 GERONIMO-4484 patches for 2.1 version.

-- 
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: 792246

Geronimo Revision: 792246 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 11 seconds
[INFO] Finished at: Wed Jul 08 15:44:24 EDT 2009
[INFO] Final Memory: 403M/1014M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-1500-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-1500-jetty/
 
 
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:48.789
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:16.191) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:37.685) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.255) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.892) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:26.631) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:36.048) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:08.275) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:53.750) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:02.195) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.661) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.469) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.291) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.191) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.625) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:59.583) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.770) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.206) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.518) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:50.894) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.767) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.074) 
[INFO] web-testsuite/test-jetty

[jira] Commented: (GERONIMO-4728) Can't access EJB Server portlet with IPV6 address.


[ 
https://issues.apache.org/jira/browse/GERONIMO-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729008#action_12729008
 ] 

Shawn Jiang commented on GERONIMO-4728:
---

I see this error
{noformat}
Error: Could not load 'dijit.Tree'; last tried '../dijit/Tree.js'
Source File: http://[2002:97b:e933::97b:e933]:8080/dojo/dojo/dojo.js
Line: 7
{noformat}
in firefox Error console when using IPV6 address.  I noticed that dojo.js has 
some TODO: support IPV6.  This might be a defect of DOJO.

 Can't access EJB Server portlet with IPV6 address.
 --

 Key: GERONIMO-4728
 URL: https://issues.apache.org/jira/browse/GERONIMO-4728
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: tomcat geronimo server 2.2_2009-07-03  + windows XP + 
 firefox 3.5
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor

 1, enable ipv6 in windows
 2, start server
 3, ipconfig to find ipv6 address of host server.  My ip is:
 2002:97b:e933::97b:e933
 4, use 
 {noformat}http://[2002:97b:e933::97b:e933]:8080/console/portal/Server/EJB%20Server
  {noformat} to access EJB Server.  
 Result: EJB server portlet can't be displayed.
 After swicthing to http://localhost:8080/console/portal/Server/EJB%20Server , 
 the portlet is working well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-4532) Port the GERONIMO-4484 patch for V2.1

2009-07-08 Thread Kan Ogawa (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa closed GERONIMO-4532.
---

Resolution: Fixed

Thanks a lot, Jarek!

The regression bug that I found is a monitoring console mistake only.

Closing this issue once.
Unless new mistake is found, please don't reopen it.

 Port the GERONIMO-4484 patch for V2.1
 -

 Key: GERONIMO-4532
 URL: https://issues.apache.org/jira/browse/GERONIMO-4532
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4
Reporter: Kan Ogawa
Assignee: Kan Ogawa
Priority: Minor
 Fix For: 2.1.5

 Attachments: activemq-portlets.patch, console-base-portlets.patch, 
 console-core.patch, console-portal-driver.patch, debugviews-portlets.patch, 
 mconsole-war.patch, mconsole-war_2nd.patch, plancreator-portlets.patch, 
 plugin-portlets.patch, sysdb-portlets.patch


 I think that this issue is very important.
 After the GERONIMO-4485 patches are committed, I will try to port 
 GERONIMO-4484 patches for 2.1 version.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4509) Two EJB server portlet issues

2009-07-08 Thread Forrest Xia (JIRA)

[
https://issues.apache.org/jira/browse/GERONIMO-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729011#action_12729011
]

Forrest Xia commented on GERONIMO-4509:
---

For #2, I verified and confirm it's fixed iin G2.2 snapshot build on July 7.

For #1, I think, since openejb module is a fundamental one of geronimo, if
prompting user to just restart it, it will cause server hang. So I would
suggest to change the prompt message to notify user to restart the overall
server as a whole. Any comments?

Two EJB server portlet issues
-

Key: GERONIMO-4509
URL: https://issues.apache.org/jira/browse/GERONIMO-4509
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2
Environment: JDK 1.6
Ubuntu 8.04
AG 2.2 snapshot 20090110
Reporter: Forrest Xia
Assignee: Forrest Xia

For the new EJB server portlet, there are these problems:
1. Message prompt just restarting openejb module cause several console
exceptions and EJB server portlet disappear in admin console at next time
restart server.
Steps:
1.1 Change value of a EJB container parameter, then it prompts OpenEJB module
should be restarted for effectiveness. So I use expert mode to restart module
org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car, confirm restart, then
several exceptions are thrown out as following:
2009-01-14 09:35:45,546 ERROR [ConfigManagerPortlet] Exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car still has children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...
2009-01-14 09:35:45,965 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.NullPointerException
at
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.getConfigurationState(ConfigManagerPortlet.java:325)
at
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:272)
...
2009-01-14 09:37:08,300 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/jaxws-ejb-deployer/2.2-SNAPSHOT/car still has
children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...
2009-01-14 09:37:19,125 ERROR [[SystemModules]] Servlet.service() for servlet
SystemModules threw exception
java.lang.IllegalStateException: Configuration
org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car still has
children
at
org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
at
org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
...
Anyway, the openejb module finally restarted, but no children modules appear
anymore. Consequently the EJB server portlet disappears from the admin
console. No way to check if the changed parameter takes effect.
2.2 Followed by step 1, restart geronimo by no change of config.xml, still
the EJB server portlet is not there. Then check the config.xml, the portlet
module module
name=org.apache.geronimo.plugins/openejb-console-tomcat/2.2-SNAPSHOT/car/
is load=false
Based on the symptom, I think it might be better to suggest user to restart
geronimo server as a whole, not just openejb module.
2. Another issue is the parameter value seems be changed only once. For
example, if you changed strictpooling from default true to false, then you
want to change it back without restarting server, there is no way. This
behavior is better to be improved.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.

Jetty build does not support IPV6 address in browser.
-

 Key: GERONIMO-4731
 URL: https://issues.apache.org/jira/browse/GERONIMO-4731
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Jetty
Affects Versions: 2.1.5, 2.2
 Environment: geronimo-jetty-2.2-snapshot + windows + ipv6 + sun jdk 1.6
Reporter: Shawn Jiang


In ipv6 enabled wondows. 

1, Start geronimo-tomcat-2.2-snapshot instance A with:

ServerHostname=0.0.0.0
PortOffset=0

2, Start geronimo-jetty-2.2-snapshot instance B with:

ServerHostname=0.0.0.0
PortOffset=10

3, netstat -na

 TCP[::]:1050  [::]:0 LISTENING
 TCP[::]:1060  [::]:0 LISTENING

 TCP[::]:1099  [::]:0 LISTENING
 TCP[::]:1109  [::]:0 LISTENING

 TCP[::]:1527  [::]:0 LISTENING
 TCP[::]:1537  [::]:0 LISTENING

 TCP[::]:2001  [::]:0 LISTENING
 TCP[::]:2011  [::]:0 LISTENING

 TCP[::]:4201  [::]:0 LISTENING
 TCP[::]:4211  [::]:0 LISTENING

 TCP[::]:6882  [::]:0 LISTENING
 TCP[::]:6892  [::]:0 LISTENING

 TCP[::]:8009  [::]:0 LISTENING
 TCP[::]:8019  [::]:0 LISTENING

 TCP[::]:8080  [::]:0 LISTENING

 TCP[::]:8443  [::]:0 LISTENING

 TCP[::]:  [::]:0 LISTENING
 TCP[::]:10009 [::]:0 LISTENING

 TCP[::]:61616 [::]:0 LISTENING
 TCP[::]:61626 [::]:0 LISTENING


4, noticed that  Jetty instance is not listening on  [::]:8090 and [::]:8453.   
As a result, you can't access http://[ipv6-ip]:8090/console successfully while 
you can access tomcat instance with http://[ipv6-ip]:8080/console





-- 
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: 792362

Geronimo Revision: 792362 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 39 minutes 31 seconds
[INFO] Finished at: Wed Jul 08 21:43:42 EDT 2009
[INFO] Final Memory: 471M/989M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-2100-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-2100-jetty/
 
 
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:43.605
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:03.297) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:33.522) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:36.468) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.518) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:19.706) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:20.118) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:07.360) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:53.925) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:05.839) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.190) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.381) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.887) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:37.445) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:45.058) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.867) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.816) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.000) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.157) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:47.663) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.885) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:33.907) 
[INFO] web-testsuite/test-jetty   RUNNING
[INFO] web-testsuite/test-jetty   SUCCESS (0:00:26.405) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces

[jira] Commented: (GERONIMO-4025) Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console


[ 
https://issues.apache.org/jira/browse/GERONIMO-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729017#action_12729017
 ] 

Shiny Cheng commented on GERONIMO-4025:
---

I have checked the modified files according to the lists on svn commits. Most 
of the properties have been properly added, but a small portion still missed 
the scope attribute. I guess may be those are new added ones after Rex fixed 
them.  

Here is the list of files which miss some of the scope attribute.
/geronimo/server/trunk/plugins/activemq/activemq-portlets/src/main/webapp/WEB-INF/view/jmsmanager/server/normal.jsp
/geronimo/server/trunk/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/webmanager/connector/normal.jsp
 
Please help me to verify them. Thanks.

 Accessibility issues: No caption tag or summary property, no column and row 
 scope property for data tables in admin console
 ---

 Key: GERONIMO-4025
 URL: https://issues.apache.org/jira/browse/GERONIMO-4025
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1, 2.1.2, 2.1.x, 2.2
 Environment: Windows XP SP2, IE 6.0
 JAWS 8.0
Reporter: Forrest Xia
Assignee: Donald Woods
 Fix For: 2.2

 Attachments: GERONIMO-4025-activemq-and-monitoring.patch, 
 GERONIMO-4025-configmanager-and-infomanager.patch, 
 GERONIMO-4025-console.patch, GERONIMO-4025-DB-Properties_zh.patch, 
 GERONIMO-4025-DB-style.patch, GERONIMO-4025-DB.patch


 To enable accessibility feature for data tables in the admin console, these 
 techniques should be used:
 1. Add caption tag or summary property to data table, for example
 table border=1 
 captionServer information/caption
 OR
 table border=1 summary=Server information
 2. Add scope property to column and row headers, for example
 tr
 th scope=colProperty name/th
 th scope=colProperty value/th
 /tr
 tr
 tdGeronimo Version/td
 td2.1.1/td
 /tr
 The data tables on these pages shall be improved:
 Server-Information
 Server-Java System Info
 server-Web Server
 Server-Thread Pools
 Server-JMS Server
 Server-Monitoring
 Services-Database Pools
 Services-JMS Resources
 Applications-Web App WARs
 Applications-System modules
 Applications-Application EARs
 Applications-EJB JARs
 Applications-J2EE Connectors
 Applications-App Clients
 Security-Users and Groups
 Security-Keystores
 Security-Security Realms
 Embedded DB-DB Info
 Embedded DB-DB Manager

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Duplicate clustername value sets in config-subsititions file

2009-07-08 Thread Rex Wang

well, Gianny, is a server farm not a type of cluster?

-Rex

2009/7/8 Gianny Damour gianny.dam...@optusnet.com.au

 Hi,

 It seems to me that farmName would be better than farmingClusterName as
 there is a clear distinction between a farm and a cluster.

 Thanks,
 Gianny


 On 06/07/2009, at 7:47 PM, chi runhua wrote:

  Hi all,

 I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in
 config-substitions.properties.  My understanding of them is one for WADI
 clustering and another for farming.

 Can we using different keywords to identify them? ie.  farmingClusterName
 and WADIClusterName or sth. like that.


 Jeff  C

[jira] Updated: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rex Wang updated GERONIMO-4729:
---

Attachment: (was: Geronimo-4729-b21.patch)

 Duplicate clusterName value sets in config-subsitious.properties
 

 Key: GERONIMO-4729
 URL: https://issues.apache.org/jira/browse/GERONIMO-4729
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
 Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch


 Look into *config-subsitions.properties* file, there are 2 places to set 
 clustername as following:
 {code}
 ClusterName=DEFAULT_CLUSTER
 ...
 clusterName=CLUSTER_NAME
 ...
 {code}
 which will confuse users when they are going to set up a clustering/farming 
 environment.
 Can we improve this?
 Jeff

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rex Wang updated GERONIMO-4729:
---

Attachment: Geronimo-4729-trunk.patch
Geronimo-4729-b21.patch

 Duplicate clusterName value sets in config-subsitious.properties
 

 Key: GERONIMO-4729
 URL: https://issues.apache.org/jira/browse/GERONIMO-4729
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
 Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch


 Look into *config-subsitions.properties* file, there are 2 places to set 
 clustername as following:
 {code}
 ClusterName=DEFAULT_CLUSTER
 ...
 clusterName=CLUSTER_NAME
 ...
 {code}
 which will confuse users when they are going to set up a clustering/farming 
 environment.
 Can we improve this?
 Jeff

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rex Wang updated GERONIMO-4729:
---

Attachment: (was: Geronimo-4729-trunk.patch)

 Duplicate clusterName value sets in config-subsitious.properties
 

 Key: GERONIMO-4729
 URL: https://issues.apache.org/jira/browse/GERONIMO-4729
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
 Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch


 Look into *config-subsitions.properties* file, there are 2 places to set 
 clustername as following:
 {code}
 ClusterName=DEFAULT_CLUSTER
 ...
 clusterName=CLUSTER_NAME
 ...
 {code}
 which will confuse users when they are going to set up a clustering/farming 
 environment.
 Can we improve this?
 Jeff

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

console-testsuite\advanced test error in Jetty.

2009-07-08 Thread Shawn Jiang

console-testsuite\advanced passed in

http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-1500-jetty/test.log

but failed again in

http://people.apache.org/builds/geronimo/server/binaries/trunk/20090708/logs-2100-jetty/test.log


Since there was no code change between the two build. And I don't see any
error with console-testsuite\advanced  in my local environment.

I guess there must be something wrong with the geronimo build server
environment.

-- 
Shawn

[jira] Commented: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties


[ 
https://issues.apache.org/jira/browse/GERONIMO-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729021#action_12729021
 ] 

Rex Wang commented on GERONIMO-4729:


the patches rename the 
clusterName - FarmName
ClusterName - WADIClusterName
clusterNodeName - ClusterNodeName

and the default value from
FarmName: CLUSTER_NAME - DEFAULT_FARM
WADIClusterName: DEFAULT_CLUSTER - DEFAULT_WADI_CLUSTER

-Rex


 Duplicate clusterName value sets in config-subsitious.properties
 

 Key: GERONIMO-4729
 URL: https://issues.apache.org/jira/browse/GERONIMO-4729
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: Any
Reporter: Chi Runhua
Assignee: Rex Wang
 Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch


 Look into *config-subsitions.properties* file, there are 2 places to set 
 clustername as following:
 {code}
 ClusterName=DEFAULT_CLUSTER
 ...
 clusterName=CLUSTER_NAME
 ...
 {code}
 which will confuse users when they are going to set up a clustering/farming 
 environment.
 Can we improve this?
 Jeff

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.


[ 
https://issues.apache.org/jira/browse/GERONIMO-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729029#action_12729029
 ] 

Shawn Jiang commented on GERONIMO-4731:
---

I looked into the JettyConnector.  Seems geronimo delegate the listener start 
up code to Jetty.   I also tried Jetty 7.0.0.0-m3 itself.  Got the same result. 

To track this,  I've added some comments to a JETTY ipv6 JIRA here:  
http://jira.codehaus.org/browse/JETTY-603

 Jetty build does not support IPV6 address in browser.
 -

 Key: GERONIMO-4731
 URL: https://issues.apache.org/jira/browse/GERONIMO-4731
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Jetty
Affects Versions: 2.1.5, 2.2
 Environment: geronimo-jetty-2.2-snapshot + windows + ipv6 + sun jdk 
 1.6
Reporter: Shawn Jiang

 In ipv6 enabled wondows. 
 1, Start geronimo-tomcat-2.2-snapshot instance A with:
 ServerHostname=0.0.0.0
 PortOffset=0
 2, Start geronimo-jetty-2.2-snapshot instance B with:
 ServerHostname=0.0.0.0
 PortOffset=10
 3, netstat -na
  TCP[::]:1050  [::]:0 LISTENING
  TCP[::]:1060  [::]:0 LISTENING
  TCP[::]:1099  [::]:0 LISTENING
  TCP[::]:1109  [::]:0 LISTENING
  TCP[::]:1527  [::]:0 LISTENING
  TCP[::]:1537  [::]:0 LISTENING
  TCP[::]:2001  [::]:0 LISTENING
  TCP[::]:2011  [::]:0 LISTENING
  TCP[::]:4201  [::]:0 LISTENING
  TCP[::]:4211  [::]:0 LISTENING
  TCP[::]:6882  [::]:0 LISTENING
  TCP[::]:6892  [::]:0 LISTENING
  TCP[::]:8009  [::]:0 LISTENING
  TCP[::]:8019  [::]:0 LISTENING
  TCP[::]:8080  [::]:0 LISTENING
  TCP[::]:8443  [::]:0 LISTENING
  TCP[::]:  [::]:0 LISTENING
  TCP[::]:10009 [::]:0 LISTENING
  TCP[::]:61616 [::]:0 LISTENING
  TCP[::]:61626 [::]:0 LISTENING
 4, noticed that  Jetty instance is not listening on  [::]:8090 and [::]:8453. 
   As a result, you can't access http://[ipv6-ip]:8090/console successfully 
 while you can access tomcat instance with http://[ipv6-ip]:8080/console

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.