No Release Tonight
by Jason T. Greene
Unfortunately, we are not releasing tonight due to the following issues:
- Security and Remoting Updates are needed for Domain Security, which is
blocking the new controllers merge
- We have identified a possible perf regression that is being looked into
- We need to do another TCK verification
I will send an update tomorrow.
Thanks
--
Jason T. Greene
JBoss, a division of Red Hat
14 years, 11 months
Building JBoss-As7 : Why I see Integration tests all the time broken on my machine
by Vimal Kansal
Hi,
I have followed all the steps as described in "Hacking on AS7"
(http://community.jboss.org/wiki/HackingOnAS7). However, when I run
"build install", every time at the end, I am getting 'build failure as
shown below. Can somebody please help.
Thx
Vimal
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.arquillian.container.managed.IntegrationTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 17.69
sec <<< F
ILURE!
Running org.jboss.as.arquillian.container.managed.ManagedAsClientTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.234
sec <<< F
ILURE!
Running org.jboss.as.arquillian.container.managed.ManagedInContainerTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.156
sec <<< F
ILURE!
Results :
Tests in error:
org.jboss.as.arquillian.container.managed.IntegrationTestCase:
file:\C:\vkk\J
oss-AS7\jboss-as\arquillian\protocol-jmx\target\jboss-as-arquillian-protocol-jm
-7.0.0.Beta4-SNAPSHOT.jar!\arquillian-service\META-INF\services\org.jboss.msc.s
rvice.ServiceActivator was not found in any available ClassLoaders
org.jboss.as.arquillian.container.managed.IntegrationTestCase
org.jboss.as.arquillian.container.managed.ManagedAsClientTestCase:
file:\C:\v
k\JBoss-AS7\jboss-as\arquillian\protocol-jmx\target\jboss-as-arquillian-protoco
-jmx-7.0.0.Beta4-SNAPSHOT.jar!\arquillian-service\META-INF\services\org.jboss.m
c.service.ServiceActivator was not found in any available ClassLoaders
org.jboss.as.arquillian.container.managed.ManagedAsClientTestCase
org.jboss.as.arquillian.container.managed.ManagedInContainerTestCase:
file:\C
\vkk\JBoss-AS7\jboss-as\arquillian\protocol-jmx\target\jboss-as-arquillian-prot
col-jmx-7.0.0.Beta4-SNAPSHOT.jar!\arquillian-service\META-INF\services\org.jbos
.msc.service.ServiceActivator was not found in any available ClassLoaders
org.jboss.as.arquillian.container.managed.ManagedInContainerTestCase
Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [2.808s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.819s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [5.008s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [4.024s]
[INFO] JBoss Application Server: Command line interface .. SUCCESS [7.754s]
[INFO] JBoss Application Server: Controller Core ......... SUCCESS [8.314s]
[INFO] JBoss Application Server: Domain Management ....... SUCCESS [1.342s]
[INFO] JBoss Application Server: Domain HTTP API ......... SUCCESS [2.090s]
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [1.108s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [1.654s]
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [1.138s]
[INFO] JBoss Application Server: Server .................. SUCCESS [11.514s]
[INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [2.668s]
[INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [2.667s]
[INFO] JBoss Application Server: EE ...................... SUCCESS [5.897s]
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [6.443s]
[INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [13.338s]
[INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [2.636s]
[INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [6.630s]
[INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [3.105s]
[INFO] JBoss Application Server: Domain Controller ....... SUCCESS [2.199s]
[INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [6.911s]
[INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [3.401s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [13.557s]
[INFO] JBoss Application Server: Weld Integration ........ SUCCESS [3.010s]
[INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [1.763s]
[INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [1.404s]
[INFO] JBoss Application Server: Host Controller ......... SUCCESS [2.793s]
[INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [5.350s]
[INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [2.106s]
[INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [2.949s]
[INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [1.341s]
[INFO] JBoss Application Server: OSGi .................... SUCCESS [0.344s]
[INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [3.541s]
[INFO] JBoss Application Server: OSGi Config Admin ....... SUCCESS [3.931s]
[INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [2.855s]
[INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [3.120s]
[INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.359s]
[INFO] JBoss Application Server: Web Services Server Integration
Subsystem SUC
ESS [9.765s]
[INFO] JBoss Application Server: Build ................... SUCCESS [50.513s]
[INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.437s]
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS
[1.576s]
[INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.151s]
[INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [2.153s]
[INFO] JBoss Application Server: Arquillian Managed Container FAILURE
[54.475s
[INFO] JBoss Application Server: Arquillian Managed Domain Container
SKIPPED
[INFO] JBoss Application Server: Demos: Aggregator ....... SKIPPED
[INFO] JBoss Application Server: Demos: AS7 API .......... SKIPPED
[INFO] JBoss Application Server: Demos: Spec ............. SKIPPED
[INFO] JBoss Application Server: Demos: AS7 Internals .... SKIPPED
[INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SKIPPED
[INFO] JBoss Application Server: Distribution ............ SKIPPED
[INFO] JBoss Application Server: Microcontainer Subsystem SKIPPED
[INFO] JBoss Application Server: OSGi Integration Plugin . SKIPPED
[INFO] JBoss Application Server: Web Services Tests Integration
Subsystem SKIP
ED
[INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
[INFO] JBoss Application Server Test Suite: Smoke Tests .. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4:42.814s
[INFO] Finished at: Thu Jun 16 11:55:24 EST 2011
[INFO] Final Memory: 90M/216M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2
8.1:test (default-test) on project
jboss-as-arquillian-container-managed: There
are test failures.
[ERROR]
[ERROR] Please refer to
C:\vkk\JBoss-AS7\jboss-as\arquillian\container-managed\
arget\surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e swi
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please re
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureEx
eption
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
comman
[ERROR] mvn <goals> -rf :jboss-as-arquillian-container-managed
Press any key to continue . . .
14 years, 11 months
Console outage
by Heiko Braun
The console does currently not work due to some shortsighted commit of mine.
Sorry, about that. I am going to release another beta for the time being.
Ike
14 years, 11 months
Aquillan module in AS 7 final ?
by Francesco Marchioni
Hi all!
I see the Snapshot4 does not include any more the Arquillan module. I wonder
if this temporarly due to the Testing Consolidation process or it will be
not included at all in the final distribution.
As a matter of fact, having Arquillan libraries built-in AS 7 makes fairly
attractive unit testing with Eclipse Indigo and JBoss Tools 3.3.1, which
already have AS 7 support.
Thanks for your feedback
Francesco
14 years, 11 months
AS7 upstream - HornetQ 2.2.5.Final release and HORNETQ-681 issue
by Jaikiran Pai
AS7 upstream has been upgraded to use HornetQ 2.2.5.Final release to
bring in the fix for https://issues.jboss.org/browse/HORNETQ-681.
However, with the latest upstream with this version of HornetQ, I still
see the same issue[1]. Wesley too seems to be running into this problem,
as he mentions in that JIRA. I have attached the test application to
that JIRA now. I'll add a test in AS7 smoke tests to make sure that this
indeed works, when it gets fixed.
-Jaikiran
[1] logs below:
09:46:22,882 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC
service thread 1-2) HornetQ Server version 2.2.5.Final
(HQ_2_2_5_FINAL_AS7, 121) [da2cadeb-9a2a-11e0-8828-001f161149f5] started
....
09:48:14,882 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) javax.jms.JMSException:
Failed to create session factory
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:615)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.jms.client.HornetQConnectionFactory.createQueueConnection(HornetQConnectionFactory.java:133)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.jms.client.HornetQConnectionFactory.createQueueConnection(HornetQConnectionFactory.java:128)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.jsp.test_jsp._jspService(test_jsp.java:68)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
09:48:14,883 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
09:48:14,884 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
09:48:14,885 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:658)
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
java.lang.Thread.run(Thread.java:619)
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) Caused by:
HornetQException[errorCode=0 message=Failed to initialise session factory]
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:558)
09:48:14,886 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:611)
09:48:14,887 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) ... 24 more
09:48:14,887 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) Caused by:
java.lang.IllegalArgumentException: Unable to instantiate load balancing
policy
"org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy"
09:48:14,887 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl$2.run(ServerLocatorImpl.java:299)
09:48:14,887 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
java.security.AccessController.doPrivileged(Native Method)
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl.instantiateLoadBalancingPolicy(ServerLocatorImpl.java:286)
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl.initialise(ServerLocatorImpl.java:313)
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:554)
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) ... 25 more
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) Caused by:
java.lang.ClassNotFoundException:
org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy
from [Module "deployment.test.war:main" from Service Module Loader]
09:48:14,888 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188)
09:48:14,889 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
09:48:14,889 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
09:48:14,889 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
09:48:14,889 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) at
org.hornetq.core.client.impl.ServerLocatorImpl$2.run(ServerLocatorImpl.java:293)
09:48:14,889 ERROR [stderr]
(http-localhost.localdomain-127.0.0.1-8080-1) ... 29 more
14 years, 11 months
security/web sucks, what can we change?
by Bill Burke
I'm not happy with the state of our security abstractions.
* For one, JBossWeb is stuck in Tomcat land and there are so many hacks
to propagate configuration/service objects to the various valves and
filters.
* Tomcat Realm and JBoss Security Domain are stuck in user/password
land. THere are a few protocols (i.e.SAML) that are not password
driven, (and maybe not even username driven). If you want to hook in
these protocols, you have to tunnel information through Threadlocals or
the PrincipalContext.
* There is no clear separation of concerns from Valve, Realm, and
Security Domain. Security Domain was originally intended to be a
user/password, user/role mapping. Some plugins are starting to bleed in
protocol information. Valves set Tomcat specific principal information.
JbossWebRealm bridges to the security domain and also sets JBoss
specific principal information.
* It is impossible to plug in a new Security Domain type at the moment.
* It is impossible to plug in a custom auth-method. (Remy is wrong
about not wanting to put this in.)
* If you want to plug in your own protocol it is a mess to do it. If
you look at picketlink, configuration is a combination of editing the
security domain config, adding tomcat valve, adding filters to web.xml.
So what do I want to do?
Step 1:
- Add ability to plug in a Security Domain type. Currently its all
hardcoded. I don't see any mechanism in AS7 at the moment for plugging
in IoC like information. I don't see mechanism for discovering config
files or a place to put config files in AS7. This isn't a bad thing. I
think what we could do is allow people to add a
"org.jboss.security.DomainMapping" file to META-INF/services directory
of any jar. When the Security Subsystem starts up it will search for
all files of that name and load up a mapping file.
- Add ability to define JBossWeb Authenticators. Tomcat/JBossWeb
already has this ability inheritently built in, but unexposed. Similar
to DomainMapping, we'll have a org.jboss.web.Authenticators file that
has a class/auth-method mapping.
I am already prototyping this stuff in my git branch. I'm pretty sure
it can require zero changes to JBossWeb which should avoid getting Remy
all flustered.
Step 2:
I'd like to gut JBossWeb security and Picketbox security. Redesign the
whole damn thing. Its just hacked and band-aided together. Its stuck
in ancient and obsolete user/password land needs to be more flexible.
- I think it would be very interesting to allow the Security Domain to
handle your authentication and authorization needs and have JBossWeb,
EJB, etc, delegate to the SecurityDomain. Allow the security domain to
view the HttpServletRequest, extract information, change the request,
etc. With this type of model your admin could deploy a new
authentication/authorization model onto an existing deployed
application. For exmaple, an app might start with user/password, but
later might convert the app to be TOTP/Soft/hard token based as they
roll out hard/soft tokens to their user base. There would be a new
auth-method named "JBOSS-SECURITY-DOMAIN". We'd need some serious
discussion on this before moving forward.
- Alternatively (and this is a must have without the above), the
SecurityDomain needs to become a more generic store of information other
than user/password user/role mappings. I writing some protocols that
use public-keys and a valve would need to query the security domain for
this key. A SAML valve may want to query the security domain for
assertions. You get the idea.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
14 years, 11 months
Having trouble in building JBoss AS7 quickstarts
by Vimal Kansal
Hi,
I am going through the quickstarts guide and have installed eclipse
indigo with JBoss tools as described in the doc. When I import maven
projects, eclipse hangs and closes suddenly.
Trying to deploy through commandline, I am getting the following error :
C:\vkk\downloads\software\jboss\JBossAS\quickstarts\helloworld>mvn
install -U
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Helloworld 7.0.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
Downloading:
http://repo1.maven.org/maven2/org/jboss/as/plugins/jboss-as-deploy-
plugin/7.0.0.Beta3/jboss-as-deploy-plugin-7.0.0.Beta3.pom
[WARNING] The POM for
org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta
3 is missing, no dependency information available
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.760s
[INFO] Finished at: Wed Jun 15 01:14:03 EST 2011
[INFO] Final Memory: 2M/15M
[INFO]
------------------------------------------------------------------------
[ERROR] Plugin org.jboss.as.plugins:jboss-as-deploy-plugin:7.0.0.Beta3
or one of
its dependencies could not be resolved: Failed to read artifact
descriptor for
org.jboss.as.plugins:jboss-as-deploy-plugin:jar:7.0.0.Beta3: Could not
find arti
fact org.jboss.as.plugins:jboss-as-deploy-plugin:pom:7.0.0.Beta3 in
central (htt
p://repo1.maven.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResoluti
onException
Can somebody please help.
Thx
Vimal
14 years, 11 months
another approach to cli commands / operations
by Alexey Loubyansky
Up until now I've been writing commands and handlers manually. It is
justified in some cases like deploy for example. But I realized it's too
much redundant work for commands to e.g. manage datasources, etc.
What I mean is I wrote add-data-source, remove-data-source,
modify-data-source. Then there could be enable, disable, flush
connections, etc. So instead, I wrote one command that I called data-source.
Now it looks like this (it's tab-completion)
[standalone@localhost:9999 /] data-source java:/H2DS
add disable enable
flush-all-connection-in-pool
flush-idle-connection-in-pool read-attribute
read-children-names read-children-resources
read-children-types read-operation-description
read-operation-names read-resource
read-resource-description remove
test-connection-in-pool write-attribute
So you can choose whatever operation you want, e.g.
data-source java:/H2DS flush-all-connection-in-pool
or whatever. If there are properties, it could look like
data-source java:/H2DS my-operation --prop1=val1 --prop2=val2
or to modify properties of the data source
data-source java:/H2DS --min-pool-size=10 --max-pool-size=100
At the end, this will save the total number of the commands, avoid
possible inconsistency between commands and operations (like supported
properties and even operations), the changes in operations and
properties will be immediately exposed through the cli w/o
changing/introducing new cli commands.
In addition, this data-source thing is actually no more than an alias to
the node path, i.e. /subsystem=datasources/data-source. So, actually,
this can be done for any component in a generic way, e.g. jms, etc. And
even it could be customized by the user at runtime.
Again, that's not for everything. For things like deploy, we could keep
hand-written command handlers but for the majority of the managed
components this could work (although there are some operations that
don't make much sense to expose, e.g. write-attribute or add as an
operation on a specific data source but these could be filtered somehow).
So, if anybody has suggestions or objections, please, let me know.
Otherwise, I intend to do it this way. Not for CR1 though.
Thanks,
Alexey
14 years, 11 months
distribution name, folder name and JBOSS_HOME
by Dan Allen
Has a decision been made about whether to rename the distribution and
compressed folder name as follows, or is this topic still open for
consideration?
distribution name: jboss-as-7.0.0.Final.zip
compressed folder name: jboss-as
I strongly encourage this convention to help reinforce the distinction
between the JBoss brand/community and the project. JBoss AS 6 went half way
by naming the distribution jboss-as-6.0.0.Final.zip but leaving the folder
as jboss.
I heard that this change has been deferred until AS 8. However, I think
deferring it will be more painful and potentially upset users in the long
run. We already change the startup script name, the deployment directory
name and the mechanism for hot deployment. Can't we just rip off the tape
all at once and rename the distribution and folder name? Seriously, I think
it would be a huge mistake to let this one go.
Max has already prepared a pull request for the build change:
https://github.com/jbossas/jboss-as/pull/53
I also noticed in the getting started guide that Pete drafted that he
recommends setting JBOSS_HOME before starting the server (though I think
that recommendation has now been removed). However, if you already have
JBOSS_HOME set (let's say for JBoss AS 5), then it's a problem when you try
to run AS 7.
Every release of AS that I download, I get around this by adding the
following to the run.conf (now standalone.conf)
JBOSS_HOME=$DIRNAME/..
That way, JBOSS_HOME is set relative to the startup script I'm executing.I
have yet to find a problem with this approach. For standalone, that seems
*way* simpler. Plus, I can toggle between different "installations" of the
server without having to change my environment variables. I would never want
to start a different instance than for the script I'm executing. That's just
nonsensical.
This last point is probably way too big of a change, but have we considered
changing JBOSS_HOME to JBOSS_AS_HOME. We could meet half way and just
support both, checking first for JBOSS_AS_HOME, then falling back to
JBOSS_HOME.
wdyt?
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
14 years, 11 months
