[JBoss Remoting] New message: "Remote client receives 'connection refused'"
by Dongjun Sun
User development,
A new message was posted in the thread "Remote client receives 'connection refused'":
http://community.jboss.org/message/523777#523777
Author : Dongjun Sun
Profile : http://community.jboss.org/people/sean171
Message:
--------------------------------------------------------------
JBoss 4.2.0 with JBoss Remoting 2.2.2SP1. The server is started with "-b 0.0.0.0"
We have a remote client using http(s) transport. On upgrading JBoss Remoting to 2.2.2SP11 (tried 2.3.x and 2.5.x also). We start to see 'connection refused' on the remote client side.
Looking at the packet trace when JR 2.2.2SP1 is used, the ip address returned in the proxy contains a valid server IP address (x.y.z.w). However on other versions or patches, the ip address returned in the proxy is all "0.0.0.0".
>From the JR doc, the client InvokeLocator will try to connect to "localhost" for no avail.
Any thoughts would be appreciated.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523777#523777
16 years, 2 months
[JBoss Tools] New message: "Re: Adding JBoss AS source to a project"
by henk de boer
User development,
A new message was posted in the thread "Adding JBoss AS source to a project":
http://community.jboss.org/message/523775#523775
Author : henk de boer
Profile : http://community.jboss.org/people/henk53
Message:
--------------------------------------------------------------
> mailto:max.andersen@jboss.com wrote:
>
> > henk53 wrote:
> >
> > > mailto:max.andersen@jboss.com wrote:
> > >
> > > If your project is setup to locate sources correctly then any debug launches that refer to that project should also work - if not then please report a bug.
> >
> > Forgive my ignorance, but how do I exactly setup my project to locate sources correctly?
> Attach sources to jars on your projects build path, incl. the jars in the AS classpath container.
That's precisely what I do. I mean, what else is there to do?
To be really clear, what I precisely do is:
I right click on my project root, select properties and go to java build path -> Libraries. I unfold a jar file listed there, select "Source attachment" click edit, and locate the correct source jar.
Alternatively, I unfold my project root in project explorer, go to Java Resources -> Libraries and select a jar for which I want to attach the source. I then right click the jar, select properties and go to Java Source Attachment, where I click Workspace... to locate my source jar.
I figure both ways are just different means that yield the exact same end result; an entry in .classpath like:
For the jars in the AS classpath container I pretty much do the same thing as mentioned above, with the small difference that I first need to unfold "Jboss 5.1 Runtime" and then attach the source to the jars listed beneath that using properties -> Java Source Attachment again.
All of this is pretty basic and is what I've been doing for my Java SE projects in base Eclipse/JDT and in MyEclipse for years. Only in Eclipse/WTP/Jboss AS Tools that I recently started using, the debugger can't find the source after I've done the above. I can browser the source though by unfolding a jar, browsing it and then clicking on any .class file it contains. ctrl-clicking into it using the Java editor also works.
I'm using JBossTools-3.1.0.CR1 btw. If this is not the expected behavior then it seems like a bug that is basically unrelated to the topic of this thread (an easy way to attach all the Jboss AS source code for a project).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523775#523775
16 years, 2 months
[JBoss Tools] New message: "Re: Adding JBoss AS source to a project"
by Denis Golovin
User development,
A new message was posted in the thread "Adding JBoss AS source to a project":
http://community.jboss.org/message/523770#523770
Author : Denis Golovin
Profile : http://community.jboss.org/people/dgolovin
Message:
--------------------------------------------------------------
> henk53 wrote:
>
> > mailto:max.andersen@jboss.com wrote:
> >
> > If your project is setup to locate sources correctly then any debug launches that refer to that project should also work - if not then please report a bug.
>
> Using the debug view I then add both the EJB and web projects to the source lookup and then it can find the source of the .java file that is directly in the project.
It looks like lunch configuration for server should be altered after project deployed/undployed to/from the server. WTP JBoss AS adapter does that but JBossTools JBossAS adapter doesn't.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523770#523770
16 years, 2 months
[jBPM] New message: "Upgrade from JBPM3 to JBPM4 woes"
by nick bauman
User development,
A new message was posted in the thread "Upgrade from JBPM3 to JBPM4 woes":
http://community.jboss.org/message/523768#523768
Author : nick bauman
Profile : http://community.jboss.org/people/nick.bauman
Message:
--------------------------------------------------------------
Hello,
I'm looking into upgrading our process definitions and integration / embedding code written in JBPM3 to JBPM4. Our code does not use any application server like JBoss so we do not rely on container or third party integration. We also are not using any persistent store because we have our own cluster synchronization technology.
Needless to say I see quite a lot has changed now that version 4 has arrived. The JBPM3 technology was more of a classic Finite State Machine. JBPM4 seems to have a new layer of abstraction: I see no sign of any GraphElement, Node, State, Transition, ActionHandler, ExecutionContext etc etc. I'm having a hard time seeing where these things morphed into or whether the original FSM idiom is simply gone. Stuff like "Swimlane" and "Task" strikes me as quite the departure so I'm not holding much hope.
Currently we have several dozen process definitions ranging from 10 to 40 elements, the larger ones end up being around 1500 lines of XML. Is it even worth it to try and figure out where JBPM4 can fit into a migration strategy from JBPM3? I see some stuff that's named similarly in a package called org.jbpm...internal (that "internal" seems quite the red flag) that unfortunately isn't even close to the old code interface-wise.
Specifically can anyone tell me where GraphElement, Node, State, Transition, ActionHandler, ExecutionContext may have gone or how they've changed?
Thanks,
Nick
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523768#523768
16 years, 2 months