From varunaseneviratna at gmail.com  Sat Jan  4 09:28:23 2014
From: varunaseneviratna at gmail.com (Varuna Seneviratna)
Date: Sat, 4 Jan 2014 19:58:23 +0530
Subject: [jboss-as7-dev] what is the JBoss AS version for learning
	Enterprise JavaBeans 3.1
Message-ID: <CAKW-c0zOu-mt_n+siovSamZJJkOXNXrnzcpOKtQoRV-bS2+b+w@mail.gmail.com>

What is the JBoss Application Server version that comply with Enterprise
JavaBeans 3.1 and How Do I find that out? I bought "Enterprise JavaBeans
3.1" by Andrew Rubinger and I want to use JBoss AS to run the examples in
it so for that which version of JBoss AS is appropriate



Thanks Varuna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140104/5f25de5d/attachment.html 

From cfang at redhat.com  Sun Jan  5 18:32:16 2014
From: cfang at redhat.com (Cheng Fang)
Date: Sun, 05 Jan 2014 18:32:16 -0500
Subject: [jboss-as7-dev] what is the JBoss AS version for learning
 Enterprise JavaBeans 3.1
In-Reply-To: <CAKW-c0zOu-mt_n+siovSamZJJkOXNXrnzcpOKtQoRV-bS2+b+w@mail.gmail.com>
References: <CAKW-c0zOu-mt_n+siovSamZJJkOXNXrnzcpOKtQoRV-bS2+b+w@mail.gmail.com>
Message-ID: <52C9EB80.2080904@redhat.com>

That will be JBoss AS 7.x, which implements Java EE 6 (EJB 3.1 is part 
of Java EE 6).  You may also want to try the newer version, WildFly 8.0, 
which implements Java EE 7 and thus EJB 3.2.

http://wildfly.org/

On 1/4/14, 9:28 AM, Varuna Seneviratna wrote:
>
> What is the JBoss Application Server version that comply with 
> Enterprise JavaBeans 3.1 and How Do I find that out? I bought 
> "Enterprise JavaBeans 3.1" by Andrew Rubinger and I want to use JBoss 
> AS to run the examples in it so for that which version of JBoss AS is 
> appropriate
>
> Thanks Varuna
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140105/27e6b12e/attachment.html 

From bgeorges at redhat.com  Sun Jan  5 18:48:08 2014
From: bgeorges at redhat.com (Bruno Georges)
Date: Mon, 6 Jan 2014 12:48:08 +1300
Subject: [jboss-as7-dev] what is the JBoss AS version for learning
	Enterprise JavaBeans 3.1
In-Reply-To: <52C9EB80.2080904@redhat.com>
References: <CAKW-c0zOu-mt_n+siovSamZJJkOXNXrnzcpOKtQoRV-bS2+b+w@mail.gmail.com>
	<52C9EB80.2080904@redhat.com>
Message-ID: <6F7EF2C7-3FCF-4416-A92D-E6DA85A354A4@redhat.com>

+1
In addition to that, the app server comes with a set of quickstarts that not only help you get going with common use cases, but they also allow you to explores the EE APIs such as EJB.
http://www.jboss.org/developer/quickstarts.html
As Cheng pointed, WF 8 is using EJB3.2, you can get it here: http://wildfly.org/downloads/
Both the app server binaries and the quick starts source code are available there.

With respect to tooling, you can download our eclipse based JBoss Developer Studio which includes WTP for our app servers along with projects templates, etc...
Latest version is 7.1 : https://devstudio.jboss.com/earlyaccess/7.1.0.GA.html


?
Bruno

On 6/01/2014, at 12:32 pm, Cheng Fang <cfang at redhat.com> wrote:

> That will be JBoss AS 7.x, which implements Java EE 6 (EJB 3.1 is part of Java EE 6).  You may also want to try the newer version, WildFly 8.0, which implements Java EE 7 and thus EJB 3.2.
> 
> http://wildfly.org/
> 
> On 1/4/14, 9:28 AM, Varuna Seneviratna wrote:
>> What is the JBoss Application Server version that comply with Enterprise JavaBeans 3.1 and How Do I find that out? I bought "Enterprise JavaBeans 3.1" by Andrew Rubinger and I want to use JBoss AS to run the examples in it so for that which version of JBoss AS is appropriate
>> 
>>  
>> Thanks Varuna
>> 
>> 
>> 
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140106/ba7b78b2/attachment.html 

From sgilda at redhat.com  Mon Jan  6 07:59:12 2014
From: sgilda at redhat.com (Sande Gilda)
Date: Mon, 06 Jan 2014 07:59:12 -0500
Subject: [jboss-as7-dev] what is the JBoss AS version for learning
 Enterprise JavaBeans 3.1
In-Reply-To: <6F7EF2C7-3FCF-4416-A92D-E6DA85A354A4@redhat.com>
References: <CAKW-c0zOu-mt_n+siovSamZJJkOXNXrnzcpOKtQoRV-bS2+b+w@mail.gmail.com>	<52C9EB80.2080904@redhat.com>
	<6F7EF2C7-3FCF-4416-A92D-E6DA85A354A4@redhat.com>
Message-ID: <52CAA8A0.7070605@redhat.com>

