I'm getting fresh from CVS just to make sure...
Adrian Brock wrote:
I'm just testing it at the moment.
I committed the code such that Dimitris can also work/test on it.
Actually I'm testing in 4.0.x, but trying to keep the two
codebases in step. Maybe I didn't port something correctly,
let me c
I'm just testing it at the moment.
I committed the code such that Dimitris can also work/test on it.
Actually I'm testing in 4.0.x, but trying to keep the two
codebases in step. Maybe I didn't port something correctly,
let me check...
On Fri, 2005-06-17 at 11:36, Bill Burke wrote:
> It is hanging
It is hanging in JDBCStateManager:
"main" prio=1 tid=0x08129510 nid=0x2d18 in Object.wait()
[0x526a1000..0x526a3e20]
at java.lang.Object.wait(Native Method)
- waiting on <0x45e51380> (a org.jboss.tm.TransactionImpl)
at java.lang.Object.wait(Object.java:474)
at or
I think it is web services:
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jboss.ws.metadata.WebServiceInterceptor
Also, the ejb-deployer is failing to start up...
I'm going to take out the WebServices interceptor unless it is fixed soon.
Regards,
Bill
--
Bill Burke
Chie
No different than using the package on monday-saturday.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexey Loubyansky
> Sent: Friday, June 17, 2005 6:47 AM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] Can we remov
Later this weekend, I'll be merging JBoss XB to Branch_4_0 and also
changing the package name of jboss xb to org.jboss.xb. as we discussed a
few weeks ago. I want EJB3 to be usable on older versions of JBoss4,
hence the reasons for the package name change.
Bill
--
Bill Burke
Chief Architect
v7 is a very bad choice for the package name in the given case.
Imagine the API is released with version number 1.0. Now we have v7 1.0.
Then we have releases v7 1.1, 2.0, etc.
At the end v7 as the shortcut of 'version 7' does not make any sense.
Scott M Stark wrote:
v7 would have been infini
v7 would have been infinitely better. What is your alternate meaning?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexey Loubyansky
> Sent: Friday, June 17, 2005 2:08 AM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev]
I removed references to MappingObjectModelFactory from WS/JAXB. After WS
guys confirm there are no problems with the change we can remove the hack.
Thomas, could you please check? I ran the jaxb tests. They are not
affected. Thanks.
alex
Scott M Stark wrote:
In rebuilding the 4.0 thirdparty
Alexey Loubyansky wrote:
Scott M Stark wrote:
So let's remove it. And while we are at it, are we keeping this
uninformative package name: org.jboss.xml.binding.sunday? It makes me
wonder if it only works on
sunday, or if I recently went to church or something.
I have very different associa
Scott M Stark wrote:
So let's remove it. And while we are at it, are we keeping this
uninformative package name:
org.jboss.xml.binding.sunday? It makes me wonder if it only works on
sunday, or if I recently went to church or something.
I have very different associations with the word :)
It's
Yes, but it will affect the users of MappingObjectModelFactory who rely
on default binding rules.
Scott M Stark wrote:
The org.jboss.xml.binding.UnmarshallerImpl class, which is using the
XniJBossXBParser by default, is the only usage I find in the 4.0 branch.
Can this use the SaxJBossXBParser
12 matches
Mail list logo
