Re: camel-oaipmh : HTTPS and endpoint schema

2020-06-17 Thread Ralf Claussnitzer
Hi Juan, camel automatically detect everything after '?' as parameters for camel. So, my Component's createEndpoint method receives these inputs. This is exactly how components work. After all, it's an enpoint URI. All parts and parameters are there for configuring this enpoint. You need to

Re: camel-oaipmh : HTTPS and endpoint schema

2020-06-16 Thread Juan Segarra
Hi. I tried adding a prefix to the camel parameters as you suggested: oaipmh: https://revista.uisrael.edu.ec/index.php?page=oai=X=Y. .. But, camel automatically detect everything after '?' as parameters for camel. So, my Component's createEndpoint method receives these inputs. *uri*: oaipmh:

Re: camel-oaipmh : HTTPS and endpoint schema

2020-06-15 Thread Ralf Claussnitzer
Hi Juan, the components parameters are different from the actual generated URL. You could prefix parameters that are needed for consumer configuration with the component name. But this is actually no needed, since the valid OAI-PMH parameters are known. All other URI parameters must therefore

camel-oaipmh : HTTPS and endpoint schema

2020-06-13 Thread Juan Segarra
Hi all. I have been importing the code from the camel-oaipmh project [1] of Carlos Badenes to my project [2] and testing it against some servers that I know. The URI of the endpoints of the component looks like this. oaipmh://oa.upm.es/perl/oai2?camel-param1=mock=foo. And it assumes that the