- 
        15. Re: More lenient HTTP parameter processingjfclere Sep 5, 2012 4:19 AM (in response to albertsese)see .classpath :-( 
- 
        16. Re: More lenient HTTP parameter processingalbertsese Sep 5, 2012 4:21 AM (in response to jfclere)Of course I did, what I meant was, where can I link to these jar files so I can correct the classpath and be able to build it properly... 
- 
        17. Re: More lenient HTTP parameter processinghd0815 Sep 5, 2012 4:55 AM (in response to albertsese)Try building it with Maven if possible. It should download the missing dependencies. 
- 
        18. Re: More lenient HTTP parameter processingalbertsese Sep 5, 2012 6:25 AM (in response to hd0815)Got an error... [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from D:\apache-maven-3.0.4\bin\..\conf\settings. xml [DEBUG] Reading user settings from C:\Documents and Settings\sesal\.m2\settings. xml [DEBUG] Using local repository at C:\Documents and Settings\sesal\.m2\repository [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for C:\Doc uments and Settings\sesal\.m2\repository [INFO] Scanning for projects... [DEBUG] Extension realms for project org.jboss.web:jbossweb:jar:7.7.0-SNAPSHOT: (none) [DEBUG] Looking up lifecyle mappings for packaging jar from ClassRealm[plexus.co re, parent: null] [DEBUG] === REACTOR BUILD PLAN ================================================ [DEBUG] Project: org.jboss.web:jbossweb:jar:7.7.0-SNAPSHOT [DEBUG] Tasks: [compile] [DEBUG] Style: Regular [DEBUG] ======================================================================= [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Web 7.7.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-so urces, generate-resources, process-resources, compile, process-classes, generate -test-sources, process-test-sources, generate-test-resources, process-test-resou rces, test-compile, process-test-classes, test, prepare-package, package, pre-in tegration-test, integration-test, post-integration-test, verify, install, deploy ] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [WARNING] The POM for org.jboss.maven.plugins:maven-injection-plugin:jar:1.0.2 i s missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.313s [INFO] Finished at: Wed Sep 05 18:24:01 SGT 2012 [INFO] Final Memory: 3M/15M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.jboss.maven.plugins:maven-injection-plugin:1.0.2 or one of it s dependencies could not be resolved: Failed to read artifact descriptor for org .jboss.maven.plugins:maven-injection-plugin:jar:1.0.2: Failure to find org.jboss .maven.plugins:maven-injection-plugin:pom:1.0.2 in http://repo.maven.apache.org/ maven2 was cached in the local repository, resolution will not be reattempted un til the update interval of central has elapsed or updates are forced -> [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.jboss.maven.plugin s:maven-injection-plugin:1.0.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.jboss.maven.plugins:maven-injection- plugin:jar:1.0.2 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.re solve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginD escriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDes criptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(D efaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalc ulator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:152) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalc ulator.setupMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:139) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalc ulator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalc ulator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:129) at org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(Bu ilderCommon.java:92) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje ct(LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje ct(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu ild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl eStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun cher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav a:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La uncher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: 352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.jboss.maven.plugins:maven-injection-plugin:jar :1.0.2 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader. loadPom(DefaultArtifactDescriptorReader.java:296) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader. readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifac tDescriptor(DefaultRepositorySystem.java:279) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.re solve(DefaultPluginDependenciesResolver.java:115) ... 25 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure t o find org.jboss.maven.plugins:maven-injection-plugin:pom:1.0.2 in http://repo.m aven.apache.org/maven2 was cached in the local repository, resolution will not b e reattempted until the update interval of central has elapsed or updates are fo rced at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def aultArtifactResolver.java:538) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti facts(DefaultArtifactResolver.java:216) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti fact(DefaultArtifactResolver.java:193) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader. loadPom(DefaultArtifactDescriptorReader.java:281) ... 28 more Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to fi nd org.jboss.maven.plugins:maven-injection-plugin:pom:1.0.2 in http://repo.maven .apache.org/maven2 was cached in the local repository, resolution will not be re attempted until the update interval of central has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newExcept ion(DefaultUpdateCheckManager.java:230) at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArti fact(DefaultUpdateCheckManager.java:204) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def aultArtifactResolver.java:427) ... 31 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResoluti onException Sorry I'm not really good at this... And I haven't used Maven before... 
- 
        19. Re: More lenient HTTP parameter processingalbertsese Sep 5, 2012 8:46 AM (in response to hd0815)I tried running using Ant also (followed the instructions in BUILDING.txt), but I got a lot of FileNotFoundException errors... 
- 
        20. Re: More lenient HTTP parameter processinghd0815 Sep 5, 2012 8:52 AM (in response to albertsese)Remove the mentioned plugin from the Maven configuration. It's not needed to compile the files. I did so too. 
- 
        21. Re: More lenient HTTP parameter processingalbertsese Sep 5, 2012 9:09 AM (in response to hd0815)It worked; got another similar error, this time with jasper-jdt, so I removed that dependency, and now I have these errors... [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[38,36] error: package org.eclipse.jdt.core.compiler do es not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[39,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[40,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[41,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[42,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[43,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[44,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[45,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[46,49] error: package org.eclipse.jdt.internal.compile r.classfmt does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[47,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[48,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[49,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[50,45] error: package org.eclipse.jdt.internal.compile r.impl does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[51,48] error: package org.eclipse.jdt.internal.compile r.problem does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CoyoteMessages.java:[102,16] error: Message id 2019 is not unique for messageMethod i nvalidCrlf with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CoyoteMessages.java:[105,16] error: Message id 2019 is not unique for messageMethod i nvalidChunkHeader with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[296,26] error: Message id 86 is not unique for messageMethod e xpiresInvalidDurationUnit with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[290,26] error: Message id 86 is not unique for messageMethod e xpiresInvalidDuration with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[383,11] error: Parameter count does not match for format 'The response to this request can be found under a different URI (%s).'. Required: 1 Provided: 0 [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[197,26] error: Parameter count does not match for format 'Erro r invoking onStartAsync on listener of class {0}'. Required: 0 Provided: 1 [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[299,29] error: Message id 87 is not unique for messageMethod r equestFilterInvalidPattern with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaMessages.java:[293,26] error: Message id 87 is not unique for messageMethod e xpiresDurationUnitNotFound with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaLogger.java:[135,9] error: Message id 1012 is not unique for messageMethod fa iledProtocolJmxRegistration with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\jboss\web\CatalinaLogger.java:[131,9] error: Message id 1012 is not unique for messageMethod co nnectorAlreadyStarted with project code JBWEB. [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[38,36] error: package org.eclipse.jdt.core.compiler do es not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[39,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[40,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[41,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[42,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[43,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[44,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[45,40] error: package org.eclipse.jdt.internal.compile r does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[46,49] error: package org.eclipse.jdt.internal.compile r.classfmt does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[47,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[48,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[49,44] error: package org.eclipse.jdt.internal.compile r.env does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[50,45] error: package org.eclipse.jdt.internal.compile r.impl does not exist [ERROR] \JavaWork\jbossweb\src\main\java\org\apache\jasper\compiler\JDTCompiler.java:[51,48] error: package org.eclipse.jdt.internal.compile r.problem does not exist **D:\JavaWork\jbossweb is my jbossweb.source path Obviously the jdt errors is because I removed the jasper-jdt dependency... This is the error that I got before I removed it... [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Web 7.7.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [WARNING] The POM for org.jboss.web:jasper-jdt:jar:7.0.3.Final is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.063s [INFO] Finished at: Wed Sep 05 21:07:48 SGT 2012 [INFO] Final Memory: 3M/15M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project jbossweb: Could not resolve dependencies for project org.jboss.web:jbossweb:jar:7.7.0-SNAPSHOT: Fa ilure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project jbossweb: Could not resolve dependencies for proje ct org.jboss.web:jbossweb:jar:7.7.0-SNAPSHOT: Failure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http://repo.maven.apache.org/maven 2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are for ced at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.jboss.web:jbossweb:jar:7.7 .0-SNAPSHOT: Failure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http://repo.maven.apache.org/maven2 was cached in the local reposit ory, resolution will not be reattempted until the update interval of central has elapsed or updates are forced at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185) ... 22 more Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http:// repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183) ... 23 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http://re po.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has e lapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358) ... 24 more Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find org.jboss.web:jasper-jdt:jar:7.0.3.Final in http://repo.m aven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elaps ed or updates are forced at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230) at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427) ... 26 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException And how about the duplicate message IDs? Can I just assign other IDs? 
- 
        22. Re: More lenient HTTP parameter processinghd0815 Sep 5, 2012 9:13 AM (in response to albertsese)You shouldn't remove any dependencies, I asked to remove the plugin maven-injection-plugin. Also it seems that your source path is wrong, it should be $JBOSSWEB_HOME/src/main/java. If your having problems with Maven you should try the tutorials on their website: http://maven.apache.org/users/index.html 
- 
        23. Re: More lenient HTTP parameter processingjfclere Sep 5, 2012 10:22 AM (in response to hd0815)ant download ant is the way to build... you have to be patient with the eclipse compiler part it takes ages to download. 
- 
        24. Re: More lenient HTTP parameter processingalbertsese Sep 6, 2012 12:47 AM (in response to hd0815)hd0815 wrote: You shouldn't remove any dependencies, I asked to remove the plugin maven-injection-plugin. Also it seems that your source path is wrong, it should be $JBOSSWEB_HOME/src/main/java. If your having problems with Maven you should try the tutorials on their website: http://maven.apache.org/users/index.html Sorry, when I said jbossweb.source path, I meant that's where my jbossweb project is, and not the project's source folder. I don't think I'm having a problem with compiling via Maven... The problem is it can't find the jasper-jdt.jar... 
- 
        25. Re: More lenient HTTP parameter processingalbertsese Sep 6, 2012 12:35 AM (in response to jfclere)Jean-Frederic Clere wrote: ant download ant is the way to build... you have to be patient with the eclipse compiler part it takes ages to download. Yep that's what I did... Got errors in ant download... Buildfile: D:\JavaWork\jbossweb\build.xml download: proxyflags: setproxy: testexist: [echo] Testing for ${destfile} downloadzip: [get] Getting: http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip [get] To: D:\usr\share\java\file.zip [get] Error opening connection java.io.FileNotFoundException: http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip [get] Error opening connection java.io.FileNotFoundException: http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip [get] Error opening connection java.io.FileNotFoundException: http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip [get] Can't get http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip to D:\usr\share\java\file.zip BUILD FAILED D:\JavaWork\jbossweb\build.xml:410: The following error occurred while executing this line: D:\JavaWork\jbossweb\build.xml:385: Can't get http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/org.eclipse.jdt-3.7.zip to D:\usr\share\java\file.zip Total time: 1 second 
- 
        26. Re: More lenient HTTP parameter processingalbertsese Sep 6, 2012 2:18 AM (in response to hd0815)So I decided to download the jars individually... I was able to finally build it... Get the Parameters.class and overwrite the one in the jbossweb jar... And then it doesn't work. My server doesn't start up... This is too much work and I think I'll just use 7.0.2.Final instead... Anyway thanks for everybody's help. 
- 
        27. Re: More lenient HTTP parameter processinghd0815 Sep 6, 2012 2:32 AM (in response to albertsese)I recompiled Parameters.java with my configuration. Replace the class file in the jar of your JBoss installation with the one I appended. This should be working. Everytime the request has such an invalid parameter, a log entry with 'invalid chunk ignored' will be created. Be sure to make a copy of your jbossweb.jar before replacing the class file. - 
            
                            
            Parameters.class.zip 4.5 KB
 
- 
            
                            
            
- 
        28. Re: More lenient HTTP parameter processingalbertsese Sep 6, 2012 2:37 AM (in response to hd0815)This will be my last try... Thanks again. 
 
     
    