ddoaj97 opened a new issue, #730:
URL: https://github.com/apache/camel-karavan/issues/730

   Many Camel component have more than one path parameter and currently the 
visual Karavan editor doesn't seem to handle these components very well. For 
example the Quartz component URI syntax is defined as  
"quartz:groupName/triggerName" and contains two path parameters: "groupName" 
and "triggerName". Trying to configure these path properties in Karavan 
generates an incorrect URI because Karavan seems to mix up the two path 
properties.
   
   Trying to enter the value "test" in the "Group name" input field of the 
Quartz component causes Karavan to generate the following URI:
   
![karavan_uri_path_bug_quartz](https://user-images.githubusercontent.com/17296796/233015685-4ba062e5-1724-4bfd-8146-1de839d141b4.PNG)
   
   It seems like the first character of the "Group name" gets parsed into the 
"Trigger name" field and only the remaining characters end up in the "Group 
name" field. The problem disappears once both input fields have a value, but as 
soon as you clear the group name and enter a new value, then the same issue 
occurs again.
   
   **I've tried other components that have multiple path properties (activemq, 
jms, rest, ftp, imap, ...) and they all have the same problem.**
   
   Components with more than 2 path properties seem to be even more buggy. For 
example the "springws" component has 4 path properties and is completely 
unuseable. Trying to enter the value "expression" into the "Expression" input 
field seems to duplicate this value multiple times into the "Web Service 
Endpoint Uri" input field:
   
![karavan_uri_path_bug_springws](https://user-images.githubusercontent.com/17296796/233016014-fad0f3ce-0df2-4247-8156-70e2f8443824.PNG)
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to