November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project

by Jose Cavieres (JIRA)

[ https://issues.jboss.org/browse/DROOLS-658?page=com.atlassian.jira.plugin... ] Jose Cavieres updated DROOLS-658: --------------------------------- Attachment: reuse.tgz Added both projects Papito="reusable project" and Hijita="top project", according to the names used in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... > External POJOs not shown in Workbench after reopen the project > -------------------------------------------------------------- > > Key: DROOLS-658 > URL: https://issues.jboss.org/browse/DROOLS-658 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: linux 64 bits > Reporter: Jose Cavieres > Assignee: Mark Proctor > Attachments: reuse.tgz > > > In order to reuse some POJOs, I followed the procedure defined in > http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... > and added a POJO to the "reusable project" (named Papito) > Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: > http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html/wb.Work... > The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project

by Jose Cavieres (JIRA)

[ https://issues.jboss.org/browse/DROOLS-658?page=com.atlassian.jira.plugin... ] Jose Cavieres updated DROOLS-658: --------------------------------- Description: In order to reuse some POJOs, I followed the procedure defined in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... and added a POJO to the "reusable project" (named Papito) Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html/wb.Work... The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" was: In order to reuse some POJOs, I followed the procedure defined in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... and added a POJO to the "reusable project" (named Papito) Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: http://docs.jboss.org/drools/release/6.1.0.Final/drools- docs/html/wb.Workbench.html#wb.DataModeller The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" > External POJOs not shown in Workbench after reopen the project > -------------------------------------------------------------- > > Key: DROOLS-658 > URL: https://issues.jboss.org/browse/DROOLS-658 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: linux 64 bits > Reporter: Jose Cavieres > Assignee: Mark Proctor > > In order to reuse some POJOs, I followed the procedure defined in > http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... > and added a POJO to the "reusable project" (named Papito) > Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: > http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html/wb.Work... > The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project

by Jose Cavieres (JIRA)

[ https://issues.jboss.org/browse/DROOLS-658?page=com.atlassian.jira.plugin... ] Jose Cavieres updated DROOLS-658: --------------------------------- Description: In order to reuse some POJOs, I followed the procedure defined in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... and added a POJO to the "reusable project" (named Papito) Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: http://docs.jboss.org/drools/release/6.1.0.Final/drools- docs/html/wb.Workbench.html#wb.DataModeller The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" was: In order to reuse some POJOs, I followed the procedure defined in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... and added a POJO to the "reusable project" (named Papito) Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "-ext-" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: http://docs.jboss.org/drools/release/6.1.0.Final/drools- docs/html/wb.Workbench.html#wb.DataModeller The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" Steps to Reproduce: 1. Follow http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... creating one POJO in "reusable project" 2. LogOut / Log/in 3. Goto the Data Modeler/Java Editor of the "top project" 4. The POJO created in 1 doesn't show as a valid Type > External POJOs not shown in Workbench after reopen the project > -------------------------------------------------------------- > > Key: DROOLS-658 > URL: https://issues.jboss.org/browse/DROOLS-658 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: linux 64 bits > Reporter: Jose Cavieres > Assignee: Mark Proctor > > In order to reuse some POJOs, I followed the procedure defined in > http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... > and added a POJO to the "reusable project" (named Papito) > Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "- ext -" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: > http://docs.jboss.org/drools/release/6.1.0.Final/drools- > docs/html/wb.Workbench.html#wb.DataModeller > The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-658) External POJOs not shown in Workbench after reopen the project

by Jose Cavieres (JIRA)

Jose Cavieres created DROOLS-658: ------------------------------------ Summary: External POJOs not shown in Workbench after reopen the project Key: DROOLS-658 URL: https://issues.jboss.org/browse/DROOLS-658 Project: Drools Issue Type: Bug Affects Versions: 6.2.0.CR2, 6.1.0.Final Environment: linux 64 bits Reporter: Jose Cavieres Assignee: Mark Proctor In order to reuse some POJOs, I followed the procedure defined in http://mswiderski.blogspot.com/2014/02/reuse-your-business-assets-with-jb... and added a POJO to the "reusable project" (named Papito) Everything works fine the first time one uses those clases in the "top project" (named Hijita) . POJOs of the "reusable project" are prefixed with the string "-ext-" in the Java editor of the "top project" just as explained in "15.7.6.6.3. Using the external objects" of the document: http://docs.jboss.org/drools/release/6.1.0.Final/drools- docs/html/wb.Workbench.html#wb.DataModeller The problem is that only happens the first time. If one logout and the login again, the "-ext" classes are no longer shown as valid Types por the POJOs in the "top project" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-274) The CLI command "read-boot-errors" does not include the timestamp of the error event

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-274: ------------------------------------------------ Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1160898|https://bugzilla.redhat.com/show_bug.cgi?id=1160898] from ASSIGNED to POST > The CLI command "read-boot-errors" does not include the timestamp of the error event > ------------------------------------------------------------------------------------ > > Key: WFCORE-274 > URL: https://issues.jboss.org/browse/WFCORE-274 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > The CLI command "read-boot-errors" does not include the timestamp of the error event. For anyone using this command for diagnostic purposes, the absence of an event's timestamp decreases the usefulness of the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4140) In some case :activare on resource-adapter fails if id != archive_name

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4140?page=com.atlassian.jira.plugin.... ] Stefano Maestri updated WFLY-4140: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/7007 (was: https://c.na7.visual.force.com/apex/Case_View?sbstr=00910815) > In some case :activare on resource-adapter fails if id != archive_name > ---------------------------------------------------------------------- > > Key: WFLY-4140 > URL: https://issues.jboss.org/browse/WFLY-4140 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > deploy /home/jolee/amq.rar > /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction) > /subsystem=resource-adapters/resource-adapter=amq/config-properties=UseInboundSession:add(value=false) > /subsystem=resource-adapters/resource-adapter=amq/config-properties=ServerUrl:add(value="vm://localhost") > /subsystem=resource-adapters/resource-adapter=amq/config-properties=BrokerXmlConfig:add(value="xbean:broker-config.xml") > /subsystem=resource-adapters/resource-adapter=amq/connection-definitions=ConnectionFactory:add(jndi-name=java:jboss/ConnectionFactory,use-java-context=true,class-name=org.apache.activemq.ra.ActiveMQManagedConnectionFactory,enabled=true) > /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter:add(jndi-name=java:jboss/queue/EAIProcessStarter,use-java-context=false,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true) > /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter/config-properties=PhysicalName:add(value=EAIProcessStarter) > /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER:add(jndi-name=java:/jboss/queue/EAI_TRIGGER,use-java-context=true,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true) > /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER/config-properties=PhysicalName:add(value=EAI_TRIGGER) > /subsystem=resource-adapters/resource-adapter=amq:activate > [4] > [standalone@localhost:9999 /] run-batch --file=/home/jolee/rar2.cli > {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-10" => "JBAS010480: RAR 'amq' not yet deployed."}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4140) In some case :activare on resource-adapter fails if id != archive_name

by Stefano Maestri (JIRA)

Stefano Maestri created WFLY-4140: ------------------------------------- Summary: In some case :activare on resource-adapter fails if id != archive_name Key: WFLY-4140 URL: https://issues.jboss.org/browse/WFLY-4140 Project: WildFly Issue Type: Feature Request Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri deploy /home/jolee/amq.rar /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction) /subsystem=resource-adapters/resource-adapter=amq/config-properties=UseInboundSession:add(value=false) /subsystem=resource-adapters/resource-adapter=amq/config-properties=ServerUrl:add(value="vm://localhost") /subsystem=resource-adapters/resource-adapter=amq/config-properties=BrokerXmlConfig:add(value="xbean:broker-config.xml") /subsystem=resource-adapters/resource-adapter=amq/connection-definitions=ConnectionFactory:add(jndi-name=java:jboss/ConnectionFactory,use-java-context=true,class-name=org.apache.activemq.ra.ActiveMQManagedConnectionFactory,enabled=true) /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter:add(jndi-name=java:jboss/queue/EAIProcessStarter,use-java-context=false,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true) /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter/config-properties=PhysicalName:add(value=EAIProcessStarter) /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER:add(jndi-name=java:/jboss/queue/EAI_TRIGGER,use-java-context=true,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true) /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER/config-properties=PhysicalName:add(value=EAI_TRIGGER) /subsystem=resource-adapters/resource-adapter=amq:activate [4] [standalone@localhost:9999 /] run-batch --file=/home/jolee/rar2.cli {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-10" => "JBAS010480: RAR 'amq' not yet deployed."}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4139) JBatch module dependencies not configured for valid deployments

by Brent Douglas (JIRA)

Brent Douglas created WFLY-4139: ----------------------------------- Summary: JBatch module dependencies not configured for valid deployments Key: WFLY-4139 URL: https://issues.jboss.org/browse/WFLY-4139 Project: WildFly Issue Type: Bug Components: Batch Affects Versions: 9.0.0.Alpha1, 8.2.0.Final Environment: Fedora 19, JDK 8u25, wildfly-dist:9.0.0.Alpha1 Reporter: Brent Douglas Assignee: Jason Greene In BatchEnvironmentProcessor the JBatch subsystem only adds a dependency on wildfly's transaction manager and bean manager if some marker files are detected. (See here) https://github.com/wildfly/wildfly/blob/bfc41360196f5183a005101bf7ac2d7bf... If they are not detected an unhelpful exception is thrown when instantiating the JobOperator: {noformat} 01:18:25,442 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 248.119 sec <<< FAILURE! - in io.machinecode.chainlink.ee.wildfly.WildFlyTest testGlassfish(io.machinecode.chainlink.ee.wildfly.WildFlyTest) Time elapsed: 0.336 sec <<< ERROR! java.util.ServiceConfigurationError: javax.batch.operations.JobOperator: Provider org.jberet.operations.JobOperatorImpl could not be instantiated at org.wildfly.jberet.services.BatchEnvironmentService$WildFlyBatchEnvironment.getArtifactFactory(BatchEnvironmentService.java:123) at org.wildfly.jberet.DelegatingBatchEnvironment.getArtifactFactory(DelegatingBatchEnvironment.java:52) at org.jberet.operations.JobOperatorImpl.<init>(JobOperatorImpl.java:89) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at java.lang.Class.newInstance(Class.java:438) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.batch.runtime.BatchRuntime.getJobOperator(BatchRuntime.java:57) at io.machinecode.chainlink.ee.wildfly.WildFlyTest.testGlassfish(WildFlyTest.java:36) {noformat} There are valid reasons that these marker files may not be in the deployment, an example being that the deployment might only read metadata from jobs started by other deployments from the configured repository. This check also does not take into account jars in a war's lib dir (for example if you try and run a test using arquillian) or in an ear, which should be allowed. I think there should be two changes. Firstly, those dependencies should be added unconditionally as there are cases where these marker will not be present and they will still be required. Secondly, the exception thrown because the beanManager has not been configured should be thrown earlier in the lifecycle where it will generate a real error message (perhaps in BatchEnvironmentService#start before creating the WildFlyBatchEnvironment where it can first be detected): https://github.com/wildfly/wildfly/blob/bfc41360196f5183a005101bf7ac2d7bf... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-260) Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-260: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1161589|https://bugzilla.redhat.com/show_bug.cgi?id=1161589] from POST to MODIFIED > Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab > ------------------------------------------------------------------------------------------ > > Key: WFCORE-260 > URL: https://issues.jboss.org/browse/WFCORE-260 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-57) Deprecated resource is present in r-r-d of /subsystem=security/security-domain=*

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-57?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-57: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1070214|https://bugzilla.redhat.com/show_bug.cgi?id=1070214] from POST to MODIFIED > Deprecated resource is present in r-r-d of /subsystem=security/security-domain=* > -------------------------------------------------------------------------------- > > Key: WFCORE-57 > URL: https://issues.jboss.org/browse/WFCORE-57 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Harald Pehl > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > When executing > {code} > /subsystem=security/security-domain=*:read-resource-description(recursive-depth=2) > {code} > the acl subresource contains both the deprecated child-resource {{login-module}} and the new one called {{acl-module}}: > {code} > ... > "acl" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > "model-description" => {"classic" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > ... > "operations" => undefined, > "children" => { > "acl-module" => { > "description" => "ACL module", > "model-description" => {"*" => { > "description" => "List of authentication modules", > ... > "operations" => undefined, > "children" => {} > }} > }, > "login-module" => { > "description" => "Login module", > "model-description" => {"*" => undefined} > } > } > }} > }, > ... > {code} > However the deprecated subresource {{login-modules}} should only appear if setting {{include-aliases=true}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014