A more complete and updated list of quickstarts can be found here: 
http://www.jboss.org/jdf/quickstarts/get-started/

Ray, the list of quickstarts in the developer site listed below is 
incomplete and the link to the 'cmt' quickstart is incorrect. Would you 
like me to enter a JIRA?

On 01/05/2014 06:48 PM, Bruno Georges wrote:
> +1
> In addition to that, the app server comes with a set of quickstarts 
> that not only help you get going with common use cases, but they also 
> allow you to explores the EE APIs such as EJB.
> http://www.jboss.org/developer/quickstarts.html
> As Cheng pointed, WF 8 is using EJB3.2, you can get it here: 
> http://wildfly.org/downloads/
> Both the app server binaries and the quick starts source code are 
> available there.
>
> With respect to tooling, you can download our eclipse based JBoss 
> Developer Studio which includes WTP for our app servers along with 
> projects templates, etc...
> Latest version is 7.1 : 
> https://devstudio.jboss.com/earlyaccess/7.1.0.GA.html
>
>
> ---
> Bruno
>
> On 6/01/2014, at 12:32 pm, Cheng Fang <cfang at redhat.com 
> <mailto:cfang at redhat.com>> wrote:
>
>> That will be JBoss AS 7.x, which implements Java EE 6 (EJB 3.1 is 
>> part of Java EE 6).  You may also want to try the newer version, 
>> WildFly 8.0, which implements Java EE 7 and thus EJB 3.2.
>>
>> http://wildfly.org/
>>
>> On 1/4/14, 9:28 AM, Varuna Seneviratna wrote:
>>>
>>> What is the JBoss Application Server version that comply with 
>>> Enterprise JavaBeans 3.1 and How Do I find that out? I bought 
>>> "Enterprise JavaBeans 3.1" by Andrew Rubinger and I want to use 
>>> JBoss AS to run the examples in it so for that which version of 
>>> JBoss AS is appropriate
>>>
>>>
>>> Thanks Varuna
>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org <mailto:jboss-as7-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140106/2925f169/attachment-0001.html 

From manderse at redhat.com  Thu Jan  9 12:05:18 2014
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 09 Jan 2014 18:05:18 +0100
Subject: [jboss-as7-dev] cli variables
In-Reply-To: <529C93FC.5050407@redhat.com>
References: <529C93FC.5050407@redhat.com>
Message-ID: <CC6B23FA-051D-4D61-AF48-2BD6B316EC57@redhat.com>

Remind me why a new syntax need to be introduced besides ${xxx} (and if 
we support standalone.xml property support ${xxx:fallbackvalue}) ?

Why not just treat these as properties?

/max

On 2 Dec 2013, at 15:06, Alexey Loubyansky wrote:

> There is this issue to provide CLI preferences
> https://issues.jboss.org/browse/WFLY-1063. Here I'd like to address
> mainly this part
>
> "prod-db = /subsystem=jadada/database=jadada/
> so you could call prod-db:read-resource"
>
> I'd like to get some opinion on the way it's gonna be implemented (and
> what I've done so far on a local branch).
>
> So, to address that I introduced variables. A variable starts with a 
> $,
> e.g. $prod_db. (Using simply prod_db is not a good idea since it might
> conflict with actual parts of the paths, names, etc)
>
> Variables can be introduced with
>
> [disconnected /] set 
> prod_db=/subsystem=datasources/data-source=ExampleDS
>
> Read with
>
> [standalone at localhost:9990 /] echo prod_db
> /subsystem=datasources/data-source=ExampleDS
>
> And unset with
>
> [standalone at localhost:9990 /] unset prod_db
>
> 'echo' without parameters will list all the variables and their 
> values,
> 'set prod_db=' will have the same effect as 'unset prod_db',
> set/echo/unset will work with and w/o '$' prefix, tab-completion works
> everywhere.
>
> The variables may appear in:
>
> - operation request addresses, e.g. 
> $prod_db/statistics=jdbc:read-resource;
> - operation names, e.g. $prod_db:$op(include-runtime=true);
> - operation parameter names and values, e.g.
> $prod_db:$op($param=$param_value);
> - the same for commands.
>
> Tab-completion helps complete the names as long as you type in '$' and
> then the rest of the line after the variable as usual.
>
> Variables added during the session are not persisted anywhere. But 
> I've
> added .jbossclirc file. This file can be located in the current
> directory, wildfly home bin directory or specified with a system
> property. The content of the file is usual CLI commands and/or
> operations. So, the variables could be initialized there. This file, 
> if
> located, will be executed before the CLI session (interactive or not)
> starts (but also after the system properties specified with 
> --properties
> are set).
>
> As a side effect, '$' is now a special character and will have to be
> escaped. Otherwise the CLI might complain about an unresolved 
> variable.
> So, this could potentially cause problems for existing scripts using 
> $.
>
> Note, most of this replacement stuff can already be done with system
> properties using ${xxx} format (and btw scripts using '$' as in 
> '${xxx}'
> won't be affected, of course).
>
> And for now I've made variable names follow the rules for Java 
> identifiers.
>
> Any remarks, objections or suggestions?
>
> Thanks,
> Alexey
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev