[ANN] JBoss Plugin 0.4 Released 关注
Hi all,
This version finally fixes JSP and EJB debugging issues. You can now
properly debug both of those with JBoss/Jetty combo.
Known issue:
- There seems to be a problem with synchronizing debugged JSPs when stopping
and restarting the debugger. If you debug once, stop then start the
debugger you might get a Wrong Line:123 error or something with your line
number. I'm working on this issue, and someone at JetBrains is going to
help figure it out as soon as they're back from Java One. In the mean time,
simply delete the temp directory Jetty creates at your default temp
directory location. On windows this is usually C:\temp on Unix /tmp.
Please report any other bugs you run into.
MANY MANY thanks to Sean Clarkson for some MAJOR QA/Investigative work on
this version.
R
请先登录再写评论。
Cool. Does it work with jboss 3.2.1?
/kesh
Robert S. Sfeir wrote:
OH! You WOULD ask me that. This is next up on my list. Sorry Kesh. JBoss
3.2.1 has a different way of starting up than 3.0.x series.
I can look into it later tonight and make a second plugin for it, or find a
way to combine the two, but something tells me it needs a second one.
Also the JBoss Group asked me if I wanted to add it to the JBoss CVS, so I
might do that soon this way everything JBoss can be accessed from there.
R
"kesh" <dummy@dummy.com> wrote in message
news:bc28l4$3tf$1@is.intellij.net...
>
>
>
stopping
line
time,
on
>
Thanks for the quick response. I'll be waiting for the second one.
/kesh
Robert S. Sfeir wrote:
>>Cool. Does it work with jboss 3.2.1?
>>
>>/kesh
>>
>>Robert S. Sfeir wrote:
>>
>>
>>>Hi all,
>>>
>>>This version finally fixes JSP and EJB debugging issues. You can now
>>>properly debug both of those with JBoss/Jetty combo.
>>>
>>>Known issue:
>>>- There seems to be a problem with synchronizing debugged JSPs when
>>>and restarting the debugger. If you debug once, stop then start the
>>>debugger you might get a Wrong Line:123 error or something with your
>>>number. I'm working on this issue, and someone at JetBrains is going to
>>>help figure it out as soon as they're back from Java One. In the mean
>>>simply delete the temp directory Jetty creates at your default temp
>>>directory location. On windows this is usually C:\temp on Unix /tmp.
>>>
>>>Please report any other bugs you run into.
>>>
>>>MANY MANY thanks to Sean Clarkson for some MAJOR QA/Investigative work
>>>this version.
>>>
>>>R
>>>
>>>
>>
Hey Kesh, I gave JBoss 3.2.2 a whirl and it works fine with the plugin, so
have at it!
I'm going to upload another version later that will change the name of the
plugin, but the puppy works as expected.
The one thing I am trying to figure out, and perhaps someone on here knows,
is how to pass an argument to JBoss startup, and what the argument is, to
tell it where the default webapp directory is. What I'm trying to do is
point it to the IDEA webapp directory setup for this particular run. This
way we don't have to put the docs under JBoss' /server/default/deploy
directory. Kind of a pain to have it in there if I can avoid it, this way
projects are much easier to deal with in JBoss.
Thanks, and let me know if you hit snags.
R
"kesh" <dummy@dummy.com> wrote in message
news:bc2bbe$3tf$2@is.intellij.net...
>
>
>
JBoss
find a
I
to
>
Great. Where can I donwload it? On the wiki page there is only version 0.3.
/kesh
Robert S. Sfeir wrote:
>>Thanks for the quick response. I'll be waiting for the second one.
>>
>>/kesh
>>
>>Robert S. Sfeir wrote:
>>
>>
>>>OH! You WOULD ask me that. This is next up on my list. Sorry Kesh.
>>>3.2.1 has a different way of starting up than 3.0.x series.
>>>
>>>I can look into it later tonight and make a second plugin for it, or
>>>way to combine the two, but something tells me it needs a second one.
>>>
>>>Also the JBoss Group asked me if I wanted to add it to the JBoss CVS, so
>>>might do that soon this way everything JBoss can be accessed from there.
>>>
>>>R
>>>
>>>"kesh" <dummy@dummy.com> wrote in message
>>>news:bc28l4$3tf$1@is.intellij.net...
>>>
>>>
>>>>Cool. Does it work with jboss 3.2.1?
>>>>
>>>>/kesh
>>>>
>>>>Robert S. Sfeir wrote:
>>>>
>>>>
>>>>
>>>>>Hi all,
>>>>>
>>>>>This version finally fixes JSP and EJB debugging issues. You can now
>>>>>properly debug both of those with JBoss/Jetty combo.
>>>>>
>>>>>Known issue:
>>>>>- There seems to be a problem with synchronizing debugged JSPs when
>>>
>>>stopping
>>>
>>>
>>>>>and restarting the debugger. If you debug once, stop then start the
>>>>>debugger you might get a Wrong Line:123 error or something with your
>>>
>>>line
>>>
>>>
>>>>>number. I'm working on this issue, and someone at JetBrains is going
>>>>>help figure it out as soon as they're back from Java One. In the mean
>>>
>>>time,
>>>
>>>
>>>>>simply delete the temp directory Jetty creates at your default temp
>>>>>directory location. On windows this is usually C:\temp on Unix /tmp.
>>>>>
>>>>>Please report any other bugs you run into.
>>>>>
>>>>>MANY MANY thanks to Sean Clarkson for some MAJOR QA/Investigative work
>>>
>>>on
>>>
>>>
>>>>>this version.
>>>>>
>>>>>R
>>>>>
>>>>>
>>>>
>>>
Trying to remember my password to remove that link, everything is on
sourceforge now.
https://sourceforge.net/projects/ideajbossplugin/
Sorry for the confusion, the 0.3 version that's up there is pretty old :(
R
"kesh" <dummy@dummy.com> wrote in message
news:bcm0ed$43o$1@is.intellij.net...
0.3.
>
>
so
the
knows,
to
This
way
so
there.
mean
work
>
Ok I figured out how to get in, and changed the pages for the JBoss Plugin
completely. Now everything points to the right spots.
Sorry for any confusion I might have caused.
R
I have a problem connecting using JDBC:
I had to configure JBoss run.bat for JAVA_OPTS:
set JAVA_OPTS=-Xmx128m -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
I tried setting this in the VM Parameters but am still getting this error:
java.lang.NullPointerException
14:40:25,370 ERROR at java.util.Hashtable.put(Hashtable.java:389)
14:40:25,370 ERROR at com.trilogy.database.JDBCConnectionSource.getConnection(JDBCConnectionSource.java:51)
Any suggestions?
Thanks.
-Ross
You need to set the JDBC stuff as per instructions for JBoss, dunno why
you're adding things to the VM parameters.
You need to define a context for JDBC to use it under JNDI, you also need to
add an xml file with something like this in it:
(my file is called rex-db.xml)
rexDS jdbc:postgresql://localhost:5432/rex org.postgresql.Driver foo bar Then add another entry in the service file specific to you app, mine is called rex-service.xml. One of the pieces, but not the only one, looks like this: RexDS ]]>
<!
embedded mbean>jdbc:postgresql://localhost:5432/rex org.postgresql.Driver foo bar All this stuff is on the JBoss site and has nothing to do with the plugin. R "Ross" ]]> wrote in message
news:36269.1056055969888.JavaMail.itn@is.intellij.net...
>
JAVA_OPTS=-Xmx128m -Djava.naming.factory.initial=org.jnp.interfaces.NamingCo
ntextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfa
ces
>
>
>
com.trilogy.database.JDBCConnectionSource.getConnection(JDBCConnectionSource
.java:51)
>
>
>
>