July 2014 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3971) Source of the etc property files used when a child container is created in fabric

by ayache khettar (JIRA)

ayache khettar created JBESB-3971: ------------------------------------- Summary: Source of the etc property files used when a child container is created in fabric Key: JBESB-3971 URL: https://issues.jboss.org/browse/JBESB-3971 Project: JBoss ESB Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Configuration Reporter: ayache khettar Hi It would be nice if the AdminService module copies resources such as jre.properties from the parent instance when creating child container. More discussion on this can be found here: https://community.jboss.org/thread/241876 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3970) Use shared directory for Fuse binary content

by Ben Parees (JIRA)

[ https://issues.jboss.org/browse/JBESB-3970?page=com.atlassian.jira.plugin... ] Ben Parees closed JBESB-3970. ----------------------------- Resolution: Rejected wrong component. > Use shared directory for Fuse binary content > -------------------------------------------- > > Key: JBESB-3970 > URL: https://issues.jboss.org/browse/JBESB-3970 > Project: JBoss ESB > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ben Parees > > The Fuse RPM cartridge is embedding a zip of the Fuse product, and then on each app creation, it extracts the zip within the user's gear. > What it should be doing is > 1) embedding the Fuse product in an extracted form > 2) using the "fuse/usr" path so it's not copied into every user's gear (Openshift will link contents in the cartridge usr directory into the user's gear, rather than copying those files) > That would reduce the time required to create new fuse apps, and reduce the quota usage required for each gear. In addition, the current mechanism restricts the ability to path the Fuse product binaries at the node level (since each gear has its own copy of them now which will have to be patched in case of any security issues) > It has been noted by the Fuse team that due to the way patching and configuration are handled, some thought needs to go into what can be put into a shared (and not user modifiable) directory versus what can be created as read-only (from the user perspective) files. Some changes to the Fuse patching logic may be required in addition to restructuring the cartridge RPM. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3970) Use shared directory for Fuse binary content

by Ben Parees (JIRA)

Ben Parees created JBESB-3970: --------------------------------- Summary: Use shared directory for Fuse binary content Key: JBESB-3970 URL: https://issues.jboss.org/browse/JBESB-3970 Project: JBoss ESB Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Ben Parees The Fuse RPM cartridge is embedding a zip of the Fuse product, and then on each app creation, it extracts the zip within the user's gear. What it should be doing is 1) embedding the Fuse product in an extracted form 2) using the "fuse/usr" path so it's not copied into every user's gear (Openshift will link contents in the cartridge usr directory into the user's gear, rather than copying those files) That would reduce the time required to create new fuse apps, and reduce the quota usage required for each gear. In addition, the current mechanism restricts the ability to path the Fuse product binaries at the node level (since each gear has its own copy of them now which will have to be patched in case of any security issues) It has been noted by the Fuse team that due to the way patching and configuration are handled, some thought needs to go into what can be put into a shared (and not user modifiable) directory versus what can be created as read-only (from the user perspective) files. Some changes to the Fuse patching logic may be required in addition to restructuring the cartridge RPM. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3969) ESB Editor not default for jboss-esb.xml files

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3969?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBESB-3969: ------------------------------------------ There is no "ESB editor" persay - it's always been a customized version of the "JBoss Tools XML Editor" and that may be where the confusion lies. Do you see that in the "Open With" list? > ESB Editor not default for jboss-esb.xml files > ---------------------------------------------- > > Key: JBESB-3969 > URL: https://issues.jboss.org/browse/JBESB-3969 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Environment: Fedora 20, JBDS 7.1.1 with JBoss SOA 5.x Development installed. > Reporter: Peter Larsen > Assignee: Brian Fitzpatrick > Attachments: first.png, second.png, third.png > > > When double clicking on the jboss-esb.xml file the ESB editor is not opened. When trying to use "Open With" the ESB Editor is not shown in the list (see attached screendumps). > I can open the ESB Editor by first openening the ESB Configuration Visualizer and then opening the ESB Editor from the right drop-down menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3969) ESB Editor not default for jboss-esb.xml files

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBESB-3969?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick reassigned JBESB-3969: ---------------------------------------- Assignee: Brian Fitzpatrick > ESB Editor not default for jboss-esb.xml files > ---------------------------------------------- > > Key: JBESB-3969 > URL: https://issues.jboss.org/browse/JBESB-3969 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Environment: Fedora 20, JBDS 7.1.1 with JBoss SOA 5.x Development installed. > Reporter: Peter Larsen > Assignee: Brian Fitzpatrick > Attachments: first.png, second.png, third.png > > > When double clicking on the jboss-esb.xml file the ESB editor is not opened. When trying to use "Open With" the ESB Editor is not shown in the list (see attached screendumps). > I can open the ESB Editor by first openening the ESB Configuration Visualizer and then opening the ESB Editor from the right drop-down menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3969) ESB Editor not default for jboss-esb.xml files

by Peter Larsen (JIRA)

[ https://issues.jboss.org/browse/JBESB-3969?page=com.atlassian.jira.plugin... ] Peter Larsen updated JBESB-3969: -------------------------------- Attachment: third.png second.png first.png Screenshots showing the plugin installed, and the unability to open the ESB Editor. > ESB Editor not default for jboss-esb.xml files > ---------------------------------------------- > > Key: JBESB-3969 > URL: https://issues.jboss.org/browse/JBESB-3969 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Environment: Fedora 20, JBDS 7.1.1 with JBoss SOA 5.x Development installed. > Reporter: Peter Larsen > Attachments: first.png, second.png, third.png > > > When double clicking on the jboss-esb.xml file the ESB editor is not opened. When trying to use "Open With" the ESB Editor is not shown in the list (see attached screendumps). > I can open the ESB Editor by first openening the ESB Configuration Visualizer and then opening the ESB Editor from the right drop-down menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3969) ESB Editor not default for jboss-esb.xml files

by Peter Larsen (JIRA)

Peter Larsen created JBESB-3969: ----------------------------------- Summary: ESB Editor not default for jboss-esb.xml files Key: JBESB-3969 URL: https://issues.jboss.org/browse/JBESB-3969 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Environment: Fedora 20, JBDS 7.1.1 with JBoss SOA 5.x Development installed. Reporter: Peter Larsen When double clicking on the jboss-esb.xml file the ESB editor is not opened. When trying to use "Open With" the ESB Editor is not shown in the list (see attached screendumps). I can open the ESB Editor by first openening the ESB Configuration Visualizer and then opening the ESB Editor from the right drop-down menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2014