Re: [JBoss-dev] J2EE Connector spec

2001-07-18 Thread Tomasz Skutnik

Tomasz Skutnik wrote:

> I've submitted 3 patches on SourceForge that finish the job. Your CVS 
> update was not complete (see description in patch no 1).
> 
> Review and submitt if you please.
> 
> -- 
> 
> Tomasz Skutnik
> <[EMAIL PROTECTED]>
> 
> 
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

I have some problems using SF patch tracker. Can't attach diffs (gzipped 
   or plain) - SF says : Error, invalid filename. Any ideas what's wrong ?

Here are these patches

 jboss.diff.gz
 jbosspool.diff.gz
 jbosscx.diff.gz


RE: [JBoss-dev] J2EE Connector spec

2001-07-18 Thread Jay Walters

Sorry, should have said started us down the road to pfd2.  I did enough to
get the j2ee tutorial connector working.

I've taken these three patches and I'll apply them to CVS.  Thanks for your
work...

-Original Message-
From: Tomasz Skutnik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 8:08 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] J2EE Connector spec


I've submitted 3 patches on SourceForge that finish the job. Your CVS 
update was not complete (see description in patch no 1).

Review and submitt if you please.

--

Tomasz Skutnik
<[EMAIL PROTECTED]>


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] J2EE Connector spec

2001-07-18 Thread Tomasz Skutnik

Tomasz Skutnik wrote:

> I've submitted 3 patches on SourceForge that finish the job. Your CVS 
> update was not complete (see description in patch no 1).
> 
> Review and submitt if you please.
> 
> -- 
> 
> Tomasz Skutnik
> <[EMAIL PROTECTED]>
> 
> 
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 


Sorry. I've had some problems submittin patches. Here there are.

Scooter


Only in jboss/jbosspool/: build
Only in jboss/jbosspool/: dist
diff -r -u --exclude=*CVS* jboss.orig/jbosspool/src/resources/jdbc-rar/META-INF/ra.xml 
jboss/jbosspool/src/resources/jdbc-rar/META-INF/ra.xml
--- jboss.orig/jbosspool/src/resources/jdbc-rar/META-INF/ra.xml Wed Jul 18 04:52:40 
2001
+++ jboss/jbosspool/src/resources/jdbc-rar/META-INF/ra.xml  Wed Jul 18 09:37:08 
+2001
@@ -72,10 +72,10 @@
 Driver
 java.lang.String
 
-
-basic-password
+
+
+BasicPassword
 
javax.resource.security.PasswordCredential
-
+
 false
 
 


Only in jboss/jbosscx/: build
Only in jboss/jbosscx/: dist
diff -r -u --exclude=*CVS* 
jboss.orig/jbosscx/src/main/org/jboss/resource/RARMetaData.java 
jboss/jbosscx/src/main/org/jboss/resource/RARMetaData.java
--- jboss.orig/jbosscx/src/main/org/jboss/resource/RARMetaData.java Wed Jul 18 
04:53:51 2001
+++ jboss/jbosscx/src/main/org/jboss/resource/RARMetaData.java  Wed Jul 18 09:12:40 
+2001
@@ -345,12 +345,12 @@
   log.warning("Loading "+getElementContent(element).trim());
}
 
-   private void setAuthMechanism(Element element) throws DeploymentException
+   private void setAuthenticationMechanism(Element element) throws DeploymentException
{
   invokeChildren(element);
}
 
-   private void setAuthMechType(Element element) throws DeploymentException
+   private void setAuthenticationMechanismType(Element element) throws 
+DeploymentException
{
   authMechType = getElementContent(element);
}
diff -r -u --exclude=*CVS* 
jboss.orig/jbosscx/src/main/org/jboss/resource/security/ManyToOnePrincipalMapping.java 
jboss/jbosscx/src/main/org/jboss/resource/security/ManyToOnePrincipalMapping.java
--- 
jboss.orig/jbosscx/src/main/org/jboss/resource/security/ManyToOnePrincipalMapping.java 
 Tue Feb  6 07:54:41 2001
+++ jboss/jbosscx/src/main/org/jboss/resource/security/ManyToOnePrincipalMapping.java  
+ Wed Jul 18 13:41:41 2001
@@ -61,7 +61,7 @@
   Subject subject = new Subject();
   subject.getPrincipals().add(resourcePrincipal);
 
