[jira] [Commented] (CAMEL-15142) Build a Documentation Under Constructions handlebar
[ https://issues.apache.org/jira/browse/CAMEL-15142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127071#comment-17127071 ] Zoran Regvart commented on CAMEL-15142: --- [~Aemie] I think we had those documents before, not sure if the code generation overwritten them or they should not be linked to. Perhaps [~acosentino] might know. In any case we're going to have work in progress documents, that might appear empty, not sure how to handle that other than to find all those documents and put a notice in them. It's a bit unclear to me what "construction page handlebar" would be and how would it be implemented. > Build a Documentation Under Constructions handlebar > --- > > Key: CAMEL-15142 > URL: https://issues.apache.org/jira/browse/CAMEL-15142 > Project: Camel > Issue Type: Task >Reporter: Aemie >Priority: Major > Labels: outreachy2020 > > * I observed that for certain pages including > [https://camel.apache.org/camel-spring-boot/latest/spring-cloud-zookeeper.html] > & > [https://camel.apache.org/camel-spring-boot/latest/spring-cloud-consul.html], > the documentation is yet not written however published on the website. So in > such cases, I believe it is a good practice to include a construction page > handlebar as a user would be informed about if documentation is yet to be > made or not. > * What are your opinions on this, [~zregvart]? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15140) Improve Main Menu for Mobile Screens
[ https://issues.apache.org/jira/browse/CAMEL-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127068#comment-17127068 ] Zoran Regvart commented on CAMEL-15140: --- I think this is a good direction, I think the first option has the highest contrast so from accessibility it might be the best option. I like that the icons are large, we should consider increasing the sizes of other icons and the hamburger menu itself, perhaps by removing the "Apache Camel" text and having just the logo on smaller screens. I find the hamburger menu is pushed too much to the right side of the screen and all icons a bit too small at 375pt. I think we need to think about applying the same design choices to the front page and to the menu icons, right now on the front page we have icons with outline on white background, here we have filled icons on inverse background, I think we should choose one of those and apply it consistently (I would choose the latter for both). I think we should also take advantage of the vertical space to incorporate the menu (hamburger icon) on the second row along with the search similar to how it's done at https://getbootstrap.com/docs/, I left a comment about this on CAMEL-14958 as well. This could also allow the current icons we have (GitHub, Gitter, Twitter) to occupy more space and perhaps allow space for more icons (e.g. Stackoverflow). > Improve Main Menu for Mobile Screens > > > Key: CAMEL-15140 > URL: https://issues.apache.org/jira/browse/CAMEL-15140 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aashna Jena >Priority: Major > Labels: outreachy2020 > Attachments: issue-mutation.png, mobile-menu-mockup-1.png, > mobile-menu-mockup-2.png, mobile-menu-mockup-3.png, mobile-menu-mockup-4.png, > mobile-menu-mockup-5.png, screenshot-1.png > > > Our current menu for mobile screens is a list of text items with a small > drop-down arrow, which don't really make for a good touch target. I like how > the facebook app displays menu items - they take up the full screen and each > menu item has an icon and text enclosed in a box-like structure. I also like > Amazon app's menu, where sub-menus replace the menu space instead of opening > up as drop-downs. I can post some mock-ups if we are open to changing the > design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127063#comment-17127063 ] Zoran Regvart commented on CAMEL-14958: --- [~Aemie] I guess one option would be to place the search at the bottom of the mobile menu, similar to how https://www.typescriptlang.org/ does it. I was looking at how projects listed on https://docsearch.algolia.com/ approach this, and seems like a fair number of them opt to show the search input always and in almost full width. I think the approach on https://getbootstrap.com/docs/ is particularly good one. > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Labels: outreachy2020, suggestions > Attachments: inline-search.png, nav-search-icon-1220.png, > nav-searchbar-1220.png, nav-searchbar-414.png, navbar-search-414.png, > navbar-searchbar.png > > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14904) Nav pane does not show current page
[ https://issues.apache.org/jira/browse/CAMEL-14904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127035#comment-17127035 ] ASF GitHub Bot commented on CAMEL-14904: zregvart commented on pull request #378: URL: https://github.com/apache/camel-website/pull/378#issuecomment-639744271 @AemieJ perhaps I wasn't too clear, sorry about that, I think that the `panel` passed into `scrollItemToMidpoint` doesn't need to be the `div` with `data-panel="menu"` it could be the `nav` that we do scroll. That is, make the same change we made in CSS in the JavaScript, we don't scroll that `div`, we scroll the `nav`, keeping the quick search fixed at the top. What I think can be done is to move `data-panel="menu"` to the `nav`, I think that then we might not need any JavaScript changes. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Nav pane does not show current page > --- > > Key: CAMEL-14904 > URL: https://issues.apache.org/jira/browse/CAMEL-14904 > Project: Camel > Issue Type: Task > Components: website >Affects Versions: 3.2.0 >Reporter: David Jencks >Priority: Major > > The Antora default UI highlights and makes sure the nav list item for the > current page remains visible. The Camel components list does not do this, > always scrolling to the top when you click on an item. This makes it very > hard to use. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127034#comment-17127034 ] ASF GitHub Bot commented on CAMEL-14994: zregvart commented on pull request #370: URL: https://github.com/apache/camel-website/pull/370#issuecomment-639741181 @aashnajena sounds great, I'd like to unify the design across the front page and the projects page, I suggest that we start with the simplest design and work from that. I'm really adverse to shortening the words, e.g. documentation to docs, this is my personal preference, doesn't have to be universally shared. I strongly believe that making things simpler takes more effort and that it pays of in the future by making maintenance/changes easier to do. We need to have a consistent design, I suggest that we start with the minimal changes and unify/change design between the front page and the projects page. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png, projects_mockup.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15146) Handle validatorFactory field in BeanValidatorComponentConfigurer
[ https://issues.apache.org/jira/browse/CAMEL-15146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-15146. - Resolution: Fixed > Handle validatorFactory field in BeanValidatorComponentConfigurer > - > > Key: CAMEL-15146 > URL: https://issues.apache.org/jira/browse/CAMEL-15146 > Project: Camel > Issue Type: Improvement > Components: camel-bean-validator >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 3.4.0 > > > Seems there's the intention of being able to provide a custom > ValidatorFactory to BeanValidatorComponent. But, there's no getter or setter > method for the private validatorFactory field. Thus it can never be handled > by BeanValidatorComponentConfigurer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15129. -- Resolution: Fixed > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.4.0 > > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work stopped] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15129 stopped by Andrea Cosentino. > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.4.0 > > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-15129: - Fix Version/s: 3.4.0 > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Priority: Major > Fix For: 3.4.0 > > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-15129: Assignee: Andrea Cosentino > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.4.0 > > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15129 started by Andrea Cosentino. > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.4.0 > > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14992) Create a Camel AWS2 Athena component
[ https://issues.apache.org/jira/browse/CAMEL-14992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126702#comment-17126702 ] Jon Chase commented on CAMEL-14992: --- PR is up! [https://github.com/apache/camel/pull/3891] I've attached the doc HTML, as that might be the best place to start for an overview. ;) [^aws2-athena-component.html] > Create a Camel AWS2 Athena component > > > Key: CAMEL-14992 > URL: https://issues.apache.org/jira/browse/CAMEL-14992 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.x > > Attachments: aws2-athena-component.html > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14992) Create a Camel AWS2 Athena component
[ https://issues.apache.org/jira/browse/CAMEL-14992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Chase updated CAMEL-14992: -- Attachment: aws2-athena-component.html > Create a Camel AWS2 Athena component > > > Key: CAMEL-14992 > URL: https://issues.apache.org/jira/browse/CAMEL-14992 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.x > > Attachments: aws2-athena-component.html > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15141) documentation - Image not display on a FAQ page
[ https://issues.apache.org/jira/browse/CAMEL-15141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126625#comment-17126625 ] Mauro Filanti commented on CAMEL-15141: --- Nice! When the site will be live with this new commits? > documentation - Image not display on a FAQ page > --- > > Key: CAMEL-15141 > URL: https://issues.apache.org/jira/browse/CAMEL-15141 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, outreachy2020 > Fix For: 3.x > > Attachments: image-2020-06-04-15-09-31-337.png, > image-2020-06-04-15-17-06-567.png, image-2020-06-04-15-18-45-423.png > > > See this page > https://camel.apache.org/manual/latest/faq/using-getin-or-getout-methods-on-exchange.html > There is an image that is not displayed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15141) documentation - Image not display on a FAQ page
[ https://issues.apache.org/jira/browse/CAMEL-15141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126625#comment-17126625 ] Mauro Filanti edited comment on CAMEL-15141 at 6/5/20, 10:20 AM: - Nice! When the site will go live with this new commits? was (Author: bigghe): Nice! When the site will be live with this new commits? > documentation - Image not display on a FAQ page > --- > > Key: CAMEL-15141 > URL: https://issues.apache.org/jira/browse/CAMEL-15141 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, outreachy2020 > Fix For: 3.x > > Attachments: image-2020-06-04-15-09-31-337.png, > image-2020-06-04-15-17-06-567.png, image-2020-06-04-15-18-45-423.png > > > See this page > https://camel.apache.org/manual/latest/faq/using-getin-or-getout-methods-on-exchange.html > There is an image that is not displayed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126598#comment-17126598 ] Aemie commented on CAMEL-14958: --- !inline-search.png! [~zregvart] if we were to include the design method you suggested, then we need to think about how we are going to be presenting the search results as well and this is applicable for width < 1024px only however for width between 1024 <= width <= 1220px, we need to include search too and the method I suggested would be more applicable at that point. What do you think? > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Labels: outreachy2020, suggestions > Attachments: inline-search.png, nav-search-icon-1220.png, > nav-searchbar-1220.png, nav-searchbar-414.png, navbar-search-414.png, > navbar-searchbar.png > > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aemie updated CAMEL-14958: -- Attachment: inline-search.png > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Labels: outreachy2020, suggestions > Attachments: inline-search.png, nav-search-icon-1220.png, > nav-searchbar-1220.png, nav-searchbar-414.png, navbar-search-414.png, > navbar-searchbar.png > > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15140) Improve Main Menu for Mobile Screens
[ https://issues.apache.org/jira/browse/CAMEL-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126491#comment-17126491 ] María Arias de Reyna commented on CAMEL-15140: -- > For the first one, I don't think the mockup-design 1 would be good for the > larger screen width i.e 675px - 1024px I agree on that. I wouldn't like to have a third intermediate style, that's too much work. Do we have to redefine what is mobile and what is desktop? For tablets as a general rule, desktop version is usually enough. Unless we make links too small. I don't have a tablet with me to test the current desktop style, sorry. > Improve Main Menu for Mobile Screens > > > Key: CAMEL-15140 > URL: https://issues.apache.org/jira/browse/CAMEL-15140 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aashna Jena >Priority: Major > Labels: outreachy2020 > Attachments: issue-mutation.png, mobile-menu-mockup-1.png, > mobile-menu-mockup-2.png, mobile-menu-mockup-3.png, mobile-menu-mockup-4.png, > mobile-menu-mockup-5.png, screenshot-1.png > > > Our current menu for mobile screens is a list of text items with a small > drop-down arrow, which don't really make for a good touch target. I like how > the facebook app displays menu items - they take up the full screen and each > menu item has an icon and text enclosed in a box-like structure. I also like > Amazon app's menu, where sub-menus replace the menu space instead of opening > up as drop-downs. I can post some mock-ups if we are open to changing the > design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15140) Improve Main Menu for Mobile Screens
[ https://issues.apache.org/jira/browse/CAMEL-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126489#comment-17126489 ] María Arias de Reyna commented on CAMEL-15140: -- I agree that mockup-1 is the best. > Since we are adding icons, should these icons be visible for big screens as > well? As a general rule I think it makes sense to be consistent on style. So if an icon is associated with an action or a section, that icon should be kept on all screen types. But, not as big, you know. If it is a touch screen I need space for my finger. If it is not, I prefer smaller links. > They will take up more horizontal space if we place icons just before the > text. My suggestion is to not have icons for big screens for now, maybe we > can look at a different design for including icons in the header menu in a > later iteration. If the icon is small enough I don't think it will be a problem to eat a bit more horizontal space, right? I am not a good stylist so maybe I'm wrong :) On an ideal world, the change between mobile and desktop is "just" CSS resizing and reshaping stuff, not adding or removing. > The other option is to keep the sub-menus, for which we can use the mockup-4 > or mockup-5 design. There should be some kind of breadcrumb to know where I am so I don't get lost on navigation. I should be able to easily jump a level up inside the hierarchy of menus. But it doesn't have to show all the possible top menu options. It may be just that, a button to jump one level higher. That could allow us to keep the design 1. > Improve Main Menu for Mobile Screens > > > Key: CAMEL-15140 > URL: https://issues.apache.org/jira/browse/CAMEL-15140 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aashna Jena >Priority: Major > Labels: outreachy2020 > Attachments: issue-mutation.png, mobile-menu-mockup-1.png, > mobile-menu-mockup-2.png, mobile-menu-mockup-3.png, mobile-menu-mockup-4.png, > mobile-menu-mockup-5.png, screenshot-1.png > > > Our current menu for mobile screens is a list of text items with a small > drop-down arrow, which don't really make for a good touch target. I like how > the facebook app displays menu items - they take up the full screen and each > menu item has an icon and text enclosed in a box-like structure. I also like > Amazon app's menu, where sub-menus replace the menu space instead of opening > up as drop-downs. I can post some mock-ups if we are open to changing the > design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126459#comment-17126459 ] Yaroslav Chukhno commented on CAMEL-15129: -- Sorry guys, i made mistake in description. On *throwExceptionOnFailure=false* all exceptions in UndertowClientCallback will be suppressed. As example, if in [https://github.com/apache/camel/blob/7df7778b1a2afe4a2da0730c11f6b1926f613943/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowClientCallback.java#L279] will be thrown IOException, then it will be supressed in [https://github.com/apache/camel/blob/7df7778b1a2afe4a2da0730c11f6b1926f613943/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowClientCallback.java#L291] because the [https://github.com/apache/camel/blob/7df7778b1a2afe4a2da0730c11f6b1926f613943/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowClientCallback.java#L187] has not be executed > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Priority: Major > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126463#comment-17126463 ] Chandrakant Hardahe commented on CAMEL-15129: - Thanks [~uzuruk], for the clarification,I'm looking into it > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Priority: Major > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15151) Cannot use placeholders on RedeliveryPolicy enums
[ https://issues.apache.org/jira/browse/CAMEL-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved CAMEL-15151. - Resolution: Fixed > Cannot use placeholders on RedeliveryPolicy enums > - > > Key: CAMEL-15151 > URL: https://issues.apache.org/jira/browse/CAMEL-15151 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.3.0 >Reporter: Brad Harvey >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 3.4.0 > > > does not > work due to IllegalArgumentException: no enum constant > org.apache.camel.LoggingLevel.placeholder. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15129) Camel-Undertow: throwExceptionOnFailure suppress all exception that not related to HttpStatusCode
[ https://issues.apache.org/jira/browse/CAMEL-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126420#comment-17126420 ] Chandrakant Hardahe commented on CAMEL-15129: - Hi [~uzuruk], if *throwExceptionOnFailure=true* then it'll throw HttpOperationFailedException in case of failed responses from the remote server [https://github.com/apache/camel/blob/master/components/camel-undertow/src/main/java/org/apache/camel/component/undertow/UndertowClientCallback.java#L235] , can you please provide a test scenario for any other exception? > Camel-Undertow: throwExceptionOnFailure suppress all exception that not > related to HttpStatusCode > - > > Key: CAMEL-15129 > URL: https://issues.apache.org/jira/browse/CAMEL-15129 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Affects Versions: 3.3.0 >Reporter: Yaroslav Chukhno >Priority: Major > > If option throwExceptionOnFailure=true then UndertowClientCallback suppresses > all exceptions that are not even related to HttpStatusCode (failed responses > from the remote server). -- This message was sent by Atlassian Jira (v8.3.4#803005)
