Web Development Tutorials

AJAX приложения, Поисковая оптимизация и зачем это нужно

2013-03-09T11:57:00.000-08:00

Сегодня, интернет технологии открывают нам огромные просторы для воображения и для осуществления самых смелых идей. На том же уровне находится и интернет сообщество – люди открыты для нового. Но, несмотря на это, большинство интернет ресурсов даже сайтами назвать сложно, просто вэб страницы. Встает вопрос, почему такой низкий уровень использования новых технологий. Данная статья описывает технологию AJAX и “проблемы”, которые с ней связаны. Также мы разберем методики поисковой оптимизации для сайтов использующих AJAX.

Введение в AJAX

AJAX(Asynchronous Javascript and XML) – технология для построения «богатых» пользовательских интерфейсов. Суть технологии заключается в обмене данными клиента (браузера) с сервером в фоновом режиме. Традиционно при ответе сервера на запрос клиента страница полностью перегружалась. AJAX же, отправляет запрос серверу в фоновом режиме и обновляет только нужную часть страницы при получении ответа.

Поисковая оптимизация для AJAX приложений

Продолжние статьи на сайте интернет агентства Boomerang

JSF Tutorials: Using SEAM 3 Remoting

2012-10-09T09:38:00.001-07:00

In this tutorial I am going to give an overview of Seam 3 Remoting module and give a simple example of how to use it.

Dependency:
Seam Conversation module

The basic idea behind Seam remoting module is to give a developer a tool to work with his Beans without using a JSF actionListeners or something else. Everything is made in background by AJAX. All you need is to execute a JavaScript Function like the following one:

Seam.createBean('myBean').myMethod(arguments,callbackFunction);

Basically you are creating an "instance" of your object on the client side and executing its methods via AJAX.

So lets see an example of how can we use Seam 3 Remoting:

1. Configuration

Put Seam libraries into your project we will definitely need seam-remoting.jar and seam-conversation.jar.

2. Server side:

import javax.enterprise.context.RequestScoped;
import javax.inject.Named;
import org.jboss.seam.remoting.annotations.WebRemote;

@Named

@RequestScoped




public class TestBean {

    @WebMethod // Enables this method for use in client side
    public String sayHello(String name)  {
        return "Hello, " + name;
    }
}




Nothing else is needed on server side.



2. Client side:

You have to add needed .JS libraries into your view:


<script type="text/javascript" src="seam/resource/remoting/resource/remote.js?compress=false"></script> // core remoting library


<script type="text/javascript" src="seam/resource/remoting/interface.js?testBean"></script>

// your Bean instance

Also you can also write interface.js?yourFirstBean&yourSecondBean




Next you can make use of Seam Remoting:




3. Usage:

function sayHello() {

  var name = prompt("Please enter your name:");

  Seam.createBean('myBean').myMethod(name,callbackFunction);

}

function callbackFunction(result) {

  alert(result);

}















Best regards,


NETLink community member

JSF HTML tag library - Form

2012-04-26T05:29:00.000-07:00

h:form

This tag renders an HTML form element. It uses the "post-back" technique to submit form data back to the page that contains the form. The use of the POST method is also required and it is not possible to use the GET method for forms generated by this tag.
If your application requires the use of the GET method for form submission, your options include using plain HTML forms, binding request parameters to backing bean properties, and using the outputLink tag to generate dynamic hyperlinks.
Example

<h:form id="formid"></h:form>

HTML Output

<form id="formid" name="formid" method="post" action="/yourapp/form.jsp" enctype="application/x-www-form-urlencoded"></form>

Tag Attributes

accept	Text

The accept attribute identifies the list of content types that the server processing this form is able to handle.

acceptcharset	Text

The acceptcharset attribute identifies the list of character encodings for user input data that the server processing this form will accept.

binding	Expression

The value-binding expression linking this component tag to a backing bean property.

dir	Enumerated

The dir attribute is a standard HTML attribute that overrides the default text directionality for this component. The values accepted for this component are "LTR" (left-to-right) and "RTL" (right-to-left).

enctype	Enumerated

The enctype attribute sets the content type of the data to be submitted to the server. The default value for this attribute is "application/x-www-form-urlencoded".

id	Text

The unique identifier value for this component. The value must be unique within the closest naming container.

lang	Text

The lang attribute is a standard HTML attribute that sets the code describing the language to be used in the markup generated by this component.

onclick	Text

The onclick attribute sets the JavaScript code to execute when the mouse pointer is clicked over this element.

ondblclick	Text

The ondblclick attribute sets the JavaScript code to execute when the mouse pointer is double-clicked over this element.

onkeydown	Text

The onkeydown attribute sets the JavaScript code to execute when a key is pressed down over this element.

onkeypress	Text

The onkeypress attribute sets the JavaScript code to execute when a key is pressed and released over this element.

onkeyup	Text

The onkeyup attribute sets the JavaScript code to execute when a key is released over this element.

onmousedown	Text

The onmousedown attribute sets the JavaScript code to execute when the mouse pointer is pressed down over this element.

onmousemove	Text

The onmousemove attribute sets the JavaScript code to execute when the mouse pointer is moved within this element.

onmouseout	Text

The onmouseout attribute sets the JavaScript code to execute when the mouse pointer is moved away from this element.

onmouseover	Text

The onmouseover attribute sets the JavaScript code to execute when the mouse pointer is moved onto this element.

onmouseup	Text

The onmouseup attribute sets the JavaScript code to execute when the mouse button is released over this element.

onreset	Text

The onreset attribute sets the JavaScript code to execute when the form is reset.

onsubmit	Text

The onsubmit attribute sets the JavaScript code to execute when the form is submitted.

rendered	Boolean

A value-binding expression that evaluates to a Boolean condition indicating if this component should be rendered.

style	CSS Style

The style attribute sets the CSS style definition to be applied to this component when it is rendered.

styleClass	CSS Class

The styleClass attribute sets the CSS class to apply to this component when it is rendered.

target	Text

The target attribute identifies the name of a frame into which the resource retrieved by this hyperlink should be displayed.

title	Text

The title attribute is a standard HTML attribute that sets the tooltip text to display for the rendered component.

JSF HTML tag library - InputHidden

2012-04-26T04:51:00.002-07:00

h:inputHidden

The inputHidden tag renders an HTML input element of the type "hidden". It is essential that this tag is inside the <h:form> tag.

Example

<h:inputHidden id="hiddenValue" value="#{yourbean.hiddenValue}" />

HTML Output

<input id="form:hiddenValue" name="form:hiddenValue"  type="hidden" value="Your Hidden Value"/>

Tag Attributes

binding	Expression

The value-binding expression linking this component tag to a backing bean property.

converter	Text

The converter attribute sets the converter instance to be registered for this component. It must match the converter-id value of a converter element defined in your Faces configuration file.

id	Text

The unique identifier value for this component. The value must be unique within the closest naming container.

immediate	Boolean

The immediate attribute is a boolean flag indicating that component events should be sent to registered event listeners immediately rather than after the validation phase of the JSF request processing lifecycle. The immediate flag allows you bypass JSF validation for a particular component.

rendered	Boolean

A value-binding expression that evaluates to a Boolean condition indicating if this component should be rendered.

required	Boolean

The required attribute is a boolean flag that indicates whether or not the user is required to provide a value for this field before the form can be submitted to the server.

validator	Text

The validator attribute accepts a method-binding expression representing a validator method that will be called when the JSF framework validates this component. A validator method must be a public method that takes FacesContext, UIComponent, and Object parameters, with a return type of void.

value	Text

The value attribute sets the current value for this component.

valueChangeListener	Text

The valueChangeListener attribute accepts a method-binding expression representing a value change listener method to be notified when a new value has been set for this input component. A value change listener method must be a public method that takes a ValueChangeEvent parameter, with a return type of void.

JSF HTML tag library - InputSecret

2012-04-26T04:45:00.001-07:00

h:inputSecret

The inputSecret tag renders an HTML input element of the type "password". It is essential that this tag is inside the <h:form> tag.

Example

<h:inputSecret id="password" value="#{yourbean.password}" />

HTML Output

<input id="form:password" name="form:password" type="password" />

Tag Attributes

accesskey	Text

The accesskey attribute is a standard HTML attribute that sets the access key that transfers focus to this element when pressed.

alt	Text

The alt attribute is a standard HTML attribute that sets the alternate textual description rendered by this component.

binding	Expression

The value-binding expression linking this component tag to a backing bean property.

converter	Text

The converter attribute sets the converter instance to be registered for this component. It must match the converter-id value of a converter element defined in your Faces configuration file.

dir	Enumerated

The dir attribute is a standard HTML attribute that overrides the default text directionality for this component. The values accepted for this component are "LTR" (left-to-right) and "RTL" (right-to-left).

disabled	Boolean

The disabled attribute is a boolean flag that when set to true indicates that this component should not receive focus or be included in a form submit.

id	Text

The unique identifier value for this component. The value must be unique within the closest naming container.

immediate	Boolean

The immediate attribute is a boolean flag indicating that component events should be sent to registered event listeners immediately rather than after the validation phase of the JSF request processing lifecycle. The immediate flag allows you bypass JSF validation for a particular component.

lang	Text

The lang attribute is a standard HTML attribute that sets the code describing the language to be used in the markup generated by this component.

maxlength	Text

The maxlength attribute sets the maximum length in characters of the string accepted by this input component.

onblur	Text

The onblur attribute sets the JavaScript code to execute when this element loses focus.

onchange	Text

The onchange attribute sets the JavaScript code to execute when this element loses focus and its value changes after gaining focus.

onclick	Text

The onclick attribute sets the JavaScript code to execute when the mouse pointer is clicked over this element.

ondblclick	Text

The ondblclick attribute sets the JavaScript code to execute when the mouse pointer is double-clicked over this element.

onfocus	Text

The onfocus attribute sets the JavaScript code to execute when the element receives focus.

onkeydown	Text

The onkeydown attribute sets the JavaScript code to execute when a key is pressed down over this element.

onkeypress	Text

The onkeypress attribute sets the JavaScript code to execute when a key is pressed and released over this element.

onkeyup	Text

The onkeyup attribute sets the JavaScript code to execute when a key is released over this element.

onmousedown	Text

The onmousedown attribute sets the JavaScript code to execute when the mouse pointer is pressed down over this element.

onmousemove	Text

The onmousemove attribute sets the JavaScript code to execute when the mouse pointer is moved within this element.

onmouseout	Text

The onmouseout attribute sets the JavaScript code to execute when the mouse pointer is moved away from this element.

onmouseover	Text

The onmouseover attribute sets the JavaScript code to execute when the mouse pointer is moved onto this element.

onmouseup	Text

The onmouseup attribute sets the JavaScript code to execute when the mouse button is released over this element.

onselect	Text

The onselect attribute sets the JavaScript code to execute when the user selects the text contained by this element.

readonly	Boolean

The readonly attribute is a boolean flag that when set to true prohibits changes to this element by the user. The element will continue to receive focus unless you set the disabled attribute to true.

rendered	Boolean

A value-binding expression that evaluates to a Boolean condition indicating if this component should be rendered.

required	Boolean

The required attribute is a boolean flag that indicates whether or not the user is required to provide a value for this field before the form can be submitted to the server.

size	Text

The size attribute sets the width in characters of this input field.

style	CSS Style

The style attribute sets the CSS style definition to be applied to this component when it is rendered.

styleClass	CSS Class

The styleClass attribute sets the CSS class to apply to this component when it is rendered.

