Databases
StackOverflow2013
Postsdbo
POJars for Seam API: FileNotFoundException during deployment
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJars for Seam API: FileNotFoundException during deployment
    primarykey
    data
    text
    <p>i've got a problem deploying my WAR bundling seam, seam-ui and seam-debug. When I start the JBossAS 6 Final from eclipse 3.8 or from run.bat under Win7 x64, I get the following Exception:</p> <pre><code>12:17:06,383 WARN [URLScanner] could not read entries: java.io.FileNotFoundException: C:\jboss-6.0.0.Final\server\default\deploy\aboutme-0.0.1-SNAPSHOT.war\WEB-INF\lib\jboss-seam-2.2.2.Final.jar ([The system could not find the path]) at java.util.zip.ZipFile.open(Native Method) [:1.6.0_26] at java.util.zip.ZipFile.&lt;init&gt;(Unknown Source) [:1.6.0_26] at java.util.zip.ZipFile.&lt;init&gt;(Unknown Source) [:1.6.0_26] at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [:2.2.2.Final] at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [:2.2.2.Final] at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [:2.2.2.Final] at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [:2.2.2.Final] at org.jboss.seam.init.Initialization.create(Initialization.java:130) [:2.2.2.Final] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [:2.2.2.Final] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3369) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [:1.6.0_26] at java.lang.reflect.Method.invoke(Unknown Source) [:1.6.0_26] [...] </code></pre> <p>for all three seam jars. What might be the reason for JBossAS not to be able to read the mentioned directory?</p> <p>In eclipse, I checked "Deploy as compressed archive." (The same error occured without that check mark).</p> <p>Any advice is appreciated. Best regards!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJanez
    1. USTheDM
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJars for Seam API: FileNotFoundException during deployment
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POJars for Seam API: FileNotFoundException during deployment
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload