hawtio / hawtio-integration Goto Github PK
View Code? Open in Web Editor NEWCore integration plugins for Hawtio: Apache ActiveMQ, Camel, Karaf, OSGi, and Spring Boot
License: Apache License 2.0
Core integration plugins for Hawtio: Apache ActiveMQ, Camel, Karaf, OSGi, and Spring Boot
License: Apache License 2.0
The Camel tree disappears when reloaded.
The tree is reloaded on some user actions, such as deleting a route or pressing F5 to reload the page.
Note: the JMX tree doesn't have this issue.
@astefanutti
The following error is thrown when a node is selected in the JMX tree of MBeans:
TypeError: selected.any is not a function
at Scope.$scope.anySelectionHasState (hawtio-integration.js:3673)
at $parseFunctionCall (angular.js:12474)
at Object.expressionInputWatch (angular.js:12883)
at Scope.$digest (angular.js:14404)
at Scope.$apply (angular.js:14675)
at Object.$apply (hawtio-utilities.js:656)
at render (hawtio-jmx.js:2958)
at Array.callback.success (hawtio-utilities.js:1678)
at jolokia.js:547
at Object.ajaxParams.success (jolokia.js:232)
We should replace old references to sugarjs with native JavaScript.
Route persists in HTML page after delete operation.
Steps to Reproduce:
Actual results:
Html page is not refreshed after Camel route delete. Camel route is still in the route tree.
Expected results:
Html page is refreshed
A number of simple data tables aren't working due to missing primary key. The entities don't contain an id
, _id
, _key
, or name
property and the configuration options don't specify the primaryKeyFn
.
More details in the hawtio-ui demo page.
We need to push the refresh button to view messages in a queue. It should show messages immediately instead.
With the current v1-ports
branch, trying to connect to remote JBoss Fuse 6.3 fails getting the following dialog:
Opening the browser console, it says:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8181/hawtio/jolokia/list?canonicalNaming=false&ignoreErrors=true&_=1483714506643. (Reason: CORS header 'Access-Control-Allow-Origin' missing). (unknown)
[workspace] Failed to load JMX tree, status: error error: jqXHR: Object { readyState: 0, getResponseHeader: .ajax/jqXHR.getResponseHeader(), getAllResponseHeaders: .ajax/jqXHR.getAllResponseHeaders(), setRequestHeader: .ajax/jqXHR.setRequestHeader(), overrideMimeType: .ajax/jqXHR.overrideMimeType(), statusCode: .ajax/jqXHR.statusCode(), abort: .ajax/jqXHR.abort(), state: .Deferred/promise.state(), always: .Deferred/promise.always(), then: .Deferred/promise.then(), 11 more… } hawtio-core.js:83:11
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8181/hawtio/jolokia?con=fuse/&maxDepth=7&maxCollectionSize=500&ignoreErrors=true&canonicalNaming=false. (Reason: CORS header 'Access-Control-Allow-Origin' missing). (unknown)
so it seems to have something to do with CORS header.
When installing hawtio-integration using Bower, the following message is printed:
bower hawtio-integration#~2.0.3 invalid-meta The "main" field has to contain only 1 file per filetype; found multiple .js files: ["dist/metrics-watcher.js","dist/camelModel.js","dist/hawtio-integration.js"]
Bower expects only one main JavaScript file.
I've just declared more types and it revealed seemingly ES5 incompatibility issues:
plugins/activemq/ts/activemqPlugin.ts(128,41): error TS2339: Property 'findIndex' does not exist on type 'NodeSelection[]'.
plugins/camel/ts/breadcrumbBar.ts(118,56): error TS2339: Property 'find' does not exist on type 'NodeSelection[]'.
plugins/camel/ts/breadcrumbBar.ts(148,54): error TS2339: Property 'find' does not exist on type 'NodeSelection[]'.
I think it's just the tip of the iceberg, as there are many places where types are not declared but any
is used so the incompatibility issues are buried.
@alexkieling @astefanutti What do you think would be the right approach to fix it? Introducing es6-shim
? Upgrading the target to ES6
?
This new release has 2 new EIPs:
We should add specialized icons for those EIPs. There is some code somewhere where these Camel EIPs are mapped to icons, and if there is no mapping then a general icon is used. But the Claim Check EIP should use the icon of "Content Enricher" as it resembles this icon. And Saga should be the icon of a transaction.
In https://github.com/hawtio/hawtio-integration/blob/master/plugins/camel/ts/endpointChooser.ts we need to bring in the documentBase service and construct the right URL for these icons.
Source maps are necessary for browser debugging.
Bundle details page shows section headers and table headers even when there is no data to show and it looks a bit ugly. Those sections could be hidden when they have data.
In the Camel Debug page, hide the "Breakpoint suspended at" slideout when not stopped at any breakpoint.
Hi
It would be great if the Route Diagram did not display the element as separate box.
Example:
A description
$.name
The above generates a separate box for the description element.
Ideally the description should be shown when hovering over the setProperty box. But even just filter out the description boxes would be an improvement.
Kind regards
/Johan
Copy the generated schema file from hawtio v1 and override existing file here.
In the upcoming Camel 2.16 we have more stats about incoming and outgoing endpoints. So lets add a page to show that.
with the source code. We had the same problem with kubernetes, and @gashcrumb fixed this nicely. And also added a widget that used syntax highlighting. As the context in the panel would be xml, then it would be nice with syntax highlight there too.
Feature details page shows section headers and table headers even when there is no data to show and it looks a bit ugly. Those sections could be hidden when they have data.
Issues:
[16:46:02] gashcrumb howdy, btw i would like the hawtio-slider to be able to position itself lower - currently it slides in on the top of the screen
[16:46:26] i wonder if from top of u head would know if there is an option or so way to say slide with top corner from this position
[16:46:41] eg the idea is to keep top half for the visual camel route and then the 2nd half where it can slide in
[16:54:22] jpkroehling (~jpkroehli@redhat/jboss/jpkroehling) left IRC. (Quit: Leaving)
[16:56:59] jpkroehling (~jpkroehli@redhat/jboss/jpkroehling) joined the channel.
[17:02:58] jcordes (~[email protected]) left IRC. (Ping timeout: 264 seconds)
[17:11:36] wramblin_wreck (~[email protected]) joined the channel.
[17:16:17] wramblin_wreck (~[email protected]) left IRC. (Ping timeout: 265 seconds)
[17:21:47] davsclaus: yeah, think there's a height option, one sec let me check
[17:23:19] davsclaus: yep, you can pass 'top="10%"' or whatever
[17:23:35] and then also 'height="80%"' to change the height of the slideout
[17:23:43] ah thanks
[17:23:45] 10% and 80% there are the defaults
[17:23:58] and it's relative to the window viewport
Typo in Camel Route Diagram.
Steps to Reproduce:
Fix typo "totoal" to "total".
I've been playing with 2.0-M2 on WildFly / EAP and noticed an issue with the Camel context tree.
The tree view only seems to display one Camel context. If I deploy 2 camel applications into the container, I only ever see one of them.
In addition, the displayed Camel context changes depending on the name of the context. E.g it's picking the first one based on ascending order of context names.
Amq Send Delete Header raise JavaScript exception
Steps to Reproduce:
In the browse endpoint and trace and debug functions then the headers are not shown. There is a expander to show them, but the headerHtml is not shown, despite the source code builds a structure with the data.
If you delete all available Camel contexts, the view you're left with is a bit messy....
The Camel tab link is removed from the sidebar (as there's no active Camel apps anymore), but the context tree is still visible (but somewhat broken) showing the remnants of the last deleted context.
like components so we can see them and also their documentation. This requires Camel 2.16 onwards.
eg when you from the route diagram click on an EIP then it shows its properties as shown below. We should add some "back" button to take you back to the route diagram.
Also those turn [x] options on/off should be aligned and maybe styled better.
Port this ticket to v2
hawtio/hawtio#1904
The model which is generated for v1 should be ported to v2
The instance
feature of Karaf which provides org.apache.karaf:type=instance,*
MBeans is an old way to manage instances for Karaf, especially in cloud environments like OpenShift.
We should rewrite the page with other MBeans. See also: https://issues.jboss.org/browse/ENTESB-8098
Steps to Reproduce:
Error printed on the browser console:
[Core] Operation addOrUpdateRoutesFromXml(java.lang.String) failed due to: java.lang.IllegalArgumentException : Unmarshalled object is an unsupported type: org.apache.camel.model.FromDefinition -> From[timer:foo1]
The source code is not updated.
So when you click "routes" in the tree we should have a diagram button so you can see all of these routes on the same page.
And as bonus we should maybe have some filter box where you can filter by routes, and/or some selector to include/exclude by route id. Maybe some slider that you can slide in / out to do this.
Hi @alexkieling @gashcrumb what is up with this new v2 branch? We normally use master for hawtio v2 stuff.
It seems Alex did some PRs to the v2 branch. Should we not merge them to master and then delete that v2 branch?
Description of problem:
ActiveMQ password edit box in user preferences should be HTML input type password not normal edit box.
Steps to Reproduce:
Actual results:
You can see plain password in edit box ActiveMQ password
Expected results:
You can not see password in edit box.
The OSGi declarative services detail view provides an 'Deactivate button'. This attempts to invoke a non-existent MBean method named 'deactiveateComponent'. It should be 'deactivateComponent'.
When updating the Routes source or a specific route source and navigating to a route fragment, the route fragment source is out of date.
Port this ticket to v2: hawtio/hawtio#2001
Description of problem:
JavaScript errors in Camel Profile tab
Steps to Reproduce:
Actual results:
TypeError: Cannot set property 'length' of undefined
at listener (hawtio-ui.js:113)
at Object.$watchCollectionAction [as fn] (angular.js:14277)
at Scope.$digest (angular.js:14412)
at Scope.$apply (angular.js:14675)
at angular.js:16423
at completeOutstandingRequest (angular.js:4940)
at angular.js:5328
Expected results:
no errors
See #11
We can now link in/out routes together and then should be able to do a wobble diagram of all the routes in Camel context and see if any are connected.
And then take that a level higher for the entire JVM and all the CamelContexts.
Port hawtio/hawtio#2200
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.