November 2012 - jboss-dev-forums - Jboss List Archives

[IronJacamar Development] - IronJacamar Oracle Reauthentication support

by Ricardo Arguello

Ricardo Arguello [https://community.jboss.org/people/ricardoarguello] created the discussion "IronJacamar Oracle Reauthentication support" To view the discussion, visit: https://community.jboss.org/message/757365#757365 -------------------------------------------------------------- Anybody interested in helping me test this? https://github.com/rarguello/ironjacamar-oracle-reauth https://github.com/rarguello/ironjacamar-oracle-reauth -- Ricardo Arguello -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/757365#757365] Start a new discussion in IronJacamar Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 4 months

3
6
0 / 0

[JBoss AS 7 Development] - VisualVM -> JBoss AS 7.1.1

by Juergen Weber

Juergen Weber [https://community.jboss.org/people/weberj] created the discussion "VisualVM -> JBoss AS 7.1.1" To view the discussion, visit: https://community.jboss.org/message/737964#737964 -------------------------------------------------------------- Hi, how can one access with VisualVM 1.3.3 the mbeans in JBoss AS 7.1.1 on a remote machine? The solutions in the theads below do *not* work for me, VisualVM just does not connect. Thanks, Juergen https://docs.jboss.org/author/display/AS71/JMX+subsystem+configuration https://docs.jboss.org/author/display/AS71/JMX+subsystem+configuration https://community.jboss.org/docs/DOC-17485 https://community.jboss.org/wiki/UsingJconsoleToConnectToJMXOnAS7 https://community.jboss.org/thread/196981 https://community.jboss.org/thread/196981 -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/737964#737964] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 5 months

3
2
0 / 0

[JBoss AS 7 Development] - Re: Custom jdbc login module for remoting

by Sigmar Tholen

Sigmar Tholen [https://community.jboss.org/people/siggi] created the discussion "Re: Custom jdbc login module for remoting" To view the discussion, visit: https://community.jboss.org/message/740168#740168 -------------------------------------------------------------- Hello, > Jason Greene schrieb: > > Although to help with usability I have created, which would allow a security domain to refer to a specific deployment module, giving you deployable login modules (not just static modules): > > https://issues.jboss.org/browse/AS7-3905 https://issues.jboss.org/browse/AS7-3905 Could someone confirm, that this fix is not in 7.1.1.Final and therefore not working in 7.1.1.Final? Thanks in advance -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/740168#740168] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 5 months

3
2
0 / 0

[JBoss Profiler Development] - Fail to Invoke - HTTP Status 403

by Daniel Ho

Daniel Ho [https://community.jboss.org/people/danielho] created the discussion "Fail to Invoke - HTTP Status 403" To view the discussion, visit: https://community.jboss.org/message/724200#724200 -------------------------------------------------------------- Hi, I install jboss-profiler-1.0.CR4 - jvmti on JBoss 4_3_0_GA_CP0, I login admin but fail to invoke *mbean:* JVMTIClass *type* Status report *message* *description* Access to the specified resource () has been forbidden. ./conf/props/jmx-console-roles.properties admin=JBossAdmin,HttpInvoker I checked admin role is able to do that -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/724200#724200] Start a new discussion in JBoss Profiler Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 5 months

2
1
0 / 0

[JBoss AS 7 Development] - Re: remote ejb client username is encrypted at the server(JBOSS7.1 CR1)

by Petr Mates

Petr Mates [https://community.jboss.org/people/mates1234] created the discussion "Re: remote ejb client username is encrypted at the server(JBOSS7.1 CR1)" To view the discussion, visit: https://community.jboss.org/message/719242#719242 -------------------------------------------------------------- Do you know, what is managed by jboss.naming.client.ejb.context? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/719242#719242] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 6 months

9
11
0 / 0

[jBPM Development] - How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE

by uvijayreddy657

uvijayreddy657 [https://community.jboss.org/people/uvijayreddy657] created the discussion "How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE" To view the discussion, visit: https://community.jboss.org/message/715135#715135 -------------------------------------------------------------- In JBoss server always for every second the below is scrolling continuously. Because of this *server.log size is increasing till 400MB to 500MB*. Getting disk out of space error and also getting *java.net.SocketException : Too many open files.* *How to stop this LoggingFilter.* Please suggest and advice. 2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:14,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:14,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:15,277 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:22,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:22,264 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE 2012-02-08 11:59:25,266 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE 2012-02-08 11:59:25,283 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE 2012-02-08 11:59:25,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/715135#715135] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 6 months

3
2
0 / 0

[JBoss AS 7 Development] - BMP entity from jboss5 to jboss7.1

by Ale S

Ale S [https://community.jboss.org/people/a.salina] created the discussion "BMP entity from jboss5 to jboss7.1" To view the discussion, visit: https://community.jboss.org/message/734732#734732 -------------------------------------------------------------- Hi, i'm trying to migrate an application from jboss 5 to version 7.1. In my application there is a 2.1 version BMP entity... i've searched throught the documentation but i cannot find how to migrate this portion of configuration... in my jboss.xml (jboss 5) i have : ... ... <container-configurations> <container-configuration extends="Standard BMP EntityBean"> <container-name>Clustered Legacy Locked BMP EntityBean</container-name> <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache> <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy> <commit-option>B</commit-option> </container-configuration> </container-configurations> ... ... Any suggestions? how could i configure jboss7.1 so that it behaves as in JBoss 5. Thanks, Ale p.s.: sorry for my english... -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/734732#734732] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

3
2
0 / 0

[JBoss AS 7 Development] - Re: EJB lookup during server shutdown

by Jason Greene

Jason Greene [https://community.jboss.org/people/jason.greene] created the discussion "Re: EJB lookup during server shutdown" To view the discussion, visit: https://community.jboss.org/message/725440#725440 -------------------------------------------------------------- This is really a problem with the way EJB specs are written. The lifecycle is intentionally very loose to allow things like circular references. The problem is that if you allow circularity you can't have strict ordering. Singleton has a solution for this using @DependsOn. We are looking at opening this up for other bean types, but it would of course be a proprietary feature. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/725440#725440] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

5
13
0 / 0

[jBPM Development] - org.drools.RuntimeDroolsException: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager, Caused by: org.jbpm.workflow.instance.WorkflowRuntimeException: -- argument type mismatch

by prashanth Reddy Dundigal

prashanth Reddy Dundigal [https://community.jboss.org/people/prashanth_biomorf] created the discussion "org.drools.RuntimeDroolsException: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager, Caused by: org.jbpm.workflow.instance.WorkflowRuntimeException: -- argument type mismatch" To view the discussion, visit: https://community.jboss.org/message/755045#755045 -------------------------------------------------------------- Sai, The service task properties are declared in this way : | Id | 3 | | Interface | org.jbpm.biomorf.sample.demo.EvenOddNumberCheckServiceImpl | | MetaData | {height=53, width=99, UniqueId=_9-3, y=121, x=129} | | Name | CheckEvenOdd | | On Entry Actions | [System.out.println(" entering into service task ");] | | On Exit Actions | [System.out.println("exiting service task");] | | Operation | checkEvenOrOdd | | Parameter | | | Parameter Mapping | {Parameter=inputNumber} | | ParameterType | java.lang.String | | Result Mapping | {Result=inputNumber} | Can anyone please see the below error and let us know what to do... We are not able to run the service task inside an Adhoc-sub-Process. When run the task, I get the following error : org.drools.RuntimeDroolsException: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalProcessInstanceAction@1080876 at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:979) at org.drools.impl.StatefulKnowledgeSessionImpl.executeQueuedActions(StatefulKnowledgeSessionImpl.java:866) at org.jbpm.process.instance.event.DefaultSignalManager.signalEvent(DefaultSignalManager.java:90) at org.jbpm.process.instance.ProcessRuntimeImpl.signalEvent(ProcessRuntimeImpl.java:372) at org.drools.impl.StatefulKnowledgeSessionImpl.signalEvent(StatefulKnowledgeSessionImpl.java:341) at org.jbpm.biomorf.sample.demo.NumberProcessTest.main(NumberProcessTest.java:108) Caused by: org.jbpm.workflow.instance.WorkflowRuntimeException: [com.biomorf.sampledemo:1 - CheckEvenOdd:3] -- argument type mismatch at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:130) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:205) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:164) at org.jbpm.workflow.instance.node.ActionNodeInstance.triggerCompleted(ActionNodeInstance.java:55) at org.jbpm.workflow.instance.node.ActionNodeInstance.internalTrigger(ActionNodeInstance.java:51) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124) at org.jbpm.workflow.instance.node.DynamicNodeInstance.signalEvent(DynamicNodeInstance.java:69) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:346) at org.jbpm.process.instance.event.DefaultSignalManager$SignalProcessInstanceAction.execute(DefaultSignalManager.java:118) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:977) ... 5 more Caused by: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jbpm.bpmn2.handler.ServiceTaskHandler.executeWorkItem(ServiceTaskHandler.java:49) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:105) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:124) ... 14 more please help me.... thank you in advance, warm regards, prashanth r dundigal -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/755045#755045] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 8 months

2
1
0 / 0

[EJB3 Development] - Embeddable EJBContainer and JBoss 7.1.1.Final

by Mohammad wrk

Mohammad wrk [https://community.jboss.org/people/mohammadwrk] created the discussion "Embeddable EJBContainer and JBoss 7.1.1.Final" To view the discussion, visit: https://community.jboss.org/message/731765#731765 -------------------------------------------------------------- Has anyone been able to get EJBContainer.createEJBContainer() to work with JBoss 7.1.1.Final? Running the following code as a JUnit test results in NullPointerException! public class EJBContainerTest { private static EJBContainer ejbContainer; private static Context context; @BeforeClass public static void beforeClass() { System.setProperty("jboss.home", "/home/usr1/jboss-as-7.1.1.Final"); ejbContainer = EJBContainer.createEJBContainer(); context = ejbContainer.getContext(); } @Test public void test() { Assert.assertNotNull(context); } } Stack trace: java.lang.NullPointerException at org.jboss.modules.Module.forClassLoader(Module.java:365) at org.jboss.modules.Module.forClassLoader(Module.java:365) at org.jboss.modules.Module.forClassLoader(Module.java:365) at org.jboss.modules.Module.getContextModuleLoader(Module.java:421) at org.jboss.as.embedded.ejb3.JBossStandaloneEJBContainerProvider.createEJBContainer(JBossStandaloneEJBContainerProvider.java:86) at javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:93) at javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:75) at org.arquillian.example.EJBContainerTest.beforeClass(EJBContainerTest.java:18) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/731765#731765] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 9 months

3
4
0 / 0

[PicketBox Development] - Cache timeout for JBossCachedAuthenticationManager

by yichen

yichen [https://community.jboss.org/people/yichen] created the discussion "Cache timeout for JBossCachedAuthenticationManager" To view the discussion, visit: https://community.jboss.org/message/752687#752687 -------------------------------------------------------------- Hi, I am new at JBoss and is wondering if there is a cache timeout for credentials cached by JBossCachedAuthenticationManager. I know this class as a "flush" method that flushes an entry from the cache but can't figure out where that is called. Also, since I am new to JBoss, some pointers on where should I start with the whole JBoss login modules would also be greatly appreciated. Thanks, Yi -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/752687#752687] Start a new discussion in PicketBox Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 10 months

1
1
0 / 0

[Clustering Development] - getting [emerg] create_mem_node /etc/httpd/logs/manager.node failed: Permission denied Configuration Failed when starting apache on rhel 6 after mod_cluster is added

by Claudianus Adjai

Claudianus Adjai [https://community.jboss.org/people/claudianus] created the discussion "getting [emerg] create_mem_node /etc/httpd/logs/manager.node failed: Permission denied Configuration Failed when starting apache on rhel 6 after mod_cluster is added" To view the discussion, visit: https://community.jboss.org/message/778630#778630 -------------------------------------------------------------- Hello all - I am getting the following error when I try to start apache on rhel 6. [emerg] create_mem_node /etc/httpd/logs/manager.node failed: Permission denied Configuration Failed Note that apache was working fine before I uploaded mod_cluster modules and configured it. I also had mod_jk configured and working with apache before this, which I disabled. I am trying to run apache with mod_cluster 1.2.0.Final on rhel 6 x64. I am also starting apache as root (starting it as a regular user causes permission denied error). Finally, note that I tried to run it both with SELinux enabled and disabled and the outcome seems to be the same. My mod_cluster conf looks like below +LoadModule slotmem_module modules/mod_slotmem.so+ +LoadModule manager_module modules/mod_manager.so+ +LoadModule proxy_cluster_module modules/mod_proxy_cluster.so+ +LoadModule advertise_module modules/mod_advertise.so+ +#Listen 192.168.10.91:8008+ +<VirtualHost 192.168.10.91:8008>+ + <Directory />+ + Order deny,allow+ + Deny from all+ + Allow from 127.0.0.1+ + Allow from 192.168.10.+ + </Directory>+ + <Location /mod_cluster-manager>+ + SetHandler mod_cluster-manager+ + Order deny,allow+ + Deny from all+ + Allow from 127.0.0.1+ + Allow from 192.168.10.+ + </Location>+ + ManagerBalancerName mycluster+ + KeepAliveTimeout 60+ + MaxKeepAliveRequests 0+ + ServerAdvertise On+ + EnableMCPMReceive+ +</VirtualHost>+ I commented out the Listen directive because I put it in the main http.conf file (having it in this file does not change the outcome) and the above mod_cluster.conf file is located under my /etc/http/conf.d/ folder. I also saw that there is a bug related to this error but under Windows OS. What am I missing? Thanks C -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778630#778630] Start a new discussion in Clustering Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 10 months

2
2
0 / 0

[JBoss Tools Development] - Startup JBoss AS 7.1.1 from Eclipse

by Yusuf Kaplan

Yusuf Kaplan [https://community.jboss.org/people/yuka78] created the discussion "Startup JBoss AS 7.1.1 from Eclipse" To view the discussion, visit: https://community.jboss.org/message/735226#735226 -------------------------------------------------------------- Hi all, I installed JBoss Tools from the update Site" http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/" and there I selected the node"JBoss Web and Java EE Development" in Eclipse Indigo. Then created new server instance in Eclipse. But server start up fails. I used JBoss AS 7.1.1 Brontes. Platform is Mac OS X 10.6.8. I managed to deploy though hello world and logIn Examples. The server starts via console and the example apps are deployed and working properly. There seem to be a problem when starting JBoss AS 7.1.1 from within Eclipse. The error message on Server startup from Eclipse looks like " Exception in thread "main" java.lang.NoClassDefFoundError: /Applications/jboss-as-7/1/1/Final Caused by: java.lang.ClassNotFoundException: .Applications.jboss-as-7.1.1.Final at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:315) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398) " Any ideas? Cheers, Y -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/735226#735226] Start a new discussion in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 10 months

2
1
0 / 0

[JBoss ESB Development] - Webservice call SOAP Client Action doesnt work

by mgrande

mgrande [https://community.jboss.org/people/mgrande] created the discussion "Webservice call SOAP Client Action doesnt work" To view the discussion, visit: https://community.jboss.org/message/766593#766593 -------------------------------------------------------------- Hi, First of all,let you know that we are beginners in the development with JBOSS,so sorry if we say any stupid thing. We have created a SOAPClient Acton in a ESB with this properties first calling a Request and later a Respond: <action class="es.vass.util.MyRequestActionMyRequestAction" name="PreparaRequest"/> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="weatherMola"> <property name="wsdl" value="http://www.webservicex.com/globalweather.asmx?WSDL"/> <property name="SOAPAction" value="http://www.webserviceX.NET/GetCitiesByCountry"/> <property name="responseAsOgnlMap" value="true"/> </action> <action class="es.vass.util.MyRequestActionMyRequestAction" name="PreparaRequest"/> We call the action with a ESB message and it returns: 09:37:18,244 INFO [InquiryHelper] uddi:juddi.apache.org:c79564de-eb3d-470d-aba7-c85217fc70c8 is modified Wed Oct 17 16:03:03 CEST 2012 1350482583192 09:37:23,360 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 09:37:23,362 INFO [STDOUT] Request map is: {GetCitiesByCountry.CountryName=Spain} 09:37:23,362 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 09:37:23,396 INFO [STDOUT] Progress: 1 - Caching definition from url [http://www.webservicex.com/globalweather.asmx?WSDL] 09:37:24,576 INFO [STDOUT] Progress: 1 - Loading definition from cache 09:37:24,582 INFO [STDOUT] Retrieving document at 'http://www.webservicex.com/globalweather.asmx?WSDL'. 09:37:24,660 INFO [SchemaUtils] Loading schema types from [http://www.webservicex.com/globalweather.asmx?WSDL] 09:37:24,677 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL 09:37:25,635 INFO [SchemaUtils] schema for [http://www.webserviceX.NET] contained [{}] namespaces 09:37:26,246 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost 09:37:26,248 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost 09:37:26,248 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherSoap12 09:37:26,317 INFO [WsdlImporter] Importing binding {http://www.webserviceX.NET}GlobalWeatherSoap12 09:37:26,322 INFO [Soap12HttpBindingImporter] importing endpoint http://www.webservicex.com/globalweather.asmx 09:37:26,393 INFO [Soap12HttpBindingImporter] importing operation GetCitiesByCountry 09:37:26,394 INFO [Soap12HttpBindingImporter] importing operation GetWeather 09:37:26,395 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherSoap 09:37:26,395 INFO [WsdlImporter] Importing binding {http://www.webserviceX.NET}GlobalWeatherSoap 09:37:26,396 INFO [Soap11HttpBindingImporter] importing endpoint http://www.webservicex.com/globalweather.asmx 09:37:26,413 INFO [Soap11HttpBindingImporter] importing operation GetCitiesByCountry 09:37:26,422 INFO [Soap11HttpBindingImporter] importing operation GetWeather 09:37:26,423 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet 09:37:26,423 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet 09:37:26,423 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet 09:37:26,457 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet 09:37:26,457 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost 09:37:26,458 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost 09:37:26,479 INFO [STDOUT] Progress: 1 - Caching definition from url [http://www.webservicex.com/globalweather.asmx?WSDL] 09:37:26,932 INFO [STDOUT] Progress: 1 - Loading definition from cache 09:37:26,948 INFO [STDOUT] Retrieving document at 'http://www.webservicex.com/globalweather.asmx?WSDL'. 09:37:26,974 INFO [SchemaUtils] Loading schema types from [http://www.webservicex.com/globalweather.asmx?WSDL] 09:37:26,974 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL 09:37:27,104 INFO [SchemaUtils] schema for [http://www.webserviceX.NET] contained [{}] namespaces 09:37:27,231 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL 09:37:27,729 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:127.0.0.1:1099#queue/esb_channel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/esb_channel/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 76891731-9980-4511-a82e-8fc03d6cd53b RelatesTo: jms:correlationID#76891731-9980-4511-a82e-8fc03d6cd53b 09:37:27,813 INFO [InquiryHelper] uddi:juddi.apache.org:e60d75e7-29e1-4455-82df-3cfff3236390 is modified Tue Oct 16 17:45:39 CEST 2012 1350402339761 It doesnt do anything else and we dont see any respond. We have truied the webservice with SoapUI and we know that its working. What can check to know what can be wrong? We are working with JBOSS AS 5.1 and JBOSS ESB 4.10 in a local server. We use for the development JBOSS developer. Thanks you in ad -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/766593#766593] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 11 months

2
1
0 / 0

[jBPM Development] - Integration of JBPM into a web application

by Cyrine Bjaoui

Cyrine Bjaoui [https://community.jboss.org/people/cyrine] created the discussion "Integration of JBPM into a web application" To view the discussion, visit: https://community.jboss.org/message/773663#773663 -------------------------------------------------------------- Hello everybody, I started creating a JBPM5 project, witch includes some functions to call in a main class. It runs perfectly. I created also a web application, witch contains 2 web pages (a web page A with a button to go to the web page B). It works too. Now i wanna use a function from the JBPM project, and call it via the button action (I used a managed bean) of my web page. I tryed to call my JBPM project as Jar file, it generated an error saying : " GRAVE: Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1595) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:419) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:785) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:519) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:581) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) org.apache.catalina.core.StandardContext start " I thought to use web services, I'm not sure if it will help. The idea is to use functions, from my JBPM project, into a web application. Any help please ! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773663#773663] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 11 months

3
3
0 / 0

[JBoss AS 7 Development] - Re: ClassNotFoundException (org.xml.sax.helpers.DefaultHandler) in a module

by Markus Straub

Markus Straub [https://community.jboss.org/people/markus_s] created the discussion "Re: ClassNotFoundException (org.xml.sax.helpers.DefaultHandler) in a module" To view the discussion, visit: https://community.jboss.org/message/714943#714943 -------------------------------------------------------------- The answer is to add the following dependencies to my module.xml: <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="at.mylib"> <resources> <resource-root path="mylib.jar"/> </resources> <dependencies> <system export="true"> <paths> <path name="org/xml/sax"/> <path name="org/xml/sax/helpers"/> </paths> </system> </dependencies> </module> -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/714943#714943] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

2
1
0 / 0

[JBoss AS 7 Development] - Install JBOSS tools on Eclipse Juno (4.x)

by Michael Needham

Michael Needham [https://community.jboss.org/people/iainnitro] created the discussion "Install JBOSS tools on Eclipse Juno (4.x)" To view the discussion, visit: https://community.jboss.org/message/754041#754041 -------------------------------------------------------------- Greetings: I recently adopted Eclipse Juno for my IDE and went to the marketplace to install the JBOSS tools. I noticed that there is only a package for Indigo and not one for Juno as of yet. I am on Mac OS X (Mountain Lion 10.8) and got the AS7 server running and starting at login. This box is not a production box, but my development box. I would probably deploy to a Linux box (specifically CentOS or Scientific) in production. This is all background information. The question is how to get the JBoss Tools setup in Eclipse Juno? I tried to install the Indigo package and got dependency errors so if someone has actually installed JBoss tools on Juno and in Mac OSX Mountain Lion, I could use some pointers on getting it done. Also be nice to know when the native Juno version of the tools may be available :^0 Thank-you in advance for your help. BTW: I am planning to develop in Grails/Groovy using JSP and want to explore the use of JSF (Java Server Faces) as well. I am pretty new to this end of the spectrum of Java. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/754041#754041] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

4
5
0 / 0

[JBoss AS 7 Development] - Re: Using Log4J in AS7

by David Jensen

David Jensen [https://community.jboss.org/people/davidj] created the discussion "Re: Using Log4J in AS7" To view the discussion, visit: https://community.jboss.org/message/776750#776750 -------------------------------------------------------------- Hi, Can someone step me thru how to setup log4j on JBoss AS7? I've tried the following. I have an EJB Jar file which has a "log4j.properties" file. This same JAR file will log correctly on other AppServers (such as Glassfish). I read else where that I must do the following in my "standalone.xml" file: +<size-rotating-file-handler+ name="*MY_LOGGER*"> <level name="TRACE"/> <formatter> <pattern-formatter pattern="%d{MMM-dd hh:mm:ss} [%c{1}] %m%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="*myLogger.log*"/> <rotate-size value="9216K"/> <max-backup-index value="3"/> +</size-rotating-file-handler>+ + + <+logger+ category="*com.mycompany*"> <level name="TRACE"/> <handlers> <handler name="*MY_LOGGER*"/> </handlers> </+logger+> I tried that and it still doesn't work I don't want to do anything fancy. All I want is for my log statements to be written in a file called "myLogger.log". Any help would be appreciated. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776750#776750] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

2
1
0 / 0

[JBoss Web Services Development] - jBoss WEb Service Tutorial

by Dipak Patel

Dipak Patel [https://community.jboss.org/people/dipak.nit] created the discussion "jBoss WEb Service Tutorial" To view the discussion, visit: https://community.jboss.org/message/762727#762727 -------------------------------------------------------------- Hi, I am new in java. I want to create web service using eclipes and want to host in jBoss. So can any one give me step by step tutorial for it. Thanks Dipak -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/762727#762727] Start a new discussion in JBoss Web Services Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

3
2
0 / 0

[JBoss AS 7 Development] - Deploy multiple resource adapters (including ironjacamar.xml)

by Alex M

Alex M [https://community.jboss.org/people/clubsoda] created the discussion "Deploy multiple resource adapters (including ironjacamar.xml)" To view the discussion, visit: https://community.jboss.org/message/746982#746982 -------------------------------------------------------------- Hi there, In JBoss 7.1.1, is it possible to deploy two resource adapter rar's at the same time which both have their own ironjacamar.xml included in META-INF? I'm trying to do that and always get the error: Invocation of listener org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor$1@4c0a2348 failed: java.lang.IllegalArgumentException: A node is already registered at '(deployment => *)(subsystem => resource-adapters)(ironjacamar => ironjacamar)' Having deployed one rar at a time does work well, but both? Thanks & regards! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/746982#746982] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

5
5
0 / 0

[PicketBox Development] - Re: LoginModule defined with cached=true, but called between web and ejb container

by Patrick Garner

Patrick Garner [https://community.jboss.org/people/pgarner] created the discussion "Re: LoginModule defined with cached=true, but called between web and ejb container" To view the discussion, visit: https://community.jboss.org/message/773387#773387 -------------------------------------------------------------- Immediately after updating an application user's password in the database, JBoss throws javax.ejb.EJBAccessException: JBAS013323: Invalid User. It appears that JBoss security attempts to reauthenticate the principal with every method invocation between web and ejb container, which fails because the principal's password has become stale. I was surprised to see the UsernamePasswordLoginModule trying to login again, with the resulting "Password invalid/Password required" error. I'm using 7.2.0.Alpha-1-SNAPSHOT. Shouldn't this problem have been resolved ( https://issues.jboss.org/browse/AS7-3498 AS7-3498)? > 00:25:35,521 ERROR [org.jboss.security] (http-/127.0.0.1:8443-2) PBOX000206: Login failure: javax.security.auth.login.FailedLoginException: PBOX000070: Password invalid/Password required > at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283) [picketbox-4.0.13.Final.jar:4.0.13.Final] > at sun.reflect.GeneratedMethodAccessor590.invoke(Unknown Source) [:1.7.0_07] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) [rt.jar:1.7.0_07] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.login(LoginContext.java:594) [rt.jar:1.7.0_07] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:408) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:333) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:354) [jboss-as-security-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.security.service.SimpleSecurityManager.push(SimpleSecurityManager.java:292) [jboss-as-security-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:49) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:45) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_07] > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:74) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at com.patrac.service.LoginHistoryService$$$view94.create(Unknown Source) [Patrac-ejb.jar:] > at com.patrac.controller.SessionManager.createLoginHistoryRecord(SessionManager.java:163) [classes:] > at com.patrac.controller.SessionManager.endOfSessionHouseKeeping(SessionManager.java:130) [classes:] > at com.patrac.controller.SessionManager.logout(SessionManager.java:87) [classes:] > at com.patrac.controller.SessionManager.changePassword(SessionManager.java:236) [classes:] > at com.patrac.controller.SessionManager$Proxy$_$$_WeldClientProxy.changePassword(SessionManager$Proxy$_$$_WeldClientProxy.java) [classes:] > at com.patrac.controller.backingbean.ChangePasswordBean.updateUserPasswordInSession(ChangePasswordBean.java:44) [classes:] > at com.patrac.controller.statemachine.effect.ChangePasswordEffect.performAction(ChangePasswordEffect.java:21) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.effect.ChangePasswordEffect.performAction(ChangePasswordEffect.java:10) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.transition.Transition.fire(Transition.java:60) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.transition.GoToWorkflowTransition.fire(GoToWorkflowTransition.java:49) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.workflow.ChangePasswordWorkflow$1.evaluate(ChangePasswordWorkflow.java:62) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.workflow.ChangePasswordWorkflow$1.evaluate(ChangePasswordWorkflow.java:56) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.event.Event.trigger(Event.java:85) [Patrac-ejb.jar:] > at com.patrac.controller.backingbean.BackingBean.dispatch(BackingBean.java:68) [classes:] > at com.patrac.controller.backingbean.ChangePasswordBean$Proxy$_$$_WeldClientProxy.dispatch(ChangePasswordBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] > at org.apache.el.parser.AstValue.invoke(AstValue.java:264) [jbossweb-7.0.17.Final.jar:] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.17.Final.jar:] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at com.patrac.filter.NoCacheFilter.doFilter(NoCacheFilter.java:46) [classes:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.17.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) [jbossweb-7.0.17.Final.jar:] > at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:897) [jbossweb-7.0.17.Final.jar:] > at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:634) [jbossweb-7.0.17.Final.jar:] > at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039) [jbossweb-7.0.17.Final.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > > > 00:25:35,566 ERROR [org.jboss.security] (http-/127.0.0.1:8443-2) PBOX000206: Login failure: javax.security.auth.login.FailedLoginException: PBOX000070: Password invalid/Password required > at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283) [picketbox-4.0.13.Final.jar:4.0.13.Final] > at sun.reflect.GeneratedMethodAccessor590.invoke(Unknown Source) [:1.7.0_07] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) [rt.jar:1.7.0_07] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) [rt.jar:1.7.0_07] > at javax.security.auth.login.LoginContext.login(LoginContext.java:594) [rt.jar:1.7.0_07] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:408) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:333) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146) [picketbox-infinispan-4.0.13.Final.jar:4.0.13.Final] > at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:354) [jboss-as-security-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.security.service.SimpleSecurityManager.push(SimpleSecurityManager.java:292) [jboss-as-security-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:49) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.security.SecurityContextInterceptor$1.run(SecurityContextInterceptor.java:45) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_07] > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:74) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ejb3.component.stateful.StatefulComponentIdInterceptor.processInvocation(StatefulComponentIdInterceptor.java:52) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at com.patrac.controller.statemachine.screen.ChangePasswordScreen$$$view77.findLeafStateAndExitUpward(Unknown Source) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.transition.Transition.exitSource(Transition.java:90) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.transition.Transition.fire(Transition.java:62) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.transition.GoToWorkflowTransition.fire(GoToWorkflowTransition.java:49) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.workflow.ChangePasswordWorkflow$1.evaluate(ChangePasswordWorkflow.java:62) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.workflow.ChangePasswordWorkflow$1.evaluate(ChangePasswordWorkflow.java:56) [Patrac-ejb.jar:] > at com.patrac.controller.statemachine.event.Event.trigger(Event.java:85) [Patrac-ejb.jar:] > at com.patrac.controller.backingbean.BackingBean.dispatch(BackingBean.java:68) [classes:] > at com.patrac.controller.backingbean.ChangePasswordBean$Proxy$_$$_WeldClientProxy.dispatch(ChangePasswordBean$Proxy$_$$_WeldClientProxy.java) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] > at org.apache.el.parser.AstValue.invoke(AstValue.java:264) [jbossweb-7.0.17.Final.jar:] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.17.Final.jar:] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.13-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.13-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.6.Final.jar:2.0.6.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.9.Final.jar:2012-08-06 19:12] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at com.patrac.filter.NoCacheFilter.doFilter(NoCacheFilter.java:46) [classes:] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.17.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.17.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) [jbossweb-7.0.17.Final.jar:] > at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:897) [jbossweb-7.0.17.Final.jar:] > at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:634) [jbossweb-7.0.17.Final.jar:] > at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2039) [jbossweb-7.0.17.Final.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > > > | | <subsystem xmlns="urn:jboss:domain:security:1.2"> | > | | <security-domains> | > | | <security-domain name="PatracSecurityDomain" cache-type="default"> | > | | <authentication> | > | | <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required"> | > | | <module-option name="dsJndiName" value="java:/postgresdb"/> | > | | <module-option name="principalsQuery" value="SELECT userpassword FROM applicationuser WHERE email=?"/> | > | | <module-option name="rolesQuery" value="SELECT r.name, 'Roles' FROM USER_ROLE ur JOIN APPLICATIONUSER u ON ur.userid=u.id JOIN ROLE r ON ur.roleid=r.id where u.email=?"/> | > | | </login-module> | > | | </authentication> | > | | </security-domain> | > | | <security-domain name="jboss-web-policy" cache-type="default"> | > | | <authorization> | > | | <policy-module code="Delegating" flag="required"/> | > | | </authorization> | > | | </security-domain> | > | | <security-domain name="jboss-ejb-policy" cache-type="default"> | > | | <authorization> | > | | <policy-module code="Delegating" flag="required"/> | > | | </authorization> | > | | </security-domain> | > | | </security-domains> | > | | </subsystem> | > -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773387#773387] Start a new discussion in PicketBox Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years

3
10
0 / 0

[JBoss Web Services Development] - Maven dependencies for JBoss WS-CXF project

by jboss_dev_16

jboss_dev_16 [https://community.jboss.org/people/jboss_dev_16] created the discussion "Maven dependencies for JBoss WS-CXF project" To view the discussion, visit: https://community.jboss.org/message/754221#754221 -------------------------------------------------------------- Hi, I'm new to JBoss WS-CXF and am looking to find what dependencies and versions, for Maven, I need to build a client and server side app. I'm running against JBoss-soa-p which I understand has JBoss WS-CXF 3.1.2 bundled within it. I've lookad at https://docs.jboss.org/author/display/JBWS/JAX-WS+User+Guide but I can't find anything there for Maven. Anyone help? Thanks, -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/754221#754221] Start a new discussion in JBoss Web Services Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

3
3
0 / 0

[JBoss AS 7 Development] - Re: CLI deployment archive problem

by Jesper Thorhauge

Jesper Thorhauge [https://community.jboss.org/people/thohawk] created the discussion "Re: CLI deployment archive problem" To view the discussion, visit: https://community.jboss.org/message/779381#779381 -------------------------------------------------------------- The "solution" was to manually copy my jdbc driver to the deploy directory, and not have inside the .war-file. Then you can reference it in your deploy.scr (in your .war-file). If you run the depoy.scr directly from within the bin directory, the file "jtds-1.2.6.jar" must be in that directory. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779381#779381] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
3
0 / 0

[JBoss AS 7 Development] - Re: Configuring jboss7 ajp connector timeout

by Nandish A

Nandish A [https://community.jboss.org/people/nandish] created the discussion "Re: Configuring jboss7 ajp connector timeout" To view the discussion, visit: https://community.jboss.org/message/778952#778952 -------------------------------------------------------------- Thanks for the reply. But I could not find anything related to timeouts in the url you have given. Sorry of I have missed it. Nandish -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778952#778952] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

4
12
0 / 0

[JBoss AS 7 Development] - Re: Apache CXF and RESTful web services...

by Stuart Douglas

Stuart Douglas [https://community.jboss.org/people/swd847] created the discussion "Re: Apache CXF and RESTful web services..." To view the discussion, visit: https://community.jboss.org/message/779402#779402 -------------------------------------------------------------- If you are using EAP, or a custom built version of AS7 upstream you should be able to get it to work by adding this into your jboss-deployment-structure.xml: <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <exclude-subsystems> <subsystem name="resteasy" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> Unfortunatly this was added after 7.1.1, however it basically means that the container will not add resteasy into your deployment, or attempt to do any jax-rs integration. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779402#779402] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
3
0 / 0

[jBPM Development] - JPAWorkingMemoryDbLogger issue on server restart

by Proteus Hades

Proteus Hades [https://community.jboss.org/people/proteus] created the discussion "JPAWorkingMemoryDbLogger issue on server restart" To view the discussion, visit: https://community.jboss.org/message/778787#778787 -------------------------------------------------------------- Hi, I'm using jpbm5.2 in my project which involves few User Tasks. I have created different methods to start and load the knowledge session and also to start and complete the user task. I'm using the JPAWorkingMemoryDbLogger to log the entering and exiting of the nodes in the log tables. The logger is initialized when ever the StatefulKnowledgeSession is created or loaded. + //load the knowledge session.+ + ksession = Configuration.loadKSession(ksessionId,+ + myJbpm.getMyEmfPersistence(),+ + myJbpm.getMyKnowledgeBase());+ + + + // Initialize logger to enter values in log table+ +JPAWorkingMemoryDbLogger myJpaLogger = new JPAWorkingMemoryDbLogger(++ksession);+ The knowledge session & process instance id created is stored in project's database, so that whenever a user log in I could get the process info and load it. Now the problem is whenever the tomcat server restarts and the knowledge session is loaded and the process continued, entries are not made in the log tables, but Task table has proper entries. When checked at the console for sql queries, whenever the tomcat restarts the 'insert into nodeinstancelog...' statements are missing. My project's working depends on the data in nodeinstancelog table which I query to check where the process has reached. So although the process has moved forward the nodeinstancelog do not have entries. Thereby crashing the whole application. This occurs only when the tomcat restarts- which occurs quite a few times where the project is intended to be deployed. The logger is giving me a hard time... kindly help. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778787#778787] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

[JBoss AS 7 Development] - Architectural overview of the AS?

by Nicklas Karlsson

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Architectural overview of the AS?" To view the discussion, visit: https://community.jboss.org/message/778269#778269 -------------------------------------------------------------- Hi, Are there any high-level architechtural overview documentation of the AS? Considering the LOC-count of the AS, getting to know the code by just browsing around is quite time-consuming. It would be nice to have some sort of overview what happens when the server boots, how subsystems are initialized, how a deployment is processed etc. People interested in the various subsystems could then venture on and document the overviews of the various subsystems (and the devs could chip in by correcting misunderstandings) -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778269#778269] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

4
8
0 / 0

[JBoss AOP Development] - Re: Problem creating service jboss.aop:service=AspectManager

by Murali K

Murali K [https://community.jboss.org/people/kmk1977] created the discussion "Re: Problem creating service jboss.aop:service=AspectManager" To view the discussion, visit: https://community.jboss.org/message/779335#779335 -------------------------------------------------------------- Not replied so far. Is this forum in active? I dont know i am new to this forum. Please extend your help. I am using jboss-4.2.3 GA. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779335#779335] Start a new discussion in JBoss AOP Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11204 -------------------------------------------------- > Jeff Mesnil wrote: > > > > I have been working on the patch CLI command to patch an AS7 installation and add to tweak the code related to module to be able to generate a correct patch generated by diffing 2 AS7 installations. > > When comparing modules to check whether they have been updated, computing the dir's checksum is not correct: > * Jar files generated during AS7 build can not have the same checksum since the creation date of the class files is store in the jar's zip entries. > => this concerns AS7's own modules (org/jboss/as/...) and also jandex jars for 3rd party libraries > > To circumvent that, instead of computing the SHA-1 of the jar files, I compute the checksum of the file's zip entries name/size/crc (ie I exclude the date metadata). > I also need to exclude some entries from the jar: > * Some java sources are generated at build time (logger and bundle classes) and embed their generation date into the code => the .class files have different size and crc > * META-INF/MANIFEST.MF and pom.properties files also contains the jar creation date => these files have different size and crc > When I replied to this before, I fear I came off more negative about it than I intended. I don't think it's the right thing to do when generating a cumulative patch. I'm not sure if it's the right thing to do with no way to turn it off when generating a one-off patch. But I can certainly imagine people preparing those would find it very useful to have a configurable option to do a generate-by-diff patch instead of a specified-content patch without having these kinds of date issues leading to irrelevant stuff ending up in the patch. --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Experimenting with Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] modified the document: "Experimenting with Single Installation Patching" To view the document, visit: https://community.jboss.org/docs/DOC-47969 -------------------------------------------------------------- Instructions for experimenting with the " https://community.jboss.org/docs/DOC-47500 Single Installation Patching" feature currently being developed. These instructions assume basic git knowledge and knowledge of how to work with the AS 7 code base. See " https://community.jboss.org/docs/DOC-15596 Hacking on JBoss AS7" for basic background. h2. Getting and Building the Source The patching feature is currently on a topic branch being maintained by Emanuel Muckenhuber. Until that branch is merged into master: 1) If you haven't already, clone the AS repo $ git clone git://github.com/jbossas/jboss-as.git 2) Add Emanuel's github repo as a remote $ cd jboss-as $ git remote add -f emanuel git://github.com/emuckenhuber/jboss-as.git 3) Checkout a new branch "patches-master" to track Emanuel's branch $ git checkout -t emanuel/patches-master 4) Build the AS $ ./build.sh add the -DskipTests option to skip running tests if you want the build to go a bit faster. h3. Generating Patches To generate a patch, you'll need 5 things: 1. An unzipped AS distribution representing the AS release being patched. This is the "applies-to-dist". This can be any AS7 release distribution, or the output of any successful build of the AS7 codebase since 7.1.0.Final was released. (Even earlier would probably work fine.) 2. An unzipped AS distribution representing the "patched" AS release. This is the "updated-dist". This is a distribution built from code that is newer than whatever went into the "applies-to" distribution. It can be a later release or build, or even the same distribution as the "applies-to-dist" that you've manually modified in some fashion. 3. An AS distribution you built following the instructions in the "Getting and Building the Source" section above. The patch generation tool is included in this distribution. If the distribution you are using for the "updated-dist" was built in that manner, then you can use it; you don't need a separate distribution. At some point we'll distribute the patch generation tool as a separate distribution, but for now it's simplest just to use an AS distribution. In the rest of this section, we'll refer to this as the "patch generation tool distribution." 4. A patch-config.xml file providing instructions about how to create the patch. See details below. 5. The filesystem location where you want the patch file to be written (including the name of the file.) To run the patch generation tool: $ cd /root/of/the/patch/generation/tool/distribution $ java -jar jboss-modules.jar -mp modules org.jboss.as.patching.generator --help INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA Usage: patch-gen.sh [args...] where args include: --applies-to-dist=<file> Filesystem path of a pristine unzip of the distribution of the version of the software to which the generated patch applies -h, --help Display this message and exit --output-file=<file> Filesystem location to which the generated patch file should be written --patch-config=<file> Filesystem path of the patch generation configuration file to use --updated-dist=<file> Filesystem path of a pristine unzip of a distribution of software which contains the changes that should be incorporated in the patch -v, --version Print version and exit To actually run the patch generation tool and not just get help output, you will need to append the --applies-to-dist, --updated-dist, --patch-config and --output-file arguments described above to the process launch command (instead of --help), with the appropriate value for each included. The patch-gen tool will attempt to use default values for --applies-to-dist, --updated-dist and --output-file, so only --patch-config absolutely needs to be specified. * Default for --updated-dist is the current working dir, or its parent if the current working dir is named bin/. The assumption here is the patch generation tool is itself being run from the --updated-dist (which is the newest dist and thus will have the newest version of the tool). The tool does a couple basic sanity checks to verify that the working dir is actually an AS distribution. If those sanity checks don't pass, the patch generation will fail with a message indicating --updated-dist needs to be specified. * Default for --applies-to-dist can be a sibling of the root of --applies-to-dist, named the same as the applies-to-version in the patch-config.xml. * Default for --output-file can be <name-of-patch-as-specified-in-patch-config>.par in the current working dir. The java command above is pretty lengthy, so we've written a shell script that does the same thing. In the source code it can be found at patching/src/main/resources/patch-gen.sh. Copy that to the bin/ dir of the patch generation tool distribution and then you can get the output above by simply doing: $ bin/patch-gen.sh --help h4. Methods of Patch Generation There are two basic methods of patch generation. Which the tool should use is declared in the patch-config.xml file: * generate-by-diff: The patch generation tool itself compares the contents of the --applies-to-dist and the --updated-dist and creates a patch. This is most useful for CP patches. +TODO for one-off patches allow an option where the diffing algorithm ignore will timestamps as described by Jeff Mesnil (http://https://community.jboss.org/wiki/SingleInstallationPatching#commen... * specified-content: The patch-config.xml file declares in detail what modules, bundles and misc files are to be added, updated or removed via the patch. This is most useful for one-off patches where the patch author knows what has changed. h4. The patch-config.xml File The patch-config.xml file provides basic metadata about the patch, along with instructions on how to generate it. The person preparing the patch creates the patch-config.xml file. +Note: the file doesn't have to be named patch-config.xml; it can be named anything.+ The simplest way to describe the file is to show a couple of examples. The full xsd for the file can be found in the AS source dist at patching/src/main/resources/patch-config.xsd. An example patch-config file for a generate-by-diff patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>6.1.0-to-6.1.1</name> <description>Cumulative patch to move from EAP 6.1.0.GA to EAP 6.1.1.GA</description> <cumulative applies-to-version="EAP 6.1.0.GA" resulting-version="EAP 6.1.1.GA"/> <generate-by-diff/> </patch-config> An example patch-config file for a specified-content patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>JBPAPP6-123</name> <description>One off patch to fix JBPAPP6-123</description> <one-off> <applies-to-version>EAP 6.1.0.GA</applies-to-version> </one-off> <specified-content> <modules> <added-module name="org.jboss.as.foo" /> <updated-module name="org.jboss.as.bar" slot="eap"/> <removed-module name="org.jboss.as.fubar" /> </modules> <misc-files> <updated-misc-content path="bin/standalone.sh" /> <updated-misc-content path="bin/standalone.bat" /> </misc-files> </specified-content> </patch-config> h3. Applying Patches Only an AS release that includes the patching feature can be patched using the patching tool. So, that means you can only experiment with applying patches to an AS distribution you built following the instructions in the "Getting and Building the Source" section above. That limits things a bit as far as what patches you can try to apply; for example you couldn't generate a patch that represents the difference between 7.1.2.Final and 7.1.3.Final and then apply it to 7.1.2.Final. To apply a patch, you need: 1. A patch file, prepared as described in the "Generating Patches" section. 2. An unzipped AS distribution that represents the "applies-to" distribution. This can be the exact same "applies-to" distribution you used when creating the patch, or, if you want to experiment with how the patch tool deals with the (typical) situation where the user has in some way modified a standard AS version, you can make some sort of modification. We use the standard AS CLI tool to provide the user interface for the patch application tool. To see how to apply the patch, cd into the root of the installation being patched, launch the CLI and get the help for the "patch" command: $ bin/jboss-cli.sh -c [standalone@localhost:9999 /] patch --help SYNOPSIS patch <action> <action_arguments>* [--override-all] [--override-modules] [--override=path(,path)*] [--preserve=path(,path)*] [--host=<host>] where <action> can be apply - apply a patch info - information about the installed patches rollback - rollback a patch that has been applied and <action_arguments> depends on the <action> ACTION: apply Apply a patch .... h3. This document won't include any more details on actually executing the patch command. Part of the goal of experimenting with it is to see if the --help output is adequate for users to understand what to do. The patch command only stages the patch (i.e. modifies the filesystem in a way that should not impact the running target process.) To actually have the patch take effect in the runtime, the target process needs to be restarted: [standalone@localhost:9999 /] :shutdown(restart=true) {"outcome" => "success"} Note that simply reloading the target process (using the :reload operation) is insufficient. +TODO add options to the patch command to automatically restart the process if staging is successful.+ h3. The patch info The patch info shows all currently active patches. In case there is no cumulative patch active it will return "base". [standalone@localhost:9999 /] patch info { "outcome" : "success", "result" : { "cumulative" : "6.1.0-to-6.1.1", "patches" : [ "JBPAPP6-123" ] } } h3. Conflict resolution Conflict dection is run for both applying and rolling back patches. In case conflicts are detected and the patch operation will fail and return all found conflicts as part of the failure-description. Since modules are not directly touched there is only a single swtich to ignore those (--override-modules). h3. Following Progress The patching feature is still under active development, so if you want update your build and see what's new: 1) cd into the git repo you cloned in step 1) of "Getting and Building the Source" above. 2) Pull down the latest $ git fetch emanuel 3) Make sure you have a clean repo $ git status 4) Rebase your branch onto the latest $ git checkout patches-master $ git rebase emanuel/patches-master 5) Build again -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47969] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[PicketBox Development] - Security Requirements Document

by Anil Saldhana

Anil Saldhana [https://community.jboss.org/people/anil.saldhana] modified the document: "Security Requirements Document" To view the document, visit: https://community.jboss.org/docs/DOC-19755 -------------------------------------------------------------- This document will collect the requirements for security for the various JBoss Community projects in one place. h2. h2. Projects Providing Requirements 1. JBoss Application Server 2. Aerogear 3. JBoss Developer Framework/JBossWay 4. RESTEasy 5. GateIN 6. DeltaSpike 7. ModeShape 8. Teiid h2. Requirements (In Progress) 1. Need simpler application security programming model. 2. Need better control over authentication mechanism. 3. Need security detached from the containers. 4. Need an Identity Management Model. (Represent Users/Roles/Groups/Attributes with databases/ldap). 5. Need Challenge/Response based authentication model. 6. Need fine grained authorization and permission model. 7. Need support for SAML2, OAuth2, JOSE. 8. Operations on the Identity Model automatically flush any authentication caches. Special requirements from DML: * Authorization framework that is compatible with the EJB security model and also integrates with EE 7 security manager requirements and AccessControlContext * Possible alternative to AccessControlContext for performance-sensitive applications * Long term, a possibly fine-grained authorization framework for server and domain management * Consolidated secure materials management (key management, certificate management, trust management) * Alternative authentication mechanisms (e.g. private key authentication, maybe revisit SRP) for web and SASL (in addition to supporting existing mechanisms such as so-called "silent" auth) * Support alternative identity/principal types (e.g. public keys, certificates) in addition to user name * Support multiple identity realms based on selection criteria (realm if supported, or other criteria such as source IP address, chosen auth mechanism, or other principal like client cert) h2. Steps Taken PicketBox5 Requirements: https://docs.jboss.org/author/display/SECURITY/PicketBox+Requirements+Doc... https://docs.jboss.org/author/display/SECURITY/PicketBox+Requirements+Doc... PicketLink3 Requirements: https://docs.jboss.org/author/display/PLINK/Requirements+Document https://docs.jboss.org/author/display/PLINK/Requirements+Document h2. Reference 1. https://community.jboss.org/docs/DOC-19232 Authentication API Design 2. https://community.jboss.org/docs/DOC-19775 Identity Model Requirements -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-19755] Create a new document in PicketBox Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Transactions Development] - Narayana Release Process

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] modified the document: "Narayana Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-17433 -------------------------------------------------------------- This page provides a list of instructions that must be done *in order* when doing a release of Narayana. h2. Check JIRA 1. Check all issues resolved. 2. Create next point release version if not exists - this is so you can push issues in step 3 below. 3. Unresolved issues should be resolved or pushed. h2. Check Hudson Ensure no test failures in the following group of hudson tests (for the branch you intend to release): * 4.16 Branch : jbossts-branch416-* * 4.17 Branch : jbossts-branch417-* * 5 Branch: jbossts-narayana-* h2. Do Release h3. Git Branches (4.17 and 5 only) Must be done first as the build-release-packages.xml relies on the tag being available for REPO in documentation quickstart narayana do BRANCH=<4.17|master> CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone mailto:git@github.com git@github.com:jbosstm/$REPO.git cd $REPOgit checkout $BRANCH find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final-SNAPSHOT/4\117\2$CURRENT\3Final/" git commit -am "Updated to 4.17.$CURRENT.Final" git tag 4.17.$CURRENT.Final find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final/4\117\2$NEXT\3Final-SNAPSHOT/" git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH --tags cd .. done h3. Update our AS7 fork BRANCH=4_BRANCH CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout $BRANCH sed -i "s/4.17.$CURRENT.Final-SNAPSHOT/4.17.$NEXT.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH h2. Build and release CURRENT=<Point version to release> mkdir -p ~/narayana/filemgmt.jboss.org/ On Linux: sshfs jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ On MacOS: sshfs -o defer_permissions jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ git clone git(a)github.com (mailto:git@github.com):jbosstm/narayana.git cd narayana git checkout 4.17.$CURRENT.Final On Linux: ant -f build-release-pkgs.xml dist downloads docs magnolia -Drsync=false On MacOS: ant -f build-release-pkgs.xml dist downloads docs magnolia h3. svn branches #Make sure your checkout has no local changes svn update svn status POINT_VERSION=5 NEXT_POINT_VERSION=6 #Update the version in text files find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/" svn commit -m "Updated to version 4.16.$POINT_VERSION.Final" #Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_4_Final/ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION" #Bump to next version using similar find to above find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/" svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" #Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as git checkout 4_16_BRANCH git pull --rebase --ff-only #Check no local changes git status sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" git push #Build and deploy the release to nexus staging: mkdir ~/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/ svn switch https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_$ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${NEXT_PO... ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia h3. h2. Release the artifact through Nexus 1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome 2. login 3. "Staging Repositories" 4. Click tickbox for your repo 5. Click "Close" 6. Don't worry about a description, just click "Close" 7. Click tickbox after it is closed 8. Click "Release" 9. Again a description doesn't matter h2. JIRA Release 1. Close all issues for the release 2. Mark as released (Need admin permissions) h2. Update Website Update the Narayana community site: * Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html * Login with credentials: Tom and Paul know these, ask them. * Documentation* Browse to 'jbosstm/documentation' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the documentation list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Downloads* Browse to 'jbosstm/downloads' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the downloads list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Announcement* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'announcement' pane * Update the announcement for this release. * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. * Release notes* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'getting started' pane on the right-hand-side * Edit the release notes url to point to the release notes for this version * Click save * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. h2. Push Upstream If appropriate for this release, update AS7. 1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7 2. create a new 'component update' issue. 1. Ensure the module is set to 'transactions' 2. select an appropriate 'fix for'. 3. Assign it to yourself. Now update the code in your fork: #cd to *your* fork of AS7 BRANCH=master # master for JBossTS-4.17.x and 7.1 for JBossTS-4.16.x JIRA=AS7-5815 PREVIOUS=4.17.1.Final CURRENT=4.17.2.Final git checkout $BRANCH git pull --rebase --ff-only upstream $BRANCH git checkout -b "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" sed -i "s/$PREVIOUS/$CURRENT/g" pom.xml git add pom.xml git commit -m "${JIRA} Upgrading JBossTS to ${CURRENT}" rm -rf ~/.m2/repository/org/jboss/jbossts rm -rf ~/.m2/repository/org/jboss/narayana ./build.sh clean install git push origin "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" 1. Raise a pull request 2. Once merged, resolve the Jira issue. h2. Promote NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;) Promote the release through the following channels: 1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org) 2. Forum 3. Blog - as appropriate -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17433] Create a new document in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Transactions Development] - Narayana Release Process

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] modified the document: "Narayana Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-17433 -------------------------------------------------------------- This page provides a list of instructions that must be done *in order* when doing a release of Narayana. h2. Check JIRA 1. Check all issues resolved. 2. Create next point release version if not exists - this is so you can push issues in step 3 below. 3. Unresolved issues should be resolved or pushed. h2. Check Hudson Ensure no test failures in the following group of hudson tests (for the branch you intend to release): * 4.16 Branch : jbossts-branch416-* * 4.17 Branch : jbossts-branch417-* * 5 Branch: jbossts-narayana-* h2. Do Release h3. Git Branches (4.17 and 5 only) Must be done first as the build-release-packages.xml relies on the tag being available for REPO in documentation quickstart narayana do BRANCH=<4.17|master> CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone mailto:git@github.com git@github.com:jbosstm/$REPO.git cd $REPOgit checkout $BRANCH find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final-SNAPSHOT/4\117\2$CURRENT\3Final/" git commit -am "Updated to 4.17.$CURRENT.Final" git tag 4.17.$CURRENT.Final find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final/4\117\2$NEXT\3Final-SNAPSHOT/" git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH --tags cd .. done h3. Update our AS7 fork BRANCH=4_BRANCH CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout $BRANCH sed -i "s/4.17.$CURRENT.Final-SNAPSHOT/4.17.$NEXT.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH h2. Build and release CURRENT=<Point version to release> mkdir -p ~/narayana/filemgmt.jboss.org/ On Linux: sshfs jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ On MacOS: sshfs -o defer_permissions jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ git clone git(a)github.com (mailto:git@github.com):jbosstm/narayana.git cd narayana git checkout 4.17.$CURRENT.Final On Linux: ant -f build-release-pkgs.xml dist downloads docs magnolia -Drsync=false On MacOS: ant -f build-release-pkgs.xml dist downloads docs magnolia h3. svn branches #Make sure your checkout has no local changes svn update svn status POINT_VERSION=5 NEXT_POINT_VERSION=6 #Update the version in text files find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/" svn commit -m "Updated to version 4.16.$POINT_VERSION.Final" #Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_4_Final/ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION" #Bump to next version using similar find to above find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/" svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" #Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as git checkout 4_16_BRANCH git pull --rebase --ff-only #Check no local changes git status sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" git push #Build and deploy the release to nexus staging: mkdir ~/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/ svn switch https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_$ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${NEXT_PO... ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia h3. h2. Release the artifact through Nexus 1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome 2. login 3. "Staging Repositories" 4. Click tickbox for your repo 5. Click "Close" 6. Don't worry about a description, just click "Close" 7. Click tickbox after it is closed 8. Click "Release" 9. Again a description doesn't matter h2. JIRA Release 1. Close all issues for the release 2. Mark as released (Need admin permissions) h2. Update Website Update the Narayana community site: * Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html * Login with credentials: Tom and Paul know these, ask them. * Documentation* Browse to 'jbosstm/documentation' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the documentation list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Downloads* Browse to 'jbosstm/downloads' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the downloads list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Announcement* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'announcement' pane * Update the announcement for this release. * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. * Release notes* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'getting started' pane on the right-hand-side * Edit the release notes url to point to the release notes for this version * Click save * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. h2. Push Upstream If appropriate for this release, update AS7. 1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7 2. create a new 'component update' issue. 1. Ensure the module is set to 'transactions' 2. select an appropriate 'fix for'. 3. Assign it to yourself. Now update the code in your fork: #cd to *your* fork of AS7 BRANCH=master # master for JBossTS-4.17.x and 7.1 for JBossTS-4.16.x JIRA=AS7-5815 PREVIOUS=4.17.1.Final CURRENT=4.17.2.Final git checkout $BRANCH git pull --rebase --ff-only upstream $BRANCH git checkout -b "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" sed -i "s/$PREVIOUS/$CURRENT/g" pom.xml git add pom.xml git commit -m "${JIRA} Upgrading JBossTS to ${CURRENT}" rm -rf ~/.m2/repository/org/jboss/jbossts rm -rf ~/.m2/repository/org/jboss/narayana build.sh clean install git push origin "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" 1. Raise a pull request 2. Once merged, resolve the Jira issue. h2. Promote NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;) Promote the release through the following channels: 1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org) 2. Forum 3. Blog - as appropriate -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17433] Create a new document in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - JBossAS 7.1.3.CR1: JBoss Solder doesn't work anymore

by Juergen Zimmermann

Juergen Zimmermann [https://community.jboss.org/people/Juergen.Zimmermann] created the discussion "JBossAS 7.1.3.CR1: JBoss Solder doesn't work anymore" To view the discussion, visit: https://community.jboss.org/message/760886#760886 -------------------------------------------------------------- I compiled JBossAS 7.1.3.CR1 and then tried to deploy my war which uses JBoss Solder 3.1.1.Final and runs fine on JBossAS 7.1.2.Final.However, during deployment I'm getting a NPE in Solder's GenericBeanExtension.registerGenericBeanObserverMethod(). Please see the stacktrace below. Any hint is very appreciated since DeltaSpike lacks e.g. all the JSF extensions being provided by Seam 3. Stacktrace: 19:58:15,920 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.deployment.unit."shop.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.war".WeldService: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : java.lang.NullPointerException at org.jboss.solder.bean.generic.GenericBeanExtension.registerGenericBeanObserverMethod(GenericBeanExtension.java:378) at sun.reflect.GeneratedMethodAccessor429.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:117) at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44) at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:85) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:75) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:60) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:38) at org.jboss.weld.bootstrap.events.ProcessObserverMethodImpl.fire(ProcessObserverMethodImpl.java:45) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:76) at org.richfaces.cdi.push.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:245) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:233) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:213) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:42) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:360) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/760886#760886] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

5
8
0 / 0

[JBoss AS 7 Development] - Re: CLI deployment archive problem

by Soto Roberto

Soto Roberto [https://community.jboss.org/people/numerico] created the discussion "Re: CLI deployment archive problem" To view the discussion, visit: https://community.jboss.org/message/779349#779349 -------------------------------------------------------------- I'm getting the exact same error, what was the resolution then? Besides, when you say +./jboss-cli.sh -c --file=deploy.scr+ does work, do you have to copy the components separately into the server? I'm getting Path /home/me/JAVA/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/jtds-1.2.6.jar doesn't exist. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779349#779349] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - CLI deployment archive

by Soto Roberto

Soto Roberto [https://community.jboss.org/people/numerico] commented on the document "CLI deployment archive" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-18945#comment-11201 -------------------------------------------------- What about deployment order? Are these instructions processed one by one or do deploy take precedence over datasource configurations, for example? --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[jBPM Development] - jbpm-designer. Get variables of task

by Sergey Kornilov

Sergey Kornilov [https://community.jboss.org/people/kornilovs] created the discussion "jbpm-designer. Get variables of task" To view the discussion, visit: https://community.jboss.org/message/779338#779338 -------------------------------------------------------------- I want to use TinyMCE+jmform for creating simple userTaskForms. I add two tabs in HTML editor window: for TinyMCE and HTML editor. Synhonized it together. Now I want get varibles of task for TinyMCE. I spied how variables gets while using "Ctrl-Z", but not understand how it can help me. Sorry for my poor english. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779338#779338] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT

by Nicklas Karlsson

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT" To view the discussion, visit: https://community.jboss.org/message/779251#779251 -------------------------------------------------------------- Strange thing is that the lookup succeds in standalone mode. Have to do some googling on how the jndi looks differ between standalone and domain modes... -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779251#779251] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
2
0 / 0

[jBPM Development] - help with email service.

by Luis Victor

Luis Victor [https://community.jboss.org/people/keymaker19] created the discussion "help with email service." To view the discussion, visit: https://community.jboss.org/message/777831#777831 -------------------------------------------------------------- Hi everybody i need help withe the email service task. I`m doing a process with two email nodes but i can figure out how to use it. I read the documentation but i need a step by step guide. Mi process is to deploy in the jbpm console so i don´t use any class with main method. Or i can do that?. Please tell me the configurations that are neccesary and where to put. Resuming, i need all the info. Thanks in advance -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777831#777831] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[JBoss Transactions Development] - Narayana Release Process

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] modified the document: "Narayana Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-17433 -------------------------------------------------------------- This page provides a list of instructions that must be done *in order* when doing a release of Narayana. h2. Check JIRA 1. Check all issues resolved. 2. Create next point release version if not exists - this is so you can push issues in step 3 below. 3. Unresolved issues should be resolved or pushed. h2. Check Hudson Ensure no test failures in the following group of hudson tests (for the branch you intend to release): * 4.16 Branch : jbossts-branch416-* * 4.17 Branch : jbossts-branch417-* * 5 Branch: jbossts-narayana-* h2. Do Release h3. Git Branches (4.17 and 5 only) Must be done first as the build-release-packages.xml relies on the tag being available For REPO in (documentation quickstart narayana); do REPO=<REPO> BRANCH=<4.17|master> CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone mailto:git@github.com git@github.com:jbosstm/$REPO.git cd $REPOgit checkout $BRANCH find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final-SNAPSHOT/4\117\2$CURRENT\3Final/" git commit -am "Updated to 4.17.$CURRENT.Final" git tag 4.17.$CURRENT.Final find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final/4\117\2$NEXT\3Final-SNAPSHOT/" git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH --tags cd .. h3. Update our AS7 fork BRANCH=4_BRANCH CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout $BRANCH sed -i "s/4.17.$CURRENT.Final-SNAPSHOT/4.17.$NEXT.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH h2. Build and release CURRENT=<Point version to release> mkdir -p ~/narayana/filemgmt.jboss.org/ On Linux: sshfs jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ On MacOS: sshfs -o defer_permissions jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ git clone git(a)github.com (mailto:git@github.com):jbosstm/narayana.git cd narayana git checkout 4.17.$CURRENT.Final On Linux: ant -f build-release-pkgs.xml dist downloads docs magnolia -Drsync=false On MacOS: ant -f build-release-pkgs.xml dist downloads docs magnolia h3. svn branches #Make sure your checkout has no local changes svn update svn status POINT_VERSION=5 NEXT_POINT_VERSION=6 #Update the version in text files find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/" svn commit -m "Updated to version 4.16.$POINT_VERSION.Final" #Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_4_Final/ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION" #Bump to next version using similar find to above find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/" svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" #Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as git checkout 4_16_BRANCH git pull --rebase --ff-only #Check no local changes git status sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" git push #Build and deploy the release to nexus staging: mkdir ~/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/ svn switch https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_$ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${NEXT_PO... ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia h3. h2. Release the artifact through Nexus 1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome 2. login 3. "Staging Repositories" 4. Click tickbox for your repo 5. Click "Close" 6. Don't worry about a description, just click "Close" 7. Click tickbox after it is closed 8. Click "Release" 9. Again a description doesn't matter h2. JIRA Release 1. Close all issues for the release 2. Mark as released (Need admin permissions) h2. Update Website Update the Narayana community site: * Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html * Login with credentials: Tom and Paul know these, ask them. * Documentation* Browse to 'jbosstm/documentation' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the documentation list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Downloads* Browse to 'jbosstm/downloads' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the downloads list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Announcement* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'announcement' pane * Update the announcement for this release. * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. * Release notes* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'getting started' pane on the right-hand-side * Edit the release notes url to point to the release notes for this version * Click save * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. h2. Push Upstream If appropriate for this release, update AS7. 1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7 2. create a new 'component update' issue. 1. Ensure the module is set to 'transactions' 2. select an appropriate 'fix for'. 3. Assign it to yourself. Now update the code in your fork: #cd to *your* fork of AS7 BRANCH=master # master for JBossTS-4.17.x and 7.1 for JBossTS-4.16.x JIRA=AS7-5815 PREVIOUS=4.17.1.Final CURRENT=4.17.2.Final git checkout $BRANCH git pull --rebase --ff-only upstream $BRANCH git checkout -b "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" sed -i "s/$PREVIOUS/$CURRENT/g" pom.xml git add pom.xml git commit -m "${JIRA} Upgrading JBossTS to ${CURRENT}" rm -rf ~/.m2/repository/org/jboss/jbossts rm -rf ~/.m2/repository/org/jboss/narayana build.sh clean install git push origin "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" 1. Raise a pull request 2. Once merged, resolve the Jira issue. h2. Promote NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;) Promote the release through the following channels: 1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org) 2. Forum 3. Blog - as appropriate -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17433] Create a new document in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Experimenting with Single Installation Patching

by Emanuel Muckenhuber

Emanuel Muckenhuber [https://community.jboss.org/people/emuckenhuber] modified the document: "Experimenting with Single Installation Patching" To view the document, visit: https://community.jboss.org/docs/DOC-47969 -------------------------------------------------------------- *+Initial draft; I haven't verified everything in this doc yet!!!+* Instructions for experimenting with the " https://community.jboss.org/docs/DOC-47500 Single Installation Patching" feature currently being developed. These instructions assume basic git knowledge and knowledge of how to work with the AS 7 code base. See " https://community.jboss.org/docs/DOC-15596 Hacking on JBoss AS7" for basic background. h2. Getting and Building the Source The patching feature is currently on a topic branch being maintained by Emanuel Muckenhuber. Until that branch is merged into master: 1) If you haven't already, clone the AS repo $ git clone git://github.com/jbossas/jboss-as.git 2) Add Emanuel's github repo as a remote $ cd jboss-as $ git remote add -f emanuel git://github.com/emuckenhuber/jboss-as.git 3) Checkout a new branch "patches-master" to track Emanuel's branch $ git checkout -t emanuel/patches-master 4) Build the AS $ ./build.sh add the -DskipTests option to skip running tests if you want the build to go a bit faster. h3. Generating Patches To generate a patch, you'll need 5 things: 1. An unzipped AS distribution representing the AS release being patched. This is the "applies-to-dist". This can be any AS7 release distribution, or the output of any successful build of the AS7 codebase since 7.1.0.Final was released. (Even earlier would probably work fine.) 2. An unzipped AS distribution representing the "patched" AS release. This is the "updated-dist". This is a distribution built from code that is newer than whatever went into the "applies-to" distribution. It can be a later release or build, or even the same distribution as the "applies-to-dist" that you've manually modified in some fashion. 3. An AS distribution you built following the instructions in the "Getting and Building the Source" section above. The patch generation tool is included in this distribution. If the distribution you are using for the "updated-dist" was built in that manner, then you can use it; you don't need a separate distribution. At some point we'll distribute the patch generation tool as a separate distribution, but for now it's simplest just to use an AS distribution. In the rest of this section, we'll refer to this as the "patch generation tool distribution." 4. A patch-config.xml file providing instructions about how to create the patch. See details below. 5. The filesystem location where you want the patch file to be written (including the name of the file.) To run the patch generation tool: $ cd /root/of/the/patch/generation/tool/distribution $ java -jar jboss-modules.jar -mp modules org.jboss.as.patching.generator --help INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA Usage: patch-gen.sh [args...] where args include: --applies-to-dist=<file> Filesystem path of a pristine unzip of the distribution of the version of the software to which the generated patch applies -h, --help Display this message and exit --output-file=<file> Filesystem location to which the generated patch file should be written --patch-config=<file> Filesystem path of the patch generation configuration file to use --updated-dist=<file> Filesystem path of a pristine unzip of a distribution of software which contains the changes that should be incorporated in the patch -v, --version Print version and exit To actually run the patch generation tool and not just get help output, you will need to append the --applies-to-dist, --updated-dist, --patch-config and --output-file arguments described above to the process launch command (instead of --help), with the appropriate value for each included. The java command above is pretty lengthy, so we've written a shell script that does the same thing. In the source code it can be found at patching/src/main/resources/patch-gen.sh. Copy that to the bin/ dir of the patch generation tool distribution and then you can get the output above by simply doing: $ bin/patch-gen.sh --help +TODO: the patch-gen tool should use sensible defaults for --applies-to-dist, --updated-dist and --output-file such that only --patch-config needs to be specified. Or, allow those locations to be specified in the patch-config.xml file itself.+ * +Default for +--updated-dist+ can be the current working dir, or its parent if the current working dir is named bin/. Apply some simple sanity checks, e.g. check for jboss-modules.jar etc. The assumption here is the tool is being run from the ++--updated-dist++ (which is the newest dist and thus will have the newest version of the tool) + * +Default for +--applies-to-dist+ can be a sibling of the root of --applies-to-dist, named the same as the applies-to-version in the patch-config.xml. + * +Default for --output-file can be patch.par in the current working dir, assuming no such file already exists+ h4. Methods of Patch Generation There are two basic methods of patch generation. Which the tool should use is declared in the patch-config.xml file: * generate-by-diff: The patch generation tool itself compares the contents of the --applies-to-dist and the --updated-dist and creates a patch. This is most useful for CP patches. +TODO for one-off patches allow an option where the diffing algorithm ignore will timestamps as described by Jeff Mesnil (http://https://community.jboss.org/wiki/SingleInstallationPatching#commen... * specified-content: The patch-config.xml file declares in detail what modules, bundles and misc files are to be added, updated or removed via the patch. This is most useful for one-off patches where the patch author knows what has changed. h4. The patch-config.xml File The patch-config.xml file provides basic metadata about the patch, along with instructions on how to generate it. The person preparing the patch creates the patch-config.xml file. +Note: the file doesn't have to be named patch-config.xml; it can be named anything.+ The simplest way to describe the file is to show a couple of examples. The full xsd for the file can be found in the AS source dist at patching/src/main/resources/patch-config.xsd. An example patch-config file for a generate-by-diff patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>6.1.0-to-6.1.1</name> <description>Cumulative patch to move from EAP 6.1.0.GA to EAP 6.1.1.GA</description> <cumulative applies-to-version="EAP 6.1.0.GA" resulting-version="EAP 6.1.1.GA"/> <generate-by-diff/> </patch-config> An example patch-config file for a specified-content patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>JBPAPP6-123</name> <description>One off patch to fix JBPAPP6-123</description> <one-off> <applies-to-version>EAP 6.1.0.GA</applies-to-version> </one-off> <specified-content> <modules> <added-module name="org.jboss.as.foo" /> <updated-module name="org.jboss.as.bar" slot="eap"/> <removed-module name="org.jboss.as.fubar" /> </modules> <misc-files> <updated-misc-content path="bin/standalone.sh" /> <updated-misc-content path="bin/standalone.bat" /> </misc-files> </specified-content> </patch-config> h3. Applying Patches Only an AS release that includes the patching feature can be patched using the patching tool. So, that means you can only experiment with applying patches to an AS distribution you built following the instructions in the "Getting and Building the Source" section above. That limits things a bit as far as what patches you can try to apply; for example you couldn't generate a patch that represents the difference between 7.1.2.Final and 7.1.3.Final and then apply it to 7.1.2.Final. To apply a patch, you need: 1. A patch file, prepared as described in the "Generating Patches" section. 2. An unzipped AS distribution that represents the "applies-to" distribution. This can be the exact same "applies-to" distribution you used when creating the patch, or, if you want to experiment with how the patch tool deals with the (typical) situation where the user has in some way modified a standard AS version, you can make some sort of modification. We use the standard AS CLI tool to provide the user interface for the patch application tool. To see how to apply the patch, cd into the root of the installation being patched, launch the CLI and get the help for the "patch" command: $ bin/jboss-cli.sh -c [standalone@localhost:9999 /] patch --help SYNOPSIS patch <action> <action_arguments>* [--override-all] [--override-modules] [--override=path(,path)*] [--preserve=path(,path)*] [--host=<host>] where <action> can be apply - apply a patch info - information about the installed patches rollback - rollback a patch that has been applied and <action_arguments> depends on the <action> ACTION: apply Apply a patch .... h3. This document won't include any more details on actually executing the patch command. Part of the goal of experimenting with it is to see if the --help output is adequate for users to understand what to do. The patch command only stages the patch (i.e. modifies the filesystem in a way that should not impact the running target process.) To actually have the patch take effect in the runtime, the target process needs to be restarted: [standalone@localhost:9999 /] :shutdown(restart=true) {"outcome" => "success"} Note that simply reloading the target process (using the :reload operation) is insufficient. +TODO add options to the patch command to automatically restart the process if staging is successful.+ h3. The patch info The patch info shows all currently active patches. In case there is no cumulative patch active it will return "base". [standalone@localhost:9999 /] patch info { "outcome" : "success", "result" : { "cumulative" : "6.1.0-to-6.1.1", "patches" : [ "JBPAPP6-123" ] } } h3. Conflict resolution Conflict dection is run for both applying and rolling back patches. In case conflicts are detected and the patch operation will fail and return all found conflicts as part of the failure-description. Since modules are not directly touched there is only a single swtich to ignore those (--override-modules). h3. Following Progress The patching feature is still under active development, so if you want update your build and see what's new: 1) cd into the git repo you cloned in step 1) of "Getting and Building the Source" above. 2) Pull down the latest $ git fetch emanuel 3) Make sure you have a clean repo $ git status 4) Rebase your branch onto the latest $ git checkout patches-master $ git rebase emanuel/patches-master 5) Build again -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47969] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Transactions Development] - Narayana Release Process

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] modified the document: "Narayana Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-17433 -------------------------------------------------------------- This page provides a list of instructions that must be done *in order* when doing a release of Narayana. h2. Check JIRA 1. Check all issues resolved. 2. Create next point release version if not exists - this is so you can push issues in step 3 below. 3. Unresolved issues should be resolved or pushed. h2. Check Hudson Ensure no test failures in the following group of hudson tests (for the branch you intend to release): * 4.16 Branch : jbossts-branch416-* * 4.17 Branch : jbossts-branch417-* * 5 Branch: jbossts-narayana-* h2. Do Release h3. Git Branches (4.17 and 5 only) Must be done first as the build-release-packages.xml relies on the tag being available For REPO in (documentation quickstart narayana); do REPO=<REPO> BRANCH=<4.17|master> CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone mailto:git@github.com git@github.com:jbosstm/$REPO.git cd $REPOgit checkout $BRANCH find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final-SNAPSHOT/4\117\2$CURRENT\3Final/" git commit -am "Updated to 4.17.$CURRENT.Final" git tag 4.17.$CURRENT.Final find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/4$[._]$17$[._]$$CURRENT$[._]$Final/4\117\2$NEXT\3Final-SNAPSHOT/" git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH --tags cd .. h3. Update our AS7 fork BRANCH=4_BRANCH CURRENT=<Point version to release> NEXT=<point version of next release, likely to be $CURRENT+1> git clone git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout $BRANCH sed -i "s/4.17.$CURRENT.Final-SNAPSHOT/4.17.$NEXT.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.17.$NEXT.Final-SNAPSHOT" git push origin $BRANCH h2. Build and release CURRENT=<Point version to release> mkdir -p ~/narayana/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/narayana/filemgmt.jboss.org/ git clone mailto:git@github.com git@github.com:jbosstm/narayana.git cd narayana git checkout 4.17.$CURRENT.Final ant -f build-release-pkgs.xml dist downloads docs magnolia h3. svn branches #Make sure your checkout has no local changes svn update svn status POINT_VERSION=5 NEXT_POINT_VERSION=6 #Update the version in text files find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/" svn commit -m "Updated to version 4.16.$POINT_VERSION.Final" #Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_4_Final/ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION" #Bump to next version using similar find to above find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/" svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" #Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as git checkout 4_16_BRANCH git pull --rebase --ff-only #Check no local changes git status sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" git push #Build and deploy the release to nexus staging: mkdir ~/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/ svn switch https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_$ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${NEXT_PO... ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia h3. h2. Release the artifact through Nexus 1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome 2. login 3. "Staging Repositories" 4. Click tickbox for your repo 5. Click "Close" 6. Don't worry about a description, just click "Close" 7. Click tickbox after it is closed 8. Click "Release" 9. Again a description doesn't matter h2. JIRA Release 1. Close all issues for the release 2. Mark as released (Need admin permissions) h2. Update Website Update the Narayana community site: * Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html * Login with credentials: Tom and Paul know these, ask them. * Documentation* Browse to 'jbosstm/documentation' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the documentation list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Downloads* Browse to 'jbosstm/downloads' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file * Right click on the new file and click 'move' * Drag the file to the top of the downloads list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Announcement* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'announcement' pane * Update the announcement for this release. * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. * Release notes* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'getting started' pane on the right-hand-side * Edit the release notes url to point to the release notes for this version * Click save * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. h2. Push Upstream If appropriate for this release, update AS7. 1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7 2. create a new 'component update' issue. 1. Ensure the module is set to 'transactions' 2. select an appropriate 'fix for'. 3. Assign it to yourself. Now update the code in your fork: #cd to *your* fork of AS7 BRANCH=master # master for JBossTS-4.17.x and 7.1 for JBossTS-4.16.x JIRA=AS7-5815 PREVIOUS=4.17.1.Final CURRENT=4.17.2.Final git checkout $BRANCH git pull --rebase --ff-only upstream $BRANCH git checkout -b "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" sed -i "s/$PREVIOUS/$CURRENT/g" pom.xml git add pom.xml git commit -m "${JIRA} Upgrading JBossTS to ${CURRENT}" rm -rf ~/.m2/repository/org/jboss/jbossts rm -rf ~/.m2/repository/org/jboss/narayana build.sh clean install git push origin "${JIRA}_Upgrading_JBossTS_to_${CURRENT}" 1. Raise a pull request 2. Once merged, resolve the Jira issue. h2. Promote NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;) Promote the release through the following channels: 1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org) 2. Forum 3. Blog - as appropriate -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17433] Create a new document in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Apache CXF and RESTful web services...

by Sergey Beryozkin

Sergey Beryozkin [https://community.jboss.org/people/sergeyb] created the discussion "Re: Apache CXF and RESTful web services..." To view the discussion, visit: https://community.jboss.org/message/779309#779309 -------------------------------------------------------------- Hi Blalux, please see my comment at https://issues.jboss.org/browse/AS7-2476?focusedCommentId=12738437&page=c... https://issues.jboss.org/browse/AS7-2476?focusedCommentId=12738437&page=c... In summary - I appreciate your support but IMHO the better approach is simply make it simpler for users to plugin alternative implementations if they choose so. Cheers, Sergey -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779309#779309] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss ESB Development] - Re: Use of ServiceInvoker to test an ESB service

by carl lee

carl lee [https://community.jboss.org/people/carl918] created the discussion "Re: Use of ServiceInvoker to test an ESB service" To view the discussion, visit: https://community.jboss.org/message/779272#779272 -------------------------------------------------------------- https://community.jboss.org/servlet/JiveServlet/showImage/2-779272-19951/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-779272-19... my project contructs like above graph,and i'sure added all jars ,but SendEsbMessage can work yet,report err following: Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:545) at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:174) at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:155) at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:197) at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:54) Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:348) at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:85) at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229) at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226) at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:532) ... 4 more Caused by: javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.apache.ws.scout.registry.BusinessQueryManagerV3Impl.findConcepts(BusinessQueryManagerV3Impl.java:516) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getJBossESBTModel(JAXRRegistryImpl.java:653) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:307) ... 8 more -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779272#779272] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss Web Services Development] - Re: Policy not supported problem

by marcin.motyka

marcin.motyka [https://community.jboss.org/people/marcin.motyka] created the discussion "Re: Policy not supported problem" To view the discussion, visit: https://community.jboss.org/message/779269#779269 -------------------------------------------------------------- I've managed to fix this issue by creating client with axis2. I also tried to use CXF, but I couldn't install it on our jboss because other webserwices stopped working. So creating an axis2 clinet and using it in regular JAX-WS webserwice was a solution. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779269#779269] Start a new discussion in JBoss Web Services Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss ESB Development] - samples\quickstarts\exceptions_faults

by carl lee

carl lee [https://community.jboss.org/people/carl918] created the discussion "samples\quickstarts\exceptions_faults" To view the discussion, visit: https://community.jboss.org/message/779247#779247 -------------------------------------------------------------- who can run the samples\quickstarts\exceptions_faults of jboss esb server 4.7 SendEsbMessage and SendEsbMessageSync i can't run both -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779247#779247] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT

by Nicklas Karlsson

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT" To view the discussion, visit: https://community.jboss.org/message/779188#779188 -------------------------------------------------------------- domain.xml? If you run standalone.sh/bat you should edit standalone.xml -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779188#779188] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[JBoss ESB Development] - no fault address defined of message

by carl lee

carl lee [https://community.jboss.org/people/carl918] created the discussion "no fault address defined of message" To view the discussion, visit: https://community.jboss.org/message/779233#779233 -------------------------------------------------------------- like title ,i want to set message's fault address ,then ,if message had err i can catch the message and i also can know what happend about the message! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779233#779233] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AOP Development] - Problem creating service jboss.aop:service=AspectManager

by Murali K

Murali K [https://community.jboss.org/people/kmk1977] created the discussion "Problem creating service jboss.aop:service=AspectManager" To view the discussion, visit: https://community.jboss.org/message/779221#779221 -------------------------------------------------------------- Hi Experts, I have been strugling with JBoss AOP execution, I did everything correct for JBoss AOP , but still i am always getting the following error. Please help me. 1)I have installed jboss-aop-jdk50.deployer 2) modified jboss-service.xml <attribute name="EnableLoadtimeWeaving">true</attribute> 3)modified run.bat with set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -javaagent:%JBOSS_ENDORSED_DIRS%\pluggable-instrumentor.jar 4)pluggable-instrumentor.jar is there in bin and as well in endorsed folder 5)I have deployed jboss-aop.xml the aspect/interceptor classes jar in /deploy folder No luck, i have been strugling for 2 days. Please help. 17:29:47,561 WARN [ServiceController] Problem creating service jboss.aop:service=AspectManager java.lang.NullPointerException at org.jboss.aop.asintegration.core.AspectManagerServiceDelegateJDK5.attachTranslator(AspectManagerServiceDelegateJDK5.java:42) at org.jboss.aop.asintegration.core.AspectManagerServiceDelegate.create(AspectManagerServiceDelegate.java:252) at org.jboss.aop.deployment.AbstractAspectManagerService.create(AbstractAspectManagerService.java:107) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at org.jboss.system.ServiceController.create(ServiceController.java:349) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.create(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:260) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Unknown Source) AND --- MBeans waiting for other MBeans --- ObjectName: jboss.aop:service=AspectManager State: FAILED Reason: java.lang.NullPointerException I Depend On: jboss.aop:service=JBoss4IntegrationWrapper --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.aop:service=AspectManager State: FAILED Reason: java.lang.NullPointerException I Depend On: jboss.aop:service=JBoss4IntegrationWrapper -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779221#779221] Start a new discussion in JBoss AOP Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Using JBoss Negotiation on AS7

by guillaume cornet

guillaume cornet [https://community.jboss.org/people/raoulpetitpied] commented on the document "Using JBoss Negotiation on AS7" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-16876#comment-11199 -------------------------------------------------- In my case, the given 'host' security-domain configuration failed, generating a 'Mechanism level: Checksum failed' exception. I successfully use this configuration : <security-domain name="host" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="storeKey" value="true"/> <module-option name="useKeyTab" value="true"/> <module-option name="principal" value="HTTP/{testserver}"/> <module-option name="keyTab" value="/home/username/service.keytab"/> <module-option name="doNotPrompt" value="true"/> <module-option name="debug" value="false"/> </login-module> </authentication> </security-domain> where {testserver} is the FQDN of the machine. --------------------------------------------------

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Using JBoss Negotiation on AS7

by guillaume cornet

guillaume cornet [https://community.jboss.org/people/raoulpetitpied] commented on the document "Using JBoss Negotiation on AS7" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-16876#comment-11198 -------------------------------------------------- @Tim H You can acheive the same results in a 'cleaner' way, with the PropertiesRolesMappingProvider. Just replace your 'RealmUsersRoles' login-module with : <mapping> <mapping-module code="PropertiesRoles" type="role"> <module-option name="rolesProperties" value="/path/to/users-roles-mapping.properties" /> </mapping-module> </mapping> And the content of '/path/to/users-roles-mapping.properties' should be username@DOMAIN=Users username2@DOMAIN=Users username3@DOMAIN=Users An alternate solution is to use the 'SimpleRolesMappingProvider' mapping-module : <mapping> <mapping-module code="SimpleRoles" type="role"> <module-option name="username@DOMAIN" value="Users" /> <module-option name="username2@DOMAIN" value="Users" /> <module-option name="username3@DOMAIN" value="Users" /> </mapping-module> </mapping> Cheers --------------------------------------------------

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Using JBoss Negotiation on AS7

by guillaume cornet

guillaume cornet [https://community.jboss.org/people/raoulpetitpied] commented on the document "Using JBoss Negotiation on AS7" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-16876#comment-11197 -------------------------------------------------- Modifying the META-INF/MANIFEST.MF is not the best solution. I recommand this one : Create a 'WEB-INF/jboss-deployment-structure.xml' which contains a dependency to 'org.jboss.security.negotiation'. Like this : <jboss-deployment-structure> <deployment> <dependencies> <module name="org.jboss.security.negotiation" /> </dependencies> </deployment> </jboss-deployment-structure> --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Configure AS7 to authenticate users with kerberos

by guillaume cornet

guillaume cornet [https://community.jboss.org/people/raoulpetitpied] created the discussion "Re: Configure AS7 to authenticate users with kerberos" To view the discussion, visit: https://community.jboss.org/message/779159#779159 -------------------------------------------------------------- Hi Antoan, I faced the same problem (e.g. 'Checksum failed'), and, in my case, I solve this error by changing the 'host' security-domain configuration. According to https://community.jboss.org/docs/DOC-16876 https://community.jboss.org/wiki/DRAFTUsingJBossNegotiationOnAS7, the 'host' security-domain should be configured like that : <security-domain name="host" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="storeKey" value="true"/> <module-option name="useKeyTab" value="true"/> <module-option name="principal" value="host/testserver@MY_REALM"/> <module-option name="keyTab" value="/home/username/service.keytab"/> <module-option name="doNotPrompt" value="true"/> <module-option name="debug" value="false"/> </login-module> </authentication> </security-domain> In my case, the solution was to configure it like that : <security-domain name="host" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="storeKey" value="true"/> <module-option name="useKeyTab" value="true"/> <module-option name="principal" value="HTTP/{testserver}"/> <module-option name="keyTab" value="/home/username/service.keytab"/> <module-option name="doNotPrompt" value="true"/> <module-option name="debug" value="false"/> </login-module> </authentication> </security-domain> where {testserver} is the FQDN of the machine. Cheers -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779159#779159] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss Transactions Development] - Added (some) exception chaining in JBossTS 4.2.3 SP5 CP10

by Eric Demorsy

Eric Demorsy [https://community.jboss.org/people/neyrick] created the discussion "Added (some) exception chaining in JBossTS 4.2.3 SP5 CP10" To view the discussion, visit: https://community.jboss.org/message/779127#779127 -------------------------------------------------------------- Hi there, Due tu a customer request, we have made a small patch to the 4.2.3 release in order to allow exceptions from the JDBC driver to be integrated as the cause of XA transaction abortions (in this case, a deferred constraint violation). I'm not sure if this release is still maintained somehow since I couldn't find a repository for it, but if it is feel free to have a look at the attached patch file and integrate it if needed. Cheers, Eric -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779127#779127] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
2
0 / 0

Community Updates, November 22 - November 29

by JBoss Community

=============================================================== Community Updates for November 22 - November 29 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,193 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,494 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Sessions and transactions [https://community.jboss.org/docs/DOC-13951] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * It's Beta Time for JBoss Tools and Developer Studio [https://community.jboss.org/community/tools/blog/2012/11/01/its-beta-time...] * JBoss Tools 3.3 and Developer Studio 5.0 Final Release! [https://community.jboss.org/community/tools/blog/2012/06/21/jboss-tools-3...] * Re: Jboss 7.1.2.Final is only for EAP? [https://community.jboss.org/message/776207#776207] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/746287#746287] * Re: Jboss and mysql connector [https://community.jboss.org/message/649296#649296] Tips and tricks - Enhance your Profile Your profile is your central identity in Community. Your colleagues will go to it to learn about you, understand your expertise, and read content you've written. Make sure it's up to date. At a minimum, you should make sure to: Upload a photo of yourself and create an avatar. An avatar is a quick thumbnail image of you. Most people use a smaller version of their photo for this but it's also fun to pick another image. Enter your contact information. This makes sure people can not only email but call or visit in person. Enter a biography and skills. Tell other people about your background and what you're an expert in. Tag yourself. Tags are a great, and succinct, way to describe yourself. This also helps Community's search engine find you if someone is looking for an expert. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Apache CXF and RESTful web services...

by Dennis Kieselhorst

Dennis Kieselhorst [https://community.jboss.org/people/kieselhorst] created the discussion "Re: Apache CXF and RESTful web services..." To view the discussion, visit: https://community.jboss.org/message/779129#779129 -------------------------------------------------------------- I'd also like to use CXF as JAX-RS provider and tried to exclude Resteasy in jboss-deployment-structure.xml as follows: <module name="org.jboss.resteasy.resteasy-atom-provider"/> <module name="org.jboss.resteasy.resteasy-cdi"/> <module name="org.jboss.resteasy.resteasy-jaxrs"/> <module name="org.jboss.resteasy.resteasy-jaxb-provider"/> <module name="org.jboss.resteasy.resteasy-jackson-provider"/> <module name="org.jboss.resteasy.resteasy-jsapi"/> <module name="org.jboss.resteasy.resteasy-multipart-provider"/> <module name="org.jboss.resteasy.async-http-servlet-30"/> Unfortunately this doesn't work: Caused by: java.lang.ClassCastException: org.jboss.resteasy.core.ServerResponse cannot be cast to org.apache.cxf.jaxrs.impl.ResponseImpl at org.apache.cxf.jaxrs.client.WebClient.handleResponse(WebClient.java:975) ... 61 more -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779129#779129] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT

by Prasad M

Prasad M [https://community.jboss.org/people/mp_lbi] created the discussion "Unable to lookup datasource in jboss-as-7.2.0.Alpha1-SNAPSHOT" To view the discussion, visit: https://community.jboss.org/message/779092#779092 -------------------------------------------------------------- I have developed a simple web application to lookup the datasource 'java:jboss/datasources/ExampleDS'. Below is the logic in the init method of my servlet: strDSName = "java:jboss/datasources/ExampleDS"; Context ctx = new InitialContext(); ds = (javax.sql.DataSource) ctx.lookup(strDSName); I am starting jboss in domain mode and when I invoke the servlet I am getting the NamingException, below is the stacktrace: 16:53:58,445 INFO [stdout] (http-localhost/127.0.0.1:8081-1) Trying to get -->java:jboss/datasources/ExampleDS 16:53:58,461 ERROR [stderr] (http-localhost/127.0.0.1:8081-1) javax.naming.NameNotFoundException: datasources/ExampleDS -- service jboss.naming.context.java.jboss.datasources.ExampleDS 16:53:58,461 ERROR [stderr] (http-localhost/127.0.0.1:8081-1) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103) *Just fyi the same code works well in jboss-as-7.1.1.Final.* Please suggest if anything else has to be done to make it work on jboss-as-7.2.0.Alpha1-SNAPSHOT PFA the sample web application. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779092#779092] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
2
0 / 0

[JBoss AS 7 Development] - JSF on AS7

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "JSF on AS7" To view the document, visit: https://community.jboss.org/docs/DOC-16546 -------------------------------------------------------------- This article documents the current status of JSF integration on AS7. It is expected that this document will evolve from being a status page to an informal documentation page. Then it will be deprecated in favor of the official documentation. *JSF Feature Status* || *Feature * || *Working in Master * || *Notes * || | Basic JSF integration | Yes | Mojarra 2.0.4-b09 was integrated on 2011-02-23 | | JSF 2.1 Support | Yes | Slated for AS7.1 | | Auto-add FacesServlet | Yes | If no FacesServlet specified in web.xml it will be automatically added according to the new rules in the FacesServlet javadoc (http://download.oracle.com/javaee/6/api/javax/faces/webapp/FacesServlet.h... This is slightly different from the auto-add feature in AS6. | | Bean Validation | Yes | Hibernate Validator is integrated with JSF as the bean validation provider. | | Legacy Facelets Apps | Yes | This refers to older JSF applications that use the JSF 1.x version of Facelets. All issues resolved. | | JSP-based JSF applciations | Yes | Fixed in Beta 2. | | JSTL | Yes | Fixed in Beta 2. | | JEE5 Injection | Yes | Fixed in CR1 | | Multi-JSF implementations | Yes | AS6 allowed you to plug in different JSF implementations. Currently in AS7, only one implementation is allowed. | | WAR_BUNDLES_JSF_IMPL | Yes | Implemented in AS7.0.1 | | Integration Tests | Partial | Several integration tests have been developed but we haven't had time to get them into the build. JSFUnit is working on AS7 now and we have a JSF smoke test. | *JSF-related Jiras for AS7:* JBAS-8876 (https://issues.jboss.org/browse/JBAS-8876) Add JSF to AS7 JBAS-8908 (https://issues.jboss.org/browse/JBAS-8908) AS6 ZipException now seen in AS7 JBAS-8909 (https://issues.jboss.org/browse/JBAS-8909) TransformerConfigurationException when reading faces-config.xml JBAS-8916 (https://issues.jboss.org/browse/JBAS-8916) Need shared TLD's for JSTL and JSF JBAS-9064 (https://issues.jboss.org/browse/JBAS-9064) Register JSF EL Resolvers with JSP JBAS-9022 (https://issues.jboss.org/browse/JBAS-9022) Changing web context with jboss-web.xml causes error in JSF AS7-1541 (https://issues.jboss.org/browse/AS7-1541) Implement WAR_BUNDLES_JSF_IMPL JBAS-9125 (https://issues.jboss.org/browse/JBAS-9125) Upgrade JSF to spec level 2.1 JBAS-5826 (https://issues.jboss.org/browse/AS7-5826) Multi-JSF Feature -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16546] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss ESB Development] - transaction of Jboss ESB

by carl lee

carl lee [https://community.jboss.org/people/carl918] created the discussion "transaction of Jboss ESB" To view the discussion, visit: https://community.jboss.org/message/779103#779103 -------------------------------------------------------------- i want to add transaction with esb message,then i can know where the message is when it has deliver fault.and how can i handle with it.for example: SystemA send message to ESB then ESB transport the message to SystemB,if the SystemB have a problem,the message send not success,how can i get the message and handl with it -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779103#779103] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Migrating from jboss5 to AS7 missing/unavailable dependencies

by chandra sekaran

chandra sekaran [https://community.jboss.org/people/chandrup] created the discussion "Re: Migrating from jboss5 to AS7 missing/unavailable dependencies" To view the discussion, visit: https://community.jboss.org/message/779077#779077 -------------------------------------------------------------- Hi Amin, I am migrating from jboss 3 to jboss 7, where did you change in your jboss-eb.xml, was it in the jboss 7 configuration files or in your application .ear files? I am also facing a similar issue, when I attempted to search for jboss-web.xml, I could get 3 such files under <myApp>.EAR/war/WEB-INF/jboss-web.xml. Should I be changing in these files? Thanks, Chandru -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779077#779077] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Remote EJB/JMS JBoss AS 7.1.1 problem

by brunothebear

brunothebear [https://community.jboss.org/people/brunothebear] created the discussion "Remote EJB/JMS JBoss AS 7.1.1 problem" To view the discussion, visit: https://community.jboss.org/message/779066#779066 -------------------------------------------------------------- Hello, Past couple of weeks ive been trying to migrate project from JBoss 4.2.2GA to JBoss 7 AS. Everything went pretty much fine till i hit the remoting part on which I've stuck for a quite time now. In JBoss 4.2.2 project uses custom login module to authenticate remote calls. The promblem is that i have trouble to get the username/password to the server so the user can eb authenticated. Ive somewhat sorted otu the EJB invocation and i do it like this. standalone.xml <security-realms> ... <security-realm name="TESTRealm"> <authentication> <jaas name="testdomain"/> </authentication> </security-realm> </security-realms> .... <subsystem xmlns="urn:jboss:domain:remoting:1.1"> <connector name="remoting-connector" socket-binding="remoting" security-realm="TESTRealm"/> </subsystem> <subsystem xmlns="urn:jboss:domain:security:1.1"> <security-domains> <security-domain name="other"> <authentication> <login-module code="UsersRoles" flag="required"/> </authentication> </security-domain> <security-domain name="jboss-web-policy"> <authorization> <policy-module code="Delegating" flag="required"/> </authorization> </security-domain> <security-domain name="jboss-ejb-policy"> <authorization> <policy-module code="Delegating" flag="required"/> </authorization> </security-domain> <security-domain name="testdomain"> <authentication> <login-module code="com.test.proj.CustomLoginModule" flag="required"> <module-option name="password-stacking" value="useFirstPass"/> <module-option name="hashAlgorithm" value="MD5"/> <module-option name="hashEncoding" value="hex"/> <module-option name="ignorePasswordCase" value="true"/> </login-module> </authentication> </security-domain> </security-domains> </subsystem> Client part: Hashtable< String, Object>props = new Hashtable< String, Object>(); props.put("jboss.naming.client.ejb.context", true); props.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming"); final String firstPassword = new String(password); org.jboss.as.naming.InitialContext ctx = new org.jboss.as.naming.InitialContext(); Properties jbossProperties = new Properties(); jbossProperties.load(EjbSupportImpl.class.getResourceAsStream("/jboss-ejb-client.properties")); jbossProperties.put("remote.connection.default.username", name); jbossProperties.put("remote.connection.default.password", firstPassword); final EJBClientConfiguration ejbClientConfiguration = new PropertiesBasedEJBClientConfiguration(jbossProperties); final ContextSelector<EJBClientContext> ejbClientContextSelector = new ConfigBasedEJBClientContextSelector(ejbClientConfiguration); EJBClientContext.setSelector(ejbClientContextSelector); final String jndiName = "ejb:ear/ejb-module/TestBean!com.test.proj.TestBean?stateful"; final Object o = ctx.lookup(jndiName); TestBean test= (TestBean) o; test.testMethod(); jboss-ejb-client-properties: remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false remote.connections=default remote.connection.default.host=localhost remote.connection.default.port=4447 remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=true remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false remote.connection.default.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS=JBOSS-LOCAL-USER With all the above everything works fine, the part that bothers me is this org.jboss.as.naming.InitialContext ctx = new org.jboss.as.naming.InitialContext(); if i use javax.naming.InitialContext instead of JBoss i get javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:121) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at com.point_fi.tms.client.communication.EjbSupport.newInitialContext(EjbSupport.java:162) at com.point_fi.tms.client.communication.EjbSupportImpl$MyLoginService.authenticate(EjbSupportImpl.java:243) at com.point_fi.tms.client.communication.EjbSupportImpl.login(EjbSupportImpl.java:179) at com.point_fi.tms.client.communication.EjbSupportImpl.getInstance(EjbSupportImpl.java:64) at com.point_fi.tms.client.Application.<init>(Application.java:35) at com.point_fi.tms.client.Application.getInstance(Application.java:59) at com.point_fi.tms.client.TMSClient.main(TMSClient.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:87) at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:56) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166) at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104) ... 16 more no errors on serverside. Anyways im ok with using method above for EJBs but then the problem comes with remote JMS where i cant acquire the connection factory i require from server via JNDI Connection factory in standalone.xml <connection-factory name="RemoteConnectionFactory"> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="RemoteConnectionFactory"/> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> </entries> </connection-factory> and the way i trie to look it up Hashtable<String, Object> env = new Hashtable<String, Object>(); env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.remote.client.InitialContextFactory"); env.put(Context.PROVIDER_URL, System.getProperty(Context.PROVIDER_URL,"remote://localhost:4447")); env.put(Context.SECURITY_PRINCIPAL, "test"); env.put(Context.SECURITY_CREDENTIALS, "123456"); InitialContext ctx = new InitialContext(env); String connectionFactoryString = "jms/RemoteConnectionFactory"; ConnectionFactoryconnectionFactory = (ConnectionFactory) ctx.lookup(connectionFactoryString); In which case im getting exception like the one above javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] Can anyone help me figure out how to properly get the ConnectionFactories/queues etc.. via remote JDNI? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779066#779066] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Experimenting with Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] modified the document: "Experimenting with Single Installation Patching" To view the document, visit: https://community.jboss.org/docs/DOC-47969 -------------------------------------------------------------- *+Initial draft; I haven't verified everything in this doc yet!!!+* Instructions for experimenting with the " https://community.jboss.org/docs/DOC-47500 Single Installation Patching" feature currently being developed. These instructions assume basic git knowledge and knowledge of how to work with the AS 7 code base. See " https://community.jboss.org/docs/DOC-15596 Hacking on JBoss AS7" for basic background. h2. Getting and Building the Source The patching feature is currently on a topic branch being maintained by Emanuel Muckenhuber. Until that branch is merged into master: 1) If you haven't already, clone the AS repo $ git clone git://github.com/jbossas/jboss-as.git 2) Add Emanuel's github repo as a remote $ cd jboss-as $ git remote add -f emanuel git://github.com/emuckenhuber/jboss-as.git 3) Checkout a new branch "patches-master" to track Emanuel's branch $ git checkout -t emanuel/patches-master 4) Build the AS $ ./build.sh add the -DskipTests option to skip running tests if you want the build to go a bit faster. h3. Generating Patches To generate a patch, you'll need 5 things: 1. An unzipped AS distribution representing the AS release being patched. This is the "applies-to-dist". This can be any AS7 release distribution, or the output of any successful build of the AS7 codebase since 7.1.0.Final was released. (Even earlier would probably work fine.) 2. An unzipped AS distribution representing the "patched" AS release. This is the "updated-dist". This is a distribution built from code that is newer than whatever went into the "applies-to" distribution. It can be a later release or build, or even the same distribution as the "applies-to-dist" that you've manually modified in some fashion. 3. An AS distribution you built following the instructions in the "Getting and Building the Source" section above. The patch generation tool is included in this distribution. If the distribution you are using for the "updated-dist" was built in that manner, then you can use it; you don't need a separate distribution. At some point we'll distribute the patch generation tool as a separate distribution, but for now it's simplest just to use an AS distribution. In the rest of this section, we'll refer to this as the "patch generation tool distribution." 4. A patch-config.xml file providing instructions about how to create the patch. See details below. 5. The filesystem location where you want the patch file to be written (including the name of the file.) To run the patch generation tool: $ cd /root/of/the/patch/generation/tool/distribution $ java -jar jboss-modules.jar -mp modules org.jboss.as.patching.generator --help INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA Usage: patch-gen.sh [args...] where args include: --applies-to-dist=<file> Filesystem path of a pristine unzip of the distribution of the version of the software to which the generated patch applies -h, --help Display this message and exit --output-file=<file> Filesystem location to which the generated patch file should be written --patch-config=<file> Filesystem path of the patch generation configuration file to use --updated-dist=<file> Filesystem path of a pristine unzip of a distribution of software which contains the changes that should be incorporated in the patch -v, --version Print version and exit To actually run the patch generation tool and not just get help output, you will need to append the --applies-to-dist, --updated-dist, --patch-config and --output-file arguments described above to the process launch command (instead of --help), with the appropriate value for each included. The java command above is pretty lengthy, so we've written a shell script that does the same thing. In the source code it can be found at patching/src/main/resources/patch-gen.sh. Copy that to the bin/ dir of the patch generation tool distribution and then you can get the output above by simply doing: $ bin/patch-gen.sh --help +TODO: the patch-gen tool should use sensible defaults for --applies-to-dist, --updated-dist and --output-file such that only --patch-config needs to be specified. Or, allow those locations to be specified in the patch-config.xml file itself.+ * +Default for +--updated-dist+ can be the current working dir, or its parent if the current working dir is named bin/. Apply some simple sanity checks, e.g. check for jboss-modules.jar etc. The assumption here is the tool is being run from the ++--updated-dist++ (which is the newest dist and thus will have the newest version of the tool) + * +Default for +--applies-to-dist+ can be a sibling of the root of --applies-to-dist, named the same as the applies-to-version in the patch-config.xml. + * +Default for --output-file can be patch.par in the current working dir, assuming no such file already exists+ h4. Methods of Patch Generation There are two basic methods of patch generation. Which the tool should use is declared in the patch-config.xml file: * generate-by-diff: The patch generation tool itself compares the contents of the --applies-to-dist and the --updated-dist and creates a patch. This is most useful for CP patches. +TODO for one-off patches allow an option where the diffing algorithm ignore will timestamps as described by Jeff Mesnil (http://https://community.jboss.org/wiki/SingleInstallationPatching#commen... * specified-content: The patch-config.xml file declares in detail what modules, bundles and misc files are to be added, updated or removed via the patch. This is most useful for one-off patches where the patch author knows what has changed. h4. The patch-config.xml File The patch-config.xml file provides basic metadata about the patch, along with instructions on how to generate it. The person preparing the patch creates the patch-config.xml file. +Note: the file doesn't have to be named patch-config.xml; it can be named anything.+ The simplest way to describe the file is to show a couple of examples. The full xsd for the file can be found in the AS source dist at patching/src/main/resources/patch-config.xsd. An example patch-config file for a generate-by-diff patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>6.1.0-to-6.1.1</name> <description>Cumulative patch to move from EAP 6.1.0.GA to EAP 6.1.1.GA</description> <cumulative applies-to-version="EAP 6.1.0.GA" resulting-version="EAP 6.1.1.GA"/> <generate-by-diff/> </patch-config> An example patch-config file for a specified-content patch: <?xml version='1.0' encoding='UTF-8'?> <patch-config xmlns="urn:jboss:patch-config:1.0"> <name>JBPAPP6-123</name> <description>One off patch to fix JBPAPP6-123</description> <one-off> <applies-to-version>EAP 6.1.0.GA</applies-to-version> </one-off> <specified-content> <modules> <added-module name="org.jboss.as.foo" /> <updated-module name="org.jboss.as.bar" slot="eap"/> <removed-module name="org.jboss.as.fubar" /> </modules> <misc-files> <updated-misc-content path="bin/standalone.sh" /> <updated-misc-content path="bin/standalone.bat" /> </misc-files> </specified-content> </patch-config> h3. Applying Patches Only an AS release that includes the patching feature can be patched using the patching tool. So, that means you can only experiment with applying patches to an AS distribution you built following the instructions in the "Getting and Building the Source" section above. That limits things a bit as far as what patches you can try to apply; for example you couldn't generate a patch that represents the difference between 7.1.2.Final and 7.1.3.Final and then apply it to 7.1.2.Final. To apply a patch, you need: 1. A patch file, prepared as described in the "Generating Patches" section. 2. An unzipped AS distribution that represents the "applies-to" distribution. This can be the exact same "applies-to" distribution you used when creating the patch, or, if you want to experiment with how the patch tool deals with the (typical) situation where the user has in some way modified a standard AS version, you can make some sort of modification. To actually apply the patch, the installation being patched needs to actually be running. It can be running a standalone server or the managed domain processes; either is ok. It can be running normally or in --admin-only mode. We use the standard AS CLI tool to provide the user interface for the patch application tool. To see how to apply the patch, cd into the root of the installation being patched, launch the CLI, connecting it to the target process and get the help for the "patch" command: $ bin/jboss-cli.sh -c [standalone@localhost:9999 /] patch --help SYNOPSIS patch <action> <action_arguments>* [--override-all] [--override-modules] [--override=path(,path)*] [--preserve=path(,path)*] [--host=<host>] where <action> can be apply - apply a patch rollback - rollback a patch that has been applied and <action_arguments> depends on the <action> ACTION: apply Apply a patch .... h3. This document won't include any more details on actually executing the patch command. Part of the goal of experimenting with it is to see if the --help output is adequate for users to understand what to do. The patch command only stages the patch (i.e. modifies the filesystem in a way that should not impact the running target process.) To actually have the patch take effect in the runtime, the target process needs to be restarted: [standalone@localhost:9999 /] :shutdown(restart=true) {"outcome" => "success"} Note that simply reloading the target process (using the :reload operation) is insufficient. +TODO add options to the patch command to automatically restart the process if staging is successful.+ h3. Following Progress The patching feature is still under active development, so if you want update your build and see what's new: 1) cd into the git repo you cloned in step 1) of "Getting and Building the Source" above. 2) Pull down the latest $ git fetch emanuel 3) Make sure you have a clean repo $ git status 4) Rebase your branch onto the latest $ git checkout patches-master $ git rebase emanuel/patches-master 5) Build again -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47969] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Jboss 7.1.1 as having problems with Picketlink 2.0.3-Final for CXF endpoints

by biswa mishra

biswa mishra [https://community.jboss.org/people/mishra900] created the discussion "Jboss 7.1.1 as having problems with Picketlink 2.0.3-Final for CXF endpoints" To view the discussion, visit: https://community.jboss.org/message/779019#779019 -------------------------------------------------------------- I am trying to develop apache CXF web service endpoints using Picketlink 2.0.3-Final.jar and deploying in Jboss 7.1.1 AS. I have updated Jboss 7.1.1 As org.picketlink modules with Picketlink 2.0.3-Final.jars as mentioned in some of the links in forum . all the examples are getting deployed and working as expected . I am planning to deploy my CXF web services as .war file in Jboss Standalone deployment . i have added <extension module="org.picketlink"/> in the standalone.xml So it means , if i will deploy *.war file , i donot need to add picketlink 2.0.3-final related jars in to web-inf\lib folder , but looks like WAR file got deployed but not started .... Hence i have added picketlink 2.0.3-final related jars in to web-inf\lib folder , and redeployed , now WAR file got deployed and started also and i am able to see CXF endpoints started also like below : 21:30:41,029 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service id=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS address=http://localhost:8080/security-token-service/PicketLinkSTS implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort wsdlLocation=null mtomEnabled=false 21:30:41,044 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service id=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP address=http://localhost:8080/security-token-service/SOAPSAMLXACMLPDP implementor=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPDP portName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPort wsdlLocation=null mtomEnabled=false *But Immediately it got failed throwing the below exception like PL00075: File could not be located :policyConfig.xml* 09:31:43,712 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {urn:picketlink:identity-federation:sts}PicketLinkSTS from WSDL: WEB-INF/wsdl/PicketLinkSTS.wsdl 09:31:50,163 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/security-token-service/PicketLinkSTS 09:31:52,303 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/C:/jboss/jboss-as-7.1.0.Final/standalone/data/wsdl/security-token-service.war/PicketLinkSTS.wsdl 09:31:53,358 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."security-token-service.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."security-token-service.war".INSTALL: Failed to process phase INSTALL of deployment "security-token-service.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: PL00075: File could not be located :policyConfig.xml at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:174) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:96) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:113) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:81) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] ... 5 more Caused by: java.lang.IllegalStateException: PL00075: File could not be located :policyConfig.xml at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.getPDP(SOAPSAMLXACMLPDP.java:115) at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.<init>(SOAPSAMLXACMLPDP.java:75) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_29] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_29] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_29] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_29] at java.lang.Class.newInstance0(Class.java:355) [rt.jar:1.6.0_29] at java.lang.Class.newInstance(Class.java:308) [rt.jar:1.6.0_29] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:170) ... 10 more This looks to me more on support issues with jboss 7.1.1 AS with Picketlink using CXF endpoints ... , any tips from the Jboss Security team will be really helpful .. Even i have tried with Jboss 7.1.0 As using Picketlink 2.0.2 -final build , same issue persists Thanks, Biswa -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779019#779019] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Logging Id's

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] modified the document: "Logging Id's" To view the document, visit: https://community.jboss.org/docs/DOC-16810 -------------------------------------------------------------- Logging id ranges for JBoss AS7 i18n message interfaces. || %1,3% *Status* || | C | = | Complete | | I | = | In Progress | | P | = | Merged, but not complete | | W | = | Waiting Merge | || *Range* || *Subsystem * || *Status * || | *10100 - 10199* | *Transaction* | C | | *10200 - 10399 * | *Clustering** * | C | | *10400 - 10499* | *Connector** * | C | | *10500 - 10599* | *CLI (not applicable) * | N/A | | *10600 - 10699* | *Controller Client* | C | | *10700 - 10799*, *18500 - 18699, 18800-18999* | *CMP* | C | | *10800 - 10899* | *Host Controller (domain packages)* | C | | *10900 - 10999, 16500 - 16599* | *Host Controller (host packages)* | C | | *11000 - 11099, 16700 - 16799* | *EE* | C | | *11100 - 11199* | *Embedded* | C | | *11200 - 11299* | *JAXRS* | C | | *11300 - 11399* | *JMX* | C | | *11400 - 11499* | *JPA* | C | | *11500 - 11599* | *Logging* | C | | *11600 - 11699* | *Messaging* | C | | *11700 - 11799* | *mod_cluster* | C | | *11800 - 11899* | *Naming* | C | | *11900 - 11999* | *OSGi* | C | | *12000 - 12099, 16600 - 16699* | *Process Controller* | C | | *12100 - 12199* | *Protocol* | C | | *12200 - 12299* | *Management Client Content* | C | | *12300 - 12399* | *Platform MBeans* | C | | *12400 - 12499* | *Threads* | C | | *12500 - 12599* | *PicketLink* | I | | *12600 - 12699* | *JSF (proposed)* | | | *12700 - 13100* | *IIOP Common (proposed)* | | | *13100 - 13199* | *JDR* | C | | *13200 - 13299* | *AppClient* | C | | *13300 - 13399* | **Security* * | C | | available block(s) | | | | *14000 - 14099* | *JAXR* | W | | *14100 - 14599* | *Ejb3* | P | | *14600 - 14899* | *Controller* | C | | *14900 - 14999* | *Deployment Repository* | C | | *15000 - 15099* | *Deployment Scanner* | C | | *15100 - 15199* | *Domain Management HTTP Interface* | C | | *15200 - 15299* | *Deployment Management* | C | | *15300 - 15399* | *Network* | C | | *15400 - 15499* | *Mail* | C | | *15500 - 15699* | *Web Services (AS subsystem)* | C | | *15700 - 15999*, *18700 - 18799* | *Server* | C | | *1**6000 - 16099* | *Weld* | C | | *16100 - 16199* | *EE Deployment* | C | | *16200 - 16299* | *Configadmin* | C | | *16300 - 16499* | *Jacorb* | C | | *10900 - 10999, 16500 - 16599* | *Host Controller (host packages)* | C | | *12000 - 12099, 16600 - 16699* | *Process Controller* | C | | *11000 - 11099, 16700 - 16799* | *EE* | C | | *16800 - 16899* | *Patching (Library)* | C | | *16900 - 16999* | *Patching (Server)* | | | *17000 - 17099* | *POJO* | C | | *17100 - 17199* | *Remoting* | W | | *17200 - 17299* | *SAR* | W | | *17300 - 17699* | *Web (reserved)* | I | | *18000 - 18399* | *Web* | C | | *18400 - 18499* | *Xts* | C | | *15700 - 15999, 18700 - 18799* | *Server* | C | | *19000-19999* | *JSR-77* | I | -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16810] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: deployment fails on jboss 7 with generic message.

by frank moss

frank moss [https://community.jboss.org/people/frankmoss] created the discussion "Re: deployment fails on jboss 7 with generic message." To view the discussion, visit: https://community.jboss.org/message/744438#744438 -------------------------------------------------------------- This was a bug in 7.1.1. and it has been fixed in 7.1.2.Final. What I did was that I downloaded the source code and replaced the ManifestClassPathProcessor.java and ServerLogger.java with the one in 7.1.2.Final. Then I built the jboss and used the server module from this build. This was the fix for me. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/744438#744438] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

3
2
0 / 0

[JBoss AS 7 Development] - Configuring jboss7 ajp connector timeout

by Nandish A

Nandish A [https://community.jboss.org/people/nandish] created the discussion "Configuring jboss7 ajp connector timeout" To view the discussion, visit: https://community.jboss.org/message/778930#778930 -------------------------------------------------------------- I am setting up Jboss7 to work with apache http using ajp. My server.xml has the following entry to open ajp port <subsystem xmlns="urn:jboss:domain:web:1.1" native="false" default-virtual-server="default-host"> <connector name="http" protocol="HTTP/1.1" scheme="http" port="8080"/> <connector name="ajp" protocol="AJP/1.3" port=8009 enabled="true" /> <virtual-server name="default-host" enable-welcome-root="false"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem> However when i try adding connectionTimeOut="10000" after port definition, I get the following error in boot.log > Caused by: > org.jboss.as.controller.persistence.ConfigurationPersistenceException: > JBAS014676: Failed to parse configuration at > > org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) > [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final] at > > org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:187) > [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.server.ServerService.boot(ServerService.java:261) > [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) > [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final] ... 1 more Caused > by: javax.xml.stream.XMLStreamException: ParseError at > [row,col]:[411,13] Message: JBAS014788: Unexpected attribute > 'connectionTimeout' encountered at > org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:104) > [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.web.WebSubsystemParser.parseConnector(WebSubsystemParser.java:831) > at > org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:389) > at > org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:60) > at > org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > [staxmapper-1.1.0.Final.jar:1.1.0.Final] at > org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > [staxmapper-1.1.0.Final.jar:1.1.0.Final] at > org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:893) > [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:329) > [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:126) > [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) > [jboss-as-server-7.1.0.Final.jar:7.1.0.Final] at > org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > [staxmapper-1.1.0.Final.jar:1.1.0.Final] at > org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > [staxmapper-1.1.0.Final.jar:1.1.0.Final] at > org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) > [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final] ... 4 more > > 15:47:20,423 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.0.Final "Thunder" stopped in 29ms My question is how do we configure timeout in jboss7. I folllowed http://docs.jboss.org/jbossweb/latest/config/ajp.html http://docs.jboss.org/jbossweb/latest/config/ajp.html and I could not make out the configuration required in server.xml . -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778930#778930] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[JBoss AS 7 Development] - Re: RESTEasy HttpProtocol Exception JBOSS AS 7.

by John Wasmat

John Wasmat [https://community.jboss.org/people/johnwasmat] created the discussion "Re: RESTEasy HttpProtocol Exception JBOSS AS 7." To view the discussion, visit: https://community.jboss.org/message/778622#778622 -------------------------------------------------------------- I tried with the 8080 port and I`m getting the "HTTP 404 Resource /queue/jmsFirstFour not found" error code in the response. Am I missing anything in the jboss configuration in hornetq-rest.xml or web.xml or standlone-full.xml? I have the queues mentioned in the standalone-full.xml <subsystem><hornetw-server> section. Thanks -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778622#778622] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [PicketBox Development] - JBoss AS7 Security Auditing

by Peter Skopek

Peter Skopek [https://community.jboss.org/people/pskopek] commented on the document "JBoss AS7 Security Auditing" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-17277#comment-11178 -------------------------------------------------- The AUDIT logger should use category org.jboss.security.audit. Then it works fine. (AS 7.2.0.Alpha1). --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[PicketBox Development] - JBoss AS7 Security Auditing

by Peter Skopek

Peter Skopek [https://community.jboss.org/people/pskopek] modified the document: "JBoss AS7 Security Auditing" To view the document, visit: https://community.jboss.org/docs/DOC-17277 -------------------------------------------------------------- h2. h2. Configure the Domain Model Logging Subsystem <subsystem xmlns="urn:jboss:domain:logging:1.1"> <console-handler name="CONSOLE" autoflush="true"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> </console-handler> <periodic-rotating-file-handler name="FILE" autoflush="true"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> <periodic-rotating-file-handler name="AUDIT" autoflush="true"> <level name="TRACE"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="audit.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> <logger category="org.jboss.security.audit"> <level name="TRACE"/> <handlers> <handler name="AUDIT"/> </handlers> </logger> <logger category="com.arjuna"> <level name="WARN"/> </logger> <logger category="org.apache.tomcat.util.modeler"> <level name="WARN"/> </logger> <logger category="sun.rmi"> <level name="WARN"/> </logger> <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> </subsystem> The key changes to the logging subsystem are: * A new logger category for "org.jboss.security.audit.providers.LogAuditProvider" is defined. * A periodic rotating file handler called "AUDIT" is defined. h2. Web Applications To enable auditing in your web applications, please configure your jboss-web.xml for your web archive. The <disable-audit> flag should be set to false. <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <security-domain>form-auth</security-domain> <disable-audit>false</disable-audit> </jboss-web> h2. h2. Quick Testing 1. Attached is the form-auth.war. Deploy it in standalone/deployments 2. Make the standalone/configuration/standalone.xml changes to the logging subsystem as defined above. 3. Start JBoss AS7 4. Access http://localhost:8080/form-auth/ http://localhost:8080/form-auth/ (User: anil Password: anil) 5. If things are working, you should see audit.log under standalone/log 1:32:27,751 TRACE [org.jboss.security.audit.providers.LogAuditProvider] (http--127.0.0.1-8080-1) [Success]principal=GenericPrincipal[anil(user,)]; Note: You will need the following security domain added to standalone.xml <security-domain name="form-auth" cache-type="default"> <authentication> <login-module code="UsersRoles" flag="required"> <module-option name="usersProperties" value="users.properties"/> <module-option name="rolesProperties" value="roles.properties"/> </login-module> </authentication> </security-domain> -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17277] Create a new document in PicketBox Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - WAR Classes visible for the Module

by Evandro Pires da Silva

Evandro Pires da Silva [https://community.jboss.org/people/evandro.pires] created the discussion "WAR Classes visible for the Module" To view the discussion, visit: https://community.jboss.org/message/778573#778573 -------------------------------------------------------------- Hi, I need to make visible my "War Classes" to a JBoss Module. I create a Module named "Frame" and this module eventually access my class com.myapp.ClassName, that this class is in my WAR. But when this happens occurs a ClassNotFoundException. How am I configure the JBoss Module to see my class in the WAR? Its possible? Thanks, -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778573#778573] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[jBPM Development] - how to re-enter the last task node when activity process node was refused ?

by lyman liu

lyman liu [https://community.jboss.org/people/lymxiang] created the discussion "how to re-enter the last task node when activity process node was refused ?" To view the discussion, visit: https://community.jboss.org/message/778495#778495 -------------------------------------------------------------- https://community.jboss.org/servlet/JiveServlet/showImage/2-778495-19931/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-778495-19... this is my test process, here is a sample scenario, about a leave process： 1. A task start and complete 2. PM agreed with A request and complete 3. now ,the activity process is DM human task. DM don't agreed with this request, I just hope re-enter PM task node in the process,and A new task instance will be created,but I don't know how to do it. and when I referred to the example http://docs.jboss.org/jbpm/v5.3/userguide/ch.flexiple-processes.html http://docs.jboss.org/jbpm/v5.3/userguide/ch.flexiple-processes.html ,still confused Could someone help meor give me some suggestions? Thanks for your help. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778495#778495] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: How to reconnect a StatefulKnowledgeSession to a process and continue the flow using jBPM5 and BRMS ?

by lyman liu

lyman liu [https://community.jboss.org/people/lymxiang] created the discussion "Re: How to reconnect a StatefulKnowledgeSession to a process and continue the flow using jBPM5 and BRMS ?" To view the discussion, visit: https://community.jboss.org/message/776352#776352 -------------------------------------------------------------- in my application ,I have disposed the session, and I'm using persistent sessions, how can I reload it ,I don't know how to do it. :-/ Please help ,thanks very much! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776352#776352] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

[JBoss AS 7 Development] - policyConfig.xml issue

by biswa mishra

biswa mishra [https://community.jboss.org/people/mishra900] created the discussion "policyConfig.xml issue" To view the discussion, visit: https://community.jboss.org/message/778433#778433 -------------------------------------------------------------- i am facing an issue with Jboss 7.1.1 as . i am using picketlink-fed-2.0.3.Final.jar with jbossxacml-2.0.8-SNAPSHOT.jar , i am seeing the below exception like : Caused by: java.lang.IllegalStateException: PL00075: File could not be located :policyConfig.xml at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.getPDP(SOAPSAMLXACMLPDP.java:115) at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.<init>(SOAPSAMLXACMLPDP.java:75) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_29] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_29] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_29] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_29] at java.lang.Class.newInstance0(Class.java:355) [rt.jar:1.6.0_29] at java.lang.Class.newInstance(Class.java:308) [rt.jar:1.6.0_29] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:170) ... 10 more so is the issue still exists as per the above mail threads ... i am actually deploying a war file in Jboss 7 as and picketlink-fed-2.0.3.Final.jar is inside web-inf\lib and jbossxacml-2.0.8-SNAPSHOT.jar is configured in jboss-deployment-structure.xml file ... still i am seeing the above exception , any suggestion will be highly appriciated ???? Thanks, Biswa -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778433#778433] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: RESTEasy HttpProtocol Exception JBOSS AS 7.

by Nicklas Karlsson

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: RESTEasy HttpProtocol Exception JBOSS AS 7." To view the discussion, visit: https://community.jboss.org/message/778268#778268 -------------------------------------------------------------- Some questions ;-) What documentation are you following? What are you trying to do? What does it have to do with RestEasy? I thought 4447 was the remoting port, can you really post json to it like that? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778268#778268] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
2
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by John Mazzitelli

John Mazzitelli [https://community.jboss.org/people/mazz] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11174 -------------------------------------------------- For the record, Brian's code is correct to support exploded deployments. To get the path, just use the File API: String urlString = new File(url.toURI()).getAbsolutePath(); contentItem.get(PATH).set(urlString); contentItem.get(ARCHIVE).set(false); I tested this and it worked in AS 7.1.1.Final. --------------------------------------------------

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Extending AS 7

by John Mazzitelli

John Mazzitelli [https://community.jboss.org/people/mazz] commented on the document "Extending AS 7" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-25627#comment-11173 -------------------------------------------------- For the record, here's some code that answers my question I had with the Mixed Approach supporing exploded deployments (I tested this and it works) - thanks to Brian for pointing me to the correct way to build the contentItem ModelNode. I put this if-stmt in there just to show you how you can do both exploded and unexploded deployment via this Mixed Approach (this is code that can go in Brian's prototype): URL url = module.getExportedResource("fibo.ear"); ModelNode contentItem = new ModelNode(); boolean explodedDeployment = true; // this is here just to keep the code around that deploys if we are unexploded if (explodedDeployment) { String urlString = new File(url.toURI()).getAbsolutePath(); contentItem.get(PATH).set(urlString); contentItem.get(ARCHIVE).set(false); } else { String urlString = url.toExternalForm(); contentItem.get(URL).set(urlString); } op.get(CONTENT).add(contentItem); So the idea is that you don't have to package fibo.ear as an unexploded deployment file in your module - you can actually package your module with fibo.ear exploded and this will enable it to be deployed properly --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "Design of AS7 multi-JSF feature" To view the document, visit: https://community.jboss.org/docs/DOC-47689 -------------------------------------------------------------- *About multi-JSF* Currently, AS7 ships with two JSF implementations, a JSF 2.1 implementation and a JSF 1.2 implementation. A web application can select which implementation is used by including a context param in web.xml. By default, it uses the JSF 2.1 imlementation. "multi-JSF" allows installation of multiple JSF implementations (and versions) on the same AS7 server. The goal is to allow use of any JSF implementation (MyFaces or Mojarra) and any version of those implementation from JSF 1.2 all the way up to the experimental JSF 2.2 versions. This is far superior to the old WAR_BUNDLES_JSF_IMPL method because JSF jars do not need to be bundled with the webapp. More importantly, "multi-JSF" provides an implementation that is fully integrated with the container. This means more efficient annotation processing, lifecycle handling, and other integration advantages. *How it works* The way multi-JSF will work is that for each JSF version, a new slot is created in the modules path under *com.sun.jsf-impl*, *javax.faces.api*, and *org.jboss.as.jsf-injection*. When the jsf-subsystem is started, it scans the module path to find all the installed JSF implementations. When the JSF subsystem deploys a web app containing the specified context param, it adds the slotted modules to the deployment. Here is an example of the context param for the latest milestone of Mojarra 2.2: <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>mojarra-2.2.0-m05</param-value> </context-param> *How a JSF implementation is installed* A single JSF implementation is installed using a https://community.jboss.org/docs/DOC-18945 CLI deployment archive. This archive includes the required jars and module.xml files. It also includes CLI scripts for installing/uninstalling the JSF impls using the https://issues.jboss.org/browse/AS7-4265 CLI module command. You execute the installation archive like this: > [standalone@localhost:9999 /] deploy <local path to archive>/install-mojarra-2.2.0-m05.cli The install script inside the archive looks like this: > module add --name=javax.faces.api --slot=mojarra-2.2.0-m05 --resources=jsf-api-2.2.0-m05.jar --module-xml=mojarra-api-module.xml > module add --name=com.sun.jsf-impl --slot=mojarra-2.2.0-m05 --resources=jsf-impl-2.2.0-m05.jar --module-xml=mojarra-impl-module.xml > module add --name=org.jboss.as.jsf-injection --slot=mojarra-2.2.0-m05 --resources=jboss-as-jsf-injection-7.2.0.Alpha1-SNAPSHOT.jar --module-xml=injection-module.xml *How the CLI deployment archives are created* A CLI deployment archive for a JSF implementation/version is created using a standalone maven project you can https://github.com/ssilvert/jboss-jsf-installer download from GitHub and run. To create an archive with the project, you call it like this: *mojarra example* > mvn -Djsf-version=2.2.0-m05 -Pmojarra clean assembly:single *myfaces example* > mvn -Djsf-version=2.1.8 -Pmyfaces clean assembly:single This pulls in the JSF resources and creates the install/uninstall scripts. It is all bundled together in an archive (zip) file that must be manually renamed with a .cli extension. *How to change the default JSF implementation in AS7* The multi-JSF feature adds a new attribute to the JSF subsystem. +default-jsf-impl-slot+ allows you to change the default JSF implementation. You just need to issue a write-attribute command and set the value to one of the active impls. Then restart AS7. https://community.jboss.org/servlet/JiveServlet/showImage/102-47689-11-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47689-1... Alternatively, you can set this in your configuration file, such as standalone.xml: <subsystem xmlns="urn:jboss:domain:jsf:1.0" default-jsf-impl-slot="mojarra-2.2.0-m05"/> To see which JSF impls are installed, you can execute the +list-active-jsf-impls+ operation. /subsystem=jsf/:list-active-jsf-impls { "outcome" => "success", "result" => [ "myfaces-2.1.8", "mojarra-2.2.0-m05", "1.2", "main" ] } *Demo* I've attached a copy of install-mojarra-2.2.0-m05.cli and install-myfaces-2.1.8.cli. You can use these *.cli files with the latest nightly build of AS7 (jboss-as-7.2.0.Alpha1-SNAPSHOT). -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47689] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11172 -------------------------------------------------- Hi Pavol, I'm not sure what may have happened. I do know that some JSF impls are incompatible with some Richfaces versions. I'm happy to report that Multi-JSF is now fully integrated into master. So you can build the very latest from https://github.com/jbossas/jboss-as here or you can wait until tomorrow and download the latest nightly build from https://github.com/jbossas/jboss-as here. Yes, it is ready for deploying apps. If you stil have a problem, please report bugs https://issues.jboss.org/browse/as7 here. Stan --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss Web Development] - Add a global valve in AS7 (7.2.x)

by Jean-Frederic Clere

Jean-Frederic Clere [https://community.jboss.org/people/jfclere] modified the document: "Add a global valve in AS7 (7.2.x)" To view the document, visit: https://community.jboss.org/docs/DOC-47954 -------------------------------------------------------------- The global valve feature has been added by pull request #3326. To use it you need to put the valve class(es) in a jar and the jar in a module, tell do that with an example: Let's use the Tomcat RemoteAddrValve. In tomcat you would have something like in server.xml <Valve className="org.apache.catalina.valves.RemoteAddrValve" deny="127.*"/> In AS7 in standalone.xml in the web subsystem: | | <valve name="myvalve" module="mymodule" class-name="org.apache.catalina.valves.RemoteAddrValve"> | | | <param param-name="deny" param-value="127.*"/> | | | </valve> | Or via the jboss-cli: ./valve=myvalve:add(class-name=org.apache.catalina.valves.RemoteAddrValve,module=mymodule,enabled=false) ./valve=myvalve:add-param(param-name=deny,param-value=127.*) ./valve=myvalve:write-attribute(name=enabled, value=true) /:reload The class needs to be in a jar. Compile the RemoteAddrValve.java from the jbossweb sources or extract it from jbossweb.jar. then create the jar: jar cvf myjar.jar org/apache/catalina/valves/RemoteAddrValve.class then create the module: mkdir modules/mymodule mkdir modules/mymodule/main mv myjar.jar modules/mymodule/main add create the modules/mymodule/main/module.xml with the content: <module xmlns="urn:jboss:module:1.1" name="mymodule"> <properties> <property name="jboss.api" value="private"/> </properties> <resources> <resource-root path="myjar.jar"/> </resources> <dependencies> <module name="sun.jdk"/> <module name="javax.servlet.api"/> <module name="org.jboss.as.web"/> </dependencies> </module> To test the valve start AS7 on 0.0.0.0 (bin/standalone.sh -b 0.0.0.0) and use curl: curl -v http://localhost:8080/ http://localhost:8080/ * About to connect() to localhost port 8080 (#0) * Trying 127.0.0.1... * connected * Connected to localhost (127.0.0.1) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.24.0 (i686-redhat-linux-gnu) libcurl/7.24.0 NSS/3.13.5.0 zlib/1.2.5 libidn/1.24 libssh2/1.4.1 > Host: localhost:8080 > Accept: */* > < HTTP/1.1 403 Forbidden < Server: Apache-Coyote/1.1 < Transfer-Encoding: chunked < Date: Mon, 26 Nov 2012 10:57:17 GMT < * Connection #0 to host localhost left intact * Closing connection #0 using curl and the hostname should give the normal AS7 page, if not try from a another box: [jfclere@neo6 ~]$ curl -v http://jfcpc:8080/ http://jfcpc:8080/ * About to connect() to jfcpc port 8080 (#0) * Trying 10.33.144.3... connected * Connected to jfcpc (10.33.144.3) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.12.6.2 zlib/1.2.3 libidn/1.9 libssh2/1.2.4 > Host: jfcpc:8080 > Accept: */* > < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Accept-Ranges: bytes < ETag: W/"2432-1353665779000" -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47954] Create a new document in JBoss Web Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Web Development] - Add a global valve in AS7 (7.2.x)

by Jean-Frederic Clere

Jean-Frederic Clere [https://community.jboss.org/people/jfclere] commented on the document "Add a global valve in AS7 (7.2.x)" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47954#comment-11171 -------------------------------------------------- The valve "org.apache.catalina.valves.RemoteAddrValve" is in jbossweb.jar to be used in webapp via jboss-web.xml. Using module="org.jboss.as.web" allows to use those valves globally without the new to build a module. --------------------------------------------------

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Web Development] - Add a global valve in AS7 (7.2.x)

by John Doyle

John Doyle [https://community.jboss.org/people/jdoyle] commented on the document "Add a global valve in AS7 (7.2.x)" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47954#comment-11170 -------------------------------------------------- I'm curious about why the class has to be extracted from JBoss Web and included in another module? Is it because JBoss Web is a private module? --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss Web Development] - Add a global valve in AS7 (7.2.x)

by Jean-Frederic Clere

Jean-Frederic Clere [https://community.jboss.org/people/jfclere] modified the document: "Add a global valve in AS7 (7.2.x)" To view the document, visit: https://community.jboss.org/docs/DOC-47954 -------------------------------------------------------------- The global valve feature has been added by pull request #3326. To use it you need to put the valve class(es) in a jar and the jar in a module, tell do that with an example: Let's use the Tomcat RemoteAddrValve. In tomcat you would have something like in server.xml <Valve className="org.apache.catalina.valves.RemoteAddrValve" deny="127.*"/> In AS7 in standalone.xml in the web subsystem: | | <valve name="myvalve" module="mymodule" class-name="org.apache.catalina.valves.RemoteAddrValve"> | | | <param param-name="deny" param-value="127.*"/> | | | </valve> | Or via the jboss-cli: ./valve=myvalve:add(class-name=org.apache.catalina.valves.RemoteAddrValve,module=mymodule,enabled=false) ./valve=myvalve:add-param(param-name=deny,param-value=127.*) ./valve=myvalve:write-attribute(name=enabled, value=true) /:reload The class needs to be in a jar (you can extract it for jbossweb.jar). jar xvf ./modules/org/jboss/as/web/main/jbossweb-7.2.0.Alpha3.jar org/apache/catalina/valves/RemoteAddrValve.class jar cvf myjar.jar org/apache/catalina/valves/RemoteAddrValve.class mkdir modules/mymodule mkdir modules/mymodule/main mv myjar.jar modules/mymodule/main add create the modules/mymodule/main/module.xml with the content: <module xmlns="urn:jboss:module:1.1" name="mymodule"> <properties> <property name="jboss.api" value="private"/> </properties> <resources> <resource-root path="myjar.jar"/> </resources> <dependencies> <module name="sun.jdk"/> <module name="javax.servlet.api"/> <module name="org.jboss.as.web"/> </dependencies> </module> To test the valve start AS7 on 0.0.0.0 (bin/standalone.sh -b 0.0.0.0) and use curl: curl -v http://localhost:8080/ http://localhost:8080/ * About to connect() to localhost port 8080 (#0) * Trying 127.0.0.1... * connected * Connected to localhost (127.0.0.1) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.24.0 (i686-redhat-linux-gnu) libcurl/7.24.0 NSS/3.13.5.0 zlib/1.2.5 libidn/1.24 libssh2/1.4.1 > Host: localhost:8080 > Accept: */* > < HTTP/1.1 403 Forbidden < Server: Apache-Coyote/1.1 < Transfer-Encoding: chunked < Date: Mon, 26 Nov 2012 10:57:17 GMT < * Connection #0 to host localhost left intact * Closing connection #0 using curl and the hostname should give the normal AS7 page, if not try from a another box: [jfclere@neo6 ~]$ curl -v http://jfcpc:8080/ http://jfcpc:8080/ * About to connect() to jfcpc port 8080 (#0) * Trying 10.33.144.3... connected * Connected to jfcpc (10.33.144.3) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.12.6.2 zlib/1.2.3 libidn/1.9 libssh2/1.2.4 > Host: jfcpc:8080 > Accept: */* > < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Accept-Ranges: bytes < ETag: W/"2432-1353665779000" -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47954] Create a new document in JBoss Web Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Hot deplyment of xsl files

by Joydeep Sarkar

Joydeep Sarkar [https://community.jboss.org/people/joydeep.sarkar] created the discussion "Hot deplyment of xsl files" To view the discussion, visit: https://community.jboss.org/message/778316#778316 -------------------------------------------------------------- Hi, I am using jboss 7.1.1 and need JSPs and XSLs to get deployed in the runtime. Though I see the issue with JSPs( https://community.jboss.org/thread/202446 https://community.jboss.org/thread/202446) is there anyway that I can have the XSLs deployed in runtime. I see glassfish is capable of XSL hot deployment. Plese advise. Regards, Joydeep -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778316#778316] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - JBoss 7 is hanging after redeploying the EAR

by S V S G Krishna Murthy K

S V S G Krishna Murthy K [https://community.jboss.org/people/murthy516] created the discussion "JBoss 7 is hanging after redeploying the EAR" To view the discussion, visit: https://community.jboss.org/message/778173#778173 -------------------------------------------------------------- Hi, I'm using Jboss 7.1.1.When I deploy an EAR,it is deploying successfully.If the server is already started and redeploying the EAR,I'm able to see server logs till certain time.But after that,it is hanging and unable to proceed and also no logs are recorded.If I restart the server,everything is working fine again. So the major problem is whenever i redeploy any ear,the JBOSS is getting hanged and unable to proceed.Is there any solution for this..And also I'm running on very good configurations. Thanks Krish -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778173#778173] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[JBoss AS 7 Development] - RESTEasy HttpProtocol Exception JBOSS AS 7.

by John Wasmat

John Wasmat [https://community.jboss.org/people/johnwasmat] created the discussion "RESTEasy HttpProtocol Exception JBOSS AS 7." To view the discussion, visit: https://community.jboss.org/message/778248#778248 -------------------------------------------------------------- Hello, I`m trying to develop a Java ReastEasy client to send messages to a hornetq queue. I followed the steps listed in the jboss documentation but I couldnt find any help to this issue Following is my client code HttpClient client = new DefaultHttpClient(); HttpPost post = new HttpPost(" http://127.0.0.1:4447/queue/jms.queue.test http://127.0.0.1:4447/queue/jms.queue.test"); JSONObject json = new JSONObject(); json.append("test", "test"); StringEntity input = new StringEntity(json.toString()); input.setContentEncoding("UTF-8"); input.setContentType("application/json"); post.setEntity(input); post.addHeader("accept", "application/json"); HttpResponse response = client.execute(post); I`m receving the following errors. a) On the cleint side Exception in thread "main" org.apache.http.ProtocolException: The server failed to respond with a valid HTTP response b) On the server side 22:51:05,530 ERROR [org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Receiv ed an invalid message length of 1347375956 I have a web.xml file that I have created based on the rest documentation and placed it in the deployements folder of the JBOSS AS 7 directory. I also have the hornetq-rest.cml file in the same folder. Both get deployed correctly. I`m not sure if this is a code issue or I`m missing any configuration on the server side. Any help would be appreciated. Thanks. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778248#778248] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[EJB3 Development] - Ejb not found on http session timeout

by Aliaksandr Stsiapanay

Aliaksandr Stsiapanay [https://community.jboss.org/people/alexdev] created the discussion "Ejb not found on http session timeout" To view the discussion, visit: https://community.jboss.org/message/761124#761124 -------------------------------------------------------------- Hi everybody! I have a problem of getting ejb local reference in Http session listener in method #sessionDestroyed(HttpSessionEvent) There is code snippet below: +@WebListener+ +public class SessionCleanUpListener implements HttpSessionListener {+ + /**+ + * @see HttpSessionListener#sessionCreated(HttpSessionEvent)+ + */+ + public void sessionCreated(HttpSessionEvent arg0) {+ + }+ + /**+ + * @see HttpSessionListener#sessionDestroyed(HttpSessionEvent)+ + */+ + public void sessionDestroyed(HttpSessionEvent arg0) {+ + ServiceLocator.getInstance().getWorkflowMessageManagerBean().removeNotPersistentItems(arg0.getSession().getId());+ + }+ +}+ ServiceLocator is a utility class to obtain ejb reference. +public class ServiceLocator {+ + private final static String JNDI_NAME_WORKFLOW_MESSAGE_MANAGER_BEAN = "java:app/EDI_EJB/WorkflowMessageManagerBean";+ + private final static ServiceLocator SERVICE_LOCATOR = new ServiceLocator();+ + private final Context context;+ + private ServiceLocator() {+ + try {+ + context = new InitialContext();+ + } catch (NamingException e) {+ + throw new RuntimeException(e);+ + }+ + }+ + public static ServiceLocator getInstance() {+ + return SERVICE_LOCATOR;+ + }+ + public WorkflowMessageManagerBeanLocal getWorkflowMessageManagerBean() {+ + try {+ + return (WorkflowMessageManagerBeanLocal) context.lookup(JNDI_NAME_WORKFLOW_MESSAGE_MANAGER_BEAN);+ + } catch (NamingException e) {+ + throw new RuntimeException(e);+ + } + + }+ +}+ When session timeout is triggered I got following exception in jboss console: 13:39:52,179 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/edi]] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Session event listener threw exception: java.lang.RuntimeException: javax.naming.NameNotFoundException: java:app/EDI_EJB/WorkflowMessageManagerBean at com.nvcm.edi.web.factory.ServiceLocator.getWorkflowMessageManagerBean(ServiceLocator.java:82) [classes(inlove) at com.nvcm.edi.web.listener.SessionCleanUpListener.sessionDestroyed(SessionCleanUpListener.java:26) [classes(inlove) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:690) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:585) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:390) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:375) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) [jbossweb-7.0.13.Final.jar(inlove) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) [jbossweb-7.0.13.Final.jar(inlove) at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_05] Caused by: javax.naming.NameNotFoundException: java:app/EDI_EJB/WorkflowMessageManagerBean at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:121) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(Unknown Source) [rt.jar:1.7.0_05] at com.nvcm.edi.web.factory.ServiceLocator.getWorkflowMessageManagerBean(ServiceLocator.java:80) [classes(inlove) ... 11 more We use Java 1.6, jboss-as-7.1.1.Final, Ejb 3 on our project. Please any help? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/761124#761124] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

[JBoss AS 7 Development] - Re: How to specify a SAR's module dependencies?

by Eduardo Martins

Eduardo Martins [https://community.jboss.org/people/emmartins] created the discussion "Re: How to specify a SAR's module dependencies?" To view the discussion, visit: https://community.jboss.org/message/752624#752624 -------------------------------------------------------------- FYI, Support for ServiceMBean and ServiceMBeanSupport development is now finalized and merged into AS source code, it will be available in AS 7.2. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/752624#752624] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[JBoss AS 7 Development] - Configuration Error JBoss AS 7 in pom.xml of maven

by Cesar Abad

Cesar Abad [https://community.jboss.org/people/cesar06ar] created the discussion "Configuration Error JBoss AS 7 in pom.xml of maven" To view the discussion, visit: https://community.jboss.org/message/778028#778028 -------------------------------------------------------------- Hola a todos soy nuevo en jboss as 7 estoy empesando con un proyecto de con seam 3 tengo generado el arquetipo con maven y configurado el pom.xml. pero a la hora de deployar con (mvn jboss-as:deploy) me lanza el siguiente error ---------------------------------------------------- cesar@hp:~/proyectos/jboss-javaee6-webapp$ mvn jboss-as:deploy [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] Unrecognised tag: 'dependencies' (position: START_TAG seen ...<id>jboss7</id>\n\t <dependencies>... @255:17) @ /usr/local/apache_maven/conf/settings.xml, line 255, column 17 [WARNING] [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Java EE 6 webapp project 0.0.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- jboss-as-maven-plugin:7.1.1.Final:deploy (default-cli) @ jboss-javaee6-webapp --- nov 23, 2012 12:59:33 AM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA nov 23, 2012 12:59:33 AM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA nov 23, 2012 12:59:33 AM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.3.GA [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7.720s [INFO] Finished at: Fri Nov 23 00:59:38 ECT 2012 [INFO] Final Memory: 7M/17M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.1.1.Final:deploy (default-cli) on project jboss-javaee6-webapp: Error executing FORCE_DEPLOY: Could not execute operation '{ [ERROR] "operation" => "read-children-names", [ERROR] "child-type" => "deployment" [ERROR] }': java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [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 read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException ------------------------------------------------------- podrian ayudarme a ver que error es, por cierto trabajo con postgresql -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/778028#778028] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Bumping slf4j version?

by Bernd Eckenfels

Bernd Eckenfels [https://community.jboss.org/people/b.eckenfels] created the discussion "Bumping slf4j version?" To view the discussion, visit: https://community.jboss.org/message/777980#777980 -------------------------------------------------------------- Hello, I noticed that AS7 7.1.1-final ships with a slf4j 1.6.1 module. There are some bugfix upgrades in the 1.6.x branch, so I wonder if you would consider bumping this version - at least for the 7.2 or next. I do know that this version is pretty independend from deployed bundles, deployments or modules but it would be good to have a on-default current environemnt. With that in mind, the 1.7.x is supposed to be API compatible but adds the additional compile feature for variable argument lists. So I would like to see a 1.7.x slf4j-api dependency in the modules especially since it makes less dependency differences for users wanting to compile explicitely for AS7 environemnt. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777980#777980] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
2
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools 3.3 with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: "How to Build JBoss Tools 3.3 with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-16604 -------------------------------------------------------------- h1. This article is superceded by https://community.jboss.org/docs/DOC-47936 How to Build JBoss Tools with Maven 3. * #This_article_is_superceded_by_How_to_Build_JBoss_Tools_with_Maven_3 This article is superceded by How to Build JBoss Tools with Maven 3. ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install_ Verify or Install ? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommanded Using published Target Platform definition (Recommanded) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Set_up Set up ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_MavenAnt_to_get_it OR, use Maven+Ant to get it **** #Use Use ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+*.* *+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.* h2. Environment Setup h3. Prerequisistes 1. Java 1.6 SDK 2. Maven 3.0.3 3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access* 4. subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected) h3. Maven and Java Make sure your maven 3 is available by default and Java 1.6 is used. mvn -version should print out something like *Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500) *Java version: 1.6.0_25*, vendor: Sun Microsystems Inc. *Java home: /usr/java/jdk1.6.0_25/jre* Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix" h3. Maven settings Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> h3. Maven & Java Memory Configuration To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX. {code} set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m {code} h2. Verify or Install ? +mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+. In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it. h2. About Target Platform and related profiles The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code. If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it. Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs: h3. Using published Target Platform definition (Recommanded) unified.target refers to the dependency as published in the Target Platfrom repository. * Pros:* No additional thing to do than invoking Maven * Always up-to-date * Cons: Speed - (to evaluate) Consume it by adding* +-Punified.target+* to you Maven invocation command-line h3. Or, getting a local copy of the Target Platform * Pros: Speed +++ * Cons: Step to be repeated whenever https://source.jboss.org/browse/JBossTools/trunk/build/target-platform/un... target platform changes h4. Set up h5. Download TP as a zip and install it by yourself You can either download the TP as a zip and unpack it into some folder on your disk. For convenience, the easiest is to unzip into jbosstools/build/target-platform/REPO/, since that's where the Maven or Ant process will by default operate. You can get it with a browser or a command line tool such as wget or curl at the following url: http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/ http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S...<actualFilename>*+.target.zip and then unzip it here (the default path for -Dlocal.site, which means you can call maven with +*-Plocal.site*+ and not need to pass in +*-Dlocal.site=file:///path/to/some/other/folder/*+ as well): unzip *.target.zip -d jbosstools/build/target-platform/REPO/ *(Note that the default path used for <local.site> will change every time a new target platform is released which is a significant change over the previous (eg., SR1, SR2), so if this breaks because the default not points at an empty folder, it's time to get a new TP! Hurray for build-time notification you're using an old target platform!)* h5. OR, use Maven+Ant to get it In that case, you also need Ant 1.8.2 or later*.* cd jbosstools/build/target-platform mvn clean install -Pget.local.target The get.local.target profile will resolve the target platform file, multiple.target, as a p2 repository on your local disk in ~/trunk/build/target-platform/REPO/. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take. Since the Maven profile is simply a wrapper call to Ant, you can also use Ant 1.8 or later directly: cd jbosstools/build/target-platform ant help # show usage instructions h4. Use Just add -*P local.site -Dlocal.site=file:///path/to/target/repository/* *NOTE:* You must specify a path starting with *file:///* (three or more slashes) to avoid errors such as "+p2.core.ProvisionException URI has an authority component+". Examples *LINUX / MAC USERS* cd build mvn clean install -U -B -fae -e -*P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/*| tee build.all.log.txt *WINDOWS USERS* cd c:\trunk\build mvn3 clean install -U -B -fae -e -Plocal.site *-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/* > build.all.log.txt h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platform and want to test it locally. Otherwise, Maven will simply retrieve parent and TP from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. This is only necessary when the TP change, prior to 3.3.Beta3 svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... *NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git.... *Instead, you can just fetch the build/ folder and one or more component folders, then as before,* *build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).* mkdir jbosstools cd jbosstools svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/build svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/jmx cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jmx* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jmx* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test cd ~/trunk/build mvn verify -P unified.target -*P jmx-bootstrap* h2. Building Everything In One Build Locally Via Commandline Assuming you have a local copy of the target platform in ${HOME}/trunk/build/target-platform/REPO/ (as explained previously: *LINUX / MAC USERS* cd build mvn clean install -P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\build mvn3 clean verify -P local.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ or mvn3 clean verify -Plocal.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt If you downloaded the zip and unpacked is somewhere else, use -Dlocal.site=file:///.../ to point at that folder instead h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-63-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/runtime.site.zip! or file:///home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., Runtime Detection depends on JBoss Common, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16604] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-47936 -------------------------------------------------------------- ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install Verify or Install? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommended Using published Target Platform definition (Recommended) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Get_it Get it ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_Maven_to_build_it OR, use Maven to build it **** #Use_it_as_a_Maven_mirror Use it as a Maven mirror ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Dealing_with_timeouts_for_tests Dealing with timeouts for tests ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-16604 How to Build JBoss Tools 3.3 with Maven 3.*+ +*Note that this article only discusses building from trunk. To work with another branch, see http://learn.github.com/p/branching.html Learn.GitHub - Branching and Merging.*+ + + +*+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.*+ + + + + h2. +Environment Setup+ h3. +Prerequisistes+ 1. +Java 1.6 SDK+ 2. +Maven 3.0.3+ 3. +About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access*+ 4. +subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected)+ h3. +Maven and Java+ +Make sure your maven 3 is available by default and Java 1.6 is used.+ + + +mvn -version+ + + +should print out something like+ + + +*Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500)+ +*Java version: 1.6.0_25*, vendor: Sun Microsystems Inc.+ +*Java home: /usr/java/jdk1.6.0_25/jre*+ +Default locale: en_US, platform encoding: UTF-8+ +OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix"+ + + h3. +Maven settings+ +Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml+ + + <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> + + +#+ +*What if Maven can't find the upstream artifacts in Nexus? / Building Parent Pom & Target Platforms Locally*+ + + +Sometimes, Maven can't find the upstream artifacts - parent pom, tycho plugins, minimum (Juno SR0) or maximum (Juno SR1 or later) target platforms. Or maybe you want to build them locally in order to see how Tycho builds them, or contribute a fix. To work around resolution problems, just build locally:+ + + cd /tmp; git clone git clone git://github.com/jbosstools/jbosstools-maven-plugins.git cd /tmp; git clone git clone git://github.com/jbosstools/jbosstools-build.git cd jbosstools-maven-plugins/tycho-plugins; mvn install; cd - cd jbosstools-build/parent; mvn install; cd - cd jbosstools-build/target-platforms; mvn install -Pjbosstools-minimum,jbosstools-maximum + + h3. +Maven & Java Memory Configuration+ + + +To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX.+ + + +{code}+ +set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m+ +{code}+ + + h2. +Verify or Install?+ ++mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+.+ +In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it.+ + + h2. +About Target Platform and related profiles+ +The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code.+ +If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it.+ + + +Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs:+ h3. +Using published Target Platform definition (Recommended)+ +unified.target refers to the dependency as published in the Target Platform repository.+ * +Pros:+* +No additional thing to do than invoking Maven+ * +Always up-to-date+ * +Cons: Speed - (to evaluate)+ +Consume it by adding* +-Punified.target+* to you Maven invocation command-line+ h3. +Or, getting a local copy of the Target Platform+ * +Pros: Speed ++++ * +Cons: Step to be repeated whenever https://github.com/jbosstools/jbosstools-build/tree/master/target-platforms target platforms change+ h4. +Get it+ h5. +Download TP as a zip and install it by yourself+ + + +You can either download the TP as a zip and unpack it into some folder on your disk. Just remember to update your #settings.xml settings.xml file to point at the location where you unpacked it.+ + + +You can get it with a browser or a command line tool such as wget or curl at the following url:+ + + + http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/e420-wtp340.target... e420-wtp340.target.zip (current minimum TP)+ + http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/e421-wtp341.target... e421-wtp341.target.zip (current maximum TP)+ + + +and then unzip it :+ + + +unzip *.target.zip -d /path/to/jbosstools-build/target-platforms/jbosstools-JunoSR0c/multiple/target/multiple.target.repo/+ + or+ +unzip *.target.zip -d /path/to/jbosstools-build/target-platforms/jbosstools-JunoSR1a/multiple/target/multiple.target.repo/+ + + h5. +OR, use Maven to build it+ +See #maven-nexus-resolution-problems Building Parent Pom & Target Platforms Locally+ +#maven-nexus-resolution-problems #h4. Use it as a Maven mirror Once you get the target platform available locally, you can use it instead of the remote sites to save time. For this, we can simply use Tycho target-platform mirroring: http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... As example, you can simply edit to your ~/.m2/settings.xml the definition of the repositories to mirror: (replace /home/hudson/static_build_env/jbds/.... by a path where your local repository actuaaly stands) <settings> <mirrors>  <mirror> <id>jenkins.jbosstools-JunoSR0c</id> <mirrorOf> http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR0c/e420-wtp340.target/</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbosstools-JunoSR1a</id> <mirrorOf> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target/</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR0c</id> <mirrorOf> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju... http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR0c/jbds600-e420-wtp340.target/</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR1a</id> <mirrorOf> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju... http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR1a/jbds600-e421-wtp341.target/</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> </mirrors> </settings> h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platforms and want to test local changes. Otherwise, Maven will simply retrieve parent and TP definitions from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. See #maven-nexus-resolution-problems Building Parent Pom & Target Platforms Locally h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jbosstools-server* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jbosstools-server* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test cd ~/trunk/jbosstools-server mvn verify -P unified.target -*Pbootstrap* h2. Building Everything In One Build Locally Via Commandline *LINUX / MAC USERS* cd jbosstools-build mvn clean install -gs ~/.m2/settings.xml | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\jbosstools-build mvn3 clean verify -gs file:///${user.home}/.m2/settings.xml or mvn3 clean verify -gs file:///${user.home}/.m2/settings.xml > build.all.log.txt Remember to adjust your #settings.xml settings.xml file to specify where you have your local target platform mirror built (or where you downloaded & unpacked a target platform zip. Windows users, if you don't have a .m2 folder, see http://stackoverflow.com/questions/6081617/missing-maven-m2-folder this article. h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -B -fae -e+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools-server/site/target/server.site-*.zip! or file:///home/rob/code/jbtools/jbosstools-server/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., jbosstools-server depends on jbosstools-base, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. Dealing with timeouts for tests (To be rewritten soon...) http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf + -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47936] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-47936 -------------------------------------------------------------- ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install_ Verify or Install ? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommanded Using published Target Platform definition (Recommanded) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Get_it Get it ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_Maven_to_build_it OR, use Maven to build it **** #Use_it_as_a_Maven_mirror Use it as a Maven mirror ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Dealing_with_timeouts_for_tests Dealing with timeouts for tests ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-16604 How to Build JBoss Tools 3.3 with Maven 3.*+ +*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+*.* *+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.* h2. Environment Setup h3. Prerequisistes 1. Java 1.6 SDK 2. Maven 3.0.3 3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access* 4. subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected) h3. Maven and Java Make sure your maven 3 is available by default and Java 1.6 is used. mvn -version should print out something like *Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500) *Java version: 1.6.0_25*, vendor: Sun Microsystems Inc. *Java home: /usr/java/jdk1.6.0_25/jre* Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix" h3. Maven settings Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> # *What if Maven can't find the upstream artifacts in Nexus?* Sometimes, Maven can't find the upstream artifacts - parent pom, tycho plugins, minimum (Juno SR0) or maximum (Juno SR1 or later) target platforms. To work around this, just build them locally: cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ mvn install -U -f build/parent/pom.xml mvn install -U -f build/tycho-plugins/pom.xml mvn install -U -f build/target-platforms/pom.xml -Pjbosstools-maximum,jbosstools-minimum h3. Maven & Java Memory Configuration To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX. {code} set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m {code} h2. Verify or Install ? +mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+. In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it. h2. About Target Platform and related profiles The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code. If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it. Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs: h3. Using published Target Platform definition (Recommanded) unified.target refers to the dependency as published in the Target Platfrom repository. * Pros:* No additional thing to do than invoking Maven * Always up-to-date * Cons: Speed - (to evaluate) Consume it by adding* +-Punified.target+* to you Maven invocation command-line h3. Or, getting a local copy of the Target Platform * Pros: Speed +++ * Cons: Step to be repeated whenever https://source.jboss.org/browse/JBossTools/trunk/build/target-platform/un... target platform changes h4. Get it h5. Download TP as a zip and install it by yourself You can either download the TP as a zip and unpack it into some folder on your disk. Just remember to update your #settings.xml settings.xml file to point at the location where you unpacked it. You can get it with a browser or a command line tool such as wget or curl at the following url: http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/e420-wtp340.target... e420-wtp340.target.zip (current minimum TP) http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/e421-wtp341.target... e421-wtp341.target.zip (current maximum TP) and then unzip it : unzip *.target.zip -d /path/to/jbosstools-build/target-platforms/jbosstools-JunoSR0c/multiple/target/multiple.target.repo/ or unzip *.target.zip -d /path/to/jbosstools-build/target-platforms/jbosstools-JunoSR1a/multiple/target/multiple.target.repo/ h5. OR, use Maven to build it Starting from https://github.com/jbosstools/jbosstools-build/ jbosstools-build: cd target-platforms/<choose_a_target_to_build>/multiple mvn install By default, a Maven profile +multiple2repo+ is enabled. You can see the result repo in +target/multiple.target.repo+. This output repo can be used as a mirror for unified.target. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take. # h4. Use it as a Maven mirror Once you get the target platform available locally, you can use it instead of the remote sites to save time. For this, we can simply use Tycho target-platform mirroring: http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... As example, you can simply edit to your ~/.m2/settings.xml the definition of the repositories to mirror: (replace /home/hudson/static_build_env/jbds/.... by a path where your local repository actuaaly stands) <settings> <mirrors>  <mirror> <id>jenkins.jbosstools-JunoSR0c</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR0c/e420-wtp340.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbosstools-JunoSR1a</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR0c</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR0c/jbds600-e420-wtp340.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR1a</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR1a/jbds600-e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> </mirrors> </settings> h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platform and want to test it locally. Otherwise, Maven will simply retrieve parent and TP from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. This is only necessary when the TP change, prior to 3.3.Beta3 svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools cd jbosstools-build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... *NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git.... *Instead, you can just fetch the build/ folder and one or more component folders, then as before,* *build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).* mkdir jbosstools cd jbosstools svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/build svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/jmx cd jbosstools-build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jmx* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jmx* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test *TODO: THIS NEEDS TO BE REWRITTEN SINCE WE ARE IN GITHUB NOW* cd ~/trunk/jbosstools-build mvn verify -P unified.target -*P jmx-bootstrap* h2. Building Everything In One Build Locally Via Commandline *LINUX / MAC USERS* cd jbosstools-build mvn clean install -gs ~/.m2/settings.xml | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\jbosstools-build mvn3 clean verify -P local.site -gs file:///${user.home}/.m2/settings.xml or mvn3 clean verify -Plocal.site -gs file:///${user.home}/.m2/settings.xml > build.all.log.txt Remember to adjust your #settings.xml settings.xml file to specify where you have your local target platform mirror built (or where you downloaded & unpacked a target platform zip. Windows users, if you don't have a .m2 folder, see http://stackoverflow.com/questions/6081617/missing-maven-m2-folder this article. h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/runtime.site.zip! or file:///home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., Runtime Detection depends on JBoss Common, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. Dealing with timeouts for tests (To be rewritten soon...) http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47936] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] created the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-47936 -------------------------------------------------------------- ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install_ Verify or Install ? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommanded Using published Target Platform definition (Recommanded) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Get_it Get it ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_Maven_to_get_it OR, use Maven to get it **** #Use_it_as_Maven_mirror Use it as Maven mirror ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Dealing_with_timeouts_for_tests Dealing with timeouts for tests ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-15513 How to Build JBoss Tools 3.2 with Maven 3.*+ +*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+*.* *+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.* h2. Environment Setup h3. Prerequisistes 1. Java 1.6 SDK 2. Maven 3.0.3 3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access* 4. subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected) h3. Maven and Java Make sure your maven 3 is available by default and Java 1.6 is used. mvn -version should print out something like *Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500) *Java version: 1.6.0_25*, vendor: Sun Microsystems Inc. *Java home: /usr/java/jdk1.6.0_25/jre* Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix" h3. Maven settings Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> # *What if Maven can't find the upstream artifacts in Nexus?* Sometimes, Maven can't find the upstream artifacts - parent pom, tycho plugins, minimum (Juno SR0) or maximum (Juno SR1 or later) target platforms. To work around this, just build them locally: cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ mvn install -U -f build/parent/pom.xml mvn install -U -f build/tycho-plugins/pom.xml mvn install -U -f build/target-platforms/pom.xml -Pjbosstools-maximum,jbosstools-minimum h3. Maven & Java Memory Configuration To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX. {code} set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m {code} h2. Verify or Install ? +mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+. In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it. h2. About Target Platform and related profiles The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code. If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it. Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs: h3. Using published Target Platform definition (Recommanded) unified.target refers to the dependency as published in the Target Platfrom repository. * Pros:* No additional thing to do than invoking Maven * Always up-to-date * Cons: Speed - (to evaluate) Consume it by adding* +-Punified.target+* to you Maven invocation command-line h3. Or, getting a local copy of the Target Platform * Pros: Speed +++ * Cons: Step to be repeated whenever https://source.jboss.org/browse/JBossTools/trunk/build/target-platform/un... target platform changes h4. Get it h5. Download TP as a zip and install it by yourself You can either download the TP as a zip and unpack it into some folder on your disk. For convenience, the easiest is to unzip into jbosstools/build/target-platform/REPO/, since that's where the Maven or Ant process will by default operate. You can get it with a browser or a command line tool such as wget or curl at the following url: http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/e420-wtp340.target... e420-wtp340.target.zip (current minimum TP) http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/e421-wtp341.target... e421-wtp341.target.zip (current maximum TP) and then unzip it : unzip *.target.zip -d /path/to/my jbosstools/build/target-platforms/jbosstools-JunoSR0c/local/target/REPO/ or unzip *.target.zip -d /path/to/my jbosstools/build/target-platforms/jbosstools-JunoSR1a/local/target/REPO/ *(Note that the default path used for <local.site> will change every time a new target platform is released which is a significant change over the previous (eg., SR1, SR2), so if this breaks because the default not points at an empty folder, it's time to get a new TP! Hurray for build-time notification you're using an old target platform!)* h5. OR, use Maven to get it Starting from jbosstools-builds: cd target-platforms/<choose_a_target_to_build>/multiple mvn install By default, a Maven profile +multiple2repo+ is enabled. You can see the result repo in target/multiple.target.repo. This output repo can be used as a mirror for unified.target. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take. h4. Use it as Maven mirror Once you get the target platform available locally, you can use it instead of the remote sites to save time. For this, we can simply use Tycho target-platform mirroring: http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... As example, you can simply edit to your ~/.m2/settings.xml the definition of the repositories to mirror: (replace /ho,e/hudson/static_build_env/jbds/.... by a path where your local repository actuaaly stands) <settings> <mirrors>  <mirror> <id>jenkins.jbosstools-JunoSR0c</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR0c/e420-wtp340.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbosstools-JunoSR1a</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR0c</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR0c/jbds600-e420-wtp340.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR1a</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR1a/jbds600-e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> </mirrors> </settings> h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platform and want to test it locally. Otherwise, Maven will simply retrieve parent and TP from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. This is only necessary when the TP change, prior to 3.3.Beta3 svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... *NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git.... *Instead, you can just fetch the build/ folder and one or more component folders, then as before,* *build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).* mkdir jbosstools cd jbosstools svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/build svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/jmx cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jmx* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jmx* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test cd ~/trunk/build mvn verify -P unified.target -*P jmx-bootstrap* h2. Building Everything In One Build Locally Via Commandline Assuming you have a local copy of the target platform in ${HOME}/trunk/build/target-platform/REPO/ (as explained previously: *LINUX / MAC USERS* cd build mvn clean install -P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\build mvn3 clean verify -P local.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ or mvn3 clean verify -Plocal.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt If you downloaded the zip and unpacked is somewhere else, use -Dlocal.site=file:///.../ to point at that folder instead h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-62-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/runtime.site.zip! or file:///home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., Runtime Detection depends on JBoss Common, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. Dealing with timeouts for tests (To be rewritten soon...) http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47936] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] created the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-47935 Comment by going to Community [https://community.jboss.org/docs/DOC-47935] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Nick Boldt

Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-16604 -------------------------------------------------------------- ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install_ Verify or Install ? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommanded Using published Target Platform definition (Recommanded) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Set_up Set up ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_MavenAnt_to_get_it OR, use Maven+Ant to get it **** #Use Use ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-15513 How to Build JBoss Tools 3.2 with Maven 3.*+ +*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+*.* *+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.* h2. Environment Setup h3. Prerequisistes 1. Java 1.6 SDK 2. Maven 3.0.3 3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access* 4. subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected) h3. Maven and Java Make sure your maven 3 is available by default and Java 1.6 is used. mvn -version should print out something like *Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500) *Java version: 1.6.0_25*, vendor: Sun Microsystems Inc. *Java home: /usr/java/jdk1.6.0_25/jre* Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix" h3. Maven settings Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> h3. Maven & Java Memory Configuration To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX. {code} set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m {code} h2. Verify or Install ? +mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+. In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it. h2. About Target Platform and related profiles The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code. If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it. Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs: h3. Using published Target Platform definition (Recommanded) unified.target refers to the dependency as published in the Target Platfrom repository. * Pros:* No additional thing to do than invoking Maven * Always up-to-date * Cons: Speed - (to evaluate) Consume it by adding* +-Punified.target+* to you Maven invocation command-line h3. Or, getting a local copy of the Target Platform * Pros: Speed +++ * Cons: Step to be repeated whenever https://source.jboss.org/browse/JBossTools/trunk/build/target-platform/un... target platform changes h4. Set up h5. Download TP as a zip and install it by yourself You can either download the TP as a zip and unpack it into some folder on your disk. For convenience, the easiest is to unzip into jbosstools/build/target-platform/REPO/, since that's where the Maven or Ant process will by default operate. You can get it with a browser or a command line tool such as wget or curl at the following url: http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/ http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S...<actualFilename>*+.target.zip and then unzip it here (the default path for -Dlocal.site, which means you can call maven with +*-Plocal.site*+ and not need to pass in +*-Dlocal.site=file:///path/to/some/other/folder/*+ as well): unzip *.target.zip -d jbosstools/build/target-platform/REPO/ *(Note that the default path used for <local.site> will change every time a new target platform is released which is a significant change over the previous (eg., SR1, SR2), so if this breaks because the default not points at an empty folder, it's time to get a new TP! Hurray for build-time notification you're using an old target platform!)* h5. OR, use Maven+Ant to get it In that case, you also need Ant 1.8.2 or later*.* cd jbosstools/build/target-platform mvn clean install -Pget.local.target The get.local.target profile will resolve the target platform file, multiple.target, as a p2 repository on your local disk in ~/trunk/build/target-platform/REPO/. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take. Since the Maven profile is simply a wrapper call to Ant, you can also use Ant 1.8 or later directly: cd jbosstools/build/target-platform ant help # show usage instructions h4. Use Just add -*P local.site -Dlocal.site=file:///path/to/target/repository/* *NOTE:* You must specify a path starting with *file:///* (three or more slashes) to avoid errors such as "+p2.core.ProvisionException URI has an authority component+". Examples *LINUX / MAC USERS* cd build mvn clean install -U -B -fae -e -*P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/*| tee build.all.log.txt *WINDOWS USERS* cd c:\trunk\build mvn3 clean install -U -B -fae -e -Plocal.site *-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/* > build.all.log.txt h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platform and want to test it locally. Otherwise, Maven will simply retrieve parent and TP from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. This is only necessary when the TP change, prior to 3.3.Beta3 svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... *NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git.... *Instead, you can just fetch the build/ folder and one or more component folders, then as before,* *build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).* mkdir jbosstools cd jbosstools svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/build svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/jmx cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jmx* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jmx* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test cd ~/trunk/build mvn verify -P unified.target -*P jmx-bootstrap* h2. Building Everything In One Build Locally Via Commandline Assuming you have a local copy of the target platform in ${HOME}/trunk/build/target-platform/REPO/ (as explained previously: *LINUX / MAC USERS* cd build mvn clean install -P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\build mvn3 clean verify -P local.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ or mvn3 clean verify -Plocal.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt If you downloaded the zip and unpacked is somewhere else, use -Dlocal.site=file:///.../ to point at that folder instead h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-61-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-6... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/runtime.site.zip! or file:///home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., Runtime Detection depends on JBoss Common, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16604] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

Community Updates, November 15 - November 22

by JBoss Community

=============================================================== Community Updates for November 15 - November 22 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,193 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,488 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * Sessions and transactions [https://community.jboss.org/docs/DOC-13951] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * JBoss Tools 3.3 and Developer Studio 5.0 Final Release! [https://community.jboss.org/community/tools/blog/2012/06/21/jboss-tools-3...] * Spring and JBoss AS7 (Part 1) : Getting Started [https://community.jboss.org/blogs/mariusb/2011/07/13/spring-and-jboss-as7...] * Re: Jboss 7.1.2.Final is only for EAP? [https://community.jboss.org/message/776207#776207] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/746287#746287] * Re: java.net.BindException: Address already in use: JVM_Bind [https://community.jboss.org/message/747101#747101] Tips and tricks - Share Something You can easily share any document, discussion, or a blog post in Community with a colleague. Just navigate to the content you want to share and choose Send as Email from the Actions menu. You can send a personalized message, a link to the content, and even a PDF of the content as an email attachment. You can either choose someone who's a member of Community or you can just enter an email address of a colleague - they'll automatically receive an invitation to join the community. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Web Console 2.0 - Layout & Design

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "Web Console 2.0 - Layout & Design" To view the document, visit: https://community.jboss.org/docs/DOC-47685 -------------------------------------------------------------- Some general ideas and approaches to improve the UI. h3. Core UX Elements & Concepts See http://heiko-braun.github.com/pages/as7/docs/ux.html http://heiko-braun.github.com/pages/as7/docs/ux.html h3. Navigation Changes https://community.jboss.org/servlet/JiveServlet/showImage/19702/navigatio... https://community.jboss.org/servlet/JiveServlet/downloadImage/19702/navig... h3. Updated Grid System https://community.jboss.org/servlet/JiveServlet/showImage/102-47685-7-196... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47685-7... h3. Icon Set Font Awesome seems to be reasonable: http://fortawesome.github.com/Font-Awesome/#all-icons http://fortawesome.github.com/Font-Awesome/#all-icons -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47685] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - AS7 Management Console 2.0

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "AS7 Management Console 2.0" To view the document, visit: https://community.jboss.org/docs/DOC-47385 -------------------------------------------------------------- h3. Project Information | - Roadmap (https://issues.jboss.org/browse/AS7/component/12313823) - Issue Tracking (https://issues.jboss.org/browse/AS7) - Source Code: - Authoritative master: https://github.com/jbossas/console - Most recent: https://github.com/jbossas/console/tree/develop - Hacking the Codebase (https://community.jboss.org/docs/DOC-16607) - Releases (https://community.jboss.org/docs/DOC-47610) If you are looking for stable build, then you should consider the jbossas/console repository. Current development however, takes place on the "develop" branch. Stable milestones will be merged onto "master" with every release. | Jenkins: https://hudson.jboss.org/hudson/job/AS7ManagementConsole/lastBuild/buildS... (https://hudson.jboss.org/hudson/job/AS7ManagementConsole/lastBuild/) | h2. Extension Mechanism In relation to http://hbraun.info/2012/09/web-console-architecture-future-directions/ http://hbraun.info/2012/09/web-console-architecture-future-directions/ * GWT Composition Build time, lowest common denominator, based on building blocks but manual plumbing We have an example of this mechanism implemented already: https://github.com/heiko-braun/composite-ui https://github.com/heiko-braun/composite-ui * Plugin descriptiors Abstract model, relies on fixed schema (DMR metadata+UI properties), fixed set of supported traits, can be consumed by many clients * Runtime extensions Applicable to both options above. Removes compile time dependecy. h3. Layered Projects Some projects already integrate/extend the AS7 console. || *Project Name* || *Repository* || *Status* || | Switchyard | https://github.com/rcernich/jbossas-console/tree/master-hbraun | Does build on a previous version. Should update to >1.5.0 | | Teiid | https://github.com/teiid/teiid-web-console | Implements the most current version (1.5.0-SNAPSHOT) | | | | | h2. UI design & Interaction Patterns General UI design issues and ideas https://community.jboss.org/docs/DOC-47685 are collected here. h3. Core UX Elements & Concepts An overview of the current UX concepts (including widgets) can be found here: http://heiko-braun.github.com/pages/as7/docs/ux.html http://heiko-braun.github.com/pages/as7/docs/ux.html h2. Requirements, Ideas, Nice-to-Have || || *Desc* || | C0100 | The UI must be able to dynamically render model elements based solely upon its predefined description (the description may (and probably often will) include UI-specific elements to give "hints" to the renderer; i.e. 0 lines of XHTML is better than 10) (note that AS8 descriptions are likely to be more robust and easier to produce than AS7) | | C0200 | The UI must provide (or work with) a mechanism by which multi-step tasks (so-called "wizards") can be defined and subsequently rendered for specific model element types, such that these operations may be automatically associated with their corresponding model elements (even better if the task metadata were reusable by other tools e.g. CLI) | | C0300 | Using these tools it should be possible to generate UIs on many platforms (GWT, Swing, iOS/Android, maybe JON, maybe third-party mgmt tools, ???) which all look, act, and "feel" as similar as possible | | C0350 | RHQ/JON upstream. Acts as POC for C0300 | | C0400 | i18n | | C0500 | Authorisation & Authentication | | C0600 | 508 compliance | | | | -------------------------------------------------------------- Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - How can I determine when the ModelController service is fully started

by Ed Roberts

Ed Roberts [https://community.jboss.org/people/ejroberts] created the discussion "How can I determine when the ModelController service is fully started" To view the discussion, visit: https://community.jboss.org/message/776730#776730 -------------------------------------------------------------- I have an OSGi service that provides container properties (i.e. JBoss Model) to our other OSGi bundles. We moved to a late October build of 7.2.0.Alpha1 from 7.1.1.Final. With the move, the startup timing between the ModelController service and the OSGi deployments changed. When my code queried the model before it was fully started, the Model Controller was returning a successful operation outcome, but the query would return an undefined value. With the latest build from github attribute queries prior to a started state now quite rightly return an unsuccessful operation outcome, and the following error is logged 2012-11-15 15:35:39,436 ERROR [org.jboss.as.controller.management-operation](EclipseGeminiBlueprintExtenderThread-18) JBAS014613: Operation ("read-attribute") failed - address: ([("interface" => "internal")]) - failure description: "JBAS014807: Management resource '[(\"interface\" => \"internal\")]' not found" My question is, what can I test to make sure the Model and Service are fully started before querying, in order to avoid these errors being logged ? I tried using the controller state before, but it wasn't actually changing to indicate it had started. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776730#776730] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
3
0 / 0

[JBoss Web Development] - HTTPS Redirect URL Problem

by pkrogel

pkrogel [https://community.jboss.org/people/pkrogel] created the discussion "HTTPS Redirect URL Problem" To view the discussion, visit: https://community.jboss.org/message/777242#777242 -------------------------------------------------------------- I have HTTP to HTTPS redirect working correctly on our JBOSS 5.0.1 Server by adding the following to web.xml: <security-constraint> <web-resource-collection> <web-resource-name>Secure Content</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint> The problem is that the URL in the response does not work correctly on all of our user's networks. If I go to http://example.com/ http://example.com, I get redirected to https://example.com:7000/ https://example.com:7000 That url does not work for all of our users. I need to remove the port specification from the URL. (just https://example.com https://example.com) How do I configure the redirect to omit the port from the URL? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777242#777242] Start a new discussion in JBoss Web Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
1
0 / 0

[jBPM Development] - Unable to run the business process using JBPM 5.4

by ganesh r

ganesh r [https://community.jboss.org/people/ganesh0902] created the discussion "Unable to run the business process using JBPM 5.4" To view the discussion, visit: https://community.jboss.org/message/777659#777659 -------------------------------------------------------------- I have downloaded latest JBPM 5.4 final full installer. After installing in my local machine, developed a business process with human task, start event -> user task -> end event. To run the business process I have used the following code, public static final void main(String[] args) throws Exception { // load up the knowledge base //startUp(); KnowledgeBase kbase = readKnowledgeBase(); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); HornetQHTWorkItemHandler humanTaskHandler = new HornetQHTWorkItemHandler( ksession); humanTaskHandler.setIpAddress("127.0.0.1"); humanTaskHandler.setPort(5445); ksession.getWorkItemManager().registerWorkItemHandler("Human Task", humanTaskHandler); Map<String, Object> params = new HashMap<String, Object>(); params.put("title", "ESS"); params.put("businessKey", "ESS-Key"); // start a new process instance ksession.startProcess("com.sample.bpmn.hello",params); } private static KnowledgeBase readKnowledgeBase() throws Exception { KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); kbuilder.add(ResourceFactory.newClassPathResource("sample.bpmn"), ResourceType.BPMN2); return kbuilder.newKnowledgeBase(); } But it is throwing the following exception, 0 21/11 03:07:38,030[main] ERROR service.hornetq.HornetQTaskClientConnector.connect - Unable to connect to server using configuration org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=127-0-0-1 Exception in thread "main" org.jbpm.workflow.instance.WorkflowRuntimeException: [com.sample.bpmn.hello:1 - User Task:4] -- Could not connect task client: on ip: 127.0.0.1 - port: 5445 at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:132) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.ActionNodeInstance.triggerCompleted(ActionNodeInstance.java:55) at org.jbpm.workflow.instance.node.ActionNodeInstance.internalTrigger(ActionNodeInstance.java:51) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320) at com.sample.ProcessMain.main(ProcessMain.java:35) Caused by: java.lang.IllegalArgumentException: Could not connect task client: on ip: 127.0.0.1 - port: 5445 at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.connect(GenericHTWorkItemHandler.java:158) at org.jbpm.process.workitem.wsht.GenericHTWorkItemHandler.executeWorkItem(GenericHTWorkItemHandler.java:180) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) ... 18 more Before running the business process I have started h2, jboss and task service using ant start.demo Do I'm missing anything here? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777659#777659] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: jBPM 5 + Vaadin?

by yusuf nazir

yusuf nazir [https://community.jboss.org/people/yusufnazir] created the discussion "Re: jBPM 5 + Vaadin?" To view the discussion, visit: https://community.jboss.org/message/756194#756194 -------------------------------------------------------------- Hi Tom, I'm also using vaadin. Currently i'm looking for a way to integrate jbpm 5.3 in my app using spring. I want to use jbpm to manage workflows. I used jbpm version before in a spring managed webapp. But jbpm 5.3 differs totally from version 3 and there is no example of how to integrate 5.3 with spring. I have in my own way integrated spring with vaadin so that it resembles a swing app. Maybe we can form a group to storm the developers in creating an spring jbpm integration example. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/756194#756194] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

3
3
0 / 0

[JBoss AS 7 Development] - writing own standalone module that needs legacy log4j support

by John Mazzitelli

John Mazzitelli [https://community.jboss.org/people/mazz] created the discussion "writing own standalone module that needs legacy log4j support" To view the discussion, visit: https://community.jboss.org/message/777275#777275 -------------------------------------------------------------- This is yet another log4j thread - however, I think its different than most that have been posted - at least I can't find the answer to my specific use case - so don't roll your eyes just yet :) I am not writing an EAR, WAR, whatever. I am writing a standalone module (it has a Main-Class in it - its just like what the org.jboss.as.cli module does) and I am deploying it as just a module. I start the server via something like "java -jar jboss-modules.jar -mp <module paths> org.my.module" (this is similar to how the jboss CLI script starts the CLI) However, my module code is using some legacy libraries that use both commons-logging with log4j underneath (there is a log4j.xml that I want to be used to configure the logging). I do NOT get any ClassNotFound or similar errors, the code runs "ok" - only, I do not see any of log messages coming out in the console or the file (I have both appenders defined in log4j.xml). In my modules.xml, I do have a dependency on modules org.apache.commons.logging, org.apache.log4j, org.jboss.logmanager and org.jboss.logging. My module does NOT have any of those jars inside of it (that is, my module does not contain the log4j.jar or the commons-logging.jar - since I have a dependency declared for them, I did not put them in my module). Does this make sense? Any ideas on how I get this to work? Oh, and where exactly is log4j getting is configuration if not from my module's own logj4.xml? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777275#777275] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

3
3
0 / 0

[JBoss AS 7 Development] - Adding separately deployed .jar files to other .ear's classpath...

by Martin Wortner

Martin Wortner [https://community.jboss.org/people/wortner] created the discussion "Adding separately deployed .jar files to other .ear's classpath..." To view the discussion, visit: https://community.jboss.org/message/777477#777477 -------------------------------------------------------------- Hi, I have an ear, and inside of this ear I need to have on the classpath some jar's classes to be able to load them via Java ServiceLoader. I'd like to use the jBoss AS maven plugin for deploying or just directly copy the .ear and jars into deployments folder of jBoss 7 server. Is it possible that the ear will somehow see(be able to load them via ServiceLoader.load(class) call) the jar files??? So the jar files should act like "shared" library. And if it is possible, what exactly happens when I will un(re)deploy these .jars? Thanks for answer in beforehand. regards Martin -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777477#777477] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Pavol Pitonak

Pavol Pitonak [https://community.jboss.org/people/ppitonak] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11160 -------------------------------------------------- Hi Stan, I built latest AS from you branch on Github but when I deploy a RichFaces app, I get this error: Unable to process annotations for url, vfs:/content/simpleapp.war/WEB-INF/lib/richfaces-components-ui-4.3.0-20121120.101714-220.jar/META-INF/faces-config.xml. Reason: java.util.zip.ZipException: zip file is empty 13:42:47,713 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) : java.util.zip.ZipException: zip file is empty Is it ready for deploying apps? --------------------------------------------------

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: How create a new deployer?

by Tomaz Cerar

Tomaz Cerar [https://community.jboss.org/people/ctomc] created the discussion "Re: How create a new deployer?" To view the discussion, visit: https://community.jboss.org/message/777407#777407 -------------------------------------------------------------- Hi, take a look how to create new subsystem https://docs.jboss.org/author/display/AS71/Extending+JBoss+AS+7 https://docs.jboss.org/author/display/AS71/Extending+JBoss+AS+7 there are also basic instructions how to create new deployer. -- tomaz -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777407#777407] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss Messaging Development] - clustering problem with JBoss Messaging in JBoss 5.1

by Nitesh Mehta

Nitesh Mehta [https://community.jboss.org/people/niteshmehta] created the discussion "clustering problem with JBoss Messaging in JBoss 5.1" To view the discussion, visit: https://community.jboss.org/message/776085#776085 -------------------------------------------------------------- We have a cluster environment with two nodes (Node1 and Node2) of JBoss 5.1. We have two queues deployed. When we bring up the Node1 and view consumer count of queue in admin-console it shows consumer count as 1 for each queue. Till now everything fine and work as expected. When we bring up the Node2 of cluster and view consumer count of queues in admin-console of both the node, we observe a random behavior sometime consumer count is incremented to 2 on Node1 whereas consumer count stays 0 on Node 2 and some time it is increase to 1 on Node2. When we have consumers for queues on both the node i.e. Node1 Queue1 consumer count =1 Node1 Queue2 consumer count =1 Node2 Queue1 consumer count=1 Node2 Queue2 consumer count=1 Everything work as expected BUT When we have a situation like Node1 Queue1 consumer count =2 Node1 Queue2 consumer count =1 Node2 Queue1 consumer count=0 Node2 Queue2 consumer count=1 Then all the messages which reach Node2 Queue1 are not processed. When one of the nodes goes down these failover happens and these messages get processed This situation is happening very often. We tried to upgrade to JBoss Messaging 1.4.5 and JBossRemoting 2.5.2.SP3 but it didn’t help. messaging-service.xml <?xml version="1.0" encoding="UTF-8"?>  <server>  <mbean code="org.jboss.jms.server.ServerPeer" name="jboss.messaging:service=ServerPeer" xmbean-dd="xmdesc/ServerPeer-xmbean.xml">  <attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:0}</attribute>  <attribute name="DefaultQueueJNDIContext">/queue</attribute>  <attribute name="DefaultTopicJNDIContext">/topic</attribute> <attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>  <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>  <attribute name="DefaultMaxDeliveryAttempts">10</attribute>  <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>  <attribute name="DefaultRedeliveryDelay">10000</attribute>  <attribute name="MessageCounterSamplePeriod">5000</attribute>  <attribute name="FailoverStartTimeout">60000</attribute>  <attribute name="FailoverCompleteTimeout">300000</attribute> <attribute name="StrictTck">false</attribute>  <attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>  <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</attribute>  <attribute name="DefaultPreserveOrdering">false</attribute>  <attribute name="RecoverDeliveriesTimeout">300000</attribute>  <attribute name="EnableMessageCounters">false</attribute> <attribute name="SuckerPassword">${queues.database.password}</attribute>   <depends optional-attribute-name="PersistenceManager">jboss.messaging:service=PersistenceManager</depends> <depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends> <depends>jboss.messaging:service=Connector,transport=bisocket</depends> <depends optional-attribute-name="SecurityStore" proxy-type="org.jboss.jms.server.SecurityStore">jboss.messaging:service=SecurityStore</depends> </mbean> </server> -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776085#776085] Start a new discussion in JBoss Messaging Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
1
0 / 0

[JBoss AS 7 Development] - Re: How create a new deployer?

by Wolf-Dieter Fink

Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion "Re: How create a new deployer?" To view the discussion, visit: https://community.jboss.org/message/777377#777377 -------------------------------------------------------------- You might have a look into the https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/cluster-ha-s... cluster-ha-singleton deployer how to use the management API and start a service. In your case I would create my own subsystem to be able to use the mngmt CLI power -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777377#777377] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - How create a new deployer?

by ulrichromahn

ulrichromahn [https://community.jboss.org/people/ulrichromahn] created the discussion "How create a new deployer?" To view the discussion, visit: https://community.jboss.org/message/777269#777269 -------------------------------------------------------------- Hi All, I would like to create a new deployer for the following use case: I would like to create a file, preferably an XML file, which contains a "bundle name" (not to confuse with OSGi bundles, though), and a list of JAR's, WAR's, or EAR's that should be deployed. All those artifacts to be deployed should be specified by a URI, e.g. "file:/home/myname/deployments/my-new-app-1.0.0.jar" or "mvn:org.mydomain.app/myapp/1.0.0/war". The file should then be picked up by my new deployer and then the list of all those artifacts should be resolved (found) according to the URI. >From the example above, the first URI should find the "my-new-app-1.0.0.jar" on the local filesystem under "/home/myname/deployments" and then deploy it to JBoss AS 7. The second example the demonstrtes the power of this new deployer: it would try to find a WAR with the filename "myapp-1.0.0.war from a Maven repository using the groupId of "org.mydomain.app" and artifactId of "myapp". My specific implementation would be configurable to look into a local ".m2" repository first and if not found, try to download it from a remote Maven repository. The URL to this repository should be configurable. This could be implemented similar to the OSGi Repository implemented as part of JBOSGI. Here is my question: Are there any HOWTO's, examples, or other documentation that describes how to implement a new deployer in JBoss AS7? It would even be helpful if someone could point me to some existing implementations? I looked at the current source and tried to figure out how the deployer for the "*-ds.xml" files was implemented, but it is hard for me to see how this would be hooked into the overall JBoss deployment subsystem? Any help or pointers would be much appreciated. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777269#777269] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Connection Re-Authentication and Security Propagation [DRAFT]

by Darran Lofthouse

Darran Lofthouse [https://community.jboss.org/people/dlofthouse] modified the document: "Connection Re-Authentication and Security Propagation [DRAFT]" To view the document, visit: https://community.jboss.org/docs/DOC-47864 -------------------------------------------------------------- h2. Introduction The purpose of this article is to outline the problems that we are attempting to solve and the solution currently being considered, this work is being tracked under the following Jira issue: - https://issues.jboss.org/browse/AS7-5901 https://issues.jboss.org/browse/AS7-5901 Currently for remote EJB invocations (Actually all invocations to the server but in this case EJB invocations are the priority) a Remoting connection is established by the client, early in establishing this connection the remote client performs authentication using SASL - once authenticated the authentication is valid for the life of the connection. As EJB invocations are received the identity on this connection is the identity used for the EJB call. The following diagram illustrates the exising calls for remote EJB clients: - https://community.jboss.org/servlet/JiveServlet/showImage/19891/Existing+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19891/Exist... The established connection here is a Remoting connection, the connection itself is independent of any service being accessed and on establishing the connection authentication is performed using the associated realm. Subsequently when the client connects to the EJB Container and sends a request to a deployed EJB the identity used for the EJB call is the identity taken from the underlying connection. As the authentication takes place as the connection is established the only way for the clients to send in requests as an alternative user is to establish a new connection as the new user. A second scenario is where the call is also passed from one server to another: - https://community.jboss.org/servlet/JiveServlet/showImage/19892/Existing+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19892/Exist... In this second scenario there is now a connection from the first server to the second server, this connection also requires authentication and the call to the EJB on the second server runs as the identity of this second connection. These two diagrams illustrate the problems to be solved: - * For a client to run as different identities different connections are required for each identity. * For a server to server call the identity on the second server is the identity of the connection and not the original caller. h3. Remoting Authentication Before reviewing alternative solutions it is worth describing the decisions relating to the authentication of the actual connection as at the very minimum it is desirable that we do not undermine this with a solution that allows interception of the exchanges in such a way that either passwords are revealed or items are revealed that could be basis for a plain text attack. When a client attempts to connect to the Remoting connection a challenge is sent back to the client containing a list of supported authentication SASL mechanisms that the client can select from to attempt to authenticate, the client selects on and attempts the authentication. If authentication succeeds then the client can then request to connect to the service it wished to use, if not the client is re-challenged with the list of mechanisms and this is repeated until the client either successfully authenticates or the list is exhausted. The SASL mechanisms that are offered are selected based on the capabilities of the backing user store - as an example if we have a user store what we can query to obtain the users password or a pre-prepared hash of their password we offer the client the Digest-MD5 mechanism - however if we can only verify a supplied password but not generate the hashes required for Digest based authenitcation then PLAIN is offered as a mechanism. A second SASL mechanism that we also support is the External mechanism, this mechanism is a special mechanism in that it automatically authenticates as an identity associated with the surrounding connection - currently we use this for ClientCert style authentication where after a TLS connection is established authentication will then proceed based on the clients certificate. Another mechanism that we are currently adding support for is GSSAPI, this is a mechanism that authenticates a user by the use of authentication tokens with no exchange of passwords between the points involved in the authentication process. The ability to authenticate using these different approaches where we can reduce the places where either passwords or replayable tokens are visible is the key reason why we do not want to introduce those kind of vulnerabilities in the solution to the two problems being described here. Authentication is only presently performed on establishing the connection and is considered valid for the life of the connection. h4. SASL As described above we are using SASL for the negotiated authentication process between the client and the server, there are a couple of areas of SASL that either we don't use or we only use in a limited way that we can potentially take advantage of for some of this work. h5. Authorization Id For all mechanisms supported by SASL there is both an authentication id and an authorization id in the request. * *authentication id* - This is the ID of the user actually performing the authentication i.e. this is the identity of the user we are comparing the password against. * *authorization id* - This is the identity that we want requests to run as, i.e. this is the identity that we load the roles for. Presently we mandate that both of these identities are the same so whilst users authenticate as themselves they can only request that the requests are run as themselves as well. >From an AS perspective this capability of SASL starts to show some possible use when we are talking about propagating security contexts and trusting requests from other clients (in our case other servers). For any server to server connection this is most likely going to be authenticated using an identity of the server. We can now review the option of allowing the server accounts to be able to request that a request is run using a different authorization id. This now means that for a server account say 'ServerA' we are saying that we know that 'ServerA' has the capability to authenticate the remote users so we can now configure a sub-set of the users that 'ServerA' can now ask that requests are executed on behalf of. h5. External The external SASL mechanism is a special SASL mechanism that uses something from the connection for the authentication step, presently use this mechanism to authenticate based on the clients certificate after a TLS connection had already been established - we can do this as the TLS negotiation process also went through a verification process using the trust store to verify that the clients certificate is trusted. When looking at the existing connections one area of solutions that will be explored below is to consider repeating the SASL process within an already authenticated connection. The External mechanism could then have another role to play in that now there is already an authenticated user associated with the connection (for these issues most likey authenticated as a server) - combined with the authorization ID as discussed above a server could authenticate using this mechanism and specify the authorization id without having to repeat the full authentication process that was performed as the connection was established. h5. GSSAPI This one is not a mechanism we are currently using but are close to being able to enable this feature - in short this is enabling Kerberos based authentication which also includes identity propagation capabilities without needing to drop to using the authorization id. For anyone really serious about security context propagation I would most likely recommend this approach - however this is very dependent on the related infrastructure so may not be a suitable as a one size fits all solution. h5. Callback Handlers Where SASL is used clients are expected to provide a CallbackHandler that will be called by a mechanism to request information that is required to make the call, the idea being that these CallbackHandlers contain no data and pro-actively prompt for these values ony if they are actually required. Although at some point we would like to review the CallbackHandler API due to some deficiencies in the current API that is not a priority here. h4. Multi Realm Support Presently within JBoss AS7 a single realm is used for the authentication process as the connection is established, there is a desire to support multiple realms however multiple realms on connecting to the server is currently outside the scope of this feature being considered. However if we implement a solution that uses any form of authentication then that solution should allow for the authentication to be against different realms. The feasibility and details for this should be considered in more depth with the selected solution. h2. Proposed Solutions This section describes the solutions currently considered and where appropriate describes why those solutions are currently discounted, at this point this is intended to be for discussion rather than a final definitive decision. h3. Solution from Previous Releases In previous AS releases unless a custom RMI socket was used the connections to the application server were not authenticated, instead the username and credential would be passed along with the EJB invocation and intercepted before the call reached the EJB - the supplied information would then be used to authenticate the remote user before allowing the call to proceed. https://community.jboss.org/servlet/JiveServlet/showImage/19893/Previous+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19893/Previ... Where a client wanted to run as multiple identities that was fine as for each invocation a different username and password could be set for the call. This approach also potentially allowed for the security context to be passed onto subsequent servers as the contents from this message invocation are available. https://community.jboss.org/servlet/JiveServlet/showImage/19894/Previous+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19894/Previ... Whilst this approach does solve the problem of being able to switch identities and propagate identities it suffers from the problem that the users password is sent in the clear so should we undertake a similar solution for AS7 it would undermine the protection available from the currently available SASL mechanisms, in addition to this it is assuming that a username / password based authentication is always the approach we will want to take even though there are now alternative mechanisms in common use. h3. Reauthenticate The Connection As the calls are executed as the identity of the connection one approach could be to allow the client side to initiate a re-authentication of the connection so that a different identity can be used. https://community.jboss.org/servlet/JiveServlet/showImage/19895/Reauthent... https://community.jboss.org/servlet/JiveServlet/downloadImage/19895/Reaut... Whilst this would allow a client to switch identities and it could potentially be implemented using the SASL mechanisms the biggest issue here is if the client is multi-threaded and wants to run as multiple identities concurrently. At best the client would need to maintain a pool of connections one for each identity in use and if all identities could be used at once then it is no better than the current situation. The multi threaded client issue is also made worse in the server to server case where sharing a single connection would be a major benefit in reducing the resources used. Above where the existing Remoting authentication is described the capabilties relating to the authorization id and the External mechanism are described, for a server to server connection we could use both of these to re-authenticate the connection to switch the authorization id to the id we wish to run as - however in a server to server environment this one identity at a time per connection issue becomes even greater. h3. Authentication On Invocation Moving beyond re-authenticating the whole connection another posibility is to add authentication to the actual invocation, above the previous approach of bundling credentials with an invocation was illustrated but another option now would be to add SASL authentication to the invocation process. For the connection re-authentication of a single client the requests would be intercepted like this: - https://community.jboss.org/servlet/JiveServlet/showImage/19897/SASL+Per+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19897/SASL+... The authentication could be optional with one of the following being used to enable it for a request: - * A flag from the client indicating that they want the authentication to occur. * A failed authorization check indicating the current client does not have the required permissions so now give them an opportunity to switch to an identity that does. Alternatively it could be mandatory for the request and where no switch is required the client could use the External mechanism to ask that the current invocation is executed as the previously authenticated identity. For the client to server scenario it would be most likely that the client is using the SASL mechanisms that perform a full authentication i.e. one of the username password mechanisms with the client knowing the usernames and password of each of the identities it wishes to use. However if the authorization ID capability is supported there is nothing to stop clients from using it should their user be allowed to do so. A server to server call would not look like: - https://community.jboss.org/servlet/JiveServlet/showImage/19898/SASL+Per+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19898/SASL+... The client to server portion of the call is described above but the server to server portion of the call would either be dependent on the authorization id and possibly the External mechanism capabilties or the set up would be using GSSAPI end to end to make use of the propagation capabilities of GSSAPI. Either way existing connections are now re-used without introducing a serialization of requests over the connections as multiple requests could be executed as different users concurrently. One point to keep in mind is that although the diagram only shows one client calling the first server there could in fact be many clients calling that server each with their own connection to the server and then a single connection between the servers. There are a couple of down sides for this approach. * The additional SASL challenge is deep within the protocol of the service being called, if we wanted to repeat this for further protocols e.g. JNDI, management, JMX etc... then it will need to be implemented again for each of these. * Where on the client side a CallbackHandler may be used to supply credentials to the client side of a selected SASL mechanism - if the authentication is using a one time password the client will be prompted to supply this on each invocation. h3. Authentication Service This solution is to add a new additional service to the server, clients can choose to call this service perform a SASL authentication, recieve a token after authentication is complete and pass this token in subsequent request to ask that the invocation containing the token is executed as the authorization id from the SASL authentication previously completed. https://community.jboss.org/servlet/JiveServlet/showImage/19899/Auth+Serv... https://community.jboss.org/servlet/JiveServlet/downloadImage/19899/Auth+... Within this solution the majority of the new interactions are handled using this new 'Authentication Service' this service is responsible for handling a new SASL authentication process and returning an authentication token to the client. It is anticipated that a process like this would support all SASL authentication mechanisms currently supported including different authorization IDs and the alternative use of the External mechanism also described above. As in the previous solution it is anticipated that the client would be using mechanism based on having the required information to perform the authentication as different users however it is possible that the client could have the ability to request a different authorization id. A small change is still required for the EJB invocation in that the token needs to be passed with the request, intercepted and the real identity that token maps to retrieved from the Authentication Service. The server to server case then looks like this: - https://community.jboss.org/servlet/JiveServlet/showImage/19900/Auth+Serv... https://community.jboss.org/servlet/JiveServlet/downloadImage/19900/Auth+... For the server to server call as with the previous solution the server could either make use of the External mechanism with a different authorization ID when calling the authentication service or the server could use GSSAPI if it has a forwardable GSSAPI identity - either way the server recieves back a token which it then uses on the EJB invocation. Should other services on the server require the ability for security context propagation then the same service would be used and the only part that would need to be repeated is the passing of this security token. h5. Token Management By introducing a token we do not want to be introducing anything that now can be used in any form of attack based on intercepting these packets, here we have a couple of options: - * Tie the token to the connection, replays over a different connection will be rejected - clients that re-connect will have to re-establish the connections.* This does have an implication if a CallbackHandler is in use on the client, this may be required to cache the username and password whilst being aware of any one time password requriements. * Investigate some form of key exchange for insecure connections so the client and server can generate their own secrets, exchange them and then allow the client to prove that it can legitimatly use the token it supplied. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47864] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - How to use modules with ServiceLoader....

by Martin Wortner

Martin Wortner [https://community.jboss.org/people/wortner] created the discussion "How to use modules with ServiceLoader...." To view the discussion, visit: https://community.jboss.org/message/777163#777163 -------------------------------------------------------------- Hi, we switched recently to JBoss 7(from 5:) We have some "strange" design. Our ear application is using Java ServiceLoader service to load some, let's say, plugins from "plugins" folder we created in profile directory. We can change these jars only during server restart. Now what I want to reach using jBoss 7. - I'd like to be able to redeploy "plugins" jar on the fly i.e. using Maven jboss-as-plugin. - Have possibility to drop the jars in the deployment folder to redeploying them. - Maybe utilize the JBoss modules framework to do this(but I'm affraid of these dependencies and modules.xmls etc. seams to complicated) So mainly is there a possibility to redeploy jars on the fly? Can I create one module, with all plugins inside, just to enable loading from main ear's ServiceLoader?(the ear will need only one dependency to this module with all plugins) What exactly are the "dynamic modules" how can I use them, static are copyied to "modules" folder, what about these dynamic ones? Isn't the easiest solution just to use extracted ear and copy/ overwrite the plugins in the /lib folder? What if the plugins formerly loaded only throught ServiceLoader have dependencies on the ear's libraries? Can ear have dependency on a module and the module dependency back to the ear??? What exactly happens when module is loaded, is just the module classpath added to the dependent ear's classpath??? When I some how redeploy the module will it stop the parent ear file? Sorry for so many question, that are not so clear, because I have mixed so much things together, but just starting to understand this area. But any hints how can I "Hot deploy" plugins, probably using jboss module, are really appreciated. Best regards to all of you. M. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777163#777163] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - HornetQ issue while started on 7.1.3.Final

by Albert Dabrowski

Albert Dabrowski [https://community.jboss.org/people/aldab] created the discussion "HornetQ issue while started on 7.1.3.Final" To view the discussion, visit: https://community.jboss.org/message/777162#777162 -------------------------------------------------------------- After suceesful jboss AS 7.1.3.Final startup on standalone-full configuration some warning regarding disconnection on hornetq occurs. It's raw start-up with no changes and no deployments. Do anyone had such similar issues? Once I remove connection pooling this warning will disapear but would be good to know what's the issue. Environment: Windows, jboss AS 7.1.3.Final build taken from a tag 09:43:59,872 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA 09:44:00,012 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 09:44:00,059 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.3.Final "Arges" starting 09:44:01,044 INFO [org.xnio] XNIO Version 3.0.6.GA 09:44:01,044 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) 09:44:01,044 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.6.GA 09:44:01,059 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.SP1 09:44:01,075 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers 09:44:01,122 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 32) JBAS016200: Activating ConfigAdmin Subsystem 09:44:01,137 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 09:44:01,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) JBAS010280: Activating Infinispan subsystem. 09:44:01,262 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 38) JBAS016300: Activating JacORB Subsystem 09:44:01,325 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final) 09:44:01,340 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 49) JBAS011906: Activating OSGi Subsystem 09:44:01,356 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 48) JBAS011800: Activating Naming Subsystem 09:44:01,356 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service 09:44:01,387 INFO [org.jboss.as.security] (ServerService Thread Pool -- 54) JBAS013171: Activating Security Subsystem 09:44:01,403 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 58) JBAS015537: Activating WebServices Extension 09:44:01,403 INFO [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory 09:44:01,419 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.13.Final 09:44:01,434 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default] 09:44:01,840 WARN [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 09:44:01,840 WARN [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1 09:44:01,872 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started 09:44:01,919 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080 09:44:02,028 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingjournal,bindingsDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messaginglargemessages,pagingDirectory=C :\Motorola\test\jboss-as-7.1.3.Final\standalone\data\messagingpaging) 09:44:02,028 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Waiting to obtain live lock 09:44:02,169 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-1) Using NIO Journal 09:44:02,200 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started 09:44:02,247 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.5.GA 09:44:02,247 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Waiting to obtain live lock 09:44:02,247 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Live Server Obtained live lock 09:44:02,340 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Motorola\test\jboss-as-7.1.3.Final\standalone\deployments 09:44:02,356 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999 09:44:02,356 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447 09:44:02,528 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 09:44:02,559 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.6.Final-20df069 127.0.0.1:5455 for CORE protocol 09:44:02,559 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-1) Started Netty Acceptor version 3.2.6.Final-20df069 127.0.0.1:5445 for CORE protocol 09:44:02,559 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) Server is now live 09:44:02,559 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) HornetQ Server version 2.2.21.SNAPSHOT (HQ_2_2_21_final, 122) [ec7e3342-321d-11e2-9852-4db017d6b448]) started 09:44:02,575 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 09:44:02,575 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory 09:44:02,606 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA 09:44:02,637 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started 09:44:02,637 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra 09:44:02,637 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 09:44:02,669 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.3.Final "Arges" started in 3032ms - Started 166 of 252 services (85 services are passive or on-demand) 09:46:04,574 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] (hornetq-failure-check-thread) Connection failure has been detected: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=3] 09:46:04,574 WARN [org.hornetq.jms.server.recovery.RecoveryDiscovery] (Thread-1 (HornetQ-client-global-threads-2022533)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException[errorCode=2 message=Channel disconnected] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:381) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:203) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] 09:46:12,574 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] (hornetq-failure-check-thread) Connection failure has been detected: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=3] 09:46:12,574 WARN [org.hornetq.core.server.impl.ServerSessionImpl] (hornetq-failure-check-thread) Client connection failed, clearing up resources for session 4ac5c5dc-3225-11e2-a523-c7d24ec98fd0 09:46:12,574 WARN [org.hornetq.core.server.impl.ServerSessionImpl] (hornetq-failure-check-thread) Cleared up resources for session 4ac5c5dc-3225-11e2-a523-c7d24ec98fd0 09:46:12,574 WARN [org.hornetq.jms.server.recovery.HornetQXAResourceWrapper] (Thread-0 (HornetQ-client-global-threads-2022533)) Notified of connection failure in xa recovery connectionFactory for provider ClientSessionFactoryImpl [serverLocator=ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0], discoveryGroupConfiguration=null], connectorConfig=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0, backupConfig=null] will attempt reconnect on next pass: HornetQException[errorCode=2 message=Channel disconnected] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:381) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:203) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777162#777162] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Unable to deploy Webservice in Jboss 7:

by Genrose Hirudaysamy

Genrose Hirudaysamy [https://community.jboss.org/people/genrosesusai] created the discussion "Re: Unable to deploy Webservice in Jboss 7:" To view the discussion, visit: https://community.jboss.org/message/776973#776973 -------------------------------------------------------------- I am trying to deploy 3 webservices on different ports e.g 8080, 8081, 8082. Out of 3 webservice , 2nd and 3rd webservice share the same endpoint and same package structure, same webservice class name and other details. But all three are in different war file. I made 3 copies of standalone folder and used each for each webservice. 1st and 2nd Webservice gets deployed but 3rd fails because of the below error: "JBAS015533: Web Service endpoint com.x.y.Z with URL pattern /* is already registered. Web service endpoint com.x.y.Z is requesting the same URL pattern." Then i deleted the 1st and 2nd instance from the jboss server and tried to run 3rd webservice only. Which still didnot work :( . It gives the same exception. Can somebody show light on this. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776973#776973] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

2
6
0 / 0

[JBoss Tools Development] - How to Build JBoss Tools with Maven 3

by Mickael Istria

Mickael Istria [https://community.jboss.org/people/mickael_istria] modified the document: "How to Build JBoss Tools with Maven 3" To view the document, visit: https://community.jboss.org/docs/DOC-16604 -------------------------------------------------------------- ** #Environment_Setup Environment Setup *** #Prerequisistes Prerequisistes *** #Maven_and_Java Maven and Java *** #Maven_settings Maven settings *** #Maven__Java_Memory_Configuration Maven & Java Memory Configuration ** #Verify_or_Install_ Verify or Install ? ** #About_Target_Platform_and_related_profiles About Target Platform and related profiles *** #Using_published_Target_Platform_definition_Recommanded Using published Target Platform definition (Recommanded) *** #Or_getting_a_local_copy_of_the_Target_Platform Or, getting a local copy of the Target Platform **** #Get_it Get it ***** #_Download_TP_as_a_zip_and_install_it_by_yourself Download TP as a zip and install it by yourself ***** #OR_use_MavenAnt_to_get_it OR, use Maven+Ant to get it **** #Use_it Use it **** #As_Maven_mirror_Recommended As Maven mirror (Recommended) **** #OR_with_local_profiles_DEPRECATED OR, with local profiles (DEPRECATED) ** #Optional_Build_parent_and_target_platform (Optional) Build parent and target platform ** #Building_Individual_Components_Locally_Via_Commandline Building Individual Components Locally Via Commandline *** #Build_a_component_resolving_to_a_recent_aggregation_build_for_other_JBT_dependencies_Recommanded Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) *** #Build_a_component_resolving_to_the_latest_CI_builds_for_other_JBT_dependencies Build a component resolving to the latest CI builds for other JBT dependencies *** #Build_a_component_along_with_all_its_dependencies_from_sources_bootstrap_build Build a component along with all its dependencies from sources ("bootstrap" build) ** #Building_Everything_In_One_Build_Locally_Via_Commandline Building Everything In One Build Locally Via Commandline ** #Building_Locally_In_Eclipse Building Locally In Eclipse ** #Installation_Testing__making_sure_your_stuff_can_be_installed_ Installation Testing - making sure your stuff can be installed ** #Adding_a_new_feature_or_plugin_to_an_existing_component Adding a new feature or plugin to an existing component ** #Dealing_with_timeouts_for_tests Dealing with timeouts for tests ** #Tips_and_tricks_for_making_BOTH_PDE_UI_and_headless_Maven_builds_happy Tips and tricks for making BOTH PDE UI and headless Maven builds happy *** #Check_your_buildproperties Check your build.properties *** #Check_your_manifestmf_dependencies Check your manifest.mf dependencies +*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-15513 How to Build JBoss Tools 3.2 with Maven 3.*+ +*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+*.* *+Looking for how to build our documentation? See+ https://community.jboss.org/docs/DOC-13341 Building JBoss Tools Documentation.* h2. Environment Setup h3. Prerequisistes 1. Java 1.6 SDK 2. Maven 3.0.3 3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access* 4. subversion client 1.6.X (should work with lower version as well, but newer versions may not work as expected) h3. Maven and Java Make sure your maven 3 is available by default and Java 1.6 is used. mvn -version should print out something like *Apache Maven 3.0.3* (r1075438; 2011-02-28 12:31:09-0500) *Java version: 1.6.0_25*, vendor: Sun Microsystems Inc. *Java home: /usr/java/jdk1.6.0_25/jre* Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.42.3-2.fc15.x86_64", arch: "amd64", family: "unix" h3. Maven settings Follow https://community.jboss.org/docs/DOC-15170 these instructions to add reference to JBoss Repositories into your settings.xml. You'll also probably need access to the SNAPSHOT repository. So here is what you should see in your ~/.m2/settings.xml <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> .... <profiles> .... <profile> <id>jboss-default</id> <repositories>  <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </repository> </repositories> <pluginRepositories>  <pluginRepository> <id>jboss-public-repository-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>jboss-default</activeProfile> ... </activeProfiles> </settings> # *What if Maven can't find the upstream artifacts in Nexus?* Sometimes, Maven can't find the upstream artifacts - parent pom, tycho plugins, minimum (Juno SR0) or maximum (Juno SR1 or later) target platforms. To work around this, just build them locally: cd /tmp; svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ mvn install -U -f build/parent/pom.xml mvn install -U -f build/tycho-plugins/pom.xml mvn install -U -f build/target-platforms/pom.xml -Pjbosstools-maximum,jbosstools-minimum h3. Maven & Java Memory Configuration To configure the amount of memory used by Maven, you can define MVN_OPTS as follows, either in the mvn / mvn.bat script you use to run Maven, or set as global environment variables. Here's how to do so for http://forums.fedoraforum.org/showthread.php?t=262465 Fedora, https://help.ubuntu.com/community/EnvironmentVariables Ubuntu, http://forums.techarena.in/windows-xp-support/1152405.htm Windows, http://www.digitaledgesw.com/node/31 OSX. {code} set MAVEN_OPTS=-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m {code} h2. Verify or Install ? +mvn verify+ will perform all build and test steps, but it won't install the bundles in your local repository. +mvn install+ does install in you local repository. When an eclipse-plugin is installed in your repo, it is always used as default when resolving dependency. It is not possible to roll-back a local installation of a bundle, so in most cases, +mvn verify+ is to be prefered to +mvn install+. However, if you want to build stuff sequentially through several maven invocations, and you want to resolve against just-built stuff, you'll need to use +mvn install+. In this page, we'll encourage people to use *mvn verify* as much as possible to ensure *isolation*; but you can mvn install the same way if your use-case requires it. h2. About Target Platform and related profiles The target platform (TP) lists all dependencies (coming from Eclipse.or and other 3rd-party update sites) that are used by JBoss Tools. This target platform is materialized as an Eclipse p2 repository (formerly update-site) that is used during build to resolve dependencies. Target Platform is managed by JBoss Tools people, and only dependencies from this TP are allowed to be used in code. If you need a new dependency in the TP, feel free to https://issues.jboss.org/secure/CreateIssueDetails!init.jspa?pid=10020&su... open a ticket to request it. Here are several ways to build locally using this target platform. It's up to you to choose the one that match your needs: h3. Using published Target Platform definition (Recommanded) unified.target refers to the dependency as published in the Target Platfrom repository. * Pros:* No additional thing to do than invoking Maven * Always up-to-date * Cons: Speed - (to evaluate) Consume it by adding* +-Punified.target+* to you Maven invocation command-line h3. Or, getting a local copy of the Target Platform * Pros: Speed +++ * Cons: Step to be repeated whenever https://source.jboss.org/browse/JBossTools/trunk/build/target-platform/un... target platform changes h4. Get it h5. Download TP as a zip and install it by yourself You can either download the TP as a zip and unpack it into some folder on your disk. For convenience, the easiest is to unzip into jbosstools/build/target-platform/REPO/, since that's where the Maven or Ant process will by default operate. You can get it with a browser or a command line tool such as wget or curl at the following url: http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/ http://download.jboss.org/jbosstools/updates/juno/SR0c/e420-wtp340.target... e420-wtp340.target.zip (current minimum TP) http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/ http://download.jboss.org/jbosstools/updates/juno/SR1a/e421-wtp341.target... e421-wtp341.target.zip (current maximum TP) and then unzip it : unzip *.target.zip -d /path/to/my jbosstools/build/target-platforms/jbosstools-JunoSR0c/local/target/REPO/ or unzip *.target.zip -d /path/to/my jbosstools/build/target-platforms/jbosstools-JunoSR1a/local/target/REPO/ *(Note that the default path used for <local.site> will change every time a new target platform is released which is a significant change over the previous (eg., SR1, SR2), so if this breaks because the default not points at an empty folder, it's time to get a new TP! Hurray for build-time notification you're using an old target platform!)* h5. OR, use Maven+Ant to get it In that case, you also need Ant 1.8.2 or later*.* cd jbosstools/build/target-platform mvn clean install -Pget.local.target The get.local.target profile will resolve the target platform file, multiple.target, as a p2 repository on your local disk in ~/trunk/build/target-platform/REPO/. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take. Since the Maven profile is simply a wrapper call to Ant, you can also use Ant 1.8 or later directly: cd jbosstools/build/target-platform ant help # show usage instructions h4. Use it h4. As Maven mirror (Recommended) Once you get the target platform available locally, you can use it instead of the remote sites to save time. For this, we can simply use Tycho target-platform mirroring: http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... http://wiki.eclipse.org/Tycho/Target_Platform/Authentication_and_Mirrors#... So you can simply edit to your ~/.m2/settings.xml the definition of the repositories to mirror: | | | <settings> <mirrors>  <mirror> <id>jenkins.jbosstools-JunoSR0c</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR0c/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR0c/e420-wtp340.target/</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbosstools-JunoSR1a</id> <mirrorOf>http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/target-platform_4.0.juno.SR1a/e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR0c</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR0c/jbds600-e420-wtp340.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> <mirror> <id>jenkins.jbdevstudio-JunoSR1a</id> <mirrorOf>http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju...</mirrorOf> <url>file:///home/hudson/static_build_env/jbds/jbds-target-platform_4.0.juno.SR1a/jbds600-e421-wtp341.target</url> <layout>p2</layout> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> </mirrors> </settings> | h4. OR, with local profiles (DEPRECATED) Just add -*P local.site -Dlocal.site=file:///path/to/target/repository/* *NOTE:* You must specify a path starting with *file:///* (three or more slashes) to avoid errors such as "+p2.core.ProvisionException URI has an authority component+". Examples *LINUX / MAC USERS* cd build mvn clean install -U -B -fae -e -*P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/*| tee build.all.log.txt *WINDOWS USERS* cd c:\trunk\build mvn3 clean install -U -B -fae -e -Plocal.site *-Dlocal.site=file:///C:/trunk/build/target-platform/REPO/* > build.all.log.txt h2. (Optional) Build parent and target platform This step is only useful if you are actually working on the parent or the target platform and want to test it locally. Otherwise, Maven will simply retrieve parent and TP from *https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ JBoss Nexus* to perform your build. This is only necessary when the TP change, prior to 3.3.Beta3 svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... *NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git.... *Instead, you can just fetch the build/ folder and one or more component folders, then as before,* *build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).* mkdir jbosstools cd jbosstools svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/build svn co http://svn.jboss.org/repos/jbosstools/trunk/ http://svn.jboss.org/repos/jbosstools/trunk/jmx cd jbosstools/build/parent mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s] [INFO] JBoss Tools Parent ................................ SUCCESS [0.461s] ... h2. Building Individual Components Locally Via Commandline h3. Build a component resolving to a recent aggregation build for other JBT dependencies (Recommanded) * Pros:* You build only your component * You only need source for your component * Speed to resolve deps: + * You get generally the latest build for you component * Cons:* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change. More risk to get out of sync than with the staging site. Tracked by https://issues.jboss.org/browse/JBIDE-11516 https://issues.jboss.org/browse/JBIDE-11516 example: *cd jmx* mvn verify -P unified.target *-Pjbosstools-staging-aggregate* h3. Build a component resolving to the latest CI builds for other JBT dependencies * Pros:* You build only your component * You only need source for your component * You get generally the latest build for you component * Cons* Takes some time to resolve dependencies on other component * Can sometimes be out of sync if no build occured recently for a component you rely on and had some important change * Speed to resolve deps: - This profile is the one use for CI builds on Hudson. *cd jmx* mvn verify -P unified.target *-Pjbosstools-nightly-staging-composite* h3. Build a component along with all its dependencies from sources ("bootstrap" build) This will build exactly what you have locally * Pros:* You are sure of the version of sources that is used for your JBT dependencies * You don't loose time in resolving your JBT deps * Cons:* You need sources for your dependencies too * You often build more stuff that what you really want to test cd ~/trunk/build mvn verify -P unified.target -*P jmx-bootstrap* h2. Building Everything In One Build Locally Via Commandline Assuming you have a local copy of the target platform in ${HOME}/trunk/build/target-platform/REPO/ (as explained previously: *LINUX / MAC USERS* cd build mvn clean install -P local.site -Dlocal.site=file:///${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt (tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.) *WINDOWS USERS* cd c:\trunk\build mvn3 clean verify -P local.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ or mvn3 clean verify -Plocal.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt If you downloaded the zip and unpacked is somewhere else, use -Dlocal.site=file:///.../ to point at that folder instead h2. Building Locally In Eclipse First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site: http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/ Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job. First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity: +clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+ Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... On the *JRE* tab, make sure you're using a 6.0 JDK. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... On the *Refresh* tab, define which workspace resources you want to refresh when the build's done. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... Click *Run* to run the build. https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-57-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-5... Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above. h2. Installation Testing - making sure your stuff can be installed Each component, when built, produces a update site zip and an unpacked update site which can be used to install your freshly-built features and plugins into a running Eclipse or JBDS instance. Simply point your Eclipse at that folder or zip, eg., jar:file:/home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/runtime.site.zip! or file:///home/rob/code/jbtools/jbosstools/trunk/runtime/site/target/repository/, and browse the site. If your component requires other upstream components to install, eg., Runtime Detection depends on JBoss Common, you will also need to provide a URL from which Eclipse can resolve these missing dependencies. In order of freshness, you can use: 1. http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ (Nightly Trunk Site - updated every few hours or at least daily - *bleeding edge*) 2. http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ (Composite Staging Site - updated every time a component respins - *bleedinger edge*) 3. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/local-site/ (see the README.txt for how to use this site to refer to things you built locally - *bleedingest edge*) h2. Adding a new feature or plugin to an existing component Need to tweak a component to add a new plugin or feature? See https://community.jboss.org/docs/DOC-18373 https://community.jboss.org/wiki/AddingAPluginandorFeatureToAnExistingCom.... h2. Dealing with timeouts for tests (To be rewritten soon...) http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html http://lists.jboss.org/pipermail/jbosstools-dev/2012-September/005835.html h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE. h3. Check your build.properties Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings. Especially check your build.properties to have entries for *source..* and *output..* -- these are needed to *http://wiki.eclipse.org/Minerva#Source generate source plugins and features*. * * source.. = src/ output.. = bin/ src.includes = * src.excludes = src bin.includes = <your own,\ list of,\ files for inclusion,\ in the jar> h3. Check your manifest.mf dependencies A new issue when building against juno shows that all compilation dependencies MUST be EXPLICITLY mentioned in your manifest.mf list of dependencies. A recent example of how this can cause compilation errors is the archives module, which failed to build due to the org.eclipse.ui.views plugin, and its IPropertySheetPage interface, not being found during the build. After investigation, it was discovered that the archives.ui plugin did not explicitly declare a dependency on org.eclipse.ui.views. Inside eclipse and during indigo builds, however, the depencency was found and there were no compilation errors. This was because a plugin archives.ui explicitly dependend on (org.eclipse.ui.ide) had an explicit dependency on org.eclipse.ui.views. The IDE was able to see that archives.ui dependended on org.eclipse.ui.ide, and org.eclipse.ui.ide depended on org.eclipse.ui.views. Resolving nested dependencies no longer seems to be guaranteed, and so anything you have a compilation dependency on must now be explicitly declared in your manifest.mf -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16604] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 1 month

1
0
0 / 0

[Javassist Development] - Why creating a new CtTypeClass while compiling

by ami tabak

ami tabak [https://community.jboss.org/people/amitabakoptier] created the discussion "Why creating a new CtTypeClass while compiling" To view the discussion, visit: https://community.jboss.org/message/777037#777037 -------------------------------------------------------------- A Question regarding the usage of CtClass I have a scenario where I first add a new field to the class and then add insertBefore which is using that new field. I noticed javassist on the insertBefore has access to the CtClass (1^st^ image) but later on when looking up the new field it goes through MemberResolver. lookupClass0 The problem is that if anyone added via public CtClass makeClass(InputStream classfile) non synchronized method a CtClass based on the original byteCode I will not find the new member I just added. My questions are 1. Why do we need to look up the CtClass in the pool if we had it at the beginning of the insertBefore flow ? e.g. use the same instance throughout the flow 2. Why are some of the ClassPool makeClass syncronized and some are not ? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777037#777037] Start a new discussion in Javassist Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[Javassist Development] - ClassPool: getCtClassVs makeClass. Why getCtClass not synchronzied while makeClass is synchronized ?

by ami tabak

ami tabak [https://community.jboss.org/people/amitabakoptier] created the discussion "ClassPool: getCtClassVs makeClass. Why getCtClass not synchronzied while makeClass is synchronized ?" To view the discussion, visit: https://community.jboss.org/message/777036#777036 -------------------------------------------------------------- ClassPool.makeClass is a synchronized flow while ClassPool.getCtClass API is not synchronized. Thing is ClassPool.getCtClass may end up creating a new CtClassType Its not clear its not being synchronized just as makeClass is -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777036#777036] Start a new discussion in Javassist Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[Javassist Development] - javassist and interfaces defining a method which throws an exception question

by ami tabak

ami tabak [https://community.jboss.org/people/amitabakoptier] created the discussion "javassist and interfaces defining a method which throws an exception question" To view the discussion, visit: https://community.jboss.org/message/777034#777034 -------------------------------------------------------------- A Question regarding the JVM spec and how javassist is expected to handle it. I’ve an interface IMyFactory extending the Remote interface. It declares a method foo() which declares throws RemoteException so will be deemed as remotable API The implementing class implements the method but *doesn’t* declare itself as throwing the remote. Code wise the JVM picked this method as valid Remote API Javassist when interrogated class MyFactory.foo() method doesn’t provide any data on its being a throwing RemoteException *Questions* 1. The JVM spec defines a method by its name and properties, not by its exception throwing. In addition it allows an implementing method to declare less “throws” then its super / defining interface without loss of polymorphism 1. e.g. this foo() implementer is deemed the same as in the interface. Why wont javassist provide me the exception data defined in the Interface’s CtClass ? 2) Is there a “recoursive” API in javassist that will wllow me to intergoate a method up to its interface definition to see if some one above it has defined it to be an Throwable thrower or do I need to implement such search myself ? *Code example:* 1. 1. MyFactory implements IMyFactory {... @Override public int foo() //on purpose didn’t declare “throws java.rmi.RemoteException” { // TODO Auto-generated method stub return 0; } 1. 2. public interface IMyFactory extends Remote { public int foo() throws RemoteException; } -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/777034#777034] Start a new discussion in Javassist Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - AS7 projects

by Jeff Mesnil

Jeff Mesnil [https://community.jboss.org/people/jmesnil] modified the document: "AS7 projects" To view the document, visit: https://community.jboss.org/docs/DOC-16399 -------------------------------------------------------------- AS7 is comprised of the following projects: || *Description* || *Project link * || *Version control link * || *IRC room * || *Issue tracking * || | AS7 core | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-as | #jboss-as7 | https://issues.jboss.org/browse/AS7 | | Java Connector Architecture | http://www.jboss.org/ironjacamar | http://anonsvn.jboss.org/repos/jbossas/projects/jboss-jca/trunk | | https://jira.jboss.org/jira/browse/JBJCA | | Management Console | http://www.jboss.org/jbossas | https://github.com/jbossas/console | | https://issues.jboss.org/browse/AS7 | | Modular Classloading System | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-modules | | https://issues.jboss.org/browse/MODULES | | Modular Service Container | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-msc | | https://issues.jboss.org/browse/MSC | | Java Annotation Indexer | http://www.jboss.org/jbossas | https://github.com/jbossas/jandex | | https://issues.jboss.org/browse/JANDEX | | JBoss Invocation API | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-invocation | | | | JBoss Class File Writer | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-classfilewriter | | | | JBoss Logging | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-logginghttps://github.com/jboss-logging/... | | https://issues.jboss.org/browse/JBLOGGING | | Dynamic Model Representation | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-dmr | | | | StAX facade with plugability + usability enhancements | http://www.jboss.org/jbossas | https://github.com/jbossas/staxmapper | | | | JBoss Threads | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-threads | | https://issues.jboss.org/browse/JBTHR | | JBoss Transactions | http://www.jboss.org/jbosstm | http://anonsvn.jboss.org/repos/labs/labs/jbosstm/trunk/ | | http://jira.jboss.org/jira/browse/JBTM | | Weld (CDI) Java Contexts and Dependency Injection | http://seamframework.org/Weld | http://github.com/weld | | https://issues.jboss.org/browse/WELD | | Hibernate | http://www.hibernate.org | https://github.com/hibernate/hibernate-orm (https://github.com/hibernate/hibernate-core/) | #hibernate | * integration issues -> https://issues.jboss.org/browse/hibernate * Hibernate issues -> http://opensource.atlassian.com/projects/hibernate | | OSGi | http://www.jboss.org/jbossas/osgi | http://github.com/jbosgi/jbosgi | | https://jira.jboss.org/browse/JBOSGI (https://issues.jboss.org/browse/JBOSGI) | | Arquillian for testing | http://www.jboss.org/arquillian | https://github.com/arquillian/ (https://github.com/arquillian/arquillian) | | https://jira.jboss.org/jira/browse/ARQ | | JBoss Java EE API | http://www.jboss.org/jbossas | https://github.com/jboss | | https://issues.jboss.org/browse/JBEE | | JBoss (VFS) Virtual File System | http://www.jboss.org/jbossas | http://github.com/jbossas/jboss-vfs | | https://issues.jboss.org/browse/JBVFS | | JBoss invocation API | | https://github.com/jbossas/jboss-invocation | | | | JGroups communications library for clustering | http://jgroups.org/ | http://www.github.com/belaban/JGroups | | http://jira.jboss.com/jira/browse/JGRP | | JBoss Web Services | http://www.jboss.org/jbossws/ | http://anonsvn.jboss.org/repos/jbossws | | https://issues.jboss.org/browse/JBWS | | JBoss Remoting JMX | | https://github.com/darranl/remoting-jmx | | https://issues.jboss.org/browse/REMJMX | | JBoss Remoting | http://www.jboss.org/jbossremoting http://www.jboss.org/jbossremoting/remoting-3.html | https://github.com/jboss-remoting/jboss-remoting | | https://jira.jboss.org/jira/browse/JBREM | | JBoss Marshalling | http://www.jboss.org/jbossmarshalling | https://github.com/jboss-remoting/jboss-marshalling | #jboss-marshalling | http://jira.jboss.org/jira/browse/JBMAR | | Infinispan | http://www.jboss.org/infinispan | https://github.com/infinispan/infinispan | #infinispan | http://jira.jboss.org/jira/browse/ISPN | | HornetQ | http://www.jboss.org/hornetq (http://www.jboss.org/infinispan) | https://github.com/hornetq/hornetq (https://github.com/infinispan/infinispan) | #hornetq | http://jira.jboss.org/jira/browse/HORNETQ (http://jira.jboss.org/jira/browse/ISPN) | | Patched version of Mojarra | | https://github.com/jboss/mojarra/ | #jboss-as7 | | All IRC channels are at Freenode IRC servers. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16399] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Connection Re-Authentication and Security Propagation [DRAFT / Work In Progress]

by Darran Lofthouse

Darran Lofthouse [https://community.jboss.org/people/dlofthouse] modified the document: "Connection Re-Authentication and Security Propagation [DRAFT / Work In Progress]" To view the document, visit: https://community.jboss.org/docs/DOC-47864 -------------------------------------------------------------- h2. Introduction The purpose of this article is to outline the problems that we are attempting to solve and the solution currently being considered, this work is being tracked under the following Jira issue: - https://issues.jboss.org/browse/AS7-5901 https://issues.jboss.org/browse/AS7-5901 Currently for remote EJB invocations (Actually all invocations to the server but in this case EJB invocations are the priority) a Remoting connection is established by the client, early in establishing this connection the remote client performs authentication using SASL - once authenticated the authentication is valid for the life of the connection. As EJB invocations are received the identity on this connection is the identity used for the EJB call. The following diagram illustrates the exising calls for remote EJB clients: - https://community.jboss.org/servlet/JiveServlet/showImage/19891/Existing+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19891/Exist... The established connection here is a Remoting connection, the connection itself is independent of any service being accessed and on establishing the connection authentication is performed using the associated realm. Subsequently when the client connects to the EJB Container and sends a request to a deployed EJB the identity used for the EJB call is the identity taken from the underlying connection. As the authentication takes place as the connection is established the only way for the clients to send in requests as an alternative user is to establish a new connection as the new user. A second scenario is where the call is also passed from one server to another: - https://community.jboss.org/servlet/JiveServlet/showImage/19892/Existing+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19892/Exist... In this second scenario there is now a connection from the first server to the second server, this connection also requires authentication and the call to the EJB on the second server runs as the identity of this second connection. These two diagrams illustrate the problems to be solved: - * For a client to run as different identities different connections are required for each identity. * For a server to server call the identity on the second server is the identity of the connection and not the original caller. h3. Remoting Authentication Before reviewing alternative solutions it is worth describing the decisions relating to the authentication of the actual connection as at the very minimum it is desirable that we do not undermine this with a solution that allows interception of the exchanges in such a way that either passwords are revealed or items are revealed that could be basis for a plain text attack. When a client attempts to connect to the Remoting connection a challenge is sent back to the client containing a list of supported authentication SASL mechanisms that the client can select from to attempt to authenticate, the client selects on and attempts the authentication. If authentication succeeds then the client can then request to connect to the service it wished to use, if not the client is re-challenged with the list of mechanisms and this is repeated until the client either successfully authenticates or the list is exhausted. The SASL mechanisms that are offered are selected based on the capabilities of the backing user store - as an example if we have a user store what we can query to obtain the users password or a pre-prepared hash of their password we offer the client the Digest-MD5 mechanism - however if we can only verify a supplied password but not generate the hashes required for Digest based authenitcation then PLAIN is offered as a mechanism. A second SASL mechanism that we also support is the External mechanism, this mechanism is a special mechanism in that it automatically authenticates as an identity associated with the surrounding connection - currently we use this for ClientCert style authentication where after a TLS connection is established authentication will then proceed based on the clients certificate. Another mechanism that we are currently adding support for is GSSAPI, this is a mechanism that authenticates a user by the use of authentication tokens with no exchange of passwords between the points involved in the authentication process. The ability to authenticate using these different approaches where we can reduce the places where either passwords or replayable tokens are visible is the key reason why we do not want to introduce those kind of vulnerabilities in the solution to the two problems being described here. h2. Proposed Solutions This section describes the solutions currently considered and where appropriate describes why those solutions are currently discounted, at this point this is intended to be for discussion rather than a final definitive decision. h3. Solution from Previous Releases In previous AS releases unless a custom RMI socket was used the connections to the application server were not authenticated, instead the username and credential would be passed along with the EJB invocation and intercepted before the call reached the EJB - the supplied information would then be used to authenticate the remote user before allowing the call to proceed. https://community.jboss.org/servlet/JiveServlet/showImage/19893/Previous+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19893/Previ... Where a client wanted to run as multiple identities that was fine as for each invocation a different username and password could be set for the call. This approach also potentially allowed for the security context to be passed onto subsequent servers as the contents from this message invocation are available. https://community.jboss.org/servlet/JiveServlet/showImage/19894/Previous+... https://community.jboss.org/servlet/JiveServlet/downloadImage/19894/Previ... Whilst this approach does solve the problem of being able to switch identities and propagate identities it suffers from the problem that the users password is sent in the clear so should we undertake a similar solution for AS7 it would undermine the protection available from the currently available SASL mechanisms, in addition to this it is assuming that a username / password based authentication is always the approach we will want to take even though there are now alternative mechanisms in common use. h3. Reauthenticate The Connection As the calls are executed as the identity of the connection one approach could be to allow the client side to initiate a re-authentication of the connection so that a different identity can be used. https://community.jboss.org/servlet/JiveServlet/showImage/19895/Reauthent... https://community.jboss.org/servlet/JiveServlet/downloadImage/19895/Reaut... Whilst this would allow a client to switch identities and it could potentially be implemented using the SASL mechanisms the biggest issue here is if the client is multi-threaded and wants to run as multiple identities concurrently. At best the client would need to maintain a pool of connections one for each identity in use and if all identities could be used at once then it is no better than the current situation. The multi threaded client issue is also made worse in the server to server case where sharing a single connection would be a major benefit in reducing the resources used. For the server to server case there is also the issue regarding how is the users identity propagated to the second server, for this possible solution the multi-threaded client problem appears to be sufficiently blocking so will cover that in subsequent solutions. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47864] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11150 -------------------------------------------------- Of course, any modifications made to the ear at runtime will be lost when the patch is applied, since the old version of the module will no longer take precedence on the module path and will not be used. I recommend you talk to the portal folks about how I recommended they deal with a requirement to use an exploded deployment. In their case it was user-modifiable and couldn't be deployed from inside a module. Better yet, just write to the data/ dir or something and don't write inside the ear. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11149 -------------------------------------------------- At FibosubsystemAdd, line 74, you wouldn't be able to use contentItem.get(URL).set(urlString); Instead, you need to convert the URL into a filesystem path (which hopefully will work) and then do: contentItem.get(PATH).set(filesystemPath); contentItem.get(ARCHIVE).set(false); I haven't tried this. The bigger problem is the fact that you are going to be writing to the module. That means when we patch the module and we attempt to detect if the user has modified the module so we can require that we approve the override, we're going to see that the module doesn't have the same hash as the original one did when we prepared the patch. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - AS7 projects

by jaikiran pai

jaikiran pai [https://community.jboss.org/people/jaikiran] modified the document: "AS7 projects" To view the document, visit: https://community.jboss.org/docs/DOC-16399 -------------------------------------------------------------- AS7 is comprised of the following projects: || *Description* || *Project link * || *Version control link * || *IRC room * || *Issue tracking * || | AS7 core | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-as | #jboss-as7 | https://issues.jboss.org/browse/AS7 | | Java Connector Architecture | http://www.jboss.org/ironjacamar | http://anonsvn.jboss.org/repos/jbossas/projects/jboss-jca/trunk | | https://jira.jboss.org/jira/browse/JBJCA | | Management Console | http://www.jboss.org/jbossas | https://github.com/jbossas/console | | https://issues.jboss.org/browse/AS7 | | Modular Classloading System | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-modules | | https://issues.jboss.org/browse/MODULES | | Modular Service Container | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-msc | | https://issues.jboss.org/browse/MSC | | Java Annotation Indexer | http://www.jboss.org/jbossas | https://github.com/jbossas/jandex | | https://issues.jboss.org/browse/JANDEX | | JBoss Invocation API | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-invocation | | | | JBoss Class File Writer | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-classfilewriter | | | | JBoss Logging | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-logginghttps://github.com/jboss-logging/... | | https://issues.jboss.org/browse/JBLOGGING | | Dynamic Model Representation | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-dmr | | | | StAX facade with plugability + usability enhancements | http://www.jboss.org/jbossas | https://github.com/jbossas/staxmapper | | | | JBoss Threads | http://www.jboss.org/jbossas | https://github.com/jbossas/jboss-threads | | https://issues.jboss.org/browse/JBTHR | | JBoss Transactions | http://www.jboss.org/jbosstm | http://anonsvn.jboss.org/repos/labs/labs/jbosstm/trunk/ | | http://jira.jboss.org/jira/browse/JBTM | | Weld (CDI) Java Contexts and Dependency Injection | http://seamframework.org/Weld | http://github.com/weld | | https://issues.jboss.org/browse/WELD | | Hibernate | http://www.hibernate.org | https://github.com/hibernate/hibernate-orm (https://github.com/hibernate/hibernate-core/) | #hibernate | * integration issues -> https://issues.jboss.org/browse/hibernate * Hibernate issues -> http://opensource.atlassian.com/projects/hibernate | | OSGi | http://www.jboss.org/jbossas/osgi | http://github.com/jbosgi/jbosgi | | https://jira.jboss.org/browse/JBOSGI (https://issues.jboss.org/browse/JBOSGI) | | Arquillian for testing | http://www.jboss.org/arquillian | https://github.com/arquillian/ (https://github.com/arquillian/arquillian) | | https://jira.jboss.org/jira/browse/ARQ | | JBoss Java EE API | http://www.jboss.org/jbossas | https://github.com/jboss | | https://issues.jboss.org/browse/JBEE | | JBoss (VFS) Virtual File System | http://www.jboss.org/jbossas | http://github.com/jbossas/jboss-vfs | | https://issues.jboss.org/browse/JBVFS | | JBoss invocation API | | https://github.com/jbossas/jboss-invocation | | | | JGroups communications library for clustering | http://jgroups.org/ | http://www.github.com/belaban/JGroups | | http://jira.jboss.com/jira/browse/JGRP | | JBoss Web Services | http://www.jboss.org/jbossws/ | http://anonsvn.jboss.org/repos/jbossws | | https://issues.jboss.org/browse/JBWS | | JBoss Remoting JMX | | https://github.com/darranl/remoting-jmx | | https://issues.jboss.org/browse/REMJMX | | JBoss Remoting | http://www.jboss.org/jbossremoting http://www.jboss.org/jbossremoting/remoting-3.html | https://github.com/jboss-remoting/jboss-remoting | | https://jira.jboss.org/jira/browse/JBREM | | JBoss Marshalling | http://www.jboss.org/jbossmarshalling | https://github.com/jboss-remoting/jboss-marshalling | #jboss-marshalling | http://jira.jboss.org/jira/browse/JBMAR | | Infinispan | http://www.jboss.org/infinispan | https://github.com/infinispan/infinispan | #infinispan | http://jira.jboss.org/jira/browse/ISPN | | Patched version of Mojarra | | https://github.com/jboss/mojarra/ | #jboss-as7 | | All IRC channels are at Freenode IRC servers. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-16399] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Re: Unable to deploy Webservice in Jboss 7:

by Nicklas Karlsson

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: Unable to deploy Webservice in Jboss 7:" To view the discussion, visit: https://community.jboss.org/message/776925#776925 -------------------------------------------------------------- On the same JBoss instance? How do you configure the ports? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776925#776925] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Extensions, Subsystem and their Dependencies

by Dmitri Zamysloff

Dmitri Zamysloff [https://community.jboss.org/people/dzcs] created the discussion "Extensions, Subsystem and their Dependencies" To view the discussion, visit: https://community.jboss.org/message/776404#776404 -------------------------------------------------------------- Hi guys, I am developing new extension for Jboss 7.1.1.Final for project needs and actually, thanx to people who did the documentation and archetype, I am pretty done. One thing which is not disclosed in documentation and which I cannot find anywhere is how to define dependencies in my subsystem or extension - practically how to say jboss, that my extension depends on other subsystems. In my example I get datasource name and topic configured for my subsystem as simple string attributes (can be I had to use something else - dunno - so far string). But how can I ensure, that "datasources" and "messaging" subsystems are started and have already deployed their stuff (datasources and topics) before start of my subsystem is called? As I said this topic is not documented well and unfortunatelly I could not find much info on it. Javadoc is also mostly absent. Many thanks for your help in advance. Dmitri -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776404#776404] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
2
0 / 0

[JBoss AS 7 Development] - Unable to deploy Webservice in Jboss 7, Exception as stated below:

by Genrose Hirudaysamy

Genrose Hirudaysamy [https://community.jboss.org/people/genrosesusai] created the discussion "Unable to deploy Webservice in Jboss 7, Exception as stated below:" To view the discussion, visit: https://community.jboss.org/message/776905#776905 -------------------------------------------------------------- JBAS015533: Web Service endpoint com.x.y.Z with URL pattern /* is already registered. Web service endpoint com.x.y.Z is requesting the same URL pattern. Can somebody through light on this. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776905#776905] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by John Mazzitelli

John Mazzitelli [https://community.jboss.org/people/mazz] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11148 -------------------------------------------------- Regarding "Patching Deployments" along with the "Mixed Approach" prototype described in https://community.jboss.org/docs/DOC-25627 ExtendingAS7 page. The prototype says to package the deployment (say, an EAR) in an unexploded, zipped format (so you literally would have one file in the module called "mydep.ear" or "myapp.war"). Should it be possible to allow for the Mixed Approach to deploy exploded content (so the module would have a directory structure "mydep.ear/<the content>"). How would this affect this patching mechanism? I bring this up because of the following use-case : suppose we have legacy code (that used to go in the scanned deployments directory but will now be using the new Mixed Approach method) - and that legacy code reads individual files from within the ear (and could even WRITE files to directories under the ear). So, the questions are: 1) Can the Mixed Approached deploy exploded content (the prototype's code assumes unexploded, I'm not sure what the code should look like if it wants to deploy exploded deployments)? 2) Does deployment of exploded content via the Mixed Approach present any problems/issues wrt the new patching mechanism? --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[IronJacamar Development] - Re: Management of IronJacamar

by Kamran Muhammad

Kamran Muhammad [https://community.jboss.org/people/muhammad.kamran] created the discussion "Re: Management of IronJacamar" To view the discussion, visit: https://community.jboss.org/message/776709#776709 -------------------------------------------------------------- Thanks . i have been using the DMR through jboss-cli.bat. "Its a service within AS with a name of ConnectorServices.IRONJACAMAR_MDR, so you need to add a dependency on it from your code and get it injected - ...addDependency(ConnectorServices.IRONJACAMAR_MDR, AS7MetadataRepository.class, service.getMdrInjector())." where to have it coded then. ? Thanks -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776709#776709] Start a new discussion in IronJacamar Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
1
0 / 0

Re: [jboss-dev-forums] [PicketBox Development] - JBoss AS7: Security : Custom Login Modules

by Jay Kumar SenSharma

Jay Kumar SenSharma [https://community.jboss.org/people/jaysensharma] commented on the document "JBoss AS7: Security : Custom Login Modules" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-17357#comment-11145 -------------------------------------------------- In the Original article the PATH of the properties file (in th value) is not mentioned which will cause the validation to fail: > <module-option name="usersProperties" value="users.properties"/> > <module-option name="rolesProperties" value="roles.properties"/> It worked for me after adding the location of these propertieds files as following: > <module-option name="usersProperties" value="${jboss.server.config.dir}/users.properties"/> > <module-option name="rolesProperties" value="${jboss.server.config.dir}/roles.properties"/> --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS Development Deployment Framework] - Re: Incorrect Undeployment Order

by Vladimir Smirnov

Vladimir Smirnov [https://community.jboss.org/people/bobzer] created the discussion "Re: Incorrect Undeployment Order" To view the discussion, visit: https://community.jboss.org/message/776825#776825 -------------------------------------------------------------- Tried to update JBoss Deployer libraries in JBoss 5.1 from version 2.0.7.GA to 2.0.9.GA, but dependecies on classes in another services did not let me do it. Then i have manually patched lib/jboss-deployers-impl.jar, replacing org.jboss.deployers.plugins.main.MainDeployerImpl class, taken from http://repo1.maven.org/maven2/org/jboss/deployers/jboss-deployers-impl/2.... jboss-deployers-impl-2.0.9.GA.jar. After that, server is working correctly and undeploy order is correct. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776825#776825] Start a new discussion in JBoss AS Development Deployment Framework at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss Portal Development] - Re: Why is JB Portal gone? Is GateIn Portal really the replacement?

by Santhosh Srinivasan

Santhosh Srinivasan [https://community.jboss.org/people/monsieursanta] created the discussion "Re: Why is JB Portal gone? Is GateIn Portal really the replacement?" To view the discussion, visit: https://community.jboss.org/message/776740#776740 -------------------------------------------------------------- @Tuan were you able to develop a JBoss portlet and deploy the same in GateIn -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776740#776740] Start a new discussion in JBoss Portal Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
1
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - ManagementLayer RBAC

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document "ManagementLayer RBAC" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47854#comment-11140 -------------------------------------------------- I added a requirement to secure JMX interactions that don't end up delegating into the normal ModelController layer (i.e. mbeans outside the jboss-as JMX domain.) My hope is such mbeans can simply be another type of resource, with a different kind of address (ObjectName instead of PathAddress). I think that if there is any overlap in the permission configuration between JMX and the core management model, the allowed actions for a given request become the intersection of the sets of permissions. IOW, if the JMX scheme allows access to mbean jboss-as:subsystem=security but the core management model doesn't allow access to /subsystem=security, then the request will fail. This can be accomplished by doing a permission check in the JMX layer, and then the normal core management check is done in the core layer. Another option is to not allow JMX permissions to be set up for the JMX domains that result in calls into the core management layer. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. *Core Concepts* * * When defining an RBAC model, the following conventions are useful: * Subject = A person or automated agent * Role = Job function or title which defines an authority level * Permissions = An approval of a mode of access to a resource * Action = An operation to execute on a resource * Constraint: Predicate that makes the permission valid in the context of the system state * Session = A mapping involving Subject, Role and/or Permissions https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-30-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-3... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Enable customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* * +Support permission enforcement that restricts visibility of model elements: +Control visibility of resources (i.e. restrict visibility of server groups) * +Support permission enforcement that restricts execution on model elements+: Control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) * +The management layer needs to enforce permission regardless of the client type and availability: +I.e. enformenent can not be delegated to the client only+ + * +Clients (CLI, Web) should indicate permissions prior to execution of management operations:+ I.e. grey out interface elements to emphasis lack of permissions * JMX access that isn't delegated to the ModelController needs to be covered by the permission scheme as well *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideration - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself - Ability to hide the existence of a resource altogether, vs the ability to show its existence but hide its content. The issue here is in some cases the address of the resource itself may provide sensitive information, e.g. security-realm=ManagementRealm structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS Development Deployment Framework] - Unfinished deployment in JBoss 7.1.1 on linux

by Zeev Lazarev

Zeev Lazarev [https://community.jboss.org/people/zlazarev256] created the discussion "Unfinished deployment in JBoss 7.1.1 on linux" To view the discussion, visit: https://community.jboss.org/message/776731#776731 -------------------------------------------------------------- Hi, After some porting changes from JBoss 5.1.0 to JBoss 7.1.1 our application worked fine on Windows 7 platform. When trying to deploy this application on linux machine (both Ubuntu and RedHat, were tried) I encounter an issue by which deployment enters idle state. After investigating the issue I realized that a servlet in its init() method is awaiting for the proxy component that represents my EJB stateless session bean. The code snippets below leads to the 'gate' flag for that component that on Windows 7 is 'ture' and on linux machine is 'false': # componentName | CAAdminSessionBean # componentClass | class org.ejbca.core.ejb.ca.caadmin.CAAdminSessionBean # org.jboss.as.ejb3.component.stateless.StatelessSessionComponent(org.jboss.as.ee.component.BasicComponent) protected BasicComponentInstance constructComponentInstance(ManagedReference instance, boolean invokePostConstruct, InterceptorFactoryContext context) { -> waitForComponentStart(); ... } protected void waitForComponentStart() { if (!gate) { // Block until successful start synchronized (this) { if (stopping.get()) { throw MESSAGES.componentIsStopped(); } while (!gate) { // TODO: check for failure condition try { -> wait(); } catch (InterruptedException e) { Thread.currentThread().interrupt(); throw MESSAGES.componentNotAvailable(); } } } } } The stack of JBoss Interceptors is given in reverse order to track back the issue that starts in servlet: The interesting thing is that the proxy for local interface is created (it is represented by View39), but the bean itselft is not - this is indicated by gate = false flag. # # org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal$$$View39 # Proxy for view class: org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal of EJB: CAAdminSessionBean # caAdminSession | org.ejbca.core.ejb.ca.caadmin.CAAdminSessionLocal # # # org.ejbca.ui.web.admin.configuration.StartServiceServlet public void init(ServletConfig config) throws ServletException { . . . -> caAdminSession.initializeAndUpgradeCAs(admin); . . . } # org.jboss.as.ee.component.ProxyInvocationHandler public Object invoke(final Object proxy, final Method method, final Object[] args) throws Throwable { final Interceptor interceptor = interceptors.get(method); if (interceptor == null) { throw new NoSuchMethodError(method.toString()); } final InterceptorContext context = new InterceptorContext(); // special location for original proxy context.putPrivateData(Object.class, proxy); context.putPrivateData(Component.class, component); context.putPrivateData(ComponentView.class, componentView); context.setParameters(args); context.setMethod(method); // setup the public context data context.setContextData(new HashMap()); -> return interceptor.processInvocation(context); } # org.jboss.invocation.ChainedInterceptor public Object processInvocation(final InterceptorContext context) throws Exception { final int oldNext = context.getNextInterceptorIndex(); final List<Interceptor> old = context.getInterceptors(); context.setInterceptors(interceptors); try { -> return context.proceed(); } finally { context.setInterceptors(old, oldNext); } } # org.jboss.invocation.InterceptorContext public Object proceed() throws Exception { final ListIterator<Interceptor> iterator = interceptorIterator; if (iterator.hasNext()) { Interceptor next = iterator.next(); try { -> return next.processInvocation(this); } finally { if (iterator.hasPrevious()) iterator.previous(); } } else { throw msg.cannotProceed(); } } # org.jboss.as.ee.component.TCCLInterceptor public Object processInvocation(final InterceptorContext context) throws Exception { final ClassLoader oldTccl = SecurityActions.getContextClassLoader(); try { SecurityActions.setContextClassLoader(classLoader); -> return context.proceed(); } finally { SecurityActions.setContextClassLoader(oldTccl); } } # # org.jboss.as.ejb3.tx.CMTTxInterceptor public Object processInvocation(InterceptorContext invocation) throws Exception { final EJBComponent component = (EJBComponent) invocation.getPrivateData(Component.class); final MethodIntf methodIntf = MethodIntfHelper.of(invocation); final TransactionAttributeType attr = component.getTransactionAttributeType(methodIntf, invocation.getMethod()); final int timeoutInSeconds = component.getTransactionTimeout(methodIntf, invocation.getMethod()); switch (attr) { case MANDATORY: return mandatory(invocation, component); case NEVER: return never(invocation, component); case NOT_SUPPORTED: return notSupported(invocation, component); case REQUIRED: -> return required(invocation, component, timeoutInSeconds); case REQUIRES_NEW: return requiresNew(invocation, component, timeoutInSeconds); case SUPPORTS: return supports(invocation, component); default: throw new IllegalStateException("Unexpected tx attribute " + attr + " on " + invocation); } } # org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor public Object processInvocation(InterceptorContext context) throws Exception { PooledComponent<ComponentInstance> component = (PooledComponent<ComponentInstance>) getComponent(context, EJBComponent.class); -> ComponentInstance instance = component.getPool().get(); context.putPrivateData(ComponentInstance.class, instance); boolean discarded = false; try { # StrictMaxPool public T get() { . . . T bean = null; try { // Pool is empty, create an instance -> bean = create(); } finally { . . . return bean; } # org.jboss.as.ejb3.component.stateless.StatelessSessionComponent StatelessObjectFactory<StatelessSessionComponentInstance> factory = new StatelessObjectFactory<StatelessSessionComponentInstance>() { @Override public StatelessSessionComponentInstance create() { -> return (StatelessSessionComponentInstance) createInstance(); } @Override public void destroy(StatelessSessionComponentInstance obj) { obj.destroy(); } }; # componentName | CAAdminSessionBean # componentClass | class org.ejbca.core.ejb.ca.caadmin.CAAdminSessionBean # org.jboss.as.ejb3.component.stateless.StatelessSessionComponent(org.jboss.as.ee.component.BasicComponent) protected BasicComponentInstance constructComponentInstance(ManagedReference instance, boolean invokePostConstruct, InterceptorFactoryContext context) { -> waitForComponentStart(); ... } protected void waitForComponentStart() { if (!gate) { // Block until successful start synchronized (this) { if (stopping.get()) { throw MESSAGES.componentIsStopped(); } while (!gate) { // TODO: check for failure condition try { -> wait(); } catch (InterruptedException e) { Thread.currentThread().interrupt(); throw MESSAGES.componentNotAvailable(); } } } } } The structure of the application ear file is 8 war modules, 2 ejb modules and the library jars under lib entry: adminweb.war ... more 7 wars ... ejbca-ejb.jar ejbca-ws-ejb.jar I tried following things: 1. Changed @Stateless(mappedName=__old_jndiName__ to @Stateless(mappedName=java:global/ejbca/ejbca-ejb/CAAdminSessionBean!org.ejbca.ca.caadmin.CAAdminSessionRemote) 2. Added below entry to standalone.xml to explicitly tie war module with ejb. <ear-subdeployments-isolated>false</ear-subdeployments-isolated> 3. Added jboss-deployment-structure.xml file to META-INF of ear file to explicitly tie war module with ejb. <jboss-deployment-structure> <sub-deployment name="adminweb.war"> <dependencies> <module name="deployment.ejbca.ear.ejbca-ejb.jar" /> </dependencies> </sub-deployment> </jboss-deployment-structure> The latter led to unnecessary dependencies errors in the logs. Please advise. Thanks. Zeev -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776731#776731] Start a new discussion in JBoss AS Development Deployment Framework at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[IronJacamar Development] - Re: Management of IronJacamar

by Jesper Pedersen

Jesper Pedersen [https://community.jboss.org/people/jesper.pedersen] created the discussion "Re: Management of IronJacamar" To view the discussion, visit: https://community.jboss.org/message/775347#775347 -------------------------------------------------------------- You need to use the DMR API - see the AS7 user forum and AS7 documentation for examples. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775347#775347] Start a new discussion in IronJacamar Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

3
8
0 / 0

Community Updates, November 8 - November 15

by JBoss Community

=============================================================== Community Updates for November 8 - November 15 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,193 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,484 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Sessions and transactions [https://community.jboss.org/docs/DOC-13951] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * JBoss Tools 3.3 and Developer Studio 5.0 Final Release! [https://community.jboss.org/community/tools/blog/2012/06/21/jboss-tools-3...] * Statement Regarding Security Threat to JBoss Application Server [https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-secu...] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/746287#746287] * Re: Jboss 7.1.2.Final is only for EAP? [https://community.jboss.org/message/776207#776207] * Re: Jboss and mysql connector [https://community.jboss.org/message/649296#649296] Tips and tricks - Table of Contents Did you know you can easily add a Table of Contents to anything you create in Community? Use the Style menu in the editor to select any of the Header styles and the header text will be added to the Table of Contents with a link to that part of the content. Then insert the Table of Contents from the >> menu in the editor and the Table of Contents will show up where ever you inserted it. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

13 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - JAX-WS fails to unmarshal payload due to strict namespaces

by Morten Nyhaug

Morten Nyhaug [https://community.jboss.org/people/morten.nyhaug] created the discussion "JAX-WS fails to unmarshal payload due to strict namespaces" To view the discussion, visit: https://community.jboss.org/message/776631#776631 -------------------------------------------------------------- I have a web service that receives the following payload {code:xml} <soap-env:Envelope xmlns:soap-env=" http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Header/> <soap-env:Body> <mm7:DeliverReq xmlns:mm7=" http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <MM7Version>5.3.0</MM7Version> </mm7:DeliverReq> </soap-env:Body> </soap-env:Envelope> {code} I have generated classes for the schema using xjc, and created a webservice with an endpoint interface to receive it {code} @WebService(name = "deliver") @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) @XmlSeeAlso({ org._3gpp.ftp.specs.archive._23_series._23_140.schema.rel_5_mm7_1_0.ObjectFactory.class }) public interface Rel5Mm710ReceiverApi { @WebMethod(action = "deliverRequest") @WebResult(name = "DeliverRsp", targetNamespace = " http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0") public DeliverRspType deliverRequest( @WebParam(name = "DeliverReq", targetNamespace = " http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0") DeliverReqType request); } {code} {code} @WebService(serviceName = "soap") @HandlerChain(file = "handler.xml") public class InboundApi implements Rel5Mm710ReceiverApi { @Override @WebMethod public DeliverRspType deliverRequest(DeliverReqType request) { ... } } {code} When I deploy this service on jboss as 7.1 and test it with soap ui by sending in the payload shown above, I get the following error: {noformat} 10:52:56,107 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http--127.0.0.1-8080-1) Interceptor for { http://mms.tele2.returia.nrk.no/ http://mms.tele2.returia.nrk.no/}soap#{ http://api.mm7.returia.nrk.no/ http://api.mm7.returia.nrk.no/}deliverRequest has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unmarshalling Error: unexpected element (uri:"", local:"MM7Version"). Expected elements are <{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...> at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:801) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:642) at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:156) at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:201) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207) ... Caused by: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"MM7Version"). Expected elements are <{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>,<{ http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1...>] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:434) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:371) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:348) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:778) ... 31 more {noformat} The funny thing is, if I try to unmarshal this using JAXB, I get no errors at all. If I try to modify the payload so that it is like this: {code:xml} <mm7:DeliverReq xmlns:mm7=" http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <mm7:MM7Version>5.3.0</mm7:MM7Version> </mm7:DeliverReq> {code} I also get no errors. Obviously changing the payload is not an option since I cant control what 3rd parties are sending me. How can I get rid of this error? How can I tell JAX-WS to not be so strict regarding namespaces? I have tried using a SOAPHandler to set some properties or other, but no amount of googeling has led me to the correct solution. Since JAXB is able to unmarshal this, then surly it must be possible to make JAX-WS do this as well? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776631#776631] Start a new discussion in JBoss Web Services Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11135 -------------------------------------------------- > Dave Chen wrote: > > > > For those distributing web app with JBOSS, it is more convenient to bundle JSF imp inside war, so do not need to change jboss container. Just drop the war for installation. Sometimes that's true. WAR_BUNDLES_JSF_IMPL is not going away. So you can still do that if you want. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "Design of AS7 multi-JSF feature" To view the document, visit: https://community.jboss.org/docs/DOC-47689 -------------------------------------------------------------- *About multi-JSF* Currently, AS7 ships with two JSF implementations, a JSF 2.1 implementation and a JSF 1.2 implementation. A web application can select which implementation is used by including a context param in web.xml. By default, it uses the JSF 2.1 imlementation. "multi-JSF" allows installation of multiple JSF implementations (and versions) on the same AS7 server. The goal is to allow use of any JSF implementation (MyFaces or Mojarra) and any version of those implementation from JSF 1.1 all the way up to the experimental JSF 2.2 versions. This is far superior to the old WAR_BUNDLES_JSF_IMPL method because JSF jars do not need to be bundled with the webapp. More importantly, "multi-JSF" provides an implementation that is fully integrated with the container. This means more efficient annotation processing, lifecycle handling, and other integration advantages. *How it works* The way multi-JSF will work is that for each JSF version, a new slot is created in the modules path under *com.sun.jsf-impl*, *javax.faces.api*, and *org.jboss.as.jsf-injection*. When the jsf-subsystem is started, it scans the module path to find all the installed JSF implementations. When the JSF subsystem deploys a web app containing the specified context param, it adds the slotted modules to the deployment. Here is an example of the context param for the latest milestone of Mojarra 2.2: <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>mojarra-2.2.0-m05</param-value> </context-param> *How a JSF implementation is installed* A single JSF implementation is installed using a https://community.jboss.org/docs/DOC-18945 CLI deployment archive. This archive includes the required jars and module.xml files. It also includes CLI scripts for installing/uninstalling the JSF impls using the https://issues.jboss.org/browse/AS7-4265 CLI module command. You execute the installation archive like this: > [standalone@localhost:9999 /] deploy <local path to archive>/install-mojarra-2.2.0-m05.cli The install script inside the archive looks like this: > module add --name=javax.faces.api --slot=mojarra-2.2.0-m05 --resources=jsf-api-2.2.0-m05.jar --module-xml=mojarra-api-module.xml > module add --name=com.sun.jsf-impl --slot=mojarra-2.2.0-m05 --resources=jsf-impl-2.2.0-m05.jar --module-xml=mojarra-impl-module.xml > module add --name=org.jboss.as.jsf-injection --slot=mojarra-2.2.0-m05 --resources=jboss-as-jsf-injection-7.2.0.Alpha1-SNAPSHOT.jar --module-xml=injection-module.xml *How the CLI deployment archives are created* A CLI deployment archive for a JSF implementation/version is created using a standalone maven project you can https://github.com/ssilvert/jboss-jsf-installer download from GitHub and run. To create an archive with the project, you call it like this: *mojarra example* > mvn -Djsf-version=2.2.0-m05 -Pmojarra clean assembly:single *myfaces example* > mvn -Djsf-version=2.1.8 -Pmyfaces clean assembly:single This pulls in the JSF resources and creates the install/uninstall scripts. It is all bundled together in an archive (zip) file that must be manually renamed with a .cli extension. *How to change the default JSF implementation in AS7* The multi-JSF feature adds two new attributes to the JSF subsystem. The first, +active-jsf-impls+, is just a read-only list of the installed JSF implementations. The second, +default-jsf-impl-slot+, allows you to change the default JSF implementation. You just need to issue a write-attribute command and set the value to one of the active impls. Then restart AS7. https://community.jboss.org/servlet/JiveServlet/showImage/102-47689-8-198... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47689-8... Alternatively, you can set this in your configuration file, such as standalone.xml: <subsystem xmlns="urn:jboss:domain:jsf:1.0" default-jsf-impl-slot="mojarra-2.2.0-m05"/> Lastly, you can execute the +list-active-jsf-impls+ operation. This is useful if you are writing an AS7 client and you need the list of impls as a ModelType.LIST. /subsystem=jsf/:list-active-jsf-impls { "outcome" => "success", "result" => [ "myfaces-2.1.8", "mojarra-2.2.0-m05", "1.2", "main" ] } *Demo* I've attached a copy of install-mojarra-2.2.0-m05.cli and install-myfaces-2.1.8.cli. You can unzip to take a look at it. You can even deploy it with the latest nightly build of AS7. This will let you see how the modules are installed. I'm not quite done with updates to the jsf-subsystem, so you can't see multi-jsf in action on a webapp yet. If you want to try it out though, let me know. I can upload a working version to my github account. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47689] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Dave Chen

Dave Chen [https://community.jboss.org/people/javatwo] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11134 -------------------------------------------------- For those distributing web app with JBOSS, it is more convenient to bundle JSF imp inside war, so do not need to change jboss container. Just drop the war for installation. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "Design of AS7 multi-JSF feature" To view the document, visit: https://community.jboss.org/docs/DOC-47689 -------------------------------------------------------------- *About multi-JSF* Currently, AS7 ships with two JSF implementations, a JSF 2.1 implementation and a JSF 1.2 implementation. A web application can select which implementation is used by including a context param in web.xml. By default, it uses the JSF 2.1 imlementation. "multi-JSF" allows installation of multiple JSF implementations (and versions) on the same AS7 server. The goal is to allow use of any JSF implementation (MyFaces or Mojarra) and any version of those implementation from JSF 1.1 all the way up to the experimental JSF 2.2 versions. This is far superior to the old WAR_BUNDLES_JSF_IMPL method because JSF jars do not need to be bundled with the webapp. More importantly, "multi-JSF" provides an implementation that is fully integrated with the container. This means more efficient annotation processing, lifecycle handling, and other integration advantages. *How it works* The way multi-JSF will work is that for each JSF version, a new slot is created in the modules path under *com.sun.jsf-impl*, *javax.faces.api*, and *org.jboss.as.jsf-injection*. When the jsf-subsystem is started, it scans the module path to find all the installed JSF implementations. When the JSF subsystem deploys a web app containing the specified context param, it adds the slotted modules to the deployment. Here is an example of the context param for the latest milestone of Mojarra 2.2: <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>mojarra-2.2.0-m05</param-value> </context-param> *How a JSF implementation is installed* A single JSF implementation is installed using a https://community.jboss.org/docs/DOC-18945 CLI deployment archive. This archive includes the required jars and module.xml files. It also includes CLI scripts for installing/uninstalling the JSF impls using the https://issues.jboss.org/browse/AS7-4265 CLI module command. You execute the installation archive like this: > [standalone@localhost:9999 /] deploy <local path to archive>/install-mojarra-2.2.0-m05.cli The install script inside the archive looks like this: > module add --name=javax.faces.api --slot=mojarra-2.2.0-m05 --resources=jsf-api-2.2.0-m05.jar --module-xml=mojarra-api-module.xml > module add --name=com.sun.jsf-impl --slot=mojarra-2.2.0-m05 --resources=jsf-impl-2.2.0-m05.jar --module-xml=mojarra-impl-module.xml > module add --name=org.jboss.as.jsf-injection --slot=mojarra-2.2.0-m05 --resources=jboss-as-jsf-injection-7.2.0.Alpha1-SNAPSHOT.jar --module-xml=injection-module.xml *How the CLI deployment archives are created* A CLI deployment archive for a JSF implementation/version is created using a standalone maven project you can https://github.com/ssilvert/jboss-jsf-installer download from GitHub and run. To create an archive with the project, you call it like this: *mojarra example* > mvn -Djsf-version=2.2.0-m05 -Pmojarra clean assembly:single *myfaces example* > mvn -Djsf-version=2.1.8 -Pmyfaces clean assembly:single This pulls in the JSF resources and creates the install/uninstall scripts. It is all bundled together in an archive (zip) file that must be manually renamed with a .cli extension. *How to change the default JSF implementation in AS7* The multi-JSF feature adds two new attributes to the JSF subsystem. The first, +active-jsf-impls+, is just a read-only list of the installed JSF implementations. The second, +default-jsf-impl-slot+, allows you to change the default JSF implementation. You just need to issue a write-attribute command and set the value to one of the active impls. Then restart AS7. https://community.jboss.org/servlet/JiveServlet/showImage/102-47689-5-198... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47689-5... Alternatively, you can set this in your configuration file, such as standalone.xml: <subsystem xmlns="urn:jboss:domain:jsf:1.0" default-jsf-impl-slot="mojarra-2.2.0-m05"/> *Demo* I've attached a copy of install-mojarra-2.2.0-m05.cli and install-myfaces-2.1.8.cli. You can unzip to take a look at it. You can even deploy it with the latest nightly build of AS7. This will let you see how the modules are installed. I'm not quite done with updates to the jsf-subsystem, so you can't see multi-jsf in action on a webapp yet. If you want to try it out though, let me know. I can upload a working version to my github account. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47689] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "Design of AS7 multi-JSF feature" To view the document, visit: https://community.jboss.org/docs/DOC-47689 -------------------------------------------------------------- *About multi-JSF* Currently, AS7 ships with two JSF implementations, a JSF 2.1 implementation and a JSF 1.2 implementation. A web application can select which implementation is used by including a context param in web.xml. By default, it uses the JSF 2.1 imlementation. "multi-JSF" allows installation of multiple JSF implementations (and versions) on the same AS7 server. The goal is to allow use of any JSF implementation (MyFaces or Mojarra) and any version of those implementation from JSF 1.1 all the way up to the experimental JSF 2.2 versions. This is far superior to the old WAR_BUNDLES_JSF_IMPL method because JSF jars do not need to be bundled with the webapp. More importantly, "multi-JSF" provides an implementation that is fully integrated with the container. This means more efficient annotation processing, lifecycle handling, and other integration advantages. *How it works* The way multi-JSF will work is that for each JSF version, a new slot is created in the modules path under *com.sun.jsf-impl*, *javax.faces.api*, and *org.jboss.as.jsf-injection*. When the jsf-subsystem is started, it scans the module path to find all the installed JSF implementations. When the JSF subsystem deploys a web app containing the specified context param, it adds the slotted modules to the deployment. Here is an example of the context param for the latest milestone of Mojarra 2.2: <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>mojarra-2.2.0-m05</param-value> </context-param> *How a JSF implementation is installed* A single JSF implementation is installed using a https://community.jboss.org/docs/DOC-18945 CLI deployment archive. This archive includes the required jars and module.xml files. It also includes CLI scripts for installing/uninstalling the JSF impls using the https://issues.jboss.org/browse/AS7-4265 CLI module command. You execute the installation archive like this: > [standalone@localhost:9999 /] deploy <local path to archive>/install-mojarra-2.2.0-m05.cli The install script inside the archive looks like this: > module add --name=javax.faces.api --slot=mojarra-2.2.0-m05 --resources=jsf-api-2.2.0-m05.jar --module-xml=mojarra-api-module.xml > module add --name=com.sun.jsf-impl --slot=mojarra-2.2.0-m05 --resources=jsf-impl-2.2.0-m05.jar --module-xml=mojarra-impl-module.xml > module add --name=org.jboss.as.jsf-injection --slot=mojarra-2.2.0-m05 --resources=jboss-as-jsf-injection-7.2.0.Alpha1-SNAPSHOT.jar --module-xml=injection-module.xml *How the CLI deployment archives are created* A CLI deployment archive for a JSF implementation/version is created using a standalone maven project you can https://github.com/ssilvert/jboss-jsf-installer download from GitHub and run. To create an archive with the project, you call it like this: *mojarra example* > mvn -Djsf-version=2.2.0-m05 -Pmojarra clean assembly:single *myfaces example* > mvn -Djsf-version=2.1.8 -Pmyfaces clean assembly:single This pulls in the JSF resources and creates the install/uninstall scripts. It is all bundled together in an archive (zip) file that must be manually renamed with a .cli extension. *How to change the default JSF implementation in AS7* The multi-JSF feature adds two new attributes to the JSF subsystem. The first, +active-jsf-impls+, is just a read-only list of the installed JSF implementations. The second, +default-jsf-impl-slot+, allows you to change the default JSF implementation. You just need to issue a write-attribute command and set the value to one of the active impls. Then restart AS7. https://community.jboss.org/servlet/JiveServlet/showImage/102-47689-4-198... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47689-4... Alternatively, you can set this in your configuration file, such as standalone.xml: <subsystem xmlns="urn:jboss:domain:jsf:1.0" default-jsf-impl-slot="mojarra-2.2.0-m05"/> *Demo* I've attached a copy of install-mojarra-2.2.0-m05.cli and install-myfaces-2.1.8.cli. You can unzip to take a look at it. You can even deploy it with the latest nightly build of AS7. This will let you see how the modules are installed. I'm not quite done with updates to the jsf-subsystem, so you can't see multi-jsf in action on a webapp yet. If you want to try it out though, let me know. I can upload a working version to my github account. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47689] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[jBPM Development] - Issue building 5.4.0.Final on linux

by Peter Courcoux

Peter Courcoux [https://community.jboss.org/people/peter_courcoux] created the discussion "Issue building 5.4.0.Final on linux" To view the discussion, visit: https://community.jboss.org/message/776437#776437 -------------------------------------------------------------- Hi, I have downloaded the 5.4.0.Final tagged sources from https://github.com/droolsjbpm/jbpm/tags https://github.com/droolsjbpm/jbpm/tags, extracted the folder and built using "mvn clean install -DskipTests". Building on windows 7 using java jdk1.7.0_05 I get a successful build. Building on ubuntu linux using the same jdk I get an error: [INFO] Building jBPM :: JPA Persistence 5.4.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jbpm-persistence-jpa --- [INFO] Deleting /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa/target [INFO] Deleting /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa (includes = [btm*, JPADroolsFlow.*.db], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ jbpm-persistence-jpa --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ jbpm-persistence-jpa --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 5 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ jbpm-persistence-jpa --- [INFO] Compiling 17 source files to /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa/src/main/java/org/jbpm/persistence/jta/ContainerManagedTransactionManager.java:[20,24] error: cannot find symbol [ERROR] package javax.transaction /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa/src/main/java/org/jbpm/persistence/jta/ContainerManagedTransactionManager.java:[50,14] error: cannot find symbol [ERROR] class ContainerManagedTransactionManager /home/peter/projects/drools-jbpm-project/5.4.0.Final/jbpm-5.4.0.Final/jbpm-persistence-jpa/src/main/java/org/jbpm/persistence/jta/ContainerManagedTransactionManager.java:[53,31] error: cannot find symbol [INFO] 3 errors Does anyone know why this might occur and point me in the right direction to fixing it. I have tried building from both zip and tar archives on linux with identical results. Maven is 3.0.4 on both boxes. This is of particular interest as we have a problem running flows on our linux as7 server because of jta transaction issues, specifically, an exception when trying to join a transaction. While the two problems may be totally unrelated, it is possible that they are in that both are jta and linux issues. Any help much appreciated. Thanks, Peter -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776437#776437] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] modified the document: "Design of AS7 multi-JSF feature" To view the document, visit: https://community.jboss.org/docs/DOC-47689 -------------------------------------------------------------- *About multi-JSF* Currently, AS7 ships with two JSF implementations, a JSF 2.1 implementation and a JSF 1.2 implementation. A web application can select which implementation is used by including a context param in web.xml. By default, it uses the JSF 2.1 imlementation. "multi-JSF" allows installation of multiple JSF implementations (and versions) on the same AS7 server. The goal is to allow use of any JSF implementation (MyFaces or Mojarra) and any version of those implementation from JSF 1.1 all the way up to the experimental JSF 2.2 versions. This is far superior to the old WAR_BUNDLES_JSF_IMPL method because JSF jars do not need to be bundled with the webapp. More importantly, "multi-JSF" provides an implementation that is fully integrated with the container. This means more efficient annotation processing, lifecycle handling, and other integration advantages. *How it works* The way multi-JSF will work is that for each JSF version, a new slot is created in the modules path under *com.sun.jsf-impl*, *javax.faces.api*, and *org.jboss.as.jsf-injection*. When the jsf-subsystem is started, it scans the module path to find all the installed JSF implementations. When the JSF subsystem deploys a web app containing the specified context param, it adds the slotted modules to the deployment. Here is an example of the context param for the latest milestone of Mojarra 2.2: <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>mojarra-2.2.0-m05</param-value> </context-param> *How a JSF implementation is installed* A single JSF implementation is installed using a https://community.jboss.org/docs/DOC-18945 CLI deployment archive. This archive includes the required jars and module.xml files. It also includes CLI scripts for installing/uninstalling the JSF impls using the https://issues.jboss.org/browse/AS7-4265 CLI module command. You execute the installation archive like this: > [standalone@localhost:9999 /] deploy <local path to archive>/install-mojarra-2.2.0-m05.cli The install script inside the archive looks like this: > module add --name=javax.faces.api --slot=mojarra-2.2.0-m05 --resources=jsf-api-2.2.0-m05.jar --module-xml=mojarra-api-module.xml > module add --name=com.sun.jsf-impl --slot=mojarra-2.2.0-m05 --resources=jsf-impl-2.2.0-m05.jar --module-xml=mojarra-impl-module.xml > module add --name=org.jboss.as.jsf-injection --slot=mojarra-2.2.0-m05 --resources=jboss-as-jsf-injection-7.2.0.Alpha1-SNAPSHOT.jar --module-xml=injection-module.xml *How the CLI deployment archives are created* A CLI deployment archive for a JSF implementation/version is created using a standalone maven project you can https://github.com/ssilvert/jboss-jsf-installer download from GitHub and run. To create an archive with the project, you call it like this: > mvn -Djsf-version=2.2.0-m05 -Pmojarra clean assembly:single This pulls in the JSF resources and creates the install/uninstall scripts. It is all bundled together in an archive (zip) file that must be manually renamed with a .cli extension. *How to change the default JSF implementation in AS7* The multi-JSF feature adds two new attributes to the JSF subsystem. The first, +active-jsf-impls+, is just a read-only list of the installed JSF implementations. The second, +default-jsf-impl-slot+, allows you to change the default JSF implementation. You just need to issue a write-attribute command and set the value to one of the active impls. Then restart AS7. https://community.jboss.org/servlet/JiveServlet/showImage/102-47689-3-198... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47689-3... Alternatively, you can set this in your configuration file, such as standalone.xml: <subsystem xmlns="urn:jboss:domain:jsf:1.0" default-jsf-impl-slot="mojarra-2.2.0-m05"/> *Demo* I've attached a copy of install-mojarra-2.2.0-m05.cli and install-myfaces-2.1.8.cli. You can unzip to take a look at it. You can even deploy it with the latest nightly build of AS7. This will let you see how the modules are installed. I'm not quite done with updates to the jsf-subsystem, so you can't see multi-jsf in action on a webapp yet. If you want to try it out though, let me know. I can upload a working version to my github account. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47689] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by Brian Stansberry

Brian Stansberry [https://community.jboss.org/people/brian.stansberry] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11120 -------------------------------------------------- Jeff, This will need to be more complex. For a CP, we don't want to ignore AS modules just because the only change is creation dates. If you apply a CP patch, the modules you should run should be the same as if you had downloaded a fresh install of that version. I discussed this with Jimmy Wilson of GSS a while back. A critical question is whether a build of a product involves a complete rebuild from source of all 3rd party libs, or whether an existing built-from-source binary is re-used if the source is unchanged. I expect the latter; otherwise a new maven GAV would be needed for every build. And if that is case, again, for a CP there is no reason not to include a 3rd party module even if the diff is only creation dates. For whatever reason the module was rebuilt. For one-off patches, the patch generator includes the ability for the patch-config to explicitly declare what modules are different. I did this as something of a workaround to the problem you're attacking. The person preparing the one-off will probably do a complete big from source of a tag + bug-fix patch, and generating a diff of that will produce spurious diffs. Your approach here provides another way to help with this case. But it shouldn't be done for CPs and for one-offs the patch-config should include a config to turn it off. Re: the .index files, I had some discussions about those and I thought they were no longer being generated. If that's wrong, then yes, we'll need to deal with them. I'm not in favor of analyzing the module.xml to determine what resources to hash. For two reasons: 1) The user-side patch tool shouldn't add any functionality that isn't really necessary. The more it does, the more ways it can break. And breaking is bad. 2) It's not the business of the patch tool to parse and understand the contents of module.xml. If jboss-modules changes something, we don't want to have to update the patch tool to understand that. I don't think it's a big deal if users stick a README in a module and we treat that as a conflict. The users looks, sees the difference (the README would likely have a different filesystem date from the rest of the module) and provides the param to the patching operation indicating that it's ok to override modules with conflicts. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[jBPM Development] - jBPM Capability

by stevie_ray

stevie_ray [https://community.jboss.org/people/stevie_ray] created the discussion "jBPM Capability" To view the discussion, visit: https://community.jboss.org/message/776115#776115 -------------------------------------------------------------- I am currently evaluting the jBPM offering from JBoss and have a few questions. When I look at the BPMS editor under the JBoss tools plugin in Eclipse I see only 2 service tasks included with the tool (Log, Email) and 13 components. Do I have the complete set? Does the paid for version offer more functionality? If I need to build a work flow that requires connecting to an external REST webserice, do I need to build my own Service Task to do that? And, one last question, If I am trying to inject data into a workflow from session.startSession() and then access the same data in WorkItemHandler downstream in the flow. At a high level, how would I do that? Thanks! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776115#776115] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Single Installation Patching

by Jeff Mesnil

Jeff Mesnil [https://community.jboss.org/people/jmesnil] commented on the document "Single Installation Patching" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47500#comment-11114 -------------------------------------------------- I have been working on the patch CLI command to patch an AS7 installation and add to tweak the code related to module to be able to generate a correct patch generated by diffing 2 AS7 installations. When comparing modules to check whether they have been updated, computing the dir's checksum is not correct: * Jar files generated during AS7 build can not have the same checksum since the creation date of the class files is store in the jar's zip entries. => this concerns AS7's own modules (org/jboss/as/...) and also jandex jars for 3rd party libraries To circumvent that, instead of computing the SHA-1 of the jar files, I compute the checksum of the file's zip entries name/size/crc (ie I exclude the date metadata). I also need to exclude some entries from the jar: * Some java sources are generated at build time (logger and bundle classes) and embed their generation date into the code => the .class files have different size and crc * META-INF/MANIFEST.MF and pom.properties files also contains the jar creation date => these files have different size and crc When a module dir is compared, .index files (generated at runtime) should not be taken into account (they are not present in the pristine AS7 installations I used to generate the patch by diff) I have a branch for this[1] which uses the same hash algo (based on the zip entries metadata) for all jars. This could likely be reduced only to jars in org/jboss/as and -jandex.jar. With these changes, the patch code is able to compute a "suitable" checksum for module. I also think the module's resource checksum should be based on the content of the module.xml. Only resources listed in the <resources> element should be included in the checksum. Eg adding a README to a module should not change its checksum. This means a 2-step check: 1. check that the module.xml are identical (with a file checksum) 2. check that the resources listed by the module are "equivalent" (with jar-specific checksum for jar + file checksum for other resources) What do you think? [1] https://github.com/jmesnil/jboss-as/compare/emuckenhuber:patches-master..... https://github.com/jmesnil/jboss-as/compare/emuckenhuber:patches-master..... --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss ESB Development] - how can I get started with jboss esb project

by lijun yueqiu

lijun yueqiu [https://community.jboss.org/people/yueqiulijun] created the discussion "how can I get started with jboss esb project" To view the discussion, visit: https://community.jboss.org/message/776012#776012 -------------------------------------------------------------- I do not know how to start with jbos esb project. https://community.jboss.org/servlet/JiveServlet/showImage/2-776012-19869/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-776012-19... I do not know how to write this file ,and why should we write like this. which book should I look ? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/776012#776012] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. *Core Concepts* * * When defining an RBAC model, the following conventions are useful: * Subject = A person or automated agent * Role = Job function or title which defines an authority level * Permissions = An approval of a mode of access to a resource * Action = An operation to execute on a resource * Constraint: Predicate that makes the permission valid in the context of the system state * Session = A mapping involving Subject, Role and/or Permissions https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-28-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-2... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Enable customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* * +Support permission enforcement that restricts visibility of model elements: +Control visibility of resources (i.e. restrict visibility of server groups) * +Suppor permission enforcement that restricts execution on model elements+: Control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) * +The management layer needs to enforce permission regardless of the client type and availability: +I.e. enformenent can not be delegated to the client only+ + * +Clients (CLI, Web) should indicate permissions prior to execution of management operations:+ I.e. grey out interface elements to emphasis lack of permissions *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - RBAC Usecases

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "RBAC Usecases" To view the document, visit: https://community.jboss.org/docs/DOC-47856 -------------------------------------------------------------- || *Name* || *Description* || *<Reject/Accept>* || | *Restricting access to server groups* | +Configuration+: Server groups: "production", "staging". roles: "admin", "developer" +Goal+: Restrict access to the production group to the "admin" role in to prevent messing with the production system +Implications+: Server groups are part of the model but also a logical concept. I.e. restricting access to a group does imply preventing access to conceptually related entities like servers, deployments, etc. | | | *Support clients & tools that provide their own security model* | +Configuration+: See JON User Guide (https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3...) +Goal+: Allow interaction with systems that provide their own authorization scheme +Implications+: Systems like JON, that provide their own scheme currently can only operate the super user level | | | *Restrict visibility of attributes* | Suppress attributes on responses, i.e. read-resource | arguable | | *Restrict visibility of operations* | Suppress operations on reponses, i.e. read-operation-names | arguable | | *Prevent execution of operations* | Execution of operations with permissions yields a security exception | | ** ** -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47856] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Re: Quartz Scheduler in Jboss AS 7

by Ifta Khirul

Ifta Khirul [https://community.jboss.org/people/ifti24] created the discussion "Re: Quartz Scheduler in Jboss AS 7" To view the discussion, visit: https://community.jboss.org/message/775949#775949 -------------------------------------------------------------- Another way is to make it workable to place the the jar files (quartz-all-2.1.6.jar,slf4j-api-1.6.1.jar) in the lib folder of EarContent. Then no need to place the dependencies in the MENIFEST.MF file. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775949#775949] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Re: Quartz Scheduler in Jboss AS 7

by Wolf-Dieter Fink

Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion "Re: Quartz Scheduler in Jboss AS 7" To view the discussion, visit: https://community.jboss.org/message/775802#775802 -------------------------------------------------------------- As you are using EJB3.1 I would prefere a simple EJB Stateless or Singleton and add a http://docs.oracle.com/javaee/6/api/javax/ejb/Schedule.html @Schedule annotation. This will do the work compatilbe. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775802#775802] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

3
3
0 / 0

[PicketBox Development] - Re: JASPI ServerAuthModule

by Ranjan Khanna

Ranjan Khanna [https://community.jboss.org/people/ranjan.khanna] created the discussion "Re: JASPI ServerAuthModule" To view the discussion, visit: https://community.jboss.org/message/766769#766769 -------------------------------------------------------------- Were you able to make it work for JBOSS. If Yes, could you please share some details. Thanks. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/766769#766769] Start a new discussion in PicketBox Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
1
0 / 0

[JBoss ESB Development] - I have not the JBoss ESB link in the directory tree at WEB

by Alexy Boykov

Alexy Boykov [https://community.jboss.org/people/alexbuilder] created the discussion "I have not the JBoss ESB link in the directory tree at WEB" To view the discussion, visit: https://community.jboss.org/message/775876#775876 -------------------------------------------------------------- *+Hi, I am just starting with+ +JBoss+ +ESB 4.10. My deployment was successful, I am successfully logged in jboss-5.1 as admin, but I have not the JBoss ESB link in the directory tree at WEB as it represents in JBoss.ESB.Beginners.Guide.pdf. Why?+* -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775876#775876] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [PicketBox Development] - JBoss AS7: Enabling JASPI Authentication for Web Applications

by arjan tijms

arjan tijms [https://community.jboss.org/people/atijms] commented on the document "JBoss AS7: Enabling JASPI Authentication for Web Applications" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-17782#comment-11105 -------------------------------------------------- Maybe of interest to the readers of this thread; I wrote an article of my experiences with installing a JASPIC SAM programmatically at: http://arjan-tijms.blogspot.nl/2012/11/implementing-container-authenticat... http://arjan-tijms.blogspot.nl/2012/11/implementing-container-authenticat... Related to this is the following Java EE spec issue: http://java.net/jira/browse/JAVAEE_SPEC-9 http://java.net/jira/browse/JAVAEE_SPEC-9 My personal stake here is that for the OmniFaces project ( http://code.google.com/p/omnifaces http://code.google.com/p/omnifaces) we were looking into creating a simplified authentication process that also better integrates with JSF. JASPIC seemed very viable to base this on, if it weren't for the issues with configuration, and among others the fact it's not active by default in JBoss AS/EAP (our showcase app runs on JBoss AS and EAP on OpenShift, so JBoss is obviously a very important target container for us). --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[jBPM Development] - Examples for using rules-decision activities

by Dominik Klein

Dominik Klein [https://community.jboss.org/people/dekay] created the discussion "Examples for using rules-decision activities" To view the discussion, visit: https://community.jboss.org/message/775861#775861 -------------------------------------------------------------- Hello, i am new to jbpm and drools and i am looking for some simple examples or tutorials for using rules-decision activities in jpbm. I want to build a process wich contains some business rules and i want to seperate the rules in an .drl file and use them for decisions in the process. I found http://docs.jboss.com/jbpm/v4/devguide/html_single/#rulesdecision this example in the jpbm documentation but it doesn´t work and i don´t know why. I copied the drl file and the process xml definition to a new jbpm project. The first error is that the class org.jbpm.jpdl.internal.rules.Outcome is missed. I added the jar for org.jbpm.jpdl but it doesn´t contain the missed class. The second error is a null pointer exception in the in the process xml description an i don´t know where. Does anybody know some other simple examples for using rules-decision activities in jbpm? Thanks a lot! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775861#775861] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Quartz Scheduler in Jboss AS 7

by Ifta Khirul

Ifta Khirul [https://community.jboss.org/people/ifti24] created the discussion "Quartz Scheduler in Jboss AS 7" To view the discussion, visit: https://community.jboss.org/message/775697#775697 -------------------------------------------------------------- Hi, I'm trying to implement quartz scheduler in on of my EJB application with Jboss AS 7. I have included quartz-jboss-2.1.6.jar and quartz-all-2.1.6 jar in my EJB application. I have implemented my SchedulerBean in the following way - {code} @Startup @Singleton public class SchedulerBean { @PostConstruct void init() { try { Scheduler sched = new StdSchedulerFactory().getScheduler(); // schedule jobs here JobDetail testjob = JobBuilder.newJob(TestJob.class).withIdentity("testjob", "testgroup").build(); SimpleTrigger trigger = TriggerBuilder.newTrigger() .withIdentity("testtrigger", "testgroup") .withSchedule(SimpleScheduleBuilder.simpleSchedule() .withIntervalInSeconds(10) .repeatForever()) .build(); sched.scheduleJob(testjob, trigger); sched.start(); } catch (Throwable t) { // log exception } } } {code} And below is the TestJob Class {code} public class TestJob implements Job { @Override public void execute(JobExecutionContext context) throws JobExecutionException { System.out.println("Quartz test job executed!"); } } {code} Everything is ok in the compile time. But when I start my application (Then Enterprise application) I got the following Error - ---------------- Caused by: java.lang.NoClassDefFoundError: org/quartz/ScheduleBuilder at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.7.0_09] at java.lang.Class.privateGetDeclaredFields(Class.java:2308) [rt.jar:1.7.0_09] at java.lang.Class.getDeclaredFields(Class.java:1760) [rt.jar:1.7.0_09] at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 10 more Caused by: java.lang.ClassNotFoundException: org.quartz.ScheduleBuilder from [Module "deployment.TestEnterpriseProject.ear.TestEjbProject.jar:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 15 more ----------------- Can anybody help me to findout a way to solve this issue please ? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775697#775697] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - JBOSS EAP 6.0 Deployment of war failure

by Amit Telang

Amit Telang [https://community.jboss.org/people/amittelang1976] created the discussion "JBOSS EAP 6.0 Deployment of war failure" To view the discussion, visit: https://community.jboss.org/message/773725#773725 -------------------------------------------------------------- Hi, My application war works fine in Weblogic and Tomcat but same war I am uanble to deploy in Jboss EAP 6.0. My application server is going to migrate on Jboss EAP. Please help me why its failing. 14:18:46,145 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "fiveseries.war" 14:18:53,665 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry xml-apis.jar in /C:/Program Files/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/fiveseries.war/WEB-INF/lib/ant-1.5.jar does not point to a valid jar for a Class-Path reference. 14:18:53,665 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry xercesImpl.jar in /C:/Program Files/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/fiveseries.war/WEB-INF/lib/ant-1.5.jar does not point to a valid jar for a Class-Path reference. 14:18:53,665 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry optional.jar in /C:/Program Files/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/fiveseries.war/WEB-INF/lib/ant-1.5.jar does not point to a valid jar for a Class-Path reference. 14:18:53,665 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry xalan.jar in /C:/Program Files/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/fiveseries.war/WEB-INF/lib/ant-1.5.jar does not point to a valid jar for a Class-Path reference. 14:18:53,675 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /C:/Program Files/jboss-eap-6.0.0/jboss-eap-6.0/standalone/deployments/fiveseries.war/WEB-INF/lib/mail-1.4.jar does not point to a valid jar for a Class-Path reference. dependencies>]","jboss.deployment.unit.\"fiveseries.war\".component.\"org.apache.strutsel.taglib.tiles.ELPutListTag\".START Missing[JBAS014861: <one or more transitive dependencies>]"]} 14:19:02,058 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011908: Unregister module: Module "deployment.fiveseries.war:main" from Service Module Loader 14:19:05,228 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment fiveseries.war in 3303ms 14:19:05,228 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => Thanks, Amit -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773725#773725] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

4
6
0 / 0

Community Updates, November 1 - November 8

by JBoss Community

=============================================================== Community Updates for November 1 - November 8 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,193 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,475 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Sessions and transactions [https://community.jboss.org/docs/DOC-13951] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * Statement Regarding Security Threat to JBoss Application Server [https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-secu...] * JBoss Tools 3.3 and Developer Studio 5.0 Final Release! [https://community.jboss.org/community/tools/blog/2012/06/21/jboss-tools-3...] * Re: Jboss 7.1.2.Final is only for EAP? [https://community.jboss.org/message/763860#763860] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/746287#746287] * Re: How to deploy war file into Jboss 5.0 [https://community.jboss.org/message/727979#727979] Tips and tricks - Get Notified You can have Community send you email when content you care about is added or changed. This is an alternative to feeds, which require a feed aggregator (although you can use both feeds and email notifications). Because an email is sent for each notification you request, you might prefer subscribing to feeds if you'd rather not get all the email. To begin receiving email notifications, navigate to the area you care about — a space or document or blog, for example — and click Receive Email Notifications underActions. To stop receiving email notifications, click Stop Email Notifications instead. You can manage all of your email notifications by going to the Email Notifications tab in your profile. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] commented on the document "ManagementLayer RBAC" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47854#comment-11096 -------------------------------------------------- I've update the model to reflect composite actions --------------------------------------------------

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. *Core Concepts* * * When defining an RBAC model, the following conventions are useful: * Subject = A person or automated agent * Role = Job function or title which defines an authority level * Permissions = An approval of a mode of access to a resource * Action = An operation to execute on a resource * Constraint: Predicate that makes the permission valid in the context of the system state * Session = A mapping involving Subject, Role and/or Permissions https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-23-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-2... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Enable customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permissions+: * structural: control visibility of resources (i.e. restrict visibility of server groups) * behavioural: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - RBAC Usecases

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "RBAC Usecases" To view the document, visit: https://community.jboss.org/docs/DOC-47856 -------------------------------------------------------------- || *Name* || *Description* || *<Reject/Accept>* || | *Restricting access to server groups* | +Configuration+: Server groups: "production", "staging". roles: "admin", "developer" +Goal+: Restrict access to the production group to the "admin" role in to prevent messing with the production system +Implications+: Server groups are part of the model but also a logical concept. I.e. restricting access to a group does imply preventing access to conceptually related entities like servers, deployments, etc. | | | *Support clients & tools that provide their own security model* | +Configuration+: See JON User Guide (https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3...) +Goal+: Allow interaction with systems that provide their own authorization scheme +Implications+: Systems like JON, that provide their own scheme currently can only operate the super user level | | | *Restrict visibility of attributes* | | | | *Restrict visibiility of operations* | | | | *Prevent execution of operations* | | | ** ** -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47856] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Connection Re-Authentication and Security Propagation

by Darran Lofthouse

Darran Lofthouse [https://community.jboss.org/people/dlofthouse] created the document: "Connection Re-Authentication and Security Propagation" To view the document, visit: https://community.jboss.org/docs/DOC-47864 -------------------------------------------------------------- h2. Introduction The purpose of this article is to outline the problems that we are attempting to solve and the solution currently being considered. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47864] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - connecting a remote hornetQ server

by Hans Steiner

Hans Steiner [https://community.jboss.org/people/hans-juergen.stemmer.vkb.de] created the discussion "connecting a remote hornetQ server" To view the discussion, visit: https://community.jboss.org/message/729620#729620 -------------------------------------------------------------- Hi out there I am trying to connect a jboss as 7.1.0 with another jboss that should only act as a hornetQ server (2.2.11). I see that in the ejb subsystem <mdb> <resource-adapter-ref resource-adapter-name="*hornetq-ra"*/> <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/> </mdb> is configured. In the message subsystem I use a connector <connectors> <connector name="*netty*"> <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class> <param key="host" value="xxxxx"/> <param key="port" value="5745"/> </connector> </connectors> that is referenced from the connection pool <pooled-connection-factory name="*hornetq-ra*"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="*netty*"/> </connectors> <entries> <entry name="java:/JmsXA"/> </entries> </pooled-connection-factory> All this works fine, except of an error/warning I receive a few seconds after I have started the server. > 15:54:20,640 WARN [org.hornetq.jms.server.recovery.HornetQXAResourceWrapper] Can't connect to any hornetq server on recovery [XARecoveryConfig [hornetQConnectionFactory=HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5745&host=xxxxx], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false], *username=null, password=null*]] > 15:54:20,656 WARN [com.arjuna.ats.jta] ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery > at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:275) [hornetq-jms-2.2.11.Final.jar:] > at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.recover(HornetQXAResourceWrapper.java:77) [hornetq-jms-2.2.11.Final.jar:] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:503) [jbossjts-4.16.2.Final.jar:] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:471) [jbossjts-4.16.2.Final.jar:] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:385) [jbossjts-4.16.2.Final.jar:] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:166) [jbossjts-4.16.2.Final.jar:] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-4.16.2.Final.jar:] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-4.16.2.Final.jar:] > Caused by: HornetQException[errorCode=2 message=null] > at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connect(HornetQXAResourceWrapper.java:351) [hornetq-jms-2.2.11.Final.jar:] > at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:251) [hornetq-jms-2.2.11.Final.jar:] > ... 7 more > > 15:54:20,703 WARN [org.hornetq.jms.server.recovery.HornetQXAResourceWrapper] Can't connect to any hornetq server on recovery [XARecoveryConfig [hornetQConnectionFactory=HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5745&host=xxxxx], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false], username=null, password=null]] The queue is found and I can send and receive messages. I use annotations like this @MessageDriven(name="MyMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "global/myQueue"), @ActivationConfigProperty(propertyName = "user", propertyValue = "guest"), @ActivationConfigProperty(propertyName = "password", propertyValue = "guest")... for the mdb. Can anybody help me with the XA warning? I suppose all I have to do is to configure username and passwort in the right manner. I read something about ra.xml and the resource-adapters subsystem, but I could not find out how to set any properties. Perhaps there is even a better way to combine a remote hornetQ server with the use of annotations. I am not happy having the messaging subsystem (not present in a standalone.xml without hornetq) in my configuration. Can I delete some portions just leaving the client-part of the jms configuration? Thx very much for help. hans -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/729620#729620] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

5
6
0 / 0

[JBoss AS 7 Development] - JBoss AS 7 is still trying to locate login-config.xml

by valentino cruz

valentino cruz [https://community.jboss.org/people/fabiovc27] created the discussion "JBoss AS 7 is still trying to locate login-config.xml" To view the discussion, visit: https://community.jboss.org/message/775472#775472 -------------------------------------------------------------- I have migrated our application from JBoss 4.0.5 to JBoss AS 7 and the only thing left to be completely done is to allow JBoss 7 to authenticate users via Kerberos SSO as we used to in JBoss 4.0.5. The documentation says that now I can simply use the standalone.xml and put the contents of my previous login-config.xml file in there and specify the type of authentication and necessary properties such as the SPN. However, when I try to login I see this exception on my logs: +18:17:39,628 WARN [org.jboss.security.auth.login.XMLLoginConfigImpl] (http-executor-threads - 10) *End loadConfig, failed to load config: file:/login-config.xml: java.io.FileNotFoundException: /login-config.xml (No such file or directory)*+ + at java.io.FileInputStream.open(Native Method) [classes.jar:1.6.0_22]+ + at java.io.FileInputStream.<init>(FileInputStream.java:106) [classes.jar:1.6.0_22]+ + at java.io.FileInputStream.<init>(FileInputStream.java:66) [classes.jar:1.6.0_22]+ + at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) [classes.jar:1.6.0_22]+ + at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) [classes.jar:1.6.0_22]+ + at java.net.URL.openStream(URL.java:1010) [classes.jar:1.6.0_22]+ + at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:440) [picketbox-4.0.7.Final.jar:4.0.7.Final]+ + at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:408) [picketbox-4.0.7.Final.jar:4.0.7.Final]+ + at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:379) [picketbox-4.0.7.Final.jar:4.0.7.Final]+ + at org.jboss.security.auth.login.XMLLoginConfigImpl.refresh(XMLLoginConfigImpl.java:118) [picketbox-4.0.7.Final.jar:4.0.7.Final]+ This tells me that somehow JB7 is not aware that I'm trying to configure this information in the standalone.xml file and not in the login-config.xml. I'm not even packaging that file anymore since the documentation says it is no longer used. Has anyone gotten SSO to work by using their previous login-config.xml contents into the standalone.xml or domain.xml files Any help woill be greatly appreciated, it seems this portion of the documetation is still lacking quite a bit. Thank you -Valentino -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775472#775472] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
1
0 / 0

[jBPM Development] - Call statefulKnowledgeSession.startProcess() from an SessionBean

by stundzig

stundzig [https://community.jboss.org/people/stundzig] created the discussion "Call statefulKnowledgeSession.startProcess() from an SessionBean" To view the discussion, visit: https://community.jboss.org/message/775461#775461 -------------------------------------------------------------- Hi folks, i would like to call startProcess() and completeWorkItem() on a StatefulKnowledgeSession. Therefore I've an SessionBean and and j2ee-client application. I call the startProcess from my client and delegates them to the SessionBean. The SessionBean itself does some logic and after that, they should call startProcess() or something else on the current running JBPM application. But how could I get a reference to the JPAKnowledgeService or StateKnowledgeService or something else? Or a SessionBean which I could get from JNDI? I've tried some different approaches in the last hours, for example inject persistence unit and build an own Session around it, but without any success. Could someone point me to the right documentation please or post a code snippet? I'm using BRMS 5.3.0. Thanks in advance. Regards Steffen... -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775461#775461] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. *Core Concepts* * * When defining an RBAC model, the following conventions are useful: * Subject = A person or automated agent * Role = Job function or title which defines an authority level * Permissions = An approval of a mode of access to a resource * Action = An operation to execute on a resource * Constraint: Predicate that makes the permission valid in the context of the system state * Session = A mapping involving Subject, Role and/or Permissions https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-21-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-2... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S= Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource * SE = Session = A mapping involving S, R and/or P https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-18-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-1... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S= Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource * SE = Session = A mapping involving S, R and/or P https://community.jboss.org/servlet/JiveServlet/showImage/102-47854-16-19... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-47854-1... *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[jBPM Development] - How to handle concurrent users in JBPM at same level

by motteRobo motte

motteRobo motte [https://community.jboss.org/people/motterobo] created the discussion "How to handle concurrent users in JBPM at same level" To view the discussion, visit: https://community.jboss.org/message/775325#775325 -------------------------------------------------------------- Hi, I am facing *‘couldn't signal token : token has ended’ exception* When the users at the same level approving the same record at the same time. I am looking for a solution where JBPM should now allow users at the same level to access same record. Thanks for your suppport in advance. Regards, MotteRobo -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775325#775325] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - RBAC Usecases

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "RBAC Usecases" To view the document, visit: https://community.jboss.org/docs/DOC-47856 -------------------------------------------------------------- Some use cases to proof the concepts put into place. *Restricting access to server groups* +Configuration+: Server groups: "production", "staging". roles: "admin", "developer" +Goal+: Restrict access to the production group to the "admin" role in to prevent messing with the production system +Implications+: Server groups are part of the model but also a logical concept. I.e. restricting access to a group does imply preventing access to conceptually related entities like servers, deployments, etc. *Support clients & tools that provide their own security model* +Configuration+: See https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3... JON User Guide +Goal+: Allow interaction with systems that provide their own authorization scheme +Implications+: Systems like JON, that provide their own scheme currently can only operate the super user level -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47856] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S= Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource * SE = Session = A mapping involving S, R and/or P *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) * Mappability with existing authorisation schemes (i.e. JON) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S= Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource * SE = Session = A mapping involving S, R and/or P *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) * Clearly distinguish security exceptions from other operation errors (i.e. custom response headers) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Use cases* See https://community.jboss.org/docs/DOC-47856 RBACUsecases* * *Advanced Topics* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - RBAC Usecases

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] created the document: "RBAC Usecases" To view the document, visit: https://community.jboss.org/docs/DOC-47856 -------------------------------------------------------------- Some use cases to proof the concepts put into place. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47856] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[IronJacamar Development] - Re: Management of IronJacamar

by Nabeel Ahmed

Nabeel Ahmed [https://community.jboss.org/people/mr.bee] created the discussion "Re: Management of IronJacamar" To view the discussion, visit: https://community.jboss.org/message/775294#775294 -------------------------------------------------------------- Hi Jesper, I was looking a way to get the list of deployed resource adapters and it's requried config properties but unable to do so. Server is Jboss 7.1.1.Final Can you provide me some sample or help, that how can i acheive this ? thanks, Nabeel Ahmed -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775294#775294] Start a new discussion in IronJacamar Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S= Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource * SE = Session = A mapping involving S, R and/or P *Generic Requirements* * Provide a usable (in terms of complexity), yet comprehensive base model * Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements * Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) * Provide the management operations to retrieve session information (i.e. roles assigned, permissions granted, etc) *Specific Requirements* +Provide an authorization scheme that distinguishes structural & behavioural permission+: * structural permissions: control access to resources (i.e. restrict visibility of server groups) * behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Advanced Use Cases / Considerations* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S = Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource *Generic Requirements* - Provide a usable (in terms of complexity), yet comprehensive base model - Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements - Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) *Specific Requirements* - Provide an authorization scheme that distinguishes structural & behavioural permission: > structural permissions: control access to resources (i.e. restrict visibility of server groups) > behavioural permission: control execution on resources (i.e. lock down certain operations, distinguish read & read/write access) *Advanced Use Cases / Considerations* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S = Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource *Generic Requirements* - Provide a usable (in terms of complexity), yet comprehensive base model - Provide a set of out-of-the-box roles & permissons that reflect common authorization requirements - Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) *Specific Requirements* - [...]* * *Advanced Use Cases / Considerations* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S = Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource *Generic Requirements* - Provide a usable (in terms of complexity), yet comprehensive base model - Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) *Specific Requirements* - [...]* * *Advanced Use Cases / Considerations* - Context based access control: i.e. Taking the connection into consideratin - Support for role hierarchies: i.e. structuring roles to reflect an organizations lines of authority and responsibility - Role constraints: i.e. mutual exclusive roles - RBAC to manage RBAC itself structuring roles to re ect an organiza tion s lines of authority and resp onsibility -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] modified the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. When defining an RBAC model, the following conventions are useful: * S = Subject = A person or automated agent * R = Role = Job function or title which defines an authority level * P = Permissions = An approval of a mode of access to a resource *Generic Requirements* - Provide a usable (in terms of complexity), yet comprehensive base model - Allow to customizations/extension of the default scheme (i.e custom permissions, permission granularity) *Specific Requirements* - [...]* * *Advanced Use Cases / Considerations* - Context access control: i.e. Taking the connection into consideratin - Support for role hierarchies -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - ManagementLayer RBAC

by Heiko Braun

Heiko Braun [https://community.jboss.org/people/heiko.braun] created the document: "ManagementLayer RBAC" To view the document, visit: https://community.jboss.org/docs/DOC-47854 -------------------------------------------------------------- Role based access control to the AS7 management layer. -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-47854] Create a new document in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

13 years, 2 months

1
0
0 / 0

[JBoss Web Development] - Failed authenticate() test in Web Application with Custom LoginModule

by Simon Martinelli

Simon Martinelli [https://community.jboss.org/people/simas_ch] created the discussion "Failed authenticate() test in Web Application with Custom LoginModule" To view the discussion, visit: https://community.jboss.org/message/775252#775252 -------------------------------------------------------------- Hi, I have a Custom LoginModule that works fine with authentication in EJBs with Remote Communication in JBoss 6. But it doesn't work when I use it in a web application. I can see the following in the logfile: 08:54:18,206 DEBUG [org.apache.catalina.authenticator.AuthenticatorBase] @ Security checking request POST /proshop/admin/j_security_check 08:54:18,206 DEBUG [org.apache.catalina.authenticator.FormAuthenticator] @ Authenticating username 'mabe' 08:54:18,222 DEBUG [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/proshop].[FacesServlet]] @ Disabling the response for futher output 08:54:18,222 DEBUG [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/proshop].[FacesServlet]] @ The Response is vehiculed using a wrapper: org.apache.catalina.connector.Response 08:54:18,222 DEBUG [org.apache.catalina.authenticator.AuthenticatorBase] @ Failed authenticate() test ??/proshop/admin/j_security_check 08:54:18,242 DEBUG [org.apache.catalina.authenticator.AuthenticatorBase] @ Security checking request GET /proshop/javax.faces.resource/theme.css.jsf 08:54:18,242 DEBUG [org.apache.catalina.realm.RealmBase] @ Checking constraint 'SecurityConstraint[proshop]' against GET /javax.faces.resource/theme.css.jsf --> false 08:54:18,242 DEBUG [org.apache.catalina.realm.RealmBase] @ Checking constraint 'SecurityConstraint[proshop]' against GET /javax.faces.resource/theme.css.jsf --> false 08:54:18,242 DEBUG [org.apache.catalina.realm.RealmBase] @ Checking constraint 'SecurityConstraint[proshop]' against GET /javax.faces.resource/theme.css.jsf --> false 08:54:18,242 DEBUG [org.apache.catalina.realm.RealmBase] @ Checking constraint 'SecurityConstraint[proshop]' against GET /javax.faces.resource/theme.css.jsf --> false 08:54:18,242 DEBUG [org.apache.catalina.realm.RealmBase] @ No applicable constraint located 08:54:18,242 DEBUG [org.apache.catalina.authenticator.AuthenticatorBase] @ Not subject to any constraint Whe I use the jmx-console Loginmodule it works. So it must be a problem with the custom LoginModule. Ist there a way to have more trace output from the security mechanism in JBoss? Thanks Simon -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/775252#775252] Start a new discussion in JBoss Web Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[EJB3 Development] - javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:

by nandi g

nandi g [https://community.jboss.org/people/ghosh_nandita] created the discussion "javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:" To view the discussion, visit: https://community.jboss.org/message/774975#774975 -------------------------------------------------------------- Hi I am a new bie in EJB3.x .I am writing JUNIT test cases for ejb which is deployed in JBOSS7.1 FINAL using remote client. I have used all the maven dependency https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+... https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+... I have jboss-ejb-client.properties in my class path. But i get the following error when i try to run the test cases. ---------------- +*javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:*+ java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.lookup(InitialContext.java:392 ------------------ Attached is the jboss-ejb-clent.properties Please help in solving this error Thanks in advance -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774975#774975] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - how I can disable all the security of JBoss7?

by Jonatan Guillen

Jonatan Guillen [https://community.jboss.org/people/jonatan.guillen] created the discussion "how I can disable all the security of JBoss7?" To view the discussion, visit: https://community.jboss.org/message/774972#774972 -------------------------------------------------------------- I keep having problems with security in Jboss 7. As I can disable it for all kinds of connections? - remote connections - local connections - jboss to jboss connections. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774972#774972] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Test failures with JDK7

by Frank Langelage

Frank Langelage [https://community.jboss.org/people/lafr] created the discussion "Test failures with JDK7" To view the discussion, visit: https://community.jboss.org/message/774564#774564 -------------------------------------------------------------- I tried to compile the current JBoss AS7 sources from github.com with Oracle JDK 1.7.0_09 on Solaris 10 SPARC. But tests failed: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.286 sec Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest Tests run: 22, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 2.028 sec <<< FAILURE! Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec Results : Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 11206542> was not:<null> getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 12646526> was not:<null> Tests in error: removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) Is this expected, meaning JDK 1.6 is mandatory for compilation? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774564#774564] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

3
6
0 / 0

[JBoss AS 7 Development] - Inter-module injection - the easy way (or even any way or alternative approaches)?

by tom-jb

tom-jb [https://community.jboss.org/people/tom-jb] created the discussion "Inter-module injection - the easy way (or even any way or alternative approaches)?" To view the discussion, visit: https://community.jboss.org/message/774712#774712 -------------------------------------------------------------- I am trying unsuccessfully to get Inter-module injection working. I expected that I could have a cdi-enabled war @Inject beans from a bean archive in the same container after haing added a dependency to the bean-archive-as-module in the war's jboss-deployment-structure.xml file My ultimate goal is to enable a rapid development process for our team where developers working on the front end redeploy just a lean war that does not contain any backend services but has a module dependency on a "services" deployable (which is currently an ear but could be just a jar if need be). Devs doing front-end work would ideally just @Inject any local dependency located in the services deployable with minimal/zero per-service configuration fuss. The services deployable is a fairly time-consuming redeploy, and a frequent redeploy seems unneeded for developers just doing front-end work. Normally, I might have liked to accomplish this goal by using an exploded ear, where the war is part of the ear, and the front end developer can just redeploy the war portion of the ear after making,say, a java file change, and only the war is redeployed, not the entire ear (which again is slow and seemingly unneeded). Other apps servers that I've worked with in the past offer this specific functionality, but it appears that AS7 does not (unless, hopefully, I'm wrong). On AS7 it seems only the entire ear can be redeployed, even if just the war needs redeployment. So, I am looking for alternative approaches to accomplish the same goal, such as using a front-end war external to the services deployable that uses inter-module injection (as described http://docs.jboss.org/cdi/spec/1.0/html/injectionelresolution.html here under 5.1.4 in the CDI spec). However when I try this, I get "unsatisfied dependencies" errors. I think I'm satisfying the requirements for inter-module injection (though the 4th part is unclear to me - "the bean class is required to be accessible to classes in the module, according to the class accessibility requirements of the module architecture"). I have confirmed that my war (which has a reference in jboss-deployment-structure.xml to the ear module and to the ejb-jar subdeployment inside the ear) can do a jndi lookup for an example EJB using "java:global/my-ear.ear/my-ejb.jar/SomeService", but @Inject can not find the same bean. I'm confident that a have cdi enabled on both the war and on the ear (plus I've tried just a simple bean archive jar instead of my full-blown ear). Any workarounds or alternative approaches would be most welcome. Thanks all, #Tom -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774712#774712] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
2
0 / 0

[JBoss Web Services Development] - Web service client user token authentication problem

by sreedhar y

sreedhar y [https://community.jboss.org/people/sreedhar_45] created the discussion "Web service client user token authentication problem" To view the discussion, visit: https://community.jboss.org/message/774844#774844 -------------------------------------------------------------- Hi, We have got a webservice with the following security policy from the client. <wsp:Policy orawsp:provides="{ http://docs.oasis-open.org/ns/opencsa/sca/200903 http://docs.oasis-open.org/ns/opencsa/sca/200903}authentication, { http://docs.oasis-open.org/ns/opencsa/sca/200903 http://docs.oasis-open.org/ns/opencsa/sca/200903}clientAuthentication, { http://docs.oasis-open.org/ns/opencsa/sca/200903 http://docs.oasis-open.org/ns/opencsa/sca/200903}clientAuthentication.mes..., { http://schemas.oracle.com/ws/2006/01/policy http://schemas.oracle.com/ws/2006/01/policy}token.usernamePassword" wsu:Id="wss_username_token_service_policy" xmlns:wsp=" http://schemas.xmlsoap.org/ws/2004/09/policy http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns=" http://schemas.xmlsoap.org/ws/2004/09/policy http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:orawsp=" http://schemas.oracle.com/ws/2006/01/policy http://schemas.oracle.com/ws/2006/01/policy" xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit... http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"> <sp:SupportingTokens xmlns:sp=" http://schemas.xmlsoap.org/ws/2005/07/securitypolicy http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"> <wsp:Policy> <sp:UsernameToken sp:IncludeToken=" http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysT... http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysT..."> <wsp:Policy> <sp:WssUsernameToken10/> </wsp:Policy> </sp:UsernameToken> </wsp:Policy> </sp:SupportingTokens> </wsp:Policy> We generated client classes using the Java JAX-WS tool from the wsdl(used the wsimport command).Afer that used the SecurityHandler class( attached the file) which incorporates the securtiy information in the handleMessage() method. When i called the web service method from a standlone client class ,security authentication is done and got the webservice response. But when accessing the webservice from the application deployed from JBoss7.1.0,Security Handler's handleMessage() method is not invoked due to this i am getting the excetion as org.apache.cxf.ws.policy.PolicyException: No username available at org.apache.cxf.ws.security.wss4j.UsernameTokenInterceptor.policyNotAsserted(UsernameTokenInterceptor.java:398) at org.apache.cxf.ws.security.wss4j.UsernameTokenInterceptor.addUsernameToken(UsernameTokenInterceptor.java:341) at org.apache.cxf.ws.security.wss4j.UsernameTokenInterceptor.addUsernameToken(UsernameTokenInterceptor.java:267) at org.apache.cxf.ws.security.wss4j.UsernameTokenInterceptor.handleMessage(UsernameTokenInterceptor.java:112) at org.apache.cxf.ws.security.wss4j.UsernameTokenInterceptor.handleMessage(UsernameTokenInterceptor.java:76) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:531) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:461) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:364) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:88) 00:05:21,350 ERROR [stderr] (http--192.168.172.142-8080-1) Caused by: org.apache.cxf.ws.policy.PolicyException: No username available Please let me know where is the issue? Thanks in advance, Sridhar -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/774844#774844] Start a new discussion in JBoss Web Services Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - not getting the messages driven from java.util.logging logger

by ramees26

ramees26 [https://community.jboss.org/people/ramees26] created the discussion "not getting the messages driven from java.util.logging logger" To view the discussion, visit: https://community.jboss.org/message/773629#773629 -------------------------------------------------------------- Sir, We had project on ERP.In that we are using the CLogger class which is extended from java.util.logging.Logger.I am getting the log details driven from CLogger in jboss4.2.x. But when I migrate it from jaboss4 to jboss7 the log details are not showing...but when error comes its showing -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773629#773629] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
3
0 / 0

[JBoss AS 7 Development] - Re: Every single remote ejb call starts full authentication process with SecurityDomain cache-type="default"

by Michael Gronau

Michael Gronau [https://community.jboss.org/people/Michael_Gronau] created the discussion "Re: Every single remote ejb call starts full authentication process with SecurityDomain cache-type="default"" To view the discussion, visit: https://community.jboss.org/message/724720#724720 -------------------------------------------------------------- Hello Jason, thank you for your suggestions I will definitely try this out. But I could imagine, that it has the same effect, because the problem is not the authentication on the connection (because this happens only once per user/thread as expected) but on the ejb call itself. But let me see if it works. Thanks alot, Michael -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/724720#724720] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

7
11
0 / 0

[JBoss AS 7 Development] - Is it possible to include a WHERE type clause in CLI ?

by Ed Roberts

Ed Roberts [https://community.jboss.org/people/ejroberts] created the discussion "Is it possible to include a WHERE type clause in CLI ?" To view the discussion, visit: https://community.jboss.org/message/772965#772965 -------------------------------------------------------------- I would like to grab the name of one of the cache containers where it's list of aliases contains "x"; e.g. "ha-partition". I do not know what the name will be at runtime, and it could be reconfigured later to avoid clashes with other JBoss AS instances running within development. Is there CLI syntax to do this ? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/772965#772965] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

3
7
0 / 0

[EJB3 Development] - Re: javax.ejb.EJBAccessException: Invalid User Jboss 5.1

by Lokesh Kumar Padhanvis

Lokesh Kumar Padhanvis [https://community.jboss.org/people/lokeshdotp] created the discussion "Re: javax.ejb.EJBAccessException: Invalid User Jboss 5.1" To view the discussion, visit: https://community.jboss.org/message/773635#773635 -------------------------------------------------------------- Hi folks Sorry for spaming this blog, the method explained in FAQ works absolutely fine, in my case the server side component was protected with the encrypted password. And i had to provide that encrypted password instead of a plain one. I got this by enabling the security TRACE logs :) -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773635#773635] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[EJB3 Development] - javax.ejb.EJBAccessException: Invalid User Jboss 5.1

by Lokesh Kumar Padhanvis

Lokesh Kumar Padhanvis [https://community.jboss.org/people/lokeshdotp] created the discussion "javax.ejb.EJBAccessException: Invalid User Jboss 5.1" To view the discussion, visit: https://community.jboss.org/message/773633#773633 -------------------------------------------------------------- Hi This might be the routine question I am posting here, but I dont know what where else to post. My configuration Jboss 5.1.0 GA app server, EJB3 And I am trying to call a secured method on a SLSB. And I am constantly getting this exception javax.ejb.EJBAccessException: Invalid User at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:165) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:421) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:211) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy3.invoke(Unknown Source) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) at $Proxy2.getAllNetworkElements(Unknown Source) at tryouts.ejb3.Client.start(Client.java:49) at tryouts.ejb3.Client.main(Client.java:33) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy3.invoke(Unknown Source) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) at $Proxy2.getAllNetworkElements(Unknown Source) at tryouts.ejb3.Client.start(Client.java:49) at tryouts.ejb3.Client.main(Client.java:33) I have gone through the security FAQ " https://community.jboss.org/docs/DOC-12198 https://community.jboss.org/wiki/SecurityFAQ" and did the same thing in my client code. Client.java public class Client { public static void main(String[] args) { new Client().start(); } private void start() { try { System.setProperty( "java.security.auth.login.config","src/auth.conf" ); SecurityClient client = SecurityClientFactory.getSecurityClient(); client.setJAAS( "myDomain", new MyCallbackHandler("username","password")); client.login(); InitialContext ctx = new InitialContext(); System.out.println( "Got the initial context" ); Object ref = ctx.lookup( "aserver/TopologySessionBean/remote" ); TopologySessionRemote remote = (TopologySessionRemote) PortableRemoteObject.narrow( ref, TopologySessionRemote.class ); System.out.println( "Got the remote bean: " + remote ); List nes = remote.getAllNetworkElements(); System.out.println( "Number of NEs: " + nes.size() ); } catch ( Exception ex ) { System.out.println( "~~~~~~~~~~~~~ ERROR ~~~~~~~~~~~~~~" ); ex.printStackTrace(); } } class MyCallbackHandler implements CallbackHandler { private String uid; private String pid; public MyCallbackHandler(String uid, String pid ) { this.uid = uid; this.pid = pid; } @Override public void handle( Callback[] callbacks ) throws IOException, UnsupportedCallbackException { for ( Callback cb : callbacks ) { if ( cb instanceof NameCallback ) { NameCallback ncb = (NameCallback) cb; ncb.setName( uid ); } else if ( cb instanceof PasswordCallback ) { PasswordCallback pcb = (PasswordCallback) cb; pcb.setPassword( pid.toCharArray() ); } else { System.out.println( "Not handling Callback: " + cb.getClass() ); } } } } } auth.conf in META-INF directory: myDomain { org.jboss.security.ClientLoginModule required; }; Can someone please help or point me to a working example in this forum or elsewhere in internet. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773633#773633] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[jBPM Development] - Re: JBPM Designer Beta - Simulator

by Juliano Carlos da Silva

Juliano Carlos da Silva [https://community.jboss.org/people/skull] created the discussion "Re: JBPM Designer Beta - Simulator" To view the discussion, visit: https://community.jboss.org/message/773508#773508 -------------------------------------------------------------- I found some bugs in source and made a fix to siumlator work -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773508#773508] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

1
0
0 / 0

[JBoss AS 7 Development] - Re: <error-page> not working for javax.ejb.NoSuchEJBException: JBAS016055

by Stephen Coy

Stephen Coy [https://community.jboss.org/people/sfcoy] created the discussion "Re: <error-page> not working for javax.ejb.NoSuchEJBException: JBAS016055" To view the discussion, visit: https://community.jboss.org/message/773359#773359 -------------------------------------------------------------- You can't catch this particular exception in an error page because it is happening in a background thread rather than the request processing thread. With respect to your original problem, you need to be careful with exception handling in stateful EJBs because the container will unceremoniously remove it if a java.lang.RuntimeException is thrown from it. This is because the bean is then considered to be in an inconsistent state. If it's normal to expect a transaction failure from time to time (duplicate keys comes to mind here) then you may be better off performing that particular operation from a stateless EJB. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/773359#773359] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

13 years, 2 months

2
1
0 / 0

Community Updates, October 25 - November 1

by JBoss Community

=============================================================== Community Updates for October 25 - November 1 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,193 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,470 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Sessions and transactions [https://community.jboss.org/docs/DOC-13951] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * JBoss Tools 4 [https://community.jboss.org/community/tools/blog/2012/09/17/the-return-of...] * JBoss Tools 3.3 and Developer Studio 5.0 Final Release! [https://community.jboss.org/community/tools/blog/2012/06/21/jboss-tools-3...] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/746287#746287] * Re: Jboss 7.1.2.Final is only for EAP? [https://community.jboss.org/message/763860#763860] * Re: How to deploy war file into Jboss 5.0 [https://community.jboss.org/message/727979#727979] Tips and tricks - Reply Using Email Stuck without web access? In a hurry? You can respond to Community discussions by using the reply feature of your email client. Just reply to the email notification that you'd like to respond to, type up your reply, and hit send. Your reply will show up in Community momentarily. Find out more. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Stan Silvert

Stan Silvert [https://community.jboss.org/people/ssilvert] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11039 -------------------------------------------------- > Lukáš Fryč wrote: > > > > Stan, do you plan to include one specific version of MyFaces 2.x in JBoss AS? I don't know yet. I agree that it would be nice. Besides increasing the size of the AS7 download, there are lots of non-technical considerations as well. > Lukáš Fryč wrote: > > Do you plan to allow switch default JSF module using VM args for AS? > e.g. -Djsf.default=myfaces-xyz > Definitely. But I don't think it will be a system property. My plan is to add a management option to the JSF subsystem. So you will be able to set this in XML and/or via CLI. --------------------------------------------------

13 years, 2 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Lukáš Fryč

Lukáš Fryč [https://community.jboss.org/people/lfryc] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11037 -------------------------------------------------- Stan, do you plan to include one specific version of MyFaces 2.x in JBoss AS? This would help adoption of Multi-JSF feature and simplify MyFaces integration testing heavily. Do you plan to allow switch default JSF module using VM args for AS? e.g. -Djsf.default=myfaces-xyz --------------------------------------------------

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2012