July 2013 - jboss-dev-forums - Jboss List Archives

[JBoss Portal Development] - Re: Account Lockout on unsuccessful login attempts

by Ashwini Bangalore

Ashwini Bangalore [https://community.jboss.org/people/ashvini.bang] created the discussion "Re: Account Lockout on unsuccessful login attempts" To view the discussion, visit: https://community.jboss.org/message/829608#829608 -------------------------------------------------------------- Hi Yogesh, Were you able to find solution for this? I need to implement this logic. Thanks, Ashwini. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829608#829608] Start a new discussion in JBoss Portal Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

[JBoss ESB Development] - Re: Original file name as message property for File/FTP gateways

by michael valle

michael valle [https://community.jboss.org/people/mp_valle77] created the discussion "Re: Original file name as message property for File/FTP gateways" To view the discussion, visit: https://community.jboss.org/message/829603#829603 -------------------------------------------------------------- Properties p= message.getProperties(); String fileName= p.getProperty("org.jboss.soa.esb.gateway.original.file.name").toString(); -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829603#829603] Start a new discussion in JBoss ESB Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

[JBoss AS 7 Development] - Ldap configuration

by Moises Jardim Pinheiro

Moises Jardim Pinheiro [https://community.jboss.org/people/jardimpinheiro] created the discussion "Ldap configuration" To view the discussion, visit: https://community.jboss.org/message/829547#829547 -------------------------------------------------------------- Hello! I need to configure jboss with ldap but I have some problems. I tried to do this: web.xml <security-constraint> <web-resource-collection> <web-resource-name>HtmlAuth</web-resource-name> <description>application security constraints </description> <url-pattern>/*</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>admin</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>LDAP Test</realm-name> </login-config> <security-role> <role-name>admin</role-name> </security-role> jboss-web.xml <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <security-domain>java:/jaas/my_ldap_security_domain</security-domain> </jboss-web> standalone.xml <security-domain name="my_ldap_security_domain"> <authentication> <login-module code="LdapExtended" flag="required"> <module-option name="java.naming.provider.url" value="ldap://hml-ldap:389"/> <module-option name="java.naming.security.authentication" value="simple"/> <module-option name="bindDN" value="cn=admin,dc=company,dc=com,dc=br"/> <module-option name="bindCredential" value="pass"/> <module-option name="baseCtxDN" value="ou=users,dc=company,dc=com,dc=br"/> <module-option name="baseFilter" value="uid={0},dc=company,dc=com,dc=br"/> <module-option name="rolesCtxDN" value="ou=groups,dc=company,dc=com,dc=br"/> <module-option name="roleFilter" value="(member={1})"/> <module-option name="roleAttributeID" value="cn"/> <module-option name="throwValidateError" value="true"/> <module-option name="searchScope" value="ONELEVEL_SCOPE"/> </login-module> </authentication> </security-domain> When a put username and password occur this exception: 11:52:48,535 ERROR org.jboss.security.authentication.JBossCachedAuthenticationManager org.jboss.security.authentication.JBossCachedAuthenticationManager (http-localhost-127.0.0.1-8080-1) Login failure: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:270) picketbox-4.0.7.Final.jar:4.0.7.Final at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at java.lang.reflect.Method.invoke(Method.java:601) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at java.security.AccessController.doPrivileged(Native Method) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at javax.security.auth.login.LoginContext.login(LoginContext.java:594) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:449) picketbox-infinispan-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:383) picketbox-infinispan-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:371) picketbox-infinispan-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:160) picketbox-infinispan-4.0.7.Final.jar:4.0.7.Final at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:214) jboss-as-web-7.1.1.Final.jar:7.1.1.Final at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:180) jbossweb-7.0.13.Final.jar: at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:455) jbossweb-7.0.13.Final.jar: at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) jboss-as-web-7.1.1.Final.jar:7.1.1.Final at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) jbossweb-7.0.13.Final.jar: at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) jbossweb-7.0.13.Final.jar: at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) jbossweb-7.0.13.Final.jar: at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) jbossweb-7.0.13.Final.jar: at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) jbossweb-7.0.13.Final.jar: at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) jbossweb-7.0.13.Final.jar: at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) jbossweb-7.0.13.Final.jar: at java.lang.Thread.run(Thread.java:722) https://community.jboss.org/message/829547#829547#829547/rt.jar:1.7.0_11 Ldap configuration Caused by: javax.naming.NamingException: PB00019: Processing Failed:Search of baseDN(ou=users,dc=company,dc=com,dc=br) found no matches at org.jboss.security.auth.spi.LdapExtLoginModule.bindDNAuthentication(LdapExtLoginModule.java:482) picketbox-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.auth.spi.LdapExtLoginModule.createLdapInitContext(LdapExtLoginModule.java:438) picketbox-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:312) picketbox-4.0.7.Final.jar:4.0.7.Final at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:267) picketbox-4.0.7.Final.jar:4.0.7.Final What is going on? I changed some configurations and tried a lot but I don't achieve. There are other programs that connect in the same ldap and work fine. However in this case (with jboss) there are some problems, certainly in my configurations. Thanks! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829547#829547] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

[jBPM Development] - Which is stable version of jbpm 5.3 or 5.4?

by dhana lakshmi

dhana lakshmi [https://community.jboss.org/people/dhanalakshmiv14] created the discussion "Which is stable version of jbpm 5.3 or 5.4?" To view the discussion, visit: https://community.jboss.org/message/801988#801988 -------------------------------------------------------------- Hi, I would like to understand differences between jbpm 5.3 and 5.4 and which is more stable (i.e with less issues). Which version would be better to integrate with a web application (using spring , hibernate and Tomcat) Please help me as I am new to jBPM. Thanks in advance!! -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/801988#801988] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

2
1
0 / 0

[JBoss AS Development Deployment Framework] - How to deploy XMBean defined for 4.2.3 in 7.1.0 Final

by Arun Varadharajan

Arun Varadharajan [https://community.jboss.org/people/arun168403] created the discussion "How to deploy XMBean defined for 4.2.3 in 7.1.0 Final" To view the discussion, visit: https://community.jboss.org/message/829280#829280 -------------------------------------------------------------- I have a XMBean defined for Jboss4.2.3 and successfully deployed. When I deploy the same on Jboss7.1.0 Final, I getting the error as : Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017224: Failed to parse service xml ["/D:/Upgrade/OFF2/export/home/application/zic/jboss-as-7.1.0.Final/standalone/deployments/gem.ear/nequeue_s ervices.sar/META-INF/jboss-service.xml"] at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:95) 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: Not a textual event (START_ELEMENT) at com.ctc.wstx.sr.BasicStreamReader.throwNotTextual(BasicStreamReader.java:5444) at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:833) at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.getText(XMLExtendedStreamReaderImpl.java:275) at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.unexpectedContent(JBossServiceXmlDescriptorParser.java:622) at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.parseMBean(JBossServiceXmlDescriptorParser.java:212) at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElement(JBossServiceXmlDescriptorParser.java:183) at org.jboss.as.service.descriptor.JBossServiceXmlDescriptorParser.readElement(JBossServiceXmlDescriptorParser.java:46) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.service.ServiceDeploymentParsingProcessor.deploy(ServiceDeploymentParsingProcessor.java:88) My jboss-service.xml and xmbean.xml looks as below: ---------------------------------------------------------------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8" ?> <server xmlns="urn:jboss:service:7.0" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd">  <mbean code="com.abc.nequeue.NeScheduler" name="GEMService:service=NeScheduler" xmbean-dd="META-INF/nescheduler-xmbean.xml"> <depends>jboss:service=Naming</depends> <depends>jboss.mq:service=DestinationManager</depends> </mbean> </server> --------------------------------------------------------------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE mbean PUBLIC "-//JBoss//DTD JBOSS XMBEAN 1.1//EN" " http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd" > <mbean> <description>XMBean for representing the NE scheduler</description> <descriptors> <persistence persistPolicy="Never" persistPeriod="0" persistLocation="data/NeScheduler.data" persistName="NeScheduler" /> </descriptors> <class>com.abc.nequeue.NeScheduler</class> <constructor> <description> The default constructor</description> <name>NeScheduler</name> </constructor>  &defaultAttributes; <attribute access="read-only" getMethod="getThreadPoolSize"> <description>The number of threads in the thread pool</description> <name>ThreadPoolSize</name> <type>int</type> </attribute> <attribute access="read-only" getMethod="getMaxThreadPoolSize"> <description>The maximum number of threads in the thread pool</description> <name>MaxThreadPoolSize</name> <type>int</type> </attribute> <attribute access="read-only" getMethod="getQueueLength"> <description>The number of number of nes in the queue</description> <name>QueueLength</name> <type>int</type> </attribute> <attribute access="read-only" getMethod="getWaitingThreadCount"> <description>The number of threads waiting for work.</description> <name>WaitingThreadCount</name> <type>int</type> </attribute>  <operation impact="ACTION_INFO"> <description>Schedule a command</description> <name>schedule</name> <parameter> <description>neId for the command</description> <name>neId</name> <type>int</type> </parameter> <parameter> <description>Scheduled Command</description> <name>cmd</name> <type>com.abc.ne.ejb.NeCommand</type> </parameter> </operation> <operation impact="ACTION_INFO"> <description>Unschedule all commands</description> <name>unschedule</name> <parameter> <description>neId for the command</description> <name>neId</name> <type>int</type> </parameter> <return-type>boolean</return-type> </operation> &defaultOperations; </mbean> Please help. I completly stucked. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829280#829280] Start a new discussion in JBoss AS Development Deployment Framework at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

[JBoss Tools Development] - Integration Tooling Release Process

by Paul Leacu

Paul Leacu [https://community.jboss.org/people/pleacu] modified the document: "Integration Tooling Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-48326 -------------------------------------------------------------- h1. Overview This document details the process for building and releasing composite/aggregate update sites for the JBoss integration tooling (formerly SOA tools). h2. Goals * Provide a light-weight process with minimal overhead for component owners. * Provide an ever-current update site containing the latest, stable releases of integration tooling components. * Allow component owners to independently manage their release schedules. * Allow component owners to manage their own dependency stack. h2. Assumptions * Components use released versions of dependencies (i.e. stable builds). * Component owners manage their own interdependencies with other integration components. * Components and dependencies adhere to Eclipse API versioning rules. h2. Implications * Aggregate releases will be driven by component releases. * Aggregate releases should manage themselves. * Component nightly/milestone builds should always be compatible with other components in the aggregate. h2. Definitions * *Integration Stack (IS)* - all JBoss middleware integration tooling * *IS configuration* - the definition of specific components and versions that make up the IS * *IS build* - an update site (p2 repo) aggregating specific versions of integration tooling components. * *Release types:** *stable* - an IS build aggregating stable (i.e. final) builds of all components that has been certified/tested by QA. * *development* - an IS build aggregating stable builds of all components that has not been certified/tested by QA. * *integration* - an IS build aggregating stable, development (e.g. beta) and/or integration builds of all components * *next* - an internal IS build incorporating the latest integration builds of all components (i.e. the current "trunk" build). This will be used for identifying potential future incompatibilities. Stable builds will align with a JBDS release in the same way JBT core builds do today. Development builds will reflect the current state of all stable components. Theoretically, any development build could be QA'd and promoted to stable (assuming no test failures). Integration builds allow for an "interim" stack which may be useful during a QA cycle (e.g. verifying a fix that requires updates to multiple components; a single component can be updated via the component update site). Next builds are used to identify potential incompatiblilities among components before they are integrated into a release and would occur weekly/monthly via a Hudson job (e.g. targeting JBT integration builds). An IS build only needs to occur when the IS configuration changes. Because the IS stack is composed of stable components, configuration changes will only occur when individual components are released. For this reason, it is assumed the build would be invoked manually and there is not reason for a nightly build. h1. Roles and Responsibilities h2. Component Owners 1. *Component update site:* Component owners must provide an update site for each release of their component that is included in an IS build. 2. *Updating IS configuration:* Component owners must update the IS build configuration when a new version of their component is released. This ensures the IS is up-to-date. 3. *Respond to change requests:* Component owners must review IS configuration change requests and respond in a timely manner. If a requested change is incompatible with the current version of your component, provide details regarding when your component will be compatible, along with a patch containing changes to the IS configuration for your compatible release. h2. Release Engineers 1. *Maintain build infrastructure:* Release engineers will be responsible for maintianing the build infrastructure, primarily the Jenkins jobs. 2. *Processing pull requests:* Release engineers will be responsible processing all pull requests related to IS configuration. This is to ensure consistency in the composition of the stack (e.g. components, component versions, IS version, etc.). 3. *Initiate IS builds:* Release engineers will be responsible for initiating IS builds. 4. *Build promotion:* Release engineers will be responsible for the promotion of IS builds (e.g. from development to stable). h1. Release Process h2. Component Updates The following outlines the basic process for updating the IS configuration. Typically, this would occur when a component is released, but the same process is also used for updating shared dependencies (e.g. JBT core, third-party plugins, etc.). 1. Create a branch in the user repository for your IS configuration changes. 2. Modify the Integration Stack configuration for your updates, e.g. update URL for SwitchYard from 0.5.0.Final to 0.6.0.Final; update IS version from 0.9.0 to 0.9.1 (see versioning rules)1. For changes to your component you must update the community aggregate: https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb.... Modify the https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... compositeArtifacts.xml and https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... compositeContent.xml files to point to the new component update site. 2. Modify the https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... category.xml file as necessary for any feature changes (e.g. adding a feature). 3. Modify the project version in https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... pom.xml. 2. For changes to your component within the production aggregate: https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... * Note: The production component update sites will be drawn from the community composite files. 0.0.1. Modify the https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... category.xml file as necessary for any feature changes (e.g. adding a feature). 0.0.2. Modify the project version in https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... pom.xml. 0.2. For changes to dependencies: https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta... https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta.... Modify https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... integration-stack-base.target, https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... core-base.target or https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... community.target. The integration-stack-base and core-base combine to include all dependencies which are included as part of JBDS. See the generated aggregate-base.target in your repository. The community target extends the base target by including dependencies which are only available in community JBT releases (aggregate-full.target). e.g. I need to update to graphiti 0.9.2: 0.0.0.1. fork/branch/modify https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... integration-stack-base.target 0.0.0.2. update the version of graphiti 0.0.0.3. verify that the updated version is being mirrored correctly on jboss.org 0.0.1. Modify project version in https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... pom.xml 0.0.2. Ensure plugins are mirrored on jboss.org 1. Build locally to validate stack dependencies. 2. Create a https://issues.jboss.org/browse/JBTIS JBTIS JIRA task requesting update, e.g. update SwitchYard to 0.6.0.Final* Include link to github branch in task * Include build results (e.g. SUCCESS or specific dependency resolution errors) 3. Create subtasks against each IS component for verification/approval* For components that failed the consistency check, mark subtasks appropriately, e.g. m2e-wtp version is inconsistent 4. Merge any changes required by other components from subtasks (e.g. update Savara to 2.1.0.Final) 5. Build IS locally to validate dependency consistency 6. Issue pull request against upstream IS configuration project 7. Process pull (by release engineer) 8. Invoke build job (by release engineer) h2. Platform Updates *Goal:* release updated IS within four weeks of JBT/JBDS core release. 1. Initiate platform update during JBT beta phase 2. Follow the component update process above (e.g. update JBT core from 3.3 to 4.0) h2. JBoss Central Discovery Updates *Goal:* Modify the JBoss Central mylyn discovery install/update mechanism. JBoss Central, based on http://wiki.eclipse.org/Mylyn/Discovery Mylyn Discovery, is in part a UI for installing new features into Eclipse or JBDS. It provides a richer, yet simpler UI than what the Eclipse equinox p2 install manager provides out of the box. For detailed information see https://community.jboss.org/docs/DOC-48297 https://community.jboss.org/wiki/JBossCentralsSoftwareUpdateTab-HowDoesIt... 1. For changes to the jbosstools community discovery update: https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... or production discovery update: https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... follow the same git process as defined in the Components Updates section. 2. Modify the plugin connector descriptors and installation units as needed within the discovery plugin. 3. Add any icons that may be required. h2. Dependency Updates The process for updating a shared dependency is the same as that for updating any other component, with the following additions: 1. Make sure the dependency is mirrored on jboss.org. 2. Make sure the dependency is not already included through JBT core. If a dependency is included through JBT core, you will need to coordinate with the core team on the upgrade, as the change may impact components outside the IS. h2. Versioning Rules - major.minor.update.build *Major* should be updated for: * Base platform changes, e.g. Eclipse Indigo->Juno, JBT 3.3->4.0 * Major component updates, e.g. SwitchYard 1.0->2.0 *Minor* should be updated for minor component updates, e.g. SwitchYard 0.5->0.6 *Update* should be updated for minor component updates, e.g. SwitchYard 0.5.0->0.5.1 *Build* should be updated for each build, e.g. when building against nightly/integration/development repositories ** Note, the basic assumption here is that components are adhering to basic API rules (per Eclipse; e.g. minor includes bug fixes and api additions, major may include breaking api changes). h1. Update Site Locations * *Integration builds: http://download.jboss.org/jbosstools/updates/integration/juno/integration... http://download.jboss.org/jbosstools/updates/integration/juno/integration... * *Development builds: http://http://download.jboss.org/jbosstools/updates/development/juno/inte... http://http://download.jboss.org/jbosstools/updates/development/juno/inte... * *Stable builds: http://http://download.jboss.org/jbosstools/updates/stable/juno/integrati... http://http://download.jboss.org/jbosstools/updates/stable/juno/integrati... h1. Infrastructure * *JIRA -* https://issues.jboss.org/browse/JBTIS https://issues.jboss.org/browse/JBTIS * *Source -* https://github.com/jbosstools/jbosstools-integration-stack https://github.com/jbosstools/jbosstools-integration-stack* *target-platform* - provides a target platform defining all upstream dependencies for use by IS components (e.g. JBT core, third-party plugins) * *aggregate-site* - provides category and feature definitions for the IS update site * *discovery* - provides JBoss Central discovery support * *Jenkins* - * *target platform* - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-target-platform https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-target-platform * *aggregate* - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate * *aggregate publish/promote* - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publish https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publish * *discovery* - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-discovery https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-discovery * *install tests* - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-4.0_stable_bra... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-4.0_stable_bra... h2. Target Platforms The provided target platforms define all upstream dependencies available to an IS component. Three target platforms are provided: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... integration-stack-base.target, https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... core-base.target and https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... community.target (see Component Updates above). If your component needs to be included in a JBDS release, DO NOT use the community target platform. For more information and an example on how to refer to the target platform definition, see: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/RE... https://github.com/jbosstools/jbosstools-integration-stack/blob/master/RE... h1. Future Plans 1. Add support for executing component unit tests as part of the aggregate build. The goal being to help ensure the stability of the aggregate. Add a "next" build that will build against upcoming core platforms (e.g. Kepler, JBT 4.1). This should serve as an early warning system to identify platform incompatibilities early in the process -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-48326] Create a new document in JBoss Tools Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

10 years, 9 months

1
0
0 / 0

[JBoss Transactions Development] - Re: Transactional MSC

by Paul Robinson

Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion "Re: Transactional MSC" To view the discussion, visit: https://community.jboss.org/message/828939#828939 -------------------------------------------------------------- David, Did you have any input on this Q? > [Q] Does Narayana currently do everything needed to prototype this? I think it makes sense to think about what changes would be needed in Narayana now, but delay implementation of them until the prototype is sufficiently well underway. This would ensure that the changes are very likely needed before we spend development time on them. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/828939#828939] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

2
2
0 / 0

[JBoss Transactions Development] - Re: Transactional MSC

by David Lloyd

David Lloyd [https://community.jboss.org/people/dmlloyd] created the discussion "Re: Transactional MSC" To view the discussion, visit: https://community.jboss.org/message/829109#829109 -------------------------------------------------------------- > Paul Robinson wrote: > > David, > > David Lloyd wrote: > > > > OK I will attempt to answer as many questions as I can. > > > [Q] Is it correct that the audit should contain the update (and it's outcome), even if the transaction failed and also in the presence of a crash? > > Starting off with the tough ones I see. :) > > > > Currently our audit requirements are met by using syslog-style remote logging, which is done in a very ad-hoc manner (i.e. without sensitivity to crashes). It will be difficult, regardless of the answer to this question, to both meet the remote log requirement as well as dealing with the possibility of crashing. AFAIK there is no way to log to syslog transactionally. > > > > Ignoring that problem though, my feeling is that we are only required to Audit (with a capital A) changes that were successfully made, but we do want to at least locally log (in a human-readable fashion) failures as well. > > Given the limitations of the syslog-style logging, is it sufficient to simply log successful operations immediately after they occur? This raises a number of possible issues: > > * There's a window between the transaction completing and the audit being written. A failure here would result in a un-audited successful action. > Yeah it's a tradeoff between logging things before the transaction is committed, and potentially losing stuff. And syslog itself is not exactly super-robust. But I think that the limitations were known and accepted when this solution was designed. > * Some transactions will be completed by the recovery manager. I don't think the audit would be written for these under the current solution. > > The problem with these two issues is that I don't think there is an easy way for the user to know that there are some potentially missing entries. We could solve this by always logging the intent of the transaction to the audit prior to beginning it. Then by taking all 'intent' entries without a corresponding 'outcome' entry, you get a list of items to investigate. With this approach you would also need to log failures, in order to ensure that the 'outcome 'is always present. > > How important is it, that the audit be complete? If we can't provide strong enough guarantees, maybe we need to consider using a transactional audit? I think it's pretty important that it's complete, and we probably will want to look into a real transactional audit at some point (not today though as the current solution was deemed good enough by its implementers). -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829109#829109] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

2
2
0 / 0

[jBPM Development] - JBPM 5.4 Persisted Sessions

by craimundo

craimundo [https://community.jboss.org/people/craimundo] created the discussion "JBPM 5.4 Persisted Sessions" To view the discussion, visit: https://community.jboss.org/message/829070#829070 -------------------------------------------------------------- Hi, I´m currently using JBPM 5.4, and I´m using one to one relationship between Session and Process Instance. So, I have multiple sessions stored in DB. When I restart server, how can I get the sessions and make the loadStatefulKnowledgeSession? I have multiple rows in SessionInfo table but I don´t know which of them are in waiting state. Thans in advance, CR -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829070#829070] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

[jBPM Development] - Include condition on User Tasks

by Rajesh P

Rajesh P [https://community.jboss.org/people/javalearner] created the discussion "Include condition on User Tasks" To view the discussion, visit: https://community.jboss.org/message/829041#829041 -------------------------------------------------------------- Hi, I have an approval process for this, I need to get the approvers based on the Group and some other condition. I will explain bit clear, In my application approvers are based on the Group as well as location. Means, If a person is part of the "Approvers Group" and should have access to "Location A" then only he can approve that request which are raised for "Location A". Do we have any solution to include one more condition along with group id in user task? As of now, to autheticate users and groups I am using Implemenation class which will talk to my application's users and groups tables. So If I pass location id/name as process variable, How can I get that information while authenticating users and groups in Implementation class? Can some one please light on this. Please let me know if you need any other information. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/829041#829041] Start a new discussion in jBPM Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2013