[JBoss JIRA] Created: (JBIDE-5152) JBoss AS plugin deploys Project Artifacts with wrong extention
by Erick Menezes (JIRA)
JBoss AS plugin deploys Project Artifacts with wrong extention
--------------------------------------------------------------
Key: JBIDE-5152
URL: https://jira.jboss.org/jira/browse/JBIDE-5152
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives, JBossAS
Affects Versions: 3.1.0.M4
Environment: Linux
Eclipse 3.5.SR1
Java 6 update 16
JBossTools 3.1.0.M4
Reporter: Erick Menezes
Assignee: Rob Stryker
I have a XXX.ear file, created using Project Archive, it deploys as XXX.ear.jar/XXX.ear file on the deployment folder. It adds this XXX.ear.jar on top of the ear's structure, but the rest is just like I created.
This used to work on JBoss Tools 3.1.0.M2, I worked this around by just replacing the JBossAS plugin from the M2 version with the M4 version and worked nicely.
Steps to reproduce: 1) Create a Java Project
2) Create a EAR file using the Project Archive plugin
3) Add the archive created to the JBoss instance to be used
4) Start the JBoss, deploying the EAR
5) Open the deployment folder and see the EAR's wrong extension
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-5034) Assign Properties editor allows copy operation that validator complains about
by Jeff DeLong (JIRA)
Assign Properties editor allows copy operation that validator complains about
-----------------------------------------------------------------------------
Key: JBIDE-5034
URL: https://jira.jboss.org/jira/browse/JBIDE-5034
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Environment: JBoss BPEL Editor 1.0.0.v200909110340M-H277-M3 with Eclipse 3.5 on Mac
Reporter: Jeff DeLong
The Assign Properties editor allow the following XML to be created:
<bpel:assign validate="no" name="AssignDataForBuyFailed">
<bpel:copy>
<bpel:from>
<bpel:literal xml:space="preserve"><tns:BuyFailed xmlns:tns="http://www.example.org/Store/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<fault></fault>
</tns:BuyFailed>
</bpel:literal>
</bpel:from>
<bpel:to variable="buyFailedVar" part="parameters"></bpel:to>
</bpel:copy>
<bpel:copy>
<bpel:from part="parameters" variable="creditCheckInvalidVar">
<bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
<![CDATA[fault]]>
</bpel:query>
</bpel:from>
<bpel:to part="parameters" variable="buyFailedVar">
<bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
<![CDATA[fault]]>
</bpel:query>
</bpel:to>
</bpel:copy>
</bpel:assign>
See attached screen shot for what this looks like in the property editor. However this generates the following error message:
Description Resource Path Location Type
The LocationPath expression "child::fault" is not allowed in expressions as there is no implicit context node present. PurchaseGoodsProcess_Store.bpel /StoreProcess/bpel line 86 BPEL Validation Marker
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-5098) Support XSLT Transform capability in BPEL Assign activity
by Jeff DeLong (JIRA)
Support XSLT Transform capability in BPEL Assign activity
---------------------------------------------------------
Key: JBIDE-5098
URL: https://jira.jboss.org/jira/browse/JBIDE-5098
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.1.0.M3
Reporter: Jeff DeLong
Test out and clarify the support for the BPEL XSLT Transform capability in BPEL Assign activity.
I used the Assign Property Editor and chose Expression from the From drop down list, used Expression language Same as Process(XPath 1.0 in BPEL 2.0). I seem to have a bit of a problem with the code completion. control spacebar just lists my variables. If I then type in bpel: and hit control space, I see the bpel:doXslTransform(...). However if I select it I wind up with bpel:bpel:doXslTransform(...).
Also, the Editor created it with the ![CDATA. Is this correct? It seems that
<bpel:copy>
<bpel:from>bpel:doXslTransform(...)
is sufficient.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-5150) NullPointerException occures while searching for the Seam Declarations made in JARs.
by Victor Rubezhny (JIRA)
NullPointerException occures while searching for the Seam Declarations made in JARs.
------------------------------------------------------------------------------------
Key: JBIDE-5150
URL: https://jira.jboss.org/jira/browse/JBIDE-5150
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common, jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.1.0.CR1
When searching for the Seam Variable declared in a JAR archive the NullPointerException occures:
!ENTRY org.jboss.tools.seam.ui 4 0 2009-11-05 19:49:35.042
!MESSAGE
!STACK 0
java.lang.NullPointerException
at org.jboss.tools.seam.ui.search.SeamElementMatch.<init>(SeamElementMatch.java:45)
at org.jboss.tools.seam.ui.search.SeamSearchQuery$SeamSearchResultCollector.acceptSeamDeclarationSourceReferenceMatch(SeamSearchQuery.java:140)
at org.jboss.tools.seam.ui.search.SeamSearchVisitor.processSeamDeclarationsInProject(SeamSearchVisitor.java:843)
at org.jboss.tools.seam.ui.search.SeamSearchVisitor.processSeamProjects(SeamSearchVisitor.java:452)
at org.jboss.tools.seam.ui.search.SeamSearchVisitor.searchForDeclarations(SeamSearchVisitor.java:434)
at org.jboss.tools.seam.ui.search.SeamSearchVisitor.search(SeamSearchVisitor.java:393)
at org.jboss.tools.seam.ui.search.SeamSearchEngine$1.search(SeamSearchEngine.java:208)
at org.jboss.tools.seam.ui.search.SeamSearchEngine$1.search(SeamSearchEngine.java:108)
at org.jboss.tools.seam.ui.search.SeamSearchQuery.queryByTokens(SeamSearchQuery.java:276)
at org.jboss.tools.seam.ui.search.SeamSearchQuery.run(SeamSearchQuery.java:259)
at org.eclipse.search2.internal.ui.InternalSearchUI$1.run(InternalSearchUI.java:220)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months