accord issueshttps://gitlab.ow2.org/accord/accord/-/issues2010-04-30T01:41:25Zhttps://gitlab.ow2.org/accord/accord/-/issues/41Separation of the OdetteFtpSession contract from the underlying NIO framework...2010-04-30T01:41:25ZRafael MarinsSeparation of the OdetteFtpSession contract from the underlying NIO framework formhttps://gitlab.ow2.org/accord/accord/-/issues/46File Transfer API Release Candidate 12010-07-05T18:40:10ZBruno BorgesFile Transfer API Release Candidate 1Commit changes after first review and release on MavenCommit changes after first review and release on Mavenhttps://gitlab.ow2.org/accord/accord/-/issues/43Support for structured connection info on Profile XML2010-08-11T20:12:58ZBruno BorgesSupport for structured connection info on Profile XMLWire should support the definition of a structured XML Schema-based connection details on a profile node for better decoupled from Apache Camel.
Today it is done this way:
<profile>
<connection>ftp://user:pass@server/</connection>
</p...Wire should support the definition of a structured XML Schema-based connection details on a profile node for better decoupled from Apache Camel.
Today it is done this way:
<profile>
<connection>ftp://user:pass@server/</connection>
</profile>
It should be done this way:
<profile>
<connection>
<ftp:ftp server="server.com" user="user" pass="pass" port="21" />
</connection>
</profile>
https://gitlab.ow2.org/accord/accord/-/issues/44File Transfer API Review 12010-08-11T20:45:09ZBruno BorgesFile Transfer API Review 1Review current trunk of File Transfer API and provide feedback.Review current trunk of File Transfer API and provide feedback.https://gitlab.ow2.org/accord/accord/-/issues/45File Transfer API Review 22010-08-11T20:45:09ZBruno BorgesFile Transfer API Review 2Review recent changes after first review and provide feedback.Review recent changes after first review and provide feedback.https://gitlab.ow2.org/accord/accord/-/issues/38Migrate underlying OFTP API transport framework to Netty2010-08-11T20:46:17ZRafael MarinsMigrate underlying OFTP API transport framework to Nettyoftp-1.2.0.Beta2https://gitlab.ow2.org/accord/accord/-/issues/39Isolate the core OFTP api from the client code2010-08-11T20:46:17ZRafael MarinsIsolate the core OFTP api from the client codehttps://gitlab.ow2.org/accord/accord/-/issues/42Implement state machine in OFTP protocol relay2010-09-10T18:35:44ZRafael MarinsImplement state machine in OFTP protocol relayCheck possibility to avoid control of state in the OdetteFtpSession object.Check possibility to avoid control of state in the OdetteFtpSession object.https://gitlab.ow2.org/accord/accord/-/issues/48Indicate zero length field on unsigned EERPs2010-10-04T15:38:59ZBruno BorgesIndicate zero length field on unsigned EERPsWhen an unsigned EERP is going to be sent, the EERPSIGNL_FIELD should be indicated, with its value set to zero.
Patch attachedWhen an unsigned EERP is going to be sent, the EERPSIGNL_FIELD should be indicated, with its value set to zero.
Patch attachedoftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/49Add missing answer reasons2010-10-06T19:57:05ZBruno BorgesAdd missing answer reasonsAdd missing fields of Answer Rerason, considering RFC 5024 page 55.
Add missing fields of Answer Rerason, considering RFC 5024 page 55.
oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/50Convert unknow code (out of spec) of NERP to 992010-10-06T20:06:44ZBruno BorgesConvert unknow code (out of spec) of NERP to 99Based on Patrick's observation:
[...] when parsing NERP NegativeReason. If the code is unknown (outside of the given list in the RFC), the current code throws an Exception. This patch does not fail but log a warn and set the reason to a...Based on Patrick's observation:
[...] when parsing NERP NegativeReason. If the code is unknown (outside of the given list in the RFC), the current code throws an Exception. This patch does not fail but log a warn and set the reason to an Unspecified Reason (99). I believe that we should not completely fail for such a small error from the remote side. Otherwise we never know that we got a NERP. [...]oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/51Set correct format for NERP fields2010-10-06T20:31:24ZBruno BorgesSet correct format for NERP fieldsIncorrect values for some NERP format (the last 4 were set to numeric while the RFC speaks of Binary)Incorrect values for some NERP format (the last 4 were set to numeric while the RFC speaks of Binary)oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/47Add warn message for invalid field content on CommandExchangeBuffer2010-10-08T13:45:52ZBruno BorgesAdd warn message for invalid field content on CommandExchangeBufferAs Patrick Dessalle from users-list stated:
[...] the code is not enforcing the field formats specification. For instance, I can set the dataset name of a Virtual file with lower case characters and a length longer than 26. [...]
And a...As Patrick Dessalle from users-list stated:
[...] the code is not enforcing the field formats specification. For instance, I can set the dataset name of a Virtual file with lower case characters and a length longer than 26. [...]
And as I reported to him:
[...] Fields contents are partially checked by the library.
Their format is not enforced but the data is stripped and filled with missing characters (it pads with space character or zeros depending on NUMERIC or ALPHA format)
Personally I think this is the best approach. Maybe we can add a log to WARN user of invalid data arriving at the library level.
The class I think we could add that warning is CommandExchangeBuffer, which would automatically proceed to all and every OFTP commands and fields. [...]
This is not considered as a bug, but may require an improvement.
So that's why we are adding a warn message for inconsistent field values.oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/54Refactor OdetteFtpHandlers to eliminate duplicated code to parse datetime2010-10-08T15:39:34ZBruno BorgesRefactor OdetteFtpHandlers to eliminate duplicated code to parse datetimeAll three OdetteFtpVer*Handler have the same method called parseDateTime. But there's also one in ProtocolUtil.All three OdetteFtpVer*Handler have the same method called parseDateTime. But there's also one in ProtocolUtil.oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/53CommandExchangeBufferBuilder incorrectly parses time2010-10-08T16:07:21ZBruno BorgesCommandExchangeBufferBuilder incorrectly parses timeAs stated by Patrick:
"When you receive a message before 10AM, 9:45:00:0000 would be written as 0945000000 in incoming messages. However in CommandExchangeBufferBuilder, line 96, as time is a numeric format, the code does :
text = Integ...As stated by Patrick:
"When you receive a message before 10AM, 9:45:00:0000 would be written as 0945000000 in incoming messages. However in CommandExchangeBufferBuilder, line 96, as time is a numeric format, the code does :
text = Integer.valueOf(text.trim()).toString() which outputs : 945000000 (without the first 0)
Later on, in the parseDateTime() method of OdetteFtpVer20Handler, the string is parsed into hour, minute, second and millis.
But as the string has no 9 characters instead of 10, the code fails."oftp-1.2.0.RC1https://gitlab.ow2.org/accord/accord/-/issues/58Unrestricted JCE policy files needed2010-10-11T18:36:16ZRafael MarinsUnrestricted JCE policy files neededAdd notes on documentation about the requirement for unrestricted JCE policy files install, in order to resolve the "Illegal key size" error.
java.security.InvalidKeyException: Illegal key size
org.bouncycastle.cms.CMSException: key inv...Add notes on documentation about the requirement for unrestricted JCE policy files install, in order to resolve the "Illegal key size" error.
java.security.InvalidKeyException: Illegal key size
org.bouncycastle.cms.CMSException: key invalid in message.https://gitlab.ow2.org/accord/accord/-/issues/64Provide network layer informational access in the OFTP session2011-03-01T14:53:02ZRafael MarinsProvide network layer informational access in the OFTP sessionIn the OFTP session some access to the network layer info is desired (i.e Listening IP of the server, listening port of the server, IP address of the client, If connection was made over TLS/SSL, TLS/SSL client certificate if any,...)
Th...In the OFTP session some access to the network layer info is desired (i.e Listening IP of the server, listening port of the server, IP address of the client, If connection was made over TLS/SSL, TLS/SSL client certificate if any,...)
Those informations can be useful to decide if client match security requirements and accept or refuse the OFTP session (SSL required for partners that don't send encrypted files for example), or doing some throttling (OFTP client connecting/reconnecting too fast, ...)
https://gitlab.ow2.org/accord/accord/-/issues/65Getting "Invalid Record count" and "Invalid byte count" as response when send...2012-06-08T05:03:17ZSyed RizwanGetting "Invalid Record count" and "Invalid byte count" as response when sending to OFTP receiverHi,
I am able to receive the file properly but when sending the file, the receiver responding with error "Invalid Record Count" or "Invalid Byte Count".
We are sending the file in fixed format with record length of 128.
Please suggest m...Hi,
I am able to receive the file properly but when sending the file, the receiver responding with error "Invalid Record Count" or "Invalid Byte Count".
We are sending the file in fixed format with record length of 128.
Please suggest me how to proceed.
Thanks in advance.
Regards,
Rizwanhttps://gitlab.ow2.org/accord/accord/-/issues/66Debt Consolidation Loans @ http://www.seerdebtconsolidationloans.co.uk @ Seer...2014-11-28T18:00:16ZGhost UserDebt Consolidation Loans @ http://www.seerdebtconsolidationloans.co.uk @ Seer Debt Consolidation Loanshttp://www.seerdebtconsolidationloans.co.uk
Given to an individual or family card interest rates often higher than
No credit problems. So you are bent on getting a credit card consolidation
Liabilities are re-thinking; If you do not, ...http://www.seerdebtconsolidationloans.co.uk
Given to an individual or family card interest rates often higher than
No credit problems. So you are bent on getting a credit card consolidation
Liabilities are re-thinking; If you do not, you could end up with more debt!Providing loans offer lower rates of interest and lower monthly
To help families and individuals Division Fan out. One
Debt relief is the best solution to begin is to examine the
Credit Report. Credit reports are stored in the three major credit rating agencies,https://gitlab.ow2.org/accord/accord/-/issues/1Migrate Odette FTP Library API code base to OW2 forge.2018-09-21T20:38:54ZRafael MarinsMigrate Odette FTP Library API code base to OW2 forge.oftp-1.2.0.Beta2