This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | I18N - entity class from dbase wont deploy if table or col name has mbyte | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Ken Frank <kfrank> |
| Component: | Persistence | Assignee: | Andrei Badea <abadea> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | pjiricka, prehak, sunlit |
| Priority: | P2 | Keywords: | I18N, RELNOTE |
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
exception
image exception bin browser zip of project SJSAS exception during deployment image oracle derby derby |
||
|
Description
Ken Frank
2006-06-19 21:20:06 UTC
Created attachment 31175 [details]
exception
Created attachment 31176 [details]
image
Ken, is the query in orambfromdb.gif written by you or generated by one of the wizards? I've checked with our glassfish query expert and he said: "The WHERE clause of this query looks like that it uses single quotes for the field access and the named input parameter which is not allowed." I'm trying to determine if this is user error or generated by NB. Adding a discussion I had with Ken on this:
Rochelle Raccah wrote:
> But the error message at deployment is due to quotes in the query, so we
> *do* need to figure them out =)!
>
> Ken Frank wrote:
>
>> lets ignore the quotes here - that is not part of this
>> - just taking what nb does - when
>> en used in col name (or table), no error msg seen on deploy; when
>> mbyte is used; the error msg is seen
>>
>> Rochelle Raccah wrote:
>>
>>> What do you mean "the problem happens when mbyte used and not when en
>>> used."? Did you have the quotes there for both?
>>>
>>> Ken Frank wrote:
>>>
>>>> cant get to iz now - you know, it could be that the quotes thing is
>>>> something
>>>> i added, trying to workaround it, thinking that mbyte needed quotes -
>>>> so i need to do it again to make sure; but in any case the problem
>>>> happens when mbyte used and not when en used.
Ken, any more information on this? How did the quotes get there? Were they generated by NetBeans? Please note this issue is marked as incomplete. I don't see any more error messages about queries when building or running the project, just the exception in the new (third) attachment, that is shown in browser. To clarify: - this issue is about column with mbyte only; issue about table with mbyte in 78286 - for scenario of new entity class with mbyte as a col name (ie variable in the java code) - and then jsf pages from ent class (where the ent class name/table name is en( -- that works ok - in browser I can add or edit columns to the table - The bug about the jsp files generated from jsf pages from entity class still exists and workaround needs to be done first - changing the bad mbyte in the col name (or table name for other scenarios) to the correct mbyte -- this is some kind of encoding read/write kind of issue on creation of these jsp files. ken.frank@sun.com Created attachment 31939 [details]
exception bin browser
The last exception doesn't seem related to I18N. Could you please zip and attach your project to the issue? Thanks. Created attachment 31965 [details]
zip of project
zip of the project is attached. ken.frank@sun.com Created attachment 32983 [details]
SJSAS exception during deployment
The attached exception is thrown when deploying the project attached by Ken to SJSAS PE 9.0 FCS. It seems the Chinese characters in the input parameter are not supported. The BNF grammar for JPQL in the JPA spec doesn't contain a production for the input_parameter nonterminal (!), so I can't tell if the characters should be supported or not. But I don't see why they shouldn't be, thus this looks like a bug in TopLink. This issues will probably be waived for 5.5. Note for anyone trying to reproduce: the Java files in the attached project are encoded in Shift-JIS. Best to start NetBeans with $ netbeans -J-Dfile.encoding=shift-jis Filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=937 against GlassFish. Yes, Japanese characters were used and it was run in ja locale. Am adding relnote keywd; what are the other bugs you or team has filed on gf based on some of these recently filed i18n bugs ? I'd like to add that keywd to those also. GlassFish issue 937 was fixed in 9.0 UR1. Can we close this issue? This works just fine for me atm, what about you Ken, satisfied too? not working for me - get some error msgs in browser; I'll let Pavel know separately. Do the enterprise3/modules/ext/toplink/* files need to be the same as the ones in gf u1 ? they are not; the ones in current nb still has size of as before -- or are the ones in gf used only ? ken.frank@sun.com Stepan agreed to test the GF fix. Ken, please post any error message to the issue. Do you get the exception in desc12, or something else? If the latter then please file a separate issue. attached are some browser error pages from using with oracle and derby, with mbyte column names as per scenario of this issue. Pavel, please provide more details of your steps and observations on windows; I am on solaris. ken.frank@sun.com Created attachment 33888 [details]
image
That is another exception than the one in desc12, which is what is being solved in this issue. Please file a separate issue for it and attach the full exception from the server logs, not an image. I also don't see anything related to Derby in the attached image. Created attachment 33890 [details]
oracle
Created attachment 33891 [details]
derby
Created attachment 33892 [details]
derby
The exceptions in orambcolent.gif, orambcolfroment.gif and derbymbcolfroment.gif are not related to this isssue. Please file two new issues: one for orambcolent.gif and one for the other two images. The exception in derbymbcolfromentdb.gif, however, seems to be the one that we are dealing with in this issue. It is weird, because I can't reproduce it with GF 9.0 UR1 Build 10. Which version did you use? Could you please reproduce the exception again and attach the server log? Thanks. Taking back. I belive this was fixed, so marking as such. Please reopen if you can still reproduce in a build of GF v1 UR1 newer than September 7. Product Version: NetBeans IDE Dev (Build 20080721233246) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 System: Windows XP version 5.1 running on x86; MS932; ja_JP (nb) I used a table with mbyte in its column and WebApp with JSF framework. Win-31j project encoding: Entity class was generated ok. Deployment of the app was ok. jsf pages from ent class were generated ok. Files have win-31j encoding. UTF-8 project encoding: Entity class was generated ok. Deployment of the app was ok. jsf pages from ent class were generated ok. Deployment of the app was also ok. Files have UTF-8 encoding. |