Re: Swing console?
Hi, On 9/18/06, Heinz Drews [EMAIL PROTECTED] wrote: That is a good suggestion. I agree with your opinion about webapps. Especially during development it seems, that using a component to configure the component which it is dependent on, is increasing risks. I had several times to manually modify config.xml to get G started again Personally I would prefer an application based on Eclipse because this could be nicely integrated with the plugin for launching G. Just to mention that at LiveTribe we're building an Eclipse-based RCP console, and the goals are to use the plugin architecture of Eclipse to create a completely modular RCP application that can manage/monitor the most common app servers, with the ability of replacing completely the UI if you don't like it (or for special management purposes). We're currently doing this for Jetty, next in list is G and AMQ. Simon -- http://livetribe.codehaus.org http://bordet.blogspot.com
Re: Swing console?
Hi, On 9/21/06, Jason Dillon [EMAIL PROTECTED] wrote: Can Eclipse be webstarted? Yes, since Eclipse 3.1. Simon
Re: Swing console?
Hi, On 9/21/06, Jason Dillon [EMAIL PROTECTED] wrote: Ah, thats good news... I was not aware of this. The webstart config does not download all platform natives for a given run does it? No, it does not, if the JNLP file has something like: jnlp ... resources !-- common jars -- /resources resources os=Linux !-- Linux-specific jars -- /resources /jnlp Simon
Re: Swing console?
Heinz, On 9/21/06, Heinz Drews [EMAIL PROTECTED] wrote: Hello Simon, that sounds great. Is there already something available to get a starting point? Well, for now a very small starting point, but we're open to ideas. Code is at https://svn.codehaus.org/livetribe/nursery/livetribe-console/trunk, tomorrow I am going to write some docs about how to build it and what environment is needed. Simon -- http://livetribe.codehaus.org http://bordet.blogspot.com
[jira] Created: (SM-346) String result element task-status-message should be compliant with JBI specification
String result element task-status-message should be compliant with JBI specification -- Key: SM-346 URL: http://jira.activemq.org/jira//browse/SM-346 Project: ServiceMix Type: Bug Components: servicemix-core Versions: 3.0 Reporter: Simone Bordet Priority: Critical Attachments: ManagementSupport.patch A typo in ManagementSupport outputs task-status-message instead of task-status-msg as required by the JBI specification (page 84). The attached patch fixes the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.activemq.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-345) Improve JMX Exception throwing in BaseStandardMBean
Improve JMX Exception throwing in BaseStandardMBean --- Key: SM-345 URL: http://jira.activemq.org/jira//browse/SM-345 Project: ServiceMix Type: Bug Components: servicemix-core Versions: 3.0 Reporter: Simone Bordet Priority: Minor Attachments: BaseStandardMBean.patch MBeanException is the JMX exception to throw when something goes wrong in method invocation. Typically, if invoking via reflection, MBeanException wraps the cause of InvocationTargetException. Attached a simple patch that fixes JMX exception throwing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.activemq.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SM-347) Exception thrown during command invocation contains nested XMLs result strings
Exception thrown during command invocation contains nested XMLs result strings
--
Key: SM-347
URL: http://jira.activemq.org/jira//browse/SM-347
Project: ServiceMix
Type: Bug
Components: servicemix-core
Versions: 3.0
Reporter: Simone Bordet
When invoking AdminCommandsService.startComponent(), and the component start()
method throws an exception, the XML result string (defined by the JBI spec) is
nested, that is contains the XML twice and the second time is encoded, like for
example:
jbi-task xmlns=http://java.sun.com/xml/ns/jbi/management-message;
version=1.0
jbi-task-result
frmwk-task-result
frmwk-task-result-details
task-result-details
task-idstartServiceAssembly/task-id
task-resultFAILED/task-result
message-typeERROR/message-type
task-status-msg
msg-loc-info
loc-token/
loc-messageloanbroker/loc-message
/msg-loc-info
/task-status-msg
exception-info
nesting-level1/nesting-level
loc-token/
loc-messagelt;?xml version=1.0 encoding=UTF-8?gt;
lt;jbi-task xmlns=http://java.sun.com/xml/ns/jbi/management-message;
version=1.0gt;
lt;jbi-task-resultgt;
lt;frmwk-task-resultgt;
lt;frmwk-task-result-detailsgt;
lt;task-result-detailsgt;
lt;task-idgt;startlt;/task-idgt;
lt;task-resultgt;FAILEDlt;/task-resultgt;
lt;message-typegt;ERRORlt;/message-typegt;
lt;/task-result-detailsgt;
lt;/frmwk-task-result-detailsgt;
lt;/frmwk-task-resultgt;
lt;component-task-result
xmlns=http://java.sun.com/xml/ns/jbi/management-messagegt;
lt;component-namegt;servicemix-httplt;/component-namegt;
lt;component-task-result-detailsgt;
lt;task-result-detailsgt;
lt;task-idgt;startlt;/task-idgt;
lt;task-resultgt;FAILEDlt;/task-resultgt;
lt;message-typegt;ERRORlt;/message-typegt;
lt;task-status-messagegt;
lt;msg-loc-infogt;
lt;loc-token/gt;
lt;loc-messagegt;Unable to start service unitlt;/loc-messagegt;
lt;/msg-loc-infogt;
lt;/task-status-messagegt;
lt;exception-infogt;
lt;nesting-levelgt;1lt;/nesting-levelgt;
lt;msg-loc-infogt;
lt;loc-token/gt;
lt;loc-messagegt;An external endpoint
for service {urn:logicblaze:soa:loanbroker}LoanBrokerService and endpoint
loanbroker is already registeredlt;/loc-messagegt;
lt;stack-tracegt;lt;![CDATA[javax.jbi.JBIException: An external endpoint for
service {urn:logicblaze:soa:loanbroker}LoanBrokerService and endpoint
loanbroker is already registered
at
org.apache.servicemix.jbi.framework.EndpointRegistry.registerExternalEndpoint(EndpointRegistry.java:319)
at
org.apache.servicemix.jbi.framework.Registry.registerExternalEndpoint(Registry.java:238)
at
org.apache.servicemix.jbi.framework.ComponentContextImpl.registerExternalEndpoint(ComponentContextImpl.java:324)
at
org.apache.servicemix.http.HttpEndpoint.activate(HttpEndpoint.java:63)
at org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:45)
at
org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:148)
at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:98)
at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
at
org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:373)
at
org.apache.servicemix.jbi.framework.AdminCommandsService.startServiceAssembly(AdminCommandsService.java:202)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
at
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:162)
at
org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStandardMBean.java:307)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81
BindingComponents, ServiceEngines, and Pojo components
Hi, ServiceMix has the notion of pojo components, aside of the ones specified by the JBI spec (binding component and service engine). The JBI management methods: ManagementContext.getBindingComponents() and ManagementContext.getServiceEngines() return not only the bcs and ses, but also (both) ServiceMix pojo's components. Since now ManagementContext has a specialized method to retrieve pojo components, I think will be useful to have the standard JBI methods (getBindingComponents() and getServiceEngines()) return only what their method name says. I filed a JIRA (http://jira.activemq.org/jira/browse/SM-325) and attached a patch. Regards, Simon -- http://bordet.blogspot.com
Re: [Vote] Installer: Default Web Container Selection
[ x ] Make Jetty the default Web Container install selection Simon -- http://bordet.blogspot.com
