[jira] Created: (GERONIMODEVTOOLS-683) GEP can not detect the Geronimo server version correctly
GEP can not detect the Geronimo server version correctly Key: GERONIMODEVTOOLS-683 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-683 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.7 When creating a Geronimo server v2.0.2 in GEP, GEP 2.1.7 detects the server version incorrectly (as 2.1.7), which blocking the server creation wizard. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-683) GEP can not detect the Geronimo server version correctly
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966013#action_12966013 ] Han Hong Fang commented on GERONIMODEVTOOLS-683: Fixed at revision: 1041303. I keep the JIRA status as open until I check if the problem exists in 22 branch and trunk. GEP can not detect the Geronimo server version correctly Key: GERONIMODEVTOOLS-683 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-683 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.7 When creating a Geronimo server v2.0.2 in GEP, GEP 2.1.7 detects the server version incorrectly (as 2.1.7), which blocking the server creation wizard. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5723) derby system-database user authentication failure when shutdown server using sun jdk 1.6.0
[ https://issues.apache.org/jira/browse/GERONIMO-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMO-5723: -- The errors exits when using IBM JDK 2010-12-02 15:36:58,399 INFO [JvmVendor] IBM JVM 1.6.0 2010-12-02 15:36:58,399 INFO [Log4jService] JVM in use = IBM JVM 1.6.0 2010-12-02 15:36:58,399 INFO [Log4jService] Java Information: 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.runtime.name] = Java(TM) SE Runtime Environment 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.runtime.version] = jvmwi3260sr8ifx-20100609_59383 2010-12-02 15:36:58,399 INFO [Log4jService] System property [os.name] = Windows Server 2003 2010-12-02 15:36:58,399 INFO [Log4jService] System property [os.version] = 5.2 build 3790 Service Pack 2 2010-12-02 15:36:58,399 INFO [Log4jService] System property [sun.os.patch.level] = null 2010-12-02 15:36:58,399 INFO [Log4jService] System property [os.arch] = x86 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.class.version] = 50.0 2010-12-02 15:36:58,399 INFO [Log4jService] System property [locale] = zh_CN 2010-12-02 15:36:58,399 INFO [Log4jService] System property [unicode.encoding]= UnicodeLittle 2010-12-02 15:36:58,399 INFO [Log4jService] System property [file.encoding] = GB18030 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.vm.name] = IBM J9 VM 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.vm.vendor] = IBM Corporation 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.vm.version] = 2.4 2010-12-02 15:36:58,399 INFO [Log4jService] System property [java.vm.info] = JRE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260sr8ifx-20100609_59383 (JIT enabled, AOT enabled) J9VM - 20100609_059383 JIT - r9_20100401_15339ifx2 GC - 20100308_AA derby system-database user authentication failure when shutdown server using sun jdk 1.6.0 -- Key: GERONIMO-5723 URL: https://issues.apache.org/jira/browse/GERONIMO-5723 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 2.1.7 Environment: windows server 2003 x86-32 R2 sun jdk 1.6.0 javaTM SE environment(build pwi3260sr8fp1-20100624_01(SR8_FP1)) Reporter: Tina Li Priority: Minor Attachments: geronimo.log 1.Using sun jdk 1.6.0 and set java_home 2.Use geronimo 2.1.7,startup geronimo server 3.shutdown geronimo server.Then error shows: 2010-12-02 10:10:44,819 WARN [DerbyUserAuthenticator] User authentication failure (userName userPassword databaseName): dbadmin manager null 2010-12-02 10:10:44,850 ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.configs/system-database/2.1.7/car?J2EEApplication=null,ResourceAdapterModule=org.apache.geronimo.configs/system-database/2.1.7/car,j2eeType=GBean,name=DerbyNetwork java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication.. at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(Unknown Source) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(Unknown Source) at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(Unknown Source) at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(Unknown Source) at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Unknown Source) at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(Unknown Source) at org.apache.derby.drda.NetworkServerControl.shutdown(Unknown Source) at org.apache.geronimo.derby.DerbyNetworkGBean.doStop(DerbyNetworkGBean.java:98) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1161) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:339) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:188) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:336)
[jira] Updated: (GERONIMO-5724) Problem with running Geronimo server as a Windows service using Java Service Wrapper
[ https://issues.apache.org/jira/browse/GERONIMO-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maojia updated GERONIMO-5724: - Attachment: wrapper.jar wrapper.dll wrapper.exe Problem with running Geronimo server as a Windows service using Java Service Wrapper Key: GERONIMO-5724 URL: https://issues.apache.org/jira/browse/GERONIMO-5724 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.2 Environment: Sun JDK 1.6.0_21, Windows XP, geronimo-tomcat6-javaee5-2.2 Reporter: maojia Priority: Minor Attachments: g_service.bat, Install_Geronimo_NT.bat, Uninstall_Geronimo_NT.bat, wrapper.conf, wrapper.dll, wrapper.exe, wrapper.jar I tried to run Geronimo server as a Windows service using Java Service Wrapper through the following steps: 1. I copied wrapper.exe, g_service.bat, Install_Geronimo.bat and Uninstall_Geronimo.bat to GERONIMO_HOME/bin. 2. I copied wrapper.jar and wrapper.dll to GERONIMO_HOME/lib. 3. I copied wrapper.conf to GERONIMO_HOME/var/config. (The files were modified as in the attachment.) 4.I ran the command: geronimo_home/bin/g_service.bat The following error message was reported: .. Loading org.apache.ger...2010-12-02 15:10:03,956 ERROR [AbstractEncryption] Unable to decrypt INFO | jvm 1| 2010/12/02 15:10:04 | java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES .. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Incorrect schema docs on Geronimo website
Hi, looked like that the schema docs are not correct for Geronimo 2.2 on the Geronimo website, because G2.2 schema docs[1] still link to G2.1 schema pages under a /schema-2.1/docs directory, see [2]. And the oXygen XML Editor do the real-time transforming to the .xsd files and publish the result files to Geronimo Website. [1]. http://geronimo.apache.org/apache-geronimo-v22-xml-schemas.html [2]. http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html IIUC, we might need to create a folder for each major release such as 2.*, 3.*, and then promote corresponding schema files into the folder, so that they could be converted and published by the oXygen tool successfully. Does anyone know where and how to create the folder? Jeff C
Re: Incorrect schema docs on Geronimo website
Just take a look at the source tree, [1] might be the place to add. [1]https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/ On Thu, Dec 2, 2010 at 5:35 PM, chi runhua chirun...@gmail.com wrote: Hi, looked like that the schema docs are not correct for Geronimo 2.2 on the Geronimo website, because G2.2 schema docs[1] still link to G2.1 schema pages under a /schema-2.1/docs directory, see [2]. And the oXygen XML Editor do the real-time transforming to the .xsd files and publish the result files to Geronimo Website. [1]. http://geronimo.apache.org/apache-geronimo-v22-xml-schemas.html [2]. http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html IIUC, we might need to create a folder for each major release such as 2.*, 3.*, and then promote corresponding schema files into the folder, so that they could be converted and published by the oXygen tool successfully. Does anyone know where and how to create the folder? Jeff C -- Shawn
[jira] Updated: (GERONIMO-5666) Add test cases for Restful Web Service new features into the testsuite.
[ https://issues.apache.org/jira/browse/GERONIMO-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang Guang Zhe updated GERONIMO-5666: - Attachment: geronimo-5666.patch Test case for Restful Web Services. Add test cases for Restful Web Service new features into the testsuite. --- Key: GERONIMO-5666 URL: https://issues.apache.org/jira/browse/GERONIMO-5666 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: testsuite Affects Versions: 3.0 Reporter: Wang Guang Zhe Fix For: 3.0 Attachments: geronimo-5666.patch Java API for RESTful Web Services (JAX-RS) 1.1, which is JSR-311,is a new part in Java EE 6.This testsuite includes its basic functions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-679) TestSuite not working on branch 2.1.7
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-679: - Attachment: gep2.1.7_automation_testsuit_final.patch The patch has covered the previous four test cases. TestSuite not working on branch 2.1.7 - Key: GERONIMODEVTOOLS-679 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Attachments: gep2.1.7_automation_testsuit_final.patch needs various version update such as gep version from 2.1.6 to 2.1.7, ans supported geronimo version etc. -- 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: 1041301
Geronimo Revision: 1041301 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 38 minutes 11 seconds [INFO] Finished at: Thu Dec 02 03:42:12 EST 2010 [INFO] Final Memory: 495M/1005M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-0300-tomcat/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.462 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.554 sec FAILURE! -- Running TestSuite Tests run: 14, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 32.096 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-0300-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.497 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.037 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.548 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/samples-0300.log Build status: FAILED
[jira] Commented: (GERONIMODEVTOOLS-679) TestSuite not working on branch 2.1.7
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966107#action_12966107 ] Han Hong Fang commented on GERONIMODEVTOOLS-679: Build successfully with the patch. Committed at revision: 1041362. Thank you YI Xiao for the patch. TestSuite not working on branch 2.1.7 - Key: GERONIMODEVTOOLS-679 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Attachments: gep2.1.7_automation_testsuit_final.patch needs various version update such as gep version from 2.1.6 to 2.1.7, ans supported geronimo version etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-684) Simplify the steps in Tutorial5MinuteTest of GEP test suites to reduce the dependency on eclipse UI
Simplify the steps in Tutorial5MinuteTest of GEP test suites to reduce the dependency on eclipse UI --- Key: GERONIMODEVTOOLS-684 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-684 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.1, 2.1.7 Reporter: Han Hong Fang Assignee: Delos Dai The current Tutorial5MinuteTest of GEP test suite creates EAR/EJB/WAR projects steps by steps. It will be more simplified if we created these projects outsides the test suite, and then import them in test suite for GEP function verification purpose. This would reduce the dependency of eclipse UI, which reduces the code change when eclipse upgrades. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-679) TestSuite not working on branch 2.1.7
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang resolved GERONIMODEVTOOLS-679. Resolution: Fixed Fix Version/s: 2.1.7 I have JIRA GERONIMODEVTOOLS-684 (Simplify the steps in Tutorial5MinuteTest of GEP test suites to reduce the dependency on eclipse UI) created for Tutorial5MinutsTest, and change the status of this JIRA as resolved. TestSuite not working on branch 2.1.7 - Key: GERONIMODEVTOOLS-679 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.7 Attachments: gep2.1.7_automation_testsuit_final.patch needs various version update such as gep version from 2.1.6 to 2.1.7, ans supported geronimo version etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r1041298 [1/2] - in /geronimo/server/trunk/testsuite/javaee6-testsuite: ./ jpa2.0-test/ jpa2.0-test/src/ jpa2.0-test/src/main/ jpa2.0-test/src/main/java/ jpa2.0-test/src/main/java/org/
Please ensure the code you are checking in is following the Geronimo and Java coding standards. Specifically, 4 spaces (no tabs) in Java _and_ XML files. Also, some Java classes/files have wrong capitalization. Jarek On Thu, Dec 2, 2010 at 2:53 AM, xiam...@apache.org wrote: Author: xiaming Date: Thu Dec 2 07:53:09 2010 New Revision: 1041298 URL: http://svn.apache.org/viewvc?rev=1041298view=rev Log: GERONIMO-5720 some tests for jpa 2.0 new feature, provided by LiWenQin Added: geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/pom.xml (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/CommentAdd.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/CourseAdd.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/CourseDelete.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/CourseSelect.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/CourseUnselect.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/StudentAdd.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/StudentDelete.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/listQuery.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/nullIfJPQL.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/queryCourseByName.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewAllComments.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewAllCourse.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewAllStudents.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewCourses.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewSelect_CourseRelation.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/action/viewStudents.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/bean/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/bean/Facade.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/entities/ geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/entities/Address.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/entities/BasicInfo.java (with props) geronimo/server/trunk/testsuite/javaee6-testsuite/jpa2.0-test/src/main/java/org/apache/geronimo/javaee6/jpa20/entities/Course.java (with props)
[jira] Assigned: (GERONIMO-5396) java.util.logging resources doesn't get picked up
[
https://issues.apache.org/jira/browse/GERONIMO-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned GERONIMO-5396:
-
Assignee: Jarek Gawor
In revision 1041446 I committed a temporary work-around for this problem.
However, the problem is really in JdkHandler.java in pax-logging-service
bundle. The problem is fixed in the latest pax logging code and should be part
of 1.5.4 release. Once 1.5.4 is out the work-around can be removed. I'll keep
this bug open until then.
java.util.logging resources doesn't get picked up
-
Key: GERONIMO-5396
URL: https://issues.apache.org/jira/browse/GERONIMO-5396
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Logging
Affects Versions: 3.0-M1
Reporter: Mark Struberg
Assignee: Jarek Gawor
In OpenWebBeans we use the i18n resource capabilities of
java.util.logging.Logger
In the code:
{noformat}
Logger logger = Logger#getLogger(String name, String resourceBundleName);
logger.info(INFO_0004, param),
{noformat}
In the Message resources:
{noformat}
INFO_0004=Adding OpenWebBeansPlugin \: [{0}]
{noformat}
Where {0} gets filled with the value of 'param'.
In geronimo I only see: [BeansDeployer] INFO_0004
, so the jul to slf4j bridge doesn't handle the message bundle.
Also if I add the String myself and call
{noformat}
logger.info(message with param {0}, rabbit);
{noformat}
I still get no parameter filling, so the resulting text in the logfile is
message with param {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: 1041384
Geronimo Revision: 1041384 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 44 minutes 13 seconds [INFO] Finished at: Thu Dec 02 10:04:51 EST 2010 [INFO] Final Memory: 483M/995M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-0900-tomcat/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.864 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.568 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-0900-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.527 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.857 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.502 sec FAILURE! -- Running TestSuite Tests run: 14, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.392 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/samples-0900.log Build status: FAILED
[jira] Resolved: (GERONIMO-5433) improve geronimo openwebbeans plugin
[ https://issues.apache.org/jira/browse/GERONIMO-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5433. --- Resolution: Invalid Resolving as this is out of date and we have a much better integration with OWB now. improve geronimo openwebbeans plugin Key: GERONIMO-5433 URL: https://issues.apache.org/jira/browse/GERONIMO-5433 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: OpenWebBeans Affects Versions: 3.0-M1 Reporter: Mark Struberg Fix For: 3.0 Attachments: GERONIMO-5433.patch The current OpenWebBeans integration does not compile + there is a new OpenWebBeans-1.0.0-alpha-1 release currently in the VOTE. I'd like to provide a few patches to test the integration with geronimo-3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5182) Fix compile errors caused by Jetty 8.0.0.M0 release
[ https://issues.apache.org/jira/browse/GERONIMO-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5182. --- Resolution: Invalid This is out of date now as we are using Jetty 8.0.0.M2. Fix compile errors caused by Jetty 8.0.0.M0 release --- Key: GERONIMO-5182 URL: https://issues.apache.org/jira/browse/GERONIMO-5182 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 3.0 Reporter: Kevan Miller Assignee: Kevan Miller Fix For: 3.0 There are multiple updates in the latest Jetty 8.0.0.M0 release which are breaking the build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5182) Fix compile errors caused by Jetty 8.0.0.M0 release
[ https://issues.apache.org/jira/browse/GERONIMO-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-5182. -- Fix compile errors caused by Jetty 8.0.0.M0 release --- Key: GERONIMO-5182 URL: https://issues.apache.org/jira/browse/GERONIMO-5182 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Jetty Affects Versions: 3.0 Reporter: Kevan Miller Assignee: Kevan Miller Fix For: 3.0 There are multiple updates in the latest Jetty 8.0.0.M0 release which are breaking the build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 1040221
Geronimo Revision: 1040221 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101129/build-1400.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101129 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 36 minutes 42 seconds [INFO] Finished at: Mon Nov 29 14:43:25 EST 2010 [INFO] Final Memory: 308M/969M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101129/logs-1400-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 23, Errors: 0, Skipped: 0, Time elapsed: 196.997 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 82.593 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.378 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101129/logs-1400-jetty/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 26, Errors: 0, Skipped: 0, Time elapsed: 202.612 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 67.186 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.788 sec FAILURE! Samples: branches/2.2 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.2/20101129/samples-1400.log Build status: FAILED
[BUILD] trunk: Failed for Revision: 1041567
Geronimo Revision: 1041567 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 35 minutes 43 seconds [INFO] Finished at: Thu Dec 02 15:41:53 EST 2010 [INFO] Final Memory: 481M/996M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-1500-tomcat/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.201 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.452 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/logs-1500-jetty/ Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.531 sec FAILURE! -- Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.517 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.735 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/samples-1500.log Build status: FAILED
[jira] Commented: (GERONIMO-5680) Find a way to slove the wired bundle cache
[ https://issues.apache.org/jira/browse/GERONIMO-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966334#action_12966334 ] David Jencks commented on GERONIMO-5680: This looks to me like a reasonable way to proceed. The only part I don't like is using the old class filters hidden classes. I was hoping to remove that bit of the schema. I wonder if we should look into using a maven-bundle-plugin compatible configuration for plugin import-export details? Then you can use a !foo.bar.* to prevent importing a particular package. If you want to commit this work we can discuss configuration options later. Find a way to slove the wired bundle cache -- Key: GERONIMO-5680 URL: https://issues.apache.org/jira/browse/GERONIMO-5680 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Attachments: GERONIMO-5680.patch http://www.apacheserver.net/wired-bundle-cache-problem-in-the-BundleClassLoader-at1043973.htm The root cause is the dynamic import * is used, think that we should have a way to replace 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-5615) Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir
[ https://issues.apache.org/jira/browse/GERONIMO-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-5615: --- Attachment: GERONIMO-5615-2.patch The attached patch creates a URI from the shortened URL file path which I believe then gives the correct File using the new File(uri) constructor. Does this work for you on windows? If not can you figure out how to modify the test to show the problem? Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir - Key: GERONIMO-5615 URL: https://issues.apache.org/jira/browse/GERONIMO-5615 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0 Environment: OS: Windows XP SP3 Reporter: Chris Zhang Assignee: viola.lu Priority: Minor Fix For: 3.0 Attachments: G5615.patch, GERONIMO-5615-2.patch The steps to recur are: (1) Create a directory called myDir under C:\Documents and Settings (2) Put the geronimo server directory under C:\Documents and Settings\myDir. Now the server root directory is C:\Documents and Settings\myDir\g. (3) Start the server and login to the admin console. (4) Deploy a war file and some exceptions thrown. The exception information is: 2010-09-20 16:33:48,329 ERROR [DeploymentPortlet] The application was not deployed. Unable to create configuration for deployment: dependencies: null org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment: dependencies: null at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208) at org.apache.geronimo.deployment.DeploymentContext.initializeConfiguration(DeploymentContext.java:188) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:615) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) 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:736) Caused by: org.osgi.framework.BundleException: An error occurred trying to read the bundle at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:922) at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:838) at java.security.AccessController.doPrivileged(AccessController.java:251) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:889) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:833) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:167) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java) at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:200) ... 15 more Caused by: java.io.FileNotFoundException: C:\Documents%20and%20Settings\myDir\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-fileutils3448848740305009830.tmpfile at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.connect(ReferenceURLConnection.java:46) at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.getInputStream(ReferenceURLConnection.java:61) at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:56) ... 23 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
How to report staging server problem ?
I'm trying to perform a 2.2.1 release. It drives me nuts when I want to close the open staging repo from [1]. It always fails and returns without any hints. After two complete release process attempts, it still does not work. Does anyone know how to report this problem ? https://repository.apache.org/index.html#stagingRepositories[1] -- Shawn
Re: How to report staging server problem ?
I find Brian Fox (brianf, I think) on the maven irc channel and ask him for help. However I don't think he's there now. Asking on maven IRC might still work. #ma...@irc.codehaus.org (hope that's the right syntax) david jencks On Dec 2, 2010, at 4:15 PM, Shawn Jiang wrote: I'm trying to perform a 2.2.1 release. It drives me nuts when I want to close the open staging repo from [1]. It always fails and returns without any hints. After two complete release process attempts, it still does not work. Does anyone know how to report this problem ? https://repository.apache.org/index.html#stagingRepositories[1] -- Shawn
[jira] Commented: (GERONIMODEVTOOLS-679) TestSuite not working on branch 2.1.7
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966363#action_12966363 ] Yi Xiao commented on GERONIMODEVTOOLS-679: -- Ok, I will watch and trace the JIRA GERONIMODEVTOOLS-684 TestSuite not working on branch 2.1.7 - Key: GERONIMODEVTOOLS-679 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-679 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.7 Attachments: gep2.1.7_automation_testsuit_final.patch needs various version update such as gep version from 2.1.6 to 2.1.7, ans supported geronimo version etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Incorrect schema docs on Geronimo website
I went ahead to add the schema files for 2.2, might need to wait the async work finishes. 2010/12/2 Shawn Jiang genspr...@gmail.com Just take a look at the source tree, [1] might be the place to add. [1]https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/ On Thu, Dec 2, 2010 at 5:35 PM, chi runhua chirun...@gmail.com wrote: Hi, looked like that the schema docs are not correct for Geronimo 2.2 on the Geronimo website, because G2.2 schema docs[1] still link to G2.1 schema pages under a /schema-2.1/docs directory, see [2]. And the oXygen XML Editor do the real-time transforming to the .xsd files and publish the result files to Geronimo Website. [1]. http://geronimo.apache.org/apache-geronimo-v22-xml-schemas.html [2]. http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html IIUC, we might need to create a folder for each major release such as 2.*, 3.*, and then promote corresponding schema files into the folder, so that they could be converted and published by the oXygen tool successfully. Does anyone know where and how to create the folder? Jeff C -- Shawn -- Ivan
Re: Incorrect schema docs on Geronimo website
Thanks Shawn. That's really helpful. I thought those .xsd.html files under /schema-2.1/docs/ directory were generated automatically, actually they're not. Looks like Hernan or some other committers did the conversion using oXygen XML editor and then committed those files. I also noticed that the copyright information on the bottom of each page is not correct, which should be copyright(C)2005-2010. Another thing I didn't figure out yet is that how those .xsd.html files were generated using the same template as other pages on Geronimo homesite, because those schema files are not from Confluence wiki thus the .html files can't be generated using the auto-export plugin. Does this means we have to update each page manually? If anyone could shed a light on me, that would be great. Another thought is we don't generate .html pages for the schema files any more, we only provide the raw data for the users just like we did for 2.0 version. see https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/schemas-1.1/ Any thoughts? Jeff C On Thu, Dec 2, 2010 at 5:38 PM, Shawn Jiang genspr...@gmail.com wrote: Just take a look at the source tree, [1] might be the place to add. [1]https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/ On Thu, Dec 2, 2010 at 5:35 PM, chi runhua chirun...@gmail.com wrote: Hi, looked like that the schema docs are not correct for Geronimo 2.2 on the Geronimo website, because G2.2 schema docs[1] still link to G2.1 schema pages under a /schema-2.1/docs directory, see [2]. And the oXygen XML Editor do the real-time transforming to the .xsd files and publish the result files to Geronimo Website. [1]. http://geronimo.apache.org/apache-geronimo-v22-xml-schemas.html [2]. http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html IIUC, we might need to create a folder for each major release such as 2.*, 3.*, and then promote corresponding schema files into the folder, so that they could be converted and published by the oXygen tool successfully. Does anyone know where and how to create the folder? Jeff C -- Shawn
[jira] Assigned: (GERONIMO-5666) Add test cases for Restful Web Service new features into the testsuite.
[ https://issues.apache.org/jira/browse/GERONIMO-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-5666: - Assignee: Forrest Xia Add test cases for Restful Web Service new features into the testsuite. --- Key: GERONIMO-5666 URL: https://issues.apache.org/jira/browse/GERONIMO-5666 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: testsuite Affects Versions: 3.0 Reporter: Wang Guang Zhe Assignee: Forrest Xia Fix For: 3.0 Attachments: geronimo-5666.patch Java API for RESTful Web Services (JAX-RS) 1.1, which is JSR-311,is a new part in Java EE 6.This testsuite includes its basic functions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5666) Add test cases for Restful Web Service new features into the testsuite.
[ https://issues.apache.org/jira/browse/GERONIMO-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5666. - Resolution: Fixed I made a little bit change, commit to tr...@1041662. Thank you Wang Guang Zhe for providing this test. Add test cases for Restful Web Service new features into the testsuite. --- Key: GERONIMO-5666 URL: https://issues.apache.org/jira/browse/GERONIMO-5666 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: testsuite Affects Versions: 3.0 Reporter: Wang Guang Zhe Assignee: Forrest Xia Fix For: 3.0 Attachments: geronimo-5666.patch Java API for RESTful Web Services (JAX-RS) 1.1, which is JSR-311,is a new part in Java EE 6.This testsuite includes its basic functions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: How to report staging server problem ?
Thanks David, Just tried to ping them from IRC but seems no one is online now. Rex agreed to try the release perform action in his environment. Hope it's only my environment problem. On Fri, Dec 3, 2010 at 8:22 AM, David Jencks david_jen...@yahoo.com wrote: I find Brian Fox (brianf, I think) on the maven irc channel and ask him for help. However I don't think he's there now. Asking on maven IRC might still work. #ma...@irc.codehaus.org (hope that's the right syntax) david jencks On Dec 2, 2010, at 4:15 PM, Shawn Jiang wrote: I'm trying to perform a 2.2.1 release. It drives me nuts when I want to close the open staging repo from [1]. It always fails and returns without any hints. After two complete release process attempts, it still does not work. Does anyone know how to report this problem ? https://repository.apache.org/index.html#stagingRepositories[1] -- Shawn -- Shawn
[BUILD] trunk: Failed for Revision: 1041673
Geronimo Revision: 1041673 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101202/unit-test-reports
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 8 source files to
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[25,33]
cannot find symbol
symbol : class WebBeansContext
location: package org.apache.webbeans.config
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[36,37]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[47,49]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[47,18]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[53,37]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[63,12]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/SharedOwbContext.java:[23,33]
cannot find symbol
symbol : class WebBeansContext
location: package org.apache.webbeans.config
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/SharedOwbContext.java:[30,4]
cannot find symbol
symbol : class WebBeansContext
location: interface org.apache.geronimo.openwebbeans.SharedOwbContext
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansWebInitializer.java:[25,33]
cannot find symbol
symbol : class WebBeansContext
location: package org.apache.webbeans.config
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/OpenWebBeansWebInitializer.java:[43,38]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.OpenWebBeansWebInitializer
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[36,81]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[48,14]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[59,8]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
/home/geronimo/geronimo/trunk/plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/GeronimoSingletonService.java:[64,8]
cannot find symbol
symbol : class WebBeansContext
location: class org.apache.geronimo.openwebbeans.GeronimoSingletonService
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
[jira] Commented: (DAYTRADER-87) DayTrader 2.2.x : Can not compile for Jboss5 / doc is not up to date (file README.jboss5)
[
https://issues.apache.org/jira/browse/DAYTRADER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966401#action_12966401
]
viola.lu commented on DAYTRADER-87:
---
Hi, Yannick:
You can find the daytrader ear under
$daytrader_source\assemblies\javaee\daytrader-ear\target. Can you try that one
on JBOSS. THanks in advance!
DayTrader 2.2.x : Can not compile for Jboss5 / doc is not up to date (file
README.jboss5)
-
Key: DAYTRADER-87
URL: https://issues.apache.org/jira/browse/DAYTRADER-87
Project: DayTrader
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2
Environment: * JDK 1.6_021
* Mandriva Linux 2010.1
* Maven 2.2.1
Reporter: Yannick LE NY
Fix For: 2.2.1
Attachments: daytrader-2.2-compile.log
I try to compile Daytrader 2.2 for Jboss 5 with the documentation available
at
http://svn.apache.org/viewvc/geronimo/daytrader/branches/2.2/README.jboss5?revision=1032571view=markupsortby=revsortdir=down
But this documentation is true/good for Daytrader 2.1.3 but not for daytrader
2.2.
1)
Part (replace ejb folder by ejb3 folder)
963. Rename these files manually:
97#
$DAYTRADER_SRC_HOME/modules/ejb/src/main/resources/META-INF/persistence.xml
98--
$DAYTRADER_SRC_HOME/modules/ejb/src/main/resources/META-INF/persistence.xml.bak
maybe should replace by
963. Rename these files manually:
97#
$DAYTRADER_SRC_HOME/modules/ejb3/src/main/resources/META-INF/persistence.xml
98--
$DAYTRADER_SRC_HOME/modules/ejb3/src/main/resources/META-INF/persistence.xml.bak
2)
Now, the part for OpenJPA PCEnhancer Ant task is not available in
$DAYTRADER_SRC_HOME/modules/ejb/pom.xml
114 5. Modify $DAYTRADER_SRC_HOME/modules/ejb/pom.xml to comment out
OpenJPA PCEnhancer Ant task:
115 !--plugin
116 artifactIdmaven-antrun-plugin/artifactId
117 executions
118 execution
119 phasecompile/phase
120 configuration
121 tasks
122 path id=enhance.path.ref
123 fileset dir=${project.build.outputDirectory}
124 include name=**/*.class/
125 /fileset
126 /path
127 pathconvert property=enhance.files
128 refid=enhance.path.ref
129 pathsep= /
130 java classname=org.apache.openjpa.enhance.PCEnhancer
131 arg line=-p persistence.xml/
132 arg line=${enhance.files}/
133 classpath
134 path refid=maven.dependency.classpath/
135 path refid=maven.compile.classpath/
136 /classpath
137 /java
138 /tasks
139 /configuration
140 goals
141 goalrun/goal
142 /goals
143 /execution
144 /executions
145 /plugin--
3) No ear file created
174 8. Finally, copy the
$DAYTRADER_SRC_HOME/modules/ear/target/daytrader-ear-2.2-SNAPSHOT.ear
175 to your $JBOSS_INST_HOME/server/standard/deploy/ directory.
After compiling with success, I have nothing in
$DAYTRADER_SRC_HOME/modules/ear/target/daytrader-ear-2.2-SNAPSHOT.ear.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 1041655
Geronimo Revision: 1041655 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101202/build-2000.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101202 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 6 seconds [INFO] Finished at: Thu Dec 02 20:39:33 EST 2010 [INFO] Final Memory: 315M/902M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101202/logs-2000-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 30, Errors: 0, Skipped: 0, Time elapsed: 185.487 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 65.444 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 68.567 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101202/logs-2000-jetty/ [INFO] Running TestSuite [INFO] Tests run: 116, Failures: 3, Errors: 0, Skipped: 113, Time elapsed: 16.445 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 91.064 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.722 sec FAILURE! Samples: branches/2.2 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.2/20101202/samples-2000.log Build status: OK
[jira] Updated: (GERONIMODEVTOOLS-685) Can not build GEP2.2.1 testsuit successfully
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-685: - Attachment: gep2.2.1_testsuit_verdep.patch Rectify the versions and exclude some unnessary maven dependencies Can not build GEP2.2.1 testsuit successfully Key: GERONIMODEVTOOLS-685 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-685 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.1 Environment: windows Xp sp3; JDK1.5.0_22 Reporter: Yi Xiao Assignee: Delos Dai Attachments: gep2.2.1_testsuit_verdep.patch Can not build GEP2.2.1 testsuit successfully for the incompatible versions and unnecessary dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-685) Can not build GEP2.2.1 testsuit successfully
Can not build GEP2.2.1 testsuit successfully Key: GERONIMODEVTOOLS-685 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-685 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.1 Environment: windows Xp sp3; JDK1.5.0_22 Reporter: Yi Xiao Assignee: Delos Dai Attachments: gep2.2.1_testsuit_verdep.patch Can not build GEP2.2.1 testsuit successfully for the incompatible versions and unnecessary dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-685) Can not build GEP2.2.1 testsuit successfully
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-685: Assignee: Yi Xiao (was: Delos Dai) Can not build GEP2.2.1 testsuit successfully Key: GERONIMODEVTOOLS-685 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-685 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.1 Environment: windows Xp sp3; JDK1.5.0_22 Reporter: Yi Xiao Assignee: Yi Xiao Attachments: gep2.2.1_testsuit_verdep.patch Can not build GEP2.2.1 testsuit successfully for the incompatible versions and unnecessary dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
More access wanted
Hi Kevan I want these privileges when doing daily work: 1. Right of Geronimo confluence administration, without this, I cannot sync confluence blog post to geronimo web site timely. 2. Right of Daytrader JIRA project administration, without this, I cannot add new versions for daytrader subproject. 3. Right of editing geronimo-contributor jira group, without this, I cannot add new contributor as the standard way. Thank you! Forrest
[jira] Commented: (GERONIMO-5020) JACC manager gbean already present deploymentException stop car-maven-plugin to generate valid geronimo plugin car
[ https://issues.apache.org/jira/browse/GERONIMO-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966441#action_12966441 ] David Jencks commented on GERONIMO-5020: I haven't looked at the plan you are trying to use to build the plugin with, however if you are using the car-maven-plugin you want to let it build most of the environment element for you from the maven project id (which turns into the geronimo module id) and the maven dependencies (modified if necessary with import type in the c-m-p configuration in the pom) (which produce the dependencies in the environment element). You ought to be able to specify class filtering elements in the plan and have them preserved. What problem are you seeing? JACC manager gbean already present deploymentException stop car-maven-plugin to generate valid geronimo plugin car Key: GERONIMO-5020 URL: https://issues.apache.org/jira/browse/GERONIMO-5020 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 2.2 Environment: ubuntu 8.04 IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr7-20091214_49398 (JIT enabled, AOT enabled) Reporter: Forrest Xia Assignee: Ivan Fix For: 2.2.1 If the deployment plan includes security configs, there will be a known issue: [ERROR] GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean already present org.apache.geronimo.common.DeploymentException: JACC manager gbean already present org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224) this exception will stop car-maven-plugin to generate configuration data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5355) ClassCastException while starting snapshot (Stat Query) in G 215 Monitoring portlet through java client
[
https://issues.apache.org/jira/browse/GERONIMO-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966444#action_12966444
]
Vamsavardhana Reddy commented on GERONIMO-5355:
---
The exception seems to be due to a
org.tranql.connector.jdbc.TranqlDataSource$SelfReference object getting bound
to the JNDI instead of org.tranql.connector.jdbc.TranqlDataSource. The
TranqlDataSource object is to be obtained by calling getContent() method on the
SelfReference object.
ClassCastException while starting snapshot (Stat Query) in G 215 Monitoring
portlet through java client
---
Key: GERONIMO-5355
URL: https://issues.apache.org/jira/browse/GERONIMO-5355
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: monitoring
Affects Versions: 2.1.5
Reporter: Amit Puri
In a java client where MBeanServerConnection is created and invoke
startSnapshot method in Monitoring Portlet of G 215, Stat Query snapshot
started but we can also find ClassCastException.
...
ERROR [MasterRemoteControlJMX]
org.tranql.connector.jdbc.TranqlDataSource$SelfReference incompatible with
javax.sql.DataSource
java.lang.ClassCastException:
org.tranql.connector.jdbc.TranqlDataSource$SelfReference incompatible with
javax.sql.DataSource
at
org.apache.geronimo.monitoring.MasterRemoteControlJMX.init(MasterRemoteControlJMX.java:110)
at
org.apache.geronimo.monitoring.snapshot.SnapshotProcessor.getMRC(SnapshotProcessor.java:148)
at
org.apache.geronimo.monitoring.snapshot.SnapshotProcessor.takeSnapshot(SnapshotProcessor.java:59)
at
org.apache.geronimo.monitoring.snapshot.SnapshotThread.run(SnapshotThread.java:103)
...
In G 214, this exception does not come while using same java client.
These steps are followed in java client:
1.Creating MBeanServerConnection object
...
MBeanServerConnection mbServerConn;
JMXServiceURL serviceURL = new
JMXServiceURL(service:jmx:rmi:///jndi/rmi://localhost/JMXConnector);
HashtableString, Object env = new HashtableString, Object();
String[] credentials = new String[2];
credentials[0] = system;
credentials[1] = manager;
env.put(JMXConnector.CREDENTIALS, credentials);
JMXConnector connector = JMXConnectorFactory.connect(serviceURL, env);
mbServerConn = connector.getMBeanServerConnection();
..
2. Retrieving the mbean name to the agent-car-jmx plugin
..
if(PATH == null) {
SetObjectName mbeanNames = mbServerConn.queryNames(new
ObjectName(*:name=MasterRemoteControlJMX,*), null);
for(IteratorObjectName it = mbeanNames.iterator(); it.hasNext(); ) {
String mbeanName = ((ObjectName)it.next()).getCanonicalName();
if(mbeanName.contains(agent-car-jmx)
mbeanName.contains(MasterRemoteControlJMX) mbeanName.contains(GBean)) {
PATH = mbeanName;
break;
}}
if(PATH == null) {
throw new Exception([ERROR] Required mbean not found: agent-car-jmx);
}}
..
Here I am getting mbean name as
geronimo:J2EEServer=geronimo,ServiceModule=org.apache.geronimo.plugins.monitoring/agent-car-jmx/2.1.5/car,j2eeType=GBean,name=MasterRemoteControlJMX
3. Invoking startSnapshot
..
long time = 30;
int days = 2;
mbServerConn.invoke(new ObjectName(PATH),startSnapshot, new Object[] {
time, days }, new String[] { java.lang.Long, java.lang.Integer });
..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
