Oops. Ok, I think this is because we started parsing ejb-jar.xml in Seam2,
which, if it has a dtd in it, we will attempt to resolve. I've pinged Norman.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062873#4062873
Reply to the post :
Michael, the app is packaged in the classic ear/war way, if the proxy is
correctly configured, it works.
However, as Pete stated it, this parsing stuff is new with seam2 and I don't
think this is aceptable that, on startup, the application makes hundreds of
call on internet to validate all the
Hi titou09,
While we (well, Norman :)) are fixing this issue, could you share your app with
me? I am interesting in seeing working WebSphere apps for Seam2. Thanks a lot.
cheers
Michael
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063043#4063043
Reply to
I've fixed this problem in CVS. Please reopen the related JIRA issue if there
are any other related issues.
http://jira.jboss.com/jira/browse/JBSEAM-1646
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063112#4063112
Reply to the post :
Thx. I'll test it when the next (beta?) release will be out.
Michael, I've sent you a minimal ear file to test seam 2.0beta on was v6.1.0.9
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063205#4063205
Reply to the post :
Given there is a dtd available at that address, I can't see why there is a
problem there. And util.DTDEntityResolver is nothing from Seam. Sorry to not
be more help, maybe Michael Yuan knows more.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062738#4062738
Hmm, what is the example app you are trying to run? Is your server connected to
the Internet?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062743#4062743
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062743
Pete, this is org.jboss.seam.util.DTDEntityResolver.
Michael, yes it is ...but behind a proxy...and it does not appear to be
configured correctly (at least the properties in the JVM are not correctly set)
BUT. Even if it was correctly configured, I don't want to have seam connect
hundreds
Since you are not using EJB, the app should be packaged in a WAR and WAS should
not try to validate the ejb-jar.xml. Perhaps you can try the JPA example and
see if it works in WAS? (I had some problems before, but your mileage may vary)
I am not exactly sure why seam is connecting to