-  if (metadata.getAuthMechType().equals("basic-password"))
+  if (metadata.getAuthMechType().equals("BasicPassword"))
   {
  // The spec says that we need a new instance of this every
  // time, because it is specific to a managed connection
@@ -74,7 +74,7 @@
   }
   else
   {
- throw new RuntimeException("Unsupported auth-mech-type: '" +
+ throw new RuntimeException("Unsupported authentication-mechanism-type: '" +
 metadata.getAuthMechType() + "'");
   }
 


diff -r -u --exclude=*CVS* 
jboss.orig/jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml 
jboss/jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml
--- jboss.orig/jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml Wed Jul 18 
05:01:52 2001
+++ jboss/jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml  Wed Jul 18 09:17:41 
+2001
@@ -18,10 +18,10 @@
 java.lang.String
 java:DefaultJMSProvider
 
-
-basic-password
+
+
+BasicPassword
 
javax.resource.security.PasswordCredential
-
+
 false
 
 
diff -r -u --exclude=*CVS* 
jboss.orig/jboss/src/resources/org/jboss/metadata/connector_1_0.dtd 
jboss/jboss/src/resources/org/jboss/metadata/connector_1_0.dtd
--- jboss.orig/jboss/src/resources/org/jboss/metadata/connector_1_0.dtd Fri Feb  2 
11:12:48 2001
+++ jboss/jboss/src/resources/org/jboss/metadata/connector_1_0.dtd  Wed Jul 18 
+09:34:22 2001
@@ -101,7 +101,7 @@
 one or more authentication mechanisms supported and additional 
 required security permissions.
 
-If there is no auth-mechanism specified as part of resource adapter
+If there is no authentication-mechanism specified as part of resource adapter
 element then the resource adapter does not support any standard
 security authentication mechanisms as part of security contract.
 The application server ignores the security part of the system 
@@ -112,22 +112,22 @@
 managedconnectionfactory-class, connectionfactory-interface, 
 connectionfactory-impl-class, connection-interface, 
 connection-impl-class, transaction-support, config-property*, 
-auth-mechanism*, reauthentication-support, security-permission* 
+authentication-mechanism*, reauthentication-support, security-permission* 
 )>
 
 
-

Re: [JBoss-dev] J2EE Connector spec

2001-07-18 Thread Tomasz Skutnik

I've submitted 3 patches on SourceForge that finish the job. Your CVS 
update was not complete (see description in patch no 1).

Review and submitt if you please.

--

Tomasz Skutnik
<[EMAIL PROTECTED]>


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] J2EE Connector spec

2001-07-17 Thread Toby Allsopp

On Tue, Jul 17, 2001 at 10:17:31AM +0200, Tomasz Skutnik wrote:
> Hi !
> 
> I'd like to know what is the policy of JBoss J2EE interfaces development 
>? My problem is that I'm implementing WebDAV connector using J2EE 
> connector specification (PFD2 - Proposed Final Draft - 05 April 2001, 
> acquired from www.jcp.org), but JBoss jboss-j2ee.jar contains classes 
> with outdated interfaces (according to this spec). My question is : 
> What's the JBoss policy of implementing (or keeping up-to-date) with 
> specs ? Are we going to move to newer spec (although it's still only 
> PFD) or wait for official release ?

I'm not aware of any general policy on this, but I'd imagine that the
idea is to keep as up to date as possible in the main CVS branch.

Updating JBossCX to PFD2 is something I've been intending to do for
a while (I even logged a job-thingy at SourceForge to remind
myself).  I've had other priorities for a while (and will continue to
have them for a while longer, I hope).

> Taking that we try to follow specs as fast as possible (even PFDs/Drafts 
> etc.) should I post diffs to patch jboss-j2ee.jar sources (removed 4 
> methods from javax.resource.cci.ConnectionFactory interface, few changes 
> in org.jboss.RARDeployer to take deployment descriptor changes into 
> account, and possibly modifying DDs of existings connectors) ? Of course 
> there'll be impact on existing deployment/connector code/DDs, but it 
> should also be quite simple.

I don't think it's necessary to worry too much about backward
compatibility in the main CVS branch.  You'd need to update the
jboss-j2ee interfaces, the JBossCX stuff and the bundled resource
adapters (the JDBC ones from JBossPool and the JMS one from wherever
its source is).

If you want to do this, I'd be grateful.  Submit a patch to SourceForge
and I'll try to find time to review and commit it.

Toby.

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development