[
http://jira.jboss.com/jira/browse/JBMETA-27?page=comments#action_12410836 ]
Scott M Stark commented on JBMETA-27:
-------------------------------------
Again this is an issue of merging with an application-client.xml:
...
<post-construct>
<lifecycle-callback-method>postConstruct</lifecycle-callback-method>
</post-construct>
<pre-destroy>
<lifecycle-callback-method>preDestroy</lifecycle-callback-method>
</pre-destroy>
<callback-handler>org.jboss.test.ee5client.client.TestCallbackHandler</callback-handler>
</application-client>
Duplicate postConstruct lifecycle metadata for simple app client
----------------------------------------------------------------
Key: JBMETA-27
URL:
http://jira.jboss.com/jira/browse/JBMETA-27
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.Beta9
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 1.0.0.Beta10
I'm seeing 3 LifecycleCallbackMetaData postConstructs show up in the
JBossClientMetaData for a simple client like the following. There should only be one.
public class HelloWorldClient
{
@EJB
private static HelloWorldService helloWorldService;
@Resource(name="msg")
private static String msg;
private static String result;
@Resource(mappedName="ConnectionFactory")
private static ConnectionFactory connectionFactory;
@Resource(name="messageReplier")
private static Destination destination;
private static int postConstructCalls = 0;
public static int getPostConstructCalls()
{
return postConstructCalls;
}
...
@PostConstruct
public static void postConstruct()
{
postConstructCalls++;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira