Messages posted by: sfrancolla

Thanks, fellas.

For future reference, in the case that one of us developers has a project that depends on Metc (or anything else) where said project has a conflict resolving an outdated dependency, the developer's fix is as follows.

Include a depMgmt block like this in your pom.xml:

<groupId>myProject</groupId> 
  <artifactId>myArtifact</artifactId> 
  <packaging>jar</packaging> 
  <version>1.0-SNAPSHOT</version> 
  <name>myArtifact</name> 
  <url>http://maven.apache.org</url>

<dependency> 
        <groupId>erroneousGroup</groupId> 
        <artifactId>erroneousArtifact</artifactId> 
        <version>1.0-SNAPSHOT</version> 
        <type>jar</type> 
        <scope>import</scope> 
      </dependency>

<dependency> 
        <groupId>log4j</groupId> 
        <artifactId>log4j</artifactId>

<version>1.2.15</version>

</dependency> 
    </dependencies> 
  </dependencyManagement>

<dependencies> 
    <dependency> 
      <groupId>erroneousGroup</groupId> 
      <artifactId>erroneousArtifact</artifactId> 
      <scope>compile</scope> 
    </dependency> 
  </dependencies>

</project>

So, since my project depends on some Metc sub-projects, my project's pom.xml includes its dependencies like this:

<dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.marketcetera</groupId>
        <artifactId>core</artifactId>
        <version>1.5.0</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>org.marketcetera</groupId>
        <artifactId>util</artifactId>
        <version>1.5.0</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>org.marketcetera</groupId>
        <artifactId>strategy</artifactId>
        <version>1.5.0</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>org.marketcetera</groupId>
        <artifactId>strategyagent</artifactId>
        <version>1.5.0</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>log4j</groupId>
        <artifactId>log4j</artifactId>
        <version>1.2.15</version>
      </dependency>
    </dependencies>
  </dependencyManagement>

<dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.marketcetera</groupId>
      <artifactId>core</artifactId>
      <version>1.5.0</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.marketcetera</groupId>
      <artifactId>util</artifactId>
      <version>1.5.0</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.marketcetera</groupId>
      <artifactId>strategy</artifactId>
      <version>1.5.0</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>org.marketcetera</groupId>
      <artifactId>strategyagent</artifactId>
      <version>1.5.0</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>

Maven user group thread regarding this fix:
http://old.nabble.com/I-have-the-right-version,-but-maven-can't-find-it-td28383590.html

SF

Colin, could you please edit the uberPom.xml in the metc repo to reflect this log4j dependency fix so that projects that depend on Metc 1.5 install properly independent of a local Metc build?

Thanks.

- SF

The Metc 1.6 tag has been downloadable for a long time.

See it here:
http://code.marketcetera.org/root/tags/

Yes, there's not much activity here. I'd say the company is focusing on their commercial application and business. It's too bad they haven't released anything publicly in a year. At least we'd have an updated basis for contribution.

Any other suggestions? I was up and running wtih Metc 1.5, have upgraded to 1.6, and now cannot connect photon to ors.

Details here:
http://www.marketcetera.org/community/posts/list/437.page

Help!?

I'd been running Metc 1.5.0 without issue after a few tweaks. I just built 1.6.0 from source successfully, started ORS, and ran as debug the Photon launch. When I try to log in, I receive the following error.

"Unable to connect to the server using the URL 'tcp://192.168.1.100:61616' user name 'admin, host name '192.168.1.100' and post number '9000'..."

Some detail:
- As you can see, I am using the exact 192.168.1.100 ip address as produced by ipconfig.
- ORS had started up successfully and is running heartbeats.
- I used the username/password: admin/admin.
- There is no firewall to be concerned with.

I did notice that "netstat -an" produces the following lines among the set while ORS it not running but I'm not too, too concerned with them as I'm pointing photon to 192.168.1.100 directly:

What am I missing here?

Thanks.

SF

RESOLVED.

I upgraded org.apache.felix dependency in uberPom.xml to version 2.0.0.

per the last comment on:
https://issues.apache.org/jira/browse/FELIX-677?focusedCommentId=12681193&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12681193

Metc 1.5.0 builds successfully on my system. Now, I'm trying to build Metc 1.6.0 and receiving the error in the log below.

