Hi
You can adjust the constructors and/or pass in the right arguments to super.
You are allowed to do changes in the camel-quickfix code. It is
afterall this new component we want to be part of the Camel family.
On Fri, May 8, 2009 at 3:18 PM, Charles Moulliard <cmoulli...@gmail.com> wrote:
> I see that the constructor of ResourceBasedEndpoint is different from the
> one used now :
>
> public ResourceBasedEndpoint(String endpointUri, Component component,
> String resourceUri, Processor processor) {
> super(endpointUri, component, processor);
> this.resourceUri = resourceUri;
> }
>
> protected ResourceBasedEndpoint(String endpointUri, Processor processor,
> String resourceUri) {
> super(endpointUri, processor);
> this.resourceUri = resourceUri;
> }
>
> what we have
>
> public QuickfixEndpoint(String uri, CamelContext context, String
> configuration) {
> super(uri, context);
> this.configuration = configuration;
> }
>
> uri = endpointUri
> configuration = resourceUri
> *context is not equal to Component !!!*
>
>
> On Fri, May 8, 2009 at 2:45 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
>> Hi
>>
>> I suggest to take a look at camel-velocity endpoint how it extends
>> ResourceBasedEndpoint from camel-spring.
>> By doing this it gets all the resource loading for free.
>>
>> Then loading your quickfix files from classpath, file system, OSGi
>> should work out of the box.
>>
>> And we benefit from using the same reusable code for doing resource
>> loading with Camel components.
>>
>>
>>
>> On Fri, May 8, 2009 at 2:15 PM, Charles Moulliard <cmoulli...@gmail.com>
>> wrote:
>> > I have the same error when I remove the beans declaration in the spring
>> XML
>> > file :
>> >
>> > org.apache.camel.NoSuchEndpointException: No endpoint could be found for:
>> > quickfix-server:META-INF/examples/server.cfg, please check your classpath
>> > contains the needed camel component jar.
>> > at
>> >
>> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:54)
>> >
>> > Have you any idea about this ?
>> >
>> > But why are you setting both the IN and OUT to the same message?
>> > Good question. Anton is the author so I can't reply BUT what I can say is
>> > that in quickfix, the application (
>> > http://www.quickfixj.org/quickfixj/usermanual/usage/application.html)
>> which
>> > is the engine communicating with a FIX server can be of type ACCEPTOR or
>> > INITIATOR. You have to both configure the two applications because the
>> > engine is not a client/server application. In one case, you accept
>> incoming
>> > messages and in the other you generate the messages. The camel-quickfix
>> does
>> > not know which role it plays because it is defined in the config.file
>> > provided as input to the quickFixAcceptor or quickFixInitiator class.
>> These
>> > two classes call the same QuickFixEndpoint.
>> > *
>> > Maybe the class has to be splitted in two endpoints, one corresponding to
>> > each to avoid both IN/OUT ???*
>> >
>> >
>> > Charles Moulliard
>> > Senior Enterprise Architect
>> > Apache Camel Committer
>> >
>> > *****************************
>> > blog : http://cmoulliard.blogspot.com
>> >
>> >
>> > On Fri, May 8, 2009 at 1:23 PM, Charles Moulliard <cmoulli...@gmail.com
>> >wrote:
>> >
>> >> OK Willem I will test it.
>> >>
>> >> Have you any idea about this ?
>> >>
>> >> But why are you setting both the IN and OUT to the same message?
>> >> Good question. Anton is the author so I can't reply BUT what I can say
>> is
>> >> that in quickfix, the application (
>> >> http://www.quickfixj.org/quickfixj/usermanual/usage/application.html)
>> >> which is the engine communicating with a FIX server can be of type
>> ACCEPTOR
>> >> or INITIATOR. You have to both configure the two applications because
>> the
>> >> engine is not a client/server application. In one case, you accept
>> incoming
>> >> messages and in the other you generate the messages. The camel-quickfix
>> does
>> >> not know which role it plays because it is defined in the config.file
>> >> provided as input to the quickFixAcceptor or quickFixInitiator class.
>> These
>> >> two classes call the same QuickFixEndpoint.
>> >> *
>> >> Maybe the class has to be splitted in two endpoints, one corresponding
>> to
>> >> each to avoid both IN/OUT ???*
>> >>
>> >>
>> >> Regards,
>> >>
>> >> Charles Moulliard
>> >> Senior Enterprise Architect
>> >> Apache Camel Committer
>> >>
>> >> *****************************
>> >> blog : http://cmoulliard.blogspot.com
>> >>
>> >>
>> >> On Fri, May 8, 2009 at 12:25 PM, Willem Jiang <willem.ji...@gmail.com
>> >wrote:
>> >>
>> >>> Hi Charles,
>> >>>
>> >>> Can you try the camel trunk's camel-quickfix component?
>> >>> When I applied your patch , I found you did update the META-INF files
>> >>> after rename the component's package name.
>> >>> I test it with PAX-Exam, every thing looks good. You don't need to
>> >>> declare the beans.
>> >>>
>> >>> Willem
>> >>>
>> >>> Charles Moulliard wrote:
>> >>> > Willem,
>> >>> >
>> >>> > Any idea how to avoid to declare the beans in the spring xml file ?
>> >>> >
>> >>> > <bean id="quickfix-server"
>> >>> > class="org.apache.camel.component.quickfix.QuickfixAcceptor"/>
>> >>> > <bean id="quickfix-client"
>> >>> > class="org.apache.camel.component.quickfix.QuickfixInitiator"/>
>> >>> >
>> >>> >
>> >>> > <camel:camelContext trace="true" xmlns="
>> >>> > http://camel.apache.org/schema/osgi";>
>> >>> > <camel:route>
>> >>> > <camel:from
>> >>> uri="quickfix-server:META-INF/examples/server.cfg"/>
>> >>> > <camel:to
>> >>> uri="quickfix-client:META-INF/examples/client.cfg"/>
>> >>> > </camel:route>
>> >>> > </camel:camelContext>
>> >>> >
>> >>> > Normally, these classes should be instantiated by the camel endpoint
>> (is
>> >>> is
>> >>> > correct what I say or I'm completely stupid) ?
>> >>> >
>> >>> > Regards,
>> >>> >
>> >>> > Charles Moulliard
>> >>> > Senior Enterprise Architect
>> >>> > Apache Camel Committer
>> >>> >
>> >>> > *****************************
>> >>> > blog : http://cmoulliard.blogspot.com
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>> Apache Camel Reference Card:
>> http://refcardz.dzone.com/refcardz/enterprise-integration
>> Interview with me:
>>
>> http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
>>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
