[jira] Assigned: (SM-1069) JAX-WS support
[ https://issues.apache.org/activemq/browse/SM-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned SM-1069: Assignee: Freeman Fang JAX-WS support -- Key: SM-1069 URL: https://issues.apache.org/activemq/browse/SM-1069 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Assignee: Freeman Fang Fix For: 4.0 It should be easy to expose a JAX-WS annotated bean on the bus, or even outside using http/soap ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-926) Add a standard JBI component for Velocity templates
[ https://issues.apache.org/activemq/browse/SM-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-926: --- Fix Version/s: (was: 3.2) Add a standard JBI component for Velocity templates --- Key: SM-926 URL: https://issues.apache.org/activemq/browse/SM-926 Project: ServiceMix Issue Type: New Feature Reporter: Jeff Puro Assignee: Jeff Puro Priority: Minor Original Estimate: 2 days Remaining Estimate: 2 days I think it would be useful for ServiceMix to provide a velocity template service engine. This would serve as an alternative to using XSLT to tranform messages and could be particularly useful when creating the content of an email message etc. The way it would work, in conjunction with JDOM, is that a normalized message would be sent to the component that would inject the properties and the content of the message into the Velocity context. You can then use Velocity's syntax for generating XML documents or any content that has CDATA tags around it. The properties of the normalized message would be accessed via the $properties variable, whereas the content of the message would be accessed via either a $content or $root variable using JDOM methods. Since it is often nice to have Velocity templates pulled from sources other than a .vm file (for example a database), it would be useful for the velocity:endpoint/ to have a pluggable resource property where the resource could be pulled from either the filesystem, a database, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-679) Create a servicemix-ehcache standard JBI component
[ https://issues.apache.org/activemq/browse/SM-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-679: --- Fix Version/s: (was: 3.2) Create a servicemix-ehcache standard JBI component -- Key: SM-679 URL: https://issues.apache.org/activemq/browse/SM-679 Project: ServiceMix Issue Type: New Feature Components: servicemix-components Affects Versions: 3.0 Reporter: Jeff Puro Assignee: Jeff Puro Priority: Minor Attachments: servicemix-ehcache.patch Add a servicemix-ehcache standard JBI component. Please see the following forum thread for more information on how this component should work. http://www.nabble.com/Ehcache-Standard-JBI-Component-tf2747953s12049.html#a7666554 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-848) ServiceMix 3.x with Java 1.4.x
[ https://issues.apache.org/activemq/browse/SM-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-848: --- Fix Version/s: (was: 3.2) 3.1.3 ServiceMix 3.x with Java 1.4.x -- Key: SM-848 URL: https://issues.apache.org/activemq/browse/SM-848 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: Java Runtime Environment 1.4.x Reporter: Juergen Mayrbaeurl Fix For: 3.1.3 Since ServiceMix 3.1 can only be used with Java 5 or higher, rework it to make it Java 1.4.x compatible -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-750) ClientFactory should implement java.io.Serializable
[ https://issues.apache.org/activemq/browse/SM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40194 ] Guillaume Nodet commented on SM-750: Did you find a solution for that ? ClientFactory should implement java.io.Serializable --- Key: SM-750 URL: https://issues.apache.org/activemq/browse/SM-750 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: All, especially when running under the JBoss Deployer Reporter: Martin Landua Priority: Minor Fix For: 3.2 The object ClientFactory should implement the interface java.io.Serializable. Otherwise, the JBoss Deployer throws an error when trying to register the object in the JBoss JNDI directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
XMLStreamException processing request
Hi, We are getting the error below for every request. Response is coming back after having couple of errors like this. Any idea where this is coming from? We are using Jetty6.1.3 in the HTTP BC. Even with Jetty6.0.1 also we have same problem. It looks like it's a problem with Continuation. Is there any way we can disable continuation? javax.xml.stream.XMLStreamException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:469) at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.java:22 9) at org.apache.servicemix.jbi.jaxp.XMLStreamHelper.writeStartElement(XMLStreamHe lper.java:169) at org.apache.servicemix.jbi.jaxp.XMLStreamHelper.copy(XMLStreamHelper.java:59) at org.apache.servicemix.soap.marshalers.SoapWriter.writeContents(SoapWriter.ja va:198) at org.apache.servicemix.soap.marshalers.SoapWriter.writeSoapEnvelope(SoapWrite r.java:190) at org.apache.servicemix.soap.marshalers.SoapWriter.writeSimpleMessage(SoapWrit er.java:99) at org.apache.servicemix.soap.marshalers.SoapWriter.write(SoapWriter.java:82) at org.apache.servicemix.http.processors.ConsumerProcessor.processResponse(Cons umerProcessor.java:223) at org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProc essor.java:204) at org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:7 1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl ection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11 4) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:372) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368) at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectCha nnelConnector.java:489) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:4 42)
Re: integration testing in spring
BTW I've added an integration test for the bridge sample... http://svn.apache.org/repos/asf/incubator/servicemix/trunk/samples/bridge/bridge-sa-itest/ which from a single spring XML boots up an ActiveMQ broker, ServiceMix with some components and the SA and then Camel to do some integration testing (though I've not yet completed the Camel stuff to fire messages into the bridge then do some Mock endpoint testing to ensure things work as expected). On 25/09/2007, James Strachan [EMAIL PROTECTED] wrote: I've taken a first stab at adding an easy way of integration testing JBI artifacts (shared libraries, components and service assemblies) using a simple Spring XML notation that can be included into any JUnit test case... http://cwiki.apache.org/SM/integration-testing-in-spring.html This allows you to depend on artifacts using their maven groupId and artifactId and then the version is inferred (using the generated META-INF/maven/dependencies.properties via the jbi-maven-plugin). My idea was to show how we can boot up servicemix with some artifacts from the local repo, then use Camel to fire in messages and make assertions and so forth to test that the JBI artifacts actually deploy correctly and do what is expected etc. Feedback most appreciated if this can be improved... -- James --- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com -- James --- http://macstrac.blogspot.com/ Open Source SOA http://open.iona.com
[jira] Resolved: (SM-750) ClientFactory should implement java.io.Serializable
[ https://issues.apache.org/activemq/browse/SM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-750. Resolution: Fixed Assignee: Guillaume Nodet Closing this issue. Please open another one if there are still problems. ClientFactory should implement java.io.Serializable --- Key: SM-750 URL: https://issues.apache.org/activemq/browse/SM-750 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: All, especially when running under the JBoss Deployer Reporter: Martin Landua Assignee: Guillaume Nodet Priority: Minor Fix For: 3.2 The object ClientFactory should implement the interface java.io.Serializable. Otherwise, the JBoss Deployer throws an error when trying to register the object in the JBoss JNDI directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1011) WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions properly
[ https://issues.apache.org/activemq/browse/SM-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1011. - Resolution: Fixed Fix Version/s: 3.1.3 Assignee: Guillaume Nodet Thx a lot for this patch ! Sending servicemix-common/src/main/java/org/apache/servicemix/common/tools/wsdl/SchemaCollection.java Sending servicemix-common/src/test/java/org/apache/servicemix/common/tools/wsdl/WSDLFlattenerTest.java Adding servicemix-common/src/test/resources/includes Adding servicemix-common/src/test/resources/includes/nested-a1.xsd Adding servicemix-common/src/test/resources/includes/nested-b1.xsd Adding servicemix-common/src/test/resources/includes/nested-b2.xsd Adding servicemix-common/src/test/resources/includes/nested-b3.xsd Adding servicemix-common/src/test/resources/includes/nested-c1.xsd Adding servicemix-common/src/test/resources/includes/service.wsdl Transmitting file data Committed revision 580017. Sending servicemix-common/src/main/java/org/apache/servicemix/common/tools/wsdl/SchemaCollection.java Sending servicemix-common/src/test/java/org/apache/servicemix/common/tools/wsdl/WSDLFlattenerTest.java Adding servicemix-common/src/test/resources/includes Adding servicemix-common/src/test/resources/includes/nested-a1.xsd Adding servicemix-common/src/test/resources/includes/nested-b1.xsd Adding servicemix-common/src/test/resources/includes/nested-b2.xsd Adding servicemix-common/src/test/resources/includes/nested-b3.xsd Adding servicemix-common/src/test/resources/includes/nested-c1.xsd Adding servicemix-common/src/test/resources/includes/service.wsdl Transmitting file data .. Committed revision 580018. WSDLFlattenner / SchemaCollection do not handle nested schemas inclusions properly -- Key: SM-1011 URL: https://issues.apache.org/activemq/browse/SM-1011 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1.1 Environment: Windows XP Reporter: Konrad Argasinski Assignee: Guillaume Nodet Fix For: 3.1.3, 3.2 Attachments: nested schemas.txt, nested-schemas-reproduced-sm.zip WSDLFlattener fails to analyse JSR-181 SU WSDL which imports multi-level (nested) schemas structure. My JSR-181 SU WSDL imports A1.xsd schema. A1.xsd includes B1.xsd, B2.xsd and B3.xsd. B1.xsd includes C1.xsd. The schema is used by JAXB during the project build and it works ok, however when the SU gets deployed on ServiceMix I receive following error: loc-messageNOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist./loc-message stack-trace![CDATA[org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist. at org.apache.xerces.dom.ParentNode.internalRemoveChild(Unknown Source) at org.apache.xerces.dom.ParentNode.removeChild(Unknown Source) at org.apache.servicemix.common.tools.wsdl.SchemaCollection.handleImports(SchemaCollection.java:150) The full stack trace is attached. As workaround I compiled my custom SchemaCollection and it works ok now, however I think a better fix is needed. My custom changes in org.apache.servicemix.common.tools.wsdl.SchemaCollection are: around line 149 I have replaced: String location = ce.getAttribute(schemaLocation); schema.getRoot().removeChild(ce); with: String location = ce.getAttribute(schemaLocation); Node parentNode = ce.getParentNode(); Element root = schema.getRoot(); if (root == parentNode) { log.debug(Removing child include node: + ce); schema.getRoot().removeChild(ce); } else { log.warn(Skipping child include node removal: + ce); } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-855) Non concurrent processing of files in LW FilePoller
[ https://issues.apache.org/activemq/browse/SM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-855: --- Fix Version/s: (was: 3.2) Unscheduling this issue until a correct patch is provided Non concurrent processing of files in LW FilePoller --- Key: SM-855 URL: https://issues.apache.org/activemq/browse/SM-855 Project: ServiceMix Issue Type: Improvement Components: servicemix-components Affects Versions: 3.1 Reporter: Juergen Mayrbaeurl Attachments: FilePoller.diff, FilePoller.diff LW FilePoller component always processes files concurrently. Sometimes it's very important that files get processed in a defined sequence, because the contents is depending on previously processed contents. I've extended the LW FilePoller class. It has a 'concurrent' property now (default is true) and properties for sorting the incoming files (Sort by name and last modification date, asc and desc) Maybe this functionality should be included in the LW FTP FilePoller and servicemix-file BC, too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Scheduling 3.2 release
I'm going through the remaining JIRA assigned for 3.2. If anybody has any important issues to schedule there (or patches to apply), please yell ! I'd like to put 3.2 in release mode asap. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Resolved: (SM-981) Transaction Exception due to ServiceMix JMS Provider
[ https://issues.apache.org/activemq/browse/SM-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-981. Resolution: Fixed Fix Version/s: 3.1.3 Assignee: Guillaume Nodet Thanks a lot for this patch! Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java Transmitting file data . Committed revision 580020. Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java Transmitting file data . Committed revision 580023. Transaction Exception due to ServiceMix JMS Provider Key: SM-981 URL: https://issues.apache.org/activemq/browse/SM-981 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.1 Environment: All platforms. The bug was encountered on ServiceMix 3.1 running in JBoss against JBossMQ. Reporter: Martin Landua Assignee: Guillaume Nodet Fix For: 3.1.3, 3.2 Attachments: servicemix-jms.patch Hi all, under heavy load, we have encountered a problem when writing messages using the JMS provider in a synchronous, transactional flow. The problem is that in the code (lines 100 and up) producer.send(msg); exchange.setStatus(ExchangeStatus.DONE); channel.send(exchange); } finally { if (session != null) { session.close(); } if (connection != null) { connection.close(); } } it is possible that the DONE state would return to the originator faster than the session and the connection is closed in the finally section. If this happens, the originator (and therefore owner of the transaction) will first commit and after this the provider would close the connection. This results in a transaction exception. From what we can tell, it should read like this: producer.send(msg); } finally { if (session != null) { session.close(); } if (connection != null) { connection.close(); } } exchange.setStatus(ExchangeStatus.DONE); channel.send(exchange); due to which we guarantee that the connection is safely closed before we send the confirmation back to the consumer. All of our load tests succeeded after this change. Best regards Martin Landua -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown
[ https://issues.apache.org/activemq/browse/SM-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-998. Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this great patch! Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/AbstractJmsProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsEndpoint.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/multiplexing/MultiplexingProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java Transmitting file data Committed revision 580043. In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown --- Key: SM-998 URL: https://issues.apache.org/activemq/browse/SM-998 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.2 Environment: any Reporter: Sam Gerstein Assignee: Guillaume Nodet Fix For: 3.2 Attachments: servicemix-jms_patch.txt Original Estimate: 0 minutes Remaining Estimate: 0 minutes Because a temporary queue is used for the reply-to destination and the Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS queue cannot be returned to their sender after a crash or shutdown of ServiceMix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1054) Port JmsMarshaler from lightweight jms component to servicemix-jms component
[ https://issues.apache.org/activemq/browse/SM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1054: Patch Info: [Patch Available] Port JmsMarshaler from lightweight jms component to servicemix-jms component - Key: SM-1054 URL: https://issues.apache.org/activemq/browse/SM-1054 Project: ServiceMix Issue Type: Improvement Components: servicemix-jms Affects Versions: 3.1.1 Reporter: Jeff Peterson Fix For: 3.2 Attachments: SM-1054.patch Many legacy JMS systems have non-xml messages (e.g. ObjectMessage) floating around on their queues and topics. The servicemix-jms component needs a way to marshall those jms messages to normalized messages. The lightweight jms component currently has a marshaller layer to perform these actions. Please port it to the servicemix-jms component. See: http://www.nabble.com/MapMessage-and-or-ObjectMessage-tf2226788s12049.html#a6188688 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1054) Port JmsMarshaler from lightweight jms component to servicemix-jms component
[ https://issues.apache.org/activemq/browse/SM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1054. - Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this patch! Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/AbstractJmsProcessor.java Adding servicemix-jms/src/main/java/org/apache/servicemix/jms/DefaultJmsMarshaler.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsEndpoint.java Adding servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsMarshaler.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/multiplexing/MultiplexingProviderProcessor.java Sending servicemix-jms/src/main/java/org/apache/servicemix/jms/standard/StandardProviderProcessor.java Adding servicemix-jms/src/test/java/org/apache/servicemix/jms/JmsMarshalerTest.java Transmitting file data Committed revision 580069. Port JmsMarshaler from lightweight jms component to servicemix-jms component - Key: SM-1054 URL: https://issues.apache.org/activemq/browse/SM-1054 Project: ServiceMix Issue Type: Improvement Components: servicemix-jms Affects Versions: 3.1.1 Reporter: Jeff Peterson Assignee: Guillaume Nodet Fix For: 3.2 Attachments: SM-1054.patch Many legacy JMS systems have non-xml messages (e.g. ObjectMessage) floating around on their queues and topics. The servicemix-jms component needs a way to marshall those jms messages to normalized messages. The lightweight jms component currently has a marshaller layer to perform these actions. Please port it to the servicemix-jms component. See: http://www.nabble.com/MapMessage-and-or-ObjectMessage-tf2226788s12049.html#a6188688 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-930) ComponentListener does not get notified on Component uninstall
[ https://issues.apache.org/activemq/browse/SM-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-930. Resolution: Fixed Assignee: Guillaume Nodet Thx a lot for this patch! Sending servicemix-core/src/main/java/org/apache/servicemix/jbi/framework/ComponentMBeanImpl.java Transmitting file data . Committed revision 580070. ComponentListener does not get notified on Component uninstall -- Key: SM-930 URL: https://issues.apache.org/activemq/browse/SM-930 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Environment: Ubuntu-64, Java 1.5_06, ServiceMix-3.1-incubating Reporter: Corey Baswell Assignee: Guillaume Nodet Priority: Minor Fix For: 3.2 Attachments: patch.txt The org.apache.servicemix.jbi.event.ComponentListener does not get notified when a component in the JBI container is uninstalled: public void componentUninstalled(ComponentEvent event); I attached a patch for how i got it working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-575) servicemix-common base classes are not designed to support persistent deployments
[ https://issues.apache.org/activemq/browse/SM-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-575: --- Fix Version/s: (was: 3.2) servicemix-common base classes are not designed to support persistent deployments - Key: SM-575 URL: https://issues.apache.org/activemq/browse/SM-575 Project: ServiceMix Issue Type: Improvement Components: servicemix-common Affects Versions: 3.0 Reporter: Guillaume Nodet The Deployer and BaseServiceUnitManager should be enhanced for that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-2) component for ActiveSOAP
[ https://issues.apache.org/activemq/browse/SM-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-2. Resolution: Won't Fix component for ActiveSOAP Key: SM-2 URL: https://issues.apache.org/activemq/browse/SM-2 Project: ServiceMix Issue Type: New Feature Reporter: James Strachan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-197) Eclipse Plugin to configure ServiceMix Integrations
[ https://issues.apache.org/activemq/browse/SM-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-197. -- Resolution: Won't Fix Cimero will be donated to Eclipse STP Eclipse Plugin to configure ServiceMix Integrations --- Key: SM-197 URL: https://issues.apache.org/activemq/browse/SM-197 Project: ServiceMix Issue Type: Wish Reporter: George Gastaldi Develop an eclipse plugin that could allow editing of the servicemix configuration file and visual representation of the flow. Please add comments regarding to the scope of this plug-in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-50) make a standard JBI component example
[ https://issues.apache.org/activemq/browse/SM-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-50. - Resolution: Fixed Done a long time ago make a standard JBI component example - Key: SM-50 URL: https://issues.apache.org/activemq/browse/SM-50 Project: ServiceMix Issue Type: New Feature Reporter: James Strachan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-157) Create a Transformation Service Engine
[ https://issues.apache.org/activemq/browse/SM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed SM-157. -- Resolution: Fixed Done with saxon Create a Transformation Service Engine -- Key: SM-157 URL: https://issues.apache.org/activemq/browse/SM-157 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Standard JBI Service Engine. Handle XSLT, XQuery with saxon. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-1037. - Resolution: Fixed Fix Version/s: 3.2 Assignee: Guillaume Nodet Hi Kristian, thx a lot for this patch. and keep up the good work :-) Sendinggeronimo/deployer/pom.xml Sendinggeronimo/deployer/src/plan/geronimo-service.xml Sendinggeronimo/deployer-service/pom.xml Sending geronimo/deployer-service/src/main/java/org/apache/servicemix/geronimo/ServiceMixConfigBuilder.java Sendinggeronimo/geronimo-plugins.xml Sendinggeronimo/pom.xml Sendinggeronimo/servicemix/pom.xml Sendinggeronimo/servicemix/src/plan/geronimo-service.xml Sendinggeronimo/servicemix-service/pom.xml Sending geronimo/servicemix-service/src/main/java/org/apache/servicemix/geronimo/ServiceMixGBean.java Transmitting file data .. Committed revision 580072. Geronimo Plugin enhancement and bug fix --- Key: SM-1037 URL: https://issues.apache.org/activemq/browse/SM-1037 Project: ServiceMix Issue Type: Bug Reporter: Kristian Koehler Assignee: Guillaume Nodet Fix For: 3.2 Attachments: geronimo-plugin.patch, geronimo-plugin.patch, geronimo-plugin.patch-03, geronimo-plugin.patch-04 Hi i encountered some problems with the Geronimo Plugin for ServiceMix. I updated the version in trunk to use Geronimo 2.0.1 and fixed a deployment bug. With the current version it's not possible to deploy service assemblies which require a deployment to a service unit. For example if you deploy JBI ODE BPEL engine package via the JBI deployment mechanism to geronimo you are not able to deploy a service unit using this BPEL engine. The deployment ends up in jbi out of sync exceptions because the service assembly must also be deployt to the service assembly! The attached patch fixes the Deployer and some ServiceMix Service problems. Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1037: Component/s: geronimo Geronimo Plugin enhancement and bug fix --- Key: SM-1037 URL: https://issues.apache.org/activemq/browse/SM-1037 Project: ServiceMix Issue Type: Bug Components: geronimo Reporter: Kristian Koehler Assignee: Guillaume Nodet Fix For: 3.2 Attachments: geronimo-plugin.patch, geronimo-plugin.patch, geronimo-plugin.patch-03, geronimo-plugin.patch-04 Hi i encountered some problems with the Geronimo Plugin for ServiceMix. I updated the version in trunk to use Geronimo 2.0.1 and fixed a deployment bug. With the current version it's not possible to deploy service assemblies which require a deployment to a service unit. For example if you deploy JBI ODE BPEL engine package via the JBI deployment mechanism to geronimo you are not able to deploy a service unit using this BPEL engine. The deployment ends up in jbi out of sync exceptions because the service assembly must also be deployt to the service assembly! The attached patch fixes the Deployer and some ServiceMix Service problems. Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1081) A StaticRecipientListAggregator like SplitAggregator is needed
[ https://issues.apache.org/activemq/browse/SM-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1081: Fix Version/s: 3.2 A StaticRecipientListAggregator like SplitAggregator is needed --- Key: SM-1081 URL: https://issues.apache.org/activemq/browse/SM-1081 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Affects Versions: 3.1.1 Environment: ServiceMix 3.1.1 Reporter: Andrea Zoppello Fix For: 3.2 Attachments: RecipientListAggregator.java, SplitAggregator.java.patch, StaticRecipientList.java.patch We need a specific aggregator to use in couple with a Static recipient List. To do this we need to: 1) Modify the static recipient list to propagate some information needed to be used by RecipientListAggregator 2) Implement the RecipientListAggregator class 3) With a small update to SplitAggregator class RecipientListAggregator could simply extend SplitAggregator to reuse the aggregation logic. The problem is that the Expression properties are private, so we need to change SplitAgggregator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530638 ] David Jencks commented on GERONIMO-3481: I didn't get a chance to try it but the -for-2.0.patch looks fine to me. Have you checked that the (2) hack is really necessary with (1)? The code in Configuration looked right to me for handling transitive deps but I might be missing something. Offline deployer throws BIND Exception when port 1099 is in use --- Key: GERONIMO-3481 URL: https://issues.apache.org/jira/browse/GERONIMO-3481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1, 2.0.x, 2.1 Environment: G 2.0.1 - Running multiple instances Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0.2, 2.0.x, 2.1 Attachments: GERONIMO-3481-1.patch, GERONIMO-3481-2.patch, GERONIMO-3481-2a.patch, GERONIMO-3481-3.patch, GERONIMO-3481-for-2.0.patch, GERONIMO-3481-weird.patch Offline deployer throws Bind Exception when port 1099 is in use. Here is a scenario steps in which the problem is experienced. 1. Extract G-2.0.1-Tomcat distro to C:\ 2. Create a dir myserver under C:\geronimo-j2ee-tomcat-2.0.1 and copy C:\geronimo-j2ee-tomcat-2.0.1\var to C:\geronimo-j2ee-tomcat-2.0.1\myserver\var (all sub-directories). 3. Edit C:\geronimo-j2ee-tomcat-2.0.1\myserver\var\config-substitutions.properties to set PortOffset=10. 4. Open a command window and start Geronimo. Since org.apache.geronimo.server.name is not set, this will start the default server instance. 5. Open a second command window, set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver. This will be command window to run the second server instance with name myserver 6. Run deploy.bat --offline list-modules. At step 6, I am getting a BIND Exception since port 1099 is in use (by the default server instance) and the offline deployer is attempting to start rmi naming on port 1099. Since, this deploy command is run against second server instance, I would expect that it uses the configuration properties of myserver in which case it should use port 1109 to start rmi-naming if at all there is a need. When port 1099 is not in use, the offline deployer works as expected by updating proper config.xml file when a configuration is deployed/undeployed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3489) Deployment problems caused by file deletion failures
[ https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530643 ] Shiva Kumar H R commented on GERONIMO-3489: --- Thanks Ted for raising this. I have hit this problem many a times when deploying from within Eclipse Plug-in. I use Windows XP + NTFS + Sun JDK 1.5.0_11. Deployment problems caused by file deletion failures Key: GERONIMO-3489 URL: https://issues.apache.org/jira/browse/GERONIMO-3489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Reporter: Ted Kirby Fix For: 2.0.2, 2.0.x, 2.1 File.delete() failures in IOUtil.recursiveDelete() are causing various deployment problems. I open this JIRA to discuss them to see how the server might better handle them. In all but one case, delete failures are not even noted with a log record! Deletion problems are seen in many environments and platforms, but they are persistently fatal when using a NFS file system for the repository. In investigating the problem, I have added code to recursiveDelete to retry the delete a few times if it fails. I added code to list directory contents if a directory delete failed, and saw a file named .nfs2bc4350053e in the directory. My first attempt at a bypass was to retry a failed delete 5 times, sleeping a second before each try. This did not work. I added a call to System.gc() before each sleep, and this got me passed the problem. Interestingly, two retries were required to get this to work. In another version, each retry was a second longer, and I printed all file names in a directory before trying the delete. This worked in most cases, but required the full 5 retries, so I suspect System.gc() would have time. System.runFinalization() would be something else to try. RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the failing end of the deletion problem, with the dreaded ConfigurationAlreadyExistsException(Configuration already exists: + configId)exception. I think this message is not good. It should really say directory already exists. If the file is not deleted on undeploy, this failure occurs on a subsequent deploy. What is really bad is if the user invokes a redeploy operation, and the file delete fails on the undeploy. It is important that undeploy not complete until the file goes away. From other environments, I am not convinced that all file handles and references, and particularly open streams, are being closed on some artifacts. This will cause the delete to fail. It may be that the gc() calls are cleaning these up, and allowing the deletes to work in my case above. Another option is that RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a ConfigurationAlreadyExistsException if the only problem is an empty directory structure exists. The next line creates the directory structure anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo box on Download page still says 1.1
Yes Hernan, let's create our own boxes. Found these useful tutorials upon Google search for software box: http://tutorialblog.org/create-a-software-box/ http://www.designtutorials.info/software-box-design/ Adobe Photoshop is used in both the tutorials. - Shiva On 9/26/07, Hernan Cunico [EMAIL PROTECTED] wrote: Shiva, The .psd you see there are the templates we used as guidelines long time ago then we overhauled the whole site. We don't have the source files for the boxed images and I have no idea what software was used to create them. We rely on asking other projects to help us with this update. I asked several times what was the software used but never get a reply. I don't check all the commits and I was certainly unaware that those files got finally committed. If we can't get the source nor the details on how these boxed images got created then we should consider creating a new set of images. What you guys think? Cheers! Hernan Shiva Kumar H R wrote: I also see some .psd files! in the same location. Must be the source for those boxes. Hernan can you try opening them with your Adobe Photoshop? - Shiva On 9/26/07, * Vamsavardhana Reddy* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hernan, I see some 2.0 box images at https://svn.apache.org/repos/asf/geronimo/site/trunk/art https://svn.apache.org/repos/asf/geronimo/site/trunk/art and they have been there since end of March!! Can you update the downloads page to show a 2.0 box? Vamsi On 8/22/07, *Hernan Cunico* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I've been trying for ages to get these updated. I asked folks from other projects using similar boxes but couldn't figure out what software they were using. All I have is the Photoshop suit but I'm sure those were created with something else. Cheers! Hernan Matt Hogstrom wrote: Does anyone know how to get an updated box for Geronimo that says 2.0.1? Since its the first thing people see on that page seems like it would make more sense for the release number to be the most recent. I'm happy to do it but not sure what software was used.
Re: Updates to Apache Geronimo Development Tools Subproject website
Tim, Thanks for the updates. Below are some more: 9) In Release Notes http://people.apache.org/dist/geronimo/eclipse/PLUGIN_RELEASE-NOTES-2.0.0.txt We must mention (may be under Requirements: section) the changes required in eclipse.ini if users are using Sun JDK 1.5.0_11. (http://www.mail-archive.com/dev@geronimo.apache.org/msg51412.html) 10) There is no mention! of http://people.apache.org/~mcconne/releases/RC3/build.xml. As you were pointing out on the other thread, it will be good idea to create a wiki page for Install Get Started instructions and capture all information in http://people.apache.org/~mcconne/releases/RC3/Geronimo_Eclipse_Plugin_2.0.0_Instructions-RC3.txtincluding the availability of build.xml, and put a link to it from http://geronimo.apache.org/development-tools.html 11) One more help Tim ;) Under News section of http://geronimo.apache.org/development-tools.html please change the title of Above presentation updated for Geronimo 2.0.1 to Above presentation updated for Java EE 5.0 Geronimo 2.0.1. Between are there any instructions on how to update our website? I would like to add my name under http://geronimo.apache.org/committers.html ;) Thanks, Shiva On 9/27/07, Tim McConnell [EMAIL PROTECTED] wrote: Shiva Kumar H R wrote: Great. Thanks Tim. Some minor corrections required to the website: 1) Prerequisites section currently says, 1. Sun JDK 5.0+ (J2SE 1.5) 2. Europa (also known as Eclipse 3.3), which is platform specific 3. Web Tools Platform (WTP) 2.0.1 4. Data Tools Platform (DTP) 1.5 5. Eclipse Modeling Framework (EMF) 2.3 6. Graphical Editing Framework (GEF) 3.3 Should be: 1. Sun JDK 5.0+ (J2SE 1.5) 2. Eclipse 3.3.1 (Eclipse Classic package of Europa distribution), which is platform specific 3. Web Tools Platform (WTP) 2.0.1 4. Data Tools Platform (DTP) 1.5.1 5. Eclipse Modeling Framework (EMF) 2.3.1 6. Graphical Editing Framework (GEF) 3.3.1 This was discussed earlier also. Please see http://www.mail-archive.com/dev@geronimo.apache.org/msg51362.html Done 2) In Downloads: Latest Release - Version 2.0.0 section: release notes http://people.apache.org/dist/geronimo/eclipse/PLUGIN_RELEASE-NOTES-2.0.0.txt link points to a non-existing document. Done, but I hope you can review the release notes as well, since you had requested specific content. 3) In Installation Alternatives section: The plug-in can be installed directly from within the plugin by clicking on the Don't see your server listed? ... ... from within the plugin is confusing. Was it meant to be from within the WTP ? Done 4) In Installation Alternatives section: Download the plugin from http://apache.org/dist/geronimo/eclipse/2.0.0/ and unzip it into the same directory ... In http://www.mail-archive.com/dev@geronimo.apache.org/msg50304.html Matt had expressed concerns about direct mentioning of http://www.apache.org/dist/geronimo/ site address. I think we need to come up with something like the download link in http://geronimo.apache.org/apache-geronimo-v201-release.html Not completely yet--will work with Hernan on this 5) In News section: Presentation titled J2EE Application Development on Apache Geronimo Simplified using Eclipse. Click here^ http://geronimo.apache.org/GMOxDOC11/j2ee-application-development-on-apache-geronimo-simplified-using-eclipse.html to view: The link is currently pointing to a non-existent doc in geronimo.apache.org http://geronimo.apache.org space. Referred doc is in cwiki.apache.org http://cwiki.apache.org space. So the correct link would be http://cwiki.apache.org/GMOxDOC11/j2ee-application-development-on-apache-geronimo-simplified-using-eclipse.html http://cwiki.apache.org/GMOxDOC11/j2ee-application-development-on-apache-geronimo-simplified-using-eclipse.html Done 6) In News section: Links for Java Developers Day 2007 in Krakow and EclipseWorld 2007 aren't yet pointing to their specific docs, but rather just point to http://cwiki.apache.org/geronimo/. I guess these will be updated once their corresponding wiki pages are created. Yes, I'm hoping that Jacek will allow us to use his presentation from Java Developers Day 2007, and I'm going to provide links to my EclipseWorld 2007 presentations when they are completed. 7) In JBoss to Geronimo Migration Tool (J2G) section: ... migrating the sources of an application written for the JBoss application server or written for Java 2 Enterprise Edition (J2EE) to the Apache Geronimo platform. Haven't yet explored J2G plug-in much. So curious to know what we mean by or written for Java 2 Enterprise Edition (J2EE)? Does J2G toolkit also help! in creating Geronimo specific deployment plans for generic J2EE modules? I'm not sure--I got this verbiage from Jason, Viet, Eric. They are probably better qualified to answer. 8) I guess
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530679 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- Thanks David. I have verified that (2) is NOT necessary with (1). Offline deployer throws BIND Exception when port 1099 is in use --- Key: GERONIMO-3481 URL: https://issues.apache.org/jira/browse/GERONIMO-3481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1, 2.0.x, 2.1 Environment: G 2.0.1 - Running multiple instances Reporter: Vamsavardhana Reddy Assignee: David Jencks Fix For: 2.0.2, 2.0.x, 2.1 Attachments: GERONIMO-3481-1.patch, GERONIMO-3481-2.patch, GERONIMO-3481-2a.patch, GERONIMO-3481-3.patch, GERONIMO-3481-for-2.0.patch, GERONIMO-3481-weird.patch Offline deployer throws Bind Exception when port 1099 is in use. Here is a scenario steps in which the problem is experienced. 1. Extract G-2.0.1-Tomcat distro to C:\ 2. Create a dir myserver under C:\geronimo-j2ee-tomcat-2.0.1 and copy C:\geronimo-j2ee-tomcat-2.0.1\var to C:\geronimo-j2ee-tomcat-2.0.1\myserver\var (all sub-directories). 3. Edit C:\geronimo-j2ee-tomcat-2.0.1\myserver\var\config-substitutions.properties to set PortOffset=10. 4. Open a command window and start Geronimo. Since org.apache.geronimo.server.name is not set, this will start the default server instance. 5. Open a second command window, set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver. This will be command window to run the second server instance with name myserver 6. Run deploy.bat --offline list-modules. At step 6, I am getting a BIND Exception since port 1099 is in use (by the default server instance) and the offline deployer is attempting to start rmi naming on port 1099. Since, this deploy command is run against second server instance, I would expect that it uses the configuration properties of myserver in which case it should use port 1109 to start rmi-naming if at all there is a need. When port 1099 is not in use, the offline deployer works as expected by updating proper config.xml file when a configuration is deployed/undeployed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-887) The default value for the result property should be set back to 'dom'
[ https://issues.apache.org/activemq/browse/SM-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-887. Resolution: Fixed Assignee: Guillaume Nodet Sendingdeployables/serviceengines/servicemix-saxon/pom.xml Sending deployables/serviceengines/servicemix-saxon/src/main/java/org/apache/servicemix/saxon/SaxonEndpoint.java Sending deployables/serviceengines/servicemix-saxon/src/main/java/org/apache/servicemix/saxon/XsltEndpoint.java Sendingpom.xml Transmitting file data Committed revision 579968. The default value for the result property should be set back to 'dom' - Key: SM-887 URL: https://issues.apache.org/activemq/browse/SM-887 Project: ServiceMix Issue Type: Improvement Components: servicemix-saxon Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.2 This was changed because of a bug in saxon 8.8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-886) Upgrade to saxon 9.9
[ https://issues.apache.org/activemq/browse/SM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-886. Resolution: Fixed Assignee: Guillaume Nodet Sendingdeployables/serviceengines/servicemix-saxon/pom.xml Sending deployables/serviceengines/servicemix-saxon/src/main/java/org/apache/servicemix/saxon/SaxonEndpoint.java Sending deployables/serviceengines/servicemix-saxon/src/main/java/org/apache/servicemix/saxon/XsltEndpoint.java Sendingpom.xml Transmitting file data Committed revision 579968. Upgrade to saxon 9.9 Key: SM-886 URL: https://issues.apache.org/activemq/browse/SM-886 Project: ServiceMix Issue Type: Improvement Components: servicemix-saxon Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-810) Create single complete ServiceMix Shared Library
[ https://issues.apache.org/activemq/browse/SM-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-810: --- Fix Version/s: (was: 3.2) Create single complete ServiceMix Shared Library Key: SM-810 URL: https://issues.apache.org/activemq/browse/SM-810 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Environment: ServiceMix 3.0 Reporter: James Lorenzen Original Estimate: 1 day Remaining Estimate: 1 day The current ServiceMix Shared Library is insufficient to support proper portability of existing ServiceMix components to other JBI containers, such as OpenESB. For example, when installing the ServiceMix HTTP BC in OpenESB, NoClassDefFoundErrors occur because the installed ServiceMix Shared Library does not contain all the necessary dependencies. Therefore it would be a good idea to create a single complete Shared Library. To accomplish this here are some ideas: 1) Combine the shared library and shared library compat projects together. 2) Ensure the new single complete Shared Library contains the following dependencies: a) activemq-core b) backport-util-concurrent c) commons-logging d) servicemix-core e) servicemix-services f) spring-2.0-rc3 g) wsdl4j h) xbean-classloader i) xbean-kernel j) xbean-server k) xbean-spring When complete the dependencies under /servicemix_home/lib should be smaller. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo box on Download page still says 1.1
g, reading those tutorials make it look so simple, why I didn't think about using those features in PS before. :-P Good catch Shiva, thanks for the pointer. I'll work on some .psd and commit them soon. Cheers! Hernan Shiva Kumar H R wrote: Yes Hernan, let's create our own boxes. Found these useful tutorials upon Google search for software box: http://tutorialblog.org/create-a-software-box/ http://tutorialblog.org/create-a-software-box/ http://www.designtutorials.info/software-box-design/ Adobe Photoshop is used in both the tutorials. - Shiva On 9/26/07, *Hernan Cunico* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Shiva, The .psd you see there are the templates we used as guidelines long time ago then we overhauled the whole site. We don't have the source files for the boxed images and I have no idea what software was used to create them. We rely on asking other projects to help us with this update. I asked several times what was the software used but never get a reply. I don't check all the commits and I was certainly unaware that those files got finally committed. If we can't get the source nor the details on how these boxed images got created then we should consider creating a new set of images. What you guys think? Cheers! Hernan Shiva Kumar H R wrote: I also see some .psd files! in the same location. Must be the source for those boxes. Hernan can you try opening them with your Adobe Photoshop? - Shiva On 9/26/07, * Vamsavardhana Reddy* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hernan, I see some 2.0 box images at https://svn.apache.org/repos/asf/geronimo/site/trunk/art https://svn.apache.org/repos/asf/geronimo/site/trunk/art and they have been there since end of March!! Can you update the downloads page to show a 2.0 box? Vamsi On 8/22/07, *Hernan Cunico* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I've been trying for ages to get these updated. I asked folks from other projects using similar boxes but couldn't figure out what software they were using. All I have is the Photoshop suit but I'm sure those were created with something else. Cheers! Hernan Matt Hogstrom wrote: Does anyone know how to get an updated box for Geronimo that says 2.0.1? Since its the first thing people see on that page seems like it would make more sense for the release number to be the most recent. I'm happy to do it but not sure what software was used.
2.0.2 Build failing
It looks like we're in an incompatible state at the moment between Geronimo-2.0 and Openejb trunk. Some changes went in yesterday to openejb (http://svn.apache.org/viewvc?rev=579817view=rev) that altered org.apache.openejb.spi.SecurityService and require comparable changes in Geronimo. Does anybody know the status of the Geronimo changes? Joe
Re: devtools/maven-plugins was not released as part of v2.0.0 eclipse-plugin
Hi Donald, I'll rectify this immediately, and will update our Plugin Release process to ensure it doesn't again. Thanks for the information. Donald Woods wrote: Tim, I just noticed that we didn't create a release of https://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/ as part of the eclipse-plugin release. Given the eclipse-plugin release used a 1.0-SNAPSHOT depend of maven-plugin (and J2G uses it too), we need to release it and use it for the 2.0.1 plugin release Also, we need to make sure that all SNAPSHOT depends are removed in future plugin releases. -Donald -- Thanks, Tim McConnell
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
Sorry again for my confused message below. I did add a newer message to your jira yesterday hoping you would pick the newer message up... - It looks like this build error is caused by the change to go to the maven-antrun-plugin. somehow, we are configuring our eclipse env differently than we used to (in sandbox). I just made a bit change to not download all the other unnecessary stuff (WTP and its prerequisites), and had thought the build error went away. But it didn't. I was able to build just now because I built the the sandbox j2g first which enabled the repo in a way that is favorable to build the org.apache.geronimo.j2g.sources plugin. Lin Erik B. Craig wrote: Errmm, I got past this point, was silly firewall issues preventing it from hitting the mirror, however I believe I'm still having the same compilation issues as previously... I'll update when I can verify that... On 9/26/07, *Erik B. Craig* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm having some issues on my ubuntu machine with this... what platform did you get this working on? [get] last modified = Wed Dec 31 19:00:00 EST 1969 - using current time instead [echo] Unzipping eclipse-SDK-3.3-linux-gtk.tar.gz to the expected location in /home/ebcraig/.m2/repository [mkdir] Created dir: /home/ebcraig/.m2/repository/eclipse [gunzip] Expanding /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar.gz to /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse-SDK-3.3-linux-gtk.tar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /home/ebcraig/g-src/j2g/eclipse/eclipse-3.3.xml:60: Problem expanding gzip Not in GZIP format On 9/26/07, *Donald Woods* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security- geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff == --- geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml (original) +++ geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml Wed Sep 26 12:04:16 2007 @@ -23,7 +23,7 @@ target name=init property name=eclipse_version value=3.3/ -echoSetting up for downloading Eclipse SDK v${eclipse_version}, WTP, EMF, GEF and DTP/echo +echoSetting up for downloading Eclipse SDK v${eclipse_version}/echo property name=base_url value= http://www.eclipse.org/downloads/download.php?file=/ property name=eclipse_sdk_url value=${base_url}/eclipse/downloads/drops/R-3.3-200706251500// property name=eclipse_sdk_win32 value=eclipse-SDK-${eclipse_version}- win32.zip/ @@ -32,15 +32,6 @@ property name=eclipse_sdk_linux_gzvalue=${eclipse_sdk_linux}.gz/ property name=eclipse_sdk_macos_gzvalue=${eclipse_sdk_macos}.gz/ -property name=dtp_download_url value=${base_url}/datatools/downloads/1.5// -property name=emf_download_url value=${base_url}/modeling/emf/emf/downloads/drops/2.3.0/R200706262000// -property name=gef_download_url value=${base_url}/tools/gef/downloads/drops/R-3.3-200706281000// -property name=wtp_download_url
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
Right - i made a comment to the j2g compile prob jira yesterday PM. I was able to build because I built the old j2g from sandbox first.But we don't need the WTP and its prereqs stuff and it can take a very long time to download them if you are at home or something. Lin Donald Woods wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff == --- geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml (original) +++ geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml Wed Sep 26 12:04:16 2007 @@ -23,7 +23,7 @@ target name=init property name=eclipse_version value=3.3/ -echoSetting up for downloading Eclipse SDK v${eclipse_version}, WTP, EMF, GEF and DTP/echo +echoSetting up for downloading Eclipse SDK v${eclipse_version}/echo property name=base_url value=http://www.eclipse.org/downloads/download.php?file=/ property name=eclipse_sdk_url value=${base_url}/eclipse/downloads/drops/R-3.3-200706251500// property name=eclipse_sdk_win32 value=eclipse-SDK-${eclipse_version}-win32.zip/ @@ -32,15 +32,6 @@ property name=eclipse_sdk_linux_gz value=${eclipse_sdk_linux}.gz/ property name=eclipse_sdk_macos_gz value=${eclipse_sdk_macos}.gz/ -property name=dtp_download_url value=${base_url}/datatools/downloads/1.5// -property name=emf_download_url value=${base_url}/modeling/emf/emf/downloads/drops/2.3.0/R200706262000// -property name=gef_download_url value=${base_url}/tools/gef/downloads/drops/R-3.3-200706281000// -property name=wtp_download_url value=${base_url}/webtools/downloads/drops/R2.0/R-2.0-200706260303// - -property name=dtp_sdk value=dtp-sdk_1.5_20070704.zip/ -property name=emf_sdo value=emf-sdo-xsd-SDK-2.3.0.zip/ -property name=gef_sdk value=GEF-SDK-3.3.zip/ -property name=wtp_sdk value=wtp-sdk-R-2.0-200706260303.zip/ property name=protocol value=amp;r=1amp;protocol=http/ /target @@ -89,62 +80,5 @@ echoRemoving any existing version of Eclipse at ${LOCAL_M2_REPO}/eclipse/echo delete dir=${LOCAL_M2_REPO}/eclipse/ echoDownloading WTP prereqs/echo -antcall target=dtp/ -antcall target=emf/ -antcall target=gef/ -antcall target=wtp/ -/target - -target name=dtp depends=init description=Download Data Tools Platform (DTP) artifact -echoDownloading ${dtp_download_url}${dtp_sdk}/echo -mkdir dir=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/ -get src=${dtp_download_url}${dtp_sdk}${protocol} - dest=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/${dtp_sdk} - verbose=true - usetimestamp=true/ -echoUnzipping ${dtp_sdk} to the expected location in ${LOCAL_M2_REPO}/echo -mkdir dir=${LOCAL_M2_REPO}/eclipse/ -unzip src=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/${dtp_sdk} - dest=${LOCAL_M2_REPO}/eclipse/ -/target - -target name=emf depends=init description=Download Eclipse Modeling Framework (EMF) artifact -echoDownloading ${emf_download_url}${emf_sdo}/echo -mkdir dir=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/ -get src=${emf_download_url}${emf_sdo}${protocol} - dest=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/${emf_sdo} - verbose=true - usetimestamp=true/ -echoUnzipping ${emf_sdo} to the expected location in ${LOCAL_M2_REPO}/echo -mkdir dir=${LOCAL_M2_REPO}/eclipse/ -unzip src=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/${emf_sdo} - dest=${LOCAL_M2_REPO}/eclipse/ /target - -target name=gef depends=init description=Download Graphical Editing Framework (GEF) artifact -echoDownloading ${gef_download_url}${gef_sdk}/echo -mkdir dir=${LOCAL_M2_REPO}/org/eclipse/eclipse/${eclipse_version}/ -get src=${gef_download_url}${gef_sdk}${protocol} -
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
Yeah, I actually just attempted the same thing. I'm trying to figure out where it could be getting the hardcoded jar from though. On 9/27/07, Lin Sun [EMAIL PROTECTED] wrote: Tried to change it to M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core- 3.3.0-v_771.jar didn't work either. Right it seems somewhere it has hardcoded value to the old level of jars... Lin Donald Woods wrote: Could it be the level of the org.eclipse.jdt.core jarfile listed in plugins\org.apache.geronimo.j2g.sources\.classpath ? Seems the Eclipse 3.3 runtime provides 3.3.0-v_771 but the .classpath is still using the older 3.1.1 level -Donald Erik B. Craig wrote: Errmm, I got past this point, was silly firewall issues preventing it from hitting the mirror, however I believe I'm still having the same compilation issues as previously... I'll update when I can verify that... On 9/26/07, *Erik B. Craig* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm having some issues on my ubuntu machine with this... what platform did you get this working on? [get] last modified = Wed Dec 31 19:00:00 EST 1969 - using current time instead [echo] Unzipping eclipse-SDK-3.3-linux-gtk.tar.gz to the expected location in /home/ebcraig/.m2/repository [mkdir] Created dir: /home/ebcraig/.m2/repository/eclipse [gunzip] Expanding /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar.gz to /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /home/ebcraig/g-src/j2g/eclipse/eclipse-3.3.xml:60: Problem expanding gzip Not in GZIP format On 9/26/07, *Donald Woods* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security- geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse- 3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff == --- geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml (original) +++ geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml Wed Sep 26 12:04:16 2007 @@ -23,7 +23,7 @@ target name=init property name=eclipse_version value=3.3/ -echoSetting up for downloading Eclipse SDK v${eclipse_version}, WTP, EMF, GEF and DTP/echo +echoSetting up for downloading Eclipse SDK v${eclipse_version}/echo property name=base_url value= http://www.eclipse.org/downloads/download.php?file=/ property name=eclipse_sdk_url value=${base_url}/eclipse/downloads/drops/R-3.3-200706251500// property name=eclipse_sdk_win32 value=eclipse-SDK-${eclipse_version}- win32.zip/ @@ -32,15 +32,6 @@ property name=eclipse_sdk_linux_gzvalue=${eclipse_sdk_linux}.gz/ property name=eclipse_sdk_macos_gzvalue=${eclipse_sdk_macos}.gz/ -property name=dtp_download_url value=${base_url}/datatools/downloads/1.5// -property name=emf_download_url value=${base_url}/modeling/emf/emf/downloads/drops/2.3.0/R200706262000// -property name=gef_download_url
[jira] Commented: (GERONIMO-3489) Deployment problems caused by file deletion failures
[ https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530765 ] Ted Kirby commented on GERONIMO-3489: - I note also that starting the server with these two system properties significantly reduced the occurrence of the problem: Xorg.apache.geronimo.JarFileClassLoader=true Xorg.apache.geronimo.kernel.config.MPCLSearchOption=safe The bad news is that server startup time was increased. :-( Deployment problems caused by file deletion failures Key: GERONIMO-3489 URL: https://issues.apache.org/jira/browse/GERONIMO-3489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Reporter: Ted Kirby Fix For: 2.0.2, 2.0.x, 2.1 File.delete() failures in IOUtil.recursiveDelete() are causing various deployment problems. I open this JIRA to discuss them to see how the server might better handle them. In all but one case, delete failures are not even noted with a log record! Deletion problems are seen in many environments and platforms, but they are persistently fatal when using a NFS file system for the repository. In investigating the problem, I have added code to recursiveDelete to retry the delete a few times if it fails. I added code to list directory contents if a directory delete failed, and saw a file named .nfs2bc4350053e in the directory. My first attempt at a bypass was to retry a failed delete 5 times, sleeping a second before each try. This did not work. I added a call to System.gc() before each sleep, and this got me passed the problem. Interestingly, two retries were required to get this to work. In another version, each retry was a second longer, and I printed all file names in a directory before trying the delete. This worked in most cases, but required the full 5 retries, so I suspect System.gc() would have time. System.runFinalization() would be something else to try. RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the failing end of the deletion problem, with the dreaded ConfigurationAlreadyExistsException(Configuration already exists: + configId)exception. I think this message is not good. It should really say directory already exists. If the file is not deleted on undeploy, this failure occurs on a subsequent deploy. What is really bad is if the user invokes a redeploy operation, and the file delete fails on the undeploy. It is important that undeploy not complete until the file goes away. From other environments, I am not convinced that all file handles and references, and particularly open streams, are being closed on some artifacts. This will cause the delete to fail. It may be that the gc() calls are cleaning these up, and allowing the deletes to work in my case above. Another option is that RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a ConfigurationAlreadyExistsException if the only problem is an empty directory structure exists. The next line creates the directory structure anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy closed GERONIMO-3481. - Resolution: Fixed Fix Version/s: (was: 2.0.x) Assignee: Vamsavardhana Reddy (was: David Jencks) Completed: At revision: 580077 o Change the scope of jaxws-deployer's dependency on webservices-common to runtime. o Prevent offline deployer from stopping the onlineConfigStores as it will leave no stores for the offline deployer to work with. Offline deployer throws BIND Exception when port 1099 is in use --- Key: GERONIMO-3481 URL: https://issues.apache.org/jira/browse/GERONIMO-3481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1, 2.0.x, 2.1 Environment: G 2.0.1 - Running multiple instances Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.0.2, 2.1 Attachments: GERONIMO-3481-1.patch, GERONIMO-3481-2.patch, GERONIMO-3481-2a.patch, GERONIMO-3481-3.patch, GERONIMO-3481-for-2.0.patch, GERONIMO-3481-weird.patch Offline deployer throws Bind Exception when port 1099 is in use. Here is a scenario steps in which the problem is experienced. 1. Extract G-2.0.1-Tomcat distro to C:\ 2. Create a dir myserver under C:\geronimo-j2ee-tomcat-2.0.1 and copy C:\geronimo-j2ee-tomcat-2.0.1\var to C:\geronimo-j2ee-tomcat-2.0.1\myserver\var (all sub-directories). 3. Edit C:\geronimo-j2ee-tomcat-2.0.1\myserver\var\config-substitutions.properties to set PortOffset=10. 4. Open a command window and start Geronimo. Since org.apache.geronimo.server.name is not set, this will start the default server instance. 5. Open a second command window, set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver. This will be command window to run the second server instance with name myserver 6. Run deploy.bat --offline list-modules. At step 6, I am getting a BIND Exception since port 1099 is in use (by the default server instance) and the offline deployer is attempting to start rmi naming on port 1099. Since, this deploy command is run against second server instance, I would expect that it uses the configuration properties of myserver in which case it should use port 1109 to start rmi-naming if at all there is a need. When port 1099 is not in use, the offline deployer works as expected by updating proper config.xml file when a configuration is deployed/undeployed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
Tried to change it to M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core-3.3.0-v_771.jar didn't work either. Right it seems somewhere it has hardcoded value to the old level of jars... Lin Donald Woods wrote: Could it be the level of the org.eclipse.jdt.core jarfile listed in plugins\org.apache.geronimo.j2g.sources\.classpath ? Seems the Eclipse 3.3 runtime provides 3.3.0-v_771 but the .classpath is still using the older 3.1.1 level -Donald Erik B. Craig wrote: Errmm, I got past this point, was silly firewall issues preventing it from hitting the mirror, however I believe I'm still having the same compilation issues as previously... I'll update when I can verify that... On 9/26/07, *Erik B. Craig* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm having some issues on my ubuntu machine with this... what platform did you get this working on? [get] last modified = Wed Dec 31 19:00:00 EST 1969 - using current time instead [echo] Unzipping eclipse-SDK-3.3-linux-gtk.tar.gz to the expected location in /home/ebcraig/.m2/repository [mkdir] Created dir: /home/ebcraig/.m2/repository/eclipse [gunzip] Expanding /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar.gz to /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse-SDK-3.3-linux-gtk.tar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /home/ebcraig/g-src/j2g/eclipse/eclipse-3.3.xml:60: Problem expanding gzip Not in GZIP format On 9/26/07, *Donald Woods* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security- geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff == --- geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml (original) +++ geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml Wed Sep 26 12:04:16 2007 @@ -23,7 +23,7 @@ target name=init property name=eclipse_version value=3.3/ -echoSetting up for downloading Eclipse SDK v${eclipse_version}, WTP, EMF, GEF and DTP/echo +echoSetting up for downloading Eclipse SDK v${eclipse_version}/echo property name=base_url value= http://www.eclipse.org/downloads/download.php?file=/ property name=eclipse_sdk_url value=${base_url}/eclipse/downloads/drops/R-3.3-200706251500// property name=eclipse_sdk_win32 value=eclipse-SDK-${eclipse_version}- win32.zip/ @@ -32,15 +32,6 @@ property name=eclipse_sdk_linux_gzvalue=${eclipse_sdk_linux}.gz/ property name=eclipse_sdk_macos_gzvalue=${eclipse_sdk_macos}.gz/ -property name=dtp_download_url value=${base_url}/datatools/downloads/1.5// -property name=emf_download_url value=${base_url}/modeling/emf/emf/downloads/drops/2.3.0/R200706262000// -property name=gef_download_url value=${base_url}/tools/gef/downloads/drops/R-3.3-200706281000// -property name=wtp_download_url value=${base_url}/webtools/downloads/drops/R2.0/R- 2.0-200706260303// - -property name=dtp_sdk value=dtp-sdk_1.5_20070704.zip/ -
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
I did some search/replace on the source files that it's actually having issues on... It seems as though it's not having any problem at all locating the org.eclipse.jdt.core.dom.CompilationUnit class... it's only the two methods (getLineNumber and getColumnNumber) that it doesn't recognize at all. Looking in the API doc for jdtcore ( http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/dom/class-use/CompilationUnit.html) the methods are still the same, and have not been deprecated. I'm not quite sure what to make of this, especially since other methods from the same exact class are being picked up and compiling fine. This was while having the .classpath changed to use M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core- 3.3.0-v_771.jar. ... Slightly dumbfounded now, got any ideas? On 9/27/07, Erik B. Craig [EMAIL PROTECTED] wrote: Yeah, I actually just attempted the same thing. I'm trying to figure out where it could be getting the hardcoded jar from though. On 9/27/07, Lin Sun [EMAIL PROTECTED] wrote: Tried to change it to M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core- 3.3.0-v_771.jar didn't work either. Right it seems somewhere it has hardcoded value to the old level of jars... Lin Donald Woods wrote: Could it be the level of the org.eclipse.jdt.core jarfile listed in plugins\org.apache.geronimo.j2g.sources\.classpath ? Seems the Eclipse 3.3 runtime provides 3.3.0-v_771 but the .classpath is still using the older 3.1.1 level -Donald Erik B. Craig wrote: Errmm, I got past this point, was silly firewall issues preventing it from hitting the mirror, however I believe I'm still having the same compilation issues as previously... I'll update when I can verify that... On 9/26/07, *Erik B. Craig* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm having some issues on my ubuntu machine with this... what platform did you get this working on? [get] last modified = Wed Dec 31 19:00:00 EST 1969 - using current time instead [echo] Unzipping eclipse-SDK-3.3-linux-gtk.tar.gz to the expected location in /home/ebcraig/.m2/repository [mkdir] Created dir: /home/ebcraig/.m2/repository/eclipse [gunzip] Expanding /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar.gz to /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /home/ebcraig/g-src/j2g/eclipse/eclipse-3.3.xml:60: Problem expanding gzip Not in GZIP format On 9/26/07, *Donald Woods* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security- geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse- 3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff == --- geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml (original) +++ geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xmlWed Sep 26 12:04:16 2007 @@ -23,7 +23,7 @@ target name=init property name=eclipse_version value= 3.3 / -echoSetting up for downloading Eclipse SDK
[jira] Updated: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3441: --- Attachment: (was: stats.patch) Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: mrc-client.zip, mrc-server.zip, screenshot1.jpg, screenshot2.jpg Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3441: --- Attachment: stats.patch I have added the lastSampleTime and startTime field for each statistic. Also, the statisticsProvider attribute was already set to true, so it is not present in the patch, but it is there when I view the mbean from jconsole. This patch also exposes the Jetty Connector stats in addition to the Jetty Container stats. I have tested this patch on the latest trunk and both tomcat and jetty works fine. If someone could review the patch along with the MRC plugins, it will be great to get this into sandbox. Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: mrc-client.zip, mrc-server.zip, screenshot1.jpg, screenshot2.jpg, stats.patch Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r579758 - in /geronimo/devtools/j2g/trunk: eclipse/eclipse-3.3.xml plugins/org.apache.geronimo.j2g.resources/test-apps/security/security-geronimo-plan.xml
Futerhmore, I've dove into the eclipse SDK repository and taken a gander at the source do org.eclipse.jdt.core.dom.CompilationUnit v771 (here: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/CompilationUnit.java?view=markuppathrev=v_771 ) and found that the methods do in fact exist in this revision. On 9/27/07, Erik B. Craig [EMAIL PROTECTED] wrote: I did some search/replace on the source files that it's actually having issues on... It seems as though it's not having any problem at all locating the org.eclipse.jdt.core.dom.CompilationUnit class... it's only the two methods (getLineNumber and getColumnNumber) that it doesn't recognize at all. Looking in the API doc for jdtcore ( http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/dom/class-use/CompilationUnit.html ) the methods are still the same, and have not been deprecated. I'm not quite sure what to make of this, especially since other methods from the same exact class are being picked up and compiling fine. This was while having the .classpath changed to use M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core- 3.3.0-v_771.jar. ... Slightly dumbfounded now, got any ideas? On 9/27/07, Erik B. Craig [EMAIL PROTECTED] wrote: Yeah, I actually just attempted the same thing. I'm trying to figure out where it could be getting the hardcoded jar from though. On 9/27/07, Lin Sun [EMAIL PROTECTED] wrote: Tried to change it to M2_REPO/org/eclipse/plugins/org.eclipse.jdt.core/3.3.0-v_771/org.eclipse.jdt.core- 3.3.0-v_771.jar didn't work either. Right it seems somewhere it has hardcoded value to the old level of jars... Lin Donald Woods wrote: Could it be the level of the org.eclipse.jdt.core jarfile listed in plugins\org.apache.geronimo.j2g.sources\.classpath ? Seems the Eclipse 3.3 runtime provides 3.3.0-v_771 but the .classpath is still using the older 3.1.1 level -Donald Erik B. Craig wrote: Errmm, I got past this point, was silly firewall issues preventing it from hitting the mirror, however I believe I'm still having the same compilation issues as previously... I'll update when I can verify that... On 9/26/07, *Erik B. Craig* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm having some issues on my ubuntu machine with this... what platform did you get this working on? [get] last modified = Wed Dec 31 19:00:00 EST 1969 - using current time instead [echo] Unzipping eclipse-SDK-3.3-linux-gtk.tar.gz to the expected location in /home/ebcraig/.m2/repository [mkdir] Created dir: /home/ebcraig/.m2/repository/eclipse [gunzip] Expanding /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar.gz to /home/ebcraig/.m2/repository/org/eclipse/eclipse/3.3/eclipse- SDK-3.3-linux-gtk.tar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /home/ebcraig/g-src/j2g/eclipse/eclipse-3.3.xml:60: Problem expanding gzip Not in GZIP format On 9/26/07, *Donald Woods* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Not sure why having WTP and its prereqs in the repo would cause you build problems, as this is exactly the same as we do for the WTP server adapter builds... -Donald [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Author: linsun Date: Wed Sep 26 12:04:16 2007 New Revision: 579758 URL: http://svn.apache.org/viewvc?rev=579758view=rev http://svn.apache.org/viewvc?rev=579758view=rev Log: These changes seem to fix GERONIMODEVTOOLS-224 on my machine (with a clean .m2 repo). Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.resources/test-apps/security/security- geronimo-plan.xml Modified: geronimo/devtools/j2g/trunk/eclipse/eclipse- 3.3.xml URL: http://svn.apache.org/viewvc/geronimo/devtools/j2g/trunk/eclipse/eclipse-3.3.xml?rev=579758r1=579757r2=579758view=diff
Re: 2.0.2 Build failing
Joe Bohn wrote: It looks like we're in an incompatible state at the moment between Geronimo-2.0 and Openejb trunk. Some changes went in yesterday to openejb (http://svn.apache.org/viewvc?rev=579817view=rev) that altered org.apache.openejb.spi.SecurityService and require comparable changes in Geronimo. Does anybody know the status of the Geronimo changes? I'm going to switch the Geronimo-2.0 dependency on openejb from 3.0.0-SNAPSHOT (trunk) to 3.0-beta-1. This should hopefully get around this build problem since the SecurityService change didn't go into 3.0-beta-1 and get geronimo 2.0.2 on a stable openejb release as we get closed to getting it out the door. Joe
[jira] Updated: (GERONIMO-3441) Server monitoring and management
[ https://issues.apache.org/jira/browse/GERONIMO-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3441: Attachment: mrc.zip I have created a combined package with a pom to handle building both the client and the server, everything has proper License information, as well as notice information (both the files and in the headers of all source files). The directory structure is completely setup for import into svn as geronimo/sandbox/svn (has the branches/tags/trunk directories created, with content in the trunk only currently) Server monitoring and management Key: GERONIMO-3441 URL: https://issues.apache.org/jira/browse/GERONIMO-3441 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: general Affects Versions: 2.1 Environment: All Reporter: Erik B. Craig Assignee: Erik B. Craig Attachments: mrc-client.zip, mrc-server.zip, mrc.zip, screenshot1.jpg, screenshot2.jpg, stats.patch Currently, there is not a good way of surfacing Geronimo's server information so that an administrator can monitor the server's status. The architecture of using MBeans is established, but not fully exploited. This enhancement will take advantage of what Geronimo currently offers and extend it so that a server can tap into a cluster of servers and extract information from specific Geronimo servers or even aggregates of Geronimo servers. The goal is to have one machine be able to reach out to all Geronimo servers in order to fetch data or even alter their state. This will be especially useful in the case of someone having to monitor a large number of Geronimo servers. Viet Nguyen and myself have completed a bit of framework towards this goal, to be attached to this jira In-depth information can be found in the confluence wiki here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [UPDATE] Server monitoring and Management plugin
I have attached a new combined mrc.zip file that contains both the mrc-server and the mrc-client sharing a pom to compile both, as well as 100% correct license.txt files, notice.txt files, and ASL license headers in all files. It also has the correct directory structure to be directly imported into geronimo/sandbox (has branches/tags/trunk, everything is in the trunk the the archive). Here's the link to the jira again: https://issues.apache.org/jira/browse/GERONIMO-3441 If someone would be so kind as to maybe import this into sandbox for some easier development for viet and I, that would be fantastic =) On 9/26/07, Donald Woods [EMAIL PROTECTED] wrote: Looks great and keep up the much needed monitoring support work! If you attach a zipfile of the source to the JIRA with the ASL contribution bit checked (and with the required ASL headers and license files in the source) I'd be glad to check it into sandbox or plugins/trunk -Donald Erik B. Craig wrote: Greetings, After a round of improvements to the monitoring and management plugin that Viet an I have been working on (https://issues.apache.org/jira/browse/GERONIMO-3441 https://issues.apache.org/jira/browse/GERONIMO-3441), we felt it was time to update everyone on where things are at, and hopefully get a good deal of feedback and perhaps a feel for the direction everyone thinks would be best for this. Since the last time we brought it to the dev list, the method in which data is collected has been changed to utilize the JSR77 defined statistics. Currently we have implemented this for the Tomcat connectors 'TomcatWebConnector', 'TomcatWebSSLConnector', and 'TomcatAJPConnector'. This information is still having 'snapshots' taken, and is then stored locally at a set interval (now defined in a configuration file) in an XML file. There are still some issues revolving around surfacing the equivalent statistics for Jetty (We have tomcat CONNECTORS, but jetty CONTAINERS), largely due to geronimo losing a handle on them since jetty6, but it is being worked on. In addition to Jetty, we're also looking at getting MEJB stats surfaced and tracked very soon down the road... and if anyone has any other suggestions for what you think should be able to be collected, it would be greatly appreciated. In addition to using JSR77 on the mrc-server component, there are a number of other improvements, including * Archiving of snapshot data in a zip file every month - prevent the single active file from getting too large * Ability to start/stop the statistics collection thread * Specify the duration between snapshots * Ability to modify mbean attributes * Ability to add mbeans to track in the snapshot process As far as the client side of things goes... The plugin has been updated to be deployable on the latest iteration of the plugable console Paul has been working on, and is working fully on the latest 2.1 trunk with the plugable console deployed. It is also now doing page generation through JSPs from the portlet, where as previously it was simple line prints to the http response. The graphing is now far more dynamic, and able to accept any time frame (in minutes) from 2*snapshotduration up to however high you can count (or fit into an integer, whichever comes first). If there is not enough snapshot data to generate the requested graph, 'older' data will be inserted with values of 0. If there are gaps in the snapshots ( I.E. the snapshot time of element 1 vs. element 2 is greater than the snapshot duration), the client will fill in dummy data between the two, so that the time frame and stamps on the generated graph is accurate. (To be further improved to indicate gaps via highlighting on the graphs). In addition to this, determining exactly 'what' is being graphed is now dynamically done depending on what is being collected on the server side. This will further be improved through a configuration page and file on the client side, that will allow enabling or disabling of graphs for statistics being collected on the server side , as well as configuring exactly how they are displayed (color, axis labels, size, etc). For some more information on the current status, check out the jira link above, or the wiki page here http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service http://cwiki.apache.org/confluence/display/GMOxDEV/Monitoring+and+Management+Service Again - all feedback, questions, suggestions would be greatly appreciated On a side note - would it be possible to get an iteration of this stuff checked into either sandbox of the plugins directory? It would certainly make things much easier for collaboration and revision control =) Thanks, -- Erik B. Craig -- Erik B. Craig
Re: refactoring jaxws support
FYI, CXF refactoring is now done in trunk. Everything seems to be working and I can now install the cxf-deployer/car plugin onto the minimal assembly and successfully deploy and run JAX-WS (Serlvet-based) web services. I'll work on Axis2 next. Jarek On 9/19/07, Jarek Gawor [EMAIL PROTECTED] wrote: As we talked about making things more modular for 2.1, I'm planning to split the CXF and Axis2 modules into smaller units. The main purpose of the split is to separate the EJB bits from Servlet bits so that we can create a minimal server with JAX-WS support but without installing OpenEJB first. Separating the EJB bits from Servlet bits will require moving some code into new modules and creating a few new configs. It will probably require creating 2 new modules, and 2 new configs per each engine implementation and 2 new modules, 2 new configs for shared code and configuration. So at the end it might be quite a few new modules and configs (unless I find or somebody suggests a better way to split this up). This is just a plan right now and things might change as I work through it. Jarek
Re: refactoring jaxws support
Excellent!!! thanks david jencks On Sep 27, 2007, at 12:23 PM, Jarek Gawor wrote: FYI, CXF refactoring is now done in trunk. Everything seems to be working and I can now install the cxf-deployer/car plugin onto the minimal assembly and successfully deploy and run JAX-WS (Serlvet-based) web services. I'll work on Axis2 next. Jarek On 9/19/07, Jarek Gawor [EMAIL PROTECTED] wrote: As we talked about making things more modular for 2.1, I'm planning to split the CXF and Axis2 modules into smaller units. The main purpose of the split is to separate the EJB bits from Servlet bits so that we can create a minimal server with JAX-WS support but without installing OpenEJB first. Separating the EJB bits from Servlet bits will require moving some code into new modules and creating a few new configs. It will probably require creating 2 new modules, and 2 new configs per each engine implementation and 2 new modules, 2 new configs for shared code and configuration. So at the end it might be quite a few new modules and configs (unless I find or somebody suggests a better way to split this up). This is just a plan right now and things might change as I work through it. Jarek
[jira] Created: (GERONIMODEVTOOLS-225) j2g-configure.sh does not support ~ in the ECLIPSE_HOME path
j2g-configure.sh does not support ~ in the ECLIPSE_HOME path Key: GERONIMODEVTOOLS-225 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-225 Project: Geronimo-Devtools Issue Type: Bug Components: J2G Affects Versions: 1.0.0 Reporter: Donald Woods Priority: Minor using ~/eclipse hen prompted for the ECLIPSE_HOME will fail, but /home/drwoods/eclipse works -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] G 2.0.2 Release plan
On Sep 26, 2007, at 7:30 PM, Kevan Miller wrote: On Sep 25, 2007, at 4:08 PM, Donald Woods wrote: OK, I'm done updating the 2.0.x closed issues (sorry for all the JIRA emails.) The only one I couldn't figure out, was: https://issues.apache.org/jira/browse/GERONIMO-3423 Donald, Thanks a bunch for going through all of those Jiras! David Blevins, Are we missing 3423 in branches/2.0? Heh. Looks like I merged the change to branches/2.0 in revision 570950 -- http://svn.apache.org/viewvc?view=revrevision=570950. --kevan
[jira] Updated: (GERONIMO-3489) Deployment problems caused by file deletion failures
[ https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMO-3489: Attachment: G3489-1.patch G4380-1.patch is a patch for IOUtil.recursiveDelete. System.runFinalization() didn't really seem to help out much, so I went with System.gc(). This patch warns on delete failure after 5 retries, and will put debug info on each failure and retry. Deployment problems caused by file deletion failures Key: GERONIMO-3489 URL: https://issues.apache.org/jira/browse/GERONIMO-3489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Reporter: Ted Kirby Fix For: 2.0.2, 2.0.x, 2.1 Attachments: G3489-1.patch File.delete() failures in IOUtil.recursiveDelete() are causing various deployment problems. I open this JIRA to discuss them to see how the server might better handle them. In all but one case, delete failures are not even noted with a log record! Deletion problems are seen in many environments and platforms, but they are persistently fatal when using a NFS file system for the repository. In investigating the problem, I have added code to recursiveDelete to retry the delete a few times if it fails. I added code to list directory contents if a directory delete failed, and saw a file named .nfs2bc4350053e in the directory. My first attempt at a bypass was to retry a failed delete 5 times, sleeping a second before each try. This did not work. I added a call to System.gc() before each sleep, and this got me passed the problem. Interestingly, two retries were required to get this to work. In another version, each retry was a second longer, and I printed all file names in a directory before trying the delete. This worked in most cases, but required the full 5 retries, so I suspect System.gc() would have time. System.runFinalization() would be something else to try. RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the failing end of the deletion problem, with the dreaded ConfigurationAlreadyExistsException(Configuration already exists: + configId)exception. I think this message is not good. It should really say directory already exists. If the file is not deleted on undeploy, this failure occurs on a subsequent deploy. What is really bad is if the user invokes a redeploy operation, and the file delete fails on the undeploy. It is important that undeploy not complete until the file goes away. From other environments, I am not convinced that all file handles and references, and particularly open streams, are being closed on some artifacts. This will cause the delete to fail. It may be that the gc() calls are cleaning these up, and allowing the deletes to work in my case above. Another option is that RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a ConfigurationAlreadyExistsException if the only problem is an empty directory structure exists. The next line creates the directory structure anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] G 2.0.2 Release plan
On Sep 26, 2007, at 4:01 PM, Kevan Miller wrote: On Sep 25, 2007, at 6:40 PM, David Blevins wrote: On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote: One thing I've noticed -- the default JNDI name for EJB's has been changed in OpenEJB. So, there is a compatibility issue with 2.0.1. We might be able to configure how OpenEJB generates this default to maintain backward compatibility. Better, IMO, to go ahead and match OpenEJB's behavior. There are no compatibility issues as it was explicitly set in Geronimo 2.0.1 to be essentially {moduleId}/{ejbName}/ {interfaceClass} (actually it's {deploymentId}/{interfaceClass} and deploymentId will be {moduleId}/{ejbName}). It'll still be the same in Geronimo 2.0.2, just now it can be changed to something shorter. Well, that's encouraging. However, something has changed between 2.0.1 and 2.0.2. Can you help explain the following? INFO log during 2.0.1 deploy: 18:45:13,785 INFO [config] Configuring app: GeneralEJB.jar 18:45:13,849 INFO [OpenEJB] Auto-deploying ejb My: EjbDeployment (deployment-id=GeneralEJB.jar/My, container-id=null) 18:45:14,066 INFO [config] Loaded Module: GeneralEJB.jar 18:45:16,653 INFO [Enhance] You have enabled runtime enhancement, but have not specified the set of persistent classes. OpenJPA must look for metadata for every loaded class, which might increase class load times significantly. 18:45:17,021 INFO [startup] Assembling app: /geronimo-jetty6- jee5-2.0.1/var/temp/geronimo-deploymentUtil24358.jar 18:45:17,375 INFO [startup] Jndi(name=GeneralEJB.jar/My/ejbs.My) 18:45:17,375 INFO [startup] Created Ejb(deployment- id=GeneralEJB.jar/My, ejb-name=My, container=Default Stateless Container) INFO log during 2.0.2-SNAPSHOT deploy: 18:52:08,701 INFO [config] Configuring app: sibc/ejb/7.0.0/ear 18:52:08,936 INFO [OpenEJB] Auto-deploying ejb My: EjbDeployment (deployment-id=GeneralEJB.jar/My) 18:52:09,281 INFO [config] Loaded Module: sibc/ejb/7.0.0/ear 18:52:11,467 INFO [Enhance] You have enabled runtime enhancement, but have not specified the set of persistent classes. OpenJPA must look for metadata for every loaded class, which might increase class load times significantly. 18:52:11,977 INFO [startup] Assembling app: /Users/kevan/geronimo/ server/branches/2.0/target/geronimo-jetty6-jee5-2.0.2-SNAPSHOT/var/ temp/geronimo-deploymentUtil14898.jar 18:52:12,440 INFO [startup] Jndi(name=GeneralEJB.jar/My/ ejbs.MyHome) -- Ejb(deployment-id=GeneralEJB.jar/My) 18:52:12,447 INFO [startup] Created Ejb(deployment- id=GeneralEJB.jar/My, ejb-name=My, container=Default Stateless Container) Note the different JNDI names... Looks like there's a change there (value of interfaceClass) I had thought went in before 2.0.1 was shipped. The interfaceClass variable now refers to the interface you get when you do a lookup, so the EJBHome, EJBLocalHome or business interface such that if you set your jndiname format to simply {interfaceClass} and did something like this in code: MyHome home = (MyHome) ctx.lookup(MyHome.class.getName()); It would work. Or if you wanted to implement a java generic service- locator in you could set your jndiname format to something like {ejbName}/{interfaceClass} you could do: public T T getComponent(String ejbName, ClassT type) { return (T)ctx.lookup(ejbName+/+type.getName()); } MyHome home = getComponent(FooBean, MyHome.class); You get the idea. Anyway, it's up to us how we want to deal with this in Geronimo. It's actually possible for us to replace this part of the system and plugin in something that does whatever we like. We could go with the change now and warn users, we could grab a copy of the old formatter and plug it in replacing the updated formatter and use it till 2.0.x is done (or longer i guess), or provide some other custom option. (fyi, all of this is doable with trunk or 3.0-beta-1) Anyone have any preferences or thoughts? -David
[BUILD] 2.0: Failed for Revision: 580192
OpenEJB trunk at 580189 Geronimo Revision: 580192 built with tests included See the full build-2200.log file at http://people.apache.org/~prasad/binaries/2.0/20070927/build-2200.log Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/xbean/xbean-naming/3.1/xbean-naming-3.1.jar [WARNING] Unable to get resource 'org.apache.xbean:xbean-naming:jar:3.1' from repository apache-incubating-repository (http://people.apache.org/repo/m2-incubating-repository) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/xbean/xbean-naming/3.1/xbean-naming-3.1.jar [WARNING] Unable to get resource 'org.apache.xbean:xbean-naming:jar:3.1' from repository tomcat-private-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/xbean/xbean-naming/3.1/xbean-naming-3.1.jar [WARNING] Unable to get resource 'org.apache.xbean:xbean-naming:jar:3.1' from repository openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/) Downloading: http://repo1.maven.org/maven2/org/apache/xbean/xbean-naming/3.1/xbean-naming-3.1.jar 47K downloaded Downloading: http://download.java.net/maven/1//org.apache.axis2/jars/axis2-jaxws-api-1.3.jar [WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:1.3' from repository java.net (http://download.java.net/maven/1/) Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar [WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:1.3' from repository apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar [WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:1.3' from repository apache-incubating-repository (http://people.apache.org/repo/m2-incubating-repository) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar [WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:1.3' from repository tomcat-private-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar [WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:1.3' from repository openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/) Downloading: http://repo1.maven.org/maven2/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar 28K downloaded Downloading: http://download.java.net/maven/1//com.sun.xml.bind/jars/jaxb-impl-2.0.3.jar 765K downloaded Downloading: http://download.java.net/maven/1//javax.xml.bind/jars/jaxb-api-2.0.jar 72K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-interceptor_3.0_spec-1.0.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-interceptor_3.0_spec:jar:1.0' from repository java.net (http://download.java.net/maven/1/) Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-interceptor_3.0_spec:jar:1.0' from repository apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-interceptor_3.0_spec:jar:1.0' from repository apache-incubating-repository (http://people.apache.org/repo/m2-incubating-repository) Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-interceptor_3.0_spec:jar:1.0' from repository tomcat-private-repository (http://tomcat.apache.org/dev/dist/m2-repository) Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-interceptor_3.0_spec:jar:1.0' from repository openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/) Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar 8K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-j2ee-deployment_1.1_spec-1.1.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-j2ee
[BUILD] 2.1: Failed for Revision: 580193
OpenEJB trunk at 580189 Geronimo Revision: 580193 built with tests included See the full build-2200.log file at http://people.apache.org/~prasad/binaries/trunk/20070927/build-2200.log [INFO] snapshot org.apache.openejb:openejb-server:3.0.0-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.openejb:openejb-server:3.0.0-SNAPSHOT: checking for updates from apache.snapshots [INFO] snapshot org.apache.openejb:openejb-ejbd:3.0.0-SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.openejb:openejb-ejbd:3.0.0-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.openejb:openejb-ejbd:3.0.0-SNAPSHOT: checking for updates from apache.snapshots Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/javamail/geronimo-javamail_1.4_mail/1.3-SNAPSHOT/geronimo-javamail_1.4_mail-1.3-20070925.091916-1.jar 306K downloaded Downloading: http://download.java.net/maven/1//org.apache.axis2/jars/axis2-jaxws-api-1.3.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar Downloading: http://repo1.maven.org/maven2/org/apache/axis2/axis2-jaxws-api/1.3/axis2-jaxws-api-1.3.jar 28K downloaded Downloading: http://download.java.net/maven/1//org.codehaus.swizzle/jars/swizzle-stream-1.0.1.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar Downloading: http://repo1.maven.org/maven2/org/codehaus/swizzle/swizzle-stream/1.0.1/swizzle-stream-1.0.1.jar 42K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-interceptor_3.0_spec-1.0.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-interceptor_3.0_spec/1.0/geronimo-interceptor_3.0_spec-1.0.jar 8K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-ws-metadata_2.0_spec-1.1.1.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-ws-metadata_2.0_spec/1.1.1/geronimo-ws-metadata_2.0_spec-1.1.1.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/geronimo/specs/geronimo-ws-metadata_2.0_spec/1.1.1/geronimo-ws-metadata_2.0_spec-1.1.1.jar Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/geronimo/specs/geronimo-ws-metadata_2.0_spec/1.1.1/geronimo-ws-metadata_2.0_spec-1.1.1.jar Downloading: http://svn.apache.org/repos/asf/openejb/repo//org/apache/geronimo/specs/geronimo-ws-metadata_2.0_spec/1.1.1/geronimo-ws-metadata_2.0_spec-1.1.1.jar Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-ws-metadata_2.0_spec/1.1.1/geronimo-ws-metadata_2.0_spec-1.1.1.jar 14K downloaded Downloading: http://download.java.net/maven/1//activemq/jars/jmdns-1.0-RC2.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//activemq/jmdns/1.0-RC2/jmdns-1.0-RC2.jar Downloading: http://people.apache.org/repo/m2-incubating-repository/activemq/jmdns/1.0-RC2/jmdns-1.0-RC2.jar Downloading: http://repo1.maven.org/maven2/activemq/jmdns/1.0-RC2/jmdns-1.0-RC2.jar 80K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-j2ee-deployment_1.1_spec-1.1.jar Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-j2ee-deployment_1.1_spec/1.1/geronimo-j2ee-deployment_1.1_spec-1.1.jar Downloading
Tranql connectors released
After the recent tranql-oracle bug fix for non-spec-compliant lack of commit-on-setting autocommit I've done a bunch of cleanup in the tranql connectors: - updated license headers to refer to the tranql team rather than any particular contributor (changed after consultation with Jeremy and Matt) - use maven-remote-resources-plugin to install LiCENSE and a generated NOTICE file into every artifact (most were missing at least one of these) - regularize the directory structure to match the project names - and finally a code change... eliminate duplicate and unused MCF config-properties. I've now released new copies of all the connectors: base: 1.4 db2: 1.1 derby: 1.4 mysql: 1.0 oracle: 1.3 postgresql: 1.0 These ought to be getting to the maven central repo shortly and I will work on updating geronimo to use and include all of these. thanks david jencks
Re: [DISCUSS] G 2.0.2 Release plan
On Sep 27, 2007, at 4:13 PM, Kevan Miller wrote: On Sep 26, 2007, at 7:30 PM, Kevan Miller wrote: On Sep 25, 2007, at 4:08 PM, Donald Woods wrote: OK, I'm done updating the 2.0.x closed issues (sorry for all the JIRA emails.) The only one I couldn't figure out, was: https://issues.apache.org/jira/browse/GERONIMO-3423 Donald, Thanks a bunch for going through all of those Jiras! David Blevins, Are we missing 3423 in branches/2.0? Heh. Looks like I merged the change to branches/2.0 in revision 570950 -- http://svn.apache.org/viewvc?view=revrevision=570950. :) -David
[DISCUSS] Geronimo Eclipse Plugin 2.0.1 Release plan
Hi, I would like to starting discussing what we think should be included in the 2.0.1 release of the Geronimo Eclipse Plugin. I have some very preliminary thoughts that I have listed below but would like to encourage input from others. My initial thoughts are: 1. High priority JIRAs 2. Inclusion of the latest WTP release candidate 3. Build and test infrastructure improvements (e.g., build cleanup/improvements, execution of testcases during the build, a testsuite framework for the plugin, and a useful set of samples). 4. Full support for the Geronimo 2.0 deployment plans -- Thanks, Tim McConnell
Re: Geronimo box on Download page still says 1.1
OK, after dusting off my old and very basic photoshop skills, and following the idea Shiva pointed out, I created a new template for the software box. It has some minor differences which I think makes it look a little bit better. The good thing is that now we have the .psd source files and I tried to be as clear as I could with the labeling the layers. I committed the new templates and samples here. https://svn.apache.org/repos/asf/geronimo/site/trunk/art/sandbox/Hernan/ Cheers! Hernan Hernan Cunico wrote: g, reading those tutorials make it look so simple, why I didn't think about using those features in PS before. :-P Good catch Shiva, thanks for the pointer. I'll work on some .psd and commit them soon. Cheers! Hernan Shiva Kumar H R wrote: Yes Hernan, let's create our own boxes. Found these useful tutorials upon Google search for software box: http://tutorialblog.org/create-a-software-box/ http://tutorialblog.org/create-a-software-box/ http://www.designtutorials.info/software-box-design/ Adobe Photoshop is used in both the tutorials. - Shiva On 9/26/07, *Hernan Cunico* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Shiva, The .psd you see there are the templates we used as guidelines long time ago then we overhauled the whole site. We don't have the source files for the boxed images and I have no idea what software was used to create them. We rely on asking other projects to help us with this update. I asked several times what was the software used but never get a reply. I don't check all the commits and I was certainly unaware that those files got finally committed. If we can't get the source nor the details on how these boxed images got created then we should consider creating a new set of images. What you guys think? Cheers! Hernan Shiva Kumar H R wrote: I also see some .psd files! in the same location. Must be the source for those boxes. Hernan can you try opening them with your Adobe Photoshop? - Shiva On 9/26/07, * Vamsavardhana Reddy* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hernan, I see some 2.0 box images at https://svn.apache.org/repos/asf/geronimo/site/trunk/art https://svn.apache.org/repos/asf/geronimo/site/trunk/art and they have been there since end of March!! Can you update the downloads page to show a 2.0 box? Vamsi On 8/22/07, *Hernan Cunico* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I've been trying for ages to get these updated. I asked folks from other projects using similar boxes but couldn't figure out what software they were using. All I have is the Photoshop suit but I'm sure those were created with something else. Cheers! Hernan Matt Hogstrom wrote: Does anyone know how to get an updated box for Geronimo that says 2.0.1? Since its the first thing people see on that page seems like it would make more sense for the release number to be the most recent. I'm happy to do it but not sure what software was used.