Win a copy of Head First Go this week in the Go forum!

frege fregenal

Greenhorn
+ Follow
since Feb 04, 2019
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by frege fregenal

Solved: didn't change all tags with IDO-8859-1 to UTF-8. After triple check, it works fine.
4 days ago
Hello all,

I'm having a problem, probably with charsets or spring, and maybe some of you can help me. The page is developed using spring boot for Internet Explorer 8 (yes, I know).

I have a form and a textarea inside it, and when I process the form, the text is missing any accented vowel or special character (like ñ) and replacing it all with the same char, "?". I really don't know why is this, if it's the page charset, the browser or spring. The html code is the following:



And the way the controller process it:



In this code I'm already trying corrections, the final goal is that inside msg.text or mes is a String with all the special characters. If the text is "áèîö eñe []{}" the output is



As you can see the problem is not only the missing special chars, but also that they are translated into the same symbol, so I can't correct this using String.replaceAll (you can see in the code that I actually did this when I thought it only was the "ñ" char, but in the end accented vowels are too being replaced). Apart from this, I tried changing the meta tag from "iso-8859-1" to "UTF-8" but no results so far.

Any advice?

EDIT: I tried it on Chrome and same fail, so most certainly it isn't the browser (go figure, the problem is not IE8)
6 days ago
Hi all, I come from this question:

https://coderanch.com/t/705832/java/servlets-capabilities-language-recomendation

