<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/epp-rtk/patches/" rel="alternate"/><link href="https://sourceforge.net/p/epp-rtk/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/epp-rtk/patches/</id><updated>2019-02-28T13:56:24.141000Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>Parsing of host attributes (name servers) from domain info response</title><link href="https://sourceforge.net/p/epp-rtk/patches/4/" rel="alternate"/><published>2019-02-28T13:56:24.141000Z</published><updated>2019-02-28T13:56:24.141000Z</updated><author><name>Olaf Ziems</name><uri>https://sourceforge.net/u/ziems/</uri></author><id>https://sourceforge.net71f5325c6aea0d3894808f19c52bc3737e0e0324</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;we currently are using your SDK in production environment for various registries and registrars. Great work!&lt;/p&gt;
&lt;p&gt;I noticed that it is not able to parse domain:hostAttr tags from domain info responses. For more information see &lt;a href="https://tools.ietf.org/html/rfc5731#section-1.1" rel="nofollow"&gt;https://tools.ietf.org/html/rfc5731#section-1.1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Since we need this feature, I added this capability and created a patch for com.tucows.oxrs.epprtk.rtk.xml.EPPDomainInfo. It would be great if it could be merged into the next release.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Olaf&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Java RTK 0.4.1 pre-release Jar file</title><link href="https://sourceforge.net/p/epp-rtk/patches/3/" rel="alternate"/><published>2001-11-07T21:16:56Z</published><updated>2001-11-07T21:16:56Z</updated><author><name>Daniel Manley</name><uri>https://sourceforge.net/u/tubadanm/</uri></author><id>https://sourceforge.net327cb16b63bb0c3bdd4056d8927816f628e9f022</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;proposed release notes for 0.4.1:&lt;/p&gt;
&lt;p&gt;epp-rtk-java-0.4.1 - Nov 7, 2001&lt;/p&gt;
&lt;p&gt;+ Now using regexp package to strip out whitespace&lt;br /&gt;
in XML from server.  &amp;amp;quot;include-ignorable-whitespace&amp;amp;quot;&lt;br /&gt;
set to false had no effect since Xerces doesn't&lt;br /&gt;
have a DTD for this XML to determine which&lt;br /&gt;
whitespaces are ignorable.&lt;br /&gt;
+ Re-added setRoid() and getRoid() as deprecated&lt;br /&gt;
methods for improved backward compatibility&lt;br /&gt;
with the 0.3.x line of RTKs.&lt;br /&gt;
+ Added Javadocs to some IDL classes (domain check&lt;br /&gt;
mostly).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Java RTK pre-0.3.9 Jar file</title><link href="https://sourceforge.net/p/epp-rtk/patches/2/" rel="alternate"/><published>2001-10-05T23:33:48Z</published><updated>2001-10-05T23:33:48Z</updated><author><name>Daniel Manley</name><uri>https://sourceforge.net/u/tubadanm/</uri></author><id>https://sourceforge.net6634452ba1355a711adb55799112210d788c5af6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is the pre-release of the 0.3.9 Java RTK jar&lt;br /&gt;
file.  It provides the fix to the null status when&lt;br /&gt;
performing a domain info on domains in the live .info&lt;br /&gt;
registry.  The reason for the null was that the&lt;br /&gt;
registry is using an 'active' status which was not&lt;br /&gt;
present in the RTK.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Pre-release of RTK 0.3.8 jar file</title><link href="https://sourceforge.net/p/epp-rtk/patches/1/" rel="alternate"/><published>2001-07-27T15:12:47Z</published><updated>2001-07-27T15:12:47Z</updated><author><name>Daniel Manley</name><uri>https://sourceforge.net/u/tubadanm/</uri></author><id>https://sourceforge.net90de6d572a82f4b3ad772f813f22ab68ec56ca00</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi everyone,&lt;/p&gt;
&lt;p&gt;This is a pre-release of the 0.3.8 RTK jar file.  This&lt;br /&gt;
jar file contains changes to the contact fax and voice&lt;br /&gt;
data members.  Previously the fax data member has been&lt;br /&gt;
a simple String.  An RTK user (J-U Gaspar) has reported&lt;br /&gt;
that the fax must allow an extension value.  This bug&lt;br /&gt;
has been in the RTK since day one.  The IDLs have been&lt;br /&gt;
updated to introduce the epp_ContactPhone struct.  This&lt;br /&gt;
struct is now being used by both the m_fax and m_voice&lt;br /&gt;
data members.&lt;/p&gt;
&lt;p&gt;Included below is my message to RTK users in the&lt;br /&gt;
epp-rtk-devel mailing list.&lt;/p&gt;
&lt;h1 id="dan"&gt;Dan&lt;/h1&gt;
&lt;p&gt;To RTK Users:&lt;br /&gt;
I've committed to CVS release 0.3.8 of the RTK and will&lt;br /&gt;
be releasing a preview of the jar file soon to SF.  If&lt;br /&gt;
reception of this jar file is good, then full 0.3.8&lt;br /&gt;
will be released next week.&lt;/p&gt;
&lt;p&gt;Release 0.3.8 is the first release (I think) that might&lt;br /&gt;
break your code.  If you are accessing the m_fax data&lt;br /&gt;
member directly, then your code will not compile.  The&lt;br /&gt;
m_fax data member, in all classes it appears, is now an&lt;br /&gt;
intance of epp_ContactPhone.  If you are setting the&lt;br /&gt;
fax with the setFax() method, then your code will still&lt;br /&gt;
work but you will not be using the fax extension. &lt;br /&gt;
There is an overloaded setFax() method with an&lt;br /&gt;
epp_ContactPhone parameter to allow you to set the&lt;br /&gt;
extension.  epp_ContactPhone has all the same members&lt;br /&gt;
as epp_ContactVoice.  Now, because of the changes to&lt;br /&gt;
the IDLs, epp_ContactVoice is being deprecated.  As of&lt;br /&gt;
this release it is a subclass of epp_ContactPhone, but&lt;br /&gt;
since m_voice is now an epp_ContactPhone, you can start&lt;br /&gt;
switching immediately.  epp_ContactVoice will be&lt;br /&gt;
officially removed in release 0.4.0 of the Java RTK.&lt;/p&gt;
&lt;p&gt;If there are any question comments or concerns, please&lt;br /&gt;
share them.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;
The Java RTK team&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>