Re: [jboss-dev-forums] [JBoss Tools Development] - Portlet Development is Effectively Unusable in JBoss Tools
by Robert Brown III
Robert Brown III [http://community.jboss.org/people/factor3] replied to the discussion
"Portlet Development is Effectively Unusable in JBoss Tools"
To view the discussion, visit: http://community.jboss.org/message/554904#554904
--------------------------------------------------------------
Greetings, all:
1. Yes, as it turns out, the Gatein Portlet Container V3 with JBoss 5.1 is exactly what I have been using.
It figures! Of all the configurations available I would end up choosing the one configuration that JBoss Tools would not recognize. I sure would make a great test engineer... :D
2. As for the user libraries: OK, perhaps the word "force" was a little too strong. How does "make life difficult if you don't" sound?
3. I do see your point, if the tools cannot detect the container then how will it be able to "find" the appropriate Jars? The problem with this is: why should the facet be "finding" anything?
You make some good points about not wanting to "shove" a particular JBoss portlet version down people's throats. But consider what "user jars"you are having people select in an environment that the Tools detects: 1. the basic JSR-286 Portlet Jar, 2. JBoss Seam Jars, and 3. JSF Jars. I submit that you are already locking people in, because the only environments that you detect are JBoss environments.
Furthermore, the jars offered are (with the exception of Seam and Seam- specific JSF tags) pretty standard for all portlets. Providing the basic portlet-api jar with the facet wouldn't be locking anybody into anything, and the Seam jars are for JBoss environments and won't change regardless of the JBoss bundle used. So again: why should the facet be "finding" anything?
The necessary jars can easily be included (within the development environment) as part of the plugin. When the facet is chosen, the jars could then be added to the classpath. You can even include different versions of some standard jars (for example: a Portlet 1 API jar in case people want to make JSR-168 portlets). That is how the Eclopse Portal Tools plugin does its thing. It uses its own copies of the jars so that the code can compile without problems. When running the test portlet container it deploys the WAR without the Jars (which shouldn't be needed at runtime because the container should already load them). That way, I don't necessarily have to depend on the facet to "find" anything. If the necessary Jar(s) are not in the container's library, then I have no business using the container in the first place.
My only question here is: why don't you folks do something similar? It is ridiculous to have a facet which you can turn on and off, then have that facet depend on what amounts to external jars that are always going to be the same anyway. Either set the classpath automatically within the facet (if you absolutely +must+ have the portal environment detection) or include the jars with the plugin and set a "development classpath" to those jars. Either way you can eliminate the need for a "user library" selection which, in the end, is clumsy from a UI standpoint and redundant in a complete and properly implemented facet.
This is, of course, just a suggestion, guys...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/554904#554904]
Start a new discussion in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
Re: [jboss-dev-forums] [jBPM Development] - JBPM-2795 erroneously filed as 'resolved'
by HuiSheng Xu
HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion
"JBPM-2795 erroneously filed as 'resolved'"
To view the discussion, visit: http://community.jboss.org/message/554902#554902
--------------------------------------------------------------
Hi Per,
So happy to see you again. There are something that need talk with you.
First I will re-open JBPM-2795 and provide a new patch later. Thank you for point out that.
Second, I want to ask you some help for some JIRA issue, if you have time, please have a look at these.
1. https://jira.jboss.org/browse/JBPM-2813 https://jira.jboss.org/browse/JBPM-2813, You notice that there is a patch, but I cannot find it. could you re-upload this patch again?
2. https://jira.jboss.org/browse/JBPM-2814 https://jira.jboss.org/browse/JBPM-2814, I marked this issue as 'Incomplete Description', because I didn't know what you want to do with custom business calendar, Could you give me some more information about these?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/554902#554902]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
[JBoss Tools Development] - Remote Debugging for Eclipse Test Plug-in Running by Tycho
by Denis Golovin
Denis Golovin [http://community.jboss.org/people/dgolovin] modified the document:
"Remote Debugging for Eclipse Test Plug-in Running by Tycho"
To view the document, visit: http://community.jboss.org/docs/DOC-15209
--------------------------------------------------------------
When I report issue in bug tracking system about nightly build's JUnit test error I usually get simple answer that it is supposed to be working because it is working on developer's workstation. After that routine conversation starts and it turns out that tests were running from development environment under Eclipse. Here I usually have to explain again and again that's not the same running tests from development environment and in build.
The right way to make yourself sure your tests will work in most cases without errors in nightly build is to start tests the same way as nightly build does. It was not easy for JBoss Tools tests until we created experimental branch and switched to Maven Tycho project. That means it is fairly easy to run tests now. Basically you need to change current directory and execute maven install goal. If it runs in development environment and in maven your tests are good and in most cases it should be fine in nightly build. Problems begin if it runs in development environment but it doesn't in maven. In this scenario you need to debug tests running in Tycho somehow and fix it. Fortunately it can be done using Java remote debugging support.
First of all you need to be sure you have built your sources you're going to debug and there is no differences between .java and .class files. If you're going find problem from previous build just get right tagged version and build it before debugging session.
There are two options to use remote debugger
1. Simple use of -DdebugPort=8001 or what ever port you would like to use
2. Add full argLine for remote debugging configuration im pom.xml
h1. Use of debugPort system properties
To use this just add -DdebugPort=<portNumber> to your maven command line replacing <portNumber> for desired port and make sure you have the same port configured in your Remote Java Application configuration in Eclipse Debug Configuration dialog as it explained for second option below.
h1. Use full argLine for remote debugging configuration in pom.xml
Open pom.xml for your Eclipse Test Plug-in and add Java VM arguments like it shown below (actual port numbers, server names and other parameters may be different, it depends from your environment)
<build>
<plugins>
<plugin>
<groupid>org.sonatype.tycho</groupid>
<artifactid>maven-osgi-test-plugin</artifactid>
<version>${tycho-version}</version>
<configuration>
<argline>-Xdebug -Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=y</argline>
</configuration>
</plugin>
</plugins>
</build>
This snipped configured for remote debugging in OpenJDK 6, if your is different you might need to read #r1 [1] and configure it right for your JVM version.
Configure java projects with sources you're going to debug in Eclipse and create Remote Java Application configuration in Eclipse Debug Configuration dialog. Fill 'host' and 'port' fields with the same values from pom.xml argLine element. Press Apply button to save your changes and start your test plug-in from terminal like
$mvn install
It will go through build process and finally you ll see something like
[INFO] Expected eclipse log file: /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data/.metadata/.log
[INFO] Command line:
/bin/sh -c cd /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test && /usr/lib/jvm/java-6-openjdk/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86 -agentlib:jdwp=transport=dt_socket,address=8001,server=y,suspend=y -jar /home/eskimo/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.0.201.R35x_v20090715/org.eclipse.equinox.launcher-1.0.201.R35x_v20090715.jar -data /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/data -dev file:/home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/dev.properties -install /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work -configuration /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/work/configuration -application org.codehaus.tycho.surefire.osgibooter.uitest -testproperties /home/eskimo/Projects/jbt-modular/jst/tests/org.jboss.tools.jst.web.kb.test/target/surefire.properties
Listening for transport dt_socket at address: 8001
At this point build is waiting for you to attach remote debugger to the process because of using
suspend=y
in argLine element of your pom.xml file. So you need to return to eclipse and hit 'Debug' button in dialog opened before.
Build will continue at this point and stop on your break points so you can find out what is wrong with tests during nightly build.
[1] http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation Java Platform Debugger Architecture - http://java.sun.com/javase/technologies/core/toolsapis/jpda/#Invocation
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15209]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 9 months