tabindex	Text

The tabindex attribute is a standard HTML attribute that sets the order in which this element receives focus when the user cycles through the elements using the TAB key. The value for this attribute must be an integer between 0 and 32767.

title	Text

The title attribute is a standard HTML attribute that sets the tooltip text to display for the rendered component.

validator	Text

The validator attribute accepts a method-binding expression representing a validator method that will be called when the JSF framework validates this component. A validator method must be a public method that takes FacesContext, UIComponent, and Object parameters, with a return type of void.

value	Text

The value attribute sets the current value for this component.

valueChangeListener	Text

The valueChangeListener attribute accepts a method-binding expression representing a value change listener method to be notified when a new value has been set for this input component. A value change listener method must be a public method that takes a ValueChangeEvent parameter, with a return type of void.

JSF HTML tag library - InputText

2012-04-26T04:41:00.000-07:00

h:inputText

The inputText tag renders an HTML input element of the type "text". It is essential that your tag is inside the <h:form> tag.

Example

<h:inputText id="login" value="#{yourbean.username}" />

HTML Output

<input id="form:login" name="form:login" type="text" />

Tag Attributes

accesskey	Text

The accesskey attribute is a standard HTML attribute that sets the access key that transfers focus to this element when pressed.

alt	Text

The alt attribute is a standard HTML attribute that sets the alternate textual description rendered by this component.

binding	Expression

The value-binding expression linking this component tag to a backing bean property.

converter	Text

The converter attribute sets the converter instance to be registered for this component. It must match the converter-id value of a converter element defined in your Faces configuration file.

dir	Enumerated

The dir attribute is a standard HTML attribute that overrides the default text directionality for this component. The values accepted for this component are "LTR" (left-to-right) and "RTL" (right-to-left).

disabled	Boolean

The disabled attribute is a boolean flag that when set to true indicates that this component should not receive focus or be included in a form submit.

id	Text

The unique identifier value for this component. The value must be unique within the closest naming container.

immediate	Boolean

The immediate attribute is a boolean flag indicating that component events should be sent to registered event listeners immediately rather than after the validation phase of the JSF request processing lifecycle. The immediate flag allows you bypass JSF validation for a particular component.

lang	Text

The lang attribute is a standard HTML attribute that sets the code describing the language to be used in the markup generated by this component.

maxlength	Text

The maxlength attribute sets the maximum length in characters of the string accepted by this input component.

onblur	Text

The onblur attribute sets the JavaScript code to execute when this element loses focus.

onchange	Text

The onchange attribute sets the JavaScript code to execute when this element loses focus and its value changes after gaining focus.

onclick	Text

The onclick attribute sets the JavaScript code to execute when the mouse pointer is clicked over this element.

ondblclick	Text

The ondblclick attribute sets the JavaScript code to execute when the mouse pointer is double-clicked over this element.

onfocus	Text

The onfocus attribute sets the JavaScript code to execute when the element receives focus.

onkeydown	Text

The onkeydown attribute sets the JavaScript code to execute when a key is pressed down over this element.

onkeypress	Text

The onkeypress attribute sets the JavaScript code to execute when a key is pressed and released over this element.

onkeyup	Text

The onkeyup attribute sets the JavaScript code to execute when a key is released over this element.

onmousedown	Text

The onmousedown attribute sets the JavaScript code to execute when the mouse pointer is pressed down over this element.

onmousemove	Text

The onmousemove attribute sets the JavaScript code to execute when the mouse pointer is moved within this element.

onmouseout	Text

The onmouseout attribute sets the JavaScript code to execute when the mouse pointer is moved away from this element.

onmouseover	Text

The onmouseover attribute sets the JavaScript code to execute when the mouse pointer is moved onto this element.

onmouseup	Text

The onmouseup attribute sets the JavaScript code to execute when the mouse button is released over this element.

onselect	Text

The onselect attribute sets the JavaScript code to execute when the user selects the text contained by this element.

readonly	Boolean

The readonly attribute is a boolean flag that when set to true prohibits changes to this element by the user. The element will continue to receive focus unless you set the disabled attribute to true.

rendered	Boolean

A value-binding expression that evaluates to a Boolean condition indicating if this component should be rendered.

required	Boolean

The required attribute is a boolean flag that indicates whether or not the user is required to provide a value for this field before the form can be submitted to the server.

size	Text

The size attribute sets the width in characters of this input field.

style	CSS Style

The style attribute sets the CSS style definition to be applied to this component when it is rendered.

styleClass	CSS Class

The styleClass attribute sets the CSS class to apply to this component when it is rendered.

tabindex	Text

The tabindex attribute is a standard HTML attribute that sets the order in which this element receives focus when the user cycles through the elements using the TAB key. The value for this attribute must be an integer between 0 and 32767.

title	Text

The title attribute is a standard HTML attribute that sets the tooltip text to display for the rendered component.

validator	Text

The validator attribute accepts a method-binding expression representing a validator method that will be called when the JSF framework validates this component. A validator method must be a public method that takes FacesContext, UIComponent, and Object parameters, with a return type of void.

value	Text

The value attribute sets the current value for this component.

valueChangeListener	Text

The valueChangeListener attribute accepts a method-binding expression representing a value change listener method to be notified when a new value has been set for this input component. A value change listener method must be a public method that takes a ValueChangeEvent parameter, with a return type of void.

JSF HTML tag library - OutputText

2012-04-26T04:31:00.003-07:00

h:outputText

The outputText tag renders basic text on your JSF page. You can customize it using standard attributes of h:outputText tag. You can add styles to it. Define the logic when it will be rendered. Also, if your output text will render some HTML code from the database, in order to render it appropriately you would set escape attribute to false.

Example

<h:outputText value="#{yourbean.hello}" />

HTML Output

Hello message of your bean!

Tag Attributes

binding	Expression

The value-binding expression linking this component tag to a backing bean property.

converter	Text

The converter attribute sets the converter instance to be registered for this component. It must match the converter-id value of a converter element defined in your Faces configuration file.

escape	Boolean

The escape attribute is a boolean flag that determines if sensitive HTML and XML characters should be escaped in the ourput generated by this component. The default value for this attribute is "true".

id	Text

The unique identifier value for this component. The value must be unique within the closest naming container.

rendered	Boolean

A value-binding expression that evaluates to a Boolean condition indicating if this component should be rendered.

style	CSS Style

The style attribute sets the CSS style definition to be applied to this component when it is rendered.

styleClass	CSS Class

The styleClass attribute sets the CSS class to apply to this component when it is rendered.

title	Text

The title attribute is a standard HTML attribute that sets the tooltip text to display for the rendered component.

value	Text

The value attribute sets the current value for this component.

JSF Tutorials: JSF 2 Lifecycle

2012-04-26T03:35:00.001-07:00

JSF 2 Lifecycle

Restore view

RestoreView is the first phase in the JSF lifecycle. Restore view phase is constructing view for the front end. Every view has it's own view id and it is stored in the FacesContext's session object. JSF View is collection of components associated with its current state. In JSF 2 you have two types of saving methods:

Server (default)
Client

Server method is set by the default. You can configure it in web.xml as context param using javax.faces.STATE_SAVING_METHOD parameter name:

<context-param>

<param-name>javax.faces.STATE_SAVING_METHOD</param-name>

<param-value>client</param-value>

</context-param>

Apply Requests

After restoring the component tree, each component in the tree extracts its new value from the request parameters by using its decode method. After that the value is locally stored in the component. If the conversion of the value fails, an error message associated with the component is generated and queued on FacesContext. This message will be displayed during the render response phase, along with any validation errors resulting from the process validations phase.

Process Validations

In Process Validations phase JavaServer Faces implementation processes all validators registered on the components in the component tree. It examines the component attributes that specify the rules for the validation and compares these rules to the local value stored for the component.

Update Model Values

After JSF validates the data, it can set component tree corresponding server-side object properties to the components' local values. The JavaServer Faces implementation will update only the bean properties pointed at by an input component's value attribute.

If it is impossible to covert the local data to the types specified by the bean properties, the life cycle advances directly to the render response phase so that the page is rerendered with errors. Same happens to the validation errors.

Invoke Applications

During Invoke Application phase, the JSF handles any application-level events, such as submitting a form or linking to another page.

At this point, if the application needs to redirect to a different web application resource or generate a response that does not contain any JavaServer Faces components, it can call FacesContext.responseComplete.

Render Response

During Render Response phase, JavaServer Faces gives authority for rendering the page to the JSP container if the application is using JSP pages. If this is an initial request, the components represented on the page will be added to the component tree as the JSP container executes the page. If this is not an initial request, the components are already added to the tree so they needn't be added again.

JSF Примеры - создание шаблонов

2012-04-23T09:42:00.002-07:00

При разработке веб приложения большинство страниц выглядят одинаково. Вместо того что-бы не создавать кучу ненужного кода, используются шаблоны. В JSF 2 предусмотрена гибкая система шаблонов. В основном мы будем использовать Facelet теги, такие как:

1. ui:composition - при добавлении аттрибута "template" ваша страница будет использовать шаблон указанный в значении аттрибута.

2. ui:insert - определяет область в которую будет вставлена информация в шаблон из страницы (аттрибут "name" тегов ui:insert и ui:define должны совпадать).

3. ui:define - Определяет область страницы, которая будет вставлена в шаблон.

4. ui:include - вставляет код отдельной страницы.

Базовая структура шаблона

<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:p="http://primefaces.org/ui" xmlns:pretty="http://ocpsoft.com/prettyfaces">

<h:head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <h:outputStylesheet library="css" name="layout.css"></h:outputStylesheet> <ui:insert name="pageHeader" /></h:head><h:body>
<ui:insert name="headerBlock" />

<ui:include src="/pages/includes/defaultHeader.xhtml" />

</ui:insert>

<div id="content"> <ui:insert name="contentBlock">

<ui:include src="/pages/includes/defaultContent.xhtml" />

</ui:insert>

</div></h:body></html>

Это структура шаблона, которую я обычно использую. В head мы будем вставлять css для определенных страниц. Тэг ui:insert определяет область куда будет вставляться контент. Если для тэга ui:insert не указан соответствующий тэг ui:define, то по стандарту будет использоваться код находящийся внутри ui:insert. К примеру, в данном случае если мы не укажем <ui:define name="headerBlock">, то по стандарту будет использоваться <ui:include src="/pages/includes/defaultHeader.xhtml" />.

Пример страницы с использованием шаблона

<ui:composition xmlns="http://www.w3.org/1999/xhtml"

xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:p="http://primefaces.org/ui"
template="/layout/template.xhtml">
<ui:define name="pageHeader">

<h:outputStylesheet library="css" name="page1.css"></h:outputStylesheet>

</ui:define>
<ui:define name="headerBlock">

This is the content of headerBlock.
</ui:define>
<ui:define name="contentBlock">
This is the content of contentBlock.
</ui:define>
</ui:composition>

Для того что-бы ваша страница использовала шаблон необходимо добавить аттрибут template в тело тэга ui:composition.

Зная выше перечисленное вы сможете еффективно создавать шаблоны с помощью JSF 2 Facelets.

С уважением,

Netlink community member

Understanding JSF - Part 4 - Templating

2012-04-23T08:32:00.001-07:00

When developing a web application your pages will usually look a same. In this JSF 2 tutorial you will see how to create templates in JSF. In JSF we do this with a set of Facelet tags:

1. ui:composition - by adding an attribute "template" your page will use a template you have created.

