[jira] Commented: (AMQ-826) LDAP based authorization support
[ https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37156 ] Nikola Goran Cutura commented on AMQ-826: - This patch needs improvement. It does not handle composite destinations and broker won't start if LDAPAuthorizationMap is configured as there is (at least) one composite destination during startup (topic://ActiveMQ.Advisory.TempTopic,topic://ActiveMQ.Advisory.TempTopic). I am on this now. LDAP based authorization support Key: AMQ-826 URL: https://issues.apache.org/activemq/browse/AMQ-826 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Nikola Goran Cutura Attachments: LdapAuth.zip Patch kindly added by ngcutura - discussion thread... http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ.DLQ
Hi, Messages are automatically sent to DLQ when they hit their redelivery maximum. I don't believe expired messages are sent to DLQs though. Regards, Jonas Christopher_Ong wrote: Is it when the message expire then it will auto been sent to DLQ? Or I have to manually send it to the DLQ? jlim wrote: Oh btw, here is an example on using them : https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/RedeliveryPolicyTest.java Jonas Lim wrote: hi, It's the destination name for the dead letter queue. You can have a consumer listen to this queue and should be able to get the message(if any) off the DLQ . Regards, Jonas Christopher_Ong wrote: May I know what is ActiveMQ.DLQ?
Re: ActiveMQ.DLQ
Sorry, what do you meant you don't believe expired messages are sent to DLQs though? Does it mean that u oso facing the problem to automatically send the dead msg to DLQ? jlim wrote: Hi, Messages are automatically sent to DLQ when they hit their redelivery maximum. I don't believe expired messages are sent to DLQs though. Regards, Jonas Christopher_Ong wrote: Is it when the message expire then it will auto been sent to DLQ? Or I have to manually send it to the DLQ? jlim wrote: Oh btw, here is an example on using them : https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/RedeliveryPolicyTest.java Jonas Lim wrote: hi, It's the destination name for the dead letter queue. You can have a consumer listen to this queue and should be able to get the message(if any) off the DLQ . Regards, Jonas Christopher_Ong wrote: May I know what is ActiveMQ.DLQ? -- View this message in context: http://www.nabble.com/ActiveMQ.DLQ-tf2407939.html#a6753187 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: renaming servicemix-jsr181?
if we call it servicemix-cxf or servicemix-xfire - that still isn't very descriptive of what it does :) I've read the documentation several times and I *still* don't know what it does. :) Terry
[jira] Commented: (SM-670) Including JMSFlow in default servicemix.conf
[ https://issues.apache.org/activemq/browse/SM-670?page=comments#action_37157 ] Jamie McCrindle commented on SM-670: Could you add this to 3.0.1 branch? thanks, j. Including JMSFlow in default servicemix.conf Key: SM-670 URL: https://issues.apache.org/activemq/browse/SM-670 Project: ServiceMix Issue Type: Improvement Components: servicemix-assembly Affects Versions: 3.0 Environment: All Reporter: Jamie McCrindle Assigned To: Guillaume Nodet Fix For: 3.1 It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box. sm:jmsFlow jmsURL=tcp://localhost:61616 / -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-670) Including JMSFlow in default servicemix.conf
[ https://issues.apache.org/activemq/browse/SM-670?page=all ] Jamie McCrindle updated SM-670: --- Attachment: servicemix.xml.jmsflow.patch patch for 3.0.1 Including JMSFlow in default servicemix.conf Key: SM-670 URL: https://issues.apache.org/activemq/browse/SM-670 Project: ServiceMix Issue Type: Improvement Components: servicemix-assembly Affects Versions: 3.0 Environment: All Reporter: Jamie McCrindle Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: servicemix.xml.jmsflow.patch It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box. sm:jmsFlow jmsURL=tcp://localhost:61616 / -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Info needed: migrating openejb-itests to testsuite framework
On 10/11/06, Prasad Kashyap [EMAIL PROTECTED] wrote: David, Thanks for that write-up on the openejb itests. It helped me understand the structure better. All the client code (in src/itests) have a dependency on the beans (in src/java) anyway. So this is what I did. I put all the beans in 1 core project (openejb-itests). I put the plans and DDs in their individual projects. The individual projects then unpack just the needed classes from that core project and build the ejb archive with it's plan and DD. testsuite/ejbcontainer-testsuite ejb-modules openejb-itests -- core project with beans openejb-security-001 -- just plan and DD openejb-security-002 openejb-security-003 openejb-cmp2-prefetch openejb-cmp2-petstore openejb-cmp2-cmrmapping openejb-cmp2-storage test-ejbcontainer --- junit tests in client Hi Prasad, Why are the matter being discussed here? Shouldn't it go to openejb-dev? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r462587 - in /geronimo/server/trunk: configs/client-deployer/src/plan/ modules/geronimo-connector-builder/src/main/java/org/apache/geronimo/connector/deployment/
On 10/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: djencks
Date: Tue Oct 10 14:36:45 2006
New Revision: 462587
URL: http://svn.apache.org/viewvc?view=revrev=462587
Log:
GERONIMO-2383 Forgot the isMergeEnvironment in a couple builders. Give client
builder its own ref builders
...
+protected boolean willMergeEnvironment(XmlObject specDD, XmlObject plan) {
+return specDD.selectChildren(adminOjbectRefQNameSet).length 0 ||
specDD.selectChildren(messageDestinationRefQNameSet).length 0;
+}
...
+protected boolean willMergeEnvironment(XmlObject specDD, XmlObject plan) {
+return specDD.selectChildren(resourceRefQNameSet).length 0;
+}
+
I'm kind of confused. You wrote isMergeEnvironment in the commit log
whereas the method name starts with 'will'. I think you were right in
your commit log as it tests not does something.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
[jira] Updated: (GERONIMO-2471) JMX Portlet doesn't display all the attributes of a web module
[ http://issues.apache.org/jira/browse/GERONIMO-2471?page=all ] Christopher M. Cardona updated GERONIMO-2471: - Attachment: GERONIMO-2471_2472-trunk.patch Attached patch which includes the fix for GERONIMO-2471 and GERONIMO-2472. JMX Portlet doesn't display all the attributes of a web module -- Key: GERONIMO-2471 URL: http://issues.apache.org/jira/browse/GERONIMO-2471 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Reporter: Christopher M. Cardona Assigned To: Christopher M. Cardona Fix For: 1.2 Attachments: GERONIMO-2471_2472-trunk.patch Viewing a web module doesn't display all its attributes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2472) Remove the display of GBeanInfo attribute in the JMX portlet
[ http://issues.apache.org/jira/browse/GERONIMO-2472?page=all ] Christopher M. Cardona updated GERONIMO-2472: - Attachment: GERONIMO-2471_2472-trunk.patch Attached patch which includes the fix for GERONIMO-2471 and GERONIMO-2472. Remove the display of GBeanInfo attribute in the JMX portlet Key: GERONIMO-2472 URL: http://issues.apache.org/jira/browse/GERONIMO-2472 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: Christopher M. Cardona Assigned To: Christopher M. Cardona Priority: Minor Fix For: 1.2 Attachments: GERONIMO-2471_2472-trunk.patch When viewing MBean's attributes in the JMX portlet we should exclude GBeanInfo attributes. This was suggested in the devlist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: micro-G modules(configs)
On 10/9/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Anyway, should I put these ideas on the cwiki for discussion / clarification? It sounds that this is the general direction we're headed in and is rather unique. If we agree in concept it would be good to get our web page updated to reflect these goals (vision) of the project so people can see where we're going and get involved if they're interested. Sure. Why not!? It's been a while since I marked the thread to read when the time permits and I must admit I like the concept of templating. I'm not sure how it's different from config.xml where you declare your deps, but it's worth to give it a thought again and sort it out. Or wait, do you want the templating tool to download (from a local or remote repo) necessary modules and create an assembly? Isn't it what car-maven-plugin and maven-assembly-plugin together are doing now? It's definitely worth to put the idea on the wiki. Even if it dies at some time (which I doubt) we can move to it later or wipe it out. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r462651 - /geronimo/genesis/trunk/plugins/script-maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/script/GroovyMojo.java
On 10/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: jdillon Date: Tue Oct 10 17:59:15 2006 New Revision: 462651 URL: http://svn.apache.org/viewvc?view=revrev=462651 Log: Improve exception reporting Use delegate to allow MavenProject.getProperties() to return resolved props, since 'properties' is special in Groovy Add 'script' helper... not sure if there is already something similar Register pom alias for project Where is the change described as 'Register pom alias for project'? I can't seem to find it. Could you describe what it is for? It reads quite interesting ;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r462651 - /geronimo/genesis/trunk/plugins/script-maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/script/GroovyMojo.java
See GroovyMojo.java line 181. Its not quite as interesting as you might think ;-) --jason On Oct 10, 2006, at 11:24 PM, Jacek Laskowski wrote: On 10/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: jdillon Date: Tue Oct 10 17:59:15 2006 New Revision: 462651 URL: http://svn.apache.org/viewvc?view=revrev=462651 Log: Improve exception reporting Use delegate to allow MavenProject.getProperties() to return resolved props, since 'properties' is special in Groovy Add 'script' helper... not sure if there is already something similar Register pom alias for project Where is the change described as 'Register pom alias for project'? I can't seem to find it. Could you describe what it is for? It reads quite interesting ;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [DISCUSS] Release Xbean 2.7
On 10/11/06, Guillaume Nodet [EMAIL PROTECTED] wrote: What about releasing xbean 2.7 ? Go for it! I'm having troubles with maven-assembly-plugin and XBean 2.7-SNAPSHOT that I think I could work around with 2.7. The sooner the merrier. +1 Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Commented: (SM-697) Using XSLT servicemix component causes a java.io.IOException: Too many open files
[ https://issues.apache.org/activemq/browse/SM-697?page=comments#action_37155 ] Helene Joanin commented on SM-697: -- It works fine now. Thanks. Using XSLT servicemix component causes a java.io.IOException: Too many open files --- Key: SM-697 URL: https://issues.apache.org/activemq/browse/SM-697 Project: ServiceMix Issue Type: Bug Components: servicemix-components Affects Versions: 3.0 Environment: Linux: ServiceMix 3.1-incubating-SNAPSHOT from 2006-10-02 Reporter: Helene Joanin Attachments: sm-http-xslt.zip Using the XSLT servicemix component causes a java.io.IOException: Too many open files A close of a stream or a socket seems to be forget in the servicemix component. You can find in attachment a very simple example to reproduce the problem. To run this example: - the SERVICEMIX_HOME variable must be setting, - then under the sm-http-xslt directory do: $ ant setup $ servicemix ./servicemix.xml $ ant run ant run will execute 512 times the client. Just do it quite often to exceed the limit of the number of file descriptors a process may have on your system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r462651 - /geronimo/genesis/trunk/plugins/script-maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/script/GroovyMojo.java
On 10/11/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not quite as interesting as you might think ;-) But the next time it's going to be something really awesome, isn't it? ;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: Location to host JBI components
'd like to start a thread about where JBI components that are contributed by users should be hosted. I think that, like most other applications that have plugins, we should cover all three bases. Components maintained by the core team should be hosted locally. An open repository should exist for components donated by third parties who don't have the resources to host them themselves and this repository should have no licensing restrictions. At the same time, a list of external components should exist on the main site to integrate larger third party projects that provide JBI connectivity as part of their remit. I agree with the need to split the component's lifecycle from that of the container. From an enterprise point of view, most IT departments would want to work against a fixed release version of a container, but would consider the merits of each component as it became available, based upon their needs. This has a couple of implications. We would need strong integration tests for each component so that we could ensure compatibility with new container releases and we would need to keep a history of component versions to ensure ongoing backward compatibility against prior container releases. We should also clearly mark as deprecated those components that have been superceded by cleaner approaches and try to provide migration advice where possible. Terry
Re: svn commit: r462651 - /geronimo/genesis/trunk/plugins/script-maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/script/GroovyMojo.java
I dunno... I might have to come up with some more magic to get the tck to run. But its probably not going to be anything I would consider awesome... unless I can figure out how to make Maven go down to the store and buy me some beer :-P --jason On Oct 11, 2006, at 12:28 AM, Jacek Laskowski wrote: On 10/11/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not quite as interesting as you might think ;-) But the next time it's going to be something really awesome, isn't it? ;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Created: (GERONIMO-2483) Yoko support also requires the yoko-rmi jar on the endorsed jars class path.
Yoko support also requires the yoko-rmi jar on the endorsed jars class path. - Key: GERONIMO-2483 URL: http://issues.apache.org/jira/browse/GERONIMO-2483 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: CORBA Affects Versions: 1.2 Reporter: Rick McGuire Assigned To: Rick McGuire Fix For: 1.2 The Sun version of the javax.rmi classes is failing to load the yoko rmi implementation unless the classes are resident in endorsed.dirs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ActiveMQ.DLQ
AFAIK, expired messages are not sent to DLQ.You can raise a jira for this if you want this feature added :) http://issues.apache.org/activemq/secure/Dashboard.jspa Regards, Jonas Christopher_Ong wrote: Sorry, what do you meant you don't believe expired messages are sent to DLQs though? Does it mean that u oso facing the problem to automatically send the dead msg to DLQ? jlim wrote: Hi, Messages are automatically sent to DLQ when they hit their redelivery maximum. I don't believe expired messages are sent to DLQs though. Regards, Jonas Christopher_Ong wrote: Is it when the message expire then it will auto been sent to DLQ? Or I have to manually send it to the DLQ? jlim wrote: Oh btw, here is an example on using them : https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/RedeliveryPolicyTest.java Jonas Lim wrote: hi, It's the destination name for the dead letter queue. You can have a consumer listen to this queue and should be able to get the message(if any) off the DLQ . Regards, Jonas Christopher_Ong wrote: May I know what is ActiveMQ.DLQ?
e-Mail woes
Apologies in advance. My ISP had another issue related to e-mail over the past few days and its come to my attention that many e-mails have disappeared. I will replay the digests and see what I missed. I've moved to another ISP so hopefully this problem will be resolved. Apologies. Matt Hogstrom [EMAIL PROTECTED]
servicemix-web error
Hello, when I try to start tomcat with the servicemix-web webbapp I encounter this error: - Installing web application at context path /servicemix-web from URL file:D:\To mcat5\webapps\servicemix-web ERROR - ContextLoader - Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected excep tion parsing XML document from ServletContext resource [/WEB-INF/applicationCont ext.xml]; nested exception is java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement method Caused by: java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement metho d Can someone help me? Best Regards, Emilio -- View this message in context: http://www.nabble.com/servicemix-web-error-tf2423166.html#a6755641 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Created: (SM-703) http endpoint wsdl generation
http endpoint wsdl generation - Key: SM-703 URL: https://issues.apache.org/activemq/browse/SM-703 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0 Reporter: Fabrice Dewasmes Hi, When you try to deploy a http provider endpoint, the target WSDL is parsed. If the targetNamespace of the targeted service is different from the endpoint namespace, the targeted wsdl is imported and operations are replicated to build the endpoint internal WSDL. But when a consumer proxies this provider, it parses the internal WSDL but fails to find the imported WSDL. Problem is coming from WSDLReader with this error : 14:01:27,344 WARN [EndpointRegistry] Error retrieving interfaces from service description: WSDLException (at /definitions/import): faultCode=OTHER_ERROR: Unable to resolve imported document at 'porttypedef.wsdl'.: This file was not found: file:/R:/java/tools/jboss/4_0_3-eici/bin/porttypedef.wsdl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: servicemix-web error
Can you paste the full stack trace ? The cause of the error is always at the bottom ... On 10/11/06, emicalc [EMAIL PROTECTED] wrote: Hello, when I try to start tomcat with the servicemix-web webbapp I encounter this error: - Installing web application at context path /servicemix-web from URL file:D:\To mcat5\webapps\servicemix-web ERROR - ContextLoader - Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected excep tion parsing XML document from ServletContext resource [/WEB-INF/applicationCont ext.xml]; nested exception is java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement method Caused by: java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement metho d Can someone help me? Best Regards, Emilio -- View this message in context: http://www.nabble.com/servicemix-web-error-tf2423166.html#a6755641 Sent from the ServiceMix - Dev mailing list archive at Nabble.com. -- Cheers, Guillaume Nodet
[jira] Commented: (AMQ-826) LDAP based authorization support
[ https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37159 ] james strachan commented on AMQ-826: Hi Nikola Don't worry about the maven stuff, I can try help with that - its mostly to get a unit test running that boots up an embedded ApacheDS, loads it with the necessary test data, then runs the test case. LDAP based authorization support Key: AMQ-826 URL: https://issues.apache.org/activemq/browse/AMQ-826 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Assigned To: Nikola Goran Cutura Attachments: LdapAuth.zip Patch kindly added by ngcutura - discussion thread... http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Info needed: migrating openejb-itests to testsuite framework
Hi Jacek, We now have a testsuite directory under geronimo which is the basis for a system and functional test framework for all of Geronimo. I have begun with a doc in the wiki about this. http://cwiki.apache.org/GMOxDEV/integration-testing.html The doc is still in a rudimentary stage but it will give you a general idea. I am enhancing it as I go along. This discussion revolves around migrating the openejb itests to this new framework. So after a G assembly is done, the build will continue to testing the various functional pieces of the server like webcontainer, ejbcontainer, console, clustering etc. Cheers Prasad On 10/11/06, Jacek Laskowski [EMAIL PROTECTED] wrote: On 10/11/06, Prasad Kashyap [EMAIL PROTECTED] wrote: David, Thanks for that write-up on the openejb itests. It helped me understand the structure better. All the client code (in src/itests) have a dependency on the beans (in src/java) anyway. So this is what I did. I put all the beans in 1 core project (openejb-itests). I put the plans and DDs in their individual projects. The individual projects then unpack just the needed classes from that core project and build the ejb archive with it's plan and DD. testsuite/ejbcontainer-testsuite ejb-modules openejb-itests -- core project with beans openejb-security-001 -- just plan and DD openejb-security-002 openejb-security-003 openejb-cmp2-prefetch openejb-cmp2-petstore openejb-cmp2-cmrmapping openejb-cmp2-storage test-ejbcontainer --- junit tests in client Hi Prasad, Why are the matter being discussed here? Shouldn't it go to openejb-dev? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
[jira] Created: (AMQ-968) Store and Forward reconnect failures
Store and Forward reconnect failures Key: AMQ-968 URL: https://issues.apache.org/activemq/browse/AMQ-968 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2 Environment: All Reporter: Andy Piper Attachments: jmstest.zip For the AMQ reconnection issue, I think it is caused by client can not stop the broker correctly after server broker is stopped. Attached zip is the test case, it is an IDEA prj, to compile or run it the incubator-activemq-4.0.jar (download from http://people.apache.org/repository/incubator-activemq/jars/incubator-activemq-4.0.jar ) should be involved. In the prj, I added two run configurations: Client, Sever to try all kinds of connection scenarios below: 1. Start client, then start server 2. Start server, then start client 3. Restart client 4. Restart server 5. Stop server, then stop client, after that restart server again, then restart client All scenarios will be successful if using the run configurations in IDEA, but if we run the server and client in DOS command line, we will find the #5 is failed. Here is the reason, if the server broker is stopped, the client can not be stopped using CTL + C, and the interrupt signal is always only captured by the client broker rather than its JVM. In this time, if we restart the server, no any messages can be received again. But the messages in client can not be lost, after killing the client and restarting it, the messages can be still sent to server. So to the scenario in Domain Log, the managed server must be killed by kill-9 shell and can not be stopped by shutdown.bat (sh) script. Uunfortunately, the scenario #4 is still failed in Domain Log though the codes are same with above test case's (it IS successful in the test case). I can not get the reason after I struggled for it the whole day :(. I am not sure if the AMQ network connector is impacted in Tomcat runtime env. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-969) .NET Compact Framevork compatibility
.NET Compact Framevork compatibility Key: AMQ-969 URL: https://issues.apache.org/activemq/browse/AMQ-969 Project: ActiveMQ Issue Type: Improvement Components: NMS (C# client) Environment: .NET Compact Framework 2.0 Reporter: Oleg Deribas For connecting to ActiveMQ from PDA (PocketPC) NMS should be compiled for .NET Compact Framework. And currently there are not projects for .NET CF in vs2005 solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-969) .NET Compact Framevork compatibility
[ https://issues.apache.org/activemq/browse/AMQ-969?page=all ] Oleg Deribas updated AMQ-969: - Attachment: nms-cf20-projects.zip As a first step I've created projects for CF. Project files and solution which includes these projects are in attachment. .NET Compact Framevork compatibility Key: AMQ-969 URL: https://issues.apache.org/activemq/browse/AMQ-969 Project: ActiveMQ Issue Type: Improvement Components: NMS (C# client) Environment: .NET Compact Framework 2.0 Reporter: Oleg Deribas Attachments: nms-cf20-projects.zip For connecting to ActiveMQ from PDA (PocketPC) NMS should be compiled for .NET Compact Framework. And currently there are not projects for .NET CF in vs2005 solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-969) .NET Compact Framevork compatibility
[
https://issues.apache.org/activemq/browse/AMQ-969?page=comments#action_37161 ]
Oleg Deribas commented on AMQ-969:
--
Currently there are some small incompatibilities with CF caused by
Monitor.Wait/Monitor.PulseAll methods usage as these methods are absent in CF.
I think it is possible to replace {{Monitor.Wait(semaphore, maxWait)}} with:
{{Monitor.Exit(semaphore);}}
{{autoResetEvent.WaitOne(maxWait, false);}}
{{Monitor.Enter(semaphore);}}
and {{Monitor.PulseAll(semaphore)}} with:
{{Monitor.Exit(semaphore);}}
{{autoResetEvent.Set();}}
{{Monitor.Enter(semaphore);}}
And possibly class which uses AutoResetEvent should implement IDisposable
interface and call autoResetEvent.Close() in Dispose method.
.NET Compact Framevork compatibility
Key: AMQ-969
URL: https://issues.apache.org/activemq/browse/AMQ-969
Project: ActiveMQ
Issue Type: Improvement
Components: NMS (C# client)
Environment: .NET Compact Framework 2.0
Reporter: Oleg Deribas
Attachments: nms-cf20-projects.zip
For connecting to ActiveMQ from PDA (PocketPC) NMS should be compiled for
.NET Compact Framework.
And currently there are not projects for .NET CF in vs2005 solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: servicemix-web error
Thank you for the replay. This is the full stack trace - Initializing Coyote HTTP/1.1 on http-8080 - Initialization processed in 1462 ms - Starting service Catalina - Starting Servlet Engine: Apache Tomcat/5.0.28 - XML validation disabled - Create Host deployer for direct deployment ( non-jmx ) - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\admin.xml - Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true - Initializing, config='org.apache.struts.action.ActionResources', returnNull=tr ue - Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNul l=true - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\balancer.xml - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\CreateUbl.xml - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\manager.xml - Installing web application at context path /abilities from URL file:D:\Tomcat5 \webapps\abilities - Installing web application at context path /argos from URL file:D:\Tomcat5\web apps\argos - Installing web application at context path /axis from URL file:D:\Tomcat5\weba pps\axis - Unable to find config file. Creating new servlet engine config file: /WEB-INF /server-config.wsdd - Installing web application at context path /jsp-examples from URL file:D:\Tomc at5\webapps\jsp-examples - Installing web application at context path from URL file:D:\Tomcat5\webapps\R OOT - Installing web application at context path /servicemix-web from URL file:D:\To mcat5\webapps\servicemix-web ERROR - ContextLoader - Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected excep tion parsing XML document from ServletContext resource [/WEB-INF/applicationCont ext.xml]; nested exception is java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement method Caused by: java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement metho d at org.apache.xbean.spring.context.v2b.XBeanBeanDefinitionParserDelegate .internalParseNestedCustomElement(XBeanBeanDefinitionParserDelegate.java:95) at org.apache.xbean.spring.context.v2b.XBeanBeanDefinitionParserDelegate .parsePropertySubElement(XBeanBeanDefinitionParserDelegate.java:50) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.pa rseListElement(BeanDefinitionParserDelegate.java:914) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseListEl ement(XBeanNamespaceHandler.java:581) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseNested PropertyViaIntrospection(XBeanNamespaceHandler.java:574) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.tryParseNes tedPropertyViaIntrospection(XBeanNamespaceHandler.java:543) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.addNestedPr opertyElements(XBeanNamespaceHandler.java:512) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFr omExtensionElement(XBeanNamespaceHandler.java:208) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFr omExtensionElement(XBeanNamespaceHandler.java:253) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parse(XBean NamespaceHandler.java:153) at org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanN amespaceHandler.java:49) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.pa rseCustomElement(BeanDefinitionParserDelegate.java:1118) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentRe ader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:141) at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader. parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:39) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentRe ader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registe rBeanDefinitions(XmlBeanDefinitionReader.java:496) at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.regis terBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB eanDefinitions(XmlBeanDefinitionReader.java:406) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea nDefinitions(XmlBeanDefinitionReader.java:360) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea nDefinitions(XmlBeanDefinitionReader.java:335) at org.springframework.beans.factory.support.AbstractBeanDefinitionReade r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126) at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
writing Geronimo documentation
Hi All, it is great to see so many folks contributing to Geronimo's documentation. I put together some guidelines for text formatting that may help us to maintain a consistent look and feel for all the documentation and other Geronimo spaces we are working on. http://cwiki.apache.org/geronimo/tips-for-writing-and-formatting-documentation.html Comments welcome! Cheers! Hernan
Re: [DISCUSS] Release Xbean 2.7
+1 Let's do it -dain On Oct 10, 2006, at 6:27 PM, Guillaume Nodet wrote: What about releasing xbean 2.7 ? There has been a bunch of fixes [1] and the new xbean-naming module. [1] https://issues.apache.org/jira/secure/IssueNavigator.jspa? reset=truepid=12310312fixfor=12312005 -- Cheers, Guillaume Nodet
Re: svn commit: r462587 - in /geronimo/server/trunk: configs/client-deployer/src/plan/ modules/geronimo-connector-builder/src/main/java/org/apache/geronimo/connector/deployment/
On Oct 11, 2006, at 1:21 AM, Jacek Laskowski wrote:
On 10/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: djencks
Date: Tue Oct 10 14:36:45 2006
New Revision: 462587
URL: http://svn.apache.org/viewvc?view=revrev=462587
Log:
GERONIMO-2383 Forgot the isMergeEnvironment in a couple builders.
Give client builder its own ref builders
...
+protected boolean willMergeEnvironment(XmlObject specDD,
XmlObject plan) {
+return specDD.selectChildren
(adminOjbectRefQNameSet).length 0 || specDD.selectChildren
(messageDestinationRefQNameSet).length 0;
+}
...
+protected boolean willMergeEnvironment(XmlObject specDD,
XmlObject plan) {
+return specDD.selectChildren(resourceRefQNameSet).length
0;
+}
+
I'm kind of confused. You wrote isMergeEnvironment in the commit log
whereas the method name starts with 'will'. I think you were right in
your commit log as it tests not does something.
The patch is right, this is a protected method in
AbstractNamingBuilder, and depending on the answer we proceed to
merge environments or not.
The method name might not be ideal, but changing it would be a much
bigger patch.
thanks
david jencks
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
[jira] Created: (AMQ-970) Compiling fails under SuSe
Compiling fails under SuSe -- Key: AMQ-970 URL: https://issues.apache.org/activemq/browse/AMQ-970 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Environment: gcc (GCC) 3.3.3 (SuSE Linux) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking build system type... x86_64-suse-linux checking host system type... x86_64-suse-linux checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking whether build environment is sane... yes checking whether byte ordering is bigendian... no checking for short... yes checking size of short... 2 checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 8 checking uuid.h usability... no checking
[jira] Created: (SM-704) FTPPoller Improvements
FTPPoller Improvements -- Key: SM-704 URL: https://issues.apache.org/activemq/browse/SM-704 Project: ServiceMix Issue Type: Improvement Components: servicemix-components Affects Versions: 3.0 Environment: Windows XP SP2; JSE 6 Beta 2 Reporter: Los Morales Priority: Minor Fix For: 3.0 In the org.apache.servicemix.components.net.FTPPoller class, there are two things that can be improved upon. 1) Give the option to NOT delete the files from the FTP server by adding a deleteFile attribute w/ corresponding accessors. In order to make this work, you will also need to keep track of the files already retrieved by using the java.util.concurrent.CopyOnWriteArraySet to keep track of each FTPFile's raw listing. 2) In the processFile() method, move the client.completePendingCommand() line AFTER the call to in.close(). Sometimes my program would hang indefinitely when the call to completePendingCommand() was done prior to closing the input stream. This situation is discussed here as well: http://mail-archives.apache.org/mod_mbox/jakarta-commons-user/200412.mbox/[EMAIL PROTECTED] -los -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (GERONIMO-2482) Remove console JARs from WEB-INF/lib
I'm just warning that unless those issues are actually fixed in that version that there is going to be a bunch of work needed to properly sort out jira when it comes release time. --jason On Oct 10, 2006, at 1:51 PM, Aaron Mulder wrote: Isn't the point of a road map to show what's coming / targeted for each release? Otherwise, it's release notes, not a road map. I feel pretty strongly that we should have some way for Jira to present a list of the issues targeted to be included in each release. Do you have an alternative to the road map to suggest? Thanks, Aaron On 10/10/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not about what version you believe it should be fixed in... fixed versions is for what version it was actually fixed in. This value is used to generate the change log in the roadmap and if the issue is not actually fixed in that version it just pollutes the details that jira shows us. For example, if this issue is not actually fixed in 1.1.2, but instead fixed in 1.1.3, then there is some confusion when inspecting the roadmap for what was fixed where. --jason On Oct 10, 2006, at 1:33 PM, Aaron Mulder wrote: How else can we track what versions we believe it should be fixed in? I don't know how else I'd find issues to fix in 1.1.2 out of the 500+ open issues. Thanks, Aaorn On 10/10/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not a good idea to set the fix for version when creating an issue. This should be set when closing the issue. --jason On Oct 10, 2006, at 1:17 PM, Aaron Mulder (JIRA) wrote: Remove console JARs from WEB-INF/lib Key: GERONIMO-2482 URL: http://issues.apache.org/jira/browse/ GERONIMO-2482 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 1.1.1 Reporter: Aaron Mulder Fix For: 1.1.2, 1.2 It's unnecessarily hard to build console extension plugins because the car-maven-plugin can't access JARs in a WEB-INF/lib directory. The console web apps should not package any JARs, but instead use dependency elements to add them to the class path. (e.g. console- framework packages castor) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/ software/jira
Re: servicemix-web error
This is a known bug (see http://issues.apache.org/activemq/browse/SM-593). You can easily fix it by removing the a line in the pom as shown in http://svn.apache.org/viewvc/incubator/servicemix/branches/servicemix-3.0/samples/servicemix-web/pom.xml?r1=448366r2=449600pathrev=449600diff_format=h On 10/11/06, emicalc [EMAIL PROTECTED] wrote: Thank you for the replay. This is the full stack trace - Initializing Coyote HTTP/1.1 on http-8080 - Initialization processed in 1462 ms - Starting service Catalina - Starting Servlet Engine: Apache Tomcat/5.0.28 - XML validation disabled - Create Host deployer for direct deployment ( non-jmx ) - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\admin.xml - Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true - Initializing, config='org.apache.struts.action.ActionResources', returnNull=tr ue - Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNul l=true - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\balancer.xml - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\CreateUbl.xml - Processing Context configuration file URL file:D:\Tomcat5\conf\Catalina\localh ost\manager.xml - Installing web application at context path /abilities from URL file:D:\Tomcat5 \webapps\abilities - Installing web application at context path /argos from URL file:D:\Tomcat5\web apps\argos - Installing web application at context path /axis from URL file:D:\Tomcat5\weba pps\axis - Unable to find config file. Creating new servlet engine config file: /WEB-INF /server-config.wsdd - Installing web application at context path /jsp-examples from URL file:D:\Tomc at5\webapps\jsp-examples - Installing web application at context path from URL file:D:\Tomcat5\webapps\R OOT - Installing web application at context path /servicemix-web from URL file:D:\To mcat5\webapps\servicemix-web ERROR - ContextLoader - Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected excep tion parsing XML document from ServletContext resource [/WEB-INF/applicationCont ext.xml]; nested exception is java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement method Caused by: java.lang.IllegalStateException: Unable to invoke parseNestedCustomElement metho d at org.apache.xbean.spring.context.v2b.XBeanBeanDefinitionParserDelegate .internalParseNestedCustomElement(XBeanBeanDefinitionParserDelegate.java:95) at org.apache.xbean.spring.context.v2b.XBeanBeanDefinitionParserDelegate .parsePropertySubElement(XBeanBeanDefinitionParserDelegate.java:50) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.pa rseListElement(BeanDefinitionParserDelegate.java:914) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseListEl ement(XBeanNamespaceHandler.java:581) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseNested PropertyViaIntrospection(XBeanNamespaceHandler.java:574) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.tryParseNes tedPropertyViaIntrospection(XBeanNamespaceHandler.java:543) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.addNestedPr opertyElements(XBeanNamespaceHandler.java:512) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFr omExtensionElement(XBeanNamespaceHandler.java:208) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parseBeanFr omExtensionElement(XBeanNamespaceHandler.java:253) at org.apache.xbean.spring.context.v2b.XBeanNamespaceHandler.parse(XBean NamespaceHandler.java:153) at org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanN amespaceHandler.java:49) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.pa rseCustomElement(BeanDefinitionParserDelegate.java:1118) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentRe ader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:141) at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader. parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:39) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentRe ader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registe rBeanDefinitions(XmlBeanDefinitionReader.java:496) at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.regis terBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB eanDefinitions(XmlBeanDefinitionReader.java:406) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea nDefinitions(XmlBeanDefinitionReader.java:360) at
[jira] Created: (AMQ-971) NMSTimestamp returning LocalTime instead of UTC
NMSTimestamp returning LocalTime instead of UTC --- Key: AMQ-971 URL: https://issues.apache.org/activemq/browse/AMQ-971 Project: ActiveMQ Issue Type: Improvement Components: NMS (C# client) Affects Versions: incubation Environment: Windows Reporter: Rob Lugt Priority: Minor The NMSTimestamp property has been changed from long to DateTime - which is a good thing. However, the DateTime is currently being adjusted to localtime before being returned to the client - which is probably not ideal. The DateTime struct does not contain timezone information, therefore the programmer has to make some assumption about what timezone the time is expressed in. A UTC time is more in-keeping with the JMS specification - which specifies that Timestamp is a normal Java time i.e. expressed in GMT. This article from Microsoft also suggests using UTC as a common time where possible: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/datetimecode.asp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Test - please ignore
Matt Hogstrom [EMAIL PROTECTED]
[jira] Created: (GERONIMO-2484) NamespaceDrivenBuilders should register QNameSets
NamespaceDrivenBuilders should register QNameSets - Key: GERONIMO-2484 URL: http://issues.apache.org/jira/browse/GERONIMO-2484 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: 1.2 All the NamespaceDrivenBuilders appear to register localParts rather than namespaces from getNamespace. In any case these should, like the NamingBUilders, register a QNameSet instead. Similar code from these kind of builders should be moved to a superclass. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-966) NMSDestination is null when receiving messages
[ https://issues.apache.org/activemq/browse/AMQ-966?page=comments#action_37170 ] Rob Lugt commented on AMQ-966: -- I see that the NMSDestination property in ActiveMQMessage returns the OriginalDestination instead of the Destination property. Is there a reason for this? It looks like Destination contains the correct value. Regards ~Rob NMSDestination is null when receiving messages -- Key: AMQ-966 URL: https://issues.apache.org/activemq/browse/AMQ-966 Project: ActiveMQ Issue Type: Bug Components: NMS (C# client) Affects Versions: 4.0.2 Reporter: Rob Lugt The NMSDestination property is null when receiving messages via an asynchronous listener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2485) PersistenceUnitGBean needs a NamespaceDrivenDeployer
PersistenceUnitGBean needs a NamespaceDrivenDeployer Key: GERONIMO-2485 URL: http://issues.apache.org/jira/browse/GERONIMO-2485 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: persistence Affects Versions: 1.2 Reporter: David Jencks Assigned To: David Jencks Fix For: 1.2 Most of the config into in PersistenceUnitGBean can be read out of persistence.xml. We should write a NamespaceDrivenBuilder that uses custom xml and can either set stuff from the supplied xml, look for persistence.xml in a specified location, or look for persistence.xml in a default location, and parse persistence.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: gcache imlementation ideas[long]
I addressed the discussion about what transport do we use, a long time ago by creating an agnostic API to plug into. http://marc.theaimsgroup.com/?l=geronimo-devm=115281186718399w=2 http://people.apache.org/~fhanik/geronimo-cluster-api.zip this way, we can continue the pluggability of G, and not pushing any specific protocols. but writing a custom one just for G doesn't sound like a sound solution in addition to ehcache, I'd like to propose that we take a look at ASF's JCS(Java Cache System) which sits under the Jakarta umbrella. http://jakarta.apache.org/jcs/index.html and a performance report http://jakarta.apache.org/jcs/JCSvsEHCache.html (could be outdated) sorry about splitting up the gcache discussion, actually it was already split when we started talking about the transport a while back in this thread. However, my take on it is that we should use code already written, while this is all really cool stuff to work on, creating a distributed cache from start is hard and takes a very long time. I would think the main goal is to get to JEE 5 right now. Filip Jason Dillon wrote: On Sep 14, 2006, at 7:56 AM, Jeff Genender wrote: The JMS provider would be a pluggable comm strategy. For performance reasons, I want to start with TCP communication. Why do you think that AMQ will not perform well? I definitely want to have a JMS strategy...maybe next. But initially I don't want any dependencies on other servers or brokers. With that said, after looking at openwire, the comm marshaller for ActiveMQ, there is a lot to leverage there and will prevent a rewrite of the comm layer. So, there will be some use of that code base initially. IMO, AMQ already provides a rich clustering environment, with failover, master-slave, dynamic discovery, firewall-happy transports, monitoring and a heck of a lot more. Seems like it would be a waste to go and re-implement all of that. It also seems that if you wanted to get something up sooner, that it would be much easier to design a AMQ strategy first, which means that you only have to worry about the message passing to sync up and invalidate state, rather than all of the details of who is in what cluster, failing over, blah, blah... And, I guess that if after that was implemented you still thought it was not fast enough, then it might be better to get AMQ fixed to perform better, though I don't think that the performance using AMQ will differ all that much from a custom socket protocol to pass messages. I am a huge fan of AMQ and would really like to see G exploit its network communications facilities as much as possible. IMO, this is the best way to get the most features for clustering up and running sooner, with less code to maintain. --jason --No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.3/447 - Release Date: 9/13/2006
[jira] Created: (GERONIMODEVTOOLS-112) Loading deployment plan editor on empty file should auto-create plan
Loading deployment plan editor on empty file should auto-create plan Key: GERONIMODEVTOOLS-112 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-112 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.x Reporter: Sachin Patel Assigned To: Sachin Patel Priority: Minor Fix For: 1.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-111) Allow project publish order to be controlled by project build order
Allow project publish order to be controlled by project build order --- Key: GERONIMODEVTOOLS-111 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-111 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Reporter: Sachin Patel Assigned To: Sachin Patel Fix For: 1.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-113) Granualize trace statements
Granualize trace statements --- Key: GERONIMODEVTOOLS-113 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-113 Project: Geronimo-Devtools Issue Type: Improvement Affects Versions: 1.x Reporter: Sachin Patel Assigned To: Sachin Patel Priority: Minor Fix For: 1.x Too many trace statements, need to break them down into INFO, ERROR, FINE and FINEST or something similar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r463024 - in /geronimo/plugins/spring: branches/ tags/ trunk/ trunk/modules/ trunk/modules/spring-deployer-service/ trunk/modules/spring-deployer-service/src/ trunk/modules/spring-depl
I'd avoid making new projects that have a modules/* Just organize your modules in the root, or make modules to organize them into meaningful groups. --jason On Oct 11, 2006, at 3:55 PM, [EMAIL PROTECTED] wrote: Author: ammulder Date: Wed Oct 11 15:55:25 2006 New Revision: 463024 URL: http://svn.apache.org/viewvc?view=revrev=463024 Log: Initial skeleton of Spring integration Added: geronimo/plugins/spring/branches/ geronimo/plugins/spring/tags/ geronimo/plugins/spring/trunk/ (with props) geronimo/plugins/spring/trunk/modules/ geronimo/plugins/spring/trunk/modules/spring-deployer- service/ (with props) geronimo/plugins/spring/trunk/modules/spring-deployer-service/ pom.xml (with props) geronimo/plugins/spring/trunk/modules/spring-deployer-service/src/ geronimo/plugins/spring/trunk/modules/spring-deployer-service/ src/java/ geronimo/plugins/spring/trunk/modules/spring-integration- service/ (with props) geronimo/plugins/spring/trunk/modules/spring-integration- service/pom.xml (with props) geronimo/plugins/spring/trunk/modules/spring-integration- service/src/ geronimo/plugins/spring/trunk/modules/spring-integration- service/src/java/ geronimo/plugins/spring/trunk/pom.xml (with props) Propchange: geronimo/plugins/spring/trunk/ -- --- svn:ignore (added) +++ svn:ignore Wed Oct 11 15:55:25 2006 @@ -0,0 +1,4 @@ +target +svn-* +velocity* +*.i?? Propchange: geronimo/plugins/spring/trunk/modules/spring-deployer- service/ -- --- svn:ignore (added) +++ svn:ignore Wed Oct 11 15:55:25 2006 @@ -0,0 +1,4 @@ +target +svn-* +velocity* +*.i?? Added: geronimo/plugins/spring/trunk/modules/spring-deployer- service/pom.xml URL: http://svn.apache.org/viewvc/geronimo/plugins/spring/trunk/ modules/spring-deployer-service/pom.xml?view=autorev=463024 == --- geronimo/plugins/spring/trunk/modules/spring-deployer-service/ pom.xml (added) +++ geronimo/plugins/spring/trunk/modules/spring-deployer-service/ pom.xml Wed Oct 11 15:55:25 2006 @@ -0,0 +1,142 @@ +project +xmlns=http://maven.apache.org/POM/4.0.0; +xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; +xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http:// maven.apache.org/maven-v4_0_0.xsd + +modelVersion4.0.0/modelVersion + +parent +groupIdorg.apache.geronimo.plugins/groupId +artifactIdspring-parent/artifactId +version1.0-SNAPSHOT/version +relativePath../../pom.xml/relativePath +/parent + +artifactIdspring-deployer-service/artifactId +nameGeronimo Spring Deployer/name + +build +plugins +!-- TODO +plugin +groupIdorg.codehaus.mojo/groupId +artifactIdxmlbeans-maven-plugin/artifactId +version2.0.1-SNAPSHOT/version +executions +execution +goals +goalxmlbeans/goal +/goals +/execution +/executions +configuration +downloadtrue/download +sourceSchemasgeronimo-spring-1.0.xsd/ sourceSchemas +schemaDirectorysrc/schema/schemaDirectory +xmlConfigs +xmlConfig implementation=java.io.Filesrc/schema/xmlconfig.xml/xmlConfig +/xmlConfigs +/configuration +/plugin +-- +/plugins +sourceDirectorysrc/java/sourceDirectory +testSourceDirectorysrc/test/testSourceDirectory +resources +resource +directorysrc/resources/directory +filteringtrue/filtering +/resource +/resources +testResources +testResource +directorysrc/test-resources/directory +/testResource +/testResources +/build + +dependencies +dependency +groupIdgplugins/groupId +artifactIdcommon/artifactId +/dependency + +dependency +groupIdorg.apache.geronimo.plugins/groupId +artifactIdspring-integration-service/artifactId +/dependency + +dependency +groupIdxmlbeans/groupId +artifactIdxbean/artifactId +/dependency + +dependency +groupIdstax/groupId +artifactIdstax-api/artifactId +/dependency + +dependency +groupIdgeronimo/groupId +artifactIdgeronimo-kernel/artifactId +/dependency + +dependency +groupIdgeronimo/groupId +artifactIdgeronimo-deployment/artifactId +/dependency + +
Re: [jira] Created: (GERONIMO-2482) Remove console JARs from WEB-INF/lib
On Oct 11, 2006, at 2:30 PM, Jason Dillon wrote: I'm just warning that unless those issues are actually fixed in that version that there is going to be a bunch of work needed to properly sort out jira when it comes release time. I would think that when we are considering whether it's time for a release a report of issues marked to be fixed in a particular version yet still open would be pretty useful. I thought we had these for just about all previous releases. Certainly previous release managers have reset all open issues marked for a particular release to the next version when no one volunteered to fix them. thanks david jencks --jason On Oct 10, 2006, at 1:51 PM, Aaron Mulder wrote: Isn't the point of a road map to show what's coming / targeted for each release? Otherwise, it's release notes, not a road map. I feel pretty strongly that we should have some way for Jira to present a list of the issues targeted to be included in each release. Do you have an alternative to the road map to suggest? Thanks, Aaron On 10/10/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not about what version you believe it should be fixed in... fixed versions is for what version it was actually fixed in. This value is used to generate the change log in the roadmap and if the issue is not actually fixed in that version it just pollutes the details that jira shows us. For example, if this issue is not actually fixed in 1.1.2, but instead fixed in 1.1.3, then there is some confusion when inspecting the roadmap for what was fixed where. --jason On Oct 10, 2006, at 1:33 PM, Aaron Mulder wrote: How else can we track what versions we believe it should be fixed in? I don't know how else I'd find issues to fix in 1.1.2 out of the 500+ open issues. Thanks, Aaorn On 10/10/06, Jason Dillon [EMAIL PROTECTED] wrote: Its not a good idea to set the fix for version when creating an issue. This should be set when closing the issue. --jason On Oct 10, 2006, at 1:17 PM, Aaron Mulder (JIRA) wrote: Remove console JARs from WEB-INF/lib Key: GERONIMO-2482 URL: http://issues.apache.org/jira/browse/ GERONIMO-2482 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 1.1.1 Reporter: Aaron Mulder Fix For: 1.1.2, 1.2 It's unnecessarily hard to build console extension plugins because the car-maven-plugin can't access JARs in a WEB-INF/lib directory. The console web apps should not package any JARs, but instead use dependency elements to add them to the class path. (e.g. console- framework packages castor) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/ software/jira
[jira] Created: (GERONIMO-2486) All plans should use 1.2 namespace
All plans should use 1.2 namespace -- Key: GERONIMO-2486 URL: http://issues.apache.org/jira/browse/GERONIMO-2486 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 1.2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Anita Kulshreshtha Priority: Minor The plans are still using 1.1 namespace. Here is an example: module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.1; gbean name=WebServiceBuilder class=org.apache.geronimo.axis.builder.AxisBuilder/ gbean name=AxisServiceRefBuilder class=org.apache.geronimo.axis.builder.AxisServiceRefBuilder attribute name=eeNamespaceshttp://java.sun.com/xml/ns/j2ee/attribute xml-attribute name=defaultEnvironment environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.1; All plans must be updated to use 1.2 namespace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Spring in Geronimo 1.1.1
I thought we had gotten rid of this but... It looks like in Geronimo 1.1.1, the Jetty server configuration includes Spring 1.2.5 on its class path. Unfortunately, this means that no web application can use any other version of Spring that it inherits from a class path parent. It can package its own Spring, but not, for example, use Spring 2.0 classes configured in a parent module (e.g. to share common Spring classes or services packaged in a parent module). Let's say we were going to release a 1.1.2 and we were going to drop WADI, Spring, and ActiveCluster from the Jetty module in that release... Would that break anybody's heart? Thanks, Aaron geronimo/jetty/1.1.1/car - repository/geronimo/geronimo-jetty/1.1.1/geronimo-jetty-1.1.1.jar repository/jetty/org.mortbay.jetty/5.1.10/org.mortbay.jetty-5.1.10.jar repository/tomcat/jasper-compiler/5.5.15/jasper-compiler-5.5.15.jar repository/tomcat/jasper-compiler-jdt/5.5.15/jasper-compiler-jdt-5.5.15.jar repository/tomcat/jasper-runtime/5.5.15/jasper-runtime-5.5.15.jar repository/commons-el/commons-el/1.0/commons-el-1.0.jar repository/springframework/spring/1.2.5/spring-1.2.5.jar repository/activecluster/activecluster/1.2-20051115174934/activecluster-1.2-20051115174934.jar repository/wadi/wadi-core/2.0M1/wadi-core-2.0M1.jar repository/wadi/wadi-jetty5/2.0M1/wadi-jetty5-2.0M1.jar
[jira] Created: (GERONIMO-2487) Spring should not be on class path of Jetty (and therefore all Jetty web apps)
Spring should not be on class path of Jetty (and therefore all Jetty web apps) -- Key: GERONIMO-2487 URL: http://issues.apache.org/jira/browse/GERONIMO-2487 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Jetty Affects Versions: 1.1.1 Reporter: Aaron Mulder Fix For: 1.1.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Geronimo integration steps
I'm trying to figure out all the steps necessary to integrate a new component/service into Geronimo. Do these high-level tasks below seem generally accurate ?? And most importantly what else am I missing ?? Thanks much for reviewing. Tim 1. Implement a GBean to represent the deployed component with appropriate: a. Constructor b. Attributes c. References d. Operations e. Interfaces 2. Create the XML Plan with the appropriate deployment descriptors 3. Create the appropriate configuration file(s) 4. Implement a Module to contain the GBean 5. Implement the class loader for the Module 6. Create/implement any/all appropriate dependencies 7. Create the POM XML file(s) for integration into existing maven build 8. Test all assemblies (that contain the new component/service) 9. Others ??
Re: Spring in Geronimo 1.1.1
On 12/10/2006, at 12:20 PM, Aaron Mulder wrote: I thought we had gotten rid of this but... snip Let's say we were going to release a 1.1.2 and we were going to drop WADI, Spring, and ActiveCluster from the Jetty module in that release... Would that break anybody's heart? Not mine :) Thanks, Gianny
[jira] Assigned: (AMQ-970) Compiling fails under SuSe
[ https://issues.apache.org/activemq/browse/AMQ-970?page=all ] Timothy Bish reassigned AMQ-970: Assignee: Timothy Bish Compiling fails under SuSe -- Key: AMQ-970 URL: https://issues.apache.org/activemq/browse/AMQ-970 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Environment: gcc (GCC) 3.3.3 (SuSE Linux) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking build system type... x86_64-suse-linux checking host system type... x86_64-suse-linux checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking whether build environment is
[jira] Work started: (AMQ-970) Compiling fails under SuSe
[ https://issues.apache.org/activemq/browse/AMQ-970?page=all ] Work on AMQ-970 started by Timothy Bish. Compiling fails under SuSe -- Key: AMQ-970 URL: https://issues.apache.org/activemq/browse/AMQ-970 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Environment: gcc (GCC) 3.3.3 (SuSE Linux) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking build system type... x86_64-suse-linux checking host system type... x86_64-suse-linux checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking whether build environment is sane... yes checking whether byte ordering is
[jira] Resolved: (AMQ-970) Compiling fails under SuSe
[ https://issues.apache.org/activemq/browse/AMQ-970?page=all ] Timothy Bish resolved AMQ-970. -- Resolution: Fixed Removed the openwire compilation from the makefile, as this wasn;t supposed to be in yet, my bad on that one. We are phasing out the use of these makefiles though, so instead you should use the autogen.sh and then ./configure to create the automake Makefiles. This should result in a better build experience. Once we are done testing the new make system the old makefiles will be removed, so its a good idea to start using the new ones now. See the Readme.txt for details. Compiling fails under SuSe -- Key: AMQ-970 URL: https://issues.apache.org/activemq/browse/AMQ-970 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Environment: gcc (GCC) 3.3.3 (SuSE Linux) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking build system type... x86_64-suse-linux checking host system type... x86_64-suse-linux checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64 checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes
[Help] mvn error in Examples
Hi All, I followed the User's Guide to deploy the exmaples, but some BUILD ERROR interrupted me. Any help would be appreciated. More information : Step 1. download and installed maven-2.0.4 Step 2. Maven configuration Step 2. bin/servicemix Step 3. cd [servicemix_install_dir]/examples/wsdl-first , then type mvn install. The logs at console below: [INFO] Scanning for projects... Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/s ervicemix/samples/3.0-incubating/samples-3.0-incubating.pom 1K downloaded Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/s ervicemix/servicemix/3.0-incubating/servicemix-3.0-incubating.pom 59K downloaded Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/a pache/1/apache-1.pom [WARNING] Unable to get resource from repository apache-incubating (http://peopl e.apache.org/repo/m2-incubating-repository) Downloading: http://people.apache.org/maven-snapshot-repository/org/apache/apach e/1/apache-1.pom [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/maven-snapshot-repository) Downloading: http://www.ibiblio.org/maven2/org/apache/apache/1/apache-1.pom 3K downloaded [INFO] Reactor build order: [INFO] ServiceMix :: Samples :: WSDL first [INFO] ServiceMix :: Samples :: WSDL first :: JSR181 [INFO] ServiceMix :: Samples :: WSDL first :: HTTP [INFO] ServiceMix :: Samples :: WSDL first :: SA Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/tooling/jbi-mav en-plugin/3.0-incubating/jbi-maven-plugin-3.0-incubating.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org /maven2) Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/s ervicemix/tooling/jbi-maven-plugin/3.0-incubating/jbi-maven-plugin-3.0-incubatin g.pom 3K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/tooling/tooling /3.0-incubating/tooling-3.0-incubating.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org /maven2) Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/s ervicemix/tooling/tooling/3.0-incubating/tooling-3.0-incubating.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/servicemix/tooling/jbi-mav en-plugin/3.0-incubating/jbi-maven-plugin-3.0-incubating.jar [WARNING] Unable to get resource from repository central (http://repo1.maven.org /maven2) [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Plugin could not be found - check that the goal name is correct: Unable t o download the artifact from any repository org.apache.servicemix.tooling:jbi-maven-plugin:3.0-incubating:maven-plugin from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.servicemix.tooling:jbi-maven-plugin:3.0-incubating:maven-plugin from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: 14 seconds [INFO] Finished at: Thu Oct 12 10:45:13 CST 2006 [INFO] Final Memory: 2M/4M [INFO] - --- -- View this message in context: http://www.nabble.com/-Help--%22mvn%22-error-in-Examples-tf2427800.html#a6769269 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Assigned: (GERONIMO-2471) JMX Portlet doesn't display all the attributes of a web module
[ http://issues.apache.org/jira/browse/GERONIMO-2471?page=all ] Anita Kulshreshtha reassigned GERONIMO-2471: Assignee: Anita Kulshreshtha (was: Christopher M. Cardona) JMX Portlet doesn't display all the attributes of a web module -- Key: GERONIMO-2471 URL: http://issues.apache.org/jira/browse/GERONIMO-2471 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Reporter: Christopher M. Cardona Assigned To: Anita Kulshreshtha Fix For: 1.2 Attachments: GERONIMO-2471_2472-trunk.patch Viewing a web module doesn't display all its attributes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-2472) Remove the display of GBeanInfo attribute in the JMX portlet
[ http://issues.apache.org/jira/browse/GERONIMO-2472?page=all ] Anita Kulshreshtha reassigned GERONIMO-2472: Assignee: Anita Kulshreshtha (was: Christopher M. Cardona) Remove the display of GBeanInfo attribute in the JMX portlet Key: GERONIMO-2472 URL: http://issues.apache.org/jira/browse/GERONIMO-2472 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 1.2 Reporter: Christopher M. Cardona Assigned To: Anita Kulshreshtha Priority: Minor Fix For: 1.2 Attachments: GERONIMO-2471_2472-trunk.patch When viewing MBean's attributes in the JMX portlet we should exclude GBeanInfo attributes. This was suggested in the devlist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[STATUS] (geronimo) Wed Oct 11 23:49:08 2006
APACHE GERONIMO STATUS: -*-text-*- Last modified at [$Date: 2006-10-07 05:14:55 -0400 (Sat, 07 Oct 2006) $] The current version of this file can be found at: * http://svn.apache.org/repos/asf/geronimo/server/trunk/STATUS Upcoming Releases: Geronimo 1.2 -- geronimo/server/trunk/ Release Manager: Dain Sundstrom and Alan Cabrera Estimated Date: Q4 2006 RELEASE SHOWSTOPPERS: Certification - Historically certification has been the most time consuming portion of a release, and there is no reason to expect it to be any different for this release. To make matters worse, the certification test suite has not been run in several months while major changes have been made to EJB, Transaction, Connector and Servlet Session. Features - The scope for the 1.2 release is currently being finalized. We have collected a list of 14 features to be included in the release and are working on prioritizing the list. The prioritized list will help guide us in determining when to release based on the number of completed high priority features. Dead 1.2 - There are still 37 unmerged commits the dead 1.2 branch. These commits must be merged before the 1.2 release. The current status of the dead-1.2 changes can be found at http://svn.apache.org/repos/asf/geronimo/server/trunk/all_changes.log Specs - There are two proposals for versioning specification jars in Geronimo. The first uses a single version number for all specifications. The makes releasing new versions of specifications easy for the Geronimo committers as only a single file must be updated. Alternatively, each specification could have an independent version number. With this approach several files may have to be updated to release a jar, but this approach reduces the number of jars that are released with no changes. This issue is in active discussion and will hopefully be resolved quickly. Outstanding patches awaiting votes: On JIRA, the following patches are oustanding: GERONIMO-1277 Change group-id to org.apache.geronimo Status: New proposal by Jason Dillon to change base the groupId to org.apache.geronimo.server GERONIMO-2015 Let's replace JKS to PKCS12 key store type - Opened Status: No active discussion GERONIMO-2409 Provide config/module aliasing ability Status: 3 +1 votes GERONIMO-2413 Add a Certification Authority (CA) portlet to Geronimo console Status: Not reviewed Release history: 2006-09-18 Geronimo 1.1.1 2006-06-26 Geronimo 1.1 2006-01-05 Geronimo 1.0 2005-10-04 Geronimo 1.0 milestone 5 2005-08-10 Geronimo 1.0 milestone 4 2004-11-11 Geronimo 1.0 milestone 3 2004-09-09 Geronimo 1.0 milestone 2 2004-04-29 Geronimo 1.0 milestone 1 If you're a contributor looking for something to do: * Review the documentation and suggest improvements * Review the bug list and suggest fixes or report reproducibility * Report bugs yourself
Re: Spring in Geronimo 1.1.1
On 10/12/06, Aaron Mulder [EMAIL PROTECTED] wrote: I thought we had gotten rid of this but... It looks like in Geronimo 1.1.1, the Jetty server configuration includes Spring 1.2.5 on its class path. Unfortunately, this means that no web application can use any other version of Spring that it inherits from a class path parent. It can package its own Spring, but not, for example, use Spring 2.0 classes configured in a parent module (e.g. to share common Spring classes or services packaged in a parent module). Let's say we were going to release a 1.1.2 and we were going to drop WADI, Spring, and ActiveCluster from the Jetty module in that release... Would that break anybody's heart? Not mine, either. The less dependencies of Geronimo falls on a application developer's shoulders, the better. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r463024 - in /geronimo/plugins/spring: branches/ tags/ trunk/ trunk/modules/ trunk/modules/spring-deployer-service/ trunk/modules/spring-deployer-service/src/ trunk/modules/spring-depl
On 10/12/06, Jason Dillon [EMAIL PROTECTED] wrote: I'd avoid making new projects that have a modules/* Just organize your modules in the root, or make modules to organize them into meaningful groups. I didn't get it. Could you show an example of it? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
