Today added document about Thread synchronization.
In Alinous-Core, synchronized block, list like java, is available.
This block has 2 ways about usage.
standard synchronized blocknamed synchronized blockThe detail is simply
written in the document.
This function will used frequently used in Rich Client UI using jQuery.
Because conflict of resource access is big enemy for the Rich Client UI.
And I consider distributed servers, such as clustering web server using cloud
computing. This lock is available in the tomcat cluster.
The Alinous-Core runs on the Apache Tomcat, and can use J2EE functions of the
I will write the detail when I write documents about distributed server and
My next job is make some RichUI samples and write the document. But I'll do
Alinous Document CMS is easily available. It works on the server and cloud
supporting Java Platform.
Today, I've add Alinous-Core IDE and Server's system requirement.
The IDE and Server are both free. You can download it from website. If you
want to work Alinous-Core application, I recommend you to setup Alinous-Core
IDE at first.
Alinous-Core IDE has embeded web server based on Tomcat. And the debugger is
on the server. So the embeded server works debug mode.
You don't have to install Alinous-Server before you finished to make
application and deploy into your server.
The Alinous-Server is release mode. There are no debugger there and work
If you want to deploy it, please sel... (more)
This time, I translated Java connector's section in Alinous-Core Official
Alinous-Core is Domain Specific Language, so in the specifiyed domain, it is
very easy to develop. But sometimes, it is not enough.
So Alinous-Core has the Java connector, which is interface to load java class
and call it from Alinous-Script.
I actually used the function, for example
Output PDF slipsAccess using socketEdit xml filesEdit binary filesJava has a
lot of useful library and if we can use it, there is no disadvantage for
the new domain specific language.
Alinous-Core has class loader to load ja... (more)
I've almost finished to make tutorial of testing automation for jQuery
examples. In this process, I found some of them are not ready for that.
The difference between one of testing automation ready and not ready is
whether it is accessible with xpath or not.
I often use xpath to specify the element in the web browser, so if it is not
specified by the xpath, it is impossible to test it by JUnit and selenium,
which is out of the web browser.
The most easy way to make the web application ready for the xpath is to add
attribute which means the identifier of the element.
For eexample, thi... (more)