jboss-admin does not quit on Windows 7
by Vimal Kansal
Hi,
I am running AS7 on Windows 7 and having problem in quitting jboss-admin
- it shows me that it is disconnecting from the AS but then it just
hangs i.e I don't get my shell prompt back.
Thx
Vimal
13 years, 7 months
node and operation property constraints description
by Alexey Loubyansky
So, how do you feel about extending property description in the model to
include optional info such as:
- value set, i.e. an enum of allowed values, e.g. for transaction
isolation, etc;
- dependency on another property, e.g. exception-sorter-properties
assumes that exception-sorter-class-name is specified;
- properties choice, e.g. driver-class and driver-name, one excludes the
other;
- property value set restricted by the existing values of some other
properties, e.g. driver-name can take values from the registered jdbc
drivers.
I actually did a simple prototype which includes all of the above except
the last one
https://github.com/aloubyansky/jboss-as/commit/833934db69bec304ff37b29188...
It's obviously not the best way of doing it but just to give an idea.
This will help with tab-completion in cli and perhaps other tools too.
Thanks,
Alexey
13 years, 7 months
Documentation - Naming conventions
by Pete Muir
I've seen various ways of referring to the project which we are documenting. Normally "JBoss Application Server" is used in the introduction to a guide, and then shortened. Some guides use "JBoss Application Server 7". There is also some inconsistency with using "the JBoss Application Server". I think we should pick one of these (my vote is "JBoss Application Server" with no preceding definite article, you would still want to use a definite article when referring to "the application server" - the difference being that we are using a description of the project, not the project name).
The shorted version is then sometimes referred to as "JBoss AS", sometimes as "AS", sometimes as "AS7", sometimes as "AS 7". My pick would be "JBoss AS".
I think it's fairly important we use a single convention so that people get a consistent experience with our docs. What do others think? Misty, what do you use for the enterprise docs - that could be a good convention to adopt (swapping EAP -> AS).
13 years, 7 months
7.0.0.Final release strategy
by Thomas Diesler
Folks,
what's the release strategy? I see the version moved on to 7.0.1. Is
there a 7.0.0.Final branch?
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
13 years, 7 months
module usability issue? or intended?
by Bill Burke
I wanted to add a custom LoginModule. To have the class visible, I had
to add my jars to the picketbox module.
Originally, I tried the intuitive approach (well, intuitive to me), of
creating a new module for my custom jars, and adding a dependency to
these jars within the picketbox module. This did not work. Is it
supposed to? If not, why?
I'm just trying to understand the logic here.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
13 years, 7 months
Recent profile changes
by Heiko Braun
The recently introduced split into "ha", "default" and "web-base" profiles,
excludes a lot of the subsystems (messaging, ws, etc)
Would it make sense to introduce a full blown "all" profile,
that provides all capabilities out of the box?
If not been used it would at least act as a configuration preset for people
that would like to include one of it's subsystems in a profile subset
(i.e. adding ”messaging" to profile "web-base").
Currently it looks like we ship an app server w/o these functionalities.
This is at least what the average user will perceive, IMO.
Ike
13 years, 7 months
Documentation headers
by Kabir Khan
The capitalization of the headers in the docs is a bit arbitrary
Some Places We Do This
Other places use this
This needs to be standardized. Either we choose one of the two options or
h1 + h2: We Use This
h3++: We use this
13 years, 7 months
Documentation - Unsorted removed
by Pete Muir
I have moved any remaining pages which were in the Unsorted bucket to the relevant places, and removed all the empty pages that had been put there by Jim. The majority of these are addressed in the getting started guide, the only missing ones are:
* How do I secure the web console (which is mentioned as a heading in the Admin Guide, but not written up)
* How do tune my instance (which I suspect is the subject of a whole new guide).
This makes the index look a lot tidier :-)
13 years, 7 months
