You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NB: If you want to use the resulting JARs in an OSGi environment you'll have to omit the `-PskipBundlePlugin` option.
60
58
59
+
## importing the project into the IDE
60
+
61
+
When the project is first created, it will not have the generated message classes and compile errors will occur! Best is to compile once on the command line before importing the project into the IDE.
62
+
63
+
If the IDE reports some errors after the compilation with `mvnw clean package`, try to use `mvnw clean install`, like:
QuickFIX/J includes some example applications in the `quickfixj-examples` module. Moreover, here are some links to example applications:
76
+
77
+
Examples by Geoffrey Gershaw: https://github.com/ggershaw/Examples
78
+
79
+
Examples from QuickFIX/J Spring Boot Starter: https://github.com/esanchezros/quickfixj-spring-boot-starter-examples
80
+
81
+
If you would like to be added to this list, please open a PR with the changes.
82
+
83
+
66
84
### Creating a QuickFIX/J application
67
85
68
86
Implement the `quickfix.Application` interface.
@@ -77,7 +95,7 @@ Here are explanations of what these functions provide for you.
77
95
78
96
`onLogout` notifies you when an FIX session is no longer online. This could happen during a normal logout exchange or because of a forced termination or a loss of network connection.
79
97
80
-
`toAdmin` provides you with a peek at the administrative messages that are being sent from your FIX engine to the counter party. This is normally not useful for an application however it is provided for any logging you may wish to do. Notice that the `quickfix.Message` is mutable. This allows you to add fields before an adminstrative message before it is sent out.
98
+
`toAdmin` provides you with a peek at the administrative messages that are being sent from your FIX engine to the counter party. This is normally not useful for an application however it is provided for any logging you may wish to do. Notice that the `quickfix.Message` is mutable. This allows you to add fields to an administrative message before it is sent out.
81
99
82
100
`toApp` is a callback for application messages that are being sent to a counterparty. If you throw a `DoNotSend` exception in this method, the application will not send the message. This is mostly useful if the application has been asked to resend a message such as an order that is no longer relevant for the current market. Messages that are being resent are marked with the `PossDupFlag` in the header set to true; If a `DoNotSend` exception is thrown and the flag is set to true, a sequence reset will be sent in place of the message. If it is set to false, the message will simply not be sent. Notice that the `quickfix.Message` is mutable. This allows you to add fields to an application message before it is sent out.
This project builds artefacts for the standard published FIX specification versions from FIX 4.0 to FIX Latest.
290
+
291
+
*```quickfixj-messages-fix40```
292
+
*```quickfixj-messages-fix41```
293
+
*```quickfixj-messages-fix42```
294
+
*```quickfixj-messages-fix43```
295
+
*```quickfixj-messages-fix44```
296
+
*```quickfixj-messages-fix50```
297
+
*```quickfixj-messages-fix50sp1```
298
+
*```quickfixj-messages-fix50sp2```
299
+
*```quickfixj-messages-fixlatest```
300
+
*```quickfixj-messages-fixt11```
301
+
*```quickfixj-messages-all``` - includes all of the above
302
+
303
+
These artefacts are <u>**test**</u> dependencies of ```quickfixj-core```. They are **not** specified as _runtime_ dependencies, this makes it easier to customise QuickFIX/J deployments.
304
+
305
+
If you have no need to customise a FIX integration then you can use the ```org.quickfixj``` artefacts built by this project. Simply include them as dependencies of your application.
306
+
307
+
Artefacts for unused FIX specification versions can be omitted from your runtime.
308
+
Many integrations will not require ```quickfixj-messages-all``` and need only depend on artefacts for a subset of the FIX standard versions. Please note that FIX Protocol versions 5.0 and later depend on ```quickfixj-messages-fixt11``` which provides the implementation for the FIXT1.1 transport messages.
309
+
310
+
Many integrations require specialisation of the FIX Messages, Components and/or Fields. This is accomplished by building and using custom artefacts. Please see [Customising QuickFIX/J](./customising-quickfixj.md) for more detail.
311
+
312
+
### Application Dependencies for QuickFIX/J Messages Build
0 commit comments