GWTP is an open-source implementation of GWT’s MVP architecture (version 2). It’s a framework on top of the GWT framework. If you don’t use such a framework, and you want to implement MVP, you’ll have to homebrew it. GWTP seems to be the livliest MVP framework at the moment. I decided to save myself the work of homebrewing MVP, and adopted GWTP to implement a webApp. It also implements further framework, such as Security; so the benefits of GWTP over plain GWT should crop up again and again.
Here are steps on building a WAR of the GWTP Basic Maven Archetype.
Following them covers all the prerequisites for a GWTP tutorial like ArcBee’s GWTP Beginner.
Comprehensive smoke testing steps for deploying and custom domain aliasing can be the same as otherwise with that .war file. For example, deploying and aliasing with Openshift like the last GWT Smoke Test post.
It is imperative to use Maven cl instead of GWTP Eclipse plugin. The plugin cannot make a working WAR for some reason!
Here’s some steps on running the GWT Web Application Starter Project (the default that a newly created GWT app comes coded out of the box with) from an OpenShift PAAS hosting account!
Even though this is just running that trivial starter webApp, getting that far is a good smoke test of these useful things to confirm:
- Your basic GWT create -> build -> deploy workflow is working
- All the necessary software dependencies & requirements are in place to make that work
- Your OpenShift account, and specifically the Tomcat 7 gear that is running the webApp, are setup and running properly
- If you choose to Alias a custom domain to your webApp, then that is working
These are high-level steps of implementing this smoke test (detailed steps follow):
- Complete up to the end of the ‘Create’ step of the GWT Tutorials
- This post assumes using Eclipse, but any IDE you can develop GWT on will work
- Build a WAR of the Web Application Start Project made with 1.
- This post assumes using Ant, but any way you create a .war file of the Project will work
- Create your OpenShift account, and create a Tomcat 7 Gear on it
- Deploy the WAR from 2. on the Gear from 3.
- This post assumes interacting with your OpenShift Gear’s Git repo, but OpenShift also supports SCP/SFTP alternatively
- Bonus points: Alias a custom domain you have bought to your deployed webApp
OK, let’s get started…
I just migrated this blog from Arvixe [shared] web hosting, to OpenShift [PAAS] cloud hosting.
- Now my hosting has gone from ~$9/month to FREE!
- I also may have had a future problem solved, by it not being an issue in the first place for OpenShift inherently…
This article has a great overview of the type of migration I just did: It starts by explaining the advantages gained from going from Shared to PAAS hosting, and opinion on why OpenShift is better than other PAAS providers; it also has some good directions on how to do the migration, although I did not need/do all of the steps, and some of the steps were a little bit different in my case: I will get into an overview of my migration steps in a moment…
At some point after initially starting this blog, I couldn’t navigate to the admin pages for ‘Plugins’ [/plugins.php] & ‘Updates’ [/update-core.php], from both my WordPress Network Dashboard & cellepo.com site Dashboard: Clicking on their links arrived at the homepage instead; ughhh!
I’ve eventually found that the problem had something to do with the .htaccess file (in my WordPress root directory): Simply deleting it solved the problem! This WordPress forum post helped me arrive at that solution.
After I published my first post to cellepo.com, along with a category and a few tags for it, I tried testing my WordPress Categories & Tags widget links feature: Those are widgets I have on my right sidebar named with those titles, and their contained links should jump to their respective pages which should contain all posts that apply to them. So clicking on the ‘Sculpture’ Category link should arrive at a page that has all posts under that category, or clicking on the ‘Buddha’ Tag link should arrive at a page that has all posts tagged with that. That first post is categorized and tagged for both of those, so we should at least be able to see that post [among future others similarly categorized or tagged] when clicking on those links… Problem was, that originally those links did not work and instead arrived at a default “Page Not Found”; what gives?!
The problem was the permalink setting that I had chosen: Setting it back to ‘Default’ simply solved the problem; the links now work as expects, hurray! This WordPress forum post helped me figure that out. I forget which other Permalink Setting was previously chosen, and I’m not sure if I actually chose it or it was automatically configured somehow… Whatever the case was, ‘Default’ has fixed the problem 🙂
If I ever want to choose a different Permalink Setting in the future, I’ll be sure to read up on them more first, and immediately test links afterwards!
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
No, I’m not a Otolaryngologist, I’m just trying to reveal the nose, ear, and neck areas of my Buddha bust study… 😛
Here we see beginning to be revealed the area where the nose & lips will be (the front side on the left in this perspective), and the ears (the left-hand ear is visible on the right in this perspective). The ears were revealed by carving down from the top of the head on the front and back sides of the ears. Similarly, the nose/lips area was revealed by carving down on the sides of the face.
If it hasn’t been apparent to you by now, the carved areas are evident by the linear striations (made with tooth chisels like this). Tooth chisels are common to be the primary chisel to use in the beginnings of a sculpture, as their purpose to shear away stone (rather than detail the stone) are well-suited to take away large areas that are still present in the beginning. And that is indeed ~80% of what I’ve been doing so far… I’ve only used flat chisels on a few areas like the current ear-area edges since that is where I want a more detailed linear edge at this point… No point chisels or rondel or diamond chisels yet; and rasps will come near the end for finer detail & smoothing…
Here is the back of the neck being revealed:
So far, I’ve been using various tools to try to measure as exact I reasonably can the locations of intersections and edges of ears: You can see some of them in the pictures so far as the black lines made with pencil on the stone. I think I am nearing the end of where I can figure out things to measure, as I am getting deeper into the stone and to more curved surfaces; you can see in the above picture that I hand-drew the side edges of the neck as they curve (can’t use any flat edge tool therefore, as I have with other measurements so far).
If it is true that I am running out of “measurable” things, and I don’t conceive further ways to measure more difficult things, then I think I am nearing the end of a relatively easier beginning: The beginning would then be easier because I was shearing away large, measurable areas; and going forward may prove to indeed be more difficult with the relative difficulty of being able to measure further things that are smaller and curved… I’ll see how I fare going forward with this challenge… This all may also mark a transition from using the toothed chisels I mentioned to using the other chisels & rasps that may be necessary for beginning more detail…
The first step was chiseling away the top ~5 inches of the original stone, to start revealing the top of the head.
You can also see I’ve progressed in revealing the back of the head and neck.
Here’s a little bit more progress with the hair-covered top of the head starting to be defined a bit more, including the distinction of its 3 tiers: