亚洲综合在线播放,中文字幕亚洲一区二区三区,波多野结衣在线

java光环 — Tue, 14 Feb 2006 08:23:00 GMT

scomp -out weather.jar weather_latlong.xsd myconfig.xsdconfig

Compiles a schema into XML Bean classes and metadata.
Usage: scomp [opts] [dirs]* [schema.xsd]* [service.wsdl]* [config.xsdconfig]*
Options include:
    -cp [a;b;c] - classpath
    -d [dir] - target binary directory for .class and .xsb files
    -src [dir] - target directory for generated .java files
    -srconly - do not compile .java files or jar the output.
    -out [xmltypes.jar] - the name of the output jar
    -dl - permit network downloads for imports and includes (default is off)
    -noupa - do not enforce the unique particle attribution rule
    -nopvr - do not enforce the particle valid (restriction) rule
    -noann - ignore annotations
    -novdoc - do not validate contents of
    -compiler - path to external java compiler
    -javasource [version] - generate java source compatible for a Java version (1.4 or 1.5)
    -ms - initial memory for external java compiler (default '8m')
    -mx - maximum memory for external java compiler (default '256m')
    -debug - compile with debug symbols
    -quiet - print fewer informational messages
    -verbose - print more informational messages
    -version - prints version information
    -license - prints license information
    -allowmdef "[ns] [ns] [ns]" - ignores multiple defs in given namespaces (use ##local for no-namespace)
    -catalog [file] - catalog file for org.apache.xml.resolver.tools.CatalogResolver. (Note: needs resolver.jar from http://xml.apache
.org/commons/components/resolver/index.html)

java光环 2006-02-14 16:23 发表评论

Avoiding "Do you want to resend information" browser messages

java光环 — Mon, 04 Apr 2005 08:24:00 GMT

This might be a minor thing but significantly improves the user experience. The problem usually happens when the update action forwards to the view action. Instead of doing a redirect. This means the user sees /editPerson.action in the address field of the browser. But he is really looking at /viewPerson.action. This means that if he presses reload he will resubmit the data. It also means the user can navigate back to the /editPerson.action by using the back and forward buttons or the browser history.

To avoid this you can use the PRG (Post, Redirect and Get) Pattern. It can be summarized as follows:

Never show pages in response to POST
Always load pages using GET
Navigate from POST to GET using REDIRECT

Using the PRG approach removes this possibility by never showing the /editPerson.action to the user. This means he cannot navigate back to the page in any way. In this case it means a redirect between the editPerson action (update action) and the viewPerson action (view action).

It is easily implemented in Webwork by using the redirect result type. The final mapping of editPerson and viewPerson looks like this.

<action name="editPerson" class="example.EditPersonAction">
   <result name="success" type="redirect">
       <param name="location">/viewPerson.action?id=${userId}param>
       <param name="parse">trueparam>
   result>
   <result name="invalid.token">/duplicate_post.vmresult>
   <interceptor-ref name="defaultStack"/>
   <interceptor-ref name="token"/>
action>

<action name="viewPerson" class="example.ViewPersonAction">
   <result name="success">/view_person.vmresult>
   <interceptor-ref name="defaultStack"/>
action>

One thing to notice is the OGNL expression in the location (/viewPerson.action?id=${userId}) This means Webwork will evaluate the expression at runtime and replace ${userId}. In this case it is taken directly from a request parameter.

In Struts you would have to manually code the redirect as far as I know.

java光环 2005-04-04 16:24 发表评论

Preventing Duplicate Logins with Acegi Security

java光环 — Fri, 25 Mar 2005 03:42:00 GMT

Acegi Security sure makes things a lot simpler (once you have it setup). Today on the AppFuse mailing list, I noticed a link to how to prevent duplicate logins. No code needed, just some configuration changes. Nice!

Update: I tried this on AppFuse and it does work, but I don't like the default implemementation. If a user is already logged in, you can't log in with that same user until the initial session times out. I'd prefer the first session gets invalidated when the second login is made. What's your preference?

java光环 2005-03-25 11:42 发表评论

Developing Test-Driven Web Applications with Spring and Hibernate

java光环 — Fri, 25 Mar 2005 01:43:00 GMT

One of the hardest parts about J2EE development is getting started. There is an immense amount of open source tools for web app development. Making a decision on which technologies to use can be tough--actually beginning to use them can be even more difficult.

Once you've decided to use Struts and Hibernate, how do you go about implementing them? If you look on the Hibernate site or the Struts site, you'll probably have a hard time finding any information on integrating the two. What if you want to throw Spring into the mix? For developers, one of the best ways to learn is by viewing sample apps and tutorials that explain how to extend those applications. In order to learn (and remember) how to integrate open source technologies such as Hibernate, Spring, Struts, and Ant/XDoclet, Raible created AppFuse.

The beauty of AppFuse is you can actually get started with Hibernate, Spring, and Struts without even knowing much about them. Using test-driven development, AppFuse and its tutorials will show you how to develop a J2EE web application quickly and efficiently.

java光环 2005-03-25 09:43 发表评论