ServiceMix and WebDav support
Hi! I'm seraching for a developer that can realize the below: I know that ServiceMix provide a file endpoint and a vfs (including WebDav) endpoint. My objective is to have a ServiceMix server that read and write files between: - Windows folder to WebDav server - WebDav server to Windows folder - Windows folder to Windows folder - WebDav server to WebDav server Based on my knowledge, the above are kind of activities that ServiceMix is able to do, after the setup of configurationf files. The work I'm asking to someone to do is to set the right configuration files to realize the above jobs. Please, could you tell me more? Waiting . Sincerely, Ivano Carrara -- View this message in context: http://www.nabble.com/ServiceMix-and-WebDav-support-tf3334693s12049.html#a9273246 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: Usage of lightweight components?
FYI, the servicemix-bean component can act as a complete replacement of the lightweight components / lightweight container, while being a compliant SE. I have began to document it: http://cwiki.apache.org/SM/servicemix-bean.html The possibilities of this component are endless. Especially if we can find a way to use the concept of BeanFlow there (or maybe something alike with the use of annotations) ... On 3/1/07, Terry Cox [EMAIL PROTECTED] wrote: What are the advantages of using 'real' components? It is very simple to build a single business story in a LW manner, however there are constraints upon the way you can deploy LW components. Dependencies of LW components must be managed manually and all component definitions are in the same servicemix.xml file. Once you start to reach an environment where you have multiple, independent business stories , each deployed with their own lifecycle, a mechanism is required to simplify deployment and management. Full components can be deployed using the JBI Service Unit / Service Assembly pattern and each SA can be managed independently. -- Terry Cox Meta-Concepts Ltd -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
[jira] Resolved: (SM-856) Add a marshaler to the servicemix-http component that handles Java serialization
[ https://issues.apache.org/activemq/browse/SM-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Snyder resolved SM-856. - Resolution: Fixed Committed: [r511025|http://svn.apache.org/viewvc?view=revrevision=511025] [r511046|http://svn.apache.org/viewvc?view=revrevision=511046] [r511056|http://svn.apache.org/viewvc?view=revrevision=511056] [r511213|http://svn.apache.org/viewvc?view=revrevision=511213] [r512040|http://svn.apache.org/viewvc?view=revrevision=512040] [r512040|http://svn.apache.org/viewvc?view=revrevision=512040] [r513438|http://svn.apache.org/viewvc?view=revrevision=513438] Add a marshaler to the servicemix-http component that handles Java serialization - Key: SM-856 URL: https://issues.apache.org/activemq/browse/SM-856 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Reporter: Bruce Snyder Fix For: 3.2 This will allow the Spring HTTP remoting to be used as a client to initiate requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
we need to use the 2.0 jaxb api and jaxws api specs
There's been some speculation about whether the 2.1 jaxb api and jaxws api specs are compliant according to the current tck. There might be an upgrade setting somewhere that I haven't found yet, but so far the 2.1 specs give signature errors, so we'll have to use the 2.0 specs for now. thanks david jencks
[jira] Created: (SM-861) servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync
servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync Key: SM-861 URL: https://issues.apache.org/activemq/browse/SM-861 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-861) servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync
[ https://issues.apache.org/activemq/browse/SM-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38636 ] Guillaume Nodet commented on SM-861: Author: gnodet Date: Fri Mar 2 00:07:43 2007 New Revision: 513653 URL: http://svn.apache.org/viewvc?view=revrev=513653 Log: SM-861: servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync Modified: incubator/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/AsyncBaseLifeCycle.java incubator/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/EndpointDeliveryChannel.java incubator/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/ServiceMixComponent.java servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync Key: SM-861 URL: https://issues.apache.org/activemq/browse/SM-861 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2501) Unable to deploy database pools
[ https://issues.apache.org/jira/browse/GERONIMO-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477221 ] jorge aguilera commented on GERONIMO-2501: -- If you use Firefox (2.0.0.2) DatabaseWizard crash always (show plan, save, ...) But if you use IExplore (7.0) it works fine. Unable to deploy database pools --- Key: GERONIMO-2501 URL: https://issues.apache.org/jira/browse/GERONIMO-2501 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: databases Affects Versions: 1.1.1 Environment: Mac OS x (version 10.4.8) Reporter: David Chudnow Priority: Critical Fix For: 1.2, 2.0 After completing the informaion and testing the connection I get the following when attempting to deploy either an oracle or sql server db pool 10:36:49,635 ERROR [[DBWizard]] Servlet.service() for servlet DBWizard threw exception java.lang.NullPointerException at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.save(DatabasePoolPortlet.java:873) at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.processAction(DatabasePoolPortlet.java:338) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:163) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at org.apache.pluto.portalImpl.Servlet.doPost(Servlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:613) 10:36:49,638 ERROR [Servlet] Exception caught: java.lang.NullPointerException at
[jira] Resolved: (SM-861) servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync
[ https://issues.apache.org/activemq/browse/SM-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-861. Resolution: Fixed Author: gnodet Date: Fri Mar 2 00:14:12 2007 New Revision: 513655 URL: http://svn.apache.org/viewvc?view=revrev=513655 Log: SM-861: servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync Modified: incubator/servicemix/branches/servicemix-3.1/common/servicemix-common/src/main/java/org/apache/servicemix/common/AsyncBaseLifeCycle.java incubator/servicemix/branches/servicemix-3.1/common/servicemix-common/src/main/java/org/apache/servicemix/common/EndpointDeliveryChannel.java incubator/servicemix/branches/servicemix-3.1/common/servicemix-common/src/main/java/org/apache/servicemix/common/ServiceMixComponent.java servicemix-common does not properly set the correlationId for exchanges that are sent using sendSync Key: SM-861 URL: https://issues.apache.org/activemq/browse/SM-861 Project: ServiceMix Issue Type: Bug Components: servicemix-common Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-860) EndpointReferenceBuilder.getReference() should cache its DocumentBuilderFactory instance
[ https://issues.apache.org/activemq/browse/SM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-860. Resolution: Fixed Fix Version/s: 3.2 Assignee: Guillaume Nodet Alex, thx for this patch. I have slightly modified it to allow more reuse amongst different threads, but the result should be the same :-) Author: gnodet Date: Fri Mar 2 01:12:08 2007 New Revision: 513670 URL: http://svn.apache.org/viewvc?view=revrev=513670 Log: SM-860: EndpointReferenceBuilder.getReference() should cache its DocumentBuilderFactory instance Modified: incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/servicedesc/EndpointReferenceBuilder.java incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/util/DOMUtil.java Author: gnodet Date: Fri Mar 2 01:15:03 2007 New Revision: 513673 URL: http://svn.apache.org/viewvc?view=revrev=513673 Log: SM-860: EndpointReferenceBuilder.getReference() should cache its DocumentBuilderFactory instance Modified: incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/servicedesc/EndpointReferenceBuilder.java incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/util/DOMUtil.java EndpointReferenceBuilder.getReference() should cache its DocumentBuilderFactory instance Key: SM-860 URL: https://issues.apache.org/activemq/browse/SM-860 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Alex Boisvert Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 Attachments: EndpointReferenceBuilder.patch.txt Doing performance testing on Apache Ode, I saw the following call stack: pool-1-thread-31 prio=1 tid=0x975717a8 nid=0x46df waiting for monitor entry [0x9e2f4000..0x9e2f4e60] at org.apache.xbean.classloader.UrlResourceFinder.findResource(UrlResourceFinder.java:91) - waiting to lock 0xa65d5a18 (a java.lang.Object) at org.apache.xbean.classloader.JarFileClassLoader$3.run(JarFileClassLoader.java:153) at java.security.AccessController.doPrivileged(Native Method) at org.apache.xbean.classloader.JarFileClassLoader.findResource(JarFileClassLoader.java:151) at org.apache.xbean.classloader.MultiParentClassLoader.getResource(MultiParentClassLoader.java:246) at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159) at javax.xml.parsers.SecuritySupport$4.run(SecuritySupport.java:72) at java.security.AccessController.doPrivileged(Native Method) at javax.xml.parsers.SecuritySupport.getResourceAsStream(SecuritySupport.java:65) at javax.xml.parsers.FactoryFinder.findJarServiceProvider(FactoryFinder.java:213) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98) at org.apache.servicemix.jbi.servicedesc.EndpointReferenceBuilder.getReference(EndpointReferenceBuilder.java:34) at org.apache.servicemix.jbi.servicedesc.InternalEndpoint.getAsReference(InternalEndpoint.java:69) at org.apache.ode.jbi.JbiEndpointReference.toXML(JbiEndpointReference.java:64) at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.invoke(BpelRuntimeContextImpl.java:761) at org.apache.ode.bpel.runtime.INVOKE.run(INVOKE.java:96) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451) at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139) at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:805) at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:310) at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:311) at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:386) at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.doExecute(QuartzSchedulerImpl.java:340) at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.access$000(QuartzSchedulerImpl.java:59) at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl$1$1.call(QuartzSchedulerImpl.java:223) at
[jira] Created: (SM-862) Possible problem when @WebMethod returns an empty string for the operation name
Possible problem when @WebMethod returns an empty string for the operation name --- Key: SM-862 URL: https://issues.apache.org/activemq/browse/SM-862 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Affects Versions: 3.1 Reporter: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-862) Possible problem when @WebMethod returns an empty string for the operation name
[ https://issues.apache.org/activemq/browse/SM-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-862. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Fri Mar 2 01:29:52 2007 New Revision: 513677 URL: http://svn.apache.org/viewvc?view=revrev=513677 Log: SM-862: Possible when @WebMethod return an empty string for the operation name Modified: incubator/servicemix/trunk/deployables/serviceengines/servicemix-jsr181/src/main/java/org/apache/servicemix/jsr181/xfire/ServiceFactoryHelper.java Author: gnodet Date: Fri Mar 2 01:31:36 2007 New Revision: 513678 URL: http://svn.apache.org/viewvc?view=revrev=513678 Log: SM-862: Possible when @WebMethod return an empty string for the operation name Modified: incubator/servicemix/branches/servicemix-3.1/deployables/serviceengines/servicemix-jsr181/src/main/java/org/apache/servicemix/jsr181/xfire/ServiceFactoryHelper.java Possible problem when @WebMethod returns an empty string for the operation name --- Key: SM-862 URL: https://issues.apache.org/activemq/browse/SM-862 Project: ServiceMix Issue Type: Bug Components: servicemix-jsr181 Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-863) Generated ids are too long, it may cause problems when using them in databases as indexes
Generated ids are too long, it may cause problems when using them in databases as indexes - Key: SM-863 URL: https://issues.apache.org/activemq/browse/SM-863 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] 2.0-M3 Release
+1 Jacek On 3/1/07, Matt Hogstrom [EMAIL PROTECTED] wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http:// people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and running DayTrader and now its your turn. This vote will conclude Saturday at 1800 Eastern time. -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: mx4j dependencies
On Mar 1, 2007, at 4:04 PM, Dain Sundstrom wrote: * modules/geronimo-jetty6/src/test/java/org/apache/geronimo/ jetty6/ClassLoaderTest.java (attempts to use mx4j.MBeanDescription to test classloading stuff) Not sure what to do about the later... or even if anything needs to be done. I'd just say remove the test. This test doesn't actually fail with the mx4j deps removed from the project. So either is picking up mx4j somewhere (that isn't getting included in the assembly, cause I can't find it there... though didn't look too hard for it), or the test is disabled, or its not testing anything useful... or its a broken test... or i've been sucked into a biiaaar universe. --jason
[jira] Resolved: (SM-863) Generated ids are too long, it may cause problems when using them in databases as indexes
[ https://issues.apache.org/activemq/browse/SM-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-863. Resolution: Fixed Author: gnodet Date: Tue Feb 27 01:24:56 2007 New Revision: 512188 URL: http://svn.apache.org/viewvc?view=revrev=512188 Log: Fix build by reducing the length of the generated IDs Modified: incubator/servicemix/trunk/core/servicemix-services/src/main/java/org/apache/servicemix/id/IdGenerator.java Author: gnodet Date: Fri Mar 2 02:07:24 2007 New Revision: 513684 URL: http://svn.apache.org/viewvc?view=revrev=513684 Log: SM-863: Generated ids are too long Modified: incubator/servicemix/trunk/core/servicemix-services/src/main/java/org/apache/servicemix/id/IdGenerator.java Author: gnodet Date: Fri Mar 2 02:12:48 2007 New Revision: 513687 URL: http://svn.apache.org/viewvc?view=revrev=513687 Log: SM-863: Generated ids are too long Modified: incubator/servicemix/branches/servicemix-3.1/core/servicemix-services/src/main/java/org/apache/servicemix/id/IdGenerator.java Generated ids are too long, it may cause problems when using them in databases as indexes - Key: SM-863 URL: https://issues.apache.org/activemq/browse/SM-863 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 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: (GERONIMO-2848) @WebServiceRef annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMO-2848: Attachment: GERONIMO-2848-1.patch Support for @WebServiceRef/@WebServiceRefs annotations added. Requires David Jencks review before it gets commited. @WebServiceRef annotation support - Key: GERONIMO-2848 URL: https://issues.apache.org/jira/browse/GERONIMO-2848 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Tim McConnell Assigned To: Tim McConnell Attachments: GERONIMO-2848-1.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38644 ] Guillaume Nodet commented on SM-841: We have discussed that on IRC. Is this still an issue ? The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1.1 Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: mx4j dependencies
The tests have been disabled (the names starts with xtest)... Thanks Anita --- Jason Dillon [EMAIL PROTECTED] wrote: On Mar 1, 2007, at 4:04 PM, Dain Sundstrom wrote: * modules/geronimo-jetty6/src/test/java/org/apache/geronimo/ jetty6/ClassLoaderTest.java (attempts to use mx4j.MBeanDescription to test classloading stuff) Not sure what to do about the later... or even if anything needs to be done. I'd just say remove the test. This test doesn't actually fail with the mx4j deps removed from the project. So either is picking up mx4j somewhere (that isn't getting included in the assembly, cause I can't find it there... though didn't look too hard for it), or the test is disabled, or its not testing anything useful... or its a broken test... or i've been sucked into a biiaaar universe. --jason Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com
Re: [VOTE] Geronimo web site update
+1 Cheers Anita --- Hernan Cunico [EMAIL PROTECTED] wrote: Folks, this vote is for moving the authoring of Geronimo's web site over Confluence. This mean that we will no longer use the anakia, xdocs and ant scripts to generate the web site, instead we will use Confluence. There is a GMOxSITE space in the cwiki site that only Geronimo committers can edit, this space will get automatically exported and massaged with a presentation template over geronimo.apache.org The source of the web site will remain in Confluence, svn repo will hold a copy of the HTML version. The other resources we serve from geronimo.apache.org such as plugins, schemas, redirects, etc. will remain unaffected. This vote will end this Saturday March 3rd at 1800 Eastern time. [ ] +1 Let's move the authoring over Confluence. [ ] 0 No opinion. [ ] -1 Do not change the authoring to Confluence, stay with ant scripts and xdocs. Cheers! Hernan Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather
[jira] Commented: (GERONIMO-2921) Tomcat does not register web service url mappings when web.xml is not present
[ https://issues.apache.org/jira/browse/GERONIMO-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477299 ] Jeff Genender commented on GERONIMO-2921: - Can you provide a simple test case for this? Tomcat does not register web service url mappings when web.xml is not present - Key: GERONIMO-2921 URL: https://issues.apache.org/jira/browse/GERONIMO-2921 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor Here's some background info. The web.xml file is now optional for JAX-WS POJO web services. In such cases, there are certain rules on how the web.xml should get updated. That is, appropriate servlet and servlet-mapping elements should be inserted into the web.xml. When I update the in-memory representation of the web.xml with the appropriate entires, everything works just fine on Jetty. However, with Tomcat, it seems like the url-mappings for the web services do not get registered. Everything else is fine, e.g. the web services gbeans get initialized, etc. and I can access a JSP deployed in the same war as the web services. After a bit of debugging I see that GeronimoStandardContext.addChild() is not called if the web.xml file is not present even though the in-memory representation of the DD is updated correctly. So somehow I think the in-memory representation of the DD is not being passed around correctly. Here's a stack trace when web.xml file is present and when addChild() is called: System Thread [RMI TCP Connection(9)-192.168.1.102] (Suspended (breakpoint at line 217 in GeronimoStandardContext)) GeronimoStandardContext.addChild(Container) line: 217 GeneratedMethodAccessor201.invoke(Object, Object[]) line: not available DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 IntrospectionUtils.callMethod1(Object, String, Object, String, ClassLoader) line: 899 SetNextRule.end() line: 193 SetNextRule(Rule).end(String, String) line: 229 Digester.endElement(String, String, String) line: 1058 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).endElement(QName, Augmentations) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanEndElement() line: not available [local variables unavailable] XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragmentScannerImpl$FragmentContentDispatcher).dispatch(boolean) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: not available SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not available Digester.parse(InputSource) line: 1562 ContextConfig.applicationWebConfig() line: 369 ContextConfig.start() line: 1060 ContextConfig.lifecycleEvent(LifecycleEvent) line: 261 LifecycleSupport.fireLifecycleEvent(String, Object) line: 120 GeronimoStandardContext(StandardContext).start() line: 4238 GeronimoStandardContext.access$201(GeronimoStandardContext) line: 66 GeronimoStandardContext$SystemMethodValve.invoke(Request, Response) line: 334 GeronimoBeforeAfterValve.invoke(Request, Response) line: 47 GeronimoStandardContext.start() line: 189 StandardHost(ContainerBase).addChildInternal(Container) line: 760 StandardHost(ContainerBase).addChild(Container) line: 740 StandardHost.addChild(Container) line: 525 TomcatContainer.addContext(TomcatContext) line: 331 TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(int, Object, Object[]) line: not available FastMethod.invoke(Object, Object[]) line: 53 FastMethodInvoker.invoke(Object, Object[]) line: 38 GBeanOperation.invoke(Object, Object[]) line: 127 GBeanInstance.invoke(int, Object[]) line: 820 RawInvoker.invoke(int, Object[]) line: 57 RawOperationInvoker.invoke(AbstractName, Object[]) line: 35 ProxyMethodInterceptor.intercept(Object, Method, Object[], MethodProxy) line: 96 TomcatContainer$$EnhancerByCGLIB$$d873f7e2.addContext(TomcatContext) line: not
[jira] Commented: (SM-858) Unable to access a JBIContainer using the supplied component context in various endpoints (i.e. JSR181)
[
https://issues.apache.org/activemq/browse/SM-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38645
]
Guillaume Nodet commented on SM-858:
Here is a workaround:
{code:lang=java}
public void setContext(ComponentContext context) {
this.context = context;
try {
Field field = context.getClass().getDeclaredField(context);
field.setAccessible(true);
Object smxContext = field.get(context);
field = smxContext.getClass().getDeclaredField(container);
field.setAccessible(true);
JBIContainer container = (JBIContainer) field.get(smxContext);
...
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
{code}
Unable to access a JBIContainer using the supplied component context in
various endpoints (i.e. JSR181)
---
Key: SM-858
URL: https://issues.apache.org/activemq/browse/SM-858
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core, servicemix-http, servicemix-jsr181
Affects Versions: 3.1
Reporter: jmdev
Following the instructions at
http://incubator.apache.org/servicemix/how-can-i-access-the-jbicontainer-from-inside-a-component-.html
a developer should be able to access the JBIContainer from within a JSR181
POJO. However, there is a ClassCastException due to the fact that the
ComponentContext returned is of type EndpointComponentContext. In turn, an
EndpointComponentContext does not provide access to it's internal context of
type ComponentContext, which allows the developer to get a reference to the
JBIContainer.
Temporary fix can be found here:
http://www.nabble.com/Error-Accessing-JBI-Container-from-JSR181-Component---Is-it-Possible--tf3281290s12049.html#a9132255
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-858) Unable to access a JBIContainer using the supplied component context in various endpoints (i.e. JSR181)
[
https://issues.apache.org/activemq/browse/SM-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-858.
Resolution: Fixed
Fix Version/s: 3.2
Assignee: Guillaume Nodet
The JBIContainer can now be injected on the POJO, the same way than the
ComponentContext.
public void setContainer(JBIContainer container) {
}
such a method will be called when the pojo is instanciated.
Author: gnodet
Date: Fri Mar 2 05:54:59 2007
New Revision: 513764
URL: http://svn.apache.org/viewvc?view=revrev=513764
Log:
SM-858: The JBIContainer can now be injected on the POJO
Modified:
incubator/servicemix/trunk/deployables/serviceengines/servicemix-jsr181/src/main/java/org/apache/servicemix/jsr181/Jsr181Endpoint.java
Unable to access a JBIContainer using the supplied component context in
various endpoints (i.e. JSR181)
---
Key: SM-858
URL: https://issues.apache.org/activemq/browse/SM-858
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core, servicemix-http, servicemix-jsr181
Affects Versions: 3.1
Reporter: jmdev
Assigned To: Guillaume Nodet
Fix For: 3.2
Following the instructions at
http://incubator.apache.org/servicemix/how-can-i-access-the-jbicontainer-from-inside-a-component-.html
a developer should be able to access the JBIContainer from within a JSR181
POJO. However, there is a ClassCastException due to the fact that the
ComponentContext returned is of type EndpointComponentContext. In turn, an
EndpointComponentContext does not provide access to it's internal context of
type ComponentContext, which allows the developer to get a reference to the
JBIContainer.
Temporary fix can be found here:
http://www.nabble.com/Error-Accessing-JBI-Container-from-JSR181-Component---Is-it-Possible--tf3281290s12049.html#a9132255
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-841) The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section.
[ https://issues.apache.org/activemq/browse/SM-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38647 ] Jeff Puro commented on SM-841: -- Yes, this is still an issue. I have a potential fix for it, so I need to attach the patch files to this defect. Will do so in the next day or so. The servicemix-http provider endpoint does not properly handle web services that return faults with multiple elements in the detail section. Key: SM-841 URL: https://issues.apache.org/activemq/browse/SM-841 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.0.1, 3.1 Reporter: Jeff Puro Assigned To: Jeff Puro Fix For: 3.0.1, 3.1.1 Original Estimate: 2 hours Remaining Estimate: 2 hours The servicemix-http provider endpoint fails when a web service it calls returns a fault with multiple child elements in the detail section. The solution to this is when there are multiple elements, we should wrap them all in a root element so they get properly passed back as a fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2922) Deploy JAX-WS services without web.xml
Deploy JAX-WS services without web.xml -- Key: GERONIMO-2922 URL: https://issues.apache.org/jira/browse/GERONIMO-2922 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: webservices Reporter: Jarek Gawor The attached patch enables JAX-WS services to be deployed without web.xml file. Please note that this feature will only work on Jetty now as there are some Tomcat issues (https://issues.apache.org/jira/browse/GERONIMO-2921). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] VOTE J2G Conversion tool acceptance
any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: Filip, There are 6 items under Copyright and Verify distribution rights. Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under Verify distribution rights can be marked Not Applicable. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: Checked in. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip
[jira] Updated: (GERONIMO-2922) Deploy JAX-WS services without web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-2922: -- Attachment: GERONIMO-2922.patch Deploy JAX-WS services without web.xml -- Key: GERONIMO-2922 URL: https://issues.apache.org/jira/browse/GERONIMO-2922 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Reporter: Jarek Gawor Attachments: GERONIMO-2922.patch The attached patch enables JAX-WS services to be deployed without web.xml file. Please note that this feature will only work on Jetty now as there are some Tomcat issues (https://issues.apache.org/jira/browse/GERONIMO-2921). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2921) Tomcat does not register web service url mappings when web.xml is not present
[ https://issues.apache.org/jira/browse/GERONIMO-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-2921: -- Attachment: jaxws-war-2.0-SNAPSHOT.war Tomcat does not register web service url mappings when web.xml is not present - Key: GERONIMO-2921 URL: https://issues.apache.org/jira/browse/GERONIMO-2921 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor Attachments: jaxws-war-2.0-SNAPSHOT.war Here's some background info. The web.xml file is now optional for JAX-WS POJO web services. In such cases, there are certain rules on how the web.xml should get updated. That is, appropriate servlet and servlet-mapping elements should be inserted into the web.xml. When I update the in-memory representation of the web.xml with the appropriate entires, everything works just fine on Jetty. However, with Tomcat, it seems like the url-mappings for the web services do not get registered. Everything else is fine, e.g. the web services gbeans get initialized, etc. and I can access a JSP deployed in the same war as the web services. After a bit of debugging I see that GeronimoStandardContext.addChild() is not called if the web.xml file is not present even though the in-memory representation of the DD is updated correctly. So somehow I think the in-memory representation of the DD is not being passed around correctly. Here's a stack trace when web.xml file is present and when addChild() is called: System Thread [RMI TCP Connection(9)-192.168.1.102] (Suspended (breakpoint at line 217 in GeronimoStandardContext)) GeronimoStandardContext.addChild(Container) line: 217 GeneratedMethodAccessor201.invoke(Object, Object[]) line: not available DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 IntrospectionUtils.callMethod1(Object, String, Object, String, ClassLoader) line: 899 SetNextRule.end() line: 193 SetNextRule(Rule).end(String, String) line: 229 Digester.endElement(String, String, String) line: 1058 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).endElement(QName, Augmentations) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanEndElement() line: not available [local variables unavailable] XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragmentScannerImpl$FragmentContentDispatcher).dispatch(boolean) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: not available SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not available Digester.parse(InputSource) line: 1562 ContextConfig.applicationWebConfig() line: 369 ContextConfig.start() line: 1060 ContextConfig.lifecycleEvent(LifecycleEvent) line: 261 LifecycleSupport.fireLifecycleEvent(String, Object) line: 120 GeronimoStandardContext(StandardContext).start() line: 4238 GeronimoStandardContext.access$201(GeronimoStandardContext) line: 66 GeronimoStandardContext$SystemMethodValve.invoke(Request, Response) line: 334 GeronimoBeforeAfterValve.invoke(Request, Response) line: 47 GeronimoStandardContext.start() line: 189 StandardHost(ContainerBase).addChildInternal(Container) line: 760 StandardHost(ContainerBase).addChild(Container) line: 740 StandardHost.addChild(Container) line: 525 TomcatContainer.addContext(TomcatContext) line: 331 TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(int, Object, Object[]) line: not available FastMethod.invoke(Object, Object[]) line: 53 FastMethodInvoker.invoke(Object, Object[]) line: 38 GBeanOperation.invoke(Object, Object[]) line: 127 GBeanInstance.invoke(int, Object[]) line: 820 RawInvoker.invoke(int, Object[]) line: 57 RawOperationInvoker.invoke(AbstractName, Object[]) line: 35 ProxyMethodInterceptor.intercept(Object, Method, Object[], MethodProxy) line: 96 TomcatContainer$$EnhancerByCGLIB$$d873f7e2.addContext(TomcatContext)
[jira] Commented: (GERONIMO-2921) Tomcat does not register web service url mappings when web.xml is not present
[ https://issues.apache.org/jira/browse/GERONIMO-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477327 ] Jarek Gawor commented on GERONIMO-2921: --- First, https://issues.apache.org/jira/browse/GERONIMO-2922 needs to be applied. Second, deploy the attached .war file. If things are deployed and connected successfully the following urls should work fine: http://localhost:8080/jaxws-war-2.0-SNAPSHOT/SOAPService?wsdl http://localhost:8080/jaxws-war-2.0-SNAPSHOT/HelloServiceService?wsdl http://localhost:8080/jaxws-war-2.0-SNAPSHOT/EchoServiceService?wsdl Tomcat does not register web service url mappings when web.xml is not present - Key: GERONIMO-2921 URL: https://issues.apache.org/jira/browse/GERONIMO-2921 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor Attachments: jaxws-war-2.0-SNAPSHOT.war Here's some background info. The web.xml file is now optional for JAX-WS POJO web services. In such cases, there are certain rules on how the web.xml should get updated. That is, appropriate servlet and servlet-mapping elements should be inserted into the web.xml. When I update the in-memory representation of the web.xml with the appropriate entires, everything works just fine on Jetty. However, with Tomcat, it seems like the url-mappings for the web services do not get registered. Everything else is fine, e.g. the web services gbeans get initialized, etc. and I can access a JSP deployed in the same war as the web services. After a bit of debugging I see that GeronimoStandardContext.addChild() is not called if the web.xml file is not present even though the in-memory representation of the DD is updated correctly. So somehow I think the in-memory representation of the DD is not being passed around correctly. Here's a stack trace when web.xml file is present and when addChild() is called: System Thread [RMI TCP Connection(9)-192.168.1.102] (Suspended (breakpoint at line 217 in GeronimoStandardContext)) GeronimoStandardContext.addChild(Container) line: 217 GeneratedMethodAccessor201.invoke(Object, Object[]) line: not available DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 IntrospectionUtils.callMethod1(Object, String, Object, String, ClassLoader) line: 899 SetNextRule.end() line: 193 SetNextRule(Rule).end(String, String) line: 229 Digester.endElement(String, String, String) line: 1058 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).endElement(QName, Augmentations) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanEndElement() line: not available [local variables unavailable] XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragmentScannerImpl$FragmentContentDispatcher).dispatch(boolean) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: not available SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not available Digester.parse(InputSource) line: 1562 ContextConfig.applicationWebConfig() line: 369 ContextConfig.start() line: 1060 ContextConfig.lifecycleEvent(LifecycleEvent) line: 261 LifecycleSupport.fireLifecycleEvent(String, Object) line: 120 GeronimoStandardContext(StandardContext).start() line: 4238 GeronimoStandardContext.access$201(GeronimoStandardContext) line: 66 GeronimoStandardContext$SystemMethodValve.invoke(Request, Response) line: 334 GeronimoBeforeAfterValve.invoke(Request, Response) line: 47 GeronimoStandardContext.start() line: 189 StandardHost(ContainerBase).addChildInternal(Container) line: 760 StandardHost(ContainerBase).addChild(Container) line: 740 StandardHost.addChild(Container) line: 525 TomcatContainer.addContext(TomcatContext) line: 331 TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(int, Object, Object[]) line: not available FastMethod.invoke(Object, Object[]) line: 53 FastMethodInvoker.invoke(Object, Object[]) line: 38
[jira] Updated: (GERONIMO-2922) Deploy JAX-WS services without web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-2922: -- Attachment: GERONIMO-2922.patch Slightly updated patch (added .trim() in one place). Deploy JAX-WS services without web.xml -- Key: GERONIMO-2922 URL: https://issues.apache.org/jira/browse/GERONIMO-2922 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Reporter: Jarek Gawor Attachments: GERONIMO-2922.patch, GERONIMO-2922.patch The attached patch enables JAX-WS services to be deployed without web.xml file. Please note that this feature will only work on Jetty now as there are some Tomcat issues (https://issues.apache.org/jira/browse/GERONIMO-2921). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2922) Deploy JAX-WS services without web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Genender closed GERONIMO-2922. --- Resolution: Fixed Fix Version/s: 2.0-M3 Committed revision 513815. Deploy JAX-WS services without web.xml -- Key: GERONIMO-2922 URL: https://issues.apache.org/jira/browse/GERONIMO-2922 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: webservices Reporter: Jarek Gawor Fix For: 2.0-M3 Attachments: GERONIMO-2922.patch, GERONIMO-2922.patch The attached patch enables JAX-WS services to be deployed without web.xml file. Please note that this feature will only work on Jetty now as there are some Tomcat issues (https://issues.apache.org/jira/browse/GERONIMO-2921). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2921) Tomcat does not register web service url mappings when web.xml is not present
[ https://issues.apache.org/jira/browse/GERONIMO-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Genender reassigned GERONIMO-2921: --- Assignee: Jeff Genender Tomcat does not register web service url mappings when web.xml is not present - Key: GERONIMO-2921 URL: https://issues.apache.org/jira/browse/GERONIMO-2921 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor Assigned To: Jeff Genender Attachments: jaxws-war-2.0-SNAPSHOT.war Here's some background info. The web.xml file is now optional for JAX-WS POJO web services. In such cases, there are certain rules on how the web.xml should get updated. That is, appropriate servlet and servlet-mapping elements should be inserted into the web.xml. When I update the in-memory representation of the web.xml with the appropriate entires, everything works just fine on Jetty. However, with Tomcat, it seems like the url-mappings for the web services do not get registered. Everything else is fine, e.g. the web services gbeans get initialized, etc. and I can access a JSP deployed in the same war as the web services. After a bit of debugging I see that GeronimoStandardContext.addChild() is not called if the web.xml file is not present even though the in-memory representation of the DD is updated correctly. So somehow I think the in-memory representation of the DD is not being passed around correctly. Here's a stack trace when web.xml file is present and when addChild() is called: System Thread [RMI TCP Connection(9)-192.168.1.102] (Suspended (breakpoint at line 217 in GeronimoStandardContext)) GeronimoStandardContext.addChild(Container) line: 217 GeneratedMethodAccessor201.invoke(Object, Object[]) line: not available DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 IntrospectionUtils.callMethod1(Object, String, Object, String, ClassLoader) line: 899 SetNextRule.end() line: 193 SetNextRule(Rule).end(String, String) line: 229 Digester.endElement(String, String, String) line: 1058 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).endElement(QName, Augmentations) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanEndElement() line: not available [local variables unavailable] XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragmentScannerImpl$FragmentContentDispatcher).dispatch(boolean) line: not available XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: not available XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: not available SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: not available SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not available Digester.parse(InputSource) line: 1562 ContextConfig.applicationWebConfig() line: 369 ContextConfig.start() line: 1060 ContextConfig.lifecycleEvent(LifecycleEvent) line: 261 LifecycleSupport.fireLifecycleEvent(String, Object) line: 120 GeronimoStandardContext(StandardContext).start() line: 4238 GeronimoStandardContext.access$201(GeronimoStandardContext) line: 66 GeronimoStandardContext$SystemMethodValve.invoke(Request, Response) line: 334 GeronimoBeforeAfterValve.invoke(Request, Response) line: 47 GeronimoStandardContext.start() line: 189 StandardHost(ContainerBase).addChildInternal(Container) line: 760 StandardHost(ContainerBase).addChild(Container) line: 740 StandardHost.addChild(Container) line: 525 TomcatContainer.addContext(TomcatContext) line: 331 TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(int, Object, Object[]) line: not available FastMethod.invoke(Object, Object[]) line: 53 FastMethodInvoker.invoke(Object, Object[]) line: 38 GBeanOperation.invoke(Object, Object[]) line: 127 GBeanInstance.invoke(int, Object[]) line: 820 RawInvoker.invoke(int, Object[]) line: 57 RawOperationInvoker.invoke(AbstractName, Object[]) line: 35 ProxyMethodInterceptor.intercept(Object, Method, Object[], MethodProxy) line: 96
[jira] Commented: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477347 ] Paul McMahan commented on GERONIMO-2743: One of the questions on the IP clearance form is: Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. These java source files don't contain an ASF copyright header: src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/Anybody.java src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/DigestCallback.java src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/GeronimoLoginModule.java src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/GeronimoSimpleGroup.java src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/Nobody.java src/dependence-plugin/src/org/apache/apps/j2gmigrator/compatibility/PasswordHasher.java src2/ejb-migration-plugin/test/org/apache/apps/j2gmigrator/descriptors/ejb/TestEJBDescriptorTool.java src2/enterprise-migration-plugin/test/org/apache/apps/j2gmigrator/descriptors/app/TestApplicationDescriptorTool.java src2/web-migration-plugin/test/org/apache/apps/j2gmigrator/descriptors/web/TestWebDescriptorTool.java src2/xml-conversion-helper/test/org/apache/apps/j2gmigrator/descriptors/xmlutil/TestXMLConversionHelper.java src2/xml-conversion-helper/test/org/apache/apps/j2gmigrator/resources/xmlutil/test/XMLConvertionHelperTestCase.java Also, I noticed these non-java files don't contain an ASF copyright header: src/common/build.properties src/common/plugin.xml src/configurator/bin/com/ibm/j2g/Configurator.class src/dependence-plugin/build.properties src/dependence-plugin/plugin.xml src/dependence-plugin/src/org/apache/apps/j2gmigrator/source/dependence/class_analogies.properties src/dependence-plugin/src/org/apache/apps/j2gmigrator/source/dependence/compatible_sources.properties src/dependence-plugin/src/org/apache/apps/j2gmigrator/source/dependence/default_jars.properties src/descriptors-tool/build.properties src/descriptors-tool/plugin.xml src/descriptors-tool/schema/tool.migrations.exsd src/ejb-environment-plugin/build.properties src/ejb-environment-plugin/plugin.xml src/ejb-environment-plugin/src/org/apache/apps/j2gmigrator/sources/env/beans-interfaces.properties src/ejb-environment-plugin/src/org/apache/apps/j2gmigrator/sources/env/beans-references.properties src/ejb-environment-plugin/src/org/apache/apps/j2gmigrator/sources/env/beans-types.properties src/jasper-plugin/build.properties src/jasper-plugin/plugin.xml src/resources-tool/build.properties src/resources-tool/plugin.xml src/resources-tool/schema/tool.migrations.exsd src/scripts/j2g-configure.cmd src/scripts/jdesc2g.cmd src/scripts/jres2g.cmd src/scripts/jsrc2g.cmd src/sources-tool/build.properties src/sources-tool/plugin.xml src/sources-tool/schema/migrations.exsd src2/data-source-plugin/build.properties src2/data-source-plugin/plugin.xml src2/data-source-plugin/src/commons-logging.properties src2/data-source-plugin/test-apps/ds/hsqldb-ds.xml src2/data-source-plugin/test-apps/ds/hsqldb-geronimo-plan.xml src2/data-source-plugin/test-apps/ds/mysql-ds.xml src2/data-source-plugin/test-apps/ds/mysql-geronimo-plan.xml src2/data-source-plugin/test-apps/ds/oracle-ds.xml src2/data-source-plugin/test-apps/ds/oracle-geronimo-plan.xml src2/ejb-cmp-migration-plugin/build.properties src2/ejb-cmp-migration-plugin/plugin.xml src2/ejb-cmp-migration-plugin/src/commons-logging.properties src2/ejb-cmp-migration-plugin/test-resources/ejb-jar.xml src2/ejb-cmp-migration-plugin/test-resources/jbosscmp-jdbc.xml src2/ejb-migration-plugin/build.properties src2/ejb-migration-plugin/plugin.xml src2/ejb-migration-plugin/src/common-logging.properties src2/ejb-migration-plugin/test-resources/jboss.xml src2/enterprise-migration-plugin/.settings/org.eclipse.ltk.core.refactoring.prefs src2/enterprise-migration-plugin/build.properties src2/enterprise-migration-plugin/plugin.xml src2/enterprise-migration-plugin/src/commons-logging.properties src2/enterprise-migration-plugin/test-resources/geronimo-application.xml src2/enterprise-migration-plugin/test-resources/jboss-app.xml src2/jms-plugin/build.properties src2/jms-plugin/plugin.xml src2/jms-plugin/src/commons-logging.properties src2/jms-plugin/test-apps/jms/geronimo-jms-resource-plan.xml src2/jms-plugin/test-apps/jms/jbossmq-destinations-service.xml src2/jms-plugin/test-apps/jms/jms-ds.xml src2/jms-plugin/test-apps/jms/jms-geronimo-plan.xml src2/mail-plugin/build.properties src2/mail-plugin/plugin.xml src2/mail-plugin/src/commons-logging.properties src2/mail-plugin/test-apps/mail/err/mail-service.xml src2/mail-plugin/test-apps/mail/geronimo-mail-service.xml src2/mail-plugin/test-apps/mail/mail-geronimo-plan.xml src2/mail-plugin/test-apps/mail/mail-service.xml src2/security-plugin/build.properties src2/security-plugin/plugin.xml
Re: [RESULT] VOTE J2G Conversion tool acceptance
One of the remaining items on the IP clearance form is: Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. I updated https://issues.apache.org/jira/browse/GERONIMO-2743 with a list of files that don't contain an ASF copyright header. Best wishes, Paul On 3/2/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: Filip, There are 6 items under Copyright and Verify distribution rights. Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under Verify distribution rights can be marked Not Applicable. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: Checked in. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip
Re: [RESULT] VOTE J2G Conversion tool acceptance
Doing this today Filip. On Mar 2, 2007, at 10:20 AM, Filip Hanik - Dev Lists wrote: any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: Filip, There are 6 items under Copyright and Verify distribution rights. Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under Verify distribution rights can be marked Not Applicable. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: Checked in. thanks, dims On 2/26/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip
Re: [VOTE] 2.0-M3 Release
+1 Not being able to use database pool wizard was a minor annoyance. http://issues.apache.org/jira/browse/GERONIMO-2916 I was able to deploy from command line using bin\deploy. DB Manager on console is working fine. Thanks Anita --- Matt Hogstrom [EMAIL PROTECTED] wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http:// people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and running DayTrader and now its your turn. This vote will conclude Saturday at 1800 Eastern time. Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Re: MyFaces 1.2 for Geronimo 2.0?
Geronimo PMC is currently discussing general access to this list for ASF committers who have signed the NDA, and I expect that discussion will be resolved very soon. any news here ?
Re: MyFaces 1.2 for Geronimo 2.0?
I think the overall process is pretty much worked out now. You can start the process by sending a note to the Geronimo PMC (private@) requesting access to the TCK with a quick summary of your goals. Best wishes, Paul On 3/2/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Geronimo PMC is currently discussing general access to this list for ASF committers who have signed the NDA, and I expect that discussion will be resolved very soon. any news here ?
Re: [VOTE] 2.0-M3 Release
+1 Best wishes, chris Matt Hogstrom wrote: I have gotten past the hurdles and present for your reviewing pleasure Geronimo 2.0-M3. All assemblies as well as source are available. http://people.apache.org/~hogstrom/2.0-M3-rc1 I have tested a few of the assemblies by deploying and running DayTrader and now its your turn. This vote will conclude Saturday at 1800 Eastern time.
SystemDatabase
I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
IIRC, the derby.log was always in the bin directory. But then again, I could be wrong. Cheers Prasad On 3/2/07, Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
When I paid attention to this some time last year, it was in var\derby directory and derby.log was not turned on by default. Wonder if this is caused by a change in derby itself? Lin Prasad Kashyap wrote: IIRC, the derby.log was always in the bin directory. But then again, I could be wrong. Cheers Prasad On 3/2/07, Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek
Re: SystemDatabase
The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
Re: SystemDatabase
A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. Thanks Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: JAXB upgrade
At this time Geronimo can only certify with JAXB 2.0 and JAXWS 2.0. We're hoping that sun will update the tck to allow supporting the 2.1 specs, but as far as we can tell this has not yet happened. Getting information out of sun about this stuff can be difficult, but perhaps if we started now and now and are sufficiently persistent we will eventually find out something useful. Are the 2.1 spec versions officially released? Meanwhile we'd certainly appreciate it at Geronimo if you went back to the 2.0 spec versions for now. thanks david jencks On Mar 1, 2007, at 7:43 AM, Jarek Gawor wrote: Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm not sure how that affects things. Jarek On 3/1/07, Dan Diephouse [EMAIL PROTECTED] wrote: I'm happy to revert the change, but I think that we ultimately need it. I believe we're targeting JAX-WS 2.1 (we switched the API jar the other day), and that requires JAXB 2.1. There are many benefits from a user perspective in 2.1. For isntance it has a lot better functionality for things like WS-A and also makes it easier for people to use substitution types, which requires all sorts of hacks right now. Is Geronimo just looking to release JAX-WS 2.0 support or 2.1? Any idea if its possible to certify Geronimo with 2.1? Or does certification require 2.0? I'm not sure what the status is of the JAX-WS 2.1 TCK either. - Dan (I CC'd [EMAIL PROTECTED] in, hope thats ok) On 2/28/07, Jarek Gawor [EMAIL PROTECTED] wrote: Hi again, CXF code was recently upgraded to JAXB 2.1 and so I tired to figure out what sort of implications that might have on Geronimo. First of all, JAXB is one of those libraries that is shared by all applications in the Geronimo server. We also have a bunch of different components using JAXB to do deployment descriptor parsing, etc. So if we upgrade JAXB in G, we have to retest all these subcomponents to make sure they are ok. And I think in general that should be ok but potentially time consuming. Another potential issue that somebody raised was TCK testing. We don't know what happens if for example TCK expects JAXB 2.0 API but gets JAXB 2.1 API/implementation. Maybe nothing (as things supposed to be backwards compatible) but maybe it blows up. That's another thing for us to worry about. So, if this JAXB upgrade is not a critical issue for CXF would it be possible to switch back to JAXB 2.0? Thanks, Jarek -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Jars in the dist
Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar #2) We need to get rid of activation-1.1.jar from Sun. (i will have to change axis2 pom's) #3) We could use saaj-api and jaxws-api jars from Axis2 instead of the sun versions #4) We need to get rid of mail-1.4.jar from Sun. (i will have to change axis2 pom's) #5) I guess xpp3-1.1.3.3.jar is needed by xstream-1.1.3.jar? #6) Do we really need to ship junit-3.8.1.jar? #7) comment in main pom.xml says that we can get rid of xml-apis-1.3.03.jar when we move to tomcat6. Should we clean it up? !-- This will go away when we move to tomcat6 -- dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version1.3.03/version /dependency #8) Has anyone compiled a list of the licenses corresponding to each jar? thanks, dims Here's the complete list: === activation-1.1.jar activeio-2.0-r118.jar activeio-core-3.0.0-incubator.jar activemq-core-4.1.0-incubator.jar activemq-ra-4.1.0-incubator.jar annogen-0.1.0.jar antlr-2.7.2.jar apache-ldapber-provider-0.9.2.jar apacheds-core-0.9.2.jar apacheds-shared-0.9.2.jar asm-2.2.3.jar asm-commons-2.2.3.jar asn1-ber-0.3.2.jar asn1-codec-0.3.2.jar asn1-der-0.3.2.jar axiom-api-SNAPSHOT.jar axiom-impl-SNAPSHOT.jar axis-1.4.jar axis2-adb-SNAPSHOT.jar axis2-java2wsdl-SNAPSHOT.jar axis2-jaxws-api-SNAPSHOT.jar axis2-jaxws-SNAPSHOT.jar axis2-kernel-SNAPSHOT.jar axis2-metadata-SNAPSHOT.jar backport-util-concurrent-2.2.jar bcel-5.2.jar castor-0.9.5.3.jar castor-1.0.5.jar cglib-nodep-2.1_3.jar client.jar commons-beanutils-1.6.1.jar commons-cli-1.0.jar commons-codec-1.3.jar commons-collections-3.1.jar commons-digester-1.8.jar commons-discovery-0.2.jar commons-fileupload-1.1.1.jar commons-httpclient-3.0.1.jar commons-io-1.1.jar commons-jexl-1.1.jar commons-lang-2.0.jar commons-logging-1.0.4.jar commons-primitives-20041207.202534.jar concurrent-1.3.4.jar cxf-api-2.0-incubator-RC-SNAPSHOT.jar cxf-common-utilities-2.0-incubator-RC-SNAPSHOT.jar cxf-metacode-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-bindings-soap-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-bindings-xml-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-core-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-databinding-jaxb-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-frontend-jaxws-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-frontend-simple-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-transports-http-2.0-incubator-RC-SNAPSHOT.jar cxf-tools-common-2.0-incubator-RC-SNAPSHOT.jar deployer.jar derby-10.2.2.0.jar derbyclient-10.2.2.0.jar derbynet-10.2.2.0.jar derbytools-10.2.2.0.jar dwr-1.1.1.jar geronimo-activation-2.0-SNAPSHOT.jar geronimo-activation_1.1_spec-1.0-SNAPSHOT.jar geronimo-activemq-gbean-2.0-SNAPSHOT.jar geronimo-activemq-gbean-management-2.0-SNAPSHOT.jar geronimo-annotation_1.0_spec-1.0.jar geronimo-axis-2.0-SNAPSHOT.jar geronimo-axis-builder-2.0-SNAPSHOT.jar geronimo-axis2-2.0-SNAPSHOT.jar geronimo-axis2-builder-2.0-SNAPSHOT.jar geronimo-client-2.0-SNAPSHOT.jar geronimo-client-builder-2.0-SNAPSHOT.jar geronimo-clustering-2.0-SNAPSHOT.jar geronimo-clustering-wadi-2.0-SNAPSHOT.jar geronimo-common-2.0-SNAPSHOT.jar geronimo-connector-2.0-SNAPSHOT.jar geronimo-connector-builder-2.0-SNAPSHOT.jar geronimo-console-core-2.0-SNAPSHOT.jar geronimo-console-framework-2.0-SNAPSHOT.jar geronimo-console-standard-2.0-SNAPSHOT.jar geronimo-converter-2.0-SNAPSHOT.jar geronimo-corba-2.0-SNAPSHOT.jar geronimo-corba-builder-2.0-SNAPSHOT.jar geronimo-core-2.0-SNAPSHOT.jar geronimo-cxf-2.0-SNAPSHOT.jar geronimo-cxf-builder-2.0-SNAPSHOT.jar geronimo-deploy-config-2.0-SNAPSHOT.jar geronimo-deploy-jsr88-2.0-SNAPSHOT.jar geronimo-deploy-jsr88-bootstrapper-2.0-SNAPSHOT.jar geronimo-deploy-tool-2.0-SNAPSHOT.jar geronimo-deployment-2.0-SNAPSHOT.jar geronimo-derby-2.0-SNAPSHOT.jar geronimo-directory-2.0-SNAPSHOT.jar geronimo-dojo-2.0-SNAPSHOT.jar geronimo-ejb_3.0_spec-1.0.jar geronimo-el_1.0_spec-1.0-SNAPSHOT.jar geronimo-hot-deploy-2.0-SNAPSHOT.jar geronimo-interceptor-2.0-SNAPSHOT.jar geronimo-interceptor_3.0_spec-1.0.jar geronimo-j2ee-2.0-SNAPSHOT.jar geronimo-j2ee-builder-2.0-SNAPSHOT.jar geronimo-j2ee-connector_1.5_spec-1.1.jar geronimo-j2ee-management_1.1_spec-1.0-SNAPSHOT.jar geronimo-j2ee-schema-2.0-SNAPSHOT.jar geronimo-jacc_1.1_spec-1.0-SNAPSHOT.jar geronimo-javaee-deployment_1.1MR3_spec-1.0-SNAPSHOT.jar geronimo-javamail_1.4_mail-1.1-SNAPSHOT.jar geronimo-jaxr_1.0_spec-1.1.jar geronimo-jaxrpc_1.1_spec-1.1.jar geronimo-jaxws-2.0-SNAPSHOT.jar geronimo-jaxws-builder-2.0-SNAPSHOT.jar geronimo-jetty6-2.0-SNAPSHOT.jar geronimo-jetty6-builder-2.0-SNAPSHOT.jar geronimo-jetty6-clustering-builder-wadi-2.0-SNAPSHOT.jar geronimo-jetty6-clustering-wadi-2.0-SNAPSHOT.jar geronimo-jms_1.1_spec-1.1.jar geronimo-jmx-remoting-2.0-SNAPSHOT.jar geronimo-jpa_3.0_spec-1.0.jar geronimo-jsp_2.1_spec-1.0-SNAPSHOT.jar geronimo-jta_1.1_spec-1.0.jar geronimo-kernel-2.0-SNAPSHOT.jar
Re: JAXB upgrade
At this time Geronimo can only certify with JAXB 2.0 and JAXWS 2.0. We're hoping that sun will update the tck to allow supporting the 2.1 specs, but as far as we can tell this has not yet happened. Getting information out of sun about this stuff can be difficult, but perhaps if we started now and now and are sufficiently persistent we will eventually find out something useful. Are the 2.1 spec versions officially released? Meanwhile we'd certainly appreciate it at Geronimo if you went back to the 2.0 spec versions for now. thanks david jencks On Mar 1, 2007, at 7:43 AM, Jarek Gawor wrote: Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm not sure how that affects things. Jarek On 3/1/07, Dan Diephouse [EMAIL PROTECTED] wrote: I'm happy to revert the change, but I think that we ultimately need it. I believe we're targeting JAX-WS 2.1 (we switched the API jar the other day), and that requires JAXB 2.1. There are many benefits from a user perspective in 2.1. For isntance it has a lot better functionality for things like WS-A and also makes it easier for people to use substitution types, which requires all sorts of hacks right now. Is Geronimo just looking to release JAX-WS 2.0 support or 2.1? Any idea if its possible to certify Geronimo with 2.1? Or does certification require 2.0? I'm not sure what the status is of the JAX-WS 2.1 TCK either. - Dan (I CC'd [EMAIL PROTECTED] in, hope thats ok) On 2/28/07, Jarek Gawor [EMAIL PROTECTED] wrote: Hi again, CXF code was recently upgraded to JAXB 2.1 and so I tired to figure out what sort of implications that might have on Geronimo. First of all, JAXB is one of those libraries that is shared by all applications in the Geronimo server. We also have a bunch of different components using JAXB to do deployment descriptor parsing, etc. So if we upgrade JAXB in G, we have to retest all these subcomponents to make sure they are ok. And I think in general that should be ok but potentially time consuming. Another potential issue that somebody raised was TCK testing. We don't know what happens if for example TCK expects JAXB 2.0 API but gets JAXB 2.1 API/implementation. Maybe nothing (as things supposed to be backwards compatible) but maybe it blows up. That's another thing for us to worry about. So, if this JAXB upgrade is not a critical issue for CXF would it be possible to switch back to JAXB 2.0? Thanks, Jarek -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: build error - caused by change in Axis2 repo?
I haven't seen this yet...but I started another deploy just now in any case. Could you please try in another 15-20 mins? Please blow up your local .m2/repository/org/apache/axis2 before you do. thanks, dims On 3/2/07, Lin Sun [EMAIL PROTECTED] wrote: Hi, I am hitting this build error after I clean my local axis2 repo. And I could not find axis2-jaxws-api-SNAPSHOT.jar in any of the repos below either. I can only find axis2-jaxws-api-timestamp.jar like axis2-jaxws-20070302.130022-22.jar at the apache repo below. WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT'from repository apache.snapshots (http://people.apache.org/repo/m2-snapshot-repsitory) INFO] ERROR] BUILD ERROR INFO] INFO] Failed to resolve artifact. issing: - ) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jaxs-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT - required artifact is missing. or artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT rom the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) INFO] INFO] For more information, run Maven with the -e switch INFO] INFO] Total time: 3 minutes 20 seconds INFO] Finished at: Fri Mar 02 15:29:58 EST 2007 INFO] Final Memory: 56M/63M INFO] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
build error - caused by change in Axis2 repo?
Hi, I am hitting this build error after I clean my local axis2 repo. And I could not find axis2-jaxws-api-SNAPSHOT.jar in any of the repos below either. I can only find axis2-jaxws-api-timestamp.jar like axis2-jaxws-20070302.130022-22.jar at the apache repo below. WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT'from repository apache.snapshots (http://people.apache.org/repo/m2-snapshot-repsitory) INFO] ERROR] BUILD ERROR INFO] INFO] Failed to resolve artifact. issing: - ) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jaxs-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT - required artifact is missing. or artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT rom the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) INFO] INFO] For more information, run Maven with the -e switch INFO] INFO] Total time: 3 minutes 20 seconds INFO] Finished at: Fri Mar 02 15:29:58 EST 2007 INFO] Final Memory: 56M/63M INFO]
Re: Jars in the dist
On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar I hope we can use the newer... never tried to see if that works or not though... #2) We need to get rid of activation-1.1.jar from Sun. (i will have to change axis2 pom's) #3) We could use saaj-api and jaxws-api jars from Axis2 instead of the sun versions #4) We need to get rid of mail-1.4.jar from Sun. (i will have to change axis2 pom's) #5) I guess xpp3-1.1.3.3.jar is needed by xstream-1.1.3.jar? Yes. #6) Do we really need to ship junit-3.8.1.jar? No, something probably has that set to a non-test scope and its getting sucked in. --jason
[jira] Commented: (GERONIMO-2841) Valve reports request method as GET even though POST request was made
[ https://issues.apache.org/jira/browse/GERONIMO-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477443 ] Paul McMahan commented on GERONIMO-2841: can you point me at a test case where this error occurs? Valve reports request method as GET even though POST request was made - Key: GERONIMO-2841 URL: https://issues.apache.org/jira/browse/GERONIMO-2841 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor The Request of EJBWebServiceValve in Tomcat return the request method as GET even though POST request was sent. In similar class in Jetty the request method is reported correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: mx4j dependencies
Ah... I didn't notice that ;-) Maybe it should be nuked then... --jason On Mar 2, 2007, at 4:49 AM, Anita Kulshreshtha wrote: The tests have been disabled (the names starts with xtest)... Thanks Anita --- Jason Dillon [EMAIL PROTECTED] wrote: On Mar 1, 2007, at 4:04 PM, Dain Sundstrom wrote: * modules/geronimo-jetty6/src/test/java/org/apache/geronimo/ jetty6/ClassLoaderTest.java (attempts to use mx4j.MBeanDescription to test classloading stuff) Not sure what to do about the later... or even if anything needs to be done. I'd just say remove the test. This test doesn't actually fail with the mx4j deps removed from the project. So either is picking up mx4j somewhere (that isn't getting included in the assembly, cause I can't find it there... though didn't look too hard for it), or the test is disabled, or its not testing anything useful... or its a broken test... or i've been sucked into a biiaaar universe. --jason __ __ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com
[jira] Commented: (GERONIMO-2841) Valve reports request method as GET even though POST request was made
[ https://issues.apache.org/jira/browse/GERONIMO-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477451 ] Jarek Gawor commented on GERONIMO-2841: --- Use testsuite/webservices-testsuite/jaxws-tests/jaxws-ejb tests. Disable testWSDL(), and testEJB() test cases from JaxWSTest. Setup a breakpoint in EJBWebServiceValve and examine the request method. The test case might itself fail but at least the request method should be POST. Valve reports request method as GET even though POST request was made - Key: GERONIMO-2841 URL: https://issues.apache.org/jira/browse/GERONIMO-2841 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor The Request of EJBWebServiceValve in Tomcat return the request method as GET even though POST request was sent. In similar class in Jetty the request method is reported correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2923) Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code
Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code --- Key: GERONIMO-2923 URL: https://issues.apache.org/jira/browse/GERONIMO-2923 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: webservices Environment: sun 1.5 + winXP Reporter: Lin Sun Priority: Minor As titled - Axis2 team suggested us to use RESTUtil.processURLRequest instead. Will put a patch whenever I can run a full build.:) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SystemDatabase
Eh... thats broke... --jason On Mar 2, 2007, at 12:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. Thanks Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: The SystemDatabase and the original derby.log is in var/derby for rev 513298. Did you use DBManager or database pool wizard? I have another derby.log and a derby.backup in var after I deployed/undeployed database pools few times. Thanks Anita --- Jarek Gawor [EMAIL PROTECTED] wrote: I've noticed recently that the SystemDatabase/ directory and derby.log files are being created in the current working directory (the directory from which I start the server from using java -jar ..) and not in the installation directory of Geronimo. I'm not sure if that's new or just something I've just noticed now but either way this seems weird. Jarek __ __ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com __ __ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367
Re: SystemDatabase
On Mar 2, 2007, at 3:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. I'm not following you, Anita. If derby log and systemdatabase are not in var/derby, would someone please create a jira? looks good in M3, at least on my system. --kevan
[jira] Closed: (GERONIMO-2848) @WebServiceRef annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2848. -- Resolution: Fixed Fix Version/s: 2.0-beta2 Assignee: David Jencks (was: Tim McConnell) Applied in rev 513941, thanks tim! I removed the setMetaDataComplete call in SwitchingServiceRefBuilder since this should only be done from the ModuleBuilder, never a NamingBuilder. @WebServiceRef annotation support - Key: GERONIMO-2848 URL: https://issues.apache.org/jira/browse/GERONIMO-2848 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Tim McConnell Assigned To: David Jencks Fix For: 2.0-beta2 Attachments: GERONIMO-2848-1.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2925) Key used for encryption same for all server instances
Key used for encryption same for all server instances - Key: GERONIMO-2925 URL: https://issues.apache.org/jira/browse/GERONIMO-2925 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 1.1.1, 1.1.2, 1.1.x, 1.2, 2.0 Reporter: Michael Malgeri Priority: Critical We understand that WASCE use AES to encrypt the password. You do javax.crypto.Cipher.getInstance(AES) and init() with a hard-coded key. This key is same for all the WASCE server instances. Anyone getting access to a downloaded version of the software can have the algorithm and decrypt the password. So we need your urgent help on the following: 1. provide a solution with key management that we can control 2. provide a pluggable encryption solution so that we can use our internal algorithms and key management At least, 3. the key should be dynamically generated in each of the installations that would reduce the ability to decrypt to someone who has access to the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jars in the dist
It would be nice if we had a mvn plugin which could generate a full NOTICE.txt and LICENSE.txt with all dependency licenses... most of these have valid m2 poms which can be used to fetch the license details... and then just have a little artifact map for those that are missing. Would be a nice addition to the other legal goals. --jason On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar #2) We need to get rid of activation-1.1.jar from Sun. (i will have to change axis2 pom's) #3) We could use saaj-api and jaxws-api jars from Axis2 instead of the sun versions #4) We need to get rid of mail-1.4.jar from Sun. (i will have to change axis2 pom's) #5) I guess xpp3-1.1.3.3.jar is needed by xstream-1.1.3.jar? #6) Do we really need to ship junit-3.8.1.jar? #7) comment in main pom.xml says that we can get rid of xml-apis-1.3.03.jar when we move to tomcat6. Should we clean it up? !-- This will go away when we move to tomcat6 -- dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version1.3.03/version /dependency #8) Has anyone compiled a list of the licenses corresponding to each jar? thanks, dims Here's the complete list: === activation-1.1.jar activeio-2.0-r118.jar activeio-core-3.0.0-incubator.jar activemq-core-4.1.0-incubator.jar activemq-ra-4.1.0-incubator.jar annogen-0.1.0.jar antlr-2.7.2.jar apache-ldapber-provider-0.9.2.jar apacheds-core-0.9.2.jar apacheds-shared-0.9.2.jar asm-2.2.3.jar asm-commons-2.2.3.jar asn1-ber-0.3.2.jar asn1-codec-0.3.2.jar asn1-der-0.3.2.jar axiom-api-SNAPSHOT.jar axiom-impl-SNAPSHOT.jar axis-1.4.jar axis2-adb-SNAPSHOT.jar axis2-java2wsdl-SNAPSHOT.jar axis2-jaxws-api-SNAPSHOT.jar axis2-jaxws-SNAPSHOT.jar axis2-kernel-SNAPSHOT.jar axis2-metadata-SNAPSHOT.jar backport-util-concurrent-2.2.jar bcel-5.2.jar castor-0.9.5.3.jar castor-1.0.5.jar cglib-nodep-2.1_3.jar client.jar commons-beanutils-1.6.1.jar commons-cli-1.0.jar commons-codec-1.3.jar commons-collections-3.1.jar commons-digester-1.8.jar commons-discovery-0.2.jar commons-fileupload-1.1.1.jar commons-httpclient-3.0.1.jar commons-io-1.1.jar commons-jexl-1.1.jar commons-lang-2.0.jar commons-logging-1.0.4.jar commons-primitives-20041207.202534.jar concurrent-1.3.4.jar cxf-api-2.0-incubator-RC-SNAPSHOT.jar cxf-common-utilities-2.0-incubator-RC-SNAPSHOT.jar cxf-metacode-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-bindings-soap-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-bindings-xml-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-core-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-databinding-jaxb-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-frontend-jaxws-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-frontend-simple-2.0-incubator-RC-SNAPSHOT.jar cxf-rt-transports-http-2.0-incubator-RC-SNAPSHOT.jar cxf-tools-common-2.0-incubator-RC-SNAPSHOT.jar deployer.jar derby-10.2.2.0.jar derbyclient-10.2.2.0.jar derbynet-10.2.2.0.jar derbytools-10.2.2.0.jar dwr-1.1.1.jar geronimo-activation-2.0-SNAPSHOT.jar geronimo-activation_1.1_spec-1.0-SNAPSHOT.jar geronimo-activemq-gbean-2.0-SNAPSHOT.jar geronimo-activemq-gbean-management-2.0-SNAPSHOT.jar geronimo-annotation_1.0_spec-1.0.jar geronimo-axis-2.0-SNAPSHOT.jar geronimo-axis-builder-2.0-SNAPSHOT.jar geronimo-axis2-2.0-SNAPSHOT.jar geronimo-axis2-builder-2.0-SNAPSHOT.jar geronimo-client-2.0-SNAPSHOT.jar geronimo-client-builder-2.0-SNAPSHOT.jar geronimo-clustering-2.0-SNAPSHOT.jar geronimo-clustering-wadi-2.0-SNAPSHOT.jar geronimo-common-2.0-SNAPSHOT.jar geronimo-connector-2.0-SNAPSHOT.jar geronimo-connector-builder-2.0-SNAPSHOT.jar geronimo-console-core-2.0-SNAPSHOT.jar geronimo-console-framework-2.0-SNAPSHOT.jar geronimo-console-standard-2.0-SNAPSHOT.jar geronimo-converter-2.0-SNAPSHOT.jar geronimo-corba-2.0-SNAPSHOT.jar geronimo-corba-builder-2.0-SNAPSHOT.jar geronimo-core-2.0-SNAPSHOT.jar geronimo-cxf-2.0-SNAPSHOT.jar geronimo-cxf-builder-2.0-SNAPSHOT.jar geronimo-deploy-config-2.0-SNAPSHOT.jar geronimo-deploy-jsr88-2.0-SNAPSHOT.jar geronimo-deploy-jsr88-bootstrapper-2.0-SNAPSHOT.jar geronimo-deploy-tool-2.0-SNAPSHOT.jar geronimo-deployment-2.0-SNAPSHOT.jar geronimo-derby-2.0-SNAPSHOT.jar geronimo-directory-2.0-SNAPSHOT.jar geronimo-dojo-2.0-SNAPSHOT.jar geronimo-ejb_3.0_spec-1.0.jar geronimo-el_1.0_spec-1.0-SNAPSHOT.jar geronimo-hot-deploy-2.0-SNAPSHOT.jar geronimo-interceptor-2.0-SNAPSHOT.jar geronimo-interceptor_3.0_spec-1.0.jar geronimo-j2ee-2.0-SNAPSHOT.jar geronimo-j2ee-builder-2.0-SNAPSHOT.jar geronimo-j2ee-connector_1.5_spec-1.1.jar geronimo-j2ee-management_1.1_spec-1.0-SNAPSHOT.jar geronimo-j2ee-schema-2.0-SNAPSHOT.jar geronimo-jacc_1.1_spec-1.0-SNAPSHOT.jar geronimo-javaee-deployment_1.1MR3_spec-1.0-SNAPSHOT.jar geronimo-javamail_1.4_mail-1.1-SNAPSHOT.jar geronimo-jaxr_1.0_spec-1.1.jar geronimo-jaxrpc_1.1_spec-1.1.jar geronimo-jaxws-2.0-SNAPSHOT.jar
Re: ServiceMix and WebDav support
On 3/2/07, icarrara [EMAIL PROTECTED] wrote: Hi! I'm seraching for a developer that can realize the below: I know that ServiceMix provide a file endpoint and a vfs (including WebDav) endpoint. My objective is to have a ServiceMix server that read and write files between: - Windows folder to WebDav server - WebDav server to Windows folder - Windows folder to Windows folder - WebDav server to WebDav server Based on my knowledge, the above are kind of activities that ServiceMix is able to do, after the setup of configurationf files. The work I'm asking to someone to do is to set the right configuration files to realize the above jobs. Please, could you tell me more? I think you can use a lightweight component for this. There are a couple of example configurations of using a lightweight component that is based on Commons VFS available here: http://svn.apache.org/repos/asf/incubator/servicemix/trunk/common/servicemix-components/src/test/resources/org/apache/servicemix/components/vfs/ These configurations are used by the test that is located here: http://svn.apache.org/repos/asf/incubator/servicemix/trunk/common/servicemix-components/src/test/java/org/apache/servicemix/components/vfs/FileTest.java You will need to specify paths that adhere to the Commons VFS URI syntax for each protocol as listed here: http://jakarta.apache.org/commons/vfs/filesystems.html Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/
[jira] Commented: (GERONIMO-2925) Key used for encryption same for all server instances
[ https://issues.apache.org/jira/browse/GERONIMO-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477537 ] David Jencks commented on GERONIMO-2925: Did you intend to file this in an IBM issue tracker? If not, why does it refer to WASCE? Who is we? Exactly what attack is we trying to protect against? Specifically which files is we talking about? The current solution makes it so that someone casually looking at config.xml can't read off the passwords that might be overridden there. I think this is an appropriate level of security. Any solution that involves the server reading a key from some file to use for decryption has the same level of security as the current one unless we wants to be able to publish whatever files they are talking about without danger. Anyone who can get to config.xml, say, can also find the file the key is stored in. If we is concerned about config.xml, and wants to be able to publish it without danger, perhaps a more appropriate solution would be to use the property substitution suggested in GERONIMO-2735 and keep the properties file secured. If that's not appropriate perhaps the vault proprosed in https://issues.apache.org/jira/browse/GERONIMO-1486 would be something to think about. I don't have a problem with making the encryption more pluggable, but I'd like to understand the benefit first. There might be other simpler more secure solutions as well, such as supplying the encryption key as a system property on the command line. (at least if you turn off bash_history) Key used for encryption same for all server instances - Key: GERONIMO-2925 URL: https://issues.apache.org/jira/browse/GERONIMO-2925 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 1.1.1, 1.1.2, 1.1.x, 1.2, 2.0 Reporter: Michael Malgeri Priority: Critical We understand that WASCE use AES to encrypt the password. You do javax.crypto.Cipher.getInstance(AES) and init() with a hard-coded key. This key is same for all the WASCE server instances. Anyone getting access to a downloaded version of the software can have the algorithm and decrypt the password. So we need your urgent help on the following: 1. provide a solution with key management that we can control 2. provide a pluggable encryption solution so that we can use our internal algorithms and key management At least, 3. the key should be dynamically generated in each of the installations that would reduce the ability to decrypt to someone who has access to the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2925) Key used for encryption same for all server instances
[ https://issues.apache.org/jira/browse/GERONIMO-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477541 ] Michael Malgeri commented on GERONIMO-2925: --- It refers to WAS CE because it comes from a customer using WAS CE not Geronimo. I assumed the fix would be applied in Geronimo and WAS CE would pick it up. The customer is we in the message and I did a cut and paste. We'll get more info from the customer and post when available. Key used for encryption same for all server instances - Key: GERONIMO-2925 URL: https://issues.apache.org/jira/browse/GERONIMO-2925 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 1.1.1, 1.1.2, 1.1.x, 1.2, 2.0 Reporter: Michael Malgeri Priority: Critical We understand that WASCE use AES to encrypt the password. You do javax.crypto.Cipher.getInstance(AES) and init() with a hard-coded key. This key is same for all the WASCE server instances. Anyone getting access to a downloaded version of the software can have the algorithm and decrypt the password. So we need your urgent help on the following: 1. provide a solution with key management that we can control 2. provide a pluggable encryption solution so that we can use our internal algorithms and key management At least, 3. the key should be dynamically generated in each of the installations that would reduce the ability to decrypt to someone who has access to the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jars in the dist
castor-0.9.5.3 is a prereq for Pluto. I haven't tried using the newer version with Pluto to see if it breaks us yet. -Donald Jason Dillon wrote: On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar I hope we can use the newer... never tried to see if that works or not though... #2) We need to get rid of activation-1.1.jar from Sun. (i will have to change axis2 pom's) #3) We could use saaj-api and jaxws-api jars from Axis2 instead of the sun versions #4) We need to get rid of mail-1.4.jar from Sun. (i will have to change axis2 pom's) #5) I guess xpp3-1.1.3.3.jar is needed by xstream-1.1.3.jar? Yes. #6) Do we really need to ship junit-3.8.1.jar? No, something probably has that set to a non-test scope and its getting sucked in. --jason smime.p7s Description: S/MIME Cryptographic Signature
Re: Jars in the dist
Seems easy enough to try... just use the new version, make sure the old version is not getting picked up (exclude it if needed), then see if the console still works? --jason On Mar 2, 2007, at 3:29 PM, Donald Woods wrote: castor-0.9.5.3 is a prereq for Pluto. I haven't tried using the newer version with Pluto to see if it breaks us yet. -Donald Jason Dillon wrote: On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar I hope we can use the newer... never tried to see if that works or not though... #2) We need to get rid of activation-1.1.jar from Sun. (i will have to change axis2 pom's) #3) We could use saaj-api and jaxws-api jars from Axis2 instead of the sun versions #4) We need to get rid of mail-1.4.jar from Sun. (i will have to change axis2 pom's) #5) I guess xpp3-1.1.3.3.jar is needed by xstream-1.1.3.jar? Yes. #6) Do we really need to ship junit-3.8.1.jar? No, something probably has that set to a non-test scope and its getting sucked in. --jason
[jira] Updated: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2743: -- Attachment: J2G-Migration_2.0.0_src_20070302-1501.zip Files listed by Paul has been updated to reflect the new ASF copyright. [Code donation] J2G Conversion tool --- Key: GERONIMO-2743 URL: https://issues.apache.org/jira/browse/GERONIMO-2743 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Affects Versions: 1.1.x Environment: MS Windows XP SP2 (although Java based should work on any OS supporting Java) Reporter: Filip Hanik Priority: Minor Fix For: 1.1.x Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, J2G-Migration_2.0.0_src_20070302-1501.zip IBM has together with in a joint effort with Covalent developed a JBoss to Geronimo conversion tool. This tool is used when converting applications from JBoss to Geronimo, and automatically converts the configuration file from one app server to the other. We feel that this piece of software adds value to Geronimo and users adopting Geronimo and would like to see this effort continue as part of the Geronimo project, a plugin or a sub project of Geronimo. The initial donation is for version 1.0 of this tool, and while a 1.1 is in the making to improve 1.0, 1.1 is not yet complete but will be donated as soon as the community feels that this tool belongs at the ASF, more specifically within the Geronimo project. If you'd think this tool is valuable, but believe it should go through incubation, we would hope that a Geronimo committer would step up and champion this effort. The tool, including IBM's CCLA, can be found at http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jars in the dist
--- Davanum Srinivas [EMAIL PROTECTED] wrote: Team, #7) comment in main pom.xml says that we can get rid of xml-apis-1.3.03.jar when we move to tomcat6. Should we clean it up? !-- This will go away when we move to tomcat6 -- dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version1.3.03/version /dependency We should not be needing/using xml-apis and xalan in J2SE 1.5. They have been added again because tck was broken. It would be nice if someone could explain why exactly they were needed. Thanks Anita Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121
Re: mx4j dependencies
Go for it... Anita --- Jason Dillon [EMAIL PROTECTED] wrote: Ah... I didn't notice that ;-) Maybe it should be nuked then... --jason On Mar 2, 2007, at 4:49 AM, Anita Kulshreshtha wrote: The tests have been disabled (the names starts with xtest)... Thanks Anita --- Jason Dillon [EMAIL PROTECTED] wrote: On Mar 1, 2007, at 4:04 PM, Dain Sundstrom wrote: * modules/geronimo-jetty6/src/test/java/org/apache/geronimo/ jetty6/ClassLoaderTest.java (attempts to use mx4j.MBeanDescription to test classloading stuff) Not sure what to do about the later... or even if anything needs to be done. I'd just say remove the test. This test doesn't actually fail with the mx4j deps removed from the project. So either is picking up mx4j somewhere (that isn't getting included in the assembly, cause I can't find it there... though didn't look too hard for it), or the test is disabled, or its not testing anything useful... or its a broken test... or i've been sucked into a biiaaar universe. --jason __ __ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front
[jira] Created: (GERONIMO-2926) Derby files are not being created in var/derby directory
Derby files are not being created in var/derby directory Key: GERONIMO-2926 URL: https://issues.apache.org/jira/browse/GERONIMO-2926 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.0-beta2 Environment: All Reporter: Anita Kulshreshtha Fix For: 2.0-beta2 The derby files/dirs like derby.log and SystemDatabase are not being created in var/derby directory. They are being created in geronimo-home directory. these were created properly in 2.0-M3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SystemDatabase
Done. https://issues.apache.org/jira/browse/GERONIMO-2926 Thanks Anita --- Kevan Miller [EMAIL PROTECTED] wrote: On Mar 2, 2007, at 3:08 PM, Anita Kulshreshtha wrote: A correction... My last message was for 2.0-M3. There is no var/derby for rev 513298. The SystemDatabase and derby.log are in g-home dir. I'm not following you, Anita. If derby log and systemdatabase are not in var/derby, would someone please create a jira? looks good in M3, at least on my system. --kevan Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know.
Re: Jars in the dist
--- Davanum Srinivas [EMAIL PROTECTED] wrote: Team, #6) Do we really need to ship junit-3.8.1.jar? tranql-connector-derby-embed-xa-...rar comes with junit! I saw Matt's name in the manifest, hence I am writing to this list.. Thanks Anita Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
Re: [VOTE] Geronimo web site update
+1 Gianny On 01/03/2007, at 9:28 AM, Hernan Cunico wrote: Folks, this vote is for moving the authoring of Geronimo's web site over Confluence. This mean that we will no longer use the anakia, xdocs and ant scripts to generate the web site, instead we will use Confluence. There is a GMOxSITE space in the cwiki site that only Geronimo committers can edit, this space will get automatically exported and massaged with a presentation template over geronimo.apache.org The source of the web site will remain in Confluence, svn repo will hold a copy of the HTML version. The other resources we serve from geronimo.apache.org such as plugins, schemas, redirects, etc. will remain unaffected. This vote will end this Saturday March 3rd at 1800 Eastern time. [ ] +1 Let's move the authoring over Confluence. [ ] 0 No opinion. [ ] -1 Do not change the authoring to Confluence, stay with ant scripts and xdocs. Cheers! Hernan
[jira] Closed: (GERONIMO-2912) Server can not be shutdown using bin\shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gianny Damour closed GERONIMO-2912. --- Resolution: Fixed Fix Version/s: (was: 2.0-M3) (was: 2.0-beta2) 2.0 Assignee: Gianny Damour (was: Anita Kulshreshtha) Regression: [Regression] Anita. Thanks for raising this problem. It has now been fixed. Server can not be shutdown using bin\shutdown - Key: GERONIMO-2912 URL: https://issues.apache.org/jira/browse/GERONIMO-2912 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M3, 2.0-beta2 Environment: All Reporter: Anita Kulshreshtha Assigned To: Gianny Damour Fix For: 2.0 Attachments: GERONIMO-2912.patch The server gives the following error when shutdown is attempted using bin\shutdown.: Exception in thread main java.lang.NoClassDefFoundError: org/apache/geronimo/deployment/cli/StopServer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JAXB upgrade
I'm OK with rolling back for now. However the spec itself is final and the RI impl is already out: https://jax-ws.dev.java.net/2.1/ Everyone else ok with it? Cheers, - Dan On 3/2/07, David Jencks [EMAIL PROTECTED] wrote: At this time Geronimo can only certify with JAXB 2.0 and JAXWS 2.0. We're hoping that sun will update the tck to allow supporting the 2.1 specs, but as far as we can tell this has not yet happened. Getting information out of sun about this stuff can be difficult, but perhaps if we started now and now and are sufficiently persistent we will eventually find out something useful. Are the 2.1 spec versions officially released? Meanwhile we'd certainly appreciate it at Geronimo if you went back to the 2.0 spec versions for now. thanks david jencks On Mar 1, 2007, at 7:43 AM, Jarek Gawor wrote: Oh... I didn't even realize you guys are targeting JAX-WS 2.1. Now, I'm not sure how that affects things. Jarek On 3/1/07, Dan Diephouse [EMAIL PROTECTED] wrote: I'm happy to revert the change, but I think that we ultimately need it. I believe we're targeting JAX-WS 2.1 (we switched the API jar the other day), and that requires JAXB 2.1. There are many benefits from a user perspective in 2.1. For isntance it has a lot better functionality for things like WS-A and also makes it easier for people to use substitution types, which requires all sorts of hacks right now. Is Geronimo just looking to release JAX-WS 2.0 support or 2.1? Any idea if its possible to certify Geronimo with 2.1? Or does certification require 2.0? I'm not sure what the status is of the JAX-WS 2.1 TCK either. - Dan (I CC'd [EMAIL PROTECTED] in, hope thats ok) On 2/28/07, Jarek Gawor [EMAIL PROTECTED] wrote: Hi again, CXF code was recently upgraded to JAXB 2.1 and so I tired to figure out what sort of implications that might have on Geronimo. First of all, JAXB is one of those libraries that is shared by all applications in the Geronimo server. We also have a bunch of different components using JAXB to do deployment descriptor parsing, etc. So if we upgrade JAXB in G, we have to retest all these subcomponents to make sure they are ok. And I think in general that should be ok but potentially time consuming. Another potential issue that somebody raised was TCK testing. We don't know what happens if for example TCK expects JAXB 2.0 API but gets JAXB 2.1 API/implementation. Maybe nothing (as things supposed to be backwards compatible) but maybe it blows up. That's another thing for us to worry about. So, if this JAXB upgrade is not a critical issue for CXF would it be possible to switch back to JAXB 2.0? Thanks, Jarek -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
Re: build error - caused by change in Axis2 repo?
Thanks Dims - I can build now. I was able to build at around 10AM EST after blow up my local .m2/repository/org/apache/axis2, but not at around 3PM EST also after blow up my local .m2/repository/org/apache/axis2. Any idea why this can happen? Doesn't look like a network glitch coz I could not download any axis2 jars at that time after a few tries. Lin Davanum Srinivas wrote: I haven't seen this yet...but I started another deploy just now in any case. Could you please try in another 15-20 mins? Please blow up your local .m2/repository/org/apache/axis2 before you do. thanks, dims On 3/2/07, Lin Sun [EMAIL PROTECTED] wrote: Hi, I am hitting this build error after I clean my local axis2 repo. And I could not find axis2-jaxws-api-SNAPSHOT.jar in any of the repos below either. I can only find axis2-jaxws-api-timestamp.jar like axis2-jaxws-20070302.130022-22.jar at the apache repo below. WARNING] Unable to get resource 'org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT'from repository apache.snapshots (http://people.apache.org/repo/m2-snapshot-repsitory) INFO] ERROR] BUILD ERROR INFO] INFO] Failed to resolve artifact. issing: - ) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jaxs-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT - required artifact is missing. or artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT rom the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) INFO] INFO] For more information, run Maven with the -e switch INFO] INFO] Total time: 3 minutes 20 seconds INFO] Finished at: Fri Mar 02 15:29:58 EST 2007 INFO] Final Memory: 56M/63M INFO]
[jira] Commented: (GERONIMO-2841) Valve reports request method as GET even though POST request was made
[ https://issues.apache.org/jira/browse/GERONIMO-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477589 ] Lin Sun commented on GERONIMO-2841: --- Experienced the same thing (request.getMethod() always returns GET) when running the same jaxws-ejb test with Axis2. Thanks, Lin Valve reports request method as GET even though POST request was made - Key: GERONIMO-2841 URL: https://issues.apache.org/jira/browse/GERONIMO-2841 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Reporter: Jarek Gawor The Request of EJBWebServiceValve in Tomcat return the request method as GET even though POST request was sent. In similar class in Jetty the request method is reported correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2923) Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code
[ https://issues.apache.org/jira/browse/GERONIMO-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated GERONIMO-2923: -- Attachment: G2923.patch Able to run a full build and verify existing tests work. Axis2: remove the deprecated processHTTPGetRequest method in Axis2 integration code --- Key: GERONIMO-2923 URL: https://issues.apache.org/jira/browse/GERONIMO-2923 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: webservices Environment: sun 1.5 + winXP Reporter: Lin Sun Priority: Minor Attachments: G2923.patch As titled - Axis2 team suggested us to use RESTUtil.processURLRequest instead. Will put a patch whenever I can run a full build.:) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2926) Derby files are not being created in var/derby directory
[ https://issues.apache.org/jira/browse/GERONIMO-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477592 ] Anita Kulshreshtha commented on GERONIMO-2926: -- This is part of the server startup log: Module 6/25 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car 22:36:26,156 ERROR [RecoveryController] javax.transaction.xa.XAException: No current connection. started in 8.500s Module 7/25 org.apache.geronimo.configs/system-database/2.0-SNAPSHOT/car The openejb configuration is being started before system-database, i.e. before DerbySystemGbean is started. IIUC, the openejb configuration seems to be creating SystemDatabase and derby.log in g home directory. Derby files are not being created in var/derby directory Key: GERONIMO-2926 URL: https://issues.apache.org/jira/browse/GERONIMO-2926 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.0-beta2 Environment: All Reporter: Anita Kulshreshtha Fix For: 2.0-beta2 The derby files/dirs like derby.log and SystemDatabase are not being created in var/derby directory. They are being created in geronimo-home directory. these were created properly in 2.0-M3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Jars in the dist
On Mar 2, 2007, at 1:22 PM, Jason Dillon wrote: On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar I hope we can use the newer... never tried to see if that works or not though... OpenEJB uses castor to load two files still. OpenEJB is using version 1.0.5. -dain
Re: Jars in the dist
Looks like we need to update our license files (we only include the older Intalio text, http://castor.org/license.html)... snip New Apache-style license As of release 0.9.7, any new code artifacts should carry a new, Apache 2.0-style license. This shall include files that have been changed substantially through e.g. refactoring. Copyright 2004-2005 Werner Guttmann Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Original Intalio license The code of this project is released under a BSD-like license [license.txt]: Copyright 1999-2004 (C) Intalio Inc., and others. All Rights Reserved. Redistribution and use of this software and associated documentation (Software), with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name ExoLab must not be used to endorse or promote products derived from this Software without prior written permission of Intalio Inc. For written permission, please contact [EMAIL PROTECTED] 4. Products derived from this Software may not be called Castor nor may Castor appear in their names without prior written permission of Intalio Inc. Exolab, Castor and Intalio are trademarks of Intalio Inc. 5. Due credit should be given to the ExoLab Project (http://www.exolab.org/). THIS SOFTWARE IS PROVIDED BY INTALIO AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTALIO OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. /snip --jason On Mar 2, 2007, at 10:15 PM, Dain Sundstrom wrote: On Mar 2, 2007, at 1:22 PM, Jason Dillon wrote: On Mar 2, 2007, at 1:17 PM, Davanum Srinivas wrote: Team, #1) 2 versions of castor jar are present. Do we even need castor jar? castor-0.9.5.3.jar castor-1.0.5.jar I hope we can use the newer... never tried to see if that works or not though... OpenEJB uses castor to load two files still. OpenEJB is using version 1.0.5. -dain
Upgrade Pluto to 1.1? (was Re: What are we using Castor for?)
On Feb 13, 2007, at 5:49 PM, David Jencks wrote: It's used by pluto for the admin console. No idea if more recent would work. We could upgrade pluto too if anyone has some time to investigate I wonder if anyone from the Pluto team would want to help with that... looks like 1.1 is not compatible with 1.0.1... but also looks like that might not be a bad thing: snip Pluto 1.1 introduces a new container architecture. If you are embedding Pluto in your portal, realize that 1.1 is not binarily compatible with Pluto 1.0.x. Pluto 1.1 aims to simplify the architecture in order to make it more user and developer friendly. You should find Pluto 1.1 easier to get started with, easier to understand, and easier to embed with your portal. Your feedback regarding how far we've come is always welcome on the user and developer mailing lists! /snip I don't know much abort portal muck, so I can't really show how much better 1.1 might be... but I know that there have been some issues with the console asis now to get stuff like plugin porlets installed dynamically... perhaps 1.1 can help solve some of these issues? Anyone know? --jason
Re: Upgrade Pluto to 1.1? (was Re: What are we using Castor for?)
Or... what about Jetspeed 2? Again I know jack about all things portal so I have no idea... but I would like to have the console get to be more pluggable and dynamic to install plugin bits at runtime. --jason On Mar 2, 2007, at 10:52 PM, Jason Dillon wrote: On Feb 13, 2007, at 5:49 PM, David Jencks wrote: It's used by pluto for the admin console. No idea if more recent would work. We could upgrade pluto too if anyone has some time to investigate I wonder if anyone from the Pluto team would want to help with that... looks like 1.1 is not compatible with 1.0.1... but also looks like that might not be a bad thing: snip Pluto 1.1 introduces a new container architecture. If you are embedding Pluto in your portal, realize that 1.1 is not binarily compatible with Pluto 1.0.x. Pluto 1.1 aims to simplify the architecture in order to make it more user and developer friendly. You should find Pluto 1.1 easier to get started with, easier to understand, and easier to embed with your portal. Your feedback regarding how far we've come is always welcome on the user and developer mailing lists! /snip I don't know much abort portal muck, so I can't really show how much better 1.1 might be... but I know that there have been some issues with the console asis now to get stuff like plugin porlets installed dynamically... perhaps 1.1 can help solve some of these issues? Anyone know? --jason
Re: Upgrade Pluto to 1.1? (was Re: What are we using Castor for?)
Actually, what I'd really like to see is our console allow app developers to plugin their own portlets for custom administration of their applications which are running in Geronimo... --jason On Mar 2, 2007, at 11:27 PM, Jason Dillon wrote: Or... what about Jetspeed 2? Again I know jack about all things portal so I have no idea... but I would like to have the console get to be more pluggable and dynamic to install plugin bits at runtime. --jason On Mar 2, 2007, at 10:52 PM, Jason Dillon wrote: On Feb 13, 2007, at 5:49 PM, David Jencks wrote: It's used by pluto for the admin console. No idea if more recent would work. We could upgrade pluto too if anyone has some time to investigate I wonder if anyone from the Pluto team would want to help with that... looks like 1.1 is not compatible with 1.0.1... but also looks like that might not be a bad thing: snip Pluto 1.1 introduces a new container architecture. If you are embedding Pluto in your portal, realize that 1.1 is not binarily compatible with Pluto 1.0.x. Pluto 1.1 aims to simplify the architecture in order to make it more user and developer friendly. You should find Pluto 1.1 easier to get started with, easier to understand, and easier to embed with your portal. Your feedback regarding how far we've come is always welcome on the user and developer mailing lists! /snip I don't know much abort portal muck, so I can't really show how much better 1.1 might be... but I know that there have been some issues with the console asis now to get stuff like plugin porlets installed dynamically... perhaps 1.1 can help solve some of these issues? Anyone know? --jason
