|
From: Patrick Y. <kc...@ce...> - 2003-07-15 10:11:03
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> 1.3 support is solely for compatibility to Weblogic and Websphere. I am not sure about the JDK support of the latest versions of the above servers, anybody got some idea? -Patrick<br> <br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>RE: [ebxmlms-develop] LDAPToURLresolverImpl.java</title> <p><font size="2">Another option is to drop 1.3 support.</font> </p> <p><font size="2">One anomaly is including servlet.jar in the distribution. I have to keep remembering to delete it. Given that it's a fairly safe assumption that we already have a servlet.jar (or equivalent), does it need to be in the distribution?</font></p> <p><font size="2">PJDM</font> <br> <font size="2">--</font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <p><font size="2">-----Original Message-----</font> <br> <font size="2">From: Patrick Yee [<a href="mailto:kc...@ce...">mailto:kc...@ce...</a>] </font><br> <font size="2">Sent: Tuesday, 15 July 2003 2:09 PM</font> <br> <font size="2">To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">Subject: Re: [ebxmlms-develop] LDAPToURLresolverImpl.java</font> </p> <br> <p><font size="2">Agreed with Peter. I think this case is similar to JSSE. Although those classes can be found in JDK1.4, we include jsse.jar in lib directory to make Hermes to be compiled under JDK 1.3.</font></p> <p><font size="2">So another option now is to include the JNDI class library (downloadable from java.sun.com) to lib directory and make the LDAPToURLresolverImpl.java to hk.hku.cecid.phoenix.message.handler package.</font></p> <p><font size="2">Regards, -Patrick</font> </p> <br> <br> <br> <p><font size="2">Ronald van Kuijk wrote:</font> </p> <p><font size="2">JNDI is part of the 1.4 JDK. It's not standard for 1.3, although several servlet engines (Tomcat, Jetty) have versions that also contain the jndi libraries, so you could use 1.3 with those versions as wel</font></p> <p><font size="2">Ronald</font> <br> <font size="2">-----Oorspronkelijk bericht-----</font> <br> <font size="2">Van: Mayne, Peter [<a href="mailto:Pet...@ap...">mailto:Pet...@ap...</a>]</font> <br> <font size="2">Verzonden: maandag 14 juli 2003 2:12</font> <br> <font size="2">Aan: '<a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a>'</font> <br> <font size="2">Onderwerp: RE: [ebxmlms-develop] LDAPToURLresolverImpl.java</font> </p> <br> <p><font size="2">Is JNDI part of standard Java? Could I compile it without an LDAP implementation? </font> <br> <font size="2">If not, it would probably be better as a contrib package? </font> <br> <font size="2">PJDM </font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne </font> <br> <font size="2">Technology Consultant </font> <br> <font size="2">Spherion Technology Solutions </font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 </font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777 </font> <br> <font size="2">> -----Original Message----- </font> <br> <font size="2">> From: Ronald van Kuijk [<a href="mailto:rv...@ab...">mailto:rv...@ab...</a>] </font> <br> <font size="2">> Sent: Monday, 14 July 2003 6:30 AM </font> <br> <font size="2">> To: ebxmlms </font> <br> <font size="2">> Subject: [ebxmlms-develop] LDAPToURLresolverImpl.java </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> Hi all, </font> <br> <font size="2">> </font> <br> <font size="2">> Im writing a LDAPToURLresolverImpl class that can get the URL </font> <br> <font size="2">> to send a </font> <br> <font size="2">> message to from an ldap server. Should I put this class in the </font> <br> <font size="2">> hk.hku.cecid.phoenix.message.handler package or is it more </font> <br> <font size="2">> something for </font> <br> <font size="2">> in the transport package? Or should it even be in my own package </font> <br> <font size="2">> (net.vankuijk.message.handler/transport) and put it in a </font> <br> <font size="2">> contrib part of </font> <br> <font size="2">> Hermes? </font> <br> <font size="2">> </font> <br> <font size="2">> Ronald </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> ------------------------------------------------------- </font> <br> <font size="2">> This SF.Net email sponsored by: Parasoft </font> <br> <font size="2">> Error proof Web apps, automate testing & more. </font> <br> <font size="2">> Download & eval WebKing and get a free book. </font> <br> <font size="2">> <a class="moz-txt-link-abbreviated" href="http://www.parasoft.com/bulletproofapps1">www.parasoft.com/bulletproofapps1</a> </font> <br> <font size="2">> _______________________________________________ </font> <br> <font size="2">> ebxmlms-develop mailing list </font> <br> <font size="2">> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> </font> <br> <font size="2">> <a href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a> </font> <br> <font size="2">> </font> <br> <font size="2">The information contained in this email and any attachments to it:</font> </p> <p><font size="2">(a) may be confidential and if you are not the intended recipient, any interference with, </font> <br> <font size="2">use, disclosure or copying of this material is unauthorised and prohibited; and</font> </p> <p><font size="2">(b) may contain personal information of the recipient and/or the sender as defined </font> <br> <font size="2">under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to </font> <br> <font size="2">collect, hold and use such information and any personal information contained in a </font> <br> <font size="2">response to this email, for any reasonable purpose in the ordinary course of </font> <br> <font size="2">Spherion's </font> <br> <font size="2">business, including forwarding this email internally or disclosing it to a third party. All </font> <br> <font size="2">personal information collected by Spherion will be handled in accordance with </font> <br> <font size="2">Spherion's Privacy Policy. If you have received this email in error, please notify the </font> <br> <font size="2">sender and delete it.</font> </p> <p><font size="2">(c) you agree not to employ or arrange employment for any candidate(s) supplied in </font> <br> <font size="2">this email and any attachments without first entering into a contractual agreement with </font> <br> <font size="2">Spherion. You further agree not to divulge any information contained in this document </font> <br> <font size="2">to any person(s) or entities without the express permission of Spherion.</font> </p> <br> <p><font size="2"> </font> <br> <font size="2">------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. <a class="moz-txt-link-abbreviated" href="http://www.parasoft.com/bulletproofapps1">www.parasoft.com/bulletproofapps1</a> _______________________________________________ ebxmlms-develop mailing list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop" target="_blank">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></font></p> </blockquote> </body> </html> |