2. ui:insert - defines the area where the code will be inserted into the template from a specific page.

3. ui:define - defines the area which will be included into the template.

4. ui:include - inserts a code from the separate file.

Basic structure of the template

<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:p="http://primefaces.org/ui" xmlns:pretty="http://ocpsoft.com/prettyfaces">

<h:head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <h:outputStylesheet library="css" name="layout.css"></h:outputStylesheet> <ui:insert name="pageHeader" /></h:head><h:body>
<ui:insert name="headerBlock" />

<ui:include src="/pages/includes/defaultHeader.xhtml" />

</ui:insert>

<div id="content"> <ui:insert name="contentBlock">

<ui:include src="/pages/includes/defaultContent.xhtml" />

</ui:insert>

</div></h:body></html>

This is a basic template structure I usually use. In the head we would include a page specific CSS.
Tag ui:insert defines where a content will be inserted. If no ui:define tag have been defined for the ui:insert, the content which lies inside the ui:insert tag will be used as a default. So in this case if in our page we do not define "headerBlock", defaultHeader.xhtml will be used as a default.

Example of page which uses template

<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:p="http://primefaces.org/ui"
template="/layout/template.xhtml">
<ui:define name="pageHeader">

<h:outputStylesheet library="css" name="page1.css"></h:outputStylesheet>

</ui:define>
<ui:define name="headerBlock">
This is the content of headerBlock.
</ui:define>
<ui:define name="contentBlock">
This is the content of contentBlock.
</ui:define>
</ui:composition>

In order for your page to use a template you have to add a template attribute to your ui:composition tag.

Knowing only this concepts you will be able to effectively use JSF 2 Templating system.

Best regards,

Netlink community member

Введение в JSF - Часть 3 - Область видимости бина

2012-04-19T13:27:00.001-07:00

Этот пост является продолжением уроков по JSF. Если вы только присоеденились, советую прочитать предидущие уроки. В этом уроке мы разберем область видимости бинов. При разработке приложения у каждого компонента есть свое предназначение и оно не вечно. Контейнер JSF предоставляет 3 области видимости бинов:

1. Область видимости действия

2. Область видимости сессии

3. Область видимости приложения

Так же существуют такие области видимости как область видимости страница и область видимости диалого. Их мы расмотрим позже в отдельности.

Для того что-бы определить область видимости бина используются следующие аннотации:

@RequestScope

@SessionScope

@ApplicationScope

Session scope

Обозначает то ваш бин будет хранится до окончания сеанса. Такой тип обычно используется для хранения информации о пользователе лил если у вас интернет магазин, для тележки покупок. Вы можете наглядно посмотреть как используется данная область видимости в предидущем уроке.

Request scope

Самы распростроненная область видимости. Используется почти при каждом действии. К примеру, добавление информации в базу данных, извлечении и удалении.

Application scope

Область видимости приложения используется в том случае если вы хотите хранить какую-либо информацию на протяжении жизни приложения.

Best regards,

Netlink community member

Understanding JSF - Part 3 - Bean scope

2012-04-19T13:12:00.004-07:00

This post is a continuation of JSF tutorials series. If you are new to jsf I would recommend you to read the previous jsf tutorials. In this session I will explain bean scopes in jsf. When you are developing an application you have a variety of components, each for a different task. In order to make those components work as they have to we have scopes. We can define 3 scopes for JSF and CDI beans:

1. Request scope

2. Session scope

3. Application scope

In JSF 2 we also have View scope and Conversation scope.

In order to assign a scope for your bean you would use the following annotations during declaration:

@RequestScope

@SessionScope

@ApplicationScope

Session scope

If the Session scope is declared your bean will be held until the session is over. This type of scope is usually used in order to store user data during the session, or for example in a web store you would use session scope in order to store the items in the shopping cart.

Request scope

Request scope is the most common scope. You would use it practically in every action like saving information to the database, retrieving it, deleting it and so on.

Application scope

Application scope indicates that the information of the bean will be stored starting from the moment the application has been launched and until it is stopped.

Best regards,

Netlink community member

Sending mail from JSF - Seam mail

2012-04-17T05:55:00.001-07:00

In this tutorial I would like to describe how to send mail from your jsf contact form.

There are a lot of solutions to this problem. But on my practice I really liked SEAM Mail.

There are a few things you have to do.

1. Download Seam libraries
2. Add seam-beans.xml to your WEB-INF folder of your project with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:s="urn:java:ee" xmlns:mail="urn:java:org.jboss.seam.mail.core"
xmlns:ss="urn:java:org.jboss.seam.security" xmlns:ee="urn:java:ee"
xsi:schemaLocation="
http://java.sun.com/xml/ns/javaee
http://docs.jboss.org/cdi/beans_1_0.xsd">

<mail:MailConfig serverHost="yoursmtpserveripaddress" serverPort="25">

</beans>

3. Use the following to send mail:

package org.netlink.view.registration;
import java.io.Serializable;
import javax.enterprise.context.SessionScoped;
import javax.enterprise.inject.Instance;
import javax.inject.*;
import org.jboss.seam.mail.api.*;
import org.jboss.seam.mail.core.enumerations.MessagePriority;
public class MailAction implements Serializable {
@Inject
private Instance<MailMessage> mailMessage;

public void sendMail() {

MailMessage m = mailMessage.get();
m.from("John Doe<customer@mysite.com>")
.to("Jane Doe<admin@ mysite.com >")
.subject(subject)
.bodyHtml(body)
.importance(MessagePriority.HIGH)
.send();
}
}

Now use sendMail() method where ever you want.

Best regards,

Netlink community member

Введение в JSF - Доступ к бинам

2012-04-17T05:01:00.000-07:00

