[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1862) Ear/jar packaging behaving weird on Eclipse 3.2.2
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Thu Apr 24 20:13:19 EDT 2008
[ http://jira.jboss.com/jira/browse/JBIDE-1862?page=comments#action_12410630 ]
Denis Golovin commented on JBIDE-1862:
--------------------------------------
Also I got weird exception, that happened during publishing seam ear 1.2 and seam ear 2.0 projects, but cannot replicate it now.
java.lang.OutOfMemoryError: Requested array size exceeds VM limit
at org.eclipse.wst.server.core.internal.ModulePublishInfo.loadResource(ModulePublishInfo.java:189)
at org.eclipse.wst.server.core.internal.ModulePublishInfo.load(ModulePublishInfo.java:184)
at org.eclipse.wst.server.core.internal.ModulePublishInfo.<init>(ModulePublishInfo.java:84)
at org.eclipse.wst.server.core.internal.ServerPublishInfo.load(ServerPublishInfo.java:274)
at org.eclipse.wst.server.core.internal.ServerPublishInfo.<init>(ServerPublishInfo.java:56)
at org.eclipse.wst.server.core.internal.PublishInfo.getServerPublishInfo(PublishInfo.java:75)
at org.eclipse.wst.server.core.internal.Server.getServerPublishInfo(Server.java:843)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:886)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Ear/jar packaging behaving weird on Eclipse 3.2.2
> -------------------------------------------------
>
> Key: JBIDE-1862
> URL: http://jira.jboss.com/jira/browse/JBIDE-1862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS, Seam
> Affects Versions: 2.0.0.GA
> Environment: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135187#4135187
> Reporter: Max Rydahl Andersen
> Assigned To: Anton Klimkovich
> Priority: Blocker
> Fix For: 2.1
>
>
> Something weird is happing with jboss-seam.jar in ear packaging. See the forum for details.
> Apparently fixing application.xml apparently fixes it but why?
--
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
More information about the jbosstools-issues
mailing list