[ANN] JBoss Integration Plugin Announcements

New versions of the JBoss Integration plugin will be announced under this topic. If you want to get informed automatically about new versions then please select the "Watch this Topic" option.

80 comments

Changes since version 0.8:

- support for JBoss 3.2.6-RC1 and 4.0.0-RC2;
- UI changes;
- bug fixes

0

Hey Martin,

This version is getting much better.

A quick note. When switching an existing module to jboss, and I have jboss
4.0 setup, the module deployment descriptor seems to default to jboss 3.2.
I think it would help prevent mistakes if it defaulted to the right
descriptor based on the server version picked.

Thanks
R


On 9/10/04 7:12 AM, in article
8018811.1094814736701.JavaMail.itn@is.intellij.net, "Martin Fuhrer"
<mf@fuhrer.com> wrote:

Changes since version 0.8:

- support for JBoss 3.2.6-RC1 and 4.0.0-RC2;
- UI changes;
- bug fixes


0

Seems the app doesn't get deployed, or it doesn't know it's deployed. I'm
still finding 2 issues:
1- App doesn't get deployed, or deployment status is unknown
2- There seems to be no way to set the context path where I would usually
find it under deployment tab.

I'm on OS X, so that might be something that's causing some differences on
startup and deployment.

These are the last 4 lines I see:
07:52:15,960 INFO Saw org.jboss.system.server.started
notification, starting connectors
07:52:16,241 INFO Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
07:52:16,371 INFO JK2: ajp13 listening on /0.0.0.0:8009
07:52:16,380 INFO Jk running ID=0 time=2/40 config=null

R


On 9/10/04 7:12 AM, in article
8018811.1094814736701.JavaMail.itn@is.intellij.net, "Martin Fuhrer"
<mf@fuhrer.com> wrote:

Changes since version 0.8:

- support for JBoss 3.2.6-RC1 and 4.0.0-RC2;
- UI changes;
- bug fixes


0

After waiting a long while this is the exception I get:

07:54:58,523 ERROR Error writing response
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.ja
va:1639)
at
java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutp
utStream.java:1548)
at
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146)
at
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1241)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1355)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
at org.jnp.server.Main.run(Main.java:295)
at java.lang.Thread.run(Thread.java:552)
07:55:45,588 ERROR Error writing response

I don't get this if I start jboss on its own.

R


On 9/10/04 7:12 AM, in article
8018811.1094814736701.JavaMail.itn@is.intellij.net, "Martin Fuhrer"
<mf@fuhrer.com> wrote:

Changes since version 0.8:

- support for JBoss 3.2.6-RC1 and 4.0.0-RC2;
- UI changes;
- bug fixes


0

Unfortunately I don't have access to the current module when I'm asked for the default descriptor version, therefore I don't know what version of JBoss you're currently using. JetBrains is still hiding a lot of functionality from us... :)

A quick note. When switching an existing module to
jboss, and I have jboss
4.0 setup, the module deployment descriptor seems to
default to jboss 3.2.
I think it would help prevent mistakes if it
defaulted to the right
descriptor based on the server version picked.

0

1- App doesn't get deployed, or deployment status is
unknown


Could you please send me you're idea.log file? I'm pretty sure there's some trace of the problem in it.

2- There seems to be no way to set the context path
where I would usually
find it under deployment tab.


I can't set the context path from the deployment tab, because the context path has to be written to the deployment descriptor. You can set the context path either in the web module settings or in the app module settings.

See also http://www.intellij.net/forums/thread.jsp?forum=18&thread=105874&message=3376223#3371431

0

Changes since version 0.9:

- bug when changing application server fixed

0

See http://www.intellij.net/forums/thread.jsp?forum=18&thread=123722

(It's quite a lot of text there, so this time it's worth reading it...)

0

Important:
Please update immediately to this version if you have previously installed version 1.8 or 1.9.

0

Please sign in to leave a comment.