You can download it from here…

There are a host of enhancements and bug fixes. Checkout the change log for more details.

The most important enhancements are:

• Support for ACORD Messaging Service standard v1.5
• Support a database message file repository
• Test page in the control panel to send messages

Read More …

Back again with more bug fixes and enhancments.

1. Fix to use proper SAAJ for saving SOAPPart to file (rather than AXIS 1.4 specific SOAPPart.write()).
2. Added logging to org.parlinkie.msgsvr.connector.acord.AcordConnectorService when log4J for this class is set to debug or trace.
3. Move build information files to be located in the classes directory to help with config externalisation.
4. Add support for ACORD Endpoint in outgoing messages.
5. Optional externalisation of the config file. The system property “parlinkie.parlinkie-config-file.path” can be set to the full path. The system property “parlinkie.parlinkie-config-file.name” can be set to the name of the bundle to look for in the class path; i.e if the file is “abc.properties”, “abc” should be specified. The default behaviour is to look for the file “parlinkie.properties” in the class path.
6. Optional externalisation of the hibernate file. The system property “parlinkie.hibernate-config-file.path” can be set to the full path. The system property “parlinkie.hibernate-config-file.name” can be set to the name of the file to look for in the class path; i.e if the file is “abc-hibernate.cfg.xml”, “abc-hibernate.cfg.xml” should be specified. The default behaviour is to look for the file “parlinkie-msgsvr-hibernate.cfg.xml” in the class path.
7. Default namespace for ACORD Outbox, Call and Ping was incorrectly specified as the Inbox.
8. Config servlet can now generate SQL scripts to create/update database.
9. Fixed issue with control panel showing only 1 attachment if 2 or more attachments in a message have the same timestamp.

Download …

Read More …

We’ve rolled up the internal releases 1.0.2 and 1.0.3 into a single public 1.0.4 release. Changes are as follows:

1. Config servlet. Fixed typo “System Properties”.
2. When adding partnership, need to refresh config settings so that don’t get bug where the config settings for the previously viewed partnership is displayed.
3. AcordConnectorService - Call response message envelope had incorrect values because it was constructed with values from the request message rather than the intended response message. Values affected were EndPoint, ApplicationType, ApplicationSchmeaVersion, MessageType, MessageId and MessageRef.
4. AcordConnectorService - Call response message envelope had incorrect values because it was constructed with values from the request message rather than the intended response message. Values affected were EndPoint, ApplicationType, ApplicationSchmeaVersion, MessageType, MessageId and MessageRef.
5. Fixed typos in core.properties
6. Added length attribute to text data type in EventLog.hbm.xml, AuditTrail.hbm.xml and Partnership.hbm.xml in order to support DB2 database.

Enjoy. Hope you find it useful.

Vibul.

This is a very minor release. We’ve added configuration settings to support DB2 database and upgraded our Hibernate and MyFaces libraries.

If you have any questions, please refer to the FAQ or contact us.

Enjoy. Hope you find it useful.

Vibul.

Does it mean anything or is it an acronym?

Well, we combined the terms Partner and Link to get ParLink. After all, we want to specialize in eBusiness and help link business partners together.

However, ParLink just did not sound right to us.

It is part of the Australian culture to end as many words as possible with an ‘o’ or an ‘e’. For example, David becomes Davo and Sunglasses becomes Sunnies.

So we went with Parlinkie and it stuck.

What can I do with it?

Here’s what it looks like.

If you have any questions, please contact us.

Enjoy. Hope you find it useful.

Vibul.