[JBoss JIRA] (DROOLS-3598) Misleading error messagaes generated by maven plugin when creating an executable model kjar
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3598?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3598:
--------------------------------
Sprint: 2019 Week 05-07
> Misleading error messagaes generated by maven plugin when creating an executable model kjar
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3598
> URL: https://issues.jboss.org/browse/DROOLS-3598
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Mario Fusco
> Assignee: Luca Molteni
> Priority: Major
> Attachments: HelloWorld2.zip
>
>
> When generating a kjar for the executable model with the maven-plugin it generates some spurious and not relevant error messages like these
> {code}
> [ERROR] Cannot load artifact org.drools:drools-core:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-model-compiler:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-canonical-model:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.jbpm:jbpm-bpmn2:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-decisiontables:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.kie:kie-api:${kie.version}. You need kie-ci on the classpath to perform this operation
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3598) Misleading error messagaes generated by maven plugin when creating an executable model kjar
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3598?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-3598:
-------------------------------------
Try a 'mvn clean install -DgenerateModel=YES' on the attached project to reporoduce the problem.
> Misleading error messagaes generated by maven plugin when creating an executable model kjar
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3598
> URL: https://issues.jboss.org/browse/DROOLS-3598
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Mario Fusco
> Assignee: Luca Molteni
> Priority: Major
> Attachments: HelloWorld2.zip
>
>
> When generating a kjar for the executable model with the maven-plugin it generates some spurious and not relevant error messages like these
> {code}
> [ERROR] Cannot load artifact org.drools:drools-core:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-model-compiler:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-canonical-model:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.jbpm:jbpm-bpmn2:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-decisiontables:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.kie:kie-api:${kie.version}. You need kie-ci on the classpath to perform this operation
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3598) Misleading error messagaes generated by maven plugin when creating an executable model kjar
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3598?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3598:
--------------------------------
Attachment: HelloWorld2.zip
> Misleading error messagaes generated by maven plugin when creating an executable model kjar
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3598
> URL: https://issues.jboss.org/browse/DROOLS-3598
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Mario Fusco
> Assignee: Luca Molteni
> Priority: Major
> Attachments: HelloWorld2.zip
>
>
> When generating a kjar for the executable model with the maven-plugin it generates some spurious and not relevant error messages like these
> {code}
> [ERROR] Cannot load artifact org.drools:drools-core:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-model-compiler:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-canonical-model:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.jbpm:jbpm-bpmn2:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.drools:drools-decisiontables:${kie.version}. You need kie-ci on the classpath to perform this operation
> [ERROR] Cannot load artifact org.kie:kie-api:${kie.version}. You need kie-ci on the classpath to perform this operation
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3598) Misleading error messagaes generated by maven plugin when creating an executable model kjar
by Mario Fusco (Jira)
Mario Fusco created DROOLS-3598:
-----------------------------------
Summary: Misleading error messagaes generated by maven plugin when creating an executable model kjar
Key: DROOLS-3598
URL: https://issues.jboss.org/browse/DROOLS-3598
Project: Drools
Issue Type: Bug
Components: executable model
Reporter: Mario Fusco
Assignee: Luca Molteni
When generating a kjar for the executable model with the maven-plugin it generates some spurious and not relevant error messages like these
{code}
[ERROR] Cannot load artifact org.drools:drools-core:${kie.version}. You need kie-ci on the classpath to perform this operation
[ERROR] Cannot load artifact org.drools:drools-model-compiler:${kie.version}. You need kie-ci on the classpath to perform this operation
[ERROR] Cannot load artifact org.drools:drools-canonical-model:${kie.version}. You need kie-ci on the classpath to perform this operation
[ERROR] Cannot load artifact org.jbpm:jbpm-bpmn2:${kie.version}. You need kie-ci on the classpath to perform this operation
[ERROR] Cannot load artifact org.drools:drools-decisiontables:${kie.version}. You need kie-ci on the classpath to perform this operation
[ERROR] Cannot load artifact org.kie:kie-api:${kie.version}. You need kie-ci on the classpath to perform this operation
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ELY-1735) Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API
by Diana Vilkolakova (Jira)
[ https://issues.jboss.org/browse/ELY-1735?page=com.atlassian.jira.plugin.s... ]
Diana Vilkolakova commented on ELY-1735:
----------------------------------------
There are two private packages in module wildfly-elytron-auth-server: wildfly.security.cache and wildfly.security.auth.server._private.
Classes from wildfly.security.cache package would create circular dependency if moved elsewhere, and maybe should become public API so custom mechanisms can use cached identities.
Class ElytronMessages from wildfly.security.auth.server._private is used in multiple packages from this module and is not used by other module.
> Clean up the 'wildfly-elytron-auth-server' module as it currently contains both public and private API
> ------------------------------------------------------------------------------------------------------
>
> Key: ELY-1735
> URL: https://issues.jboss.org/browse/ELY-1735
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: Farah Juma
> Assignee: Diana Vilkolakova
> Priority: Major
> Fix For: 2.0.0.Alpha1, 1.9.0.CR1
>
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3597) Drools Refresh KB gives error
by RAMNATHA ACHARYA (Jira)
RAMNATHA ACHARYA created DROOLS-3597:
----------------------------------------
Summary: Drools Refresh KB gives error
Key: DROOLS-3597
URL: https://issues.jboss.org/browse/DROOLS-3597
Project: Drools
Issue Type: Bug
Affects Versions: 7.17.0.Final
Reporter: RAMNATHA ACHARYA
Assignee: Mario Fusco
Please create huge knowledge base (4GB) where the tomcat memory is 8GB and try to refresh the engine multiple time every 3hr
You will see the drools will stop responding sporadically
it will be nice if you can help and do some memory manage
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (DROOLS-3595) KIA error in 7.17.0
by RAMNATHA ACHARYA (Jira)
[ https://issues.jboss.org/browse/DROOLS-3595?page=com.atlassian.jira.plugi... ]
RAMNATHA ACHARYA commented on DROOLS-3595:
------------------------------------------
cool got it resolved my self thanks for the help
> KIA error in 7.17.0
> -------------------
>
> Key: DROOLS-3595
> URL: https://issues.jboss.org/browse/DROOLS-3595
> Project: Drools
> Issue Type: Bug
> Components: Artifact Repository, kie server
> Affects Versions: 7.17.0.Final
> Reporter: RAMNATHA ACHARYA
> Assignee: Mario Fusco
> Priority: Blocker
>
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Loading kie.conf from jar:file:/C:/Users/bacharya/.m2/repository/org/drools/drools-core/7.17.0.Final/drools-core-7.17.0.Final.jar!/META-INF/kie.conf in classloader sun.misc.Launcher$AppClassLoader@18b4aac2
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.core.io.impl.ResourceFactoryServiceImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.core.marshalling.impl.MarshallerProviderImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.core.concurrent.ExecutorProviderImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Loading kie.conf from jar:file:/C:/Users/bacharya/.m2/repository/org/drools/drools-compiler/7.17.0.Final/drools-compiler-7.17.0.Final.jar!/META-INF/kie.conf in classloader sun.misc.Launcher$AppClassLoader@18b4aac2
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.compiler.kie.builder.impl.KieServicesImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.compiler.builder.impl.KnowledgeBuilderFactoryServiceImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Loading kie.conf from jar:file:/C:/Users/bacharya/.m2/repository/org/drools/drools-decisiontables/7.17.0.Final/drools-decisiontables-7.17.0.Final.jar!/META-INF/kie.conf in classloader sun.misc.Launcher$AppClassLoader@18b4aac2
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.drools.decisiontable.DecisionTableProviderImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Loading kie.conf from jar:file:/C:/Users/bacharya/.m2/repository/org/kie/kie-internal/7.17.0.Final/kie-internal-7.17.0.Final.jar!/META-INF/kie.conf in classloader sun.misc.Launcher$AppClassLoader@18b4aac2
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.kie.internal.services.KieAssemblersImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.kie.internal.services.KieRuntimesImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.kie.internal.services.KieWeaversImpl
> [main] INFO org.kie.api.internal.utils.ServiceDiscoveryImpl - Adding Service org.kie.internal.services.KieBeliefsImpl
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11664) EJB client 4 is unable to discover EJB after WildFly crash during previous call and reboot
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin... ]
Ivan Straka commented on WFLY-11664:
------------------------------------
[~flavia.rainone] I have assigned to you the issue, since JBEAP-16318 has been automatically assigned to you.
> EJB client 4 is unable to discover EJB after WildFly crash during previous call and reboot
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11664
> URL: https://issues.jboss.org/browse/WFLY-11664
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 14.0.0.Final, 15.0.0.Final
> Reporter: Ivan Straka
> Assignee: Flavia Rainone
> Priority: Blocker
> Attachments: reproducer.zip
>
>
> Issue is not valid for 7.2.0.CD12 (upstream client: 12.0.0.Final) therefore we consider this as a blocker.
> Lets have two WildFly servers and same EJB on both. They have nothing to do with each other. And the client app that call beans on them.
> *Scenario*
> # Client invokes _hello_ method on the first server which crash during the call. Exception is consumed.
> # Client calls successfully _hello_ method on the second one.
> # Now, the first server is started again and then the client (same thread) try to call _hello_ on the first one. The call should be successful but the client is unable to discover bean.
> {code:java}Exception in thread "main" java.lang.RuntimeException: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
> at client.Client.call(Client.java:41)
> at client.Client.main(Client.java:21)
> Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:592)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:133)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:115)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:79)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:172)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:938)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:177)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112)
> at com.sun.proxy.$Proxy0.hello(Unknown Source)
> at client.Client.call(Client.java:35)
> ... 1 more
> {code}
> I hit this issue with 15.0.0.Final, 14.0.0.Final but not with 12.0.0.Final.
> If client try to invoke _hello_ on the first server before it reboots (exception is consumed), there is no problem after.
> *Client side*
> {code:java}
> public static void main(String[] args)
> throws Exception {
> call("server-2", true);
> call("server-1", true);
> for (int i = 30; i > 0; i--) {
> System.out.println(i);
> Thread.sleep(1000);
> }
> call("server-1", false);
> }
> public static Properties getCtxProperties() {
> Properties props = new Properties();
> props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
> return props;
> }
> public static void call(String container, boolean exceptedFailure) {
> try {
> InitialContext ctx = new InitialContext(getCtxProperties());
> String lookupName = "ejb:/" + container + "/HelloBean!ejb.HelloBeanRemote";
> HelloBeanRemote bean = (HelloBeanRemote) ctx.lookup(lookupName);
> System.out.println(bean.hello());
> } catch (Exception e) {
> if (exceptedFailure) {
> System.out.println("EXPECTED FAILURE");
> e.printStackTrace();
> } else {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> *Server side*
> {code:java}
> @Stateless
> @Remote(HelloBeanRemote.class)
> public class HelloBean {
> private static Logger log = Logger.getLogger(HelloBean.class);
> public String hello() throws RemoteException {
> log.info("hello called with message");
> return "Hello there";
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (WFLY-11664) EJB client 4 is unable to discover EJB after WildFly crash during previous call and reboot
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin... ]
Ivan Straka reassigned WFLY-11664:
----------------------------------
Assignee: Flavia Rainone
> EJB client 4 is unable to discover EJB after WildFly crash during previous call and reboot
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11664
> URL: https://issues.jboss.org/browse/WFLY-11664
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 14.0.0.Final, 15.0.0.Final
> Reporter: Ivan Straka
> Assignee: Flavia Rainone
> Priority: Blocker
> Attachments: reproducer.zip
>
>
> Issue is not valid for 7.2.0.CD12 (upstream client: 12.0.0.Final) therefore we consider this as a blocker.
> Lets have two WildFly servers and same EJB on both. They have nothing to do with each other. And the client app that call beans on them.
> *Scenario*
> # Client invokes _hello_ method on the first server which crash during the call. Exception is consumed.
> # Client calls successfully _hello_ method on the second one.
> # Now, the first server is started again and then the client (same thread) try to call _hello_ on the first one. The call should be successful but the client is unable to discover bean.
> {code:java}Exception in thread "main" java.lang.RuntimeException: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
> at client.Client.call(Client.java:41)
> at client.Client.main(Client.java:21)
> Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:592)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:133)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:115)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:79)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:172)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
> at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:938)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:177)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112)
> at com.sun.proxy.$Proxy0.hello(Unknown Source)
> at client.Client.call(Client.java:35)
> ... 1 more
> {code}
> I hit this issue with 15.0.0.Final, 14.0.0.Final but not with 12.0.0.Final.
> If client try to invoke _hello_ on the first server before it reboots (exception is consumed), there is no problem after.
> *Client side*
> {code:java}
> public static void main(String[] args)
> throws Exception {
> call("server-2", true);
> call("server-1", true);
> for (int i = 30; i > 0; i--) {
> System.out.println(i);
> Thread.sleep(1000);
> }
> call("server-1", false);
> }
> public static Properties getCtxProperties() {
> Properties props = new Properties();
> props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
> return props;
> }
> public static void call(String container, boolean exceptedFailure) {
> try {
> InitialContext ctx = new InitialContext(getCtxProperties());
> String lookupName = "ejb:/" + container + "/HelloBean!ejb.HelloBeanRemote";
> HelloBeanRemote bean = (HelloBeanRemote) ctx.lookup(lookupName);
> System.out.println(bean.hello());
> } catch (Exception e) {
> if (exceptedFailure) {
> System.out.println("EXPECTED FAILURE");
> e.printStackTrace();
> } else {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> *Server side*
> {code:java}
> @Stateless
> @Remote(HelloBeanRemote.class)
> public class HelloBean {
> private static Logger log = Logger.getLogger(HelloBean.class);
> public String hello() throws RemoteException {
> log.info("hello called with message");
> return "Hello there";
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months