Если вы только начали читать этот блог, то советую прочитать предидущие примеры jsf. В этом уроке я расскажу как использовать Управляемые бины в JSF страницах. Мы будем использовать приложение Hello World, которое мы разработали в прошлом уроке.

Управляемые бины - Глубокий взгляд

Java бин - это Java класс который предоставляет доступ к своим свойствам и методам JSF страницам. Вы имеете доступ к свойствам (переменным) бина по средствам общепринятого стандарта - get/set методы. К примеру, если у вас есть свойство name, то метод для доступа к этому свойству будет getName() (первая буква переменной в названии метода должна быть заглавной).

Вот пример управляемого бина:

package org.netlink.examples;

import javax.inject.*;
import javax.enterprise.context.SessionScoped;
import java.io.Serializable;

@Named
@SessionScoped
public class MyBean implements Serializable {
private String name;
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}

1. @Named - аннотация, котороя указывает что это CDI (Context & Dependency Injection) бин. Это очень удобно так как не надо объявлять бин в faces-config.xml. Используя аннотацию @Named мы можем получить доступ к бину из JSF страница по средствам EL #{myBean.name}. Также мы могли бы написать @Named(name="myBestBean") и использовать #{myBestBean.name).

2. @SessionScoped - время жизни бина. SessionScoped означает что бин будет жить до окончания сессии. Жизненные циклы мы рассмотрим в последующих уроках.

3. Serializable - CDI бин должен имплементировать итерфейс Serializable.

Теперь мы можем получить доступ к бину из JSF страницы. Пример:

1. home.xhtml

<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html">
<h:head>
</h:head>
<h:body>
<h:form>
Enter your name: <br />
<h:inputText value="#{myBean.name}" /><br />
<h:commandButton action="welcome" value="Welcome!"></h:commandButton>
</h:form>
</h:body>
</ui:composition>

Note: любая вводимая пользователем информация должна заключаться в тэг <h:form>.

2. welcome.xhtml

<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html">

<h:outputText value="Welcome #{myBean.name} !" />
</ui:composition>

3. Последнее что нужно сделать это добавить файл beans.xml в дерикторию WEB-INF:

<?xml version="1.0" encoding="UTF-8"?><beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:java:ee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd"></beans>

Теперь поместите приложение на сервер и запустите его >>> localhost:8080/helloworld

Вопросы пишите в комментариях. В будущем вы сможете найти всевозможные примеры jsf на этом блоге.

Best regards,
Netlink community member

Understanding JSF - Part 2 - Accessing Beans

2012-04-17T04:47:00.001-07:00

If you are just starting with JSF I would recommend you to read the previous tutorials. In this tutorial I will explain how to access your Managed Beans from JSF view pages. We will use a JSF application which we have developed in the previous tutorial.

Managed Beans - Deeper look

Java bean - is a Java class which gives the access to its variables and methods to JSF pages. You are accessing your beans using a declaration of get/set method of your variables. For example, if you have a variable name, the get method will be getName() (first letter of the variable in the method which corresponds to this variable have to be uppercase).

Here is the example of the simple bean:

package org.netlink.examples;

import javax.inject.*;
import javax.enterprise.context.SessionScoped;
import java.io.Serializable;

@Named
@SessionScoped
public class MyBean implements Serializable {
private String name;
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}

1. @Named - this annotation indicates that we are using CDI (Context & Dependency Injection) bean. It is better thus we do not have to specify our bean in faces-config.xml. Using @Named annotation we will be able to access our bean from JSF view page using EL #{myBean.name}. We could also write @Named(name="myBestBean") and use #{myBestBean.name).

2. @SessionScoped - it is the scope of the bean. SessionScoped means that our bean will live through out the session. We will have a deeper look on bean scopes later in other tutorials.

3. Serializable - CDI beans must also implement Serializable interface.

So, now we can access our bean from JSF page. Here is an example:

1. home.xhtml

<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html">
<h:head>
</h:head>
<h:body>
<h:form>
Enter your name: <br />
<h:inputText value="#{myBean.name}" /><br />
<h:commandButton action="welcome" value="Welcome!"></h:commandButton>
</h:form>
</h:body>
</ui:composition>

Note: every input should be nested in h:form.

2. welcome.xhtml

<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html">

<h:outputText value="Welcome #{myBean.name} !" />
</ui:composition>

3. The last thing you have to add is an empty beans.xml file:

<?xml version="1.0" encoding="UTF-8"?><beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:java:ee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd"></beans>

Now deploy your application, start jboss and go to localhost:8080/helloworld

If you have any questions please write them in comments.

Best regards,
Netlink community member

Новостной обзор: Google - Project Glass

2012-04-15T22:09:00.001-07:00

Незнаю как вы, но я был действительно впечатлен тем, что увидел. Потрясающая штука!

До нас это конечно дойдет ещё не скоро, но если это появится то будет очень круто!

Введение в JSF

2012-04-15T06:38:00.001-07:00

Введение

JSF - Java Server Faces это Java вэб фреймворк построенный на идее переиспользуемых ui компонентов. JSF - это стандардизированная Java технология. На моем опыте JSF очень облегчил работу если сравнивать его с JSP. Смысл JSF это переиспользуемые компоненты которые очень облегают разработку.

Основные элементы JSF которые вам нужно помнить:

1. Управляемые бины
2. Сильная система шаблонов
3. Большой спектр библиотек тегов на основе XML
4. Встроенная поддержка AJAX - <f:ajax /> (советую попробовать такие фреймворки как Richfaces, PrimeFaces и IceFaces)
5. Expression Language (EL) - методика по средствам которой вы имеете доступ к своим управляемым бинам в JSF странице.

Это были ключевые элементы JSF 2.

Примеры JSF:

Simple "Hello World" JSF Application

Для данного урока требуется пройти предыдущие уроке по установке рабочей среды. Откройте Eclipse.

