[JBoss AS7 Development] - JBoss AS7 User Guide
by Jason Greene
Jason Greene [http://community.jboss.org/people/jason.greene] modified the document:
"JBoss AS7 User Guide"
To view the document, visit: http://community.jboss.org/docs/DOC-16068
--------------------------------------------------------------
This is a brief guide intended to help users who wish to experiment with JBoss AS 7 as it undergoes development. Feedback on its content is most appreciated, either via comments on this page, via forum posts in this "JBoss AS7 Development" section of the wiki, or by posts to the https://lists.jboss.org/mailman/listinfo/jboss-development jboss-development mailing list.
AS 7 is currently in "Beta" status, so users should not expect all of the capabilities of more stable AS 5 and 6 releases to be present. Users should also be aware that significant changes may be made from one alpha release to another.
h2. Getting JBoss AS 7
AS 7 is available from the http://www.jboss.org/jbossas/downloads.html jboss.org download page. As in earlier JBoss AS releases, installation consists of unzipping the release distribution.
Users are encouraged to check out the AS 7 source and build it themselves. This is quite quick and painless once git is installed on your system, and getting git set up is also quite easy to do. See the http://community.jboss.org/docs/DOC-15596 Hacking On JBoss AS 7 wiki page for more details on working with the AS 7 source.
h2. Quick Start
Once you have the distribution unzipped, you need to decide whether you want to work in "domain mode" or "standalone mode". See "Domain Mode vs. Standalone Mode" below for more on what those choices mean.
If you want to work in domain mode, open a terminal and cd into the distribution's bin directory, and run the "domain" launch script:
$ cd bin
$ ./domain.sh
On Windows:
> cd bin
> domain.bat
This will launch a total of 5 processes on your system: three JBoss AS server instances; a Domain Controller process that acts as a central management point for all servers that belong to the same "domain"; and a lightweight Process Controller process that is responsible for spawning the other 4 processes and monitoring their lifecycle.
If you want to work in standalone mode, open a terminal and cd into the distribution's bin directory, and run the "standalone" launch script:
$ cd bin
$ ./standalone.sh
On Windows:
> cd bin
> standalone.bat
This will launch a single process on your system, a standalone JBoss AS server instance.
If you have the AS 7 source checked out, there are a number of demos that can be run from the source checkout's demos module. See below for details.
h2. Domain Mode vs. Standalone Mode
One of the primary new features of AS 7 is the ability to manage multiple AS instances from a single control point. A collection of such servers are referred to as members of a "domain", with a single Domain Controller process acting as the management control point. Domains can span multiple physical (or virtual) machines, with all AS instances on a given host under the control of a Host Controller process. The Host Controllers interact with the Domain Controller to control the lifecycle of the AS instances running on that host and to assist the Domain Controller in managing them.
When you launch JBoss AS in "domain mode" (via the domain.sh or domain.bat launch scripts) your intent is to launch a Domain Controller, a Host Controller and usually at least one AS instance.
For more on running servers in domain mode, a roughly 20 minute video is available online (divided in two pieces):
http://www.youtube.com/watch?v=phV3QiKQf2E http://www.youtube.com/watch?v=phV3QiKQf2E
http://www.youtube.com/watch?v=gCeQ2KIO0qc http://www.youtube.com/watch?v=gCeQ2KIO0qc
For many use cases, the centralized managment capability available via domain mode is not necessary. For these use cases, the AS can also be run in "standalone mode". In standalone mode each AS instance is an independent process, much like an AS 3, 4, 5, or 6 instance is. Standalone instances can be launched via the standalone.sh or standalone.bat launch scripts.
If more than one standalone instance is launched and multi-server management is desired, it is the user's responsibility to coordinate management across the servers.
A given server instance cannot be switched between domain mode and standalone mode; i.e. you cannot launch domain.sh, stop the processes, and then launch standalone.sh and expect any relationship between what was running. The configurations are separate. We may in future releases include some tooling to ease the task of translating a given server configuration from domain mode to standalone mode.
h4. Deciding Between Domain Mode and Standalone Mode
Which use cases are appropriate for domain mode and which are appropriate for standalone mode? Domain mode is all about coordinated multi-server management -- with it JBoss AS provides a central point through which users can manage multiple servers, with rich capabilities to keep those servers' configurations consistent and the ability to roll out configuration changes (including deployments) to the servers in a coordinated fashion.
It's important to understand that domain mode and standalone mode are all about how your servers are managed, not what capabilities they have to service end user requests. This distinction is particularly important when it comes to high availability clusters. The current AS 7 beta1 release does not support HA functionality. However, it's important to understand that once HA functionality is added in a later beta, it will be orthogonal to "domain mode" vs. "standalone mode". That is, a group of servers running in standalone mode will be able to be configured to form an HA cluster. The domain and standalone modes determine how the servers are managed, not what capabilities they provide.
So, given all that:
* A single server installation gains nothing from domain mode, so standalone mode is a better choice.
* For multi-server production environments, the choice of domain mode versus standalone mode comes down to whether the user wants to use the centralized management capability domain mode provides. Some enterprises have developed their own sophisticated multi-server management capabilities and are comfortable coordinating changes across a number of independent JBoss AS instances. For these enterprises, a multi-server architecture comprised of individual standalone mode AS instances is a good option.
* Standalone mode is better suited for most development scenarios. In particular, there is no "domain mode" for embedding JBoss AS; e.g. in an Arquillian-based testsuite. Any individual server configuration that can be achieved in domain mode can also be achieved in standalone mode, so even if the application being developed will eventually run in production on a domain mode installation, much (probably most) development can be done using standalone mode.
* Domain mode can be helpful in some advanced development scenarios; i.e. those involving interaction between multiple AS instances. Developers may find that setting up various servers as members of a domain is an efficient way to launch a multi-server cluster.
h2. Contents of the AS 7 Distribution
The AS 7 distribution includes the following directories:
*bin* -- location of the launch scripts
*docs* -- license files, documentation, schemas, examples, etc. The amount of content in this directory will increase as development continues.
*modules* -- AS 7 is based on a modular classloading architecture. The various modules used in the server are stored here. Generally speaking, this is not an area that would be modified by end users.
*domain* -- only relevant when domain mode is used. Configuration files, deployment content, and writeable areas used by the domain mode processes that run off of this installation. See below for further details.
*standalone* -- only relevant when standalone mode is used. Configuration files, deployment content, and writeable areas used by the single standalone server that runs off this installation. See below for further details.
h3. Contents of the "domain" Directory
Only relevant when domain mode is used.
*configuration* -- configuration files for the domain and for the Host Controller and any servers running off of this installation. If we've done our jobs well, these configuration files are the only configuration files end users should need to touch (outside of deployment descriptors in their own application deployments). See below for more on these files.
*content* -- an internal working area for the Host Controller that controls this installation. This is where it internally stores deployment content. This directory is not meant to be manipulated by end users.
*log* -- location where the Process Controller and Host Controller write their log files.
*servers* -- writeable area used by each AS instance. Each AS instance will have its own subdirectory, created when the server is first started. In each server's subdirectory there will be the following subdirectories:
data -- information written by the server that needs to survive a restart of the server
log -- the server's log files
tmp -- location for temporary files written by the server
*system-content* -- an internal working area. Storage for non-end-user deployments; i.e. deployments that the subsystems that comprise a running AS themselves deploy into the runtime as part of the service they provide.
h3. Contents of the "standalone" Directory
Only relevant when standalone mode is used.
*configuration* -- configuration files for the standalone server that runs off of this installation. If we've done our jobs well, these configuration files are the only configuration files end users should need to touch (outside of deployment descriptors in their own application deployments). See below for more on these files.
*data* -- information written by the server that needs to survive a restart of the server
*deployments* -- an area where end user deployment content can be placed if automatic detection and deployment of that content into the server's runtime is desired. The server's management API exposes other means for installing deployment content, and use of that API in preference to the deployments directory is preferred. We realize however, that at this early stage in AS 7's development the tooling around the deployment API is in its infancy, so many users will utilize the deployments directory to deploy content. Note that "domain mode" does not support deploying content based on scanning a filesystem.
*log* -- the server's log files
*tmp* -- location for temporary files written by the server
*system-content* -- an internal working area. Storage for non-end-user deployments; i.e. deployments that the subsystems that comprise a running AS themselves deploy into the runtime as part of the service they provide.
h2. "Domain Mode" Configuration Files
Located in the *domain/configuration* directory.
*domain.xml* -- primary configuration file for the domain. Among other things, includes the configuration of the various "profiles" that AS instances can be configured to run. A profile configuration includes the detailed configuration of the various subsystems that comprise that profile (e.g. an embedded JBoss Web instance is a subsystem; a JBoss TS transaction manager is a subsystem, etc). Includes the definition of groups of sockets that those subsystems may open. And includes definition of "server groups", to which a profile, a group of socket definitions and zero or more deployments are mapped. Each individual server will be mapped (in host.xml, see below) to a server group; the configuration of that server group largely defines the configuration of the individual server.
A domain.xml file must be located in the domain/configuration directory of an installation that's meant to run the Domain Controller. It does not need to be present in installations that are not meant to run a Domain Controller; i.e. those whose Host Controller is configured to contact a remote Domain Controller. The presence of a domain.xml file on such a server does no harm; it will be ignored.
Users are encouraged to have a look at the https://github.com/jbossas/jboss-as/blob/master/domain/src/main/resources... AS 7 configuration schema, starting with the <domain> element, to learn more about configuration of a Domain Controller.
*host.xml* -- configuration file for the Host Controller that runs off of this particular installation. Each installation must have a host.xml file. Contains configuration information that is specific to the particular installation. Primarily:
* the listing of the names of the actual AS server instances that are meant to run off of this installation, along with the server group they belong to.
* configuration of how the Host Controller is to contact the Domain Controller to register itself and access the domain configuration. This may either be configuration of how to find and contact a remote Domain Controller, or a configuration telling the Host Controller to itself act as the Domain Controller.
* configuration of items that are specific to the local physical installation. For example, named interface definitions declared in domain.xml can be mapped to an actual machine-specific IP address in host.xml. Abstract path names in domain.xml can be mapped to actual filesystem paths in host.xml.
Users are encouraged to have a look at the https://github.com/jbossas/jboss-as/blob/master/domain/src/main/resources... AS 7 configuration schema, starting with the <host> element, to learn more about configuration of a Host Controller.
*logging.properties* -- Contains the logging configuration for the Host Controller and Process Controller that run off of this installation. Also defines the initial bootstrap logging configuration for each individual AS instance. This boostrap logging configuration is replaced with the logging configuration specified in the domain.xml file once the server boot has reached the point where that configuration is available.
h2. "Standalone Mode" Configuration Files
Located in the *standalone/configuration* directory.
*standalone.xml* -- primary configuration file for the AS instance. Among other things, includes the configuration of the "profile" that the AS instance is configured to run. A profile configuration includes the detailed configuration of the various subsystems that comprise that profile (e.g. an embedded JBoss Web instance is a subsystem; a JBoss TS transaction manager is a subsystem, etc). Also includes the definition of the sockets that those subsystems may open.
Users are encouraged to have a look at the https://github.com/jbossas/jboss-as/blob/master/domain/src/main/resources... AS 7 configuration schema, starting with the <server> element, to learn more about configuration of a standalone AS instance.
*logging.properties* -- Contains the initial bootstrap logging configuration for the AS instance. This boostrap logging configuration is replaced with the logging configuration specified in the standalone.xml file once the server boot has reached the point where that configuration is available.
h2. General Configuration Concepts
In both Domain Mode and Standalone Mode a number of common configuration concepts apply:
h4. Extensions
An extension is a module that extends the core capabilities of the server. The AS core is very simple and lightweight; most of the capabilities people associate with an application server are provided via extensions. An extension is packaged as a module in the modules folder. The user indicates that they want a particular extension to be available by including an <extension/> element naming its module in the domain.xml or standalone.xml file.
<extensions>
...
<extension module="org.jboss.as.transactions"/>
<extension module="org.jboss.as.web" />
<extension module="org.jboss.as.webservices" />
<extension module="org.jboss.as.weld" />
</extensions>
h4. Paths
A logical name for a filesystem path. The domain.xml, host.xml and standalone.xml configurations all include a section where paths can be declared. Other sections of the configuration can then reference those paths by their logical name, rather than having to include the full details of the path (which may vary on different machines). For example, the logging subsystem configuration includes a reference to the "jboss.server.log.dir" path that points to the server's "log" directory.
<file relative-to="jboss.server.log.dir" path="server.log"/>
The AS automatically provides a number of standard paths without any need for the user to configure them in a configuration file:
* jboss.home - the root directory of the JBoss AS distribution
* user.home - user's home directory
* user.dir - user's current working directory
* java.home - java installation directory
* jboss.server.base.dir - root directory for an individual server instance
* jboss.server.data.dir - directory the server will use for persistent data file storage
* jboss.server.log.dir - directory the server will use for log file storage
* jboss.server.tmp.dir - directory the server will use for temporary file storage
* jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances (domain mode only)
Users can add their own paths or override all except the first 5 of the above by adding a <path/> element to their configuration file.
<path name="example" path="example" relative-to="jboss.server.data.dir"/>
See the XSD for details.
A <path/> element in a domain.xml need not include anything more than the name attribute; i.e. it need not include any information indicating what the actual filesystem path is:
<path name="x"/>
Such a configuration simply says, "There is a path named 'x' that other parts of the domain.xml configuration can reference. The actual filesystem location pointed to by 'x' is host-specific and will be specified in each machine's host.xml file." If this approach is used, there must be a path element in each machine's host.xml that specifies what the actual filesystem path is:
<path name="x" path="/var/x" />
h4. Interfaces
h4.
A logical name for a network interface/IP address/host name to which sockets can be bound. The domain.xml, host.xml and standalone.xml configurations all include a section where interfaces can be declared. Other sections of the configuration can then reference those interfaces by their logical name, rather than having to include the full details of the interface (which may vary on different machines).
An interface configuration includes the logical name of the interface as well as information specifying the criteria to use for resolving the actual physical address to use. The criteria is one of two types: either a single element indicating that the interface should be bound to a wildcard address, or a set of one or more characteristics that an interface or address must have in order to be a valid match.
<interface name="global">
<!-- Use the wildcard address -->
<any-address/>
</interface>
<interface name="external">
<nic name="eth0"/>
</interface>
<interface name="default">
<!-- Match any interface/address on the right subnet if it's
up, supports multicast and isn't point-to-point -->
<subnet-match value="192.168.0.0/16"/>
<up/>
<multicast/>
<not>
<point-to-point/>
</not>
</interface>
<interface name="loopback">
<inet-address value="127.0.0.1"/>
</interface>
See the XSD for full details on the various criteria options.
An <interface/> element in a domain.xml need not include anything more than the name attribute; i.e. it need not include any information indicating what the actual IP address associated with the name is:
<interface name="internal"/>
Such a configuration simply says, "There is an interface named 'internal' that other parts of the domain.xml configuration can reference. The actual IP address pointed to by 'internal' is host-specific and will be specified in each machine's host.xml file." If this approach is used, there must be an interface element in each machine's host.xml that specifies the criteria for determining the IP address:
<interface name="internal">
<nic name="eth1"/>
</interface>
h4. Socket Bindings and Socket Binding Groups
A socket binding is a named configuration for a socket.
The domain.xml and standalone.xml configurations both include a section where named socket configurations can be declared. Other sections of the configuration can then reference those sockets by their logical name, rather than having to include the full details of the socket configuration (which may vary on different machines).
A socket binding includes the following information:
* name -- logical name of the socket configuration that should be used elsewhere in the configuration
* port -- base port to which a socket based on this configuration should be bound. (Note that servers can be configured to override this base value by applying an increment or decrement to all port values. See below for more details.)
* interface (optional) -- logical name (see "Interfaces" above) of the interface to which a socket based on this configuration should be bound
* multicast-address (optional) -- if the socket will be used for multicast, the multicast address to use
* multicast-port (optional) -- if the socket will be used for multicast, the multicast port to use
* fixed-port (optional, defaults to false) -- if true, declares that the value of port should always be used for the socket and should not be overridden
Socket binding configurations are organized inside a <socket-binding-group/> element. That element also includes a default-interface attribute; that interface will be used for any bindings that do not specify their interface attribute.
h4. System Properties
System property values can be set in a number of places in
domain.xml, host.xml and standalone.xml. The values in standalone.xml are set as part of the server boot process. Values in domain.xml and host.xml are applied to servers when they are launched.
h4. Profiles and Subsystems
The most significant part of the configuration in domain.xml and standalone.xml is the configuration of one (in standalone.xml) or more (in domain.xml) "profiles". A profile is a named set of subsystem configurations. A subsystem is an added set of capabilities added to the core server by an extension (see "Extensions" above). A subsystem provides servlet handling capabilities; a subsystem provides an EJB container; a subsystem provides JTA, etc. A profile is a named list of subsystems, along with the details of each subsystem's configuration. A profile with a large number of subsystems results in a server with a large set of capabilities. A profile with a small, focused set of subsystems will have fewer capabilities but a smaller footprint.
The content of an individual profile configuration looks largely the same in domain.xml and standalone.xml. The only difference is standalone.xml is only allowed to have a single profile element (the profile the server will run), while domain.xml can have many profiles, each of which can be mapped to one or more groups of servers. The profile element in domain.xml also supports an <includes profile="another_profile"/> tag which allows configuration reuse whereby several more complex profiles can include the contents of simpler profiles.
The contents of individual subsystem configurations look exactly the same between domain.xml and standalone.xml.
h2. Standalone Mode Configuration Concepts
In addition to the general configuration concepts described above, the following concepts are specific to an AS instance running in standalone mode.
h4. Server Name
The root <server/> element in standalone.xml include a name attribute. If set, the value becomes the name of the server. If not set
If not set, defaults to the runtime value of java.net.InetAddress.getLocalHost().getHostName(). Users are encouraged to use distinct names for all servers in the operational environment. The server name is made available to all services running in the server.
h4. Paths and Interfaces
As mentioned above, domain.xml supports not fully describing a path (by providing the actual filesystem path) or an interface (by providing criteria to determine the IP address to use). This is not supported in standalone.xml.
h4. Socket Binding and Avoiding Port Conflicts
In standalone.xml, only a single <socket-binding-group/> element is allowed.
In standalone.xml, the <socket-binding-group/> element can also include a port-offset attribute. The value of this attribute will be added to the port attribute value for any binding to derive the actual port to use for the socket. Setting the port-offset to a value other than zero allows multiple AS instances with the same socket binding and interface configurations to run on the same machine without having port conflicts.
In domain.xml the <socket-binding-group/> element does not include a port-offset attribute; see "Domain Mode Configuration Concepts" below for more on how an equivalent configuration is done.
h4. Profiles
As noted above, only a single profile element is allowed in standalone.xml.
h4. Deployments
The standalone.xml file includes a section listing the deployment content available for use on the server. Deployment content is made available for use either by uploading it using the AS's management APIs, or by configuring a deployment scanner service and placing the content in the folder scanned by that service (i.e. the deployments/ folder.)
Each deployment element includes the following information:
* name -- Unique identifier of the deployment. Must be unique across all deployments.
* runtime-name -- name by which the deployment should be known within the runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as name, but in some cases users may wish to have two deployments with the same runtime-name may (e.g. two versions of "foo.war") both available in the deployment content repository, in which case the deployments would need to have distinct name values but would have the same runtime-name
* hash -- a hash of the deployment content, created by the server when the content was uploaded. The server uses the hash internally to find content in the repository.
* start -- a boolean flag indicating whether the content is actually deployed into the runtime (and should be automatically deployed when the server starts.)
h2. Domain Mode Configuration Concepts
In addition to the general configuration concepts described above, the following concepts are specific to configuring a set of JBoss AS instances in domain mode.
h4. Domain.xml vs Host.xml
Domain configuration is divided into two portions: a set of configuration elements that is consistent on all hosts across the domain (stored in the domain.xml file on the host that is acting as the Domain Controller), and a set of configuration elements that differs on each host (stored in a host.xml on each host). Most configuration should come from the domain.xml; the host.xml is meant to be limited to details that need to vary from one host to another (e.g. IP addresses, filesystem paths, and, most significantly the names of the servers that should run on each host.
Each host's Host Controller is responsible for launching the servers configured in its host.xml file. To do this the Host Controller gets a copy of the domain-wide configuration from the Domain Controller, extracts the portion of the domain-wide configuration that is relevant to the server (e.g. the details of the profile the server is configured to run), applies host-specific information (e.g. the IP addresses to use for named interfaces), and creates a server-specific configuration. The Host Controller then launches the server process and provides it its configuration. If that server-specific configuration were represented in XML form, it would look the same as a standalone.xml file -- the Host Controller essentially synthesizes a standalone.xml from the relevant domain.xml and host.xml content.
h3. Domain.xml Configuration Concepts
h4. Profiles
As noted above, the domain.xml file can contain multiple profiles. Different servers in the domain can run different profiles.
h4. Paths and Interfaces
As discussed above, path and interface elements in domain.xml can legally include nothing more than the name of the path or interface, in which case each host.xml is responsible for specifying the details of the path or interface.
h4. Deployments
The Domain Controller maintains a repository of deployment content that is available for use in the servers in the domain.
The domain.xml file includes a section listing the deployment content available for use in the domain. Deployment content is made available for use by uploading it using the AS's management APIs.
Each deployment element includes the following information:
* name -- Unique identifier of the deployment. Must be unique across all deployments in the domain.
* runtime-name -- name by which the deployment should be known within the runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as name, but in some cases users may wish to have two deployments with the same runtime-name may (e.g. two versions of "foo.war") both available in the deployment content repository, in which case the deployments would need to have distinct name values but would have the same runtime-name
* hash -- a hash of the deployment content, created by the server when the content was uploaded. The server uses the hash internally to find content in the repository.
Note that the fact that a deployment is listed in the domain-level deployments listing does not mean it will actually be deployed on any servers. It simply means its content is known to the domain and available for use. Deployments are only deployed on servers when they are mapped to server groups (see below).
h4. Server Groups
Besides the general configuration concepts described in the "General Configuration Concepts" section above, the most important element in the domain.xml is the definition of Server Groups. Each AS instance is a member of a server group. (Even if the group only has a single server, the server is still a member of a group.) It is the responsibility of the domain management system to ensure that all servers in a server group have a consistent configuration. They should all be configured with the same profile and they should have the same deployment content deployed.
The domain can have multiple server groups.
An example server group definition is as follows:
<server-group name="main-server-group" profile="default">
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="foo.war_v1" runtime-name="foo.war" hash="ABCDEFG1234567890ABC"/>
<deployment name="bar.ear" runtime-name="bar.ear" hash="1234567890ABCDEFG123"/>
</deployments>
</server-group>
A server-group configuration includes the following required attributes:
* name -- the name of the server group
* profile -- the name of the profile the servers in the group should run
In addition, the following optional elements are available:
* socket-binding-group -- specifies the name of the default socket binding group to use on servers in the group. Can be overridden on a per-server basis in host.xml. If not provided in the server-group element, it must be provided for each server in host,xml.
* deployments -- the deployment content that should be deployed on the servers in the group.
* system-properties -- system properties that should be set on all servers in the group
* jvm -- default jvm settings for all servers in the group. The Host Controller will merge these settings with any provided in host.xml to derive the settings to use to launch the server's JVM. See the "JVMs" section in "Host.xml Configuration Concepts" below.
h3. Host.xml Configuration Concepts
h4.
Paths and Interfaces
Any paths or interfaces declared in domain.xml but not fully specified there need to be fully specified in host.xml. Since filesystem paths and IP addresses often vary from host to host, these details are often provided in eac host's host.xml.
h4. System Properties
System property values can be declared in a top level element in host.xml. Properties declared here will be set on all servers launched on the host.
h4. JVMs
The host.xml file can include one or more named JVM configurations. The configurations will include such details as the location of the JVM binary, heap sizes, environment variables, etc. The individual server configurations can refer to one of these JVM configurations by name and the Host Controller will use the named configuration to launch the server.
Note that JVM configuration details can also come from the server-group element in domain.xml and from the individual server element (see below.) If configured in more than one place, the elements will be merged, with server element values taking priority over server-group values, which in turn take priority over the host-level jvm configuration.
h4. Management Interfaces
The configuration of the connectors the Host Controller exposes to support remote management. TODO details
h4. Domain Controller
Configuration of how the Host Controller should find and communicate with the Domain Controller:
<domain-controller>
<!-- Remote domain controller configuration with a host and port -->
<remote host="192.168.100.1" port="9999"/>
</domain-controller>
TODO details
If this host should act as Domain Controller, this is declared as follows:
<domain-controller>
<local/>
</domain-controller>
h4.
h4. Servers
The most significant configuration item in host.xml is the listing of the servers that should be launched on the host. Each server has its own element:
<servers>
<server name="server-one" group="main-server-group">
<!-- server-one inherits the default socket-group declared in the server-group -->
<jvm name="default" />
</server>
<server name="server-two" group="main-server-group" start="true">
<!-- server-two avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-binding-group ref="standard-sockets" port-offset="150"/>
<jvm name="default">
<heap size="64m" max-size="256m"/>
</jvm>
</server>
<server name="server-three" group="other-server-group" start="false">
<!-- server-three avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-binding-group ref="standard-sockets" port-offset="250"/>
</server>
</servers>
Each server element includes the following required attributes:
* name -- the name of the server. Must be unique across the host.
* group -- the name of the server-group the server is a member of
* start -- (defaults to true) whether the server should be automatically started when the Host Controller starts
In addition, the server element includes the following optional elements:
* socket-binding-group -- the name of the socket binding group to use. Besides the socket binding group name, a port-offset can also be configured. The value of this attribute will be added to the port attribute value for any binding to derive the actual port to use for the socket. Setting the port-offset to a value other than zero allows multiple AS instances with the same socket binding and interface configurations to run on the same machine without having port conflicts.
* paths -- allows specification of paths at the individual server level. Configurations at this level will override any configurations with the same name at the domain or host level.
* interface-specs -- allows specification of interfaces at the individual server level. Configurations at this level will override any configurations with the same name at the domain or host level.
* system-properties -- system properties values specific to this server
* jvm -- jvm configurations for this server
h2.
Available Subsystems
AS 7 is under active development. Not all capabilities present in more mature releases of the AS 5 and 6 series are available in AS 7 yet. Following is a brief listing of the subsystems available in the various AS 7 releases. Items listed below may not be entirely feature complete.
h4. 7.0.0.Beta1
* logging -- configuration of logging appenders, categories, etc
* threads -- thread pool management
* sockets -- socket binding management
* naming -- local JNDI. Note that direct remote access to JNDI is not supported in Alpha1 (see the client.jms demo for an example of a clever hack to get remote access to JNDI via an MBeanServerConnection)
* transactions -- JTA
* jmx -- MBeanServer with remote access capability
* web -- basic servlet and JSP support
* ee - common EE facilities (injection etc)
* ejb3 - EJB3 component implementaton
* jax-rs - RestEasy integration
* messaging -- HornetQ server
* JMS -- JMS queues, topics and connection factories
* JCA connectors
* Datasources
* JCA resource adapter deployments
* osgi -- OSGI bundle deployment
* remoting -- JBoss Remoting 3 connectors
* managed beans -- EE 6 managed bean deployments
* SAR deployments -- both legacy mbean deployments and those based on the JDK 6 ServiceLoader concept. Note that not all legacy sar capabilities are supported
* Filesystem based hot deployment scanning (standalone mode only) -- note that exploded deployments are not currently supported
h2. Demos in the Source Checkout
The source checkout includes a "demos" module that includes a number of demos that can be run from maven. Building the module from the /demos directory will output a usage note that explains how to run the demos:
usage:
[echo] To run an example:
[echo] 1) In a separate console window,start either a standalone JBoss AS instance or a JBoss AS domain
[echo] 2) Run mvn package -Dexample=<example.name> where "exammple.name is the name of the example
[echo]
[echo] Valid example names to run against a standalone JBoss AS instance are
[echo] sar - deploys mbeans packaged in a sar
[echo] managedbean - deploys a managed bean
[echo] serviceloader - deploys a serviceloader style service
[echo] messaging - deploys HornetQ native sender and receiver
[echo] jms - deploys HornetQ JMS sender and receiver
[echo] jms.client - Uses HornetQ JMS API from the client
[echo] rar - deploys a resource adapter
[echo] ds - deploys a test bean for data sources
[echo] war - deploys a simple servlet and connects to it
[echo] client.messaging - creates a HornetQ core queue using the management API
[echo] client.jms - creates a JMS queue using the management API
[echo] web.connector - creates and removes a jboss web connector
[echo]
[echo] Valid example names to run against a JBoss AS domain are
[echo] domain.configs - reads the domain config and any available host controller configs
[echo] domain.ds - deploys deploys a test bean for data sources
[echo] domain.messaging - deploys HornetQ native sender and receiver
[echo] domain.rar - deploys deploys a resource adapter
[echo] domain.servers - shows domain, host controller and server configs, starts/stops servers
The primary point of the demos is to look at the source code and see how they use the AS's management API to deploy content and/or alter the configuration of the running server(s). To see how an example works, look at the relevant demos/src/main/java/org/jboss/as/demos/<example.name>/runner.ExampleRunner.java file.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16068]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 1 month
- 1
- 0
[jBPM Development] - jbpm 3.x to 5 migration path
by Sasi R
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"jbpm 3.x to 5 migration path"
To view the discussion, visit: http://community.jboss.org/message/593800#593800
--------------------------------------------------------------
We have existing jbpm 3.2 project which uses class liek IdentitySession, User, Group for mainitnign users and groups. But soem of the classes are missing in 5 and is there any docuemnt which specifies the recommendations. I saw the project eschabell-jbpmmigration but it doesnt say about that path
Is there any code snippet which implemented the logic around users, groups management in 5.0?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/593800#593800]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
- 2
- 11
[JBoss AS7 Development] - Re: Thoughts on filesystem action driven hot deployment
by Dimitris Andreadis
Dimitris Andreadis [http://community.jboss.org/people/dimitris] created the discussion
"Re: Thoughts on filesystem action driven hot deployment"
To view the discussion, visit: http://community.jboss.org/message/593364#593364
--------------------------------------------------------------
You know, this whole idea with the marker files, I think it's just to complex for a simple deployment. If one is truly interested in deploying in a safe way, they could use the CLI, no?
Or, why not turn the problem upside down?
Treat the deployments directory exactly like in previous jboss versions (i.e. deploy something when is copied, undeploy when is removed) to retain backwards compatibility with user expectation, tools and the like.
In addition, if you want to go for an atomic deployment of XXX (packed or unpacked), create first a marker file XXX.skip, then copy in the deployment (packed or unpacked) and remove the XXX.skip file when done to trigger the deployment. Voila.
To undeploy either remove directly the deployment, or if you fear it cannot be done atomically, create again a XXX.skip, remove the deployment and then remove the XXX.skip file to trigger undeployment.
For a re-deployment just touch the packed file, or the directory in the unpacked case.
This would ensure atomic deployments, while retaining "backwards compatibility" for the ./deploy directory notion.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/593364#593364]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
- 8
- 20
[JBoss AS7 Development] - JBoss AS7 Logging
by Anil Saldhana
Anil Saldhana [http://community.jboss.org/people/anil.saldhana] created the document:
"JBoss AS7 Logging"
To view the document, visit: http://community.jboss.org/docs/DOC-16648
--------------------------------------------------------------
This article describes the logging configuration starting JBoss AS v7.0.0. The article should be updated periodically with any changes that have happened to logging (and note the version where the change occurred).
h2.
h2. Boot Logging
This is the +boot.log+ that you see. Its configuration is in the +logging.properties+.
h2.
h2. Server Logging
The configuration should be done in the +standalone.xml+ for the standalone distribution. Basically the configuration now is done in the domain model. So it is either +domain.xml+ or +standalone.xml+ depending on the type of distribution.
The log output will go into server.log
h2.
h2. Deployment Level Logging
This is when you want to have your own JDK or Log4J logging driven at the deployment level. This feature needs to be implemented by https://issues.jboss.org/browse/JBAS-9084 https://issues.jboss.org/browse/JBAS-9084
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16648]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 1 month
- 1
- 0
[JBoss Tools Development] - JBoss Tools wish list
by Snjezana Peco
Snjezana Peco [http://community.jboss.org/people/snjeza] modified the document:
"JBoss Tools wish list"
To view the document, visit: http://community.jboss.org/docs/DOC-16609
--------------------------------------------------------------
Here is a list of features that we could add to JBoss Tools:
h4. Arquillian
1. creating a wizard that would create a new Arquillian project (maven), add required libraries and a simple test case
2. adding m2eclipse configurator that would add Arquillian capabilities to an existing maven project and when importing a maven projectArquillian capabilities would be a nature that marks a project as an Arquillian project and a builder that validates the Arquillian project ( https://issues.jboss.org/browse/JBIDE-6319 JBIDE-6319 Add Arquillian Capabilities)
3. adding an action that would recognize Arquillian tests (junit or testng) and offer a choice of; deployments that Arquillian supports
https://issues.jboss.org/browse/JBIDE-6317 JBIDE-6317 Run As targets for Arquillian
4. creating new wizards for Arquillian project, test, deployment method ...
https://issues.jboss.org/browse/JBIDE-6318 JBIDE-6318 New Arquillian test wizard
5. creating a view that would show Arquillian projects, test cases, deployment archives, resources, classes
https://issues.jboss.org/browse/JBIDE-6662 JBIDE-6662 View Arquillian DeploymentThe view would analyze Java code and populate deployment methods/archives ... The user would get errors/warnings for missing resources, classes, jars ( https://issues.jboss.org/browse/JBIDE-6568 JBIDE-6568 Give error/warning on use of Class in a TestCase that are not found in the @Deployment).
The user would be able to add/edit a new project, test case, deployment method, missing resources/classes ( https://issues.jboss.org/browse/JBIDE-8553 JBIDE-8553 Generation of Arquillian @Deployment method ) using a context menu.
6. completion proposals in the Java editor for resources/classes in a deployment method
h4. Project examples
1. creating a project examples xsd schema ( https://issues.jboss.org/browse/JBIDE-8514 JBIDE-8514 Create xml schema for project-examples.xml files)
2. adding project examples hosted on git, svn ( https://issues.jboss.org/browse/JBIDE-8452 JBIDE-8452 JBoss Maven Git integration )
3. improving the documentation
h4. JBoss Maven Integration
1. updating to m2e 0.13 ( https://issues.jboss.org/browse/JBIDE-8536 JBIDE-8536 Upgrade JBoss Maven Integration feature to use m2eclipse 0.13.x)
h4. JBoss Portlet integration
1. adding a validator, editor, content assists for the portlet.xml file
2. moving the Seam portlet to a new feature so that the basic/JSF portlet doesn't depend on Seam ( https://issues.jboss.org/browse/JBIDE-7293 JBIDE-7293 Dynamic Web Project isn't created properly when JBoss Portlet Tool installed)
3. creating a portal wizard ( https://issues.jboss.org/browse/JBIDE-4218 JBIDE-4218 Add option to create a JBoss Portal project)
h4. JBoss Runtime Detection
1. adding JDK, WTP runtime recognizers
2. downloading some runtimes automatically ( https://issues.jboss.org/browse/JBIDE-6369 JBIDE-6369 - Should support auto download of new container for Tools)
h4. TPTP Profile on JBoss Server
1. upgrading to http://www.eclipse.org/proposals/tools.rat/ Runtime Analysis Tools (RAT)
https://issues.jboss.org/browse/JBIDE-8495 JBIDE-8495 Evaluate removal of TPTP from JBT 3.3
A Creation Review for the RAT project will conclude on http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=16&year=... Wed, 16 Mar 2011
h4. JBoss BIRT Integration
1. changing BIRT WTP facet so that the BIRT Equinox Platform can be out of the application (out of the WEB-INF directory) That would decrese the size of the BIRT application by more than 30 MB. Besides, BIRT applications would be executed within the same Equinox engine. Currently every BIRT application has its own Equinox platform.
Related to https://issues.jboss.org/browse/JBIDE-4971 JBIDE_4971 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=300924 https://bugs.eclipse.org/bugs/show_bug.cgi?id=300924
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16609]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 1 month
- 1
- 0
[JBoss AS7 Development] - EJB3/JPA 2.0 support for AS7
by Scott Marlow
Scott Marlow [http://community.jboss.org/people/smarlow] modified the document:
"EJB3/JPA 2.0 support for AS7"
To view the document, visit: http://community.jboss.org/docs/DOC-16271
--------------------------------------------------------------
This is about the AS7 JPA layer and related concerns. Its a rough draft, mostly points copied from the JPA 2.0 spec.
1. Container-managed persistence context
1. Transaction scope (JPA 7.6.1)
1. Transaction active invocation
1. Persistence context is created if none already associated with transaction
2. Created persistence context ends when transaction ends
3. An extended persistence context can also be used, which survives when transaction ends.
4. Managed entities are detached at transaction end time.
2. No transaction invocation
1. Managed entities are detached at end of EntityManager call.
2. Extended scope (JPA 7.6.2)
1. Only supported for stateful session beans.
2. Entity modifications can be made outside of a transaction and are applied on the next joined transaction (anywhere on the cluster).
3. Extended persistence context (XPC) is created when stateful bean that depends on a XPC is created.
4. Managed entities continue to be managed at transaction commit time.
5. Managed entities are detached at transaction rollback time.
6. XPC is closed when dependent session bean(s) are closed (via @remove method).
7. Inheritance
1. Stateful beans that create other (local) stateful beans, share the same XPC.
3. Persistence context propagation (JPA 7.6.3)
1. A persistence context will be propagated to multiple entity managers (instances) within the same local transaction.
2. Remote invocations do not propagate the persistence context.
4. Persistence context propagation requirements for component invocations (JPA 7.6.3.1)
1. no propagation if component is invoked without a JTA transaction or without the JTA transaction propagating:
1. Transaction scoped entity manager used within the invoked component, will create a new persistence context.
2. Extended scoped entity manager used within the invoked component, will use the XPC already bound to the (invoked stateful) bean.
3. If the entity manager is invoked within a JTA transaction, the persistence context is bound to the JTA transaction.
2. If a component is invoked and the JTA transaction is propagated into the component:
1. If (SFSB) component has a XPC and the transaction already has a different persistence context associated with it, an EJBException is thrown by the container.
2. If a persistence context is bound to the JTA transaction, it is propagated into any entity managers used in the invocation.
2. Container requirements review
1. Application-managed persistence context (JPA 7.8.1)
1. Container needs to inject entity manager factory into jndi for application use.
2. Must use PersistenceProvider.createContainerEntityManagerFactory method for 3^rd^ party support. Internal APIs are fine for our persistence provider.
3. Must use EntityManagerFactory.close method to close the entity manager factory prior to shutdown (again for 3^rd^ party support).
2. Container-managed persistence context (JPA 7.9.1)
1. For 3^rd^ party support, use EntityManagerFactory.createEntityManager . Consider using for our persistence provider as well.
2. May pass (PersistenceProperty (http://download.oracle.com/javaee/6/api/javax/persistence/PersistenceProp... PersistenceContext.properties to EntityManagerFactory.createEntityManager(Map).
3. Container EM wrapper could implement some EntityManager.unwrap(Class<T> cls) calls but should default to underlying EM for unhandled classes.
4. If invoked without a JTA transaction and a transaction scoped persistence context is used, will throw TransactionRequiredException for any calls to entity manager remove/merge/persist/refresh.
3. Deployment
1. Extract persistence metadata from persistence.xml
2. Determine the PersistenceProvider classname for each persistence unit (PU). The default class is currently org.hibernate.ejb.HibernatePersistence.
3. Invoke the PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) to create the EMF that will be used to create all EntityManager's for the PU. The properties read from the PU are passed as the second parameter.
4. Also pass the “javax.persistence.validation.factory ” property if validation mode is not set to NONE. The validator factory value appears to be org.hibernate.validator.engine.ValidatorFactoryImpl. Consult ValidatorFactoryProvider which is currently used to bootstrap the validator factory in AS6.
5. The PU classes shouldn't be loaded until after the EMF is created.
6. The EntityManagerFactory is closed at undeploy time, which also closes all EntityManager's opened by each factory.
7. Switchboard changes for PU + PC???
1. Determine the available persistence providers following JPA 9.3 1. http://download.oracle.com/javaee/6/api/javax/persistence/spi/Persistence... PersistenceProviderResolver
2. http://download.oracle.com/javaee/6/api/javax/persistence/spi/Persistence... PersistenceProviderResolverHolder
4. Clustering
1. Determine impact on http://community.jboss.org/docs/DOC-13822 http://community.jboss.org/wiki/OptimizingentityandXPCreplication which may need to be tweaked for clustering other persistence providers. Judging by the jira status, this optimization is not in place yet (although Hibernate persistence provider HHH-2762 is done).
2. Determine impact on http://community.jboss.org/docs/DOC-9565 http://community.jboss.org/wiki/DevEJB3NewSFSBCache (consider support for other persistence providers).
3. Other changes?
5. Weld integration (JpaInjectionServices implementation is wired in at boot time).
6. Determine Hibernate release to target integration with (Hibernate 4.0).
7. EJB Container interaction
8. Desires1. Maintainable code (a ten minute fix will take ten minutes :)
2. Would like to do a better job of showing what is going on at the EM level (e.g. logging the EM units of work grouped by transaction).
3. Consider any EM (container) extensions that make it easier to measure performance (perhaps based on Hibernate statistics). Its always nice to see how long each transaction took and the units of work within the transaction. It would be nice if we could do this with any persistence provider (for performance comparison).
4. Deal with the Hibernate persistence provider via the same way as we would interact with other persistence providers (via PersistenceProvider mentioned above).
5. It should be easy to switch to a new persistence provider.
6. If an application bundles a persistence provider that is referenced from their persistence unit(s), use the bundled persistence provider (even if its a different version of a JPA 2.0 provider that is also available to all applications). This should handle bundling a different version of Hibernate.
7. Peace.
9. Questions1. The JPA specification section 7.9.1 (Container Responsibilities) implies that only one (container managed) entity manager will be associated with the JTA transaction. However, what if someone injects multiple persistence contexts (different persistent units) in separate entity managers for the same bean. Should that be considered an application error or allowed behaviour (e.g. each separate entity manager is joined to the JTA transaction). *ANSWER: we will allow it and design for it.*
2. For a few different cases, we will need to know which EntityManager was injected into a component. One such case is for XPC inheritance. For example, SFSB1 (with extended persistence context) gets injected into a web component and SFSB2 (with extended persistence context) gets injected into SFSB1. SFSB2 should inherit the XPC from SFSB1. Open question is how we want to maintain the bookkeeping for this. The JPA layer could expose a SPI like BeanToEntityManager{ List<EntityManager> getEntityManagers(); } that can be passed in on other SPI calls (basically depending on the EJB container to track injected EntityMangers via other magic). Another solution would be to track the mapping in the JPA layer (might be a pretty big map with a lot of weak references that need to be considerate of GC/undeploy concerns). Or perhaps there will some other solution that will appear for this. :)
3. What about injecting a Hibernate session or session factory as mentioned http://bill.burkecentral.com/2007/07/06/co-existence-with-hibernate-jpa-a... here and http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/hiberna... here. Do we want to carry this into AS7? Is there another way to do this that we would want to implement for AS7? [Emmanuel] I think this is valuable and quite natural. An alternative approach would be to let all injection logic be handle by Seam 3 which does Session/SessionFactory injection already (it also inject FullTextEntityManager and FullTextSession form Hibernate Search for that matter).
4. Should the jboss-jpa project continue to have its own release cycle or should it live in the AS7 source repo? If anything outside AS7 wants to consume the JPA integration project, then jboss-jpa will need to have its own release cycle. One obvious case is the EJB container, if that continues lives in its own project, jboss-jpa will have to follow suit. I'm not aware of any other projects that desire that.
5. For the JPA EE container integration, should we integrate with a component level invocation context or purely with the containers directly? At this point, I'm assuming direct container integration but we might be able to refactor some of that to be more generic. This will make more sense soon. http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/entityc... :)
6. http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/entityc... Keep support for jboss.entity.manager.* properties? How about securing entity beans from same doc (4.5)?
7. What about existing code that might attempt casting a javax.persistence.Query to a Hibernate QueryImpl class (described here (http://http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/....
Illustration of how a stateful session bean (SFSB) named SFSB_XPC1 interacts with a stateless session bean (SLSB) named SLSB_PC2. Note that the extended persistence context (XPC) is injected into SFSB_XPC1 at bean creation time. Also note that the SFSB_XPC1 persistence context is bound to the JTA transaction and will be injected into the SLSB_PC2 by the EJB container as part of each invocation. The XPC1 will retain changes made by each invocation to SLSB_PC2 until the transaction commits.
|| *Action* || *Transaction* || *PersistenceContext
* ||
| SFSB_XPC1 created |
| XPC1 injected into SFSB_XPC1 |
| SFSB_XPC1.updateInventory | T1 started | XPC1 bound to T1 |
| SFSB_XPC1 calls SLSB_PC2 | T1 |
|
| SLSB_PC2.dowork | T1 | XPC1 injected into SLSB_PC2 EM instance |
| SLSB_PC2 loads entity item1 | T1 | item1 is loaded |
| SLSB_PC2 persists new entity order1 | T1 | order1 will be saved at commit time |
| SLSB_PC2 returns | T1 |
|
| SFSB_XPC1 calls SLB_PC2 again | T1 |
|
| SLSB_PC2.morework | T1 | XPC1 injected into SLSB_PC2 EM instance |
| SLSB_PC2 loads entity order1 | T1 | order1 is returned from XPC1 |
| SLSB_PC2 calls order1.increase(4) | T1 | change made in XPC1 held entity |
| SLSB_PC2 returns | T1 |
|
| SFSB_XPC1 returns | T1 commit | XPC1 changes are saved, item1 + order1 remain in XPC1 |
| SFSB_XPC1 removed |
| XPC1 is closed |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16271]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 1 month
- 1
- 0
[JBoss AS7 Development] - Re: Thoughts on filesystem action driven hot deployment
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion
"Re: Thoughts on filesystem action driven hot deployment"
To view the discussion, visit: http://community.jboss.org/message/594274#594274
--------------------------------------------------------------
> Stan Silvert wrote:
>
> > Brian Stansberry wrote:
> >
> > AIUI, the bug is Stan mistyped the file name. :-) The question is whether deleting the wrnog-spelling.dodeploy is the right thing to do. The scanner deletes extraneous marker files as a matter of housekeeping. That behavior could be removed, but I'd argue that in this case, it's disconcerting but somewhat helpful. The file is gone, forcing the user to try again and maybe get it right.
>
> At the risk of owing David a beer (you'll have to come to ATL to get it!), let me point something out. If I mistype the long file name I want to edit it, not type the whole thing in again. I can't edit the file name if it is deleted. If I did this from the command line I could just scroll through my previous commands, but from Explorer I'm screwed.
>
> Stan
Looking at the code I don't see how leaving around marker files that don't match content causes any difficulties in the code, so I'll remove the bit that deletes them.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/594274#594274]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
- 1
- 0
[JBoss Web Development] - Struts2 and ... what forward?
by gienasek
gienasek [http://community.jboss.org/people/gienasek] created the discussion
"Struts2 and ... what forward?"
To view the discussion, visit: http://community.jboss.org/message/594261#594261
--------------------------------------------------------------
Hello,
We are starting new project - the portal with a large number of users simultaneously logged in 17000.
Portal will be processed and presented mainly XML documents.
50% of the logic will be available on the outside through the ESB.
Target solution (portal) will be run on JBoss Application Platform.
Technology (portal):
1. Front Controller - Struts 2
2. Business logic:
a) *EJB 3 (local SLSB) or Spring*
b) Business Delegate Pattern (access ESB)
3) ORM JPA
Please help in the selection in item 2a on the above assumptions (EJB 3 or Spring).
I would also mention that the *performance* is crucial.
Thanks in advance
gienas
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/594261#594261]
Start a new discussion in JBoss Web Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
- 1
- 0
[JBoss Web Services Development] - How to return the arraylist having byte as value
by Sudhir Kumar Jha
Sudhir Kumar Jha [http://community.jboss.org/people/sudhirjha] created the discussion
"How to return the arraylist having byte as value"
To view the discussion, visit: http://community.jboss.org/message/594209#594209
--------------------------------------------------------------
Hello All,
I was trying to write a web service programme in which i suppose to return the array list having value as byte in it to the client.
But as of now i don't know any feasible solution for the same.
(More Info : well i was taking the image from Sybase db which is indeed stored as byte only. and i need to return this value to the client.)
Can anyone help me regarding this.
Best Regards,
Sudhir
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/594209#594209]
Start a new discussion in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
- 1
- 0
[JBoss AS7 Development] - EJB3/JPA 2.0 support for AS7
by Scott Marlow
Scott Marlow [http://community.jboss.org/people/smarlow] modified the document:
"EJB3/JPA 2.0 support for AS7"
To view the document, visit: http://community.jboss.org/docs/DOC-16271
--------------------------------------------------------------
This is about the AS7 JPA layer and related concerns. Its a rough draft, mostly points copied from the JPA 2.0 spec.
1. Container-managed persistence context
1. Transaction scope (JPA 7.6.1)
1. Transaction active invocation
1. Persistence context is created if none already associated with transaction
2. Created persistence context ends when transaction ends
3. An extended persistence context can also be used, which survives when transaction ends.
4. Managed entities are detached at transaction end time.
2. No transaction invocation
1. Managed entities are detached at end of bean method call EntityManager call.
2. Extended scope (JPA 7.6.2)
1. Only supported for stateful session beans.
2. Entity modifications can be made outside of a transaction and are applied on the next joined transaction (anywhere on the cluster).
3. Extended persistence context (XPC) is created when stateful bean that depends on a XPC is created.
4. Managed entities continue to be managed at transaction commit time.
5. Managed entities are detached at transaction rollback time.
6. XPC is closed when dependent session bean(s) are closed (via @remove method).
7. Inheritance
1. Stateful beans that create other (local) stateful beans, share the same XPC.
3. Persistence context propagation (JPA 7.6.3)
1. A persistence context will be propagated to multiple entity managers (instances) within the same local transaction.
2. Remote invocations do not propagate the persistence context.
4. Persistence context propagation requirements for component invocations (JPA 7.6.3.1)
1. no propagation if component is invoked without a JTA transaction or without the JTA transaction propagating:
1. Transaction scoped entity manager used within the invoked component, will create a new persistence context.
2. Extended scoped entity manager used within the invoked component, will use the XPC already bound to the (invoked stateful) bean.
3. If the entity manager is invoked within a JTA transaction, the persistence context is bound to the JTA transaction.
2. If a component is invoked and the JTA transaction is propagated into the component:
1. If (SFSB) component has a XPC and the transaction already has a different persistence context associated with it, an EJBException is thrown by the container.
2. If a persistence context is bound to the JTA transaction, it is propagated into any entity managers used in the invocation.
2. Container requirements review
1. Application-managed persistence context (JPA 7.8.1)
1. Container needs to inject entity manager factory into jndi for application use.
2. Must use PersistenceProvider.createContainerEntityManagerFactory method for 3^rd^ party support. Internal APIs are fine for our persistence provider.
3. Must use EntityManagerFactory.close method to close the entity manager factory prior to shutdown (again for 3^rd^ party support).
2. Container-managed persistence context (JPA 7.9.1)
1. For 3^rd^ party support, use EntityManagerFactory.createEntityManager . Consider using for our persistence provider as well.
2. May pass (PersistenceProperty (http://download.oracle.com/javaee/6/api/javax/persistence/PersistenceProp... PersistenceContext.properties to EntityManagerFactory.createEntityManager(Map).
3. Container EM wrapper could implement some EntityManager.unwrap(Class<T> cls) calls but should default to underlying EM for unhandled classes.
4. If invoked without a JTA transaction and a transaction scoped persistence context is used, will throw TransactionRequiredException for any calls to entity manager remove/merge/persist/refresh.
3. Deployment
1. Extract persistence metadata from persistence.xml
2. Determine the PersistenceProvider classname for each persistence unit (PU). The default class is currently org.hibernate.ejb.HibernatePersistence.
3. Invoke the PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) to create the EMF that will be used to create all EntityManager's for the PU. The properties read from the PU are passed as the second parameter.
4. Also pass the “javax.persistence.validation.factory ” property if validation mode is not set to NONE. The validator factory value appears to be org.hibernate.validator.engine.ValidatorFactoryImpl. Consult ValidatorFactoryProvider which is currently used to bootstrap the validator factory in AS6.
5. The PU classes shouldn't be loaded until after the EMF is created.
6. The EntityManagerFactory is closed at undeploy time, which also closes all EntityManager's opened by each factory.
7. Switchboard changes for PU + PC???
1. Determine the available persistence providers following JPA 9.3 1. http://download.oracle.com/javaee/6/api/javax/persistence/spi/Persistence... PersistenceProviderResolver
2. http://download.oracle.com/javaee/6/api/javax/persistence/spi/Persistence... PersistenceProviderResolverHolder
4. Clustering
1. Determine impact on http://community.jboss.org/docs/DOC-13822 http://community.jboss.org/wiki/OptimizingentityandXPCreplication which may need to be tweaked for clustering other persistence providers. Judging by the jira status, this optimization is not in place yet (although Hibernate persistence provider HHH-2762 is done).
2. Determine impact on http://community.jboss.org/docs/DOC-9565 http://community.jboss.org/wiki/DevEJB3NewSFSBCache (consider support for other persistence providers).
3. Other changes?
5. Weld integration (JpaInjectionServices implementation is wired in at boot time).
6. Determine Hibernate release to target integration with (Hibernate 4.0).
7. EJB Container interaction
8. Desires1. Maintainable code (a ten minute fix will take ten minutes :)
2. Would like to do a better job of showing what is going on at the EM level (e.g. logging the EM units of work grouped by transaction).
3. Consider any EM (container) extensions that make it easier to measure performance (perhaps based on Hibernate statistics). Its always nice to see how long each transaction took and the units of work within the transaction. It would be nice if we could do this with any persistence provider (for performance comparison).
4. Deal with the Hibernate persistence provider via the same way as we would interact with other persistence providers (via PersistenceProvider mentioned above).
5. It should be easy to switch to a new persistence provider.
6. If an application bundles a persistence provider that is referenced from their persistence unit(s), use the bundled persistence provider (even if its a different version of a JPA 2.0 provider that is also available to all applications). This should handle bundling a different version of Hibernate.
7. Peace.
9. Questions1. The JPA specification section 7.9.1 (Container Responsibilities) implies that only one (container managed) entity manager will be associated with the JTA transaction. However, what if someone injects multiple persistence contexts (different persistent units) in separate entity managers for the same bean. Should that be considered an application error or allowed behaviour (e.g. each separate entity manager is joined to the JTA transaction). *ANSWER: we will allow it and design for it.*
2. For a few different cases, we will need to know which EntityManager was injected into a component. One such case is for XPC inheritance. For example, SFSB1 (with extended persistence context) gets injected into a web component and SFSB2 (with extended persistence context) gets injected into SFSB1. SFSB2 should inherit the XPC from SFSB1. Open question is how we want to maintain the bookkeeping for this. The JPA layer could expose a SPI like BeanToEntityManager{ List<EntityManager> getEntityManagers(); } that can be passed in on other SPI calls (basically depending on the EJB container to track injected EntityMangers via other magic). Another solution would be to track the mapping in the JPA layer (might be a pretty big map with a lot of weak references that need to be considerate of GC/undeploy concerns). Or perhaps there will some other solution that will appear for this. :)
3. What about injecting a Hibernate session or session factory as mentioned http://bill.burkecentral.com/2007/07/06/co-existence-with-hibernate-jpa-a... here and http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/hiberna... here. Do we want to carry this into AS7? Is there another way to do this that we would want to implement for AS7? [Emmanuel] I think this is valuable and quite natural. An alternative approach would be to let all injection logic be handle by Seam 3 which does Session/SessionFactory injection already (it also inject FullTextEntityManager and FullTextSession form Hibernate Search for that matter).
4. Should the jboss-jpa project continue to have its own release cycle or should it live in the AS7 source repo? If anything outside AS7 wants to consume the JPA integration project, then jboss-jpa will need to have its own release cycle. One obvious case is the EJB container, if that continues lives in its own project, jboss-jpa will have to follow suit. I'm not aware of any other projects that desire that.
5. For the JPA EE container integration, should we integrate with a component level invocation context or purely with the containers directly? At this point, I'm assuming direct container integration but we might be able to refactor some of that to be more generic. This will make more sense soon. http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/entityc... :)
6. http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/entityc... Keep support for jboss.entity.manager.* properties? How about securing entity beans from same doc (4.5)?
7. What about existing code that might attempt casting a javax.persistence.Query to a Hibernate QueryImpl class (described here (http://http://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/....
Illustration of how a stateful session bean (SFSB) named SFSB_XPC1 interacts with a stateless session bean (SLSB) named SLSB_PC2. Note that the extended persistence context (XPC) is injected into SFSB_XPC1 at bean creation time. Also note that the SFSB_XPC1 persistence context is bound to the JTA transaction and will be injected into the SLSB_PC2 by the EJB container as part of each invocation. The XPC1 will retain changes made by each invocation to SLSB_PC2 until the transaction commits.
|| *Action* || *Transaction* || *PersistenceContext
* ||
| SFSB_XPC1 created |
| XPC1 injected into SFSB_XPC1 |
| SFSB_XPC1.updateInventory | T1 started | XPC1 bound to T1 |
| SFSB_XPC1 calls SLSB_PC2 | T1 |
|
| SLSB_PC2.dowork | T1 | XPC1 injected into SLSB_PC2 EM instance |
| SLSB_PC2 loads entity item1 | T1 | item1 is loaded |
| SLSB_PC2 persists new entity order1 | T1 | order1 will be saved at commit time |
| SLSB_PC2 returns | T1 |
|
| SFSB_XPC1 calls SLB_PC2 again | T1 |
|
| SLSB_PC2.morework | T1 | XPC1 injected into SLSB_PC2 EM instance |
| SLSB_PC2 loads entity order1 | T1 | order1 is returned from XPC1 |
| SLSB_PC2 calls order1.increase(4) | T1 | change made in XPC1 held entity |
| SLSB_PC2 returns | T1 |
|
| SFSB_XPC1 returns | T1 commit | XPC1 changes are saved, item1 + order1 remain in XPC1 |
| SFSB_XPC1 removed |
| XPC1 is closed |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16271]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 1 month
- 1
- 0