used trunk build 0529.
In the default en locale on Solaris 10 and WinXP I was able to create WS client and HTTP monitor looks ok there.
1. Create WebApp using mbyte in its name
2. Create Web Service using mbyte in its name
3. Add an Operation using mbyte in its name
4. Deploy the app to GlassFish
5. Create WS Client using this web service
In ja locale Http Monitor shows incorrect mbyte.
Happens for UTF-8 and win-31j project encodings.
Solaris 10, UTF-8 project encoding:
Using both locales: Ja UTF-8 and non UTF-8 Http Monitor shows incorrect mbyte.
Also I see errors in GF log and the client looks not generated.
I'll investigate more and file separate issue on this.
Created attachment 62522 [details]
winxp: ja locale, utf-8 project encoding
Created attachment 62523 [details]
Solaris 10: ja non UTF-8 locale
Created attachment 62524 [details]
Solaris 10: ja UTF-8 locale
As far as I know, the http monitor code does not create any request/response to the resource.The code implements a
javax.servlet.Filter and performs filtering tasks on the request to a resource and on the response from a resource. The
code gets a HttpServletRequest and gets all the params from it, including the RequestURI, and displays the attributes.
What the code sees, it displays. If it sees an incorrect mbyte, thats what it will display..Not sure if bug is in the
servlet container or webservices code.
Can you attach the project that you used for this bug? I created a web project with all the steps given and it doesnt
Once the project is attached, I will transfer the bug to web services team so that they can evaluate if the bug is in
After Step 4, please right-click on the web service created in Step2, and select "Test Web Service" option..
What does the browser show?
I tried to debug a little more - The GET requests that are not being I18n are the ones generated by webservices - the
query string are "xsd=1" and "WSDL"
Transferring the bug to webservices
Created attachment 71310 [details]
After the step 4, Test Web Service results
kaa, if the info you provided is what was asked for, can you
remove the incomplete keyword ?
Hope I answered all questions.
Removing INCOMPLETE keyword.
The query strings are absolutely fine.
I used tcmpon tool to monitor that web service
The picture shows that HTTP monitor mangle somehow the request URI.
The client for that Web service is working fine. May be just the GlassFish Tester web application is not working for
Sending back to http monitor
Is this really P2 bug.
Created attachment 73922 [details]
TCP monitor and HTTP Monitor