Similar to Tomcat 7, the WAR works fine inside of JBoss 5

-Matthias

On Tue, Jan 11, 2011 at 9:43 AM, Matthias Wessendorf <mat...@apache.org> wrote:
> Hi,
>
> on tomcat 7 it works (I just had to add MyFaces 1.2.9 and JSTL 1.2 to
> the demo WAR file).
> I want to try JBoss AS5, but jboss.org is currently down.
>
> I gave Stan silvert a heads up on this issue as well (he thought that
> Tomcat 7 may have
> the same issue - but it works in beta-5)
>
> -Matthias
>
> On Mon, Jan 10, 2011 at 7:43 PM, Christian Kaltepoth
> <christ...@kaltepoth.de> wrote:
>> As far as I know the schemaLocation attribute must always contain the
>> namespace and the location of the XSD file. Specifying only the
>> location of the XSD is wrong in my option as it is not clear for which
>> namespace the XSD is (without downloading it of cause).
>>
>> But I might be wrong. I didn't find the correct section in the spec yet! :-)
>>
>> Christian
>>
>> 2011/1/10 Matthias Wessendorf <mat...@apache.org>:
>>> meh...
>>>
>>> 19:22:49,086 WARN  [SaxJBossXBParser] SchemaLocation: schemaLocation
>>> value = 'http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd'
>>> must have even number of URI's. @
>>> vfs:///home/matzew/JBoss6/jboss-6.0.0.Final/server/default/deploy/trinidad-demo-1.2.14.war/WEB-INF/lib/trinidad-impl-1.2.14.jar/META-INF/tr.tld[1,238]
>>> 19:22:49,102 WARN  [JBossEntityResolver] Trying to resolve systemId as
>>> a non-file URL: http://java.sun.com/xml/ns/javaee
>>>
>>>
>>>
>>> this sucks :)
>>>
>>> Question is... should the container resolve it, or is the current behavior 
>>> OK...
>>>
>>> -Matthias
>>>
>>>
>>> On Mon, Jan 10, 2011 at 7:08 PM, Matthias Wessendorf <mat...@apache.org> 
>>> wrote:
>>>> looks like we are OK here.
>>>>
>>>> (currently downloading JBoss to check details early 2morrow)
>>>>
>>>> -M
>>>>
>>>> On Mon, Jan 10, 2011 at 7:06 PM, Matthias Wessendorf <mat...@apache.org> 
>>>> wrote:
>>>>> It looks like the TLD starts with the correct namespaces
>>>>>
>>>>> <taglib 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/web-jsptaglibrary_2_1.xsd";
>>>>> version="2.1">
>>>>>
>>>>>
>>>>>  <display-name>Apache Trinidad Core</display-name>
>>>>> .......................
>>>>> .......................
>>>>>
>>>>> -Matthias
>>>>>
>>>>> On Mon, Jan 10, 2011 at 7:04 PM, Matthias Wessendorf <mat...@apache.org> 
>>>>> wrote:
>>>>>> So basically JBoss' JavaEE 6 container is not backwards compatible to 
>>>>>> EE5.
>>>>>>
>>>>>> Why are the URLs and elements outdated? Aren't say valid for JavaEE 5 ?
>>>>>>
>>>>>> -Matthias
>>>>>>
>>>>>> On Mon, Jan 10, 2011 at 6:09 PM, Christian Kaltepoth
>>>>>> <christ...@kaltepoth.de> wrote:
>>>>>>> Hey Matthias,
>>>>>>>
>>>>>>> Although not being a team member I would like to add a comment on
>>>>>>> this. I recently had major problems deploying some of the MyFaces
>>>>>>> artifacts to the just released JBoss AS 6.0.0.Final. The problems were
>>>>>>> caused by invalid TLD descriptors generated by the MyFaces Builder
>>>>>>> Plugin. As far as I can tell the current trunk of Trinidad for JSF 1.2
>>>>>>> is also affected by this. Perhaps it would be a good idea if somebody
>>>>>>> of the Trinidad team takes a look at this before starting the release.
>>>>>>>
>>>>>>> Please refer to the following Tomahawk issue for details:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/TOMAHAWK-1560
>>>>>>>
>>>>>>> Kind regards
>>>>>>>
>>>>>>>  Christian
>>>>>>>
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/TOMAHAWK-1560
>>>>>>> 2011/1/10, Matthias Wessendorf <mat...@apache.org>:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I've created a Trinidad 1.2.14 release candidate, with the following
>>>>>>>> artifacts
>>>>>>>> up for a vote:
>>>>>>>>
>>>>>>>> SVN source tag (r1057250):
>>>>>>>> http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.14/
>>>>>>>>
>>>>>>>> Maven staging repo:
>>>>>>>> https://repository.apache.org/content/repositories/orgapachemyfaces-013/
>>>>>>>>
>>>>>>>> Source release:
>>>>>>>> https://repository.apache.org/content/repositories/orgapachemyfaces-013/org/apache/myfaces/trinidad/trinidad/1.2.14/trinidad-1.2.14-source-release.zip
>>>>>>>>
>>>>>>>> Vote will be open for 72 hours.
>>>>>>>>
>>>>>>>> [ ] +1  approve
>>>>>>>> [ ] +0  no opinion
>>>>>>>> [ ] -1  disapprove (and reason why)
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Matthias
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Christian Kaltepoth
>>>>>>> Blog: http://chkal.blogspot.com/
>>>>>>> Twitter: http://twitter.com/chkal
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Christian Kaltepoth
>> Blog: http://chkal.blogspot.com/
>> Twitter: http://twitter.com/chkal
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Reply via email to