[JBoss Tools] New message: "Problem creating local mirror of JBoss Tools for 3.1 final."
by Konstantin Larionov
User development,
A new message was posted in the thread "Problem creating local mirror of JBoss Tools for 3.1 final.":
http://community.jboss.org/message/532492#532492
Author : Konstantin Larionov
Profile : http://community.jboss.org/people/KenfromMera
Message:
--------------------------------------------------------------
Hello,
We have local mirror of JBoss Tools in order to 1) avoid access to remote update site when many developers need to update Eclipse plug-ins, 2) have only needed plug-ins to make install/update process easier for newcomers and 3) reduce load on JBoss update site
Previously I used the following script to update development milestones of JBoss Tools 3.1 on our local mirror:
for %%i in (
org.jboss.tools.richfaces.feature
org.jboss.tools.seam.feature
org.jboss.tools.jmx.feature
org.jboss.ide.eclipse.as.feature
org.jboss.ide.eclipse.archives.feature
org.hibernate.eclipse.feature
org.drools.eclipse.feature
org.drools.eclipse.task.feature
org.guvnor.tools.feature
org.jboss.tools.bpel.feature
org.jboss.tools.xulrunner.feature
org.jboss.tools.jbpm.convert.feature
org.jbpm.gd.jpdl.feature
org.jboss.tools.jbpm4.feature
org.jboss.tools.flow.common.feature
org.jboss.tools.flow.jpdl4.feature
org.jboss.tools.jbpm.common.feature
) do (
call :syncf "http://download.jboss.org/jbosstools/updates/development/" %%i
)
exit
:sync
eclipse\eclipsec.exe -application org.eclipse.update.core.standaloneUpdate -command mirror -from %* -to site -noSplash -vmargs -Dhttp.proxyHost=%PROXY_HOST% -Dhttp.proxyPort=%PROXY_PORT%
exit /b
:syncf
call :sync %1 -featureId %2
exit /b
I was very happy when JBoss Tools for 3.1 final have been released and was eager to update our local mirror but failed.
Seems that the problem occurred because some feature disappeared from the http://download.jboss.org/jbosstools/updates/JBossTools-3.1.0.GA/site.xml
Namely jBPM tools:
org.jboss.tools.jbpm.common.feature
org.jboss.tools.flow.common.feature
org.jboss.tools.bpel.feature
org.jboss.tools.flow.jpdl4.feature
org.jboss.tools.jbpm4.feature
org.jbpm.gd.jpdl.feature
At the same time I can easily install these features by pointing Eclipse at http://download.jboss.org/jbosstools/updates/JBossTools-3.1.0.GA
Can anyone help in resolving my problem?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532492#532492
16 years, 4 months
[JCA] New message: "HornetQ RA integration"
by Jeff Mesnil
User development,
A new message was posted in the thread "HornetQ RA integration":
http://community.jboss.org/message/532488#532488
Author : Jeff Mesnil
Profile : http://community.jboss.org/people/jmesnil
Message:
--------------------------------------------------------------
Hi,
As you probably know, we are integrating HornetQ in AS 6 (and the clock is ticking!).
HornetQ now has its own resource adapter and no longer use the generic JMS RA.
However, I've some difficulties to understand how it fits with *-ds.xml connection factories.
<tx-connection-factory>
<jndi-name>DURABLE_SUB_CONNECTION_FACTORY</jndi-name>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.hornetq.ra.HornetQRAConnectionFactory</connection-definition>
<xa-transaction/>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="ClientID" type="java.lang.String">cts</config-property>
<max-pool-size>1</max-pool-size>
</tx-connection-factory>
I don't understand how I can find whether the managed connection factory will use XA or not when I effectively create the JMS resources in HornetQRAConnectionFactory class.
Is there a way to know whether a connection factory is using <xa-transaction /> or <local-transaction /> from the SPI or am I missing something obvious?
Thanks for the help,
jeff
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532488#532488
16 years, 4 months
[JBoss Tools] New message: "Re: Jboss tools 3.1, create a jsf 2.0 project"
by Krasimir Goutcev
User development,
A new message was posted in the thread "Jboss tools 3.1, create a jsf 2.0 project":
http://community.jboss.org/message/532487#532487
Author : Krasimir Goutcev
Profile : http://community.jboss.org/people/krasig
Message:
--------------------------------------------------------------
Next try:
1. create JSF Project 1.2 with template "JSFKickStartWthoutLibs
2. test -> OK
3. add <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
4. add facelets.jar in lib
5 create simple test.xhtm
6 test -> OK
7 replace jsf-impl and jsf-api with jsf-api-2.0.2.jar, jsf-impl-2.0.2.jar
8 test ->ok
9 add in test.xhtml <h:body> to test jsf 2.0
10 test -> error
+
com.sun.facelets.tag.TagException: /test.xhtml @7,10 <h:body> Tag Library supports namespace: http://java.sun.com/jsf/html, but no tag was defined for name: body
at com.sun.facelets.compiler.CompilationManager.pushTag(CompilationManager.java:193)
at com.sun.facelets.compiler.SAXCompiler$CompilationHandler.startElement(SAXCompiler.java:194)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:767)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:232)
at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:218)
at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:149)
at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:100)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:517)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)+
11. remove <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
12.test -> no error but xhtm is not interpreted.
Any ideas?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532487#532487
16 years, 4 months
[EJB 3.0] New message: "Re: Getting InvocationType from org.jboss.aop.joinpoint.Invocation"
by Jens Krause
User development,
A new message was posted in the thread "Getting InvocationType from org.jboss.aop.joinpoint.Invocation":
http://community.jboss.org/message/532482#532482
Author : Jens Krause
Profile : http://community.jboss.org/people/jjk77
Message:
--------------------------------------------------------------
We are using JBoss 4.3.0.GA.
The usecase is that we need to measure the time a method call takes with all interceptors attached und we also log this time to a logfile. I think the only reason we need to know if it is a local or remote call is that we could see it in the logfile :-). My supervisor said i should figure out if it is possible to get this information and i have tried a few things like to get a SessionContext in my Interceptor class to get the InvokedBusinessInterface, but this didn't work out, or to get my needed information from some metadata stored with the call ...
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532482#532482
16 years, 4 months
[jBPM] New message: "New version of process with modification in java class : the change is not taken into account"
by Valery LEPRETRE
User development,
A new message was posted in the thread "New version of process with modification in java class : the change is not taken into account":
http://community.jboss.org/message/532474#532474
Author : Valery LEPRETRE
Profile : http://community.jboss.org/people/v.lepretre@cadwin.com
Message:
--------------------------------------------------------------
Hi,
I'm using jBPM 4.3 on JBoss 5.1.0 and Oracle 10g
I've performed the jBPM installation with the following ant tasks :
ant -Ddatabase=oracle -Djboss.version=5.1.0.GA -Djbpm.home=%JBPM_HOME% -Djboss.home=%JBOSS_HOME% create.jbpm.schema
ant -Ddatabase=oracle -Djboss.version=5.1.0.GA -Djbpm.home=%JBPM_HOME% -Djboss.home=%JBOSS_HOME% install.jbpm.into.jboss
I've deployed the jBPM examples using ant task :
ant -Ddatabase=oracle -Djboss.version=5.1.0.GA -Djbpm.home=%JBPM_HOME% -Djboss.home=%JBOSS_HOME% install.examples.into.jboss
I've written an small web application (deployed on the same Jboss server as jBPM) and using the jBPM service (processEngine obtained with the getProcessEngine API) able to start the "Async" process and it works fine.
I modify the Async process just by adding some output in Application.java
public void generatePdf() {
System.out.println("generatePdf");
}
public void calculatePrimes() {
System.out.println("calculatePrimes");
}
and then I deploy.
When I start the new version of "Async", i see the correct outputs in the logs.
*Now my problem :*
I've written a small process "Test2"
<?xml version="1.0" encoding="UTF-8"?>
<process name="test2" xmlns="http://jbpm.org/4.3/jpdl">
<start name="start"
g="32,49,88,30">
<transition name="toJava1" to="java1" g="-29,-26"/>
</start>
<java name="java1" class="com.cadwin.jbpm.process.test2.Java1" method="display">
<transition name="toEnd" to="end"/>
</java>
<end name="end" g="185,507,48,48"/>
</process>
package com.cadwin.jbpm.process.test2;
public class Java1 {
public void display() {
System.out.println("Java1");
}
}
I deploy it with the same ant task as for "Async"
I start it from my web application, and It works fine (correct output in the log)
I modify the java1.java(just adding one more output)
package com.cadwin.jbpm.process.test2;
public class Java1 {
public void display() {
System.out.println("Java1");
System.out.println("Java1");
}
}
I deploy and when I start the new version of "Test2" process I see only one output in the log. (Exactly as if the process continue to use the previous version of java1.java)
If I add another output in java1.java and deploy again, I continue to see only one output in the log.
Could you help me to fix that problem?
*PS :*
If I modify the "Test2" process as follow
<java name="java1" class="com.cadwin.jbpm.process.test2.Java1_1" method="display">
<transition name="toEnd" to="end"/>
</java>
and if i copy je java1.java to java1_1.java and I deploy, the new version of process displays the two outputs.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532474#532474
16 years, 4 months
[JBoss Cache] New message: "Re: JBoss Cache usage: direct gets vs ordinary gets"
by Alex Reshetnyak
User development,
A new message was posted in the thread "JBoss Cache usage: direct gets vs ordinary gets":
http://community.jboss.org/message/532467#532467
Author : Alex Reshetnyak
Profile : http://community.jboss.org/people/areshetnyak
Message:
--------------------------------------------------------------
Hi, Manik Surtani.
Thanks for the quick responseю
We was tested our Query benchmark with eviction wakeup interval equal 500 and 2000.
Result of Query benchmark with different eviction wakeup interval :
Threads 1 2 3 4
300threads ~407tps ~458tps ~1947tps ~2593tps
1. JBoss Cache-based configuration (current one) with wakeUpInterval="2000".
2. JBoss Cache-based configuration (current one) with wakeUpInterval="500".
3. JBoss Cache-based configuration (current one) with wakeUpInterval="2000", but with patched
jcr.core, using peek/getDirect methods.
4. JBoss Cache-based configuration (current one) with wakeUpInterval="500", but with patched
jcr.core, using peek/getDirect methods.
After drop eviction wakeUpInterval to 500, we have increase performance to :
- JCR (non patched) : ~12%
- JCR (patched jcr.core, using peek/getDirect methods) ~33%
[ https://jira.jboss.org/jira/browse/EXOJCR-545 ]
https://jira.jboss.org/jira/secure/ViewProfile.jspa?name=areshetnyak - 17/Mar/10 06:44 AM The test SearchNodesByPropertyTest was checked with eviction wakeup interval equal 500 and 2000. Result of Query benchmark with different eviction wakeup interval : Threads 1 2 3 4 300threads ~407tps ~458tps ~1947tps ~2593tps 1. JBoss Cache-based configuration (current one) with wakeUpInterval="2000". 2. JBoss Cache-based configuration (current one) with wakeUpInterval="500". 3. JBoss Cache-based configuration (current one) with wakeUpInterval="2000", but with patched jcr.core, using peek/getDirect methods. 4. JBoss Cache-based configuration (current one) with wakeUpInterval="500", but with patched jcr.core, using peek/getDirect methods. After drop eviction wakeUpInterval to 500, we have increase performance to : - JCR (non patched) : ~12% - JCR (patched jcr.core, using peek/getDirect methods) ~33%
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532467#532467
16 years, 4 months