Afaik we used to support this:
| <bean name="GetInstance" class="org.jboss.test.kernel.deployment.support.GetInstanceBean">
| <constructor factoryMethod="getInstance"/>
| </bean>
|
| public class GetInstanceBean
| {
| private static final GetInstanceBean instance = new GetInstanceBean("X");
|
| private GetInstanceBean(String x)
| {
| }
|
| public static GetInstanceBean getInstance()
| {
| return instance;
| }
| }
|
Meaning when there was no factoryClass,
the bean's class attribute was used.
I guess this got lost with transition to jbossxb?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191770#4191770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191770
anonymous wrote : I assume the second line is reporting a satisfied dependency and not an unsatisfied one!
|
This means that the profiler depends on an external communication module to access it from a remote client - otherwise the only access to the information will be in-VM.
anonymous wrote :
| When I debug and stop at ProfilerThreadImpl.java, line 226, I find that activeFrame (and hence fi) is null and this apparently causes the NPE. Why is this happening? Is there something wrong with my configuration, or is there something in the newer version of JBoss (4.3) that's causing this?
|
Fixed in SVN -- I'll cut a new beta soon to get this fix out.
Thanks for the feedback !
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191767#4191767
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191767
Ok, I'll say it differently. The real problem is letting internal details, like VFS options, leak to the client.
The client only cares about deploying a URL. He doesn't care how this should be done or what is VFS and especially not what VFS options would be needed to workaround a particular problem.
If we need to workaround the problem for this particular testcase, that's easy, just introduce a small delay and a note pointing to a JIRA with future work on this.
Extending the MainDeployer api with implentation details doesn't offer any real value, it just complicates things.
And BTW, I think all VFS options should be visible in bootstrap/vfs.xml with the user able to override them in the command line, or by modifying the file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191764#4191764
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191764
Hi!
Just a quick question: Why is ONLY the installer available for the new release? I got the question already a couple of times and for myself the same is true: If I want to update to the latest jbpm I only need the jbpm-jpdl.jar. But I cannot download it standalone any more? And with the installer I am forced to install jbpm into a JBoss AS?
I think the jar should be provided standalone too! Or was I too blind to find it somewhere?
Cheers
Bernd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191742#4191742
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191742