1. File >> New >> Other >> Web >> Dynamic Web Project
2. Project name: helloworld
3. Choose your Jboss runtime
4. Dynamic web module version: 3.0
5. Configuration: Default for your targeted runtime
6. Next
7. Now you have to choose your folders on the build path. I use the following structure:
src/main/java (For your java classes)
src/main/resources (For some of your configuration files)
8. In the next window tick on "Generate web.xml"
8.1 Now the wizard will ask if you prefer Java EE perspective. Personally me, I prefer Web Development perspective.

Теперь у вас есть структура стандартного веб проекта. Далее вам нужно изменить некоторые вещи.
В web.xml который находится в WebContent/WEB-INF поместите следующий код (вместо того который там есть):

<?xml version="1.0" encoding="UTF-8"?><web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
<display-name>Helloworld</display-name>

<context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Development</param-value> </context-param>
<session-config> <session-timeout>6</session-timeout> </session-config>

<servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet>
<servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.xhtml</url-pattern> </servlet-mapping>
 </web-app>

В WebContent/WEB-INF создайте файл faces-config.xml и вставьте в н:его следующий код:

<?xml version="1.0" encoding="UTF-8"?><faces-config version="2.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"> <name>Helloworld1</name>
<application> <resource-bundle> <base-name>resources</base-name> <var>resources</var> </resource-bundle> </application></faces-config>

Создайте index.html в корне вашего вэб приложения (WebContent) со следующим контентом:

<html><head><meta http-equiv="Refresh" content="0; URL=home.xhtml"/></head></html>

Создайте home.xhtml в той же дериктории:

<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html">

<h:outputText value="Hello World!" />
</ui:composition>

Project >> Clean >> Your project

Внизу у вас есть вкладка Server. Добавьте в ней нужный сервер и добавьте ваше приложение. Full Publish.

Включаем сервер и заходим через браузер на localhost:8080/helloworld. Если у вас возникли какие-либо вопросы то пишите их в комментариях.

С уважением,

Netlink community member

Understanding JSF

2012-04-15T04:42:00.002-07:00

Introduction

JSF - Java Server Faces is a Java Web framework based on idea of components driven development. JSF is a standardized Java technology. On my personal experience starting from Java servlets and JSP, JSF really makes difference. The core is the concept which lies behind the idea of JSF. The core idea is reusable components which simplifies the development process a lot.

The core features of JSF which you have to remember are:

1. Managed beans
2. Powerful template system
3. Variety of XML-based tag libraries
4. Ajax in-built support (especially if you will try Richfaces, PrimeFaces or IceFaces)
5. Expression Language (EL) - the technique to access your Managed beans from your JSF pages.

These are the things that I consider the main features of JSF 2. You will see how the majority of those features is used in the following application.

Simple "Hello World" JSF Application

For this tutorial you need to have installed Eclipse with Jboss Tools and configured Jboss Application Server. If you do not have it, please follow the previous tutorials. Now open the Eclipse.

1. File >> New >> Other >> Web >> Dynamic Web Project
2. Project name: helloworld
3. Choose your Jboss runtime
4. Dynamic web module version: 3.0
5. Configuration: Default for your targeted runtime
6. Next
7. Now you have to choose your folders on the build path. I use the following structure:
src/main/java (For your java classes)
src/main/resources (For some of your configuration files)
8. In the next window tick on "Generate web.xml"
8.1 Now the wizard will ask if you prefer Java EE perspective. Personally me, I prefer Web Development perspective.

So now you have a basic structure of a web application. But there are a few things that we have to change.
Change your web.xml in WebContent/WEB-INF to the following:

<?xml version="1.0" encoding="UTF-8"?><web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
<display-name>Helloworld</display-name>

<context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Development</param-value> </context-param>
<session-config> <session-timeout>6</session-timeout> </session-config>

<servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet>
<servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.xhtml</url-pattern> </servlet-mapping>
 </web-app>

In WebContent/WEB-INF create file faces-config.xml with the following content:

<?xml version="1.0" encoding="UTF-8"?><faces-config version="2.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"> <name>Helloworld1</name>
<application> <resource-bundle> <base-name>resources</base-name> <var>resources</var> </resource-bundle> </application></faces-config>

Create index.html in the root of your WebContent folder with the following content:

<html><head><meta http-equiv="Refresh" content="0; URL=pages/home.xhtml"/></head></html>

Create home.xhtml in the same directory which will contain the following:

<ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html">

<h:outputText value="Hello World!" />
</ui:composition>

Project >> Clean >> Your project

Now in the bottom you will find Server tab. Add your server and add your application there. Now right click on your application and Full Publish.

Now run your server and go to localhost:8080/helloworld. If you had any questions or problems please write in comments.

Best regards,

Netlink community member

JSF - Displaying images from database in JSF

2012-04-13T01:31:00.001-07:00

In the past it took me some time to get an idea of how to store images in database and how to display them in jsf. So I would like to show everyone how come around this problem how it is done.

What do you need:
1. Image entity class
2. Servlet which retrieves images by name and renders them.

Image entity class is not a big deal. In the database you would usually store images as a BLOB value in bytes. In your entity you just have to add an annotation @LOB to your image binary field.

Here is the servlet:

import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.inject.Inject;
import java.io.BufferedOutputStream;
import java.io.BufferedInputStream;
import org.gicm.cms.CMSDao;
import org.gicm.model.UploadedImage;
@WebServlet("/images/*")
public class TestServlet extends HttpServlet {

    @Inject
    private CMSDao cms;

    @Override
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {
        String imageId = String.valueOf(request.getPathInfo().substring(1)); // Gets string that goes after "/images/".
        UploadedImage image = cms.findImage(imageId); // Get Image from DB.

        response.setHeader("Content-Type", getServletContext().getMimeType(image.getName()));
        response.setHeader("Content-Disposition", "inline; filename=\"" + image.getName() + "\"");

        BufferedInputStream input = null;
        BufferedOutputStream output = null;

        try {
            input = new BufferedInputStream(image.getData()); // Creates buffered input stream.
            output = new BufferedOutputStream(response.getOutputStream());
            byte[] buffer = new byte[8192];
            for (int length = 0; (length = input.read(buffer)) > 0;) {
                output.write(buffer, 0, length);
            }
        } finally {
            if (output != null) try { output.close(); } catch (IOException logOrIgnore) {}
            if (input != null) try { input.close(); } catch (IOException logOrIgnore) {}
        }
    }
}



Now the images can be accessed through yoursite.com/images/imagename



So what you can do is basically create a reference table in your database which will be connected to your images table to reference the name of the image, and in your managed bean retrieve the List of images in reference table.



In your JSF you will do something like this:

<img src="/images/{image.name} />



Best regards,

NETLink community member

Eclipse configuration for JBOSS

2012-04-11T12:49:00.002-07:00

Hello dear readers.

In this tutorial I will explain how to configure Eclipse, so we can finally move to development process.

If you have not yet downloaded all the tools you need for development, then see the previous article. Now you need the following:

1. Window >> Preferences >> Java >> Installed JREs >> Link to your JDK

2. Window >> Preferences >> Server >> Runtime Environments >> Add

Pick your version of Jboss
Specify the directory of your JBOSS
Choose your JDK
Specify the path to your main configuration file of Jboss - standalone.xml ($JBOSS_HOME/standalone/configuration/standalone.xml)
Specify the type of the server (Local || Externally managed)

Now your environment is practically ready to start programming. In the next tutorial we will take a quick overview of the techniques we will use for development and write our first application.

Best regards,

NetLink community member

Environment configuration for Java EE platform

2012-04-11T12:44:00.002-07:00

Greetings dear readers.

In this tutorial you will see the environment I am working in while developing Java EE applications. Write now I am working as a web developer developing applications on JBOSS AS using JSF, SEAM, Richfaces, PrettyFaces and some other frameworks. In this tutorial the main aspect will be the configuration of your work space.

What is Application Server?

It is a server which has in-built services that makes your application a much more powerful tool. Those services include security, load balancing, transaction support and much more. Application servers are usually used to create enterprise applications. In the upcoming articles you will get a better understanding of application servers.

Environment configuration

1. Install the latest JDK

2. Download JBOSS AS (preferably of version 7*)

3. Install it the desired directory
4. Add an environment variables $JAVA_HOME and $JBOSS_HOME targeting on your JDK and JBOSS directory respectively.

5. In order to start a development process you need an IDE. There is plenty of them but I would suggest Eclipse because it has a good integration with JBOSS (through Jboss Tools plugin for Eclipse).

6. Download Jboss Tools Plugin.

7. Install it into Eclipse

If you have any questions or issues please feel free to write it in the comments. It is enough for this time. In the next tutorial I will explain how to configure Eclipse to work with JBOSS.

Best regards,

NetLink community member

Настройка Eclipse

2012-04-10T11:16:00.000-07:00

Добрый день дорогие читатели.

Сегодня я расскажу как правильно настроить Eclipse для того чтобы приступить хоть к какому то кодингу.

С учетом что вы уже установили Eclipse вместе с Jboss Tools, ваши действия будут следующими:

1. Window >> Preferences >> Java >> Installed JREs >> Ставим наш JDK

2. Window >> Preferences >> Server >> Runtime Environments >> Add

Выбираем нашу версию Jboss
Указываем на директорию где он находится
Выбираем JDK
Указываем путь к основному конфигурационному файлу Jboss - standalone.xml ($JBOSS_HOME/standalone/configuration/standalone.xml)
Далее указываем тип сервера (Local || Externally managed)

Так, вроде бы все на сегодня. В следующем уроке будем писать первое приложение. Всем спасибо.

С уважением,

NetLink community member

Настройка рабочей среды для разработки на платформе Java EE

2012-04-09T05:52:00.000-07:00

Добрый день дорогие читатели.

Сегодня я хотел бы немного рассказать о среде разработки в которой я работаю и как её построить. В данный момент я разрабатываю вэб приложения на Java EE. В качестве Application Server я использую Jboss AS 7.1. Как раз таки этому я и хотел бы уделить основное внимание.

Так что же такое сервер приложений?

Это сервер который снабжает ваши приложения рядом незаменимых "сервисов". Таких как защита, балансировка нагрузки, поддержка транзакций и т.д. Такого рода сервера в основном используются для приложений на уровне предприятия. По ходу публикаций все станет намного понятнее.

Настройка рабочей среды

1. Ставим последний JDK

2. Скачиваем JBOSS AS (желательно версию 7*)

3. Ставим его в удобную вам директорию
4. В пременные среды добавьте $JAVA_HOME и $JBOSS_HOME указывающие на директории в которых находятся JDK and JBOSS соответственно.

5. Для того чтобы начать разрабатывать приложения вам нужна среда разработки. Можете скачать что вам удобно, но я бы посоветовал Eclipse так как у него идет очень хороша интеграция с Jboss (по средствам Jboss Tools).

6. Скачиваем Jboss Tools.

7. Привинчиваем к Eclipse

Если у вас возникли какие-то вопросы, то обязательно задавайте их в комментариях. Пока что я немного отдохну и чуть позже расскажу как правильно настраивать Eclipse.

С уважением,

NetLink community member

Introduction

2012-04-08T23:20:00.001-07:00

Данный блог создан для начинающих разработчиков и просто интересующихся в сфере разработки. Уроки будут идти по следующим темам: HTML, CSS, Javascript, Java, SEAM, JPA, Prettyfaces, Primefaces, Richfaces, IceFaces, JBOSS AS, Tomcat...

С уважением,

TutsLink