Re: The wonderfull worlds of encodings...

UTF Unicode Transfer Fromat can be many different lengths. UTF-8 uses 8 bit bytes to encode ISO-10646 code points. When the code point value is less than 65,768 (i.e. UNICODE) then UTF-8 will use up to 3 bytes (24 bits) to encode the code point. However, when the code point value is from the

Re: [tomcat 4] RequestUtil.parseParameters() method

I remember this code. It is correct given previous development history. The bytes in the input data string are NOT encoded. The look back earlier to where the original byte array from the browser is converted to a string. You will notice that no encoding is applied to the bytes as they are

Re: Multi-Byte character support.

I have helped work on a fix for this on 4.0 (which supports the javax.servlet.ServletRequest.setCharacterEncoding() method). Tomcat 3.x does not support the new servlet 2.3 methods, so I did not look at fixing it in Tomcat. However, I have an easy to use object (included) which is able to

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory EjbFactory.java

I am happy with this version of EjbFactory. Thanks, Tim Tye [EMAIL PROTECTED] writes: remm01/03/20 15:17:37 Modified:catalina/src/share/org/apache/naming/factory EjbFactory.java Log: - Comment out the type checking, as suggested by Tim Tye. Revision Changes

Re: Strange problem with URL_PKG_PREFIXES

Remy Maucherat writes: I've updated the object factory for the EJB references. It should now attempt to resolve ejb-links using a JNDI lookup. I can't really test the feature, so I'm waiting for your feedback and stack traces, if it goes wrong ;-) Remy Ok, I will test with the

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory EjbFactory.java

This code does not work because the classloader is different than the servlet class loader. The "Class home = Class.forName(homeClassName);" line fails with "Class.forName() failed: java.lang.ClassNotFoundException: cool.models.coop07.java.S_STRESS_31KpsHome". This same line works in the

Re: Strange problem with URL_PKG_PREFIXES

Remy Maucherat writes: Quoting [EMAIL PROTECTED]: Remy Maucherat writes: I've updated the object factory for the EJB references. It should now attempt to resolve ejb-links using a JNDI lookup. I can't really test the feature, so I'm waiting for your feedback and stack

Re: Strange problem with URL_PKG_PREFIXES

Remy Maucherat writes: Quoting [EMAIL PROTECTED]: I am trying to make the ejb-link use jnp://ttt1:1099/EJBresource work. So it doesn't work either the other way around ? No: ... When I call 'lc = (Context)ctx.lookup("jnp://ttt1.ca.com:1099");' in any form, I get

Re: Strange problem with URL_PKG_PREFIXES

Remy Maucherat writes: Remy Maucherat writes: Quoting [EMAIL PROTECTED]: I am trying to make the ejb-link use jnp://ttt1:1099/EJBresource work. So it doesn't work either the other way around ? No: ... When I call 'lc = (Context)ctx.lookup("jnp://ttt1.ca.com:1099");' in

Re: Strange problem with URL_PKG_PREFIXES

I've got some of the lookup working now, but ejb-link still fails: WORKS-- lc = (Context)ctx.lookup("jnp://ttt1.ca.com:1099"); WORKS-- ho = (EJBHome)ctx.lookup("jnp://ttt1.ca.com:1099/S_STRESS_31Kps"); FAILS--- ho = (EJBHome)ctx.lookup("java:/comp/ejb/S_STRESS_31K"); Web.xml entry:

Re: Strange problem with URL_PKG_PREFIXES

Thanks, I look forward to the final patch. I placed jnp-client.jar in jdk1.3/jdk/lib/ext and removed a hand build jar (containing only jnpURLContextFactory) in jakarta-tomcat-4.0/common/lib. Finally, setting "java.naming.factory.url.pkgs = org.apache.naming:org.jnp.interfaces". Tim Remy

Re: Strange problem with URL_PKG_PREFIXES

Remy, Thanks for helping me look into this problem. I believe that short term, prepending the apache pkg prefix is a simple way to make results consistent. I thought that some of my problem might be from having out of date 'org.jnp.interface' library. I have looked all morning, and cannot

Re: ejb-ref/EjbRef/EjbFactory implementation

I am very interested in this implementation. I have been trying to use the tomcat context to get a reference to an EJB in another machine (running Jboss). In my investigation, the ejb-link is the most important field in ejb-ref when there are multiple machines because it defines the full URL

Strange problem with URL_PKG_PREFIXES

The Context.URL_PKG_PREFIXES environment variable is a colon-seperated list of package prefixes. However, when I set this environment variable to "org.jnp.interfaces:org.apache.naming" and attempt to get a Context; Context ctx = new InitialContext().lookup("java:/comp"); The lookup fails

ejb-ref ejb-link Implementation in 4.0.b1

I am trying to obtain a remote reference to an EJB in another machine. I have set the ejb-ref in web.xml as follows: ejb-ref descriptionSample bean generated by coolgen placed here for ease of early testing/description ejb-ref-nameejb/S_STRESS_32K/ejb-ref-name

Re: ejb-ref ejb-link Implementation in 4.0.b1

Weining Qi writes: if you are running tomcat 3.x in the same window (tomcat run), look at the feedback from tomcat when call the ejb that way, you can see that tomcat does not recognize the namespace "java:com/env/" for calling ejb as The name is "java:comp/ejb" NOT --.