Well continuing with this job, I found some more doubts along the path. This time, their server will offer webservices to me, which I have to invoke via SOAP. They gave me a SoapUI project to test the webservice, I tested it and generated an wsdl from the project, which I used to generate java classes but in the end I couldn't make it work on java (in souapUI it worked). I'm using Spring boot and Jaxb. The webservice uses 2 certificates SoapUI asks for, but java project doesn't, and this is where my firs question comes from:

  • It's usually enough with the WSDL generated from the SoapUI project or should I ask them to give me a "full WSDL"? It's my first time working with SOAP outside college and I don't want to sound too stupid too soon.


  • If the answer to this is a solid YES, then probably the rest of this post is useless, but just in case I will continue:

    The second part is about what if I don't have a full functioning WSDL but they gave me written specifications. I would like to know some good open library I could use and some good tutorial about it, but not just SOAP in general, but some more specific tutorial because they ask for several requisites:

    WSDL 1.1/1.2; SOAP 1.1/1.2; WS-SECURITY 1.1 to sign SOAP messages; creator must include "Created" timestamp inside WS-Security Timestamp; the SOAP body must by digitally sign by the creator, and also the creator has to calculate the digital sing for each element; clients must include certificate in request using the "Direct Reference" mechanism from WS-Security 1.1; digital signing using X.509 certificates with id "Binary Security Token"; service should implement X.509 Token Profile 1.1; service will use PKI as security credentials; all comunications will be cyphered using SSL protocol.

    (I haven't written these as a list because the message would be too big, but if you think it's better as a list tell me and I will change it)

    The thing is, all this requisites are automatically fullfilled in SoapUI (except for the location of the two certificates), but in my java project I'm missing some stuff, and that's another reason for my first question. Can you help me solve some of this doubts?

    Thanks in advance,
    Frege.


    3 weeks ago
    Instead of "stringent digital privacy laws" you should say "LOPD" but, besides that, you are right on the spot!
    1 month ago

    Tim Holloway wrote:Yes, it's an ironic truth that doctors are infamous for being technological laggards, but on the other hand, the US medical industry is tightly regulated - AND full of lawsuit-happy people, so using a technology that Microsoft doesn't support is opening up a major set of liabilities. And that's even before HIPAA gets involved. If a major leak of medical records gets tracked back to an un-repaired IE8 exploit, it would have major repercussions. Being a little out of date is somewhat forgiveable. Being so far out of date that you can't even get brought up to date borders on malfeasance. And many other countries are going to have similar considerations, if fewer lawyers.

    I think the principals here need to do some major soul-searching before they promote a solution like this for new development.

    JSF is, in fact, a very good platform for anything that is based on a lot of data entry. The JSF framework validates data automatically, and will actually refuse to act until every last item on a submitted form is valid. When a JSF action fires, your Model has already been updated with the data from the form and you know that that data is complete and valid. Note that for the most part "valid" here primarily means syntax and range. More complex constraints may still need to be checked by the action code, but in any event, if data is rejected, the form is re-displayed and error messages can be automatically placed either in a fixed area of the page or next to the offending form controls.

    There is a bit of a learning curve, since most Java web programmers are used to a procedural approach, and JSF operates on Inversion of Control. Meaning that instead of having the app go out and get data, the JSF framework obtains the data from the form, validates it, and if it's valid, JSF itself injects the data into the Model (backing) bean properties. Likewise, changing the bean causes the next form display to update with the new bean properties.

    The downside to using JSF, however, is that probably none of the the extensions such as RichFaces, IceFaces, PrimeFaces, and so forth will work properly with IE8. And in Red Hat (soon to be IBM) RichFaces, they have actually formally declared that they never will. In fact, I'm not even sure if JSF version 2 supports IE8, since the differences between IE8's JavaScript and industry-standard JavaScript is the primary reason why it was singled out as a cutoff point. And JSF version 2 uses AJAX, which means JavaScript.



    Yes, it's a pain in the ass, but it's the government who hire us and all healthcare is public here, so it's almost impossible that we have problems with lawsuits if we don't screw up badly. What my boss did was delegate security on the ones who had been already storing the medical info (the main ISP here). So they have a DB which can only be accessed (until now) from the VPN the doctors use (the big red button I told earlier). But now we (my page) will have to access the DB from a third party machine, and I don't really know how they want to manage.

    But I agree with you that they need to do some major soul-searching. Most people suggesting the features of the system need help to access their own email so... that's something...
    1 month ago

    Tim Holloway wrote:Be warned that IE 8 isn't just past End-of-Life, even the Walking Dead won't touch it. Absolutely FORGET about Microsoft giving you assistance unless you come to them with large quantities of money in your hands.

    On top of that, IE 8 has some serious compatability issues with the rest of the world. Not IE6-level, but enough that the Red Hat JBoss Version 3 framework (which is also long past its end of support) won't work right with it.

    In short, you are being commanded to construct a monster which is very likely to come back and blow holes in corporate security and fail in unpredictables ways at unpredictable times. And no one is going to feel sorry for you. Unless you pay them. And when you're that far behind, there are things that broke other things, that in turn broke other things. As I've said before, software doesn't "wear out", but it does rot from the outside (hardware, OS) in.

    OK, now you've been warned. Regardless, servlets and JSPs are fully capable of doing major work. In fact, my understanding that that's exactly what Amazon.com was originally written in.

    And despite the fact that JavaServer Faces doesn't get much love, it's my first option for form-based data entry apps, because it aids so much in the validation of the input data. And loved or not, it's part of the JEE standard, so vendor support is very good - which is more than I can say about IE8.

    I'm not sure I agree with Tim Moore's asserting that apps are using client side rendering. Even when I use NodeJS, the page templates are on the server. But conversely, a lot of client GUI functions are JavaScript, especially the AJAX stuff, and that's true even with JSF. Many third-party JSF tagsets include a copy of jQuery internally.

    JSF isn't the only Java server-side technology, and I'll admit I'm biased towards it. I manage the JSF forum here on the Ranch. But the icing on the cake is that it's a non-exclusive technology, so if it doesn't need a particular set of needs, I can blend in other non-JSF features into a JSF webapp.



    I know you are right, but the IE8 thing with as little client side rendering as possible is an obligation. This will be used mostly by medical doctors and pharmacists, and doctors WILL use old pcs with a red button wich will open IE8 and stablish a VPN connection with the DB. And my page must work fine on those pcs. This is because healthcare is public so the databases are shared, and because of that they force doctors to use specific machines with specific software installed so they have "absolute control" over sent and received data.

    Believe me when I say I'm the first one whose jaw dropped when I was told about the IE8 thing. I wouldn't be surprised a little bit if they tell me that these pcs have windows xp or 98 installed hahaha.

    On the other hand: do you think I will get some noticeable advantages from switching to JSF? Currently I'm switching from JSP to servlets+springBoot, so any extra-time learning JSF should be justifiable.
    1 month ago
    Thanks for the advice, I will check what is spring about and watch a tutorial on SpringBoot.
    1 month ago
    I am doing a webpage for work in JSP and they asked me for new features, so I'm learning about servlets because the logic is getting too big. What I don't want is to be doing this for a couple of weeks to only then realize servlets aren't good enough for what I want to do, so I need some advice.

    Initially, the page is used to enter medical measurements (i.e. weight, bpm...) and also it works as a mail server, but now I have to implement some kind of notifications: another server will sent alert messages and I have to redirect (or show some sort of notification) to all sessions active at that moment. Are servlets and JSP capable of this? Do you recommend I use another language for that? Also, I've been coding from scratch, without any frameworks, do you recommend some framework for me, too?

    I also should mention that the webpage MUST run on IE8, so the less javascript and modern functions the better.

    Thanks in advance,
    Frege.
    1 month ago