NB 5.5.1 Beta (200702192300)
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
Created attachment 39043 [details]
Please consult with
http://docs.sun.com/source/819-0789/tsg-security.html#wp20452 or attach your
Here is the project. Note that some filenames contains japan characters.
Created attachment 39762 [details]
removing incomplete keyword since requested info was attached.
Obsolete milestone, please reevaluate
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.
Currently I cannot reproduce because of issue 118203
*** This issue has been marked as a duplicate of 118203 ***
Sorry, of course not duplicate, but blocked by 118203
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.
does it still reproduce using latest nb or does the 118203 block from
seeing if it does ?
Are there any real users who have hit this issue?
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.
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.
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:
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 ?
can this be fixed for 6.1 or for upcoming patch 3 ?
I'll try, but probably for 6.1.
Not critical for 7.0. Will be addressed in the next release.
Not planned for 6.8
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.