AEM CRXDE Query widget customization
I need to customize the query widget in CRXDE (the one from Tools -> Query). Specifically I need to be able to add a new button to save queries into some sort of favorites as well as to load them.
And a second button in search result widget to export the results into a excel file.
Any idea what nodes/templates are related to each widget?
aem cq5 crx
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
add a comment |
I need to customize the query widget in CRXDE (the one from Tools -> Query). Specifically I need to be able to add a new button to save queries into some sort of favorites as well as to load them.
And a second button in search result widget to export the results into a excel file.
Any idea what nodes/templates are related to each widget?
aem cq5 crx
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
2
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37
add a comment |
I need to customize the query widget in CRXDE (the one from Tools -> Query). Specifically I need to be able to add a new button to save queries into some sort of favorites as well as to load them.
And a second button in search result widget to export the results into a excel file.
Any idea what nodes/templates are related to each widget?
aem cq5 crx
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
I need to customize the query widget in CRXDE (the one from Tools -> Query). Specifically I need to be able to add a new button to save queries into some sort of favorites as well as to load them.
And a second button in search result widget to export the results into a excel file.
Any idea what nodes/templates are related to each widget?
aem cq5 crx
aem cq5 crx
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
asked Nov 15 '18 at 14:57
Diana RDiana R
1,1121821
1,1121821
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
2
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37
add a comment |
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
2
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
2
2
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37
add a comment |
1 Answer
1
active
oldest
votes
I believe this interface is not designed with overlays in mind. I'd be very cautious about extending it.
While you're still using AEM 6.1, there's a lot that has been done recently about improving the visibility of what should and what shouldn't be customized in AEM.
Furthermore, CRXDE is the kind of interface I really wouldn't like to break because of a bug in an overlay. It's just the kind of a low-level, last-resort UI that I like to be rock-solid.
CRXDE has remained relatively unchanged at least since AEM 5.6 but customising this particular interface could still cause you trouble at a later date when you need to upgrade. And if you're still using 6.1, it's likely that you'll be due for an upgrade to a newer version. 6.1 has reached end of core support and extended support is only planned until 2020
If I were you, I'd consider implementing a custom interface of your own. It might just be easier and you would be free to add further functionality without risking it breaking during an AEM upgrade.
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322193%2faem-crxde-query-widget-customization%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe this interface is not designed with overlays in mind. I'd be very cautious about extending it.
While you're still using AEM 6.1, there's a lot that has been done recently about improving the visibility of what should and what shouldn't be customized in AEM.
Furthermore, CRXDE is the kind of interface I really wouldn't like to break because of a bug in an overlay. It's just the kind of a low-level, last-resort UI that I like to be rock-solid.
CRXDE has remained relatively unchanged at least since AEM 5.6 but customising this particular interface could still cause you trouble at a later date when you need to upgrade. And if you're still using 6.1, it's likely that you'll be due for an upgrade to a newer version. 6.1 has reached end of core support and extended support is only planned until 2020
If I were you, I'd consider implementing a custom interface of your own. It might just be easier and you would be free to add further functionality without risking it breaking during an AEM upgrade.
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
add a comment |
I believe this interface is not designed with overlays in mind. I'd be very cautious about extending it.
While you're still using AEM 6.1, there's a lot that has been done recently about improving the visibility of what should and what shouldn't be customized in AEM.
Furthermore, CRXDE is the kind of interface I really wouldn't like to break because of a bug in an overlay. It's just the kind of a low-level, last-resort UI that I like to be rock-solid.
CRXDE has remained relatively unchanged at least since AEM 5.6 but customising this particular interface could still cause you trouble at a later date when you need to upgrade. And if you're still using 6.1, it's likely that you'll be due for an upgrade to a newer version. 6.1 has reached end of core support and extended support is only planned until 2020
If I were you, I'd consider implementing a custom interface of your own. It might just be easier and you would be free to add further functionality without risking it breaking during an AEM upgrade.
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
add a comment |
I believe this interface is not designed with overlays in mind. I'd be very cautious about extending it.
While you're still using AEM 6.1, there's a lot that has been done recently about improving the visibility of what should and what shouldn't be customized in AEM.
Furthermore, CRXDE is the kind of interface I really wouldn't like to break because of a bug in an overlay. It's just the kind of a low-level, last-resort UI that I like to be rock-solid.
CRXDE has remained relatively unchanged at least since AEM 5.6 but customising this particular interface could still cause you trouble at a later date when you need to upgrade. And if you're still using 6.1, it's likely that you'll be due for an upgrade to a newer version. 6.1 has reached end of core support and extended support is only planned until 2020
If I were you, I'd consider implementing a custom interface of your own. It might just be easier and you would be free to add further functionality without risking it breaking during an AEM upgrade.
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
I believe this interface is not designed with overlays in mind. I'd be very cautious about extending it.
While you're still using AEM 6.1, there's a lot that has been done recently about improving the visibility of what should and what shouldn't be customized in AEM.
Furthermore, CRXDE is the kind of interface I really wouldn't like to break because of a bug in an overlay. It's just the kind of a low-level, last-resort UI that I like to be rock-solid.
CRXDE has remained relatively unchanged at least since AEM 5.6 but customising this particular interface could still cause you trouble at a later date when you need to upgrade. And if you're still using 6.1, it's likely that you'll be due for an upgrade to a newer version. 6.1 has reached end of core support and extended support is only planned until 2020
If I were you, I'd consider implementing a custom interface of your own. It might just be easier and you would be free to add further functionality without risking it breaking during an AEM upgrade.
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
edited Nov 25 '18 at 19:10
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
answered Nov 20 '18 at 10:46
toniedzwiedztoniedzwiedz
13k85596
13k85596
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
add a comment |
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
yeah, totally make sense. The reason why we thought to enhance the functionality was specifically because it is so stable and upgrade (which will happen very soon) is not going to break it (too much). By "implementing a custom interface" do you mean adding a completely new page in AEM Web Console?
– Diana R
Nov 20 '18 at 14:07
1
1
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
Yes, I would actually prefer to build it from scratch as a separate console of really needed. Apart from the potential to break, you may find it quite difficult to understand and extend. As far as I can tell, it's not backed by actual components sitting on the JCR and just seeing how it works may require decompiling some classes. Sounds cumbersome and it's probably against the license anyway.
– toniedzwiedz
Nov 20 '18 at 18:44
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322193%2faem-crxde-query-widget-customization%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
which version of AEM are you on ?
– SubSul
Nov 20 '18 at 6:10
@SubSul 6.1 SP2
– Diana R
Nov 20 '18 at 10:06
2
Unlike most of other stuff in aem crxde code doesn't actually reside in jcr, but in an OSGi bundle. I guess it's possible to decompile the bundle jar and rebuild after making changes, if you really want to.
– awd
Nov 20 '18 at 18:37