[JBoss JIRA] Created: (JBIDE-5688) java.lang.NullPointerException happens in SeamELValidator.shouldValidate(SeamELValidator.java:63) during JUnit Tests Execution
by Denis Golovin (JIRA)
java.lang.NullPointerException happens in SeamELValidator.shouldValidate(SeamELValidator.java:63) during JUnit Tests Execution
------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5688
URL: https://jira.jboss.org/jira/browse/JBIDE-5688
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: QA, Seam
Affects Versions: 3.1.0.CR2
Reporter: Denis Golovin
Assignee: Alexey Kazakov
Fix For: 3.1.0.CR2
[java] java.lang.NullPointerException
[java] at org.jboss.tools.seam.internal.core.validation.SeamELValidator.shouldValidate(SeamELValidator.java:63)
[java] at org.jboss.tools.jst.web.kb.internal.validation.ValidationContext.<init>(ValidationContext.java:84)
[java] at org.jboss.tools.jst.web.kb.internal.validation.ContextValidationHelper.getValidationContext(ContextValidationHelper.java:109)
[java] at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:58)
[java] at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
[java] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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, 6 months
[JBoss JIRA] Created: (JBDS-1063) Invalid Duplicate component name validation error
by David Hibbs (JIRA)
Invalid Duplicate component name validation error
-------------------------------------------------
Key: JBDS-1063
URL: https://jira.jboss.org/jira/browse/JBDS-1063
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: seam
Affects Versions: 3.0.0.CR1
Reporter: David Hibbs
Working from Seam In Action examples, but now with SEAM 2.2 and tools 3.1 CR1.
RegisterAction uses some additional configuration from components.xml, defined by a component element without a class specified;
<component name="registerAction">
<property name="pro-status-types">amateur pro semi-pro</property>
<property name="specialtyTypes">
<value>#{messages['specialty.drive']}</value>
<value>#{messages['specialty.chip']}</value>
<value>#{messages['specialty.putt']}</value>
<value>#{messages['specialty.iron']}</value>
<value>#{messages['specialty.looks']}</value>
</property>
</component>
The RegisterAction java source is annotated with an @Name header:
package org.open18.action;
...
@Name("registerAction")
public class RegisterAction {
Validation flags this as "Duplicate component name: "registerAction".
This does not prevent the project from building or deploying to JBoss AS 5.1, which in fact operates correctly. The validation simply flags it as an error.
This same validation works properly in Seam 2.1 and tools 3.0.1.GA-R2.
Updated to the latest nightly build (JBossTools-Update-3.1.0.v201001140301N-H131-CR2.zip) and the problem still exists.
--
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, 6 months
[JBoss JIRA] Created: (JBIDE-5669) Artifacts in lib of ear and lib of war for Maven projects
by Oliver Freivogel (JIRA)
Artifacts in lib of ear and lib of war for Maven projects
----------------------------------------------------------
Key: JBIDE-5669
URL: https://jira.jboss.org/jira/browse/JBIDE-5669
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration, JBossAS, maven
Affects Versions: 3.1.0.CR1, 3.1.0.M4
Environment: OS X 1.6.2, Eclipse Galieo for JEE 32-bit
Reporter: Oliver Freivogel
Artefacts used by EJB Modules are addded to the ear lib folder (correct) and also added to war's lib folder (incorrect). Further the ejb module itself is also added to the war's lib folder. the result are java.lang.ClassCastExceptions, because the classes are found twice and loaded by different classloaders.
I did:
1. import existing maven project
2. Add ear modul to server
3. Clean server
--
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, 6 months
[JBoss JIRA] Created: (JBIDE-5364) Make namespace prefix consistent
by Tom Fennelly (JIRA)
Make namespace prefix consistent
--------------------------------
Key: JBIDE-5364
URL: https://jira.jboss.org/jira/browse/JBIDE-5364
Project: Tools (JBoss Tools)
Issue Type: Task
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Fix For: 3.1.0.GA
Seems like the namespace prefixes come from the EMF generate code, so I didn't modify them :)
At present, they tend to include schema version numbers etc as part of the prefix. Can we have them generated such that they are consistent with what existing Smooks users i.e. without version numbers etc.
Some are already OK, but I'll list the ones (relevant to this release) I can think of anyway...
- EDI - "edi"
- CSV - "csv"
- JSON - "json"
- Javabean - "jb"
- FreeMarker - "ftl"
I think that's all that's relevant for this release :)
--
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, 6 months