[JBoss JIRA] Created: (JBIDE-2190) Seam 2.0.1 EAR web project can not be started on JBoss AS 4.3
by Anton Klimkovich (JIRA)
Seam 2.0.1 EAR web project can not be started on JBoss AS 4.3
-------------------------------------------------------------
Key: JBIDE-2190
URL: http://jira.jboss.com/jira/browse/JBIDE-2190
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.1.0.CR1
Environment: JDK 1.5.0
OS=win32, ARCH=x86, WS=win32
1.1.0.CR1
Reporter: Anton Klimkovich
Attachments: exception.txt
EXECUTE: Create Seam 2.0.1 Ear web project
ASSERT: jboss-seam.jar deployed to server
EXECUTE: Press Clean/Publish button
ASSERT: *-ejb.jar appeares in deploy directory
EXECUTE: Run project on Jboss AS 4.3
FAILURE: The project can not be started because of some exceptions in console.
Log attached. (exception.txt)
Created Seam 2.0.1 Ear web project can be started on Jboss AS 4.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[JBoss JIRA] Created: (JBIDE-2016) There are issues with the feature "code completion now respect "var" attributes in e.g. h:dataTable"
by Adrian Mitev (JIRA)
There are issues with the feature "code completion now respect "var" attributes in e.g. h:dataTable"
----------------------------------------------------------------------------------------------------
Key: JBIDE-2016
URL: http://jira.jboss.com/jira/browse/JBIDE-2016
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Environment: jboss tools nightly build 0404/2008, windows vista,
Reporter: Adrian Mitev
Attachments: pic1.jpg
Having the following code:
<h:dataTable value="#{myBean.users}" var="user">
<h:column>
<h:outputText value="#{user" />
</h:column>
</h:dataTable>
public class MyBean {
private List<User> users;
//getters and setters for users
}
public class User {
private String userName;
//getter and setter for userName
}
--------------------------
When the project is seam project and the class MyBean is annotated with @Name("myBean"), the CA in the dataTable works as expected.
When the project is seam project and the class MyBean is NOT annotated with @Name, but it's defined as managed bean in faces-config.xml there is CA only for the var of the datatable, but not for the properties of the var - see pic1.jps
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[JBoss JIRA] Created: (JBIDE-632) Severity and Description Path Resource Location Creation Time Id
by Steve Davidson (JIRA)
This project needs to migrate WTP
metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Severity and Description Path Resource Location Creation Time Id
This project needs to migrate WTP metadata
------------------------------------------------------------------------------------------------------------
Key: JBIDE-632
URL: http://jira.jboss.com/jira/browse/JBIDE-632
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Environment: SuSE 10.1 Linux
Intel P4 1GB Ram
KDE Desktop
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
Reporter: Steve Davidson
Assigned To: Marshall Culpepper
Quick Fix is available for this error, but does not fix it. I Googled the internet, but was unable to find anything applicable to this issue.
NOTE: I am in Texas, and can meet up anywhere in Texas, and some of the surrounding states.
-Steve
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[JBoss JIRA] Created: (JBIDE-2484) java.lang.NullPointerException when select Validate from context menu in Package Explorer
by Anton Klimkovich (JIRA)
java.lang.NullPointerException when select Validate from context menu in Package Explorer
-----------------------------------------------------------------------------------------
Key: JBIDE-2484
URL: http://jira.jboss.com/jira/browse/JBIDE-2484
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.alpha
Environment: WinXP
200807071935-nightly
Reporter: Anton Klimkovich
Assigned To: Alexey Kazakov
EXECUTE: Create Seam War web project or JSF web project
EXECUTE: Select Validate from context menu in Package Explorer for created project
FAILURE:
java.lang.NullPointerException
at org.eclipse.jpt.core.internal.validation.JpaValidator.validationMessages(JpaValidator.java:55)
at org.eclipse.jpt.core.internal.validation.JpaValidator.validate(JpaValidator.java:48)
at org.eclipse.jpt.core.internal.validation.JpaValidator.validateInJob(JpaValidator.java:77)
at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:78)
at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:689)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:559)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:523)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:662)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:527)
at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:100)
at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:60)
at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBIDE-2512) Problem with referencing libaries
by Marcin M (JIRA)
Problem with referencing libaries
----------------------------------
Key: JBIDE-2512
URL: http://jira.jboss.com/jira/browse/JBIDE-2512
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: libmanagement
Affects Versions: 2.1.2
Environment: Ububtu Linux 8.04
Reporter: Marcin M
Fix For: 2.1.3
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
version="5">
<display-name>SymNet-ear</display-name>
<module>
<web>
<web-uri>SymNet.war</web-uri>
<context-root>/SymNet</context-root>
</web>
</module>
<module>
<ejb>SymNet-ejb.jar</ejb>
</module>
<module>
<ejb>jboss-seam.jar</ejb>
</module>
</application>
such application.xml will work after patching the eclipse installation by mentioned in the thread patch.
but if you want to have your librarites to be put inside a folder (eg. lib) the problem remains
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
version="5">
<display-name>SymNet-ear</display-name>
<module>
<web>
<web-uri>SymNet.war</web-uri>
<context-root>/SymNet</context-root>
</web>
</module>
<module>
<ejb>lib/SymNet-ejb.jar</ejb>
</module>
<module>
<ejb>jboss-seam.jar</ejb>
</module>
</application>
15:41:21,000 ERROR [MainDeployer] Could not initialise deployment: file:/D:/Java/jboss-4.2.2.GA/serv
er/default/deploy/SymNet-ear.ear/
org.jboss.deployment.DeploymentException: url file:/D:/Java/jboss-4.2.2.GA/server/default/deploy/Sym
Net-ear.ear/jboss-seam.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:288)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja
va:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentSc
anner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja
va:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja
va:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months