I'm doing:
> mvn -f uberPom.xml install
> mvn -DskipTests=true install

It's failing at "Building Photon Third Party Dependency Bundle".

I'd have presumed that there would be some fix that I can make to either of these files:
- C:\marketcetera-platform\source\photon\maven\pom.xml
- C:\marketcetera-platform\source\photon\maven\bundle\pom.xml
...but a diff with each of these in Metc 1.5.0 shows no big changes.

How are others getting around this?

Thanks.

[INFO] Installing C:\marketcetera-platform\source\photon\maven\pom.xml to M:\r\org\marketcetera\photon-maven\1.6.0\photon-maven-1.6.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building Photon Third Party Dependency Bundle
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting file set: C:\marketcetera-platform\source\photon\maven\bundle\target (included: [**], excluded: [])
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Tests are skipped.
[INFO] [bundle:bundle]
[ERROR] Error building bundle org.marketcetera:photon-bundle:bundle:1.6.0 : Unresolved references to [.] by class(es) on the Bundle-Classpath[Jar:csv-1.0.jar, Jar:xbean-spring-3.3.jar, Jar:cxf-rt-core-2.1.2.jar, Jar:spring-context-2.5.2.jar, Jar:xmlParserAPIs-2.6.2.jar, Jar:log4j-1.2.14.jar, Jar:jsr305-1.3.8.jar, Jar:commons-beanutils-1.8.0.jar, Jar:camel-core-1.5.0.jar, Jar:asm-xml-3.1.jar, Jar:cxf-rt-bindings-soap-2.1.2.jar, Jar:cxf-rt-bindings-xml-2.1.2.jar, Jar:spring-core-2.5.2.jar, Jar:cxf-common-utilities-2.1.2.jar, Jar:glazedlists_java15-1.8.0.jar, Jar:commons-logging-1.0.3.jar, Jar:joda-time-1.5.1.jar, Jar:persistence-api-1.0.jar, Jar:cxf-rt-frontend-jaxws-2.1.2.jar, Jar:commons-cli-1.1.jar, Jar:annotations-1.3.8.jar, Jar:jaxen-1.1.1.jar, Jar:commons-pool-1.2.jar, Jar:geronimo-jta_1.1_spec-1.1.1.jar, Jar:geronimo-javamail_1.4_spec-1.3.jar, Jar:asm-tree-3.1.jar, Jar:spring-2.5.2.jar, Jar:velocity-dep-1.4.jar, Jar:xml-apis-1.0.b2.jar, Jar:spring-web-2.5.2.jar, Jar:cxf-api-2.1.2.jar, Jar:geronimo-jaxws_2.1_spec-1.0.jar, Jar:neethi-2.0.4.jar, Jar:cxf-common-schemas-2.1.2.jar, Jar:xercesImpl-2.6.2.jar, Jar:antlr-2.7.7.jar, Jar:xalan-2.6.0.jar, Jar:aopalliance-1.0.jar, Jar:jaxb-impl-2.1.7.jar, Jar:geronimo-ws-metadata_2.0_spec-1.1.2.jar, Jar:cxf-rt-frontend-simple-2.1.2.jar, Jar:xom-1.0.jar, Jar:FastInfoset-1.2.2.jar, Jar:XmlSchema-1.4.2.jar, Jar:quickfixj-all-1.3.3-bd.jar, Jar:icu4j-2.6.1.jar, Jar:commons-io-1.4.jar, Jar:jruby-1.1.3.jar, Jar:google-collections-1.0-rc2.jar, Jar:xml-resolver-1.2.jar, Jar:slf4j-api-1.5.3.jar, Jar:backport-util-concurrent-2.1.jar, Jar:antlr-runtime-3.1.1.jar, Jar:saaj-api-1.3.jar, Jar:geronimo-annotation_1.0_spec-1.1.1.jar, Jar:commons-lang-2.4.jar, Jar:bsf-2.4.0.jar, Jar:asm-util-3.1.jar, Jar:asm-analysis-3.1.jar, Jar:commons-logging-api-1.1.jar, Jar:commons-collections-3.2.1.jar, Jar:commons-csv-20081024.jar, Jar:jFormatString-1.3.8.jar, Jar:activemq-core-5.2.0.jar, Jar:wstx-asl-3.2.4.jar, Jar:cxf-rt-databinding-jaxb-2.1.2.jar, Jar:velocity-1.4.jar, Jar:stringtemplate-3.2.jar, Jar:cglib-nodep-2.1_3.jar, Jar:geronimo-jta_1.0.1B_spec-1.0.1.jar, Jar:jaxb-api-2.1.jar, Jar:geronimo-jms_1.1_spec-1.1.1.jar, Jar:cxf-rt-ws-addr-2.1.2.jar, Jar:saaj-impl-1.3.jar, Jar:activeio-core-3.1.0.jar, Jar:dom4j-1.6.1.jar, Jar:activemq-pool-5.2.0.jar, Jar:asm-commons-3.1.jar, Jar:bcel-1.3.8.jar, Jar:slf4j-log4j12-1.5.3.jar, Jar:cxf-rt-transports-http-2.1.2.jar, Jar:cxf-tools-common-2.1.2.jar, Jar:geronimo-stax-api_1.0_spec-1.0.1.jar, Jar:jdom-1.0.jar, Jar:geronimo-activation_1.1_spec-1.0.2.jar, Jar:wsdl4j-1.6.2.jar, Jar:commons-i18n-20081024.jar, Jar:geronimo-j2ee-management_1.0_spec-1.0.jar, Jar:mina-core-1.1.0.jar, Jar:asm-3.1.jar, Jar:esper-3.1.0.jar, Jar:spring-beans-2.5.2.jar]: [JDOMAbout$Info.class, JDOMAbout.class, JDOMAbout$Author.class]
[ERROR] Error(s) found in bundle configuration
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error(s) found in bundle configuration

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error(s) found in bundle configuration
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error(s) found in bundle configuration
	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:344)
	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
	... 16 more
