Bug 96927 - charset in servlet code could be seeded with the project encoding
charset in servlet code could be seeded with the project encoding
Status: NEW
Product: javaee
Classification: Unclassified
Component: Servlet
5.x
All All
: P4 (vote)
: 7.1
Assigned To: issues@javaee
issues@javaee
: I18N
Depends on: 118203
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-01 11:23 UTC by Jiri Prox
Modified: 2013-08-22 00:42 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
:


Attachments
full log (55.92 KB, text/plain)
2007-03-01 11:24 UTC, Jiri Prox
Details
sample project (65.00 KB, application/x-compressed)
2007-03-21 15:40 UTC, Jiri Prox
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Prox 2007-03-01 11:23:07 UTC
NB 5.5.1 Beta (200702192300)
JDK 1.6.0
Locales: ja_JP
Sun Java System Application Server 9.1 (build b33)

Session bean with multibyte character in its name cannot be called. It results
in javax.ejb.AccessLocalException: Client not authorized for this invocation.

Steps to reproduce:
1) create enterprise application
2) in ejb module create session bean with multibyte
3) in web module create servlet which uses  session bean from step 2
4) run servlet
-> response status 500, exceptions in log
Comment 1 Jiri Prox 2007-03-01 11:24:10 UTC
Created attachment 39043 [details]
full log
Comment 2 Martin Adamek 2007-03-21 07:44:44 UTC
Please consult with
http://docs.sun.com/source/819-0789/tsg-security.html#wp20452 or attach your
project here.
Comment 3 Jiri Prox 2007-03-21 15:39:26 UTC
Here is the project. Note that some filenames contains japan characters.
Comment 4 Jiri Prox 2007-03-21 15:40:26 UTC
Created attachment 39762 [details]
sample project
Comment 5 Ken Frank 2007-03-29 03:45:53 UTC
removing incomplete keyword since requested info was attached.

ken.frank@sun.com
Comment 6 Jiri Prox 2007-09-17 20:30:16 UTC
Obsolete milestone, please reevaluate
Comment 7 Ken Frank 2007-10-03 17:46:25 UTC
can this be fixed for nb6 ? other parts of nb allow multibyte chars in names of items, or in java file names
or methods, variables, etc.

ken.frank@sun.com
Comment 8 martin_adamek 2007-10-09 10:14:03 UTC
Currently I cannot reproduce because of issue 118203

*** This issue has been marked as a duplicate of 118203 ***
Comment 9 martin_adamek 2007-10-09 10:16:15 UTC
Sorry, of course not duplicate, but blocked by 118203
Comment 10 martin_adamek 2007-11-01 13:40:59 UTC
It looks to me like server/runtime problem. Is there anything wrong in what NetBeans has done? I really have no idea what should I do with this.
Comment 11 Ken Frank 2007-11-01 17:50:59 UTC
Jirka,

does it still reproduce using latest nb or does the 118203 block from
seeing if it does ?

ken.frank@sun.com
Comment 12 Petr Jiricka 2007-11-01 23:51:54 UTC
Are there any real users who have hit this issue?
Comment 13 Ken Frank 2007-11-02 00:49:05 UTC
I don't know about actual users about this issues, but do see in other issues about use of non ascii
here and there, in file/paths and data, and nb overall is good about allowing use of those kind of characters,
so I think fixing this one would be about consistency of all project and file types, especially since various
file types can be used in different project types.

Since the issue was filed, there has been a lot of feq project and file fucntionality; I don't know if that
is related to or helps avoid this issue so maybe we can see if its still a problem in current nb6.

ken.frank@sun.com
Comment 14 Petr Jiricka 2007-11-04 13:20:02 UTC
From what Martin wrote this really sounds like a runtime problem, so we agreed we would not try to fix for 6.0. Removing
the fix-in-60 marker.
Comment 15 Ken Frank 2007-11-10 16:17:22 UTC
since it was seem in nb6, the following comment might still apply even though
its about nb6, since the case is in effect the same:

I don't know if this happens when using utf-8 project properties or
when using another one, like for solaris ja locale, the encoding is
euc-jp so a user might need to change proj encoding prop to that -
but in created servlet the encoding is hardcoded from template as:

      response.setContentType("text/html;charset=UTF-8");
        PrintWriter out = response.getWriter();

I realize the issue is about use of mbyte in name of session bean but the
error referred to servlet.

the higher level question for nb6 is -- should the charset in servlet
code be seeded with the project encoding, and not always utf-8, 
as per the new feq for nb6 ?

ken.frank@sun.com
Comment 16 Ken Frank 2008-01-10 20:12:38 UTC
can this be fixed for 6.1 or for upcoming patch 3 ?

ken.frank@sun.com
Comment 17 martin_adamek 2008-01-11 07:12:35 UTC
I'll try, but probably for 6.1.
Comment 18 _ jyothivasa 2008-11-19 23:26:42 UTC
Not critical for 7.0. Will be addressed in the next release.
Comment 19 Andrey Yamkovoy 2009-11-13 07:48:20 UTC
Not planned for 6.8
Comment 20 Martin Fousek 2011-10-10 12:41:38 UTC
Ok, it seems that the real issue is about default charset encoding for servlet instead of calling multibyte EJB (which finally worked to user after removing his project issue). Changing to proper category.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo