[JBoss Tools] - Jboss Maven Jsf Integration: Faces-config.xml Editor Problem
by yoel.ben
yoel.ben [http://community.jboss.org/people/yoel.ben] created the discussion
"Jboss Maven Jsf Integration: Faces-config.xml Editor Problem"
To view the discussion, visit: http://community.jboss.org/message/627276#627276
--------------------------------------------------------------
Dear all,
My problem is that I want to use Eclipse JSF Faces-config editor to draw navigation rules between xhtml page.
But with the use of Jboss Maven Jsf Integration it's seem impossible (see the file in attachment).
I have detected the problem :
The Jboss plugin adds in the file *org.eclipse.wst.common.component :*
* ...*
* <wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>*
<wb-resource deploy-path="/" source-path="/src/main/webapp"/> *...*
And the Eclipse faces-config editor seems to load the first wb-resource with the attribute "source-path" and ignoring the next one.
If you inverse these two ligns. the faces editors works (we can chose Page to define Navigation rules).
But when an maven update project configuration is launch, the plugin writes *<wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>* always before <wb-resource deploy-path="/" source-path="/src/main/webapp"/>.
Is it a bug of Jboss Tools or of the Editor?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627276#627276]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months
[JBoss Messaging] - Re: close jms conection cause block
by Ivan Nushev
Ivan Nushev [http://community.jboss.org/people/ivannushev] created the discussion
"Re: close jms conection cause block"
To view the discussion, visit: http://community.jboss.org/message/611357#611357
--------------------------------------------------------------
Hi all. Just to add that I succeeded to make remote JMS MessageListeners reliable using sslservlet remoting transport. To achieve this goal I use the remoting servlet configuration packed in JBM 1.4.6.GA.SP1:
http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_6_GA_SP1... http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_6_GA_SP1...
plus a few settings for SSL flavour and a JMS Connection' javax.jms.ExceptionListener which recreate the JMS Connection and Topic subscription in case of connection exception. I attach the exact configuration used:
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=connector,transport=sslservlet,target=jms,loc=public"
display-name="JMS Public Servlet transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="sslservlet">
<!-- There should be no reason to change these parameters - warning!
Changing them may stop JBoss Messaging working correctly -->
<attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="dataType" isParam="true">jms</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">443</attribute>
<attribute name="clientConnectAddress">${public.firewall.address}</attribute>
<attribute name="clientConnectPort">443</attribute>
<attribute name="numberOfCallRetries" isParam="true">1</attribute>
<attribute name="pingFrequency" isParam="true">214748364</attribute>
<attribute name="pingWindowFactor" isParam="true">10</attribute>
<attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
<attribute name="callbackStore">org.jboss.remoting.callback.BlockingCallbackStore</attribute>
<attribute name="unwrapSingletonArrays">true</attribute>
<attribute name="path">unified-invoker/PublicJmsServerInvokerServlet</attribute>
<attribute name="return-exception">true</attribute>
<attribute name="createUniqueObjectName">true</attribute>
<attribute name="useAllParams" isParam="true">true</attribute>
<!-- End immutable parameters -->
<attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
<!-- Periodicity of client pings. Server window by default is twice this figure -->
<attribute name="clientLeasePeriod" isParam="true">10000</attribute>
<attribute name="validatorPingPeriod" isParam="true">10000</attribute>
<attribute name="validatorPingTimeout" isParam="true">5000</attribute>
<attribute name="failureDisconnectTimeout" isParam="true">0</attribute>
<attribute name="callbackErrorsAllowed">1</attribute>
<attribute name="registerCallbackListener">false</attribute>
<attribute name="useClientConnectionIdentity" isParam="true">true
</attribute>
<attribute name="timeout" isParam="true">0</attribute>
<!-- Max Number of connections in client pool. This should be significantly
higher than the max number of sessions/consumers you expect -->
<attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
<!-- Set this to true if you want the servlet transport to block waiting
for server->client traffic. Or false if you want it to poll for new traffic
periodically. Recommended is blocking -->
<attribute name="blockingMode" isParam="true">blocking</attribute>
<!-- Timeout for blocking. Only has relevance if blockingMode = blocking -->
<attribute name="blockingTimeout" isParam="true">30000</attribute>
<!-- The periodicity of polling. Only has relevance if blockingMode = nonblocking -->
<!--attribute name="callbackPollPeriod" isParam="true">10000</attribute -->
</invoker>
<handlers>
<handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler
</handler>
</handlers>
</config>
</attribute>
</mbean>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/611357#611357]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months
[JBoss Tools] - Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
by u j
u j [http://community.jboss.org/people/bcn] created the discussion
"Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported."
To view the discussion, visit: http://community.jboss.org/message/597020#597020
--------------------------------------------------------------
I try to run Eclipse with a JDK 64 bits.
Is there anything I can do to make it work?
Thanks,
Ulrich
org.jboss.tools.vpe.xulrunner.XulRunnerException: Current platform 'win32.win32.x86_64' is not supported.
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.wrapXulRunnerError(MozillaEditor.java:789)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.showXulRunnerError(MozillaEditor.java:705)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:639)
at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:902)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:231)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:440)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:164)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReferenc
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/597020#597020]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months
[jBPM] - jBPM5.1 - eclipse BPMN process editor loses imports of script tasks
by Sebastien Lelarge
Sebastien Lelarge [http://community.jboss.org/people/slelarge] created the discussion
"jBPM5.1 - eclipse BPMN process editor loses imports of script tasks"
To view the discussion, visit: http://community.jboss.org/message/614763#614763
--------------------------------------------------------------
Hi all,
I am using the eclipse BPMN process editor v5.1.0.Final (not the new one BPMN visual editor) to design my processes and I have discovered something that is really annoying.
When using script tasks with Java code inside, I use the "imports" button to import external classes and make them available in the code executed from the task. When I save my process definition just after setting imports, they are successfully saved in the generated BPMN file for this process.
The problem is that the imports disappear when I re-open the process definition in editor to update it and then save it. When the process is saved after the update, then the imports are lost.
Is this a known problem for the plugin ? Is there something am I doing wrong in task config ?
How can I solve this problem ?
I am still using this editor because I think the new one is not very useable to configure script & user tasks. Maybe future versions will be easier and intuitive to use.
regards
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/614763#614763]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 6 months