Caused by: org.apache.maven.plugin.MojoFailureException: Error(s) found in bundle configuration
	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:296)
	... 20 more

- SF

Ok. Receiver module approach it is then. I already have that running, now need to plug in persistence on it -- was trying to avoid that.

Great. I have direction now. Thanks!

I've got my strategies running and producing Suggestions and I essentially want to persist those the simplest way possible but using an intelligent persistence layer. While looking through the code today, I'd have been happy with a solution of either using the Metc persistence layer or the similar one of my own app by interfacing via the ORS Client API. Seeing that the latter's not possible, what's the best approach?

You mention plumbing to a CEP Module or Photon. We've already touched on Photon in that it uses the ModuleManager. Perhaps I can look at a CEP Module as an example of some other independent actor in the system that can listen on them? I have built a receiver module that can filter for the Suggestion type. If that's a good approach, can I tap into the Metc persistence layer from there?

Thanks again.

I'm managing suggestions more than order executions. Would love if could have used org.marketcetera.client.Client api to listen on this data. Or, if ExecutionReport passed the originating OrderSingle as one of its parameters, I could wrap that obj with some additional context and use that in my Client implementation. Since it doesn't look like those are options...

What's the simplest way to listen for Suggestions from outside of ORS?

I see a pattern of employing the ModuleManager+SinkDataListener in various test classes as well as in photon. If this is the answer, just need a bit of info to get me started... what's needed to get the ModuleManager running?

Thanks.

Looking forward to info here as well. Thanks.

I'm a Java guy that has played with esper for a month or so. I've found it to be a clearly powerful tool for modeling exactly those things you do already with Java. Recommend giving it a go.

I'm surprised that that's what the issue was, just the cast. I started playing with your eql last night but almost fell asleep on my keyboard and planned to continue with it tonight.

Yes, good advice is to break it down to more simple pieces. That's what I did while debugging mine.

Were you able to find any EQL message boards anywhere? Seems to me that there is a void that needs to be filled there. More than just you and I are playing with this technology independently and a dedicated forum would be useful.

I'll email you tonight. Thanks for the follow-up.

RealTimeMovingAverages java strategy attached.

(edit) Updated the class to pull out some proprietary references. Should work now out of the box.

For what it's worth, I've gotten beyond the issues mentioned here. Esper queries weren't correct. An example real-time 2-4-8 MovingAverages java strategy available here:
http://www.marketcetera.org/community/posts/list/183.page

Footer Links