Thoughts on i18n
by Heiko Braun
I am currently going through the console, preparing it for i18n.
Basically making sure everything is properly placed into bundles that can be translated.
There is one thing I need your feedback on:
How are we going to treat strings that reflect technical terms?
I.e. a log handler has an editable field name (speaking of the UI here) called "Auto Flush".
To me this represent a technical term that corresponds with other places like the XML schema, the CLI and the actual XML configuration files. As such, I objecting to translate those. "Log Level" is another good example.
Now, to many native english speaking people, this might not be obvious, but once you start translating those things get pretty awkward. IMO technical terms should stay untouched and I expect people to incorporate those easily into their own language. As a result the web management interface would keep english terms for elements that derive from the XML schema or other API and provide localized description and help texts for anything else.
What are you thoughts on this?
--
Heiko Braun
Senior Software Engineer
JBoss by Red Hat
http://about.me/hbraun
12 years, 6 months
AS7-1807
by Paul Gier
I started working on a way to modularize the product name and version in
the startup/shutdown logs of AS7 [1][2]. There is a new module called
"product" which contains the product name and version. However this
approach doesn't seem good to me because the "host-controller",
"process-controller", and "server" modules all now have dependencies on
this new module.
Ideally, I want to set this up so that there is sort of a placeholder
product name/version used during the build or these modules, but then
this can be overridden by the product module later in the build. Anyone
have suggestions about how to do this?
Thanks!
[1]https://github.com/pgier/jboss-as/commits/AS7-1807
[2]https://issues.jboss.org/browse/AS7-1807
12 years, 6 months
Components that we do not (want to) support
by Thomas Diesler
Hi Dimitris,
currently there are a number of OSGi bundles in the distro that we don't
want to support (e.g Jetty HttpService, Aries Blueprint). Generally I
assume that every jar we ship must also potentially be supported. Is
that still true?
If so, I would remove these bundles
<https://issues.jboss.org/browse/AS7-3036> from the distro and move test
coverage to the jbosgi project. AS7 would then only contain basic OSGi
core support and 3rd party bundles would not be shipped any more.
An alternative could be to label all OSGi functionality (that relies on
3rd party bundles) as tech preview and leave the bundles and test
coverage in the project source.
please advise
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 6 months
Getting rid of arquillian/container-managed-domain
by Brian Stansberry
Hi Aslak,
I'd like to get rid of the current arquillian/container-managed-domain
module in the AS7 source tree and move the couple classes there to the
testsuite/domain module. That's the only place they are used, and their
current location implies they are a proper arquillian container
implementation, which isn't the case. They're just some utilities that I
hoped someday to turn into a proper container implementation.
Any objections?
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
12 years, 6 months
resource bundle loading
by William DeCoste
Hi all,
I've got a war ( org.apache.sling.launchpad-6.war from
http://sling.apache.org/site/downloads.cgi) that deploys and functions
properly in EAP5, but fails in AS7. In AS7, the war deploys without
error but when accessing
http://localhost:8080/org.apache.sling.launchpad-6 the web app fails
with an NPE (stacktrace below). Looks like a resource bundle is not
being loaded in AS7. This issue originally came up with an Express user,
but is recreatable outside of Express.
Any ideas?
Do I need to explicitly list the resource bundle jar in AS7?
Thanks -Bill
17:13:07,607 INFO [org.jboss.as.server.controller]
(DeploymentScanner-threads - 2) Deployed "org.apache.sling.launchpad-6.war"
17:13:08,740 ERROR [stderr] (FelixStartLevel) 2012-01-02 22:13:08.739
GMT Thread[FelixStartLevel,5,main] java.io.FileNotFoundException:
derby.log (Permission denied)
I have noticed the error on the last line, but that should not, by my
experience, cause the app to fail completely. However, when attempting
to request http://appname-namespace.rhcloud.com, the following is logged:
17:15:26,654 ERROR [org.apache.catalina.connector.CoyoteAdapter]
(http--127.1.0.129-8080-1) An exception or error occurred in the
container during the request processing: java.lang.NullPointerException
at
org.apache.tomcat.util.res.StringManager.getString(StringManager.java:113)
[jbossweb-7.0.1.Final.jar:7.0.2.Final]
at
org.apache.tomcat.util.http.HttpMessages.getMessage(HttpMessages.java:68) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at
org.apache.coyote.http11.InternalOutputBuffer.getMessage(InternalOutputBuffer.java:463)
[jbossweb-7.0.1.Final.jar:7.0.2.Final]
at
org.apache.coyote.http11.InternalOutputBuffer.sendStatus(InternalOutputBuffer.java:430)
[jbossweb-7.0.1.Final.jar:7.0.2.Final]
--
Bill DeCoste
Principal Software Engineer, Red Hat
978-204-0920
wdecoste(a)redhat.com
12 years, 6 months
Access to public API jars from (remote) client applications
by Jaikiran Pai
I'm writing up the documentation for invoking remote EJBs from a
(really) remote application like standalone Java applications. One of
the things that we have to decide about is how we want the users to
access some of our public API jars (I'm not calling this "client" jars
since one of the previous discussions around this suggested that it
would confuse things). Right now we don't have a way where users can
*easily* add these public API jars to their classpath. Some of the
requirements that I can think of are:
1) These jars must be available at a well known location within the AS
distribution. i.e. the users shouldn't have to drill down into
individual module path to find the jars.
2) The jar names shouldn't contain the version names (since that will
require changes to client scripts if some API jar version changes)
3) Modular environment on the client side is not a requirement. i.e. the
client application should just be able add these jars to their classpath
and use them
4) IDE and build tool requirements should be taken into account
separately. i.e. a "bom" or some other IDE specific way of getting
access to these API jars _shouldn't_ be the only way of referencing
these jars.
5) Identifying the public API jars
Thoughts? Is this something that we could target for 7.1 Beta1?
-Jaikiran
12 years, 6 months
Quickstarts unused/undeclared dependencies
by Paul Gier
The quickstarts currently have some possibly incorrect dependencies.
For example, using "mvn dependency:analyze" against the helloworld
quickstart reports the following dependency warnings. Should these be
fixed, or is there a reason to keep it as is?
[WARNING] Used undeclared dependencies found:
[WARNING] javax.inject:javax.inject:jar:1:provided
[WARNING] Unused declared dependencies found:
[WARNING] javax.enterprise:cdi-api:jar:1.0-SP4:provided
[WARNING]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar:1.0.0.Final:provided
12 years, 6 months
Can't build AS7.1.0
by Vimal Kansal
Hi,
I had been successfully building AS7.1.0 till 24th Dec, although some
integration tests used to fail but I still used to get
..build\target\jboss-as-7.1.0.Final-SNAPSHOT folder created and could
start the appserver. But, when I came back from vacation yesterday,
since then I am not able to build I mean the target\.. folder itself is
not getting created. Here is what my reactor summary looks like :
========================================================================================================================
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.414s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.447s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [13.294s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [4.281s]
[INFO] JBoss Application Server: Controller Core ......... SUCCESS [17.807s]
[INFO] JBoss Application Server: Domain Management ....... SUCCESS [4.068s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.354s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [2.471s]
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [1.680s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [2.706s]
[INFO] JBoss Application Server: Platform MBean integration SUCCESS
[4.069s]
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [5.952s]
[INFO] JBoss Application Server: Network ................. SUCCESS [2.049s]
[INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [6.153s]
[INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.841s]
[INFO] JBoss Application Server: Server .................. SUCCESS [9.879s]
[INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [4.415s]
[INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [11.326s]
[INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [6.160s]
[INFO] JBoss Application Server: EE ...................... SUCCESS [7.432s]
[INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [6.082s]
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.322s]
[INFO] JBoss Application Server: Common code for clustering subsystems
SUCCESS [4.247s]
[INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [4.683s]
[INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [11.843s]
[INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [7.395s]
[INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [10.175s]
[INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [9.756s]
[INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [24.048s]
[INFO] JBoss Application Server: Clustering Server API ... SUCCESS [10.245s]
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS
[2.966s]
[INFO] JBoss Application Server: Clustering Server API implementation
SUCCESS [3.630s]
[INFO] JBoss Application Server: Distributed Web Session Infinispan
provider SUCCESS [4.911s]
[INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [11.267s]
[INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.295s]
[INFO] JBoss Application Server: Web Services Server Integration
Subsystem SUCCESS [8.605s]
[INFO] JBoss Application Server: Application Client Bootstrap SUCCESS
[5.315s]
[INFO] JBoss Application Server: Command line interface .. SUCCESS [7.258s]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache
Infinispan provider SUCCESS [2.568s]
[INFO] JBoss Application Server: Clustered registry service SUCCESS
[1.538s]
[INFO] JBoss Application Server: Clustered service provider registry
services SUCCESS [2.308s]
[INFO] JBoss Application Server: Clustered singleton services SUCCESS
[2.969s]
[INFO] JBoss Application Server: EJB Container Managed Persistence
Subsystem SUCCESS [17.521s]
[INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [6.053s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [0.568s]
[INFO] JBoss Application Server: EE Deployment ........... SUCCESS [2.576s]
[INFO] JBoss Application Server: JAXR Client ............. SUCCESS [2.591s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.288s]
[INFO] JBoss Application Server: JPA SPI ................. SUCCESS [4.220s]
[INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [1.952s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [4.975s]
[INFO] JBoss Application Server: Weld Integration ........ SUCCESS [7.441s]
[INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [4.153s]
[INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.289s]
[INFO] JBoss Application Server: JDR ..................... SUCCESS [4.471s]
[INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [3.384s]
[INFO] JBoss Application Server: Management Client Content SUCCESS [1.387s]
[INFO] JBoss Application Server: Host Controller ......... SUCCESS [10.318s]
[INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [8.297s]
[INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [5.375s]
[INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [11.046s]
[INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [5.570s]
[INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [3.718s]
[INFO] JBoss Application Server: OSGi .................... SUCCESS [0.293s]
[INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [8.997s]
[INFO] JBoss Application Server: OSGi Config Admin ....... FAILURE [2.781s]
[INFO] JBoss Application Server: sosreport scripts ....... SKIPPED
[INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
[INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
[INFO] JBoss Application Server: Infinispan Hibernate 2nd level cache
provider SKIPPED
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
[INFO] JBoss Application Server: Build ................... SKIPPED
[INFO] JBoss Application Server: Exported Java EE Specification APIs
SKIPPED
[INFO] JBoss Application Server: Public APIs ............. SKIPPED
[INFO] JBoss Application Server: Arquillian .............. SKIPPED
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
[INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
[INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
[INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
[INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Domain Container
SKIPPED
[INFO] JBoss Application Server: Demos: Aggregator ....... SKIPPED
[INFO] JBoss Application Server: Demos: Spec ............. SKIPPED
[INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SKIPPED
[INFO] JBoss Application Server: Distribution ............ SKIPPED
[INFO] JBoss Application Server: OSGi Integration Plugin . SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
[INFO] JBoss Application Server: Validation Tests for Exported Java EE
Specification APIs SKIPPED
[INFO] JBoss Application Server: Web Services Tests Integration
Subsystem SKIPPED
[INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
[INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
[INFO] JBoss Application Server Test Suite: Integration Aggregator SKIPPED
[INFO] JBoss AS Test Suite: Integration - Smoke .......... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 6:16.679s
[INFO] Finished at: Sun Jan 01 12:22:45 EST 2012
[INFO] Final Memory: 184M/3915M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.3.1:install
(default-install) on project jboss-as-osgi-configadmin: Failed to
install metadata org.jboss.as:jboss-as-osgi
-configadmin/maven-metadata.xml: Could not parse metadata
C:\vkk\maven_repository\org\jboss\as\jboss-as-osgi-configadmin\maven-metadata-local.xml:
only whitespace content allowed before start tag and
not \u0 (position: START_DOCUMENT seen \u0... @1:1) -> [Help 1]
[ERROR]
==============================================================================================================================================================================================================
Can somebody please help me in resolving this?
Thx
Vimal
12